We have just designed a board with BNO055 on it. As per the datasheet (Rev 1.7, Nov 2020), we left pins 15,16 "DNC" - unconnected.
On powering up the board, the BNO055 does not respond to I2C commands (no ACK to slave address).
We had previously prototyped the system using 3rd party BNO055 eval boards, and it worked fine.
The only difference we can spot is that pins 15 and 16 are connected to GNDIO on every eval board we can find.
We see the datsheet also used to have these pins connected to GNDIO, but it got updated in Rev 1.6, Feb 2020. There was a firmware update also just before this.
The ICs on our board may be several years old, so might it be possible that the older firmware in these does actually need pins 15 and 16 connected to GNDIO?
Solved! Go to Solution.
This is official schematic of BNO055 shuttle board. You could pin 15, pin 16 were not be connected, the same with data sheet description.
For "On powering up the board, the BNO055 does not respond to I2C commands (no ACK to slave address)."
1.Could you give out your schematic to check?
2.You could read chip ID in your promgrame first, and capture I2C waveform to check actual communication.
The shuttle board schematic only shows pins 15,16 wired to the connector, so their use is not explained.
Here is the relevant part of our schematic and a scope grab of the I2C trying to talk to the device (noisy because our software engineers don't fully understand how ground clips should work!).
We have a few other I2C devic es on the board, and they all work fine.