3 ms·
You're being way too kind to these chips. Look at the datasheet for the BMP280 barometer chip, the AK8963 compass, and the MPU6500 accelerometer (close enough)
by joezydeco 13y ago
You're being way too kind to these chips.
Look at the datasheet for the BMP280 barometer chip, the AK8963 compass, and the MPU6500 accelerometer (close enough):
http://datasheet.octopart.com/BMP280-Bosch-datasheet-13691204.pdf http://datasheet.octopart.com/BMP280-Bosch-datasheet-1369120...
http://www.akm.com/akm/en/file/datasheet/AK8963.pdf http://www.akm.com/akm/en/file/datasheet/AK8963.pdf
http://dlnmh9ip6v2uc.cloudfront.net/datasheets/Components/General%20IC/PS-MPU-6000A.pdf http://dlnmh9ip6v2uc.cloudfront.net/datasheets/Components/Ge...
The compass (AK8963) has a reset line, the other two have no reset line at all. Your best bet is to drop VCC, but what are the chances the hardware guy just tied them to the power bus and left it at that?
- kosma 13y ago> The compass (AK8963) has a reset line, the other two have no reset line at all. Your best bet is to drop VCC, but what are the chances the hardware guy just tied them to the power bus and left it at that? That is, if you also have even more circuitry to disable the bus pullups; otherwise they will continue to power the device via clamping diodes, potentially calling further confusion. The hardware guys don't implement I2C slave power control for a reason: it gets bloody expensive real fast - both in terms of BOM cost and PCB estate. Having said that, the lack of a RESET line on many I2C slaves is just ridiculous. I have a sticker on my monitor that says "fix the hanging MMA8451Q bug"; it's been there for at least three months. The very thought of debugging I2C transactions makes me stop even trying.
- joezydeco 13y agoGood point about the pull-ups. Forgot about that.