Closed hukuzatuna closed 3 years ago
Related? https://forums.adafruit.com/viewtopic.php?f=19&t=174424
Dealing with clock stretching is always the first suspicion. But the BNO08x seems to be ever more "fun".
Related? https://forums.adafruit.com/viewtopic.php?f=19&t=174424
Dealing with clock stretching is always the first suspicion. But the BNO08x seems to be ever more "fun".
Yes, clearly related! I had tried the 10kHz baudrate trick, but it does not work. As per the forum suggestion I added
dtparam=i2c_arm_baudrate=400000
to /boot/config.txt, rebooted, and the sensor is working as expected. Thank you @caternuson ! (Closing issue)
@caternuson ok want to add to guide?
I'll update it for now, since this seems to work. And the 10kHz slowdown does not. But seems really weird to me that speeding up the I2C clock is fixing a clock stretching issue. I'm concerned there's more going on with this sensor maybe.
maybe at too-low rates it cant read the reports fast enough, and the sensors gets 'backed up'?
I have a freshly-configured Raspberry Pi 4 (8GB) that generates an exception when exercising the BNO085 sensor. When I first tried it I was using the Beta 64-bit OS, so I thought it was a storage boundary problem. Reverted to the standard 32-bit OS and the problem persists. Configured a Raspberry Pi Pico and attached the same device, and it ran flawlessly for days (ruling out a hardware problem with the sensor?)
Problem:
Code that generated the problem (taken straight from the learning guide):
Expected behavior: It should print the IMU data.