• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 295 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.

TCAN4550-Q1: Does it support error detection for MRAM overwriting?

ILWOO NAM
Prodigy 60 points
Part Number: TCAN4550-Q1
Other Parts Discussed in Thread: TCAN4550

Hi,

I'm using TCAN4550-Q1 for CAN FD feature.

When I set an invalid MRAM configuration, RX FIFO 0 was overlapped with TX Buffers and TX data was corrupted by RX data.

Is there any feature to detect error for MRAM corruption like as overwriting?

Best regards

  • 0
    TI__Guru 74252 points

    Ilwoo,

    Have you tried using the watermark feature for the different RX FIFOs? The watermark is a value configured by the user so that once the FIFO reaches a certain amount of messages, an interrupt will trigger, allowing the user to stop filling the FIFO with messages. There is also an RX FIFO full interrupt that can be enabled. On the TCAN4550, both of these interrupts can be assigned to trigger an indication on GPIO1 or GPO2. 

    An example of how to setup the interrupts can be found in this post.

    Please let me know if this helps or if you have more questions/issues.

    Regards,

  • 0 in reply to Eric Hackett
    TI__Guru 62920 points

    Ilwoo,

    I'll also add that the device will not check for overlaps in MRAM allocations, and so you should be careful in configuring the device to avoid this.  There is a design example showing how to do this in Section 4.2.2 of our Software User's Guide:

    http://www.ti.com/lit/ug/sllu270/sllu270.pdf

    If you have any questions about whether a configuration is valid, we would be happy to help you check the register values.  If you can tell us how SIDFC, XIDFC, RXF0C, RXF1C, RXBC, RXESC, TXEFC, TXBC, and TXESC are configured we will confirm whether or not there are potential memory overlaps.

    Best regards,
    Max