PROCESSOR-SDK-J721S2: Enable USB 2.0 Hub on J721EXCP01EVM

Ahmed Mujtaba

HI,

I am using a Jacinto7 Common Processor Board (J721EXCP01EVM) with System On Module (J721S2XSOMG01EVM). I have build the image using the Processor SDK Linux with this version.

Be default, the USB Type C port is enabled on the EVM, and I want to enable the stacked 2 x USB 2.0 Hub on the EVM.

Thanks,

Ahmed

over 1 year ago

0 Diwakar Dhyani over 1 year ago

TI__Guru 56925 points

Hi Ahmed,

Please follow the similar steps mentioned in the FAQ

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1303008/faq-j721s2xsomxevm-enable-usb-2-0-hub-on-j7200-j721s2-j784s4

Regards
Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

According to the FAQ you provided, there is one issue.

In my SD card boot folder, there is no "k3-j7200-common-proc-board.dtb" file. I have "k3-j721s2-common-proc-board.dtb" file in my boot folder.

The patch provided in the FAQ update the "k3-j7200-som-p0.dtsi" file.

I also tried one solution in which I modified the patch, where I changes j7200 to j721s2. Like this,

From b7ca3f7362fccc9403230f28611c9fd0d0ddaff6 Mon Sep 17 00:00:00 2001
From: diwakar <d-dhyani@ti.com>
Date: Wed, 7 Dec 2022 12:22:32 +0530
Subject: [PATCH] Enable staked USB2.0

---
 arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi b/arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi
index 347244401..bfd34580c 100644
--- a/arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi
+++ b/arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi
@@ -6,6 +6,8 @@
 /dts-v1/;
 
 #include "k3-j721s2.dtsi"
+#include <dt-bindings/gpio/gpio.h>
+
 
 / {
 	memory@80000000 {
@@ -249,7 +251,13 @@ exp_som: gpio@21 {
 				  "CANUART_MUX2_SEL0", "CANUART_MUX_SEL1",
 				  "UART/LIN_MUX_SEL", "TRC_D17/AUDIO_REFCLK_SEL",
 				  "GPIO_LIN_EN", "CAN_STB";
-	};
+                usb_hub@0 {
+                        gpio-hog;
+                        gpios = <0 GPIO_ACTIVE_HIGH>;
+                        output-high;
+                        line-name = "USB2.0_MUX_SEL";
+                };
+        };
 };
 
 &ospi0 {
-- 
2.34.1

However, when I run this command with the modified changes (j7200 -> j721s2),

git am 0001-Enable-staked-USB2.0.patch

I receive this error,

Applying: Enable staked USB2.0
error: patch failed: arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi:6
error: arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi: patch does not apply
Patch failed at 0001 Enable staked USB2.0
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Can you send me the patched "k3-j721s2-common-proc-board.dtb" file so that I can simply replace it in my SD card boot folder?

Or updated patch "0001-Enable-staked-USB2.0.patch" for j721s2?

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

Hi Ahmed ,

In the Faq it is mentioned that the example patch is for the J7200 .you need to make similar changes for your soc.

Regards

Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

Can you specify what changes must be made to modify the patch for j721s2 soc?

Thanks,

Ahmed

0 Ahmed Mujtaba over 1 year ago in reply to Ahmed Mujtaba

Prodigy 235 points

And, these are the logs I see when I boot up the board.

U-Boot 2021.01-g62a9e51344 (May 02 2023 - 16:17:36 +0000)

SoC:   J721S2 SR1.0 GP
Model: Texas Instruments J721S2 EVM
Board: J721S2X-PM1-SOM rev E3
DRAM:  16 GiB
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Net:   eth0: ethernet@46000000port@1
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'
907 bytes read in 6 ms (147.5 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
588872 bytes read in 21 ms (26.7 MiB/s)
Load Remote Processor 2 with data@addr=0x82000000 588872 bytes: Success!
306092 bytes read in 14 ms (20.9 MiB/s)
Load Remote Processor 3 with data@addr=0x82000000 306092 bytes: Success!
Failed to load '/lib/firmware/j721s2-main-r5f1_0-fw'
Failed to load '/lib/firmware/j721s2-main-r5f1_1-fw'
14815296 bytes read in 323 ms (43.7 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 14815296 bytes: Success!
9760696 bytes read in 216 ms (43.1 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 9760696 bytes: Success!
19079680 bytes read in 412 ms (44.2 MiB/s)
Failed to load '/boot/k3-j721s2-common-proc-board.dtb'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
9262 bytes read in 7 ms (1.3 MiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
=>

In the logs, I see,

"Failed to load '/boot/k3-j721s2-common-proc-board.dtb'"

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

Hi Ahmed

You are modifying the by just changing the name from j7200 to j721s2 that will not work.

Please remove those changes and use below patch for j721s2

https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/0001_2D00_Enable_2D00_USB2.0_2D00_stacked_2D00_in_2D00_j721s2.patch

SDK used : 08_06_01_02

command:

cd <linux_sdk>/board-support/<linux*>/
git am 0001-Enable-USB2.0-stacked-in-j721s2.patch
cd ../../
make linux-dtbs
cp board-support/<linux*>/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dtb /media/<xyz>/rootfs/boot/

Regards
Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

Thanks for sharing the updated patch file.

I have successfully applied the changes, however, upon changing the "k3-j721s2-common-proc-board.dtb" in SD card's "/media/<xyz>/rootfs/boot/" folder, I still receive this error message on the UART port upon boot-up,

U-Boot 2021.01-g62a9e51344 (May 02 2023 - 16:17:36 +0000)

SoC:   J721S2 SR1.0 GP
Model: Texas Instruments J721S2 EVM
Board: J721S2X-PM1-SOM rev E3
DRAM:  16 GiB
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Net:   eth0: ethernet@46000000port@1
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'
907 bytes read in 6 ms (147.5 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
588872 bytes read in 20 ms (28.1 MiB/s)
Load Remote Processor 2 with data@addr=0x82000000 588872 bytes: Success!
306092 bytes read in 15 ms (19.5 MiB/s)
Load Remote Processor 3 with data@addr=0x82000000 306092 bytes: Success!
Failed to load '/lib/firmware/j721s2-main-r5f1_0-fw'
Failed to load '/lib/firmware/j721s2-main-r5f1_1-fw'
14815296 bytes read in 322 ms (43.9 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 14815296 bytes: Success!
9760696 bytes read in 216 ms (43.1 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 9760696 bytes: Success!
19079680 bytes read in 412 ms (44.2 MiB/s)
Failed to load '/boot/k3-j721s2-common-proc-board.dtb'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
9262 bytes read in 7 ms (1.3 MiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
=>

To confirm that the patch file has successfully worked, I saw the "k3-j721s2-som-p0.dtsi" file in "<linux_sdk>/board-support/<linux*>/arch/arm64/boot/dts/ti/". The patch file has successfully included the code. However, for some reason, the EVM fails to load "k3-j721s2-common-proc-board.dtb" upon boot up.

By the way, I am using the default edgeai image "tisdk-edgeai-image-j721s2-evm" in "/bin/mksdboot.sh".

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

HI Ahmed

Ahmed Mujtaba said:
By the way, I am using the default edgeai image "tisdk-edgeai-image-j721s2-evm" in "/bin/mksdboot.sh".

Are you using 9x sdk i thought you are using 8.6 sdk

In 9.x SDK dtbs are kept in media/<xyz>root/boot/dtb/ti/ folder whereas in 8.6 SDK "/media/<xyz>/rootfs/boot/" folder

Regards
Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

Diwakar Dhyani said:
Are you using 9x sdk i thought you are using 8.6 sdk

I am using 8.6 SDK.

Diwakar Dhyani said:
In 9.x SDK dtbs are kept in media/<xyz>root/boot/dtb/ti/ folder whereas in 8.6 SDK "/media/<xyz>/rootfs/boot/" folder

Therefore, I placed the "k3-j721s2-common-proc-board.dtb" in "/media/<xyz>/rootfs/boot/" in my SD card.

Thanks,

Ahmed

0 Ahmed Mujtaba over 1 year ago in reply to Ahmed Mujtaba

Prodigy 235 points

Just for the clarity, the patch you provided

Diwakar Dhyani said:
0001-Enable-USB2.0-stacked-in-j721s2.patch

has included the following changes in "k3-j721s2-common-proc-board.dtb",

			gpio@21 {
				compatible = "ti,tca6408";
				reg = <0x21>;
				gpio-controller;
				#gpio-cells = <0x2>;
				gpio-line-names = "USB2.0_MUX_SEL", "CANUART_MUX1_SEL0", "CANUART_MUX2_SEL0", "CANUART_MUX_SEL1", "GPIO_RGMII1_RST", "GPIO_eDP_ENABLE", "GPIO_LIN_EN", "CAN_STB";
				phandle = <0x28>;

				usb_hub@0 {
					gpio-hog;
					gpios = <0x0 0x0>;
					output-high;
					line-name = "USB2.0_MUX_SEL";
				};
			};

And, I copy the device tree "k3-j721s2-common-proc-board.dtb" file in my SD card by using this command,

cp board-support/<linux*>/arch/arm64/boot/dts/ti/k3-j721s2-common-proc-board.dtb /media/<xyz>/rootfs/boot/

The file successfully includes in my SD card, however, the board does not boots up and gives this error,

U-Boot 2021.01-g62a9e51344 (May 02 2023 - 16:17:36 +0000)

SoC:   J721S2 SR1.0 GP
Model: Texas Instruments J721S2 EVM
Board: J721S2X-PM1-SOM rev E3
DRAM:  16 GiB
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Net:   eth0: ethernet@46000000port@1
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'
907 bytes read in 6 ms (147.5 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
588872 bytes read in 20 ms (28.1 MiB/s)
Load Remote Processor 2 with data@addr=0x82000000 588872 bytes: Success!
306092 bytes read in 15 ms (19.5 MiB/s)
Load Remote Processor 3 with data@addr=0x82000000 306092 bytes: Success!
Failed to load '/lib/firmware/j721s2-main-r5f1_0-fw'
Failed to load '/lib/firmware/j721s2-main-r5f1_1-fw'
14815296 bytes read in 322 ms (43.9 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 14815296 bytes: Success!
9760696 bytes read in 216 ms (43.1 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 9760696 bytes: Success!
19079680 bytes read in 412 ms (44.2 MiB/s)
Failed to load '/boot/k3-j721s2-common-proc-board.dtb'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
9262 bytes read in 7 ms (1.3 MiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
=>

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

HI Ahmed

an you run below command in U-BOOT to see if the partition contain the file or not.

mmc dev 1
ls mmc 1:2 boot/'

Share the output of the above comnad.

Or try re flashing the SD card with the prebuild image just replace the k3-j721s2-common-proc-board.dtb in the sd card.

Regards
Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Sure,

for this command,

Diwakar Dhyani said:
mmc dev 1

the logs are,

=> mmc dev 1
switch to partitions #0, OK
mmc1 is current device

for this command,

Diwakar Dhyani said:
ls mmc 1:2 boot/'

the logs are,

=> ls mmc 1:2 boot/
<DIR>       4096 .
<DIR>       4096 ..
<SYM>         26 Image
        19079680 Image-5.10.162-g76b3e88d56
<SYM>         29 fitImage
         8345343 fitImage-5.10.162-g76b3e88d56
           74891 k3-am68-sk-base-board.dtb
            3108 k3-am68-sk-bb-csi2-ov5640.dtbo
            3816 k3-am68-sk-bb-rpi-cam-imx219.dtbo
            3989 k3-am68-sk-fpdlink-fusion.dtbo
           74774 k3-am68-sk-reve1-base-board.dtb
            2900 k3-am68-sk-reve1-bb-csi2-ov5640.dtbo
            3740 k3-am68-sk-reve1-bb-rpi-cam-imx219.dtbo
            1741 k3-am68-sk-rpi-hdr-ehrpwm.dtbo
            7996 k3-am68-sk-som-ddr_mem_carveout.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-0-0.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-0-1.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-0-2.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-0-3.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-1-0.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-1-1.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-1-2.dtbo
            2471 k3-j721e-fpdlink-imx390-cm-1-3.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-0-0.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-0-1.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-0-2.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-0-3.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-1-0.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-1-1.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-1-2.dtbo
            2471 k3-j721e-fpdlink-imx390-rcm-1-3.dtbo
               0 k3-j721s2-common-proc-board.dtb
            1614 k3-j721s2-cpb-csi2-ov5640.dtbo
            9262 k3-j721s2-edgeai-apps.dtbo
            3155 k3-j721s2-fpdlink-cpb-fusion.dtbo
            1764 k3-j721s2-gesi-exp-board.dtbo
           10142 k3-j721s2-vision-apps.dtbo
=>

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

HI Ahmed

Why the size is 0

did you make sure that you are building and copying binary correctly ?

Regards
Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

I unmounted the SD card to check the "k3-j721s2-common-proc-board.dtb" file in my SD card, it does not shows size 0.

data-mode="text">total 27164 4096 Dec 18 08:06 . 4096 May 2 2023 .. 26 May 2 2023 Image -> Image-5.10.162-g76b3e88d56 root root 19079680 May 2 2023 Image-5.10.162-g76b3e88d56 29 May 2 2023 fitImage -> fitImage-5.10.162-g76b3e88d56 8345343 May 2 2023 fitImage-5.10.162-g76b3e88d56 74891 May 2 2023 k3-am68-sk-base-board.dtb 3108 May 2 2023 k3-am68-sk-bb-csi2-ov5640.dtbo 3816 May 2 2023 k3-am68-sk-bb-rpi-cam-imx219.dtbo 3989 May 2 2023 k3-am68-sk-fpdlink-fusion.dtbo 74774 May 2 2023 k3-am68-sk-reve1-base-board.dtb 2900 May 2 2023 k3-am68-sk-reve1-bb-csi2-ov5640.dtbo 3740 May 2 2023 k3-am68-sk-reve1-bb-rpi-cam-imx219.dtbo 1741 May 2 2023 k3-am68-sk-rpi-hdr-ehrpwm.dtbo 7996 May 2 2023 k3-am68-sk-som-ddr_mem_carveout.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-cm-0-0.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-cm-0-1.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-cm-0-2.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-cm-0-3.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-cm-1-0.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-cm-1-1.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-cm-1-2.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-cm-1-3.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-rcm-0-0.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-rcm-0-1.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-rcm-0-2.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-rcm-0-3.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-rcm-1-0.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-rcm-1-1.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-rcm-1-2.dtbo 2471 May 2 2023 k3-j721e-fpdlink-imx390-rcm-1-3.dtbo 82643 Dec 18 08:15 k3-j721s2-common-proc-board.dtb 1614 May 2 2023 k3-j721s2-cpb-csi2-ov5640.dtbo 9262 May 2 2023 k3-j721s2-edgeai-apps.dtbo 3155 May 2 2023 k3-j721s2-fpdlink-cpb-fusion.dtbo 1764 May 2 2023 k3-j721s2-gesi-exp-board.dtbo 10142 May 2 2023 k3-j721s2-vision-apps.dtbo

And, I tried booting up the board, it worked for the first time, which is good.

However, if I restart the board, it give the same error. This is strange.

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

Hi Ahmed

What is the error you are getting

Is usb2.0 stack is working ?

Regards
Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

Diwakar Dhyani said:
What is the error you are getting

This one upon multiple boot ups,

U-Boot 2021.01-g62a9e51344 (May 02 2023 - 16:17:36 +0000)

SoC:   J721S2 SR1.0 GP
Model: Texas Instruments J721S2 EVM
Board: J721S2X-PM1-SOM rev E3
DRAM:  16 GiB
Flash: 0 Bytes
MMC:   mmc@4f80000: 0, mmc@4fb0000: 1
In:    serial@2880000
Out:   serial@2880000
Err:   serial@2880000
am65_cpsw_nuss ethernet@46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
Net:   eth0: ethernet@46000000port@1
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'
907 bytes read in 6 ms (147.5 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
588872 bytes read in 20 ms (28.1 MiB/s)
Load Remote Processor 2 with data@addr=0x82000000 588872 bytes: Success!
306092 bytes read in 15 ms (19.5 MiB/s)
Load Remote Processor 3 with data@addr=0x82000000 306092 bytes: Success!
Failed to load '/lib/firmware/j721s2-main-r5f1_0-fw'
Failed to load '/lib/firmware/j721s2-main-r5f1_1-fw'
14815296 bytes read in 322 ms (43.9 MiB/s)
Load Remote Processor 6 with data@addr=0x82000000 14815296 bytes: Success!
9760696 bytes read in 216 ms (43.1 MiB/s)
Load Remote Processor 7 with data@addr=0x82000000 9760696 bytes: Success!
19079680 bytes read in 412 ms (44.2 MiB/s)
Failed to load '/boot/k3-j721s2-common-proc-board.dtb'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
9262 bytes read in 7 ms (1.3 MiB/s)
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
=>

Diwakar Dhyani said:
Is usb2.0 stack is working ?

Yes, it is working.

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

Hi Ahmed

During pass and failure cases what is the size you getting of k3-j721s2-common-proc-board.dtb

using command

mmc dev 1
ls mmc 1:2 boot/'

Regards
Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

Diwakar Dhyani said:
During pass and failure cases what is the size you getting of k3-j721s2-common-proc-board.dtb

I get size=0.

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

Hi Ahmed

Is it always the case of in case of failure only you are getting this issue.

Can you reflash the SD card with the prebuild image and see.

Regards

Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

Diwakar Dhyani said:
Can you reflash the SD card with the prebuild image and see.

I have tested multiple times and found out that the only time the board does not boots up is when the device tree file does not copy into the SD card.

After I copy the device tree file correctly, the TI board boots up correctly.

However, after booting up the board, the original edgeai-gui is not showing? Is this because of patching?

Thanks,

Ahmed

0 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

HI Ahmed

Are you able to use the display or just GUI is not coming?

Regards
Diwakar

0 Ahmed Mujtaba over 1 year ago in reply to Diwakar Dhyani

Prodigy 235 points

Hi Diwakar,

Diwakar Dhyani said:
Are you able to use the display or just GUI is not coming?

I think just the GUI is not coming. I tried to display the GUI using,

etc/init.d/edgeai-launcher.sh start

but found that there is no "edgeai-launcher.sh" in "etc/init.d/",

ls /etc/init.d

Did you faced this issue on your side?

Thanks,

Ahmed

+1 Diwakar Dhyani over 1 year ago in reply to Ahmed Mujtaba

TI__Guru 56925 points

Hi Ahmed

I dont deal with the edgeai

If you havent changed the rootfs you should not see this kind of issue probably you have changed your rootfs .

Regards
Diwakar

Processors

Processors forum

PROCESSOR-SDK-J721S2: Enable USB 2.0 Hub on J721EXCP01EVM