Linux: Can't run apps.out VSDK_3.03

Nevena Stojanovic

Intellectual 540 points

Tool/software: Linux

Hello,

When I run ./apps.out on VSDK_3.03 it get stuck when System A15 Init is in progress. Any suggestions how to solve this?

Regards,

Nevena Stojanovic

over 7 years ago

0 Shiju Sivasankaran over 7 years ago

TI__Genius 13395 points

Hello

Can you please make sure you follow the user guide \vision_sdk\docs\Linux\VisionSDK_Linux_UserGuide.pdf to build and run VSDK demos?

i could see some errors with ./vision_sdk_load.sh command

BTW, did you make any changes on top of VSDK 3.3 release?

regards, Shiju

0 Shravan Karthik over 7 years ago

TI__Genius 14650 points

Hi Navena,

Can you confirm which board you're running the VSDK application? Also, are you observing this on every boot?
Are you using the early-boot + late-attach feature on VSDK? If not what can you paste your the contents of the uenv.txt file (present in the boot (FAT32) partition of your SD card).

Can you run the below commands on the board and paste the output?
cat /sys/kernel/debug/remoteproc/remoteproc*/name
cat /sys/kernel/debug/remoteproc/remoteproc*/state
cat /sys/kernel/debug/remoteproc/remoteproc*/trace0

Regards
Shravan

0 Nevena Stojanovic over 7 years ago in reply to Shravan Karthik

Intellectual 540 points

Hi, I am using custom tda2xx board. I am not using early-boot+late-attach feature on VSDK and we are observing this issue on every boot.

Here you have uenv.txt file :

Fullscreen 7713.uenv.txt Download

fdtfile=alpha_amv_board.dtb
args_mmc=part uuid mmc 0:2 uuid; setenv bootargs "console=ttyS0,115200n8 vram=16M root=PARTUUID=${uuid} rw rootwait ip=none mem=1024M"

Also, I tried to run commands as you suggessted but seems like I don't have remoteproc folder under debug :

I don't have any issues with VSDK_3.02 only with VSDK_3.03.

0 Shravan Karthik over 7 years ago in reply to Nevena Stojanovic

TI__Genius 14650 points

Hi,

Please apply the patch attached on the linux kernel and rebuild (make linux, make linux_install). It should resolve the issue.

Regards

Shravan

Fullscreen 1157.0001-arm-dts-Update-timer-entries-for-remote-cores.patch.txt Download

From 3fecdc0c83e9d001ccad6baecbfae06a625824d2 Mon Sep 17 00:00:00 2001
From: Shravan Karthik <shravan.karthik@ti.com>
Date: Mon, 9 Apr 2018 17:39:57 +0530
Subject: [PATCH] arm: dts: Update timer entries for remote-cores

VSDK firmwares use the following timers:
IPU-1 -- timer9, timer11
IPU-2 -- timer9, timer11
DSP-1 -- timer5, timer6
DSP-2 -- timer5, timer6

By default on Processor-SDK Linux Automotive IPU-2 binaries use timer3.
Since ipu1 is disabled for all infoadas builds an explicit entry for both
timer9 and timer11 must be specified.
In DRA75x and DRA76x since both DSPs are used no additional changes are needed,
however for DRA72x and DRA71x where only 1 DSP is available, timer5, timer6
entries are specified.

Signed-off-by: Shravan Karthik <shravan.karthik@ti.com>
---
 arch/arm/boot/dts/dra7-evm-infoadas.dts  | 1 +
 arch/arm/boot/dts/dra71-evm-infoadas.dts | 2 ++
 arch/arm/boot/dts/dra72-evm-infoadas.dts | 2 ++
 arch/arm/boot/dts/dra76-evm-infoadas.dts | 1 +
 4 files changed, 6 insertions(+)

diff --git a/arch/arm/boot/dts/dra7-evm-infoadas.dts b/arch/arm/boot/dts/dra7-evm-infoadas.dts
index 83fed99..26ece53 100755
--- a/arch/arm/boot/dts/dra7-evm-infoadas.dts
+++ b/arch/arm/boot/dts/dra7-evm-infoadas.dts
@@ -96,6 +96,7 @@ DISABLE_PRCM(gpio6);
 
 &ipu2 {
 	/delete-property/ watchdog-timers;
+  timers= <&timer9> , <&timer11>;
 };
 
 &dsp1 {
diff --git a/arch/arm/boot/dts/dra71-evm-infoadas.dts b/arch/arm/boot/dts/dra71-evm-infoadas.dts
index bc4496e..8da3da1 100755
--- a/arch/arm/boot/dts/dra71-evm-infoadas.dts
+++ b/arch/arm/boot/dts/dra71-evm-infoadas.dts
@@ -85,8 +85,10 @@ DISABLE_PRCM(gpio6);
 
 &ipu2 {
 	/delete-property/ watchdog-timers;
+  timers= <&timer9> , <&timer11>;
 };
 
 &dsp1 {
 	/delete-property/ watchdog-timers;
+  timers= <&timer5> , <&timer6>;
 };
diff --git a/arch/arm/boot/dts/dra72-evm-infoadas.dts b/arch/arm/boot/dts/dra72-evm-infoadas.dts
index 5d7123a..ed39adc 100755
--- a/arch/arm/boot/dts/dra72-evm-infoadas.dts
+++ b/arch/arm/boot/dts/dra72-evm-infoadas.dts
@@ -85,8 +85,10 @@ DISABLE_PRCM(gpio6);
 
 &ipu2 {
 	/delete-property/ watchdog-timers;
+  timers= <&timer9> , <&timer11>;
 };
 
 &dsp1 {
 	/delete-property/ watchdog-timers;
+  timers= <&timer5> , <&timer6>;
 };
diff --git a/arch/arm/boot/dts/dra76-evm-infoadas.dts b/arch/arm/boot/dts/dra76-evm-infoadas.dts
index a6358d4..7958e81 100755
--- a/arch/arm/boot/dts/dra76-evm-infoadas.dts
+++ b/arch/arm/boot/dts/dra76-evm-infoadas.dts
@@ -98,6 +98,7 @@ DISABLE_PRCM(gpio6);
 
 &ipu2 {
 	/delete-property/ watchdog-timers;
+  timers= <&timer9> , <&timer11>;
 };
 
 &dsp1 {
-- 
2.7.4

0 Nevena Stojanovic over 7 years ago in reply to Shravan Karthik

Intellectual 540 points

Hi, Shravan

I applied patch on the linux kernel and rebuild with make linux and make linux_install but the issue is not resolved.

0 Shravan Karthik over 7 years ago in reply to Nevena Stojanovic

TI__Genius 14650 points

Hi,

Have you made any changes to VSDK?

Can you post your kernel logs by running dmesg on the target, and attach the DTB you're using.

Regards
Shravan

0 Nevena Stojanovic over 7 years ago in reply to Shravan Karthik

Intellectual 540 points

Hi,

here are all files zipped: 8228.files.zip

I have the same problem with dra7-evm-infoadas.dtb .

Regards.

0 Shravan Karthik over 7 years ago in reply to Nevena Stojanovic

TI__Genius 14650 points

Hi Nevena,

From your logs I can see that there is a miss-match between the kernel module and the image used. Please make sure you follow the below steps (please follow the step-by-step instruction is section-3 of VDSK Linux user-guide)

1. make clean

2. make linux

3. make linux_install

4. make depend

5. make vision_sdk

6. Create updated file system tar ball (step-7 of section 3.1 of VisionSDK_Linux_UserGuide.pdf in vision-SDK docs).

7. mksdboot.sh

You should see Vision-SDK work.

Regards
Shravan

Processors

Processors forum

Linux: Can't run apps.out VSDK_3.03