• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 100 subscribers
  • Views 359 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.

AM62A7: Using the WKUP_UART from Linux

Jonathan Cormier
Genius 4061 points

Part Number: AM62A7

Is it possible to disable the WKUP_UART in the dm_edgeai_mcu1_0_release_strip.out firmware so the A53 can use it from Linux?

There is a guide here on how to disable the WKUP_UART for the AM62x
 
 
Unfortunately, the AM62A uses a special build of the DM firmware to add something for the AI support and so the standard MCU firmware used by the AM62x/P isn't one to one compatible.
 
I downloaded the mcu_plus_sdk_am62ax_11_01_00_16 just in case, but unfortunately there doesn't appear to be any reference to the following filename anywhere in the provided code.
dm_edgeai_mcu1_0_release_strip.out
 
  • 0
    TI__Intellectual 1060 points

    Hello Jonathan,

    Before we proceed, could you confirm whether you are using the VPAC/ISP camera functionality on your AM62A7?

    The reason we ask is that dm_edgeai_mcu1_0_release_strip.out is an AM62Ax-specific firmware that includes VPAC/ISP code alongside the DM task. Depending on your answer, we will route this to the appropriate expert for further assistance.

    Regards,
    Harshith

  • 0 in reply to Harshith Puram
    Prodigy 30 points

    Hi Harshith,

    We are not using any cameras in our current project so we do not need that functionality. 

    Thanks,

    Holden

  • 0 in reply to Holden Wozniak
    TI__Intellectual 1260 points

    Hello,
    Thank you for your query. The concerned expert is Out of Office due to **TI India** Holiday.
    Please expect a delay in response. We appreciate your patience and understanding.

    Best regards,
    TI E2E Support Team
    ---
    *This is an automated notification.*

  • 0
    TI__Intellectual 1060 points

    Hi Jonathan,

    Apologies for the delay here.

     You are correct that dm_edgeai_mcu1_0_release_strip.out source is not available in the MCU+ SDK. However, this fix does not require it — disabling WKUP_UART for DM logging is a board configuration change, not a DM firmware change. The same approach in the AM62x guide you referenced applies directly to AM62Ax, just using the AM62Ax board configuration file instead - https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/latest/exports/docs/api_guide_am62x/DEVELOP_AND_DEBUG_DMR5.html#autotoc_md358

    Additionally, enable wkup_uart0 in your Linux board DTS:

    &wkup_uart0 {
    status = "okay";
};

    Both changes are required — the board config releases WKUP_UART0 ownership from the DM firmware, and the DTS change enables Linux to use it.

    Regards,
    Harshith

  • 0 in reply to Harshith Puram
    Genius 4061 points

    Thanks for the clarification

    Harshith Puram said:
    You are correct that dm_edgeai_mcu1_0_release_strip.out source is not available in the MCU+ SDK. However, this fix does not require it — disabling WKUP_UART for DM logging is a board configuration change, not a DM firmware change.

     These two statements seem contradictory to me.  How do I change the board config and effect the dm firmware, if I don't need to rebuild the dm_edgeai firmware file? 

  • 0
    TI__Intellectual 1060 points

    Hi Jonathan,

    The two statements are not contradictory — board configuration and DM firmware are separate components that live in different boot binaries:

    • Board configuration is packed into tiboot3.bin and is consumed by TIFS at early boot.
    • DM firmware is packed into tispl.bin

    For more information on target images, please refer to this page - Target Images

    DM firmware does not embed the board configuration. When TIFS initializes, it reads and parses the board configuration from tiboot3.bin and passes the relevant settings including UART routing and debug trace destinations to DM via the TI-SCI protocol during DM initialization. DM automatically picks up the new configuration at the next boot. So the correct step is to modify the board configuration and rebuild tiboot3.bin only — no changes to tispl.bin or the DM binary needed.

    Regards,
    Harshith