ZCU104 Returning HDMI Error

[nickaitken]

Hello, 

I've looked through a lot of posts that had similar issues and none of the solutions worked for me. (However, I am currently ordering one of the recommended monitors and hope that it is that easy of a fix.)

I am following this tutorial: http://www.wiki.xilinx.com/reVISION+Getting+Started+Guide+2017.4+rev2

In section 8.1 I am told to use the command video_cmd -s 1 -i 1920x1080@YUY2 -X 

to initialize a media the HDMI media pipeline. (In my case the 1 is a 0 but that should not make a difference.)

An error occurs: ERROR: Query DV timings failed: Link has been severed.

Any advice? 

Thanks!

[florentw]

Hello @nickaitken,

I've looked through a lot of posts that had similar issues and none of the solutions worked for me.

A recommendation for next time: you should say which topic you have visited and what you have tried. To avoid being suggested the same solution.

Did you see the following known issue in the wiki page and tried the solution:

When utilizing an HDMI monitor it is sometimes necessary to run the following command before launching the examples. 
This is because the HDMI display is not initialized.
Solution: Run the command with the correct resolution of your display "modetest -M xilinx_drm_mixer -s 33:3840x2160@AR24"

[nickaitken]

Yes, I tried to do that but I was met with this error:

failed to find mode "1280x720" for connector 33
failed to create dumb buffer: Invalid argument

[florentw]

Hi @nickaitken,

What output do you have for the command:

modetest -M xilinx_drm_mixer -c

[nickaitken]

Here is the output :

id      encoder status          name            size (mm)       modes   encoders
33      0       disconnected    HDMI-A-1        0x0             0       32
  props:
        1 EDID:
                flags: immutable blob
                blobs:

                value:
        2 DPMS:
                flags: enum
                enums: On=0 Standby=1 Suspend=2 Off=3
                value: 0

[florentw]

HI @nickaitken,

Is it an HDMI monitor? Or are you using a HDMI to VGA converter (I do not think this would work)

[nickaitken]

Nope! I am using the HDMI cable included in the box. One thing that I think may be a problem but haven't had a chance to test is the monitor that I am using has a default resolution of 1600x900. However, it does support 1280x720 resolution so I'm not sure if this would be a problem.  I have to request a monitor, so it make take some time for it to get to me. I've tried this on 2 separate monitors, the second is 1920x1200 default resolution. I got the same errors on both.

I noticed on some forums posts the command fbset was mentioned so I tried that and got a weird resolution:

mode "1024x384"
    geometry 1024 384 1024 768 32
    timings 0 0 0 0 0 0 0
    accel true
    rgba 8/16,8/8,8/0,8/24
endmode

BUT, when I tried to change the resolution... I got this error:

input: fbset -xres 1280

output: ioctl FBIOPUT_VSCREENINFO: Invalid argument

[florentw]

HI @nickaitken,

Sorry about the delay.

Did you try with the pre-built images. Did you try different one?

[nickaitken · Accepted solution]

Hi florentw, 

Don't worry about the delay, it is no problem. However, I did find something on another forum post that seemed to work! 

Fix - pauldirac (4th reply)

To answer your question, I was doing this with images that I built using the tutorial. I tried the pre-built ones and I was having the same problem before. I think they should work flawlessly now though! I'm not sure if these commands worked perfectly but the optical flow seemed to be working pretty well!

Thanks!

[florentw]

HI @nickaitken,

Good to know that you found a workaround by looking on the forums.

Could you mark your last reply as solution? It might help users having the same issue.

Thanks,

[sdsocdso]

Hi Nick,

May I know you use which version of SDSOC and ZCU104 reVISION file to rebuild the application?

Thank you