Bosch Shared
- Top Results
See all results
- About jjanus
- About jjanus
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About jjanus
since
07-21-2021
08-30-2022
jjanus
Member
4
Posts
0
Likes
0
Solutions
06-27-2022
01:17 PM
Hello Jakub, in my case it turned out to be a hardware related problem. After I replaced the chip with a new one, my software worked just fine and the error was gone. It is unfortunate that BST does not provide documentation on these error code as this could have saved a lot of time. Best regards, Josua Janus
... View more
12-10-2021
03:20 PM
Hello BSTRobin, the part is a BHI160B and the firmware is the standalone BHI160B firmware provided here: https://www.bosch-sensortec.com/media/boschsensortec/downloads/firmware/bhi160_b_firmware/20210616_update/bosch_pcb_7183_di03_bmi160-7183_di03-2-1-11824.fw I tried to get it to work with the Arduino driver (https://github.com/BoschSensortec/BoschSensorHub) and a self-developed driver. The self-developed driver runs on bare-metal and does not use any Arduino related code. However, I used the communication logging feature of the Arduino driver and our custom one to compare them and they produced the same output. Finally, I compared it to the bhy1 driver (https://github.com/BoschSensortec/BHy1_driver_and_MCU_solution.git) by using a mocked I2C function, which resulted in the same sequence of I2C transactions (the mocked I2C return the correct ROM version and CRC when requested). Therefore, I reckon, the initialization sequence is fine and the I2C communication is working properly. Also, the RAM version is reported after enabling the CPU. Best regards, Josua Janus
... View more
12-03-2021
04:47 PM
Hello, I am trying to get the BHI160 to start. However, after uploading the RAM patch successfully the BHI160 generates an error meta event and stops working. More precisely, I can read the following sequence of bytes from the FIFO: "0xFD, 0x00, 0x00, 0xFC, 0x8F, 0x04, 0xFE, 0x04, 0x22, 0x15". According to the datasheet (Table 29), "0xFD, 0x00, 0x00" and "0xFC, 0x8F, 0x04" are timestamp events and "0xFE, 0x04, 0x22, 0x15" is a meta event signaling an error. My question is, how to interpret the two payload bytes of this event? The datasheet states, that byte 1 contains the "Error Register" and byte 2 the "Debug State", but I cannot find any documentation on either of them. Best regards, Josua Janus
... View more
- Tags:
- BHI160
07-21-2021
12:42 PM
Hello, we are planning to use the BNO055 in a product and would like to use the Data Ready Interrupts. However, according to the Datasheet, firmware version 3.14 and above is required for this functionality (p. 56, note 6). The preprogrammed version is 3.11 (p. 56, note 6). The datasheet also states "In case there is a firmware update, then an application note would be available in time with the necessary information to upgrade at the host side." (p. 51, 3.10 Bootloader). We would like to use our host MCU to update the firmware via I2C. Can you provide example code or a specification for bootloader protocol? Kind regards, Josua Janus
... View more
Still looking for something?
- Top Results
See all results