TDA4VEN-Q1: single camera app with fusion2 board does not work

Hi Mahipal Reddy Patlolla,

Can you send your error messages?

Did you execute the gpioset command on target?

How is the Fusion 2 board connected to the J722S EVM?

Best,
Jared

single-cam-failure-errors-log.txt

Fusion2 is connected directly to the EVK which is option 3 in the reference e2e thread,  camera is connected to J4(CAM1) port of Fusion2 board.

Executed the followng commands:

cd /opt/vision_apps
source ./vision_apps_init.sh
gpioset -c gpiochip2 68=1 &
./run_app_single_cam.sh

Then i input 0,,1,1 for the prompts on the terminal as shown below

Select camera port index 0-7 : 0
Select a sensor above or press '0' to autodetect the sensor : a
Sensor selected : IMX390-UB953_D3
LDC Selection Yes(1)/No(0) : LDC Selection Yes(1)/No(0) : 1
CAC Selection Yes(1)/No(0) : CAC Selection Yes(1)/No(0) : 1

Hi Mahipal Reddy Patlolla,

The fusion board appears to be coming up properly. The issue has something to do with the camera sensor.

Can you make sure that you are plugging the camera into the first camera port?

Can you test a different FPDLink cable?

Best,
Jared

Hi Jared McArthur 

Used new Fakra cable, I see the same errors.can we have a call ? mpatloll@visteon.com

I am available from 1:30pm to 4pm EST.

Regards

Mahipal

These are the D3 cameras that we got, are they supposed to work straight away with TDA4VEN EVK+ Fuson2 Board ? 

Here is the image of the setup, camera is connected to the port CAM1(J4) of Fusion2 Board

Hi Mahipal Reddy Patlolla,

Mahipal Reddy Patlolla said:

Used new Fakra cable, I see the same errors.can we have a call ? mpatloll@visteon.com

There is no need for a call. The issue is likely somewhere in the hardware. Can you hold your hand near the board when the board is powered on to see if it's warm? If it's not, you may need to remove the fuse and supply power externally.

Mahipal Reddy Patlolla said:

These are the D3 cameras that we got, are they supposed to work straight away with TDA4VEN EVK+ Fuson2 Board ? 

We have tested and verified this camera module: https://www.d3embedded.com/product/designcore-d3rcm-imx390-953-rugged-camera-module/ 

This camera module works out of box with the SDK.

Best,
Jared

Hi Jared McArthur 

Both EVK and Fusion2 boards are warm

Hi Mahipal Reddy Patlolla,

The IMX390 module that you have is not the same as the module we support in the SDK. Can you get the version supported by the SDK or contact D3 to see if there is a difference between the two?

Best,
Jared

Hi Mahipal Reddy Patlolla,

Actually, we do support the https://www.d3embedded.com/product-category/camera-modules/?fwp_platform=texas-instruments&fwp_series=discovery modules as well. Does the module fall under this?

If so, you should change which sensor you are selecting.

All supported modules are listed here: https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/11_02_01_03/exports/docs/imaging/imaging_release_notes.html 

Best,
Jared

Hi Jared McArthur 

Yes, 3rd one in the list is what we have except that ours is 174FOV instead of 180 FOV

D3CMC70N-106-085, I hve this same SKU on the camera which s there on the 3rd one in the list at https://www.d3embedded.com/product-category/camera-modules/?fwp_platform=texas-instruments&fwp_series=discovery

For D3CMC70N-106-085 camera, which sensor do  need to select n the prompt ?

I do not see D3CMC70N-106-085 camera in  https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/11_02_01_03/exports/docs/imaging/imaging_release_notes.html,
is D3CMC70N-106-085 supposed to work out of the box wth TDA4VEN+Fusion2?

Hi Mahipal Reddy Patlolla,

Yes, that should be the IMX390-UB953-DISCOVERY-WIDE.

You could also try auto-detecting the sensor.

Best,
Jared

single-cam-failure-errors-log-IMX390-UB953-DISCOVERY-WIDE.txt

I see following errors with IMX390-UB953-DISCOVERY-WIDE, also attached the full terminal log.

Enter Choice: [MCU2_0] 145.866716 s: Error : I2C Timeout while writing 0x0 to IMX390 register 0x0
145.972844 s: ISS: Starting sensor [IMX390-UB953-DISCOVERY-WIDE] failed !!!
Failed to start sensor IMX390-UB953-DISCOVERY-WIDE
Defaulting to file test mode
145.973221 s: get_dcc_dir_size : Could not open directory or directory is empty /opt/vision_apps/dcc/IMX390-UB953-DISCOVERY-WIDE/wdr
[MCU2_0] 145.972678 s: Error : Failed to start sensor at channel Id 5
[MCU2_0] 146.472721 s: RTOS DPL ERROR: Semaphore wait failed. Timeout expired.
[MCU2_0] 146.505725 s: RTOS DPL ERROR: Semaphore wait failed. Timeout expired.
[MCU2_0] 146.538727 s: RTOS DPL ERROR: Semaphore wait failed. Timeout expired.
[MCU2_0] 146.571733 s: RTOS DPL ERROR: Semaphore wait failed. Timeout expired.

Hi Mahipal Reddy Patlolla,

Can you try auto-detecting the sensor?

Best,
Jared

Hi Jared McArthur 

Thank You.

With auto detect, port selected as 0, it is detecting s IMX390-UB953-DISCOVERY-NARROW, not sure why narrow, it is wide angle lens, but anyways I am able to dump the images viss, ldc, msc etc

How can i pull the files from the board or push the files to the board over USB or ethernet ? I had to remove the sd card and connect to PC to get the dumped files.

Regards

Mahipal

Hi Mahipal Reddy Patlolla,

Mahipal Reddy Patlolla said:

With auto detect, port selected as 0, it is detecting s IMX390-UB953-DISCOVERY-NARROW, not sure why narrow, it is wide angle lens, but anyways I am able to dump the images viss, ldc, msc etc

Looking at the driver, there should be no difference in the "power on" function between the two drivers. It likely detects discovery narrow because the module ID and camera ID are the same between all three modules (narrow, mid, wide) and it iterates through narrow first.

Mahipal Reddy Patlolla said:

How can i pull the files from the board or push the files to the board over USB or ethernet ? I had to remove the sd card and connect to PC to get the dumped files.

Can you open a new thread for this question? It is not relevant to the current thread.

Best,
Jared