BHI260AB - Accuracy change events not received

[btruden_henway]

Hello,

I'm using a BHI260AB hosted by an STM32 micro over SPI. The BHI260AB is mounted in a custom board together with a BMM150. 

I'm downloading the following firmware to the chip and booting from RAM successfully :

https://github.com/BoschSensortec/BHY2-Sensor-API/blob/master/firmware/bhi260ab/Bosch_SHUTTLE_BHI260...

I then enable the Gravity virtual sensor and the Rotation Vector virtual sensor successfully. I start receiving samples on the Non-wakeup FIFO for both virtual sensors.

As soon as I enable the Gravity virtual sensor I get a Meta Event of Sensor Status changed, which indicates that the Gravity virtual sensor has changed to accuracy = 3 (the maximum).

But for the Rotation Vector virtual sensor, I never get any Meta Event indicating that the Sensor Status has changed.

I'm following the procedure indicated in the Youtube video: https://www.youtube.com/watch?v=Bw0WuAyGsnY

I note that in the video, the BNO055 chip reports the accuracy for the physical sensors (accelerometer, gyro, magnetometer). But in my case, where I use the BHI260AB Gravity virtual sensor and the Rotation Vector virtual sensor, I only get the Gravity virtual sensor Sensor Status meta event, not the Rotation Vector Sensor Status event or any physical sensor status change event.

How can I know if my chip is in the maximum accuracy and ready for use?

Thanks!

[btruden_henway · Accepted solution]

Hello BSTRobin, 

I've found the issue here. There is a problem with the firmware provided on github (https://github.com/BoschSensortec/BHY2-Sensor-API/blob/master/firmware/bhi260ab/Bosch_SHUTTLE_BHI260.... Using that firmware the Accelerometer Corrected Sensor Status meta event is not generated by the fuser2 core processor.

I had to generate the BHI260AB firmware by using Eclipse IDE and the BHI260AB SDK v1.1.6. With that firmware, all the events are generated successfully. 

Please notify the corresponding sector in your company about this issue.

Regards

[BSTRobin]

Hi btruden_henway,

Thank for your feedback. We also did the test and found this issue accel calibration status was not received.

We will update BHI260AB fw in github.