The current version of Embedded MotionApps now available in the Developers Corner does support rev D of the MPU-6050
Hi,
I'm using MPU-6000 revision D and I have some questions:
1. Does version 2.00 of Embedded MotionApps support MPU-6000 revision D?
2. If the answer to the above question is Yes, then can I use the SPI interface (instead of the I2C interface) to talk with the DMP? In other words, I intend to modify the source code of MotionApps to use SPI. Is there any problem with this approach?
3. If the answer to question 2 is No, then how can I use more than 2 MPUs in my system? (I have asked this question because the maximum number of MPUs we can connect to the same I2C bus is 2)
MPU-6000 Rev D is supported in I2C mode only, we don’t currently include an SPI driver.
The limitation of 2 MPU devices on a single I2C channel comes from the two available I2C addresses for the chip.
Multiple or multiplexed I2C ports could be utilized to expand the number of MPU’s. Coupling the sensors with a small microcontroller (such as our MotionFit SDK’s MSP430) would allow you to use higher level communication (CAN, UART, etc.) to read sensor data from multiple devices.
CONFIG_MPU_SENSORS_MPU6050B1 should be used. The naming reflects a register map change in an early verison of the silicon, the file name is not updated to the latest chip revisions but will work for Rev D.
Re: Re: Where is MotionApps v2.01?
We are targeting the next release of Embedded MotionApps sometime in Q2
Re: Re: Where is MotionApps v2.01?
The current version of Embedded MotionApps now available in the Developers Corner does support rev D of the MPU-6050
Re: Re: Where is MotionApps v2.01?
@sectionsbest wrote:
Hi,
I'm using MPU-6000 revision D and I have some questions:
1. Does version 2.00 of Embedded MotionApps support MPU-6000 revision D?
2. If the answer to the above question is Yes, then can I use the SPI interface (instead of the I2C interface) to talk with the DMP? In other words, I intend to modify the source code of MotionApps to use SPI. Is there any problem with this approach?
3. If the answer to question 2 is No, then how can I use more than 2 MPUs in my system? (I have asked this question because the maximum number of MPUs we can connect to the same I2C bus is 2)
Thanks in advance.
Re: Re: Where is MotionApps v2.01?
MPU-6000 Rev D is supported in I2C mode only, we don’t currently include an SPI driver.
The limitation of 2 MPU devices on a single I2C channel comes from the two available I2C addresses for the chip.
Multiple or multiplexed I2C ports could be utilized to expand the number of MPU’s. Coupling the sensors with a small microcontroller (such as our MotionFit SDK’s MSP430) would allow you to use higher level communication (CAN, UART, etc.) to read sensor data from multiple devices.
Re: Re: Where is MotionApps v2.01?
The latest I was able to download was motionapps-2011-07-25-Rel-V2_0_0.
I can not find any reference to Rev D. for registers or anything.
Should there be CONFIG_MPU_SENSORS_MPU6050D ?
Re: Re: Where is MotionApps v2.01?
CONFIG_MPU_SENSORS_MPU6050B1 should be used. The naming reflects a register map change in an early verison of the silicon, the file name is not updated to the latest chip revisions but will work for Rev D.