• State
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 233 views
  • Users 0 members are here
Support feedback
Options
Options
Related

TDA4VH-Q1: TDA4VH EVM board uboot software reset will hung.

Tao Han
Expert 6965 points

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

Hi Experts:

Our customer are runing LPDDR4 stability test at their board. They found that uboot has low probability hung at their production. We has compared LPDDR4 parameter setting and insure their configure is right. below is parameter review link.

TDA4VH-Q1: uboot boot error - Processors forum - Processors - TI E2E support forums

Now i has work at EVM board reproduce customer issue. Write a script run uboot software reset at EVM board. Looks like EVM uboot run reset has same problem. Could you please help us confirm at your side and debug it together?

This is reproduce method:

  1. EVM board E5 version TDA4VH.
  2. Software 11.02.00.04 and make SD card with prebuild release. just copy boot partition and keep rootfs partion is blank.
  3. run below test script at minicom 
    minicom -D /dev/ttyUSB0 -S autoboot.scr -C ./autoboot.logautoboot.txt 
    change autoboot.txt to autoboot.scr
  4. power on EVM board and capture the log.autoboot.log 

    we can find two kind of hung at EVM board.
    TypeA: LPDDR4 init failure like below log.
    SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.8--v11.02.08 (Fancy Rat)')
    k3_lpddr4_start: FAIL
    ### ERROR ### Please RESET the board ###
    at this failure mode use JTAG connect MCU R5 core, we can not access 0x80000000 LPDDR4 and PC stopped at 0x41c0869c
    image.png
    TypeB: Hung at sysfw print log.
    U-Boot SPL 2025.01-00773-gdf1fe2382304 (Dec 24 2025 - 07:50:42 +0000)
    SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.8--v11.02.08 (Fancy Rat)')

    At this failure mode use JTAG connect MCU R5 core, it hung at 0x41C1A024

image.png

 

Could you please help us analyze those uboot problem?

Best Regards!
Han Tao

  • 0
    TI__Mastermind 45040 points

    Hi Tao,

    I downloaded the boot partition of Linux SDK 11.02.00.04 from link below and flashed to SD card. We will run the test and update once results are available. 

    https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-lOshtRwR8P/11.02.00.04/boot-adas-j784s4-evm.tar.gz 

    Regards,
    Kevin

  • 0 in reply to Kevin S
    TI__Expert 6965 points

    HI Kevin:

    I am try old version SDK 10.01 uboot (10.01.00.05). Use same method at same EVM board, looks like RDK10.01 the uboot reset is difficult reproduce it.

    First time i run 2611 test circle, the EVM board has stopped and the current is 84ma@24V, i believe it is PMIC power supply problem. At this failure mode CCS can not connect any core. Second time run 1500 circle do not reproduce it and now still run it. Looks like this problem maybe relationship with SYSFW or uboot software. Below is test method at 10.01

    1. EVM board E5 version TDA4VH.
    2. Software 10.01.00.05 and make SD card with prebuild release. just copy boot partition and keep rootfs partion is blank.
    3. run below test script at minicom 
      minicom -D /dev/ttyUSB0 -S autoboot.scr -C ./autoboot.log autoboot10-01.tar

    could you please share your side verify results and suggest?

    Best Regards!

    Han Tao

  • 0 in reply to Tao Han
    TI__Mastermind 45040 points

    Hi Tao,

    It seems you observing various results. 

    First post mentioned two different failure modes, and latest post indicates you cannot even connect to any core. None of these results seem to align to exact failure location as the customers. 

    I would recommend that we focus on understanding the customer's failure in more detail. A review of the other thread seems like we are still missing some requested data. I will post a reply on the older thread.

    Regards,
    Kevin

  • 0 in reply to Kevin S
    TI__Expert 6965 points

    Hi Kevin:

    I try to integrate you shared retry patch at RDK11.02.00.04. Looks like those j784s4_ddr_retry.patch is different with Linux RDK11.02.00.04.

    Manual method integrate those patch and i added SPL cache enable and open TIFS log output. Will use this version run uboot reset command test it tonight.

    Could you please double check those retry patch (attached retrymodify.patch) whether has problem?

    Best Regards!

    Han Tao

    Original you shared retry patch.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/j784s4_5F00_ddr_5F00_retry.patch

    I modify the folder path to match RDK11.02.00.04 because j784s4_init.c change folder at RDK. /arch/arm/mach-k3/j784s4/j784s4_init.c

    Below are those patch added reject log.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/j784s4_5F00_init.c.rejhttps://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/k3_2D00_ddrss.c.rej

    this is final manual method add log test modify.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/retrymodify.patch