Part Number: PROCESSOR-SDK-DRA8X
Tool/software: TI C/C++ Compiler
Dear TI
I want to run my own camera in TDA4 (AR0233+GW5200+TI953, Resolution is 1920*1080, The camera produces YUV422 8bit of data), it has ISP in camera module, so I modify [vision_apps\apps\basic_demos\app_single_cam\app_single_cam_main.c], I modify the code and make the openvx_node be capture_node -> display_node, I upload this C file; I also chang the code in (imaging\sensor_drv\src\ar0233), I change the register data of TI953, change the register address of TI953, modify the code in imaging\sensor_drv\src\ar0233\iss_sensor_ar0233.c to disable ar0233.
but when I try to run app_single_cam_main.out,I found that the code has been stuck in the [tiovx\kernels_j7\hwa\capture\vx_capture_target.c: static vx_status VX_CALLBACK tivxCaptureProcess] function, specifically this line of code:[tivxEventWait(prms->frame_available, TIVX_EVENT_TIMEOUT_WAIT_FOREVER);];Later, I traced back to the driver part and found that under normal circumstances, each camera output would trigger an interrupt function of CSIRX driver:[pdk\packages\ti\drv\csirx\src\csirx_drvUdma.c CsirxDrv_udmaCQEventCb];However, this interrupt function is no trigger now, so I printed the relevant register of TI960. I found that the value of the 0x4D register is 0X03, and the registers of 0x73~0x74 also have values (the value of the register of TU960 is below).
so I have three problems:
1. Which step of my code is wrong?
2. I did not change the register Value of TI960, but only changed the two values of TI953 register: [TI953: Address: 0x0d, Value: 0x0f; TI953: Address: 0x0e, Value: 0xf0].
3. Is it true that CSI driver only accepts RAW data and not YUV data from camera ? Do I need to change code in CSI driver ?
[MCU2_1] 355.061868 s: TI960: Address: 0x01, Value: 0x00.
[MCU2_1] 355.071833 s: TI960: Address: 0x0f, Value: 0xff.
[MCU2_1] 355.081811 s: TI960: Address: 0x32, Value: 0x01.
[MCU2_1] 355.091820 s: TI960: Address: 0x33, Value: 0x03.
[MCU2_1] 355.101819 s: TI960: Address: 0x4d, Value: 0x03.
[MCU2_1] 355.111804 s: TI960: Address: 0x5b, Value: 0x30.
[MCU2_1] 355.121818 s: TI960: Address: 0x5c, Value: 0xe8.
[MCU2_1] 355.131801 s: TI960: Address: 0x5d, Value: 0x30.
[MCU2_1] 355.141812 s: TI960: Address: 0x5e, Value: 0x20.
[MCU2_1] 355.151815 s: TI960: Address: 0x65, Value: 0xe8.
[MCU2_1] 355.161803 s: TI960: Address: 0x66, Value: 0x30.
[MCU2_1] 355.171810 s: TI960: Address: 0x6e, Value: 0x88.
[MCU2_1] 355.181807 s: TI960: Address: 0x6f, Value: 0x88.
[MCU2_1] 355.191813 s: TI960: Address: 0x73, Value: 0x04.
[MCU2_1] 355.201814 s: TI960: Address: 0x74, Value: 0x38.
[MCU2_1] 355.211808 s: TI960: Address: 0x75, Value: 0x0f.
[MCU2_1] 355.221816 s: TI960: Address: 0x76, Value: 0x00.
iss_sensor_ar0233.c:
/cfs-file/__key/communityserver-discussions-components-files/791/iss_5F00_sensor_5F00_ar0233.c
app_single_cam_main.c:
/cfs-file/__key/communityserver-discussions-components-files/791/app_5F00_single_5F00_cam_5F00_main.c