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: Why does tiboot3.bin in uboot can not print log in wakeup uart?

Part Number: AM62A7

I has configured the dts as follow,But it can not printf log in wakeup uart.Only it can printf until uboot.img.Why?????

aliases {
remoteproc0 = &sysctrler;
remoteproc1 = &a53_0;
serial0 = &wkup_uart0;
serial3 = &main_uart1;
};

chosen {
stdout-path = "serial0:115200n8";
tick-timer = &timer1;
};

&mcu_pmx0 {
status = "okay";
u-boot,dm-spl;

wkup_uart0_pins_default: wkup-uart0-pins-default {
pinctrl-single,pins = <
AM62X_MCU_IOPAD(0x02c, PIN_INPUT, 0) /* (C6) WKUP_UART0_CTSn */
AM62X_MCU_IOPAD(0x030, PIN_OUTPUT, 0) /* (A4) WKUP_UART0_RTSn */
AM62X_MCU_IOPAD(0x024, PIN_INPUT, 0) /* (B4) WKUP_UART0_RXD */
AM62X_MCU_IOPAD(0x028, PIN_OUTPUT, 0) /* (C5) WKUP_UART0_TXD */
>;
u-boot,dm-spl;
};

  • Hi,

    WKUP_UART0 is used by DM firmware, what are you trying to accomplish?

    ~ Judith

  • OK,Thank you!

    I have another two questions:

    1.Does DM firmware exist in tiboot3.bin,and it is loaded by SOC ROM,RBL?

    2.If I want to use wkupuart to printf log in tiboot3.bin,how do I configure it?

  • Hi,

    1. DM FW is packaged in tispl.bin:

    FIT description: Configuration to load ATF and SPL
    Created:         Tue Jul 25 13:43:44 2023
     Image 0 (atf)
      Description:  ARM Trusted Firmware
      Created:      Tue Jul 25 13:43:44 2023
      Type:         Firmware
      Compression:  uncompressed
      Data Size:    44056 Bytes = 43.02 KiB = 0.04 MiB
      Architecture: AArch64
      OS:           ARM Trusted Firmware
      Load Address: 0x9e780000
     Image 1 (tee)
      Description:  OPTEE
      Created:      Tue Jul 25 13:43:44 2023
      Type:         Trusted Execution Environment Image
      Compression:  uncompressed
      Data Size:    399408 Bytes = 390.05 KiB = 0.38 MiB
     Image 2 (dm)
      Description:  DM binary
      Created:      Tue Jul 25 13:43:44 2023
      Type:         Firmware
      Compression:  uncompressed
      Data Size:    152520 Bytes = 148.95 KiB = 0.15 MiB
      Architecture: Unknown Architecture
      OS:           Unknown OS
      Load Address: 0x89000000
     Image 3 (spl)
      Description:  SPL (64-bit)
      Created:      Tue Jul 25 13:43:44 2023
      Type:         Standalone Program
      Compression:  uncompressed
      Data Size:    318352 Bytes = 310.89 KiB = 0.30 MiB
      Architecture: AArch64
      Load Address: 0x80080000
      Entry Point:  0x80080000
     Image 4 (k3-am625-sk.dtb)
      Description:  k3-am625-sk
      Created:      Tue Jul 25 13:43:44 2023
      Type:         Flat Device Tree
      Compression:  uncompressed
      Data Size:    20785 Bytes = 20.30 KiB = 0.02 MiB
      Architecture: ARM
     Default Configuration: 'k3-am625-sk.dtb'
     Configuration 0 (k3-am625-sk.dtb)
      Description:  k3-am625-sk
      Kernel:       unavailable
      Firmware:     atf
      FDT:          k3-am625-sk.dtb
      Loadables:    tee
                    dm
                    spl
    


    It is loaded by u-boot as you can see here: https://software-dl.ti.com/processor-sdk-linux-rt/esd/AM62X/08_06_00_42/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html#boot-flow

    2. Why do you want to use wkupuart0 to print u-boot logs? What is the usecase? It is a complicated process to switch UART for U-boot, so please explain to better help you.

    ~ Judith

  • My application is that DM-R5 monitor MCU-R5 and A53.And DM-R5 will printf log in wakeup uart.And MCU-UART ,SOC-UART are used for MCU and SOC.Because considerring POWERDomain.

  • Hi kingphy,

    Ok, thank you for this information. I am discussing your use-case internally and will get back to you.

    ~ Judiht

  • Hello Kingphy,

    I am not clear on what you want here. Which core on the AM62A do you want to write outputs to the wakeup UART? (i.e., Linux A53 cores, the DM-R5 core, a different core?)

    Also, are you looking for that core to be writing output to the wakeup UART at specific points in time during bootup? Or just during Linux runtime?

    Regards,

    Nick

  • I  want to write output to wakeup uart when boot tiboot3.bin and dm_firmware

  • Hi Kingphy,

    It is not clear what you want.

    My application is that DM-R5 monitor MCU-R5 and A53.And DM-R5 will printf log in wakeup uart.And MCU-UART ,SOC-UART are used for MCU and SOC.Because considerring POWERDomain.

    --> Here it seems like you want DM R5 to monitor and print to wakup_uart0, but it is already sending log to wakup_uart0.

    If I want to use wkupuart to printf log in tiboot3.bin,how do I configure it?

    --> Here it seems like you want to send u-boot log to wakup_uart0.

    Please clarify what is your trying to do, thanks.

    ~ Judith