About btruden_henway

btruden_henway

Hello BSTRobin, Please see if you can access the code now from the following link. This link corresponds to the file bhi260ab.c which I created and is the file that uses the bhy2 API. https://codeshare.io/BAp8ep Below is the schematic of our board. I'm not using the Shuttle board, it's a custom board. This is the firmware that I used: https://codeshare.io/DZNV1r I downloaded it from the following link: https://github.com/BoschSensortec/BHY2-Sensor-API/blob/master/firmware/bhi260ab/Bosch_SHUTTLE_BHI260_BMM150.fw.h Something important to mention is that I have this board already working with another API, an API that was developed by me. So the hardware is working correctly. With that custom API, I'm able to upload the firmware to the BHI and enable any virtual sensor that I want. But the reason why now I'm trying to use the Bosch API is because with my custom API I'm not able to catch the Meta Events that indicate when the sensor accuracy changes. So now, I'd like to use the Bosch API and see if I'm able to catch the Sensor Status meta events. BR

btruden_henway

Hello Bosch team, I'm using a BHI260AB hosted by an STM32 micro communicating over SPI. I want to upload the BHI firmware and boot from RAM. For accomplishing that, I've used the API offered in: https://github.com/BoschSensortec/BHY2-Sensor-API I based my implementation on the example: https://github.com/BoschSensortec/BHY2-Sensor-API/tree/master/examples/load_firmware But unfortunately, after successfully transferring the firmware over SPI, the boot from RAM process fails. More specifically, the API function bhy2_hif_check_boot_status_ram() times out. Checking the register 0x25 (Boot Status register), the value is 0b01111000. Where the bit6 is Firmware Verify Error. So the firmware verification is throwing an error. Here's a link from where you can download my code: https://drive.google.com/file/d/1cF9MUF7viVbqwoKUXT2Wzcf6CpWkPVY_/view?usp=sharing For the BHI firmware, I used the one that is located at: https://github.com/BoschSensortec/BHY2-Sensor-API/blob/master/firmware/bhi260ab/Bosch_SHUTTLE_BHI260_BMM150.fw.h. My implementation is in the file called bhi260ab.c Could you please help me to understand what could be the issue?

btruden_henway

Hello BSTRobin, thank you for your reply. I think that it happens if I start the test and do movements with the physical sensors not calibrated, or with low accuracy. If I refresh the right panel before the discontinuity event the accelerometer and magnetometer are with low accuracy (1~2). And right after the discontinuity event, I refresh the right pannel and all the sensors are with full accuracy.

btruden_henway

Hi, I was doing tests with my Application Board and a BHI160 Shuttle board. I'm running the Development Desktop application and reading both the Game Rotation Vector and the Rotation Vector simultaneously, and drawing the w,x,y, and x curves for each of them in real-time. At the beginning of the test all seem to be pretty normal, both virtual sensors present the same curves. But at some point the Rotation Vector presents a discontinuity. From that moment onwards the Rotation Vector curves are different from the Game Rotation Vector curves. See below picture for having a clearer understanding: I have a custom board with a BHI260AB on it and it's presenting the same behavior. I recently added a BMM150 magnetometer to my board and wanted to change from using the Game Rotation Vector to the Rotation Vector for better accuracy. But unfortunately, I'm having that strange behavior of the Rotation Vector. Could you please help me to understand what's happening and to find a way for solving the issue? Thanks!

btruden_henway

Hey sebp, It seems that there's no way rather than to catch the event.

Bosch Shared

About btruden_henway

Re: BHI260AB - Boot from RAM Error using bhy2 API

BHI260AB - Boot from RAM Error using bhy2 API

Re: BHI260AB Rotation Vector curve discontinuity

BHI260AB Rotation Vector curve discontinuity

Re: BHI260AB calibration

Still looking for something?