• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 229 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TDA4VM: Issue in a new image sensor enabling: white screen displayed

Jungwoo Park
Prodigy 40 points
Part Number: TDA4VM

Hello.

I made a driver to use a custom sensor on J721 board. I used max9295/9296 as ser/des device . However, I have a problem.

 

I use /opt/vision_apps/run_app_single_cam.sh to run the sensor.

The problem is that white screens (or full noise screens) are frequently displayed, not normal screens.

 

I saved a raw file and yuv file with 's' command in app_single_cam when white screen is displayed.

In this case, a raw file shows normal screen. However, a yuv file shows white screen.

 

So I tried not to use isp while deleting all dcc xml and bin files. I also removed DCC use setting in the SENSOR_FEATURES in iss_sensor_xxx.h file.

But the result doesn't change. A normal screen is stored in the raw file, and a white screen is stored in the yuv file.

 

When the white screen is displayed, the log that appears when the program is terminated is as follows.

5117.657561 s: ISS: Stopping sensor [SAMIS-UB971] ... !!!

5117.658282 s: ISS: Stopping sensor [SAMIS-UB971] ... Done !!!

[MCU2_0]   5117.657806 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_STREAM_OFF

[MCU2_0]   5117.657891 s: IM_SENSOR_CMD_STREAM_ON:  channel_mask = 0x1

5117.664978 s: ISS: Stopping sensor [SAMIS-UB971] ... !!!

5117.665594 s: ISS: Stopping sensor [SAMIS-UB971] ... Done !!!

app_run_graph done

releasing capture node

releasing node_viss

releasing node_aewb

releasing displayNode

releasing raw image done

releasing cap_frame # 0

releasing cap_frame # 1

releasing cap_frame # 2

releasing cap_frame # 3

releasing y8_r8_c2

releasing configuration

releasing ae_awb_result done

releasing h3a_aew_af

releasing aewb_config

releasing VISS DCC Data Object

releasing Display Param Data Object

releasing 2A DCC Data Object

releasing test raw image buffer # 3

releasing graph

[MCU2_0]   5117.665182 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_STREAM_OFF

[MCU2_0]   5117.665254 s: IM_SENSOR_CMD_STREAM_ON:  channel_mask = 0x1

[MCU2_0]   5117.668254 s: ==========================================================

[MCU2_0]   5117.668348 s:  Capture Status: Instance|0

[MCU2_0]   5117.668384 s: ==========================================================

[MCU2_0]   5117.668429 s:  overflowCount: 0

[MCU2_0]   5117.668463 s:  spuriousUdmaIntrCount: 0

[MCU2_0]   5117.668498 s:  frontFIFOOvflCount: 0

[MCU2_0]   5117.668528 s:  crcCount: 48

[MCU2_0]   5117.668556 s:  eccCount: 45

[MCU2_0]   5117.668665 s:  correctedEccCount: 55

[MCU2_0]   5117.668708 s:  dataIdErrorCount: 3

[MCU2_0]   5117.668742 s:  invalidAccessCount: 0

[MCU2_0]   5117.668775 s:  invalidSpCount: 0

[MCU2_0]   5117.668812 s:  strmFIFOOvflCount[0]: 407

[MCU2_0]   5117.668850 s:  strmFIFOOvflCount[1]: 808

[MCU2_0]   5117.668879 s:  Channel Num | Frame Queue Count | Frame De-queue Count | Frame Drop Count | Error Frame Count |

[MCU2_0]   5117.668952 s:            0 |                 8 |                    8 |                0 |                 0 |

[MCU2_0]   5117.669758 s: ==========================================================

[MCU2_0]   5117.669847 s:  Capture Status: Instance|1

[MCU2_0]   5117.669883 s: ==========================================================

[MCU2_0]   5117.669929 s:  overflowCount: 0

[MCU2_0]   5117.669962 s:  spuriousUdmaIntrCount: 0

[MCU2_0]   5117.669997 s:  frontFIFOOvflCount: 0

[MCU2_0]   5117.670028 s:  crcCount: 0

[MCU2_0]   5117.670056 s:  eccCount: 0

[MCU2_0]   5117.670085 s:  correctedEccCount: 0

[MCU2_0]   5117.670116 s:  dataIdErrorCount: 0

[MCU2_0]   5117.670147 s:  invalidAccessCount: 0

[MCU2_0]   5117.670179 s:  invalidSpCount: 0

[MCU2_0]   5117.670216 s:  strmFIFOOvflCount[0]: 0

[MCU2_0]   5117.670254 s:  strmFIFOOvflCount[1]: 0

[MCU2_0]   5117.670283 s:  Channel Num | Frame Queue Count | Frame De-queue Count | Frame Drop Count | Error Frame Count |

releasing graph done

app_delete_graph done

tivxHwaUnLoadKernels done

tivxImagingUnLoadKernels done

vxReleaseContext done

app_deinit done

5117.675881 s: ISS: De-initializing sensor [SAMIS-UB971] ... !!!

5117.676226 s: ISS: De-initializing sensor [SAMIS-UB971] ... Done !!!

5117.676242 s:  VX_ZONE_INIT:[tivxHostDeInitLocal:107] De-Initialization Done for HOST !!!

5117.680635 s:  VX_ZONE_INIT:[tivxDeInitLocal:193] De-Initialization Done !!!

APP: Deinit ... !!!

REMOTE_SERVICE: Deinit ... !!!

REMOTE_SERVICE: Deinit ... Done !!!

IPC: Deinit ... !!!

IPC: DeInit ... Done !!!

MEM: Deinit ... !!!

DDR_SHARED_MEM: Alloc's: 20 alloc's of 19429900 bytes

DDR_SHARED_MEM: Free's : 20 free's  of 19429900 bytes

DDR_SHARED_MEM: Open's : 0 allocs  of 0 bytes

DDR_SHARED_MEM: Total size: 536870912 bytes

MEM: Deinit ... Done !!!

APP: Deinit ... Done !!!

root@j7-evm:~#

 

When a normal screen is displayed, all values in 'Capture Status: Instance|0 ' are 0. 

I followed the values in 'Capture Status' and I found that these values are in the csirx driver.

According to error log, it looks like there may be an error in the capture process. But a raw file with error status shows a normal screen.

 

How can I fix this issue? I want to see the normal screen without error.

 

Thanks