Bosch Shared
- Top Results
See all results
- About MartinIOT
- About MartinIOT
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About MartinIOT
since
01-23-2024
05-27-2024
MartinIOT
Member
5
Posts
1
Likes
0
Solutions
03-01-2024
02:14 AM
Actually my question, if the OCSB-pin instead of the JTAG_DIO-pin could be read by the BHI360-firmware to detect new data by BMM350, was to rescue our prototypes with "wrong" wiring. But now we detected that the JTAG-DIO-pin (pin 16) is an inner pin, more dificult to reach then the OCSB-pin (pin 10) which would make a more complex/more expensive hardware-design necessary. That said, it would be more important for us to have the feature to use the BHI360-OCSB-pin to connect to BMM350-INT, i.e. again the question if that can be changed in the BHI360-firmware? Additional question as alternative to keep hardware-design-complexity low: the pin 18 should be unused, same for pin 10, by the BHI360-firmware - would it be possible to use this two pins as "bridge" to make pin 16 accesible, i.e. connect pin 16 to pin 18, and pin 18 to pin 10 and pin 10 to BMM350-INT?
... View more
02-29-2024
06:08 PM
@FCO_VK Thank you for sharing your analisis! I have the exact same symptoms (my post from 24.01. "BMM350 connected to BHI360 – hardware and firmware", although I had connected BMM350-INT, but unfortunately to BHI360-OCSB. Concerning your failed self test of physical sensor 3: I have the same problem but after a while the test turns into "ok". @Bosch_SensorTec Is there a way to re-configure the firmware to read "OCSB" instead of "JTAG_DIO"?
... View more
01-26-2024
09:20 AM
Additional remarks: With firmware „BHI360_BMM350“ the self-test of physical sensor 5 returns “ok”. With firmware “BHI360_Aux_BMM150” booting returns error “0x21 - Sensor Init Failed: Unexpected Device ID” and with firmware “BHI360_BMM150” error “0x22 - Sensor Init Failed: No Response from Device”. My conclusion of these three results would be that the BMM350 is detected and/or even works correctly (depending on what exactly is covered by the self-test of sensor 5).
... View more
01-26-2024
08:26 AM
Hello Robin, Thank you for your quick reply. As mentioned the communication ESP32-BHI360 works without problems. Therefore I just attach the schematics for the part BHI360-BMM350. My doubt is if it is a design-problem, a faulty prototype-implementation (unfortunately my second prototype is unavailable for an other reaseon to double-check that), or if it is "just" a problem of my software-implementatin.
... View more
01-24-2024
05:01 PM
1 Like
Hardware BMM350 via I2C directly connected with BHI360: BMM350-SDA-A2 with BHI360-ASDX-2 and 4,7KOhm pull-up-resistor BMM350-SCK-A3 with BHI360-ASCX-3 and 4,7Kohm pull-up-resistor BMM350-INT-A1 with BHI360-OCSB-10 BMM350-ADSEL-B2 to GND. Source: chapter 4.1.2 of BHI360-datasheet and “BHI360 Shuttle board 3.0 flyer” Firmware Firmware from GitHub „BHI360_BMM350C.fw.h“ Actual situation The BHI360 itself works as expected (connected via I2C to an ESP32-S3-WROOM-1): Firmware loads and boots without errors. The self-tests of the physical sensors 1 (Accelerometer), 3 (Gyroscope) and 5 (Magnetometer) return “ok”. The virtual sensors which use the physical sensors 1 and 3 (like 3 (Accel uncalibrated) and 12 (Gyro uncalibrated)) work correctly. But all virtual sensors which also use the physical sensor 5 (like 21 (Magneto uncalibrated) and 43 (Orientation)) do not report anything, even not any error message; the physical sensor 5 (like 1 and 3) shows “Power mode: 7-Active”, but no data, no error message. I also tried “BHI360_Aux_BMM150” which returns after booting the error “0x21 - Sensor Init Failed: Unexpected Device ID”, and “BHI360_BMM150” which returns after booting the error “0x22 - Sensor Init Failed: No Response from Device”. Doubts and questions Hardware: 1. Any remarks to the described hardware-design? 2. Is the connection “BMM350-INT-A1 with BHI360-OCSB-10” correct/necessary? Firmware: 3. Is „BHI360_BMM350C.fw.h“ the correct firmware for this hardware-design? 4. What does the “C” stand for in “BHI360_BMM350C”? 5. What is the difference between “BHI360_Aux_BMM150” and “BHI360_BMM150”? Software (supposing that „BHI360_BMM350C.fw.h“ is the correct firmware): 6. Would the self-test of physical sensor 5 detect a failure in the I2C-connection to BMM350? 7. Are there other possibilities to test the I2C-connection BHI360-BMM350 by software? 8. Is there anything different in the configuration of virtual sensors 3 and 12 (which work and use physical sensors 1 and 3) and virtual sensor 21 (which does not work and use physical sensor 5)? General: 9. Beside the comments in the source-code on GitHub and the BHI360-datasheet, are there other sources of documentation available?
... View more
Latest Tags
No tags yet
Still looking for something?
- Top Results
See all results