This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/TM4C123GH6PM: MPU-9150

Part Number: TM4C123GH6PM

Tool/software: Code Composer Studio

 Hi,

i am working with sensor Boost that contain MPU-9150 sensor using TivaC123 sensor algorithm from Ti and when debugging the code on board changing in the system frequency or the delay between write configuration and read using I2C from the sensor, i found that the readings changes but also give me wrong readings when comparing it with the mobile application readings for gyroscope, accelerator, and magnetometer.

i need to know the right value of function delay that i need to set to get the accurate readings while using the maximum frequency from the internal oscillator of the master MCU.

  • Hello,

    Is there a reason you cannot use the SensorLib code for MPU-9150 that we provide?

    I saw a few mentions of delays in the solution we provide, but they don't seem to align with what you have set up here. That said, we aren't really knowledgeable with the MPU-9150 and already provide working code with SensorLib, so I am not in position to deep dive this issue when a solution readily exists and is provided.

    If you can't just outright use what we provide, I would recommend you study the mpu9150.c file from SensorLib to see if you can figure out what is going on. 

  • Hi,

    I checked Ti again and apologize about this conflict, what happened is that i put a screen from another code.

     I see that in Ti code it wasn't depend on time delay it depend on setting a flag that show me that the transaction is done and there is no errors and i have no problem to use Ti code, but if i ask you to help me knowing that how can i use the correct time delay in the mentioned portion of code above if you can.

    best regards. 

  • Hello,

    As mentioned, we do not have expertise with the MPU-9150 to know the proper delays - the writers for SensorLib aren't with the team anymore, but it is a proven solution that works. If you have questions specific to the TM4C itself, that is something we can help with.