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: Single camera debugging issue

Part Number: TDA4VM

Hi team,

Here's an issue from the customer may need your help:

Debugging new cameras on the tda4evm platform, camera data goes through serializer max96705-> deserializer max9286-> tda4. Camera resolution: 1344 X 968, output data format: Raw12.

The data in the raw12 format output of the deserializer max9286 is generally OK, but the picture exception output to the display via the mipi port is handled by tda4, which is significantly different from the actual scene. The application refers to the single camera operation example vx_app_single_cam.out (Software-dl.ti.com/...iss_sensor_raw_testpat.h), with resolution set to 3840 X 2160, results in the picture output to the screen via the mipi port at this time overlapping and significantly different from the actual scene.

However, when the demo is modified to a resolution of 1344 X 968 and the application is run again, no data output (suspect the display node has no data update) is present, then input p prints the information, showing: PERF: Total: 0. 0 FPS.

Requirements: the customer want to modify parameters such as the resolution of the demo to properly display the raw12 data image of the new camera with resolution 1344 X 968 on the screen via the mipi port, based on the existing demo. How to implement it?

Could you help check this case? Thanks.

Best Regards,

Cherry

  • Hi,

    However, when the demo is modified to a resolution of 1344 X 968 and the application is run again, no data output (suspect the display node has no data update) is present, then input p prints the information, showing: PERF: Total: 0. 0 FPS.

    When any data output is on the display, the information about the cpu that is printed using the p instruction after running the application is as follows:

    ==========================
    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: p


    Summary of CPU load,
    ====================

    CPU: mpu1_0: TOTAL LOAD = 0.28 % ( HWI = 0. 4 %, SWI = 0. 0 % )
    CPU: mcu2_0: TOTAL LOAD = 42949260.96 % ( HWI = 0. 0 %, SWI = 0. 0 % )
    CPU: mcu2_1: TOTAL LOAD = 42937414.96 % ( HWI = 0. 0 %, SWI = 0. 0 % )
    CPU: c6x_1: TOTAL LOAD = 0. 5 % ( HWI = 0. 2 %, SWI = 0. 1 % )
    CPU: c6x_2: TOTAL LOAD = 0. 5 % ( HWI = 0. 2 %, SWI = 0. 1 % )
    CPU: c7x_1: TOTAL LOAD = 0. 7 % ( HWI = 0. 3 %, SWI = 0. 2 % )


    HWA performance statistics,
    ===========================

    DDR performance statistics,
    ===========================

    DDR: READ BW: AVG = 0 MB/s, PEAK = 0 MB/s
    DDR: WRITE BW: AVG = 0 MB/s, PEAK = 0 MB/s
    DDR: TOTAL BW: AVG = 0 MB/s, PEAK = 0 MB/s


    Detailed CPU performance/memory statistics,
    ===========================================

    CPU: mcu2_0: TASK: IPC_RX: 0. 0 %
    CPU: mcu2_0: TASK: REMOTE_SRV: 19.23 %
    CPU: mcu2_0: TASK: LOAD_TEST: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_CPU: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_NF: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_LDC1: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_MSC1: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_MSC2: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_VISS1: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_CAPT1: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_CAPT2: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_DISP1: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_DISP2: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_CSITX: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_CAPT3: 0. 0 %
    CPU: mcu2_0: TASK: TIVX_CAPT4: 0. 0 %

    CPU: mcu2_0: HEAP: DDR_SHARED_MEM: size = 16777216 B, free = 16273664 B ( 96 % unused)
    CPU: mcu2_0: HEAP: L3_MEM: size = 262144 B, free = 261888 B ( 99 % unused)
    CPU: mcu2_0: HEAP: DDR_NON_CACHE_M: size = 16777216 B, free = 16776960 B ( 99 % unused)

    CPU: mcu2_1: TASK: IPC_RX: 0. 0 %
    CPU: mcu2_1: TASK: REMOTE_SRV: 5.76 %
    CPU: mcu2_1: TASK: LOAD_TEST: 0. 0 %
    CPU: mcu2_1: TASK: TIVX_SDE: 0. 0 %
    CPU: mcu2_1: TASK: TIVX_DOF: 0. 0 %
    CPU: mcu2_1: TASK: IPC_TEST_RX: 0. 0 %
    CPU: mcu2_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: mcu2_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: mcu2_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: mcu2_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: mcu2_1: TASK: IPC_TEST_TX: 0. 0 %

    CPU: mcu2_1: HEAP: DDR_SHARED_MEM: size = 16777216 B, free = 16773376 B ( 99 % unused)
    CPU: mcu2_1: HEAP: L3_MEM: size = 262144 B, free = 262144 B (100 % unused)
    CPU: mcu2_1: HEAP: DDR_NON_CACHE_M: size = 117440512 B, free = 117440256 B ( 26 % unused)

    CPU: c6x_1: TASK: IPC_RX: 0. 0 %
    CPU: c6x_1: TASK: REMOTE_SRV: 0. 0 %
    CPU: c6x_1: TASK: LOAD_TEST: 0. 0 %
    CPU: c6x_1: TASK: TIVX_CPU: 0. 0 %
    CPU: c6x_1: TASK: IPC_TEST_RX: 0. 0 %
    CPU: c6x_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c6x_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c6x_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c6x_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c6x_1: TASK: IPC_TEST_TX: 0. 0 %

    CPU: c6x_1: HEAP: DDR_SHARED_MEM: size = 16777216 B, free = 16774912 B ( 99 % unused)
    CPU: c6x_1: HEAP: L2_MEM: size = 229376 B, free = 229376 B (100 % unused)
    CPU: c6x_1: HEAP: DDR_SCRATCH_MEM: size = 50331648 B, free = 50331648 B ( 14 % unused)

    CPU: c6x_2: TASK: IPC_RX: 0. 0 %
    CPU: c6x_2: TASK: REMOTE_SRV: 0. 0 %
    CPU: c6x_2: TASK: LOAD_TEST: 0. 0 %
    CPU: c6x_2: TASK: TIVX_CPU: 0. 0 %
    CPU: c6x_2: TASK: IPC_TEST_RX: 0. 0 %
    CPU: c6x_2: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c6x_2: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c6x_2: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c6x_2: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c6x_2: TASK: IPC_TEST_TX: 0. 0 %

    CPU: c6x_2: HEAP: DDR_SHARED_MEM: size = 16777216 B, free = 16774912 B ( 99 % unused)
    CPU: c6x_2: HEAP: L2_MEM: size = 229376 B, free = 229376 B (100 % unused)
    CPU: c6x_2: HEAP: DDR_SCRATCH_MEM: size = 50331648 B, free = 50331648 B ( 14 % unused)

    CPU: c7x_1: TASK: IPC_RX: 0. 0 %
    CPU: c7x_1: TASK: REMOTE_SRV: 0. 0 %
    CPU: c7x_1: TASK: LOAD_TEST: 0. 0 %
    CPU: c7x_1: TASK: TIVX_CPU: 0. 0 %
    CPU: c7x_1: TASK: IPC_TEST_RX: 0. 0 %
    CPU: c7x_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c7x_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c7x_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c7x_1: TASK: IPC_TEST_TX: 0. 0 %
    CPU: c7x_1: TASK: IPC_TEST_TX: 0. 0 %

    CPU: c7x_1: HEAP: DDR_SHARED_MEM: size = 268435456 B, free = 268435456 B ( 4 % unused)
    CPU: c7x_1: HEAP: L3_MEM: size = 8159232 B, free = 8159232 B (100 % unused)
    CPU: c7x_1: HEAP: L2_MEM: size = 491520 B, free = 491520 B (100 % unused)
    CPU: c7x_1: HEAP: L1_MEM: size = 16384 B, free = 16384 B (100 % unused)
    CPU: c7x_1: HEAP: DDR_SCRATCH_MEM: size = 268435456 B, free = 268435456 B ( 4 % unused)


    GRAPH: graph_84 (#nodes = 6, #executions = 0)
    NODE: CAPTURE2: node_95: avg = 0 usecs, min/max = 18446744073709551 / 0 usecs, #executions = 0
    NODE: VPAC_VISS1: VISS_Processing: avg = 0 usecs, min/max = 18446744073709551 / 0 usecs, #executions = 0
    NODE: IPU1-0: 2A_AlgNode: avg = 0 usecs, min/max = 18446744073709551 / 0 usecs, #executions = 0
    NODE: VPAC_LDC1: node_110: avg = 0 usecs, min/max = 18446744073709551 / 0 usecs, #executions = 0
    NODE: VPAC_MSC1: node_112: avg = 0 usecs, min/max = 18446744073709551 / 0 usecs, #executions = 0
    NODE: DISPLAY1: node_114: avg = 0 usecs, min/max = 18446744073709551 / 0 usecs, #executions = 0

    PERF: TOTAL: avg = 0 usecs, min/max = 4294967295 / 0 usecs, #executions = 0

    PERF: TOTAL: 0. 0 FPS

    Thanks and regards,

    Cherry

  • Hi,

    May I know is there any updates?

    Thanks and regards,

    Cherry

  • Hi Cherry,

    For the resolution 3840 X 2160, you had said that there is overlap in the images,
    Could you provide a dump from the capture output? we could check if this is there right from the capture output.

    Could you also please share the logs of "source ./vision_apps_init.sh"  and the application logs for the demo you are running?

    Regards,
    Nikhil