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

Original question:

AM2634: LIN driver is not sending a Published frame after Subscribed frame is sent

AM2634: LIN driver is not sending a Published frame after Subscribed frame is sent

Prashanth Arun
Intellectual 255 points
Part Number: AM2634

Dear TI Experts and ,

We have raised a issue with LIN which is present in the below link and it was replicated. We are waiting for the solution:

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1208882/am2634-lin-driver-is-not-sending-a-published-frame-after-subscribed-frame-is-sent

Please provide us the solution for the above problem so that we can use LIN in our project. Currently its a Major critical blocker in our project.

Thanks & Regards,

Prashanth Arun

  • 0
    TI__Mastermind 26145 points

    Hi Prashanth Arun,

    The pre-silicon testing for this issue is undergoing. The bus seems to be normal and but all the responders I have tried it is not behaving as expected. I am not sure if this is commander issue or responders issue. To replicate, we are doing a loopback between two instances, where one will be commander and another will be responder. The commander will first send a publisher packet and then the subscriber packet.

    Prashanth Arun said:
    Currently its a Major critical blocker in our project.

    I understand the same, and hence we are working on it at full force.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    TI__Mastermind 26145 points

    Hi ,

    We have confirmed this is not an issue. To determine, if the packet is supposed to be received or transmitted, that id filter needs to be updated in the filter mask.

    Hence, in case of transmit, you need to call -

    txID = LIN_generateParityID(txID);
    LIN_setTxMask(APP_LIN_BASE_ADDR, txID);

    In case of receive -

    rxID = LIN_generateParityID(rxID);
    LIN_setRxMask(APP_LIN_BASE_ADDR, rxID);

    We tested the same and we don't see the packet drop anymore.

    Hope it helps.

    Best Regards,
    Aakash