• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 97 subscribers
  • Views 926 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.

TDA4VH-Q1: Display Port Not working

Kim TaeJung
Intellectual 771 points

Part Number: TDA4VH-Q1

Hello

I am currently using TDA4VH-Q1 J784S4EVM.

RTOS-SDK is being used, and the version is 09_01_00_06.

After booting the board, a dp error is displayed as shown below.

[   17.575403] platform 4800000.dsi: deferred probe pending
[   17.580718] platform a000000.dp-bridge: deferred probe pending
[   17.586542] platform main-r5fss-cpsw9g-virt-mac1: deferred probe pending
[   17.593234] platform main-r5fss-cpsw9g-virt-mac0: deferred probe pending
[   17.599922] platform dp0-connector: deferred probe pending
[   17.605397] platform regulator-dp1-prw: deferred probe pending
[   17.611219] platform regulator-dp0-prw: deferred probe pending

If I leave the name_overlays entry empty in the uEnv.txt file, the DP port works fine.

I think the symptoms are similar to the issue below

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1330903/no-signal-from-dp-when-using-dp-to-hdmi-adapter-and-hdmi-grabber/5072916?tisearch=e2e-sitesearch&keymatch=platform%252520dp0-connector%25253A%252520deferred%252520probe%252520pending#5072916

Is there a solution?

  • 0
    TI__Guru**** 502615 points

    Hi,

    I think if you are using vision apps/RTOS SDK, display is controlled from R5F and so it is not enabled on the Linux and this overlay just disables it from the Linux. If you want to use it from Linux, please disable display from RTOS SDK and remove DP disable node from this overlay. 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 771 points

    I understand controlling the display on R5F.
    After running vision apps without changing the overlay, I ran ./run_app_tidl.sh and the display screen did not appear.
    We are using a Dp to HDMI converter.
    There was no error message displayed in the terminal.

  • 0 in reply to Kim TaeJung
    TI__Guru**** 502615 points

    oh, DP to HDMI convertor has an issue on SDK9.x, can you please apply attached patch on top of PDK folder and see if it helps?  

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

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 771 points

    This is the log after applying the patch.

    The log repeats infinitely, Still not displayed.

    root@j784s4-evm:/opt/vision_apps# ./run_app_tidl.sh 
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 !!!
    63.123222 s: GTC Frequency = 200 MHz
APP: Init ... Done !!!
    63.123293 s:  VX_ZONE_INIT:Enabled
    63.123301 s:  VX_ZONE_ERROR:Enabled
    63.123307 s:  VX_ZONE_WARNING:Enabled
    63.124070 s:  VX_ZONE_INIT:[tivxInitLocal:130] Initialization Done !!!
    63.124554 s:  VX_ZONE_INIT:[tivxHostInitLocal:101] Initialization Done for HOST !!!


 =================================
 Demo : TIDL Object Classification
 =================================

 p: Print performance statistics

 x: Exit

 Enter Choice: network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin
Iteration 0 of 1000000 ... 
network file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_net_mobilenet_v1.bin
config  file: /opt/vision_apps/test_data/tivx/tidl_models/tidl_io_mobilenet_v1_1.bin

  • 0 in reply to Kim TaeJung
    TI__Guru**** 502615 points

    Was this DP to HDMI convertor working earlier? and stopped working in SDK9.1? 

    This is because only active DP to HDMI convertor can be supported, even with this patch. So can you please check if you are using correct convertor? 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 771 points

    We haven't tested it on 8.x yet.

    So this time, I'm going to test it with a dp to dp cable. Is it okay to do it with the previous patch applied?

  • 0 in reply to Kim TaeJung
    TI__Guru**** 502615 points

    Yes, DP display should work fine even with the previous patch.

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 771 points

    When testing with a DP cable, normal output was confirmed.

    im using acitve convertor

    https://naroit.co.kr/product/detail.html?product_no=17&cate_no=26&display_group=1#prdDetail

  • 0 in reply to Kim TaeJung
    TI__Guru**** 502615 points

    ok,

    With active DP to HDMI convertor, it should work as it is on SDK8.6, without any additional patch.

    With active DP to HDMI convertor, SDK9.x requires additional patch that i shared earlier. 

    I will not be able to confirm if this is active DPtoHDMI convertor. 

    Regards,

    Brijesh

  • 0 in reply to Brijesh Jadav
    Intellectual 771 points

    Then, can you tell me the converter model that was tested?