Reading BNO055

[livius]

@fehlfarbe
if you really do not need to have recent firmware on Wipy2
then the most stable for me is 1.7.2.b1 - try downgrade or upgrade

[robert-hh]

@fehlfarbe What does i2c.scan() return, after you have initialized the interface?

[fehlfarbe]

@livius I downgraded to WiPy-1.7.9.b3 - no change.

[fehlfarbe]

@robert-hh sometimes it returns the adress of the device 0x28, sometimes it returns nothing.

[livius]

@fehlfarbe

I downgraded to WiPy-1.7.9.b3 - no change.

1.7.2.b1 ;-)

but how looks like your wiring?
Do you have some pullups? Maybe internal puulups on the board BNO055?

[fehlfarbe]

@livius oldest firmware available at https://forum.pycom.io/topic/517/downgrading-firmware-advanced-users/20 is 1.7.9.b3

Wiring:

The breakout board has 10k pullups on SDA/SCL. I tried a second board but same problem :)

[livius]

@fehlfarbe said in Reading BNO055:

oldest firmware available

just change numbers in the link
https://software.pycom.io/downloads/WiPy-1.7.2.b1.tar.gz

I see on the BN0055 there are 10k pullup resistors - should be ok because there are shifter on BS138.

[incognico]

Maybe try adding some lower value pullup resistors.

From the FAQ page of your device BNO055 FAQ #4

"Depending on your system setup, you might need to adjust the pullups on the SCL and SDA lines to be a bit stronger. The BNO055 has very tight timing requirements on the I2C bus, requiring short setup and rise times on the signals. By default the breakout board has 10K pullups, which might be too weak on some setups."

[fehlfarbe]

@incognico I tried different pullups from 1.2k to 10k but there is no change. The device works flawless on my OrangePi Zero (ARM device) with 3.3V logic level.

[brotherdust]

@incognico said in Reading BNO055:

Maybe try adding some lower value pullup resistors.

From the FAQ page of your device BNO055 FAQ #4

"Depending on your system setup, you might need to adjust the pullups on the SCL and SDA lines to be a bit stronger. The BNO055 has very tight timing requirements on the I2C bus, requiring short setup and rise times on the signals. By default the breakout board has 10K pullups, which might be too weak on some setups."

I had a similar problem. I'm not sure if it's been fixed or not, because I haven't tested it lately. Anyway, it had to do with I2C Clock Stretching. For me the solution was to set the I2C baud rate as low as it would go and work my way up until i found the fastest value that worked. Maybe give that a try, if you haven't already. =)