Actions
Forum Thread Details
  • State Verified Answer
  • Replies 14 replies
  • Answers 3 answers
  • Subscribers 325 subscribers
  • Views 1851 views
  • Users 0 members are here
Related

Display Port issue on Ultrazed 7EV SOM+Carrier Card

ontran

We bought two Ultrazed 7EV SOM+Carrier Card starter kits. I cannot get the display port to work with the shipped SDCARD as is, and looking for some help.

 

I followed the avnet 7ev cc test document and display port config document from gitlab. I also have a ZCU106 that worked with the same display-port cable+monitor for comparison.

 

(1) Ultrazed didn't seem to have a drm (Direct Rendering Manager) driver:

 

root@uz7ev-evcc-2017-3:~# drmdevice
drmGetDevices() has returned 0

 

On ZCU106:

 

root@zcu106_vcu_trd:~# drmdevice

device[0]

   available_nodes 0001

   nodes

... [lots of stuff]

 

(2) Ultrazed has a different device name

 

root@uz7ev-evcc-2017-3:~# ls -al /sys/class/drm/card0/device
lrwxrwxrwx 1 root root 0 Feb  6 23:32 /sys/class/drm/card0/device -> ../../../xilinx_drm

 

On ZCU106:

root@zcu106_vcu_trd:~# ls -al /sys/class/drm/card0/device
lrwxrwxrwx 1 root root 0 Feb  4 07:13 /sys/class/drm/card0/device -> ../../../fd4a0000.zynqmp-display

 

(3) I was able to get colorbar show up on the monitor at 1920x1080 on ZCU106, but the two Ultrazed boards showed different behavior, one has no resolution (return nothing) when poked with "$ cat /sys/class/drm/card0-DP-1/modes", the other board returns "1366x768" and others, but no 1920x1080. I was able to get colorbar on Ultrazed with resolution of 1366x768 with "modetest ...". This might be an EDID issue?

 

Anyone got the display port working with the board as is? Any comments or advice are appreciated.

 

Liyong Z

 

  • 0

    Hi there,

     

    Have you seen this design?

    UltraZED-EV + IO Carrier Card VCU Design Example (v2018.3)

     

    image

     

    That will link you over to some pre-built images that you can test rather quickly based on the instructions on that same page.

     

    I've personally used that image in my webinar if you would rather see how to run this demo using video instructions

    Embedded Video Processing Using the UltraZed-EV

     

    --Dan

  • 0 in reply to drozwood90

    Hi Dan,

    thanks for the quick response.

    Yes, I was following reference design example v2018.3 and went through your youtube video series. We are trying to reproduce what you did step-by-step. Thanks for all the great documents. The commands I was using in above post were coming from "Configuring and Working with the DisplayPort Interface" as shown in your post.

     

    I have also tried to use the "pre-build" images in the design example to put on a sdcard. It behaved the same.

     

    I did notice that in your video, the prompt is

      root@vcu_uz7ev_cc:~#

    while the shipped sdcard boots up as (is it supposed to 2018 something?)

      root@uz7ev-evcc-2017-3:~#

     

    Regards,

    Liyong

  • 0

    Hi Liyong,

     

    I can't be 100% sure this is your issue, but that nugget of information leads me to believe you do not have your boot switches set properly.

    The board ships from the factory setup for QSPI boot.  That factory test image is from 2017.3.

    You need to change the boot jumpers on the SOM to be SDCARD Boot.

     

    Left to RIGHT as depicted in the below image

    ON OFF OFF OFF
    image

     

    --Dan

    Also, it appears that once I flipped my phone into MACRO view, that I need to clean my SOM - didn't get a dusting when I was cleaning my office!

  • 0 in reply to drozwood90

    Hi Dan,

    You are right! I was able to get through with the dip switch settings.

    Some minor questions:

    (1) why does it say open device of 'i915' as shown below? Is it supposed to be GPU Mali? i915 is an intel GPU.

     

    root@uz7ev-evcc-2018-2:~# modetest -D fd4a0000.zynqmp-display -s 38@36:1280x720-60@AR24

    trying to open device 'i915'...done

    setting mode 1280x720-60Hz@AR24 on connectors 38, crtc 36

    [   46.103226] PLL: shutdown

    [   46.112613] PLL: enable

     

    (2) I have a 4K monitor. I could recognize that on ZCU106, but only 1920x1080 on Ultrazed. Was there some limitation on the display port hardware of carrier card or SOM?

     

    Much appreciate your help!

    Liyong

  • 0 in reply to ontran

    Hi there,

     

    1) let me check - it could just be a "goofy" linux driver  thing.  To be honest, I had never noticed that.

    2) while the UltraZed-EV SOM supports 4K2K, the CURRENT Carrier does it using a SINGLE lane.  There are FEW monitors out there that support the full 4K in a single lane.  Thus we see almost all monitors we attach run at 1080P.  There are things in the works regarding this, but the solution you have right now (as it was explained to me) is get a really expensive monitor that can support a single lane 4K2K or live with 1080P while using our current carrier card.  A custom carrier would solve this issue.

  • 0 in reply to ontran

    Hi Liyong,

     

    The UltraZed may not recognize the high resolution of your 4K monitor because it is limited to just one lane of DP video.  Here is a screenshot from DP connector in the schematics:

     

    image

     

    It is my understanding that UHD or 4K video requires 2 lanes of DisplayPort.  If this is a requirement you may want to take a look at the UltraZed-EG SOM with the I/O carrier.  The Zynq MPSoC device on the UltraZed-EG SOM has a smaller PL and doesn't have the VCU that the UltraZed-EV does, but if you need 4K video this may be an option for you.  Keep in mind only the UltraZed-EG I/O carrier has two lanes of DP video.

    --Tom

  • 0 in reply to narrucmot

    Hello Tom and Dan,

    Thanks! Another puzzle solved. We will take a look of EG design when we do our own carrier card.

    Appreciate your help!

    Liyong

  • 0 in reply to ontran

    Hi there, regarding question 1, this is the response I was able to find:

    "I have seen this before – I believe it’s one of the quirky modetest things with the pre-v2019.2 codebase

    I don’t see this in v2019.2 port I’m currently running.

    I’ll note that the MALI binaries are not included in the base port, so this isn’t happening at the GPU level – just the DRM device driver for the displayport controller, the GPU isn’t involved at this stage."

     

    I hope that helps!

     

    --Dan

  • 0 in reply to drozwood90

    Hello Dan,

    Very informative. We would go with GPU route since the final video has a graphical overlay with touch control mixed with video.

    Thanks,

    liyong

  • 0

    Hi

    I too am having this same problem. I have the jumpers set correctly but I don't see anything on the display port.

     

    When I type cat /sys/kernel/debug/dri/0/state I don't get the output in the test screen, I get:

     

    image

     

    note that the mode is all zero. I have a display attached to the display port. I've checked the voltages on the board. It seems all is ok apart from no image on the display. Any suggestions please?