Bosch Shared
- Top Results
See all results
- About bbooher
- About bbooher
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
About bbooher
since
04-24-2024
07-18-2024
bbooher
Member
5
Posts
0
Likes
1
Solution
05-31-2024
06:00 PM
We did get the correct Chip ID. And most of the source code for the wrapper at this point is moot, since we're only in the init function. We got the custom hardware in, and things are working as expected - I'm going to chalk it up as an error hacking the devkit to old hardware. However, it still would be helpful to have more documentation about the Sign Error flag in the status register and what that means.
... View more
05-16-2024
07:15 AM
We're updating a custom board that used the BMM150 to use the BMM350. Ahead of hardware availability, we've hacked the BMM350 shuttle board to the custom host board. We've connected the eval kit to available test points and fortunately used a dedicated I2C bus and MCU peripheral. The host is the nrf5340. The original implementation uses a recent version of Zephyr packaged by Nordic. We've used the latest BMM350 API from GitHub and wrote a wrapper to leverage the BMM I2C and sensor interfaces - similar to what was done for the BMM150. In the bmm350_init() function, we get the above "Sign Error" as a result of the "otp_dump_after_boot()" function call.
... View more
05-15-2024
05:31 AM
I'm integrating the BMM350 API into a project with a custom board and host MCU. The result of otp_dump_after_boot(dev) results in -12(BMM350_E_OTP_SIGN). Looking at the documentation, there's no elaboration on what the "Sign error" is or what causes it. Any supporting info would be helpful.
... View more
04-26-2024
06:45 PM
Thanks for the quick response. That link appears to only be IMU (not magnetometer) products. Do you mean another product line, instead? Or do those products have an option to pair with a magnetometer like the BMM350?
... View more
04-25-2024
12:01 AM
I'm developing an application that uses the BMM350. The product is a custom board, using the nRF5340 SOC running Zephyr RTOS. We've developed an out-of-tree driver to support the BMM350 (wrapping the BMM350API) and verified we can read data - so all good there. I'm looking for calibration documentation or guidance during run-time, as it's not apparent from the documentation I've seen. A few questions: - can the compensation values be overwritten? If so, is that the recommended method for run-time calibration? - should instead, the SOC (or off-board application, since I have BLE connectivity) be responsible for the calibration algorithm and merely apply an offset and bias at collection time? If so, is there recommended guidance for this approach?
... View more
Latest Tags
No tags yet
Still looking for something?
- Top Results
See all results