This question applies to MotionApps Lite as well as MotionApps 2.0.
I notice that there are a number of functions, such as:
msp430_configure_sysclock()
msp430_clock_enable()and similar, that are called in main.c, have function prototypes in header files like msp430_sysclock.h, but do not appear to have function declarations anywhere in the project.
I initially thought that the declarations could contained in the Lite version's precompiled library, but the same applies to MotionApps 2.0.
Where are the function declarations for functions like those above? (or are they just placeholder functions)
Re: Re: Code organization question
The msp430_sysclock.c file should be at the root directory of the MotionApps UC3 project.
Re: Re: Code organization question
I think you referenced msp430_sysclock.h, which is indeed in the root directory, but only contains the function prototypes. I'm much more interested in the MSP430 clock configuration--I'll be re-configuring or replacing it. I did find some much more useful files in embedded_motionapps-2012-05-02-Rel-V2_0_2srcasfcommonservicesclock
I'm really just trying to isolate the clock management functions in MotionApps Lite.
Re: Re: Code organization question
These functions are part of the precompiled libraries, but the source files were removed during the packaging of the MotionApps lite library for the MotionFit SDK
Re: Re: Code organization question
I'm trying to figure out how to use this device in a project, and I'm a bit frustrated working around this. I used the datasheets to make up a batch of boards that have the MPU 6000 connected via SPI to an MSP430F5528. From what I read, I should be able to use this to read the motion fusion results from the DMP.
The issues I've run into are:
(1) no way to change the MSP430 clock settings to run the device at the require pace. My workaround is trying to overload the Invensense clock functions to change them *after* your functions run.
(2) I'm still trying, but I think the i2c functions are also "removed during packaging." I think this means there is no way to replace the i2c functions with SPI functions and thus conduct motionfusion over SPI.
Does this mean that I need to scrap the code and rewrite my own motionfusion algorithm? I would hate to do that as this is the whole point of using an Invensense product. If so, surely there is someone who ran into the same problems and is ahead of me on writing a motionfusion code that will allow these tweaks?