TDA4VM-Q1: Establishing ground zero

Hi;

Thanks for the question. 

Could you let us know what you have done exactly? Such as how you have built your own Edge AI? Which example you have followed? So we can replicate it on our end. 

Normally, for TIDL application, you can follow the TIDL examples in RTOS-SDK. 

Here is the link for vision apps and how to build SDK.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/vision_apps/docs/user_guide/index.html

Thanks and regards

Wen Li

Using TDA4VM SK board,  I load a SD card with "tisdk-edgeai-image-j721e-evm.wic"  This is from the latest "ti-processor-sdk-linux-edgeai-j721e-evm-11_00_00_08-Linux-x86-Install.bin"

The TI image will work. I can run demos.  Linux Demo's.  

Now, with the SDK installing and following the make directions under "Simplified SDK Build Using Top-Level Makefile.  I do a clean.  then Make All.  then install u-boot and then install linux.  I also install linux-dtbs_install.  All of this is to the SD card.  I see updated u-boot and linux image file.

I expected to run this SD card and get same demo's to run.  But it does not.  Below is the output.  but not all.  I question the lines for remote proc.  Why failed to load.

Question. Did I need to rename u-boot.img.unsigned to u-boot-img  and one other.

I also ran setup_script.sh and let everything rebuild there.  But no run.

U-Boot SPL 2025.01-ti-g70667128cb5b-dirty (Dec 08 2025 - 20:47:24 -0500)
SYSFW ABI: 4.0 (firmware rev 0x000b '11.0.9--v11.00.09+ (Fancy Rat)')
Trying to boot from MMC2
Skipping authentication on GP device
Skipping authentication on GP device
Skipping authentication on GP device
Skipping authentication on GP device
Skipping authentication on GP device
Loading Environment from nowhere... OK
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.12.0(release):11.00.09-dirty
NOTICE:  BL31: Built : 12:35:58, Mar 24 2025
 0 
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
845 bytes read in 1 ms (825.2 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
k3_r5f_rproc r5f@41000000: Core 1 is already in use. No rproc commands work
Failed to load '/lib/firmware/j7-mcu-r5f0_1-fw'
564896 bytes read in 143 ms (3.8 MiB/s)
Load Remote Processor 2 with data@addr=0x82000000 564896 bytes: Success!
351412 bytes read in 136 ms (2.5 MiB/s)
Load Remote Processor 3 with data@addr=0x82000000 351412 bytes: Success!
Failed to load '/lib/firmware/j7-main-r5f1_0-fw'
Failed to load '/lib/firmware/j7-main-r5f1_1-fw'
1014576 bytes read in 149 ms (6.5 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 1014576 bytes: Success!
1014576 bytes read in 149 ms (6.5 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 1014576 bytes: Success!
13234320 bytes read in 236 ms (53.5 MiB/s)
Load Remote Processor 8 with data@addr=0x82000000 13234320 bytes: Success!
22256128 bytes read in 458 ms (46.3 MiB/s)
121850 bytes read in 6 ms (19.4 MiB/s)
Working FDT set to 88000000
10314 bytes read in 3 ms (3.3 MiB/s)
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
   Loading Device Tree to 000000008fedf000, end 000000008fffffff ... OK
Working FDT set to 8fedf000

Starting kernel ...

Thank you for responding.

Thank for the feedback info. 

I am not sure about here the u-boot/linux and then hand over the TIDL apps to processor working correctly. Because, we use the RTOS SDK to build from scratch. Maybe we need to ask the boot expert. I will try to ask around. So give us some time.  

Best regards

Wen Li

Hello;

Here is the documentation link for how to build a boot-able SD card and copy the vision-apps to the card.

https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/vision_apps/docs/user_guide/RUN_INSTRUCTIONS.html

Thanks and regards

Wen Li