UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
391 Views
Registered: ‎12-28-2015

UltraZed-EG DisplayPort Problem

Jump to solution

Hello,

 

I am trying to work with the DisplayPort on UltraZed IO Carrier Board but I have a problem in Linux Bootup.

Attached my Linux Bootup Log. It's an exception in the dma allocation related to the zynqamp display driver.

Attached also my overall system.dts

Attached also a tcl for my vivado project

 

I tried binaries posted from Avnet here and it's working on my display with my board.

 

So can any one help me with the error logged in my linux bootup log.

[    6.034827] xilinx-psgtr fd400000.zynqmp_phy: Lane:3 type:8 protocol:4 pll_locked:yes
[    6.045070] xilinx-dp-snd-codec fd4a0000.zynqmp-display:zynqmp_dp_snd_codec0: Xilinx DisplayPort Sound Codec probed
[    6.055692] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
[    6.063703] xilinx-dp-snd-pcm zynqmp_dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
[    6.071938] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
[    6.084291] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
[    6.096893] xilinx-dp-snd-card fd4a0000.zynqmp-display:zynqmp_dp_snd_card: Xilinx DisplayPort Sound Card probed
[    6.106993] OF: graph: no port node found in /amba/zynqmp-display@fd4a0000
[    6.113928] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    6.120464] [drm] No driver support for vblank timestamp query.
[    6.126447] xlnx-drm xlnx-drm.0: bound fd4a0000.zynqmp-display (ops 0xffffff8008ac6b28)
[    6.169516] zynqmp-display fd4a0000.zynqmp-display: Cannot do DMA to address 0x0000000000000000
[    6.178140] swiotlb: coherent allocation failed for device fd4a0000.zynqmp-display size=9216000
[    6.186818] CPU: 2 PID: 58 Comm: kworker/2:1 Not tainted 4.14.0-xilinx-v2018.2 #9
[    6.194272] Hardware name: Avnet UltraZed-3EG (DT)
[    6.199055] Workqueue: events deferred_probe_work_func
[    6.204165] Call trace:
[    6.206600] [<ffffff80080881f0>] dump_backtrace+0x0/0x368
[    6.211980] [<ffffff800808856c>] show_stack+0x14/0x20
[    6.217016] [<ffffff80089ed678>] dump_stack+0x9c/0xbc
[    6.222050] [<ffffff8008457c9c>] swiotlb_alloc_coherent+0x174/0x180
[    6.228301] [<ffffff8008093a6c>] __dma_alloc+0x13c/0x250
[    6.233596] [<ffffff8008555494>] drm_gem_cma_create+0x8c/0x110
[    6.239409] [<ffffff8008562ab8>] xlnx_fbdev_create+0x68/0x230
[    6.245139] [<ffffff800852eeac>] __drm_fb_helper_initial_config_and_unlock+0x1bc/0x3d0
[    6.253038] [<ffffff800852f100>] drm_fb_helper_initial_config+0x40/0x50
[    6.259633] [<ffffff8008562d20>] xlnx_fb_init+0xa0/0x158
[    6.264927] [<ffffff8008562740>] xlnx_bind+0x270/0x298
[    6.270049] [<ffffff8008570828>] try_to_bring_up_master+0x178/0x1d8
[    6.276299] [<ffffff8008570a88>] component_master_add_with_match+0xa0/0xf8
[    6.283156] [<ffffff8008562934>] xlnx_platform_probe+0x1cc/0x1f8
[    6.289146] [<ffffff8008578148>] platform_drv_probe+0x38/0x78
[    6.294875] [<ffffff80085767b0>] really_probe+0x1b8/0x270
[    6.300257] [<ffffff80085769d4>] __device_attach_driver+0xa4/0x110
[    6.306419] [<ffffff8008574b54>] bus_for_each_drv+0x4c/0x98
[    6.311974] [<ffffff80085765a8>] __device_attach+0xb0/0xe8
[    6.317443] [<ffffff8008576b70>] device_initial_probe+0x10/0x18
[    6.323345] [<ffffff8008575ab4>] bus_probe_device+0x94/0xa0
[    6.328900] [<ffffff8008573ac8>] device_add+0x378/0x578
[    6.334108] [<ffffff8008577f44>] platform_device_add+0x124/0x2a8
[    6.340097] [<ffffff8008562294>] xlnx_drm_pipeline_init+0x7c/0x108
[    6.346263] [<ffffff800856cff0>] zynqmp_dpsub_probe+0x100/0x150
[    6.352163] [<ffffff8008578148>] platform_drv_probe+0x38/0x78
[    6.357892] [<ffffff80085767b0>] really_probe+0x1b8/0x270
[    6.363274] [<ffffff80085769d4>] __device_attach_driver+0xa4/0x110
[    6.369437] [<ffffff8008574b54>] bus_for_each_drv+0x4c/0x98
[    6.374992] [<ffffff80085765a8>] __device_attach+0xb0/0xe8
[    6.380460] [<ffffff8008576b70>] device_initial_probe+0x10/0x18
[    6.386363] [<ffffff8008575ab4>] bus_probe_device+0x94/0xa0
[    6.391918] [<ffffff8008575f5c>] deferred_probe_work_func+0x94/0x140
[    6.398256] [<ffffff80080b0c6c>] process_one_work+0x1dc/0x348
[    6.403983] [<ffffff80080b1024>] worker_thread+0x24c/0x488
[    6.409452] [<ffffff80080b67a4>] kthread+0x12c/0x130
[    6.414399] [<ffffff8008084290>] ret_from_fork+0x10/0x18
[    6.419711] zynqmp-display fd4a0000.zynqmp-display: failed to allocate buffer with size 9216000
[    6.428392] zynqmp-display fd4a0000.zynqmp-display: Failed to set initial hw configuration.
[    6.436721] zynqmp-display fd4a0000.zynqmp-display: failed to initialize drm fb
[    6.444184] [drm] Initialized xlnx 1.0.0 20130509 for fd4a0000.zynqmp-display on minor 0
[    6.452225] zynqmp-display fd4a0000.zynqmp-display: ZynqMP DisplayPort Subsystem driver probed

 

0 Kudos
1 Solution

Accepted Solutions
Moderator
Moderator
249 Views
Registered: ‎04-24-2017

Re: UltraZed-EG DisplayPort Problem

Jump to solution

Hi ahmed.kamel@valeo.com ,

Looks like you are using IDT Clock generator for DP, Actually you don't need this in your design in 2018.x version. Linux CCF should handle this.

You can create a simple Ultrazed PS block using the Ultrazed board files then create a petalinux project this works as expected.

To make your life little easier I have attached the vivado design file and petalinux project-spec files.

You can make a diff and compare it.

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------
4 Replies
Moderator
Moderator
327 Views
Registered: ‎11-09-2015

Re: UltraZed-EG DisplayPort Problem

Jump to solution

Hi ahmed.kamel@valeo.com ,

Can you try to run the modetest command and let me know the output?

modetest -M xlnx

 


Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
0 Kudos
274 Views
Registered: ‎12-28-2015

Re: UltraZed-EG DisplayPort Problem

Jump to solution

Here's the output of modetest

root@uz3eg-iocc-sd-oob-2018-2:~# modetest -M xlnx
Encoders:
id      crtc    type    possible crtcs  possible clones
37      0       TMDS    0x00000001      0x00000000

Connectors:
id      encoder status          name            size (mm)       modes   encoders
38      0       connected       DP-1            520x320         34      37
  modes:
        name refresh (Hz) hdisp hss hse htot vdisp vss vse vtot)
  1920x1200 60 1920 1968 2000 2080 1200 1203 1209 1235 154000 flags: phsync, nvsync; type: preferred, driver
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: nhsync, nvsync; type: driver
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
  1920x1080 60 1920 2008 2052 2200 1080 1084 1089 1125 148352 flags: phsync, pvsync; type: driver
  1920x1080 50 1920 2448 2492 2640 1080 1084 1089 1125 148500 flags: phsync, pvsync; type: driver
  1600x1200 60 1600 1664 1856 2160 1200 1201 1204 1250 162000 flags: nhsync, nvsync; type: driver
  1680x1050 60 1680 1784 1960 2240 1050 1053 1059 1089 146250 flags: nhsync, pvsync; type: driver
  1280x1024 75 1280 1296 1440 1688 1024 1025 1028 1066 135000 flags: phsync, pvsync; type: driver
  1280x1024 72 1280 1368 1504 1728 1024 1025 1028 1067 132840 flags: nhsync, pvsync; type:
  1280x1024 60 1280 1328 1440 1688 1024 1025 1028 1066 108000 flags: phsync, pvsync; type: driver
  1440x900 75 1440 1536 1688 1936 900 903 909 942 136750 flags: nhsync, pvsync; type: driver
  1440x900 60 1440 1520 1672 1904 900 903 909 934 106500 flags: nhsync, pvsync; type: driver
  1366x768 60 1366 1436 1579 1792 768 771 774 798 85500 flags: phsync, pvsync; type: driver
  1280x800 60 1280 1352 1480 1680 800 803 809 831 83500 flags: nhsync, pvsync; type: driver
  1152x864 75 1152 1216 1344 1600 864 865 868 900 108000 flags: phsync, pvsync; type: driver
  1280x768 60 1280 1288 1320 1360 768 776 784 790 64400 flags: phsync, pvsync; type: driver
  1280x720 60 1280 1390 1430 1650 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  1280x720 60 1280 1390 1430 1650 720 725 730 750 74176 flags: phsync, pvsync; type: driver
  1280x720 50 1280 1720 1760 1980 720 725 730 750 74250 flags: phsync, pvsync; type: driver
  1024x768 75 1024 1040 1136 1312 768 769 772 800 78750 flags: phsync, pvsync; type: driver
  1024x768 70 1024 1048 1184 1328 768 771 777 806 75000 flags: nhsync, nvsync; type: driver
  1024x768 60 1024 1048 1184 1344 768 771 777 806 65000 flags: nhsync, nvsync; type: driver
  800x600 75 800 816 896 1056 600 601 604 625 49500 flags: phsync, pvsync; type: driver
  800x600 72 800 856 976 1040 600 637 643 666 50000 flags: phsync, pvsync; type: driver
  800x600 60 800 840 968 1056 600 601 605 628 40000 flags: phsync, pvsync; type: driver
  720x576 50 720 732 796 864 576 581 586 625 27000 flags: nhsync, nvsync; type: driver
  720x480 60 720 736 798 858 480 489 495 525 27027 flags: nhsync, nvsync; type: driver
  720x480 60 720 736 798 858 480 489 495 525 27000 flags: nhsync, nvsync; type: driver
  640x480 75 640 656 720 840 480 481 484 500 31500 flags: nhsync, nvsync; type: driver
  640x480 73 640 664 704 832 480 489 492 520 31500 flags: nhsync, nvsync; type: driver
  640x480 67 640 704 768 864 480 483 486 525 30240 flags: nhsync, nvsync; type: driver
  640x480 60 640 656 752 800 480 490 492 525 25200 flags: nhsync, nvsync; type: driver
  640x480 60 640 656 752 800 480 490 492 525 25175 flags: nhsync, nvsync; type: driver
  720x400 70 720 738 846 900 400 412 414 449 28320 flags: nhsync, pvsync; type: driver
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:
                        00ffffffffffff0030aeb46101010101
                        041c0104a53420783e5595a9544c9e24
                        0d5054bdcf00d1c0714f818c81008180
                        950f9500b300283c80a070b023403020
                        360006442100001a000000ff00563330
                        31414c34370a20202020000000fd0032
                        4b1e5311000a202020202020000000fc
                        004c454e20543234642d31300a200128
                        020318f14b010203040514111213901f
                        23090707830100002819005050001630
                        0820880006442100001e662156aa5100
                        1e30468f330006442100001e483f4030
                        62b0324040c013000644210000180000
                        00000000000000000000000000000000
                        00000000000000000000000000000000
                        000000000000000000000000000000b9
        2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 3
        5 link-status:
                flags: enum
                enums: Good=0 Bad=1
                value: 0
        39 sync:
                flags: range
                values: 0 1
                value: 0
        40 bpc:
                flags: enum
                enums: 6BPC=6 8BPC=8 10BPC=10 12BPC=12
                value: 8

CRTCs:
id      fb      pos     size
36      0       (0,0)   (0x0)
   0 0 0 0 0 0 0 0 0 0 flags: ; type:
  props:
        29 output_color:
                flags: enum
                enums: rgb=0 ycrcb444=1 ycrcb422=2 yonly=3
                value: 0
        30 bg_c0:
                flags: range
                values: 0 4095
                value: 0
        31 bg_c1:
                flags: range
                values: 0 4095
                value: 0
        32 bg_c2:
                flags: range
                values: 0 4095
                value: 0

Planes:
id      crtc    fb      CRTC x,y        x,y     gamma size      possible crtcs
34      0       0       0,0             0,0     0               0x00000001
  formats: VYUY UYVY YUYV YVYU YU16 YV16 YU24 YV24 NV16 NV61 BG24 RG24 XB24 XR24 XB30 XR30 YU12 YV12 NV12 NV21 XV15 XV20
  props:
        6 type:
                flags: immutable enum
                enums: Overlay=0 Primary=1 Cursor=2
                value: 0
        33 tpg:
                flags: range
                values: 0 1
                value: 0
35      0       0       0,0             0,0     0               0x00000001
  formats: AB24 AR24 RA24 BA24 BG24 RG24 RA15 BA15 RA12 BA12 RG16 BG16
  props:
        6 type:
                flags: immutable enum
                enums: Overlay=0 Primary=1 Cursor=2
                value: 1
        27 alpha:
                flags: range
                values: 0 255
                value: 255
        28 g_alpha_en:
                flags: range
                values: 0 1
                value: 1

Frame buffers:
id      size    pitch
0 Kudos
Moderator
Moderator
262 Views
Registered: ‎11-09-2015

Re: UltraZed-EG DisplayPort Problem

Jump to solution

Hi ahmed.kamel@valeo.com ,

From the result of your modetest command, it seems that the Displayport driver is correctly started and that it can successfully read the EDID from your monitor.

What application is using the DP? Did you started the X server?

Can tyou try the following command to see if you can dispaly something:

modetest -M xlnx -s 38:1920x1080@RG16

Florent
Product Application Engineer - Xilinx Technical Support EMEA
**~ Don't forget to reply, give kudos, and accept as solution.~**
Moderator
Moderator
250 Views
Registered: ‎04-24-2017

Re: UltraZed-EG DisplayPort Problem

Jump to solution

Hi ahmed.kamel@valeo.com ,

Looks like you are using IDT Clock generator for DP, Actually you don't need this in your design in 2018.x version. Linux CCF should handle this.

You can create a simple Ultrazed PS block using the Ultrazed board files then create a petalinux project this works as expected.

To make your life little easier I have attached the vivado design file and petalinux project-spec files.

You can make a diff and compare it.

Thanks,
Sandeep
PetaLinux Yocto | Embedded SW Support

---------------------------------------------------------------------------
Don’t forget to Reply, Kudo, and Accept as Solution.
---------------------------------------------------------------------------