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.
Hi,
I am using the following packages to build the QNX+RTOS SDK
RTOS: ti-processor-sdk-rtos-j721e-evm-08_00_00_12
QNX: qnx710
QNX BSP: /qnx710/bsp/BSP_ti-j721e-am752x-evm_br-710_be-710_SVN927158_JBN10
Followed following steps to Build mentioned in:
https://software-dl.ti.com/jacinto7/esd/processor-sdk-qnx-jacinto7/latest/exports/docs/getting_started_j721e.html#downloading-and-installing-the-psdk-qnx
https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/latest/exports/docs/vision_apps/docs/user_guide/BUILD_INSTRUCTIONS.html
Build Gets successful for QNX + RTOS mode. However when i am booting the board using SD card, I don't get any log on any UART.
But if i use the RTOS+LINUX package, i am able to run the applications.
Attached is the image of the board I am using.
Please let me know how to debug this issue.
Note: I have the QNX license 7.1 and have installed all the packages as mentioned in the Dependency section.
Hi,
A full install / rebuild was done locally and no issues were seen with SPL SD Boot mode using Processor SDK QNX 8.0.
An "ls -l" of the SD card root directory and main UART boot los are below.
Possible issues you're running into could be:
Regards,
kb
SD Card Contents:
Main UART Boot log:
U-Boot SPL 2021.01-g53e79d0e89 (Aug 04 2021 - 23:32:00 +0000) Model: Texas Instruments K3 J721E SoC Board: J721EX-PM2-SOM rev E6 SYSFW ABI: 3.1 (firmware rev 0x0015 '21.5.0--v2021.05 (Terrific Llam') Trying to boot from MMC2 Starting ATF on ARM64 core... NOTICE: BL31: v2.5(release):08.00.00.004-dirty NOTICE: BL31: Built : 22:30:09, Aug 4 2021 U-Boot SPL 2021.01-g53e79d0e89 (Aug 04 2021 - 22:33:28 +0000) Model: Texas Instruments K3 J721E SoC Board: J721EX-PM2-SOM rev E6 SYSFW ABI: 3.1 (firmware rev 0x0015 '21.5.0--v2021.05 (Terrific Llam') Detected: J7X-BASE-CPB rev E3 Detected: J7X-VSC8514-ETH rev E2 Trying to boot from MMC2 U-Boot 2021.01-g53e79d0e89 (Aug 04 2021 - 22:33:28 +0000) SoC: J721E SR1.0 Model: Texas Instruments K3 J721E SoC Board: J721EX-PM2-SOM rev E6 DRAM: 4 GiB Flash: 0 Bytes MMC: sdhci@4f80000: 0, sdhci@4fb0000: 1 In: serial@2800000 Out: serial@2800000 Err: serial@2800000 Detected: J7X-BASE-CPB rev E3 Detected: J7X-VSC8514-ETH rev E2 Net: am65_cpsw_nuss_slave ethernet@46000000: 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 Failed to load 'boot.scr' 526 bytes read in 9 ms (56.6 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 k3_r5f_rproc r5f@41400000: Core 2 is already in use. No rproc commands work 2550940 bytes read in 115 ms (21.2 MiB/s) Load Remote Processor 2 with data@addr=0x82000000 2550940 bytes: Success! 506744 bytes read in 31 ms (15.6 MiB/s) Load Remote Processor 3 with data@addr=0x82000000 506744 bytes: Success! Failed to load '/lib/firmware/j7-main-r5f1_0-fw' Failed to load '/lib/firmware/j7-main-r5f1_1-fw' 1579088 bytes read in 71 ms (21.2 MiB/s) Load Remote Processor 6 with data@addr=0x82000000 1579088 bytes: Success! 1579088 bytes read in 72 ms (20.9 MiB/s) Load Remote Processor 7 with data@addr=0x82000000 1579088 bytes: Success! 10399616 bytes read in 183 ms (54.2 MiB/s) Load Remote Processor 8 with data@addr=0x82000000 10399616 bytes: Success! 8144576 bytes read in 348 ms (22.3 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 vffffff8060086e10 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.. Starting shmemallocator.. Starting tiipc-mgr.. Starting TI IPC Resmgr Starting tiudma-mgr.. Start screen.. screen started with dss_on_r5 configuration.. done...
Hi,
My SD card content contains all the files/folders mentioned by you above.
I did clean build 2-3 times and even removed the linux package from my system. Still facing the same issue.
Do i need to do anything w.r.t Board revision number. As per the board image shared earlier, BOM Revision 1.0 is mentioned on the J721EX SOM board.
In file vision_apps/vision_apps_build_flags.mak # Flag to select silicon revision: 1_1 for ES 1.1, 1_0 for ES 1.0
J7ES_SR?=1_1
Also in the tiovx/build_flags.mak "RTOS?=FREERTOS", this is the default setting for 8.0 package. Do i need to change this?
Hi,
Please check to ensure the file sizes on the SD card under test, match the above. If there are deltas, then we can work to figure out why.
In local testing no modifications were made to SDK 8.0, outside of those in the Vision Apps User guide steps.
I'm not aware of any EVM related issues, with the release. If you want to provide the SD card creation commands, and build commands being used, I can follow those on this end to see if boot is successful.
Regards,
kb
I doubt there is issue with the build and sd-card contents.
I tried to use QNX+RTOS for 7.3 as well, but that also did not boot up. Got the same issue as mentioned in earlier posts.
This points me to some other issue.
We would like to know if the QNX +RTOS build has been tested for the following EVM version, details are mentioned below.
SoC: J721E SR1.0
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM1-SOM rev E2
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 E2
Detected: J7X-VSC8514-ETH rev E2
Note: Above information has been taken when the device boots up using LINUX+RTOS package
Hi,
I will check into EVMs tested by the TI SDK release team.
Please be aware that if the SDK QNX is being used in SPL SD boot mode (Uboot boot based SD boot mode), then the same UBoot version for QNX / Linux will be being used. Uboot prompt should be reached in both cases. Any issues specific to loading QNX vs. Linux images would occur once the HLOS is loaded.
For the issue being reported, UART console has no output, meaning UBoot prompt is not being reached. This would infer issue is before HLOS.
Are there any logs on port 1 of the MCU UART?
Please confirm image sizes in root of SD card have been checked against those provided above.
Thanks,
kb
Hi,
my sd card content size matches with the one shared by you.
There is no logs seen on both the UART, i have checked that every time i have attempted the boot.
Hi,
Noted that IFS is not the same size in our setups, but as boot is not getting that far, not a concern for current issue.
Re-ran the SD creation / build / install with below commands, still not seeing any issues.
S/W:
Boot Mode: SPL SD boot mode.
Build Commands:
Followed: Vision Apps User Guide: Build Instructions
<unseated / reseated SD card, so it would re-enumerate>
EVM Boot Log on local board:
SoC: J721E SR1.0
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev E6
DRAM: 4 GiB
Flash: 0 Bytes
MMC: sdhci@4f80000: 0, sdhci@4fb0000: 1
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Detected: J7X-BASE-CPB rev E3
Detected: J7X-VSC8514-ETH rev E2
EVM Boot log from 1 board on test farm
SoC: J721E SR1.0
Model: Texas Instruments K3 J721E SoC
Board: J721EX-PM2-SOM rev E7
DRAM: 4 GiB
Flash: 0 Bytes
MMC: sdhci@4f80000: 0, sdhci@4fb0000: 1
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
Quick test to try:
Reformat the SD card, copy linux prebuilt boot binaries to target.
In local testing this will get you to the uboot prompt.
Please also try disconnecting / reconnecting the serial cable, have seen that cause issues in the past when switching between HLOS's.
Regards,
kb
Hi,
I am able to boot the board with QNX now.
However there appears to be a bug with the RUN instructions for QNX at my side.
If i follow the steps like this as mentioned in the Run Instructions:
Thanks for the update, good to hear the boot is working.
Regarding Step 1, Step2, Step 3 above, assumption is that there is a "typo" in the cut'n paste above, as linux steps are being referenced. This thread is for QNX, the QNX version of the same steps should be used.
Regarding Step 2, this should have no impact on boot. The content being extracted will be present in the /vision_apps directory in root of the DOS partition of the SD card. This will not touch any of the required boot content for SD SPL boot flow. Will try locally to see if issue can be reproduced
Regards,
kb
Hi,
Can reproduce, an issue, which is likely what you are hitting
Recreating Issue
Following below steps as documents, boot is not working.
Step 1: Prepare SD card for boot
Step2: Copy test data to SD card (one time only)
Step 3a: Copy executable files to SD card for boot using SPL_Uboot
Workaround
To work around this, swap the sequence of step2 and step3a, and boot will work fine.
Step 1: Prepare SD card for boot
Step 3a: Copy executable files to SD card for boot using SPL_Uboot
Step2: Copy test data to SD card (one time only)
Regards,
kb
Hi,
Yes, I was also doing the above steps earlier and was facing the boot issue. Swapping Step 2 and Step 3a solves this problem.
I would like to know the reason behind this. Please let me know as well just for understanding purpose.