SK-TDA4VM: SDK8.4 Vision Apps demo for DL + 4 cameras

Please note, this E2E is talking about the TDA4 EVM, not the "SK" EVM, I don't know why the system categories it as SK-TDA4EVM.

Hi Rio,

When choosing a part number when creating a new post for TDA4VM EVM, please use J721EXSOMXEVM from the next post.

As for the TIDL scripts, they should be installed after running the command to build, and then the command to install to SD card. Could you follow the Vision Apps User Guide for those steps: https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/08_04_00_06/exports/docs/vision_apps/docs/user_guide/ENVIRONMENT_SETUP.html

The instructions look to be the same between 8.2 and 8.4 SDK versions.

Regards,

Takuma

Hi Takuma:

it seems this doc only tested with the OV camera:

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

I was able to test the on-Semi AR2033 camera, please see this demo: https://www.youtube.com/watch?v=NjlupEnBfy8

Any procedure I can follow for testing AR2033 caemra?

BR Rio

Hi Takuma:

By reading this: https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-jacinto7/08_04_00_06/exports/docs/vision_apps/docs/user_guide/RUN_INSTRUCTIONS.html

After issuing this cmd:

I have this error:

mkdir -p /media/root/rootfs/usr/include/processor_sdk
# copy full vision apps linux fs stage directory into linux fs
cp -r /tmp/tivision_apps_targetfs_stage/* /media/root/rootfs/.
sync
# copy uEnv.txt and sysfw.itb for PSDK RTOS
cp /opt/ti-processor-sdk-rtos-j721e-evm-08_04_00_06/vision_apps/apps/basic_demos/app_linux_fs_files/uEnv_j721e_vision_apps.txt /media/root/BOOT/
cp: cannot create regular file '/media/root/BOOT/': Not a directory
makerules/makefile_linux_arm.mak:255: recipe for target 'linux_fs_install_sd' failed
make: *** [linux_fs_install_sd] Error 1

My SD card is located with this place:

/media/rio/boot

/media/rio/rootfs

It's not the "root/boot , root/rootfs", where is the place to modify it as "rio"?

BR Rio

okay, I have fixed it thru this file: vision_apps_tools_path.mak

I'm continuing the testing now.

Now, it has this kind of error, it seems the SDK8.4 cannot recognize this AR0233, please tell us how to fix it.

Enter Choice: get_dcc_dir_size : Could not open directory or directory is empty /opt/vision_apps/dcc/AR0233-UB953_MARS/wdr
[MCU2_0] 132.602250 s: Error : Failed to start sensor at channel Id 1
[ 136.208082] Initializing XFRM netlink socket
[ 137.698805] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[ 137.714523] Bridge firewalling registered
[ 138.309924] process 'docker/tmp/qemu-check096467965/check' started with executable stack

TDA4_SDK8.4_With_Onsemi_AR0233_Failed.txt

Hi.

By selecting the port "0"

The log seems be more correct.

However, how to solve those 2 errors:

read_test_image_raw : Unable to open file .//img_test.raw

get_dcc_dir_size : Could not open directory or directory is empty /opt/vision_apps/dcc/AR0233-UB953_MARS/wdr

BR Rio

NETWORK: Opened at IP Addr = 1.4.16.64, socket port=5000!!!
364.434879 s: ISS: Enumerating sensors ... found 0 : IMX390-UB953_D3
364.434930 s: ISS: Enumerating sensors ... found 1 : AR0233-UB953_MARS
364.434936 s: ISS: Enumerating sensors ... found 2 : AR0820-UB953_LI
364.434941 s: ISS: Enumerating sensors ... found 3 : UB9xxx_RAW12_TESTPATTERN
364.434946 s: ISS: Enumerating sensors ... found 4 : UB96x_UYVY_TESTPATTERN
364.434951 s: ISS: Enumerating sensors ... found 5 : GW_AR0233_UYVY
Select camera port index 0-7 : 0
6 registered sensor drivers
a : IMX390-UB953_D3
b : AR0233-UB953_MARS
c : AR0820-UB953_LI
d : UB9xxx_RAW12_TESTPATTERN
e : UB96x_UYVY_TESTPATTERN
f : GW_AR0233_UYVY
Select a sensor above or press '0' to autodetect the sensor : Invalid selection
. Try again
6 registered sensor drivers
a : IMX390-UB953_D3
b : AR0233-UB953_MARS
c : AR0820-UB953_LI
d : UB9xxx_RAW12_TESTPATTERN
e : UB96x_UYVY_TESTPATTERN
f : GW_AR0233_UYVY
Select a sensor above or press '0' to autodetect the sensor : b
Sensor selected : AR0233-UB953_MARS
LDC Selection Yes(1)/No(0) : LDC Selection Yes(1)/No(0) : 0
Querying AR0233-UB953_MARS
371.189499 s: ISS: Querying sensor [AR0233-UB953_MARS] ... !!!
371.189856 s: ISS: Querying sensor [AR0233-UB953_MARS] ... Done !!!
371.189866 s: ISS: Initializing sensor [AR0233-UB953_MARS], doing IM_SENSOR_CMD_PWRON ... !!!
371.190156 s: ISS: Initializing sensor [AR0233-UB953_MARS], doing IM_SENSOR_CMD_CONFIG ... !!!
374.998599 s: ISS: Initializing sensor [AR0233-UB953_MARS] ... Done !!!
Test data path is NULL. Defaulting to current folder
read_test_image_raw : Unable to open file .//img_test.raw
app_create_viss : sensor_dcc_id = 233
Scaler is enabled
375.036681 s: ISS: Starting sensor [AR0233-UB953_MARS] ... !!!

==========================
Demo : Single Camera w/ 2A
==========================

p: Print performance statistics

s: Save Sensor RAW, VISS Output and H3A output images to File System

e: Export performance statistics

u: Update DCC from File System

x: Exit

Enter Choice:
Unsupported command

==========================
Demo : Single Camera w/ 2A
==========================

p: Print performance statistics

s: Save Sensor RAW, VISS Output and H3A output images to File System

e: Export performance statistics

u: Update DCC from File System

x: Exit

Enter Choice: 375.574700 s: ISS: Starting sensor [AR0233-UB953_MARS] ... !!!
get_dcc_dir_size : Could not open directory or directory is empty /opt/vision_apps/dcc/AR0233-UB953_MARS/wdr

Hi Brijesh:

After reviewing the log in detail, I'm pretty sure those files are missing in the SDK8.4.

So, please help to solve this.

Thanks.

BR Rio

read_test_image_raw : Unable to open file .//img_test.raw

get_dcc_dir_size : Could not open directory or directory is empty /opt/vision_apps/dcc/AR0233-UB953_MARS/wdr

Hi Rio Chan,

Do you mean below errors ?

"get_dcc_dir_size : Could not open directory or directory is empty /opt/vision_apps/dcc/AR0233-UB953_MARS/wdr"

You could ignore these errors. These will be used when sensor stops streaming frames..  

These images are available in the test data set, which is available as a separate zip file. You need to copy this test data to the rootfs.

If you have it from previous release, you can continue using the same. 

Regards,

brijesh

Hi Brijesh:

I confirmed the zip file of the dataset/ dataset_ptk has no those files in the current SDK.

Can you ask someone to provide these missing files to us?

THanks.

BR Rio

Hi Rio Chan,

In this case, i would suggest to ignore this error.

The main issue is not file not found in dcc file. but i2c write/read failure, can you check if there is any lock between SERDES? 

Regards,

Brijesh

Hi Brijesh:

Sorry to make you confused.

Please see the attached again.

After I try the correct "camera port" , this log shows " no any i2c errors".

But the error logs of the missing file are remained.

Any suggestion?

BR Rio

TDA4_SDK8.4_With_Onsemi_AR0233_Failed_2.txt

Hi Rio Chan,

But what's the issue now?

Is it error "get_dcc_dir_size : Could not open directory or directory is empty /opt/vision_apps/dcc/AR0233-UB953_MARS/wdr"? Please ignore this error, as it will not affect working of this example.. 

Regards,

Brijesh

Hi Brijesh:

The issue is: I cannot see the Camera preview on the LCD screen thru the DP output.

Any thought?

BR Rio

HI Brijesh:

BTW, I tested with this modified for AR0233.

Please see if my modification is correct as the below.

root@j7-evm:/opt/vision_apps# cat run_app_single_cam.sh
/opt/vision_apps/vx_app_single_cam.out --cfg /opt/vision_apps/app_single_cam.cfgroot@j7-evm:/opt/vision_apps#
root@j7-evm:/opt/vision_apps# cat app_single_cam.cfg

# sensor selection
# 0 : IMX390
# 1 : AR0233
# 2 : AR0820
sensor_index 1

# LDC Enable
ldc_enable 0

# Number of frames to run
num_frames_to_run 1000000000

# enable interactive mode
is_interactive 1
root@j7-evm:/opt/vision_apps#

Hi Brijesh:

Will the EVM version affect this issue?

My EVM is still version 1.0.

BR Rio

Hi Rio Chan,

No EVM version does not affect this example. 

Can you please press 'p' on the console and check the performance stats? 

Also was this demo working fine in earlier release? 

Regards,

Brijesh

Hi Brijesh:

This is the SDK7.1 I did before.

https://www.youtube.com/watch?v=NjlupEnBfy8

I confirm the "p" will show something, but I need to get it again when I'm in the office.

Will provide you tomorrow.

BR Rio

Hi Brijesh:

The attached is the log within the "performance" dump.

plz check.

It seems the camera did act, but the DP LCD screen shows nothing.

BR RIo

TDA4_SDK8.4_With_Onsemi_AR0233_Failed_3_With_Performance_Dump.txt

Hi Rio Chan,

Yes, capture is running fine, frame are being captured at 30fps. 

Which display are you using? Is it eDP display, directly connected to EVM?

Can you please try disabling Ethernet Firmware and check it again? Ethernet Firmware can be disabled by setting flag BUILD_ENABLE_ETHFW to no in vision_apps_build_flags.mk file and rebuilding vision apps ("make vision_apps_clean && make vision_apps")..

Regards,

Brijesh

Hi Brijesh:

Got it, plz wait my testing.

BR Rio

Hi Brijesh:

The method you offered is to use the HDMI, not the DP.

I followed this doc:

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

• In file vision_apps_build_flags.mak, set BUILD_ENABLE_ETHFW?=no
• Run "make vision_apps_scrub" prior to re-building
• Note: Ethernet firmware must be disabled in order to use the HDMI display

So, my question:

   A. Where is the HDMI connector?

   B. if I insist to use the DP port, do I need to disable the ETH in the vision app mk file?

BR Rio

Hi Rio Chan,

This is required, if you have using external DP to HDMI convertor/adaptor. If you are using directly DP display, then it isn't required to disable ethernet firmware. But i still want to check with ethernet firmware disabled. So can you please check it?

Regards,

Brijesh 

Hi Brijesh:

Q1.

The current 8.4 SDK, this flag is "yes", please see the below.

BUILD_ENABLE_ETHFW?=yes

# ETHFW is not supported in J721S2
ifneq (,$(filter $(SOC),j721s2))
BUILD_ENABLE_ETHFW=no
endif

ifeq ($(RTOS),SAFERTOS)
BUILD_ENABLE_ETHFW=no
endif

Q2. I have a question, do I need to chagne this cfg to test AR0233?

root@j7-evm:/opt/vision_apps# cat app_single_cam.cfg

# sensor selection
# 0 : IMX390
# 1 : AR0233
# 2 : AR0820
sensor_index 0

# LDC Enable
ldc_enable 0

# Number of frames to run
num_frames_to_run 1000000000

# enable interactive mode
is_interactive 1
root@j7-evm:/opt/vision_apps#

Q3:

If this ETH disabled is required, but, if the Customer is having their ETH function working right now, how to proceed?

I believe Disable the ETH is not an option.

BR Rio

Hi Rio,

#1, Yes, ethernet functionality is by default enabled in the vision apps.

#2, none, because in interactive mode, you could select the sensor based on the provided menu on the Linux console.

#3, This change is required on the EVM, because there is an external mux which is required for both Ethernet and DP output and which is controlled by common i2c. If customer board does not have this board mux, they dont need to disable ethernet in vision apps. 

Regards,

Brijesh

Hi Brijesh:

I have rebuilt it according your saying:-->

• n file vision_apps_build_flags.mak, set BUILD_ENABLE_ETHFW?=no
• Run "make vision_apps_scrub" prior to re-building

Now, There is no display output while attaching the AR0233, btw, I'm testing with DP display.

So, do you need me to test with the HDMI display?

BR Rio