Our MotionFit Wireless SDK is built on the MSP 430 platform, and provides an embedded motionprocessing library that can be used for development. You should be able to start from that package, and develop your application around our latest eMPL.
Our MotionFit Wireless SDK is built on the MSP 430 platform, and provides an embedded motionprocessing library that can be used for development. You should be able to start from that package, and develop your application around our latest eMPL.
Thanks for the reply.
Everything here is specific to the MSP4305438A/F5528/F5529 and I need to implement this with other packages. Can you expose some of the source code in the lib or at least allow us to change some of the pins that are device specific (SDA/SCL)?
The MotionFit SDK is not designed to be ported, as it was exclusively built around the MSP430 and the MPU-9150.
Our Atmel package for the MPU-6050 can be ported. We are also in the process of developing new solutions for the Developer Community targeting ease of portability and 9-axis capabilities.
Re: Re: MotionApps MPU6050EVB support for MSP430?
Our MotionFit Wireless SDK is built on the MSP 430 platform, and provides an embedded motionprocessing library that can be used for development. You should be able to start from that package, and develop your application around our latest eMPL.
Re: Re: MotionApps MPU6050EVB support for MSP430?
@sectionsbest wrote:
Thanks for the reply.
Everything here is specific to the MSP4305438A/F5528/F5529 and I need to implement this with other packages. Can you expose some of the source code in the lib or at least allow us to change some of the pins that are device specific (SDA/SCL)?
Re: Re: MotionApps MPU6050EVB support for MSP430?
The MotionFit SDK is not designed to be ported, as it was exclusively built around the MSP430 and the MPU-9150.
Our Atmel package for the MPU-6050 can be ported. We are also in the process of developing new solutions for the Developer Community targeting ease of portability and 9-axis capabilities.