• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Subscribers 100 subscribers
  • Views 486 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.

TDA4VH-Q1: Cannot display output from EVM sample apps

Liu Tsing-Yue
Intellectual 291 points
Part Number: TDA4VH-Q1

Hi,

We tried to run sample vision apps (such as single cam app), the apps seemed to be working, but no signal showed up at the monitor (DisplayPort).

The message indicates: DISPLAY: ERROR: Display Create Failed!

What might be the cause of this error?

The RTOS version we're using is 09_00_00_02

Thanks.

here's the log:

11747.682869 s:  VX_ZONE_ERROR:[ownContextSendCmd:822] Command ack message returned failure cmd_status: -1
 11747.682895 s:  VX_ZONE_ERROR:[ownContextSendCmd:862] tivxEventWait() failed.
 11747.682906 s:  VX_ZONE_ERROR:[ownNodeKernelInit:527] Target kernel, TIVX_CMD_NODE_CREATE failed for node node_116
 11747.682914 s:  VX_ZONE_ERROR:[ownNodeKernelInit:528] Please be sure the target callbacks have been registered for this core
 11747.682923 s:  VX_ZONE_ERROR:[ownNodeKernelInit:529] If the target callbacks have been registered, please ensure no errors are occurring within the create callback of this kernel
 11747.683108 s:  VX_ZONE_ERROR:[ownGraphNodeKernelInit:583] kernel init for node 5, kernel com.ti.display ... failed !!!
 11747.683125 s:  VX_ZONE_ERROR:[vxVerifyGraph:2055] Node kernel init failed
 11747.683133 s:  VX_ZONE_ERROR:[vxVerifyGraph:2109] Graph verify failed
Scaler is enabled
 11747.685905 s: ISS: Starting sensor [IMX390-UB953_D3] ... !!!
[MCU2_0]  11747.682636 s: src/drv/disp/dss_dispApi.c @ Line 273:
[MCU2_0]  11747.682636 s: src/drv/disp/dss_dispApi.c @ Line 273:
[MCU2_0]  11747.682673 s: Driver instance already created!!
[MCU2_0]  11747.682702 s: src/fvid2_drvMgr.c @ Line 759:
[MCU2_0]  11747.682702 s: src/fvid2_drvMgr.c @ Line 759:
[MCU2_0]  11747.682723 s: Driver create failed!!
[MCU2_0]  11747.682751 s:  VX_ZONE_ERROR:[tivxDisplayCreate:547] DISPLAY: ERROR: Display Create Failed!
[MCU2_0]  11747.682751 s:  VX_ZONE_ERROR:[tivxDisplayCreate:547] DISPLAY: ERROR: Display Create Failed!
[MCU2_0]  11747.682751 s:  VX_ZONE_ERROR:[tivxDisplayCreate:547] DISPLAY: ERROR: Display Create Failed!
[MCU2_0]  11747.682751 s:  VX_ZONE_ERROR:[tivxDisplayCreate:547] DISPLAY: ERROR: Display Create Failed!

  • 0
    Intellectual 291 points

    Some updates to this question:

    1. There's also no signal for OOB display either

    2. I use ethernet firmware to connect the board, should i disable it?

  • 0 in reply to Liu Tsing-Yue
    TI__Guru* 81846 points

    Hi,

    It says, Driver instance already created.

    Have you ran any application before this that did not end correctly or you did any exit with Ctrl+C ?

    Could you also confirm if you have ever seen output on a display from this board before? Like, in the previous SDK versions?

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Intellectual 291 points

    Hi,

    Thanks for reminding, the application might not end correctly due to Ctrl+C, after reboot, the error messages were gone during the first execution of apps, is there a way to exit correctly?

    However, we' ve never seen any display from this board before, 09_00_00_02 is the only SDK version we will use, we're using the DP port from a benq monitor.

  • 0 in reply to Liu Tsing-Yue
    TI__Guru* 81846 points

    Hi,

    Liu Tsing-Yue said:
    Thanks for reminding, the application might not end correctly due to Ctrl+C, after reboot, the error messages were gone during the first execution of apps, is there a way to exit correctly?

    All the vision_apps application by default runs in interactive mode and the exit is done by pressing "x". If you would like to exit the application using Ctrl+C, then the signal handler for the same should contain the deinit sequence (i.e. release of openVX object, graph context etc). Please refer the implementation of "x" for the same.

    Liu Tsing-Yue said:
    However, we' ve never seen any display from this board before, 09_00_00_02 is the only SDK version we will use, we're using the DP port from a benq monitor.

    Please connect to Display port 1 on the J784s4 EVM and you should be able to view the display here.

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Intellectual 291 points

    I've tried both DP port on J784s4 EVM, but both didn't display anything on the screen.

    I also tried modetest -M tidss, but failed to detect the device

    root@j784s4-evm:~/# modetest -M tidss
    failed to open device 'tidss': No such file or directory

    Can you suggest what to do next? Thanks

  • 0 in reply to Liu Tsing-Yue
    TI__Guru* 81846 points

    Hi,

    Liu Tsing-Yue said:
    root@j784s4-evm:~/# modetest -M tidss
    failed to open device 'tidss': No such file or directory

    This is expected to fail as the tidss is the linux driver of DSS and that is disabled when using vision_apps. This is because the vision_apps uses the RTOS driver of the display

    Are you still getting Driver instance already created!! error?

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Intellectual 291 points

    Thanks for the reply, I will not get Driver instance already created!! error now.

    The issue now is no signal was displayed on screen.

  • 0 in reply to Liu Tsing-Yue
    TI__Guru* 81846 points

    Hi,

    Could you share me the ./vision_apps_init.sh logs?

    And also, can you press "p" multiple times with a certain interval while executing the application to print out the perf_stats and share the same?

    This would confirm if the application is running fine.

    Also, may I know which display are you using?

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Intellectual 291 points

    Hi,

    Here's the ./vision_apps_init.sh logs:

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    [MCU2_0] 71956.924021 s: CIO: Init ... Done !!!
    [MCU2_0] 71956.924072 s: ### CPU Frequency = 1000000000 Hz
    [MCU2_0] 71956.924096 s: CPU is running FreeRTOS
    [MCU2_0] 71956.924113 s: APP: Init ... !!!
    [MCU2_0] 71956.924148 s: SCICLIENT: Init ... !!!
    [MCU2_0] 71956.924276 s: SCICLIENT: DMSC FW version [9.0.6--v09.00.06 (Kool Koala)]
    [MCU2_0] 71956.924304 s: SCICLIENT: DMSC FW revision 0x9
    [MCU2_0] 71956.924325 s: SCICLIENT: DMSC FW ABI revision 3.1
    [MCU2_0] 71956.924346 s: SCICLIENT: Init ... Done !!!
    [MCU2_0] 71956.924365 s: UDMA: Init ... !!!
    [MCU2_0] 71956.925224 s: UDMA: Init ... Done !!!
    [MCU2_0] 71956.925262 s: UDMA: Init for CSITX/CSIRX ... !!!
    [MCU2_0] 71956.925708 s: UDMA: Init for CSITX/CSIRX ... Done !!!
    [MCU2_0] 71956.925741 s: MEM: Init ... !!!
    [MCU2_0] 71956.925766 s: MEM: Created heap (DDR_LOCAL_MEM, id=0, flags=0x00000004) @ e1000000 of size 16777216 bytes !!!
    [MCU2_0] 71956.925813 s: MEM: Created heap (L3_MEM, id=1, flags=0x00000000) @ 60000000 of size 262144 bytes !!!
    [MCU2_0] 71956.925850 s: MEM: Init ... Done !!!
    [MCU2_0] 71956.925867 s: IPC: Init ... !!!
    [MCU2_0] 71956.925908 s: IPC: 11 CPUs participating in IPC !!!
    [MCU2_0] 71956.925940 s: IPC: Waiting for HLOS to be ready ... !!!
    [MCU2_0] 71966.024879 s: IPC: HLOS is ready !!!
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    And here's the log while executing the single_cam app in vision apps and press multiple times of 'p'.

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    APP: Init ... !!!
    MEM: Init ... !!!
    MEM: Initialized DMA HEAP (fd=5) !!!
    MEM: Init ... Done !!!
    IPC: Init ... !!!
    IPC: Init ... Done !!!
    REMOTE_SERVICE: Init ... !!!
    REMOTE_SERVICE: Init ... Done !!!
    72193.130442 s: GTC Frequency = 200 MHz
    APP: Init ... Done !!!
    72193.134626 s: VX_ZONE_INIT:Enabled
    72193.134631 s: VX_ZONE_ERROR:Enabled
    72193.134634 s: VX_ZONE_WARNING:Enabled
    72193.135598 s: VX_ZONE_INIT:[tivxInitLocal:130] Initialization Done !!!
    72193.137124 s: VX_ZONE_INIT:[tivxHostInitLocal:96] Initialization Done for HOST !!!
    sensor_selection = [0]
    ldc_enable = [0]
    num_frames_to_run = [1000000000]
    is_interactive = [1]
    IttCtrl_registerHandler: command echo registered at location 0
    IttCtrl_registerHandler: command iss_read_2a_params registered at location 1
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    Finally, here's the display I use.

    Thank you so much for your patience!

  • 0 in reply to Liu Tsing-Yue
    TI__Guru* 81846 points

    I see. 

    The application is running fine, but nothing is shown on the display. 

    Do you by any chance have another monitor (i.e. maybe DELL or HP with Display Port 1.2 support) to test if you are seeing the output there?

    Or could you test on any monitor as well?

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Intellectual 291 points

    Currently we only have this monitor for DP port, or is it able to use monitor with HDMI port only?

  • 0 in reply to Liu Tsing-Yue
    TI__Guru* 81846 points

    Hi,

    Could you please try testing with the below patch?

    /cfs-file/__key/communityserver-discussions-components-files/791/Fixed_5F00_DP_5F00_HDMI_5F00_Issue.patch

    Please apply attached patch on ti-processor-sdk-rtos-j721e-evm-09_01_00_06\pdk_jacinto_09_01_00_22 folder, rebuild the SDK

    Regards,

    Nikhil

  • 0 in reply to Nikhil Dasan
    Intellectual 291 points

    Sorry for the reply, but can we keep using the 09_00_00_02 sdk? Currently we're trying to find a supported monitor, but it might take time. Are there still any possible ways to display successfully? thanks.

  • +1 in reply to Liu Tsing-Yue
    TI__Guru* 81846 points

    Hi,

    Liu Tsing-Yue said:
    Sorry for the reply, but can we keep using the 09_00_00_02 sdk? Currently we're trying to find a supported monitor, but it might take time. Are there still any possible ways to display successfully? thanks.

    You could also apply this patch onto the SDK 9.0 PDK path and rebuild the same. 

    But if the changes with the patch does not help, then I think it is a monitor issue as the graph and the node execution is working fine.

    Regards,

    Nikhil

  • +1 in reply to Nikhil Dasan
    Intellectual 291 points

    Hi,

    We tried testing the app on another monitor from other team and it worked, the monitor is EIZO ColorEdge CG2420.

    Thanks for the many help.