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

TMS320F2800157-Q1: MCAN function

Andy Jin
Intellectual 470 points
Part Number: TMS320F2800157-Q1


Tool/software:

Hi Expert,

Occasionally, during the power-up process, MCAN peripheral-level interrupt is enabled, and the peripheral interrupt flag is positioned, and the PIE interrupt is enabled, but the corresponding PIEACK interrupt flag is not set. Code Status:

 bMCAN has gone through the initialization process in boot, and after jumping to the App, the MCANSS_EOI is not initialized and cleared when the App is initialized; If the operation is missing, there is a packet on the bus, whether it may cause the peripheral interrupt not to trigger the peripheral interrupt when the packet is received?

Thanks a lot! 

Andy

  • 0
    TI__Mastermind 38970 points

    Hi Andy,

    Usually, this happens when the device is in the startup and boot process and there are already frames appearing on the CAN bus.  Typically, the CAN transceivers have standby pins such that if the F2800157 is not yet ready, the CAN transceiver will be in standby mode and when boot up sequence is complete, a GPIO from the F2800157 drives the standby pin of the transceiver to active allowing the device to start CAN communications.  Is this something that you can implement?

    Regards,

    Joseph