• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 198 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSPM0C1104: I2C issue while porting from MSPM0L1105 to MSPM0C1104

SHRAWANI PAWAR
Prodigy 120 points

Part Number: MSPM0C1104
Other Parts Discussed in Thread: MSPM0L1105, , MCF8315A, SYSCONFIG

Tool/software:

Dear Team ,

Customer has ported the LVCF Code from the MSPM0L1105 to the MSPM0C1104 n currently facing an issue while doing the I2C communication protocol between the controller n Motor Driver MCF8315A.

The problem occurs when customer tries to read the data, execution is stuck at DL_I2C_flushControllerTXFIFO(I2C_INST); cmd  whereas the same code was working fine with MSMP0L1105.

It was observed that when customer commented out the cmd ,the code is executed and customer was able to read the data but at the time of writing again code stops executing further.

I'm attaching the snapshot of timing diagram when customer comments out the cmd also an image of FIFO reg when customer tries to monitor the FIFO reg .

Please help me understand what's causing this issue and how can it be solved.    

I2C_Issue.docx

Best Regards,

Shrawani

  • 0
    TI__Mastermind 20772 points

    Hi Shrawani,
    Can you share the schematics of your customer? We want to make sure it is not a hardware issue from our side (please send it to the list we have for msp schematic reviews). Also, can the customer share the project with us? I would like to inspect it and see if there's anything that could be wrong with it. If not, can the customer send a screenshot like the one attached to this E2E in the project, and the .sysconfig file used in the project?

    Best Regards,

    Diego Abad

  • 0 in reply to Diego Abad Sajamin
    TI__Prodigy 120 points

    Hi Diego Abad Sajamin,

    Thank you for your response. Issue was arising because the buffer for MSPM0-C series is only 4 bytes, while the flush API from the driverlib wrongly expects 8 bytes (which was a case for MSPM0-L series), we have suggested a quick way to fix it. The issue has been resolved .