Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

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.

[FAQ] AM625: How to enable DM firmware logs & TIFS firmware logs in Processor SDK Linux v8.4

Part Number: AM625

Hello,

I am using the AM62 SK eva kit with PROCESSOR-SDK-LINUX-AM62 08.04.01.03

As I understand MAIN_UART1 and WKUP_UART0 is used by the DM and TIFS firmware.

This is the configuration

MAIN_UART0: Used for Linux and U-Boot on A53
MAIN_UART1: Used for TIFS firmware
WKUP_UART0: Used for DM firmware
MCU_UART0: Used for MCU+ SDK demos and examples on M4

Should I expect any print outs on MAIN_UART1 and WKUP_UART0 from DM and TIFS firmware when I start the AM62 SK board?

Can I switch TX & RX pins for the DM or/and TIFS firmware easily with configuration?  (from E19 & A20 to example B17 & A17 for MAIN_UART1)

Is CTS and RTS used by DM and TIFS firmware for their UART port?

Best regards

Magnus

  • Hi Magnus,

    Should I expect any print outs on MAIN_UART1 and WKUP_UART0 from DM and TIFS firmware when I start the AM62 SK board?

    On my AM62x SK EVM with SDK v8.3, I see log messages on the WKUP UART0 from DM, but no prints on MAIN_UART1 from TIFS.

    Can I switch TX & RX pins for the DM or/and TIFS firmware easily with configuration?  (from E19 & A20 to example B17 & A17 for MAIN_UART1)

    Yes, the UART pinmux is defined in the U-Boot device tree file.

    Is CTS and RTS used by DM and TIFS firmware for their UART port?

    As Linux doesn't use hardware flow control on MAIN_UART0, I don't think DM and TIFS use the CTS and RTS either.

  • Hello again.

    I do not see any logs for WKUP_UART0 from DM. Do I have to enable it?

    I am looking at all 4 UARTs in the USB debug port from the AM62 SK. I am using rev E2 and booting from your tisdk-default-image-am62xx-evm.wic.xz via SD card.

    /Magnus

  • Hi Magnus,

    The TIFS and DM debug trace is disabled in the SDK v8.4 pre-built images. You would have to rebuild U-Boot with the debug trace enabled.

    1. First please download and install the SDK installer, which provides the u-boot source code.

    2. Apply the following patch to the top level Makefile to enable the debug trace. The patch adds "ENABLE_TRACE=1" option to the make command.

    --- Makefile.orig       2022-10-04 11:17:51.106405852 -0500
    +++ Makefile    2022-10-27 13:36:52.123570746 -0500
    @@ -360,7 +358,7 @@
            @echo    Building SYSFW Image
            @echo =============================
            @cd board-support; cd `find . -maxdepth 1 -type d -name "*k3-image*"`; \
    -               make SBL=$(SBL_PATH) $(SYSFW_MAKEARGS) CROSS_COMPILE=$(CROSS_COMPILE_ARMV7) PATH=$(PATH):$(LINUXKERNEL_INSTALL_DIR)/scripts/dtc
    +               make ENABLE_TRACE=1 SBL=$(SBL_PATH) $(SYSFW_MAKEARGS) CROSS_COMPILE=$(CROSS_COMPILE_ARMV7) PATH=$(PATH):$(LINUXKERNEL_INSTALL_DIR)/scripts/dtc
    
     sysfw-image_clean:
            @echo =============================
    

    3. Run the following command at the top level directory to rebuild U-Boot.

    $ make u-boot sysfw-image

    4. Copy the following file to the SD card boot partition to overwrite the default one.

    board-support/k3-image-gen-2022.01/tiboot3.bin

    Now boot the SK EVM with the SD card, you will see debug messages on the MAIN UART1 and WKUP UART0 ports.