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.

TCAN4550-Q1: Sending data to the bus, stopping abnormally after several attempts

Part Number: TCAN4550-Q1


Hi team,

One of our customer's issues, I'm forwarding it below, could you please provide some troubleshooting suggestions

The CANFD mode can communicate with other CANs, but it will suddenly stop abnormally, with the nINT light constantly on. Sometimes, the 0x820 register value is printed as 0x100000, and sometimes it is 0x100088;

The value of the 0xC register is 0x8 when there is no exception, sometimes 0x900000c when there is an exception, and sometimes 0xb00000c. May I ask what are the reasons for each

Best Regards,

Amy Luo

  • Hi Amy,

    Thanks for the detailed register status on this issue.This helps us a lot in identifying the problem fast.

    Based on your register description, the device is reporting a SPI error with a Write FIFO overflow status. The write_fifo_overflow flag is typically the result of transmitting more data than was declared in the LENGTH portion of the SPI frame (see figure 8-17 of the datasheet). This could also be caused by a new command coming in on SPI before the previous command could be processed fully. In this case, repeating the previous SPI command should allow the device to properly process all commands. It may be good to introduce some artificial delay between SPI frames to prevent this from happening if this is indeed the root cause.

    In both cases when the nINT pin indicates that the SPIERR flag is set, the flag should be cleared by writing to the interrupt register and the previous SPI command should be repeated to ensure on actions or data are missed.

    Let me know what you are able to find out regarding this information when applied to the current system. 

    Regards, 
    Eric Schott 

  • Hi Eric,

    Thanks for taking the time to respond, really appreciated!

    The customer feedback is that the soft reset part was not configured due to this.