• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Subscribers 100 subscribers
  • Views 951 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Some questions on TDA4 board and DCC

wang zhili
Intellectual 875 points
Part Number: TDA4VM

Hello,

I encountered some problems when I use TDA4 board for ISP tuning, the SDK version used in board is 7.02, The problem is described as follows:

1. When I save images on DCC 2.02, the error below will show up, and failed to save images,

the connection of board and PC is checked OK, as shown in figures below, the board can be pinged successfully through Ethernet,

      

Can you give me some help about this? Is it the DCC problem or the SDK code needs to be changed?

2. The image displayed in LCD Monitor through DP line is only a quarter of the original image of the sensor, the resolution of the screen is 1920*1080 while the resolution of sensor image is 3848*2168, how can the screen completely display the camera image? Can this be achieved by changing the SDK code part?

  • 0
    TI__Mastermind 24525 points

    1. Which app is being run on the EVM when you attempt RAW/YUV capture? Please ensure that you are running app_single_cam

    2. RTOS does not have support for 4K display. Therefore VISS output is downscaled to 1920x1080 for display.

  • 0 in reply to Mayank Mangla
    Intellectual 875 points

    The app I run is app_multi_cam, is this app not supporting the use of DCC to capture images?

    Can the sensor image be scaled in the SDK code before be displayed?

  • 0 in reply to Mayank Mangla
    Intellectual 875 points

    And when I run app_single_cam, the image shown in monitor is wrong, there is nothing but full of color stripes. Is there a problem with the app_single_cam configuration?

  • 0 in reply to wang zhili
    TI__Mastermind 24525 points

    app_multi_cam does not have support for Live Tuning, needed for runtime interaction with DCC Tuning Tool. Please use app_single_cam.

    Can you please share the image you see with app_single_cam? If you can capture RAW and YUV image from tuning tool, please share those. Also list the steps you use - sensor, LDC selection etc.

  • 0 in reply to Mayank Mangla
    Intellectual 875 points

    Thanks for your reply.

    The image of app_single_cam I saw on the monitor is shown below:

    while the image of app_multi_cam I saw on the monitor is shown below:

    but the YUV image saved from the board use app_multi_cam is bigger than the image on the monitor, the YUV/RAW images save from the board are uploaded below:

    YUV&RAW images.zip

    You can see  the steps I use (sensor, LDC selection) in the log files below:

     

    Log_app-single-cam_app-multi-cam.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    root@TDA4-Borad:/opt/vision_apps# ./run_app_single_cam.sh
    APP: Init ... !!!
    MEM: Init ... !!!
    MEM: Initialized DMA HEAP (fd=4) !!!
    MEM: Init ... Done !!!
    IPC: Init ... !!!
    IPC: Init ... Done !!!
    REMOTE_SERVICE: Init ... !!!
    REMOTE_SERVICE: Init ... Done !!!
    APP: Init ... Done !!!
    175.042204 s: VX_ZONE_INIT:Enabled
    175.042213 s: VX_ZONE_ERROR:Enabled
    175.042217 s: VX_ZONE_WARNING:Enabled
    175.042682 s: VX_ZONE_INIT:[tivxInit:71] Initialization Done !!!
    175.042882 s: VX_ZONE_INIT:[tivxHostInit:48] Initialization Done for HOST !!!
    sensor_selection = [0]
    ldc_enable = [0]
    num_frames_to_run = [1000000000]
    is_interactive = [1]
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Log_vision-apps-init_app-single-cam_app-multi-cam.txt

    If you find anything from these documents, please let me know in time, I will appreciate it.

  • 0 in reply to wang zhili
    TI__Mastermind 24525 points

    VISS output from app_single_cam is correct. The issue is that MSC tries to downscale it to 1920x1080, but max downscale possible is 4x. 3848x2168 exceeds this ratio. It seems like app_multi_cam is displaying the image without downscale, therefore it looks correct but only top-left quarter of the image is displayed.

    Is it possible to configure the sensor as 3840x2160? If you can do this, app_single_cam will display correctly scaled full screen image.

  • 0 in reply to Mayank Mangla
    Intellectual 875 points

    Okay, I understand now, thanks.
    I will try to configure the sensor to 3840*2160 to see if it can be displayed normally on the screen.

    One more thing, can the problem of app_single_cam not displaying images normally be located because the sensor driver configuration is incorrect?

  • 0 in reply to wang zhili
    TI__Mastermind 24525 points

    sensor driver configuration is not incorrect, but it is slightly higher than 4x of max display resolution (1920x1080).

  • 0 in reply to Mayank Mangla
    Intellectual 875 points

    Yes, I understand that the image from app_multi_cam is not fully displayed on the screen because of the ratio problem, but the image from app_single_cam is abnormal. I think this may be related to the sensor configuration.

    I think the ratio problem will only affect the display on the screen. The image saved on the board from app_single_cam should be normal. Isn't this problem caused by the sensor configuration? Or can you give some suggestions on the possible causes of this problem? 

  • 0 in reply to wang zhili
    TI__Mastermind 24525 points

    ISP output image saved from the board is correct. Please see attached

    Your sensor configuration is fine. The issue is with display.

  • 0 in reply to Mayank Mangla
    Intellectual 875 points

    Is the file you opened img_viss_0000_Ch00.yuv or img_viss 0000.yuv?

    The image files img_viss_0000_Ch00.yuv and img_ldc_0000_Ch00.yuv were saved by app_multi_cam, we can see normal images after opening img_viss_0000_Ch00.yuv, as shown in your reply.

    The other five files were saved by app_single_cam, the image we seen is abnormal after opening img_viss_0000.yuv (or img_0000.raw), as shown below:

    I think this may be related to the configuration of the sensor. What do you think about this problem?

  • 0 in reply to wang zhili
    TI__Mastermind 24525 points

    I see the issue. Sensor configuration is the same through both the apps. The only difference is that app_single_cam checks if a 60fps mode is supported by the driver and enables it by default if the driver supports. You can disable that by removing the following code in app_single_cam_main.c


    if(ISS_SENSOR_FEATURE_CFG_UC1 == (sensor_features_supported & ISS_SENSOR_FEATURE_CFG_UC1))
    {
    APP_PRINTF("CMS Usecase is supported \n");
    sensor_features_enabled |= ISS_SENSOR_FEATURE_CFG_UC1;
    }

    After this change, sensor configuration is guaranteed to be the same between the two apps.

  • 0 in reply to Mayank Mangla
    Intellectual 875 points

    Okay, I get it, thanks.

    I will try this method to see if this is the reason for the abnormal output of app_single_cam.

  • 0 in reply to Mayank Mangla
    Intellectual 875 points

    Hi, I have a question to ask you after I changed to a newer tda4 board:

    When I run the app "vision_apps_init.sh", there is an error keeps appearing: EnetPhy_enableState: PHY 0: no supported caps found; EnetPhy_enableState: PHY 3: no supported caps found.

    There are the app and log:

    vision_apps_init.sh.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    export VX_TEST_DATA_PATH=/opt/vision_apps/test_data
    # Location of DLR library
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib:/usr/lib/python3.8/site-packages/dlr
    # Location of the input data for PTK demos
    export TIAP_DATABASE_PATH=/opt/vision_apps/test_data_ptk
    # Location of the input data for Stereo demo
    export APP_STEREO_DATA_PATH=$VX_TEST_DATA_PATH/psdkra/stereo_test_data
    # APP config path for PTK demos
    export APP_CONFIG_BASE_PATH=/opt/vision_apps/ptk_app_cfg
    /opt/vision_apps/vx_app_arm_remote_log.out &
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    2656.Logs.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    root@TDA4-Board:/opt/vision_apps# source ./vision_apps_init.sh
    root@TDA4-Board:/opt/vision_apps# [MCU2_0] 3.583914 s: CIO: Init ... Done !!!
    [MCU2_0] 3.583995 s: ### CPU Frequency <ORG = 1000000000 Hz>, <NEW = 1000000000 Hz>
    [MCU2_0] 3.584042 s: APP: Init ... !!!
    [MCU2_0] 3.584063 s: SCICLIENT: Init ... !!!
    [MCU2_0] 3.585223 s: SCICLIENT: DMSC FW version [20.8.5--v2020.08b (Terrific Lla]
    [MCU2_0] 3.585276 s: SCICLIENT: DMSC FW revision 0x14
    [MCU2_0] 3.585304 s: SCICLIENT: DMSC FW ABI revision 3.1
    [MCU2_0] 3.585329 s: SCICLIENT: Init ... Done !!!
    [MCU2_0] 3.585350 s: UDMA: Init ... !!!
    [MCU2_0] 3.595314 s: UDMA: Init ... Done !!!
    [MCU2_0] 3.595371 s: MEM: Init ... !!!
    [MCU2_0] 3.595412 s: MEM: Created heap (DDR_SHARED_MEM, id=0, flags=0x00000004) @ e1000000 of size 16777216 bytes !!!
    [MCU2_0] 3.595472 s: MEM: Created heap (L3_MEM, id=1, flags=0x00000000) @ 3600000 of size 131072 bytes !!!
    [MCU2_0] 3.595522 s: MEM: Created heap (DDR_NON_CACHE_ME, id=5, flags=0x00000000) @ d8000000 of size 16777216 bytes !!!
    [MCU2_0] 3.595570 s: MEM: Init ... Done !!!
    [MCU2_0] 3.595590 s: IPC: Init ... !!!
    [MCU2_0] 3.595625 s: IPC: 6 CPUs participating in IPC !!!
    [MCU2_0] 3.595661 s: IPC: Waiting for HLOS to be ready ... !!!
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Do you know what make this error happen?

  • +1 in reply to wang zhili
    TI__Mastermind 24525 points

    I suggest creating new threads for new questions. Let's close this thread and create another one for  EnetPhy errors.

    Regards,

    Mayank