• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 91 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.

MSPM0G3519: MCAN TX FIFO - RX FIFO

John De Clercq
Prodigy 141 points

Part Number: MSPM0G3519
Other Parts Discussed in Thread: SYSCONFIG

CAN bus issue.xlsx 

Dear,

We have the following issue using MCAN0 on MSPM0G3519. 

CAN_CLK = 80MHZ

Please see XLS find attached.

The first XLS tab contains a logging on oscilloscope (but have same using PCAN).

We send 588 frames into TX FIFO from node A to node B. 

You can see at the in the read lines that 2 messages have wrong identifier and data.

This only happens in the case the that the node B is sending also frames (0x700) on the bus.

If we don't send frames (0x700) from node B to node A, we allways receive the 588 packages in node B (coming from node A).

The other tabs in the XLS files contain the configuration code of the MCAN0.

We are sure that we don't send the frames in the red lines by mistake.

 

Looking for help.

John

 

 

 

 

 

 

 

 

 

 

 

 

  • 0
    TI__Mastermind 31085 points

    Hi John,

    I assume you are setting the CANFD moudle with SysConfig tool, can you share this files for my reference.

    I see when the CAN fram 0x4c8 shows up, the node A missed one data frame

    For the issues, I right now have no idea, while I think you can monitor several things inside CANFD process task:

    1. Enable TC interrupt to counting the transmission

    2. Check IR status register to see if any error is asserted

    3. Monitor the ECR.TEC in TC interrupt to see if there any abnormal behavior during TX and RX

    4. I see you mention it is logged on oscilloscope, can you check the waveform of the error packet and compared to the normal one?

    B.R.

    Sal