• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 359 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.

28035 LIN can not enter interrupt when receive control command and data request alternately

Ronnie
Intellectual 750 points


DSP 28035 as a slave, when it receives data request periodically, it works well, when it receives control command periodically, it works well.

But, when it receives control command and data request alternately, it can not work well and can not enter interrupt. That's why ?

  • 0
    TI__Guru* 95315 points

    Could you please elaborate on “it can not work well and can not enter interrupt”? Are you saying the communication event itself happens, but the interrupt does not get asserted? Have you confirmed that the communication event indeed happens with the help of oscilloscope or a LIN protocol analyzer?

  • 0 in reply to Hareesh Janakiraman
    Intellectual 750 points
    By debugging, it can not enter interrupt because of NRE(no response error).

    And, when transmit data the first time, LINRDy has the same value with LINTDy, but not trigger receive interrupt.
    Then 28035 receives data, and transmit data the sencond time, but this time, I find RXRDY flag is set and LINRDy has the same value with LINTDy and receive interrupt is triggered.

    Why LINRDy has the same value with LINTDy? is it normal?
    Why the first time do not trigger receive interrupt, but receive interrupt is triggered the second time ?
  • 0 in reply to Ronnie
    TI__Guru* 95315 points

    Could you check if Loopback mode is enabled?

     

    Have you looked into the errata (SPRZ295P) concerning issues in the LIN module? Specifically, the one titled “When LIN Slave Adapts Itself to a Faster Incoming Header, No Response Error (NRE)/Time-out Might not get Flagged Within Expected Time Frame”