Just to confirm, I sent your the MPU9150EVB raw data with plots and plotting script. They are all in a .zip file. (There were a few delayed attempts because of difficulty inserting graphics in-line and intercept by the Forum editor). The raw data comprises the time in milliseconds, gyro, accel,compass and temperature (Temp). Temperature is available on-chip but not essential for this investigation. The conversion from raw to engineering units can all be found in the Octave/Matlab script readMPU9150EVB.m.
All of the reference quiescent data from from my EVB and SDK are understandable and steady and do not lead to unstable displays. I would like to be able to say the same for the Tiva implementation. So if you could provide a similar file of "sensor" data vs time for 10 minutes from Tiva, e.g. lets start with pfData, that would be helpful. If you can log time with the data that would also be helpful and I guess you may as well log all the pfData including Eulers and Quaternions. Log float data for now. If we see raw to float issues we can go back to pull out the raw sensor data as we have in the EVB .csv file.
I am sorry I may have caused some confusion with an earlier statement about pfData not being the same as the elements pfAccel, etc. I gather they are the effectively references to the same data.. I ddidn't understand the C syntax.
The simple goal is to see a steady stream of sensor data at some point in the Tiva stream, similar to the EVB or SDK.
