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.

AM62P-Q1: How to use AM62P internal MCU channel R5F restart A53 linux OS?

Part Number: AM62P-Q1
Other Parts Discussed in Thread: AM62P

Tool/software:

Hi Experts:

We are working with customer develop AM62P Automotive application. In order to increase AM62P system safety, we are working with customer try use MCU channel R5F restart A53 running linux system. But follow our user guide customer tried MCU-only mode. Looks like AM62P MCU-only mode A53 linux just enter suspend mode, not shutdown A53 linux OS. (https://software-dl.ti.com/processor-sdk-linux/esd/AM62PX/10_00_07_04/exports/docs/linux/Foundational_Components/Power_Management/pm_wakeup_sources.html)

Our application is MCU R5F monitor A53 linux stability, if A53 Linux hang. customer want to use MCU R5F restart A53 linux. MCU R5F core still running FreeRTOS communicate with other device through CAN interface. System request that AM62P can not reboot whole SOC, keep MCU R5F working and just reboot A53.

Could you please tell us which demo can meet this request?

Best Regards!

Han Tao

  • Hello Han Tao,

    The documentation below is helpful for your requirement.


    Use Case
    The objective is to reset the Linux core (MAIN domain) from the MCU domain if a crash or panic occurs on the A53 core.


    Methods for Identifying Linux Core Crashes :

    IPC Mechanism:
    •The Linux core sends periodic "heartbeat" messages to the M4F core.
    •If the M4F core fails to receive these messages within a specified time frame, it can initiate a reset of the Linux core.


    Advantages:
    •Simplifies system architecture by leveraging IPC for crash detection.

    Disadvantages:
    •IPC uses DDR memory, necessitating M4F core configuration in isolated mode with monitoring capabilities.
    •This setup allows MCU domain access to MAIN domain peripherals, preventing full isolation of the M4F core.

    Watchdog and Error Handling Module:
    •Enable the watchdog interrupt on the A53 core.
    •Route the watchdog interrupt to the MAIN ESM (Error Signaling Module) and propagate all MAIN ESM errors to the MCU ESM.
    •MAIN ESM initialization is managed by the DM R5F core, while MCU ESM initialization is handled by the MCU core.


    Advantages:
    •Allows the M4F core to be configured in fully isolated mode.


    Disadvantages:
    •Adds complexity due to ESM initialization procedures.

    Demo Setup : 

    1. Configure the SOC with isolated M4F core settings.

    (Integrate the Reset Isolation example in the customer Application Path : \ti\mcu_plus_sdk_am62px_10_00_00_14\examples\drivers\safety\reset_isolation)

    2. Implement IPC for heartbeat messaging between A53 core and MCU Core and monitor for Linux core crashes from MCU core.

    3.  Trigger a Linux crash scenario through a software switch on the EVM or any other method.

    4. Once the crash is detected by the MCU core, do the MAIN domain Reset with the help of MCU MMR registers .

    5. After trigger the WarmReset, the Linux core (MAIN domain) will start freshly and MCU core will still be isolated and running continuously .

    6. Validate the above setup in both SBL_OSPI and SD boot scenarios.

    Please let me know still if customer wants any help on the demo setup .

    Regards,

    Anil.



  • Hi Anil:

    Thanks share it with us. We are working with customer try it and i will close this thread.

    Best Regards!

    Han Tao