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: MCU2-0 enter ABORT status in startup phase

Part Number: TDA4VM

Tool/software:

Hi Ti's supporters,

We found an issue in MCU 2-0 startup phase, it is a Low probability to occur MCU2-0 enter ABORT status in startup phase.

please see below picture, it will call XDC functions and enter abort status.

please analyze the reason of ABORT, thanks!

  • Hi,

    please see below picture, it will call XDC functions and enter abort status

    Could you please explain the process that you are doing to address this abort issue?

    Regards,

    Karthik 

  • Hi,

    We have a CAN wakeup/sleep stress test case, this test case will startup and stop all the COREs(for our ECU, it means Power On/Off). When we test this case, we found sometimes MCU 2-0 can startup successfully, sometimes it is stuck.

    When MCU 2-0 is stuck, we debug and found it is abort.

    So we want to know what reason will cause MCU 2-0 to abort during MCU 2-0 core software startup phase.

    The SDK version is 7.3.

    Thanks.

  • Hello,

    could you be more specific ? Are you using MCAL CAN driver ? as far as i know we are not using CAN wakeup pin at all.

    which OS are we talking about ? Can you share me more details on boot flow and boot media ?

    Regards

    Tarun Mukesh

  • hello,

           MCU2_0 does not use can driver, and we use can to wake up TDA4, the CAN driver is installed  within mcu1_0.

          after mcu1_0 brings up, it boots the core mcu2_0. we run TI  RTOS on mcu2_0.

          The TDA4 boots from opsi flash.

  • Hello,

    I am still trying to understand here, 

    All cores are Powered off , PMIC is in sleep state then you are driving CAN Wake up pin to wake up PMIC.so the BOOT sequence is started from MCU1_0 . MCU1_0 is loaded successfully whereas MCU2_0 is getting abort sometimes. Is this what you are conveying ?

    Regards

    Tarun Mukesh

  • Hello,

       yes, it is. Would  you check the image above?  We find that a task stack had been checked error. Do you know how to check what happened when the error occurred?