• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 1210 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.

TDA4VM: TDA4VM

hutian
Expert 1785 points
Part Number: TDA4VM


Hi experts,

We have designed a new board with TDA4 and i choose WKUP_Uart0 for boot mode. After power on our board, i can get the "CCCC..." output from WKUP_Uart0 which means i can send the tiboot3.bin by XMODE to MCU core. But when i send the tiboot3.bin successfully, nothing output from the WKUP_Uart0 and sysfw.itb also can't send. I would like to kindly ask about which part  should i take care to let the SPL start normally? Or how to debug with SPL in MCU_R5F?

Thanks,

Hutian

  • 0
    TI__Guru**** 166440 points

    Hi Hutian,

    http://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/latest/exports/docs/linux/Foundational_Components_U-Boot.html#booting-u-boot-from-the-console-uart

    Please follow the above documentation for UART boot on TDA4VM. For sysfw.itb you need to switch to ymodem on mcu_UART.

    Then ymodem should be used for tispl.bin and u-boot.img on main_uart.

    I hope that gets your UART boot working. If you are successful please resolve the issue.

    Thanks,
    Keerthy

  • 0 in reply to Keerthy J
    Expert 1785 points

    Hi Keerthy,

    I try with ymodem to send tispl.bin but failed with our board. When i use EVM board to run the same tiboot3.bin, it works. So, i guess Boot ROM may failed when booting our board with tiboot3.bin. 

    Do you know how to debugging with tiboot3.bin?

    Best Regards,

    Hutian 

  • 0 in reply to hutian
    TI__Guru**** 166440 points

    Hello Hutian,

    ROM Code expectation is clearly specified in the table:

    WHOLoading WHATHW ModuleProtocol
    Boot ROM tiboot3.bin MCU_UART0 X-Modem
    R5 SPL sysfw.itb MCU_UART0 Y-Modem
    R5 SPL tispl.bin MAIN_UART0 Y-Modem
    A53/A72 SPL u-boot.img MAIN_UART0 Y-Modem


    Please give me the exact steps you are following on the failing board. Also any logs from the
    console please share it.

    Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Expert 1785 points

    Hi Keerthy,

    I am failed at the 2-step.

    R5 SPL sysfw.itb MCU_UART0 Y-Modem

    and the log is shown below:

    Thanks,

    Hutian

  • 0 in reply to hutian
    TI__Guru**** 166440 points

    Hi Hutian,

    So the same step works on TDA4=EVM & fails on custom board? Is mu understanding right?

    - Keerthy

  • 0 in reply to Keerthy J
    Expert 1785 points

    Hi Keerthy,

    Yes it is. I changed the customer board’s boot mode for SD card, it can boot up the uboot regardless of some error log. Back to failure of Uart boot mode, do you know how to debugging SPL under this situation?

    Thanks,

    Hutian

  • 0 in reply to hutian
    TI__Guru**** 166440 points

    Hi Hutian,

    Do you get CCC in MCU UArt after tiboot3.bin is transferred and before sysfw is transferred on the failing board? Can you post the logs of SD boot on your custom board ?

    Thanks,

    Keerthy

  • 0 in reply to Keerthy J
    Expert 1785 points

    Hi Keerthy,

    Sorry for late reply. I can't get CCCC in WKUP UArt( because we changed  pinmux for the MCU Uart , so we use WKUP Uart instead). For WKUP Uart, i can get CCC at the start up, but no output when tiboot3.bin sends success. Below is the SD boot log with some modification related to our project:

    U-Boot SPL 2019.01-gc4ebb155ac (May 05 2020 - 08:20:00 +0000)
    SYSFW ABI: 2.9 (firmware rev 0x0013 '19.12.1-v2019.12a (Terrific Lla')
    Trying to boot from MMC2
    Loading Environment from MMC... *** Warning - No MMC card found, using default environment

    Remoteproc 2 started successfully
    ** File not found /lib/firmware/j7-mcu-r5f0_0-fw **
    Starting ATF on ARM64 core...

    NOTICE: BL31: v2.2(release):ti2019.05-rc1
    NOTICE: BL31: Built : 09:42:32, Mar 6 2020
    I/TC:
    I/TC: OP-TEE version: ti2019.05-rc1-dev (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #1 Fri Mar 6 10:00:07 UTC 2020 aarch64
    I/TC: Initialized

    U-Boot SPL 2019.01-gc8ea9edee2 (May 05 2020 - 08:09:52 +0000)
    Trying to boot from MMC2


    U-Boot 2019.01-gc8ea9edee2 (May 05 2020 - 08:09:52 +0000)

    SoC: J721E PG 1.0
    Model: TECHNOMOUS VDCU BOARD J721E SoC
    Board: TN-VDCU-J721EX Sample: B
    DRAM: 4 GiB
    cdns3_bind: unsupported dr_mode
    Flash: 0 Bytes
    MMC: sdhci@4f80000: 0, sdhci@4fb0000: 1
    Loading Environment from SPI Flash... Detected n25q00a OK
    In: serial@2800000
    Out: serial@2800000
    Err: serial@2800000
    Net: read phy id:ffffffff ,from addr:0
    read phy id:ffffffff ,from addr:0
    read phy id:ffffffff ,from addr:0
    read phy id:ffffffff ,from addr:0
    read phy id:ffffffff ,from addr:0
    Could not get PHY for ethernet@046000000: addr 0
    phy_connect() failed
    eth-1: ethernet@046000000
    Hit any key to stop autoboot: 0

    Thanks,

    Hutian

  • 0 in reply to hutian
    TI__Guru**** 166440 points

    Hi Hutian,

    I checked on TDA4-EVM No "CCCCC" Comes on wkup-uart0. It only comes on mcu_uart0.
    Expectation of RoM Code is to always load tiboot3.bin on mcu_uart0 otherwise we cannot
    predict what is going on. I am not sure how you are getting "CCCCC" on wkup-uart0 on
    custom board but even if you do RoM code will surely be expecting it on mcu-uart0 so
    we cannot predict the behavior.

    Regards,
    Keerthy

  • 0 in reply to Keerthy J
    Expert 1785 points

    Hi Keerthy,

    Thanks for your information. In the TRM Chapter 4.3.12, you can choose MCU UART or WKUP UART for UART boot mode by setting the BOOTMODE pins. I have already successfully test on EVM board by WKUP UART. Currently it is not urgent enough, because we have start up our custom board by SD card. I will close this conversation soon.

    Best Regards

    Hutian