• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 186 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.

J784S4XEVM: FPS 0 in app single cam

DARSHAN S
Prodigy 50 points

Part Number: J784S4XEVM

Hi team ,

We have bring up a sensor  and we are trying to run the app single cam but we are getting zero fps , we tried debugging the loop inside app_run_graph the loop only runs for 3 iterations and gets stuck at dq api call, we are able to dump proper raw and yuv frames initially , can you please help us fix this problem.

 

Thanks ,

Darshan S

  • 0
    TI__Mastermind 27440 points

    Hi ,

    Can you share details about your setup and error logs?

    Details to share:

    • What sensor are you using?
    • How many sensors are you using?
    • How are they connected to the EVM? Through the Fusion2 board?

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Prodigy 50 points

    HI Jared,

    sensor - omnivision OX03N10

    we are using one sensor 

    Sensor connected to board using GMSL2  Des -MAX96724 Ser-MAX96717

    We are able to run the camera at 30 fps in one of our application with only the capture node.

    When i disable the viss and display node and keep only capture node the application runs at 30fps. 

    log when running app_single_cam application 

    Querying IMX390-UB953_D3 
      2414.412527 s: ISS: Querying sensor [IMX390-UB953_D3] ... !!!
      2414.412732 s: ISS: Querying sensor [IMX390-UB953_D3] ... Done !!!
      2414.412755 s: ISS: Initializing sensor [IMX390-UB953_D3], doing IM_SENSOR_CMD_PWRON ... !!!
    [MCU2_0]   2414.412638 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_QUERY 
    [MCU2_0]   2414.412638 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_QUERY 
    [MCU2_0]   2414.412668 s: Received Query for IMX390-UB953_D3 
    [MCU2_0]   2414.412668 s: Received Query for IMX390-UB953_D3 
    [MCU2_0]   2414.412806 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_PWRON 
    [MCU2_0]   2414.412806 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_PWRON 
    [MCU2_0]   2414.412831 s: IM_SENSOR_CMD_PWRON : channel_mask = 0x01 
    [MCU2_0]   2414.412831 s: IM_SENSOR_CMD_PWRON : channel_mask = 0x01 
    [MCU2_0]   2414.412856 s: IssSensor_PowerOn : chMask = 1 chId = 0x0 
    [MCU2_0]   2414.412856 s: IssSensor_PowerOn : chMask = 1 chId = 0x0 
    [MCU2_0]   2415.173061 s: [configureI2cAccess] I2C0 current moduleState=1, resetState=0
    [MCU2_0]   2415.173061 s: [configureI2cAccess] I2C0 current moduleState=1, resetState=0
    [MCU2_0]   2415.173155 s: [configureI2cAccess] I2C0 powered on successfully
    [MCU2_0]   2415.173155 s: [configureI2cAccess] I2C0 powered on successfully
    [MCU2_0]   2415.173274 s: [configureI2cAccess] Current FWL: control=0xa, perm[0]=0xd4ffff, start=0x2000000, end=0x2000fff
    [MCU2_0]   2415.173274 s: [configureI2cAccess] Current FWL: control=0xa, perm[0]=0xd4ffff, start=0x2000000, end=0x2000fff
    [MCU2_0]   2415.173386 s: [configureI2cAccess] Firewall configured successfully for I2C0
    [MCU2_0]   2415.173386 s: [configureI2cAccess] Firewall configured successfully for I2C0
    [MCU2_0]   2415.173487 s: [configureI2cAccess] After config FWL: control=0xa, perm[0]=0xd4ffff
    [MCU2_0]   2415.173487 s: [configureI2cAccess] After config FWL: control=0xa, perm[0]=0xd4ffff
    [MCU2_0]   2415.483343 s: 
    [MCU2_0] MAX96724_SetSensorAlias: chId = 0x00
    [MCU2_0]   2415.484011 s: Probing I2C bus 0
    [MCU2_0]   2415.484029 s:      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    [MCU2_0]   2415.484029 s:      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
    [MCU2_0]   2415.484855 s: 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.484855 s: 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.485862 s: 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.485862 s: 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.487116 s: 20: -- -- -- -- -- -- -- -- 28 -- -- -- -- -- 2e -- 
    [MCU2_0]   2415.487116 s: 20: -- -- -- -- -- -- -- -- 28 -- -- -- -- -- 2e -- 
    [MCU2_0]   2415.488243 s: 30: -- -- -- -- -- -- 36 -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.488243 s: 30: -- -- -- -- -- -- 36 -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.489373 s: 40: 40 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.489373 s: 40: 40 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.490624 s: 50: -- -- -- -- 54 -- -- -- -- -- -- -- 5c -- -- -- 
    [MCU2_0]   2415.490624 s: 50: -- -- -- -- 54 -- -- -- -- -- -- -- 5c -- -- -- 
    [MCU2_0]   2415.491628 s: 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.491628 s: 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
    [MCU2_0]   2415.492142 s: 70: -- -- -- -- -- -- -- --                         
    [MCU2_0]   2415.492142 s: 70: -- -- -- -- -- -- -- --                         
    [MCU2_0]   2415.492164 s: Ox03N10_PowerOn : chId = 0x0 
    [MCU2_0]   2415.492164 s: Ox03N10_PowerOn : chId = 0x0 
      2415.555171 s: ISS: Initializing sensor [IMX390-UB953_D3], doing IM_SENSOR_CMD_CONFIG ... !!!
    [MCU2_0]   2415.555240 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_CONFIG 
    [MCU2_0]   2415.555240 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_CONFIG 
    [MCU2_0]   2415.555272 s: Application requested features = 0x138 and sensor_name IMX390-UB953_D3
    [MCU2_0]   2415.555272 s: Application requested features = 0x138 and sensor_name IMX390-UB953_D3
    [MCU2_0]  
    [MCU2_0]   2415.555321 s: Deseralizer Type = 2, Broadcast mode = 0 
    [MCU2_0]   2415.555343 s: IM_SENSOR_CMD_CONFIG channel_mask = 01
    [MCU2_0]   2415.570342 s: OX03N10_Probe SUCCESS : Read expected value 0x58 at chip ID register 0x300a 
    [MCU2_0]   2415.570342 s: OX03N10_Probe SUCCESS : Read expected value 0x58 at chip ID register 0x300a 
    [MCU2_0]   2415.570376 s: Configuring camera # 0 
    [MCU2_0]   2415.570376 s: Configuring camera # 0 
    [MCU2_0]   2415.570407 s: sensor_cfg_script_len : 3902 
    [MCU2_0]   2415.570407 s: sensor_cfg_script_len : 3902 
    [MCU2_0]   2415.642123 s:  Configuring OX03N10 imager 0x36.. Please wait till it finishes 
    [MCU2_0]   2415.642123 s:  Configuring OX03N10 imager 0x36.. Please wait till it finishes 
      2419.793222 s: ISS: Initializing sensor [IMX390-UB953_D3] ... Done !!!
    read_test_image_raw : Unable to open file /vision_apps/test_data/img_test.raw
    app_create_viss : sensor_dcc_id = 390 
    [MCU2_0]   2419.793126 s: IM_SENSOR_CMD_CONFIG returning status = 0
    [MCU2_0]   2419.793126 s: IM_SENSOR_CMD_CONFIG returning status = 0
    Scaler is enabled
      2419.815334 s: ISS: Starting sensor [IMX390-UB953_D3] ... !!!
    [MCU2_0]   2419.815452 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_STREAM_ON 
    [MCU2_0]   2419.815452 s: ImageSensor_RemoteServiceHandler: IM_SENSOR_CMD_STREAM_ON 
    [MCU2_0]   2419.815515 s: IM_SENSOR_CMD_STREAM_ON:  channel_mask = 0x01
    [MCU2_0]   2419.815515 s: IM_SENSOR_CMD_STREAM_ON:  channel_mask = 0x01
      2419.825003 s: ISS: Starting sensor [IMX390-UB953_D3] ... Done !!!

    Best regards,

    Darshan S

  • 0 in reply to DARSHAN S
    TI__Mastermind 27440 points

    Hi ,

    Can you send the raw image file and its parameters (resolution, datatype, etc)? I would like to check to see if the image is coming out properly.

    DARSHAN S said:
      2419.815334 s: ISS: Starting sensor [IMX390-UB953_D3] ... !!!

    Why do your logs say this?

    Do you have a DCC file for your sensor?

    Best,
    Jared

  • 0 in reply to Jared McArthur
    Prodigy 50 points

    raw_yuv_images.zip

    Hi Jared ,

    We have generated dcc bins for our sensor now and running it ,earlier we were using imx390 default bins , the issue still exists .

    res-1920*1538(2 lines embedded data)

    16 bit image

    I have attached the raw and yuv dump.

    Thanks,

    Darshan S

  • 0 in reply to DARSHAN S
    TI__Mastermind 24920 points

    Hi Darshan,

    You cannot use imx390 bins for your custom sensor, and have you generated the dcc files for your sensor and validated those.

    The pipeline hang would be because the viss node would have hang because of wrong dcc config, and in the logs i am seeing IMX390-UB953_D3 getting configured, for your sensor you might have modified the driver, have you not changed the name there.

    https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j721s2/10_01_00_04/exports/docs/psdk_rtos/docs/user_guide/developer_notes_image_sensor.html

    DARSHAN S said:
    We have generated dcc bins for our sensor now and running it ,

    How did you generate it and have you validated that. If it is validated  then check the correct dcc values are applied to viss node and aewb node and ldc node (if used).

    Regards,
    Gokul

  • 0 in reply to Gokul S
    Prodigy 50 points

    Hi Gokul ,

    We have generated the dcc bins using the tool available in imaging/tools directory and it is validated by our isp team .

    we have changed the name in driver as well .

    LDC we are not using .

    The issue still exists , is there any way to debug this ?

    Thanks,

    Darshan S

  • 0 in reply to DARSHAN S
    TI__Mastermind 24920 points

    Hi Darshan,

    DARSHAN S said:
    LDC we are not using .

    ok.

    DARSHAN S said:
    The issue still exists , is there any way to debug this ?

    First confirm which node is blocked can you enable info logs on both a72 and mcu2_0 core and run the application, and share the logs.

    Second, add print statements to the viss and aewb node's process callback in the entry and exit and we can confirm which node has entered process callback and have not exited. I am mostly suspecting viss node, because there is a chance when the input image resolution does not match with the dcc configuration viss could hang.

    Let's first find which node is blocking the pipeline

    Regards,
    Gokul