• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 100 subscribers
  • Views 85 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TDA4VM: It takes too long for TDA4 to send the first frame of message from power-on

Katherine Wang
Intellectual 2210 points
Part Number: TDA4VM

Hi Team,

Through tests, we’ve found that it takes TDA4 3.38s to send the first frame of message from power-on. As shown in Figure 1, the software start-up time is 2.6s, and the hardware start-up time is 780ms. The oscilloscope measures the TX end of the CAN transceiver of the MCU end. The SD start-up mode is used.

Our customer cannot accept this time, and the customer requires this time be 500ms. Is it because of the startup mode? How can I start the MAU’s app from EMMC?

The app used is the can_profile program in the mcu demo. The log is shown in Figure 4.

Regards,

Katherine

  • 0
    TI__Guru* 77054 points

    Hi

    Katherine Wang said:
    Through tests, we’ve found that it takes TDA4 3.38s to send the first frame of message from power-on. As shown in Figure 1, the software start-up time is 2.6s, and the hardware start-up time is 780ms. The oscilloscope measures the TX end of the CAN transceiver of the MCU end. The SD start-up mode is used.

    Can you explain your bootflow here? I see you are using SD card which will definitely consume a lot of time in initialization as compared to OSPI which is what TI recommends for early CAN response.

    Also, I assume this is running on the MCU R5F, can you confirm?

    Regards

    Karan