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: r5 core load failed in uboot

Part Number: TDA4VM

HI, TI team:

when board starting  up, this error occured. please help to check this question. thinks.

" Load Remote Processor 3 with data@addr=0x82000000 1968096 bytes: Failed! "

LOG:

U-Boot 2020.01-g2781231a33 (Apr 10 2021 - 00:17:14 +0000)

SoC: J721E SR1.0
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev E8
DRAM: 4 GiB
not found for dev hbmc-mux
Flash: 0 Bytes
MMC: sdhci@4f80000: 0, sdhci@4fb0000: 1
Loading Environment from MMC... OK
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Detected: J7X-BASE-CPB rev E3
Detected: J7X-GESI-EXP rev E3
Detected: J7X-VSC8514-ETH rev E2
Net: K3 CPSW: nuss_ver: 0x6BA00101 cpsw_ver: 0x6BA80100 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
eth0: ethernet@46000000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
526 bytes read in 4 ms (127.9 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
Core 1 is already in use. No rproc commands work
Core 2 is already in use. No rproc commands work
1968096 bytes read in 44 ms (42.7 MiB/s)
Invalid seq: Enable primary core before loading secondary core
Load Remote Processor 3 with data@addr=0x82000000 1968096 bytes: Failed!
1579120 bytes read in 34 ms (44.3 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 1579120 bytes: Success!
1579120 bytes read in 35 ms (43 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 1579120 bytes: Success!
10268600 bytes read in 92 ms (106.4 MiB/s)
Load Remote Processor 8 with data@addr=0x82000000 10268600 bytes: Success!
8188524 bytes read in 174 ms (44.9 MiB/s)
## Starting application at 0x80080000 ...
MMU: 16-bit ASID 44-bit PA TCR_EL1=b5183519
cpu0: MPIDR=80000000
cpu0: MIDR=411fd080 Cortex-A72 r1p0
cpu0: CWG=4 ERG=4 Dminline=4 Iminline=4 PIPT
cpu0: CLIDR=a200023 LoUU=1 LoC=2 LoUIS=1
cpu0: L1 Icache 48K linesz=64 set/way=256/3
cpu0: L1 Dcache 32K linesz=64 set/way=256/2
cpu0: L2 Unified 1024K linesz=64 set/way=1024/16
Display set to R5
Loading IFS...decompressing...done
cpu1: MPIDR=80000001
cpu1: MIDR=411fd080 Cortex-A72 r1p0
cpu1: CWG=4 ERG=4 Dminline=4 Iminline=4 PIPT
cpu1: CLIDR=a200023 LoUU=1 LoC=2 LoUIS=1
cpu1: L1 Icache 48K linesz=64 set/way=256/3
cpu1: L1 Dcache 32K linesz=64 set/way=256/2
cpu1: L2 Unified 1024K linesz=64 set/way=1024/16

System page at phys:0000000080011000 user:ffffff8040254000 kern:ffffff8040251000
Starting next program at vffffff80600883c0
All ClockCycles offsets within tolerance
Welcome to QNX Neutrino 7.1.0 on the TI J721E EVM Board!!
Starting random service ...
start serial driver
Starting MMC/SD memory card driver... eMMC
Starting MMC/SD memory card driver... SD
Starting XHCI driver on USB3SS0 and USB3SS1
Path=0 - am65x
target=0 lun=0 Direct-Access(0) - SDMMC: S0J56X Rev: 1.0
Setting environment variables...
done..
Mounting the sd ..
Looking for user script to run: /ti_fs/scripts/user.sh
Running user script...
user.sh called...
Setting additional environment variables...
Starting tisci-mgr..

  • Hi Wenyu,

    I see that you are using 7.3 SDK based on the U-Boot version. Did you move from an older U-Boot to a newer U-Boot?

    The error is thrown because you are trying to boot Main R5FSS Core1 (U-Boot remoteproc id #3) before the corresponding Main R5FSS Core0 (U-Boot remoteproc id #2) from the following traces.

    Invalid seq: Enable primary core before loading secondary core
    Load Remote Processor 3 with data@addr=0x82000000 1968096 bytes: Failed! 

    Please double check your rproc_fw_binaries variable. This should also list the Core 0 (2 /lib/firmware/j7-main-r5f0_0-fw ...). This variable is updated in 7.1 SDK.

    If you have moved from an older U-Boot, please get the new environment variables by executing the following commands once,

    env default -a -f; env save

    regards

    Suman

  • HI, Suman:

     I fixed this issue according your solution, thank you!