HDMI Demo on Nexys Video Board Issue

[Moeen]

Hi guys,

As part of my 4th year project, we are implementing motion detection on Nexys Video board.

While trying to run the hdmi demo, I am able to program the fpga successfully and connect to COM3 port at 9600 baudrate.

However, I recieve a strange sequence of characters from in the SDK Terminal and not the expected menu options for the different operations on the video stream. 

Btw, I am running the 2018.3 version of Vivado on windows 10. I am having trouble trying to figure out what is wrong. 

Also I am following the instructions for the HDMI demo from the following link:

https://github.com/Digilent/Nexys-Video-HDMI?_ga=2.26704445.1058419481.1644979584-710660249.1642605048

And I have taken the demo zipped folder from the following link:

https://github.com/Digilent/Nexys-Video-HDMI/releases/tag/v2018.2-2

Can someone help me? Half the semester is gone and we are stressed and short on time. We really need to get this working. 

Thank you! and God bless you!

https://imgur.com/undefined

[Niță Eduard]

Hello @Moeen,
According to the readme on github, you should use a baudrate of 115200 instead of 9600.
Perhaps this will fix the issue.

Best regards,
Eduard
 

[Moeen]

Hi Eduard, Thank you so much for your quick reply!!!

I tried with 115200. I am now able to see the menu options in the SDK terminal. It shows the following:

Connected to COM3 at 115200
Couldn't start display during demo initialization1
[H[2J**************************************************

*             Nexys Video HDMI Demo              *

**************************************************

*Display Resolution:                 640x480@60Hz*

*Display Pixel Clock Freq. (MHz):          25.000*
*Display Frame Index:                           0*

*Video Capture Resolution:       !HDMI UNPLUGGED!*

*Video Frame Index:                             0*

**************************************************

1 - Change Display Resolution

2 - Change Display Framebuffer Index

3 - Print Blended Test Pattern to Display Framebuffer

4 - Print Color Bar Test Pattern to Display Framebuffer

5 - Start/Stop Video stream into Video Framebuffer

6 - Change Video Framebuffer Index

7 - Grab Video Frame and invert colors

8 - Grab Video Frame and scale to Display resolution

q - Quit

Enter a selection:

 

So I was thinking that perhaps some HDMI cables were defective. But I have tried the cable by connecting them directly between laptop to the HDMI monitor and the display is flawless. So my guess is something is not right in the project files. Btw, I updated the the IPs which were out of date in the project folder (without updating the IPs, nothing displays in teh SDK terminal). 

 

If I make a selection, it says the following:

Invalid Selection[H[2J**************************************************

*             Nexys Video HDMI Demo              *

**************************************************

*Display Resolution:                 640x480@60Hz*

*Display Pixel Clock Freq. (MHz):          25.000*
*Display Frame Index:                           0*

*Video Capture Resolution:       !HDMI UNPLUGGED!*

*Video Frame Index:                             0*

**************************************************

1 - Change Display Resolution

2 - Change Display Framebuffer Index

3 - Print Blended Test Pattern to Display Framebuffer

4 - Print Color Bar Test Pattern to Display Framebuffer

5 - Start/Stop Video stream into Video Framebuffer

6 - Change Video Framebuffer Index

7 - Grab Video Frame and invert colors

8 - Grab Video Frame and scale to Display resolution

q - Quit

Enter a selection:

 

I wonder if you have any other advice.tops for me?

Once again thank you for your help!!!

Edited February 20, 2022 by Moeen

[Niță Eduard]

Hello @Moeen,
Unfortunately I do not have a Nexys Video at hand to test the demo, but you should try taking a look at this post:

The demos are similar, so what is written there can be applied here as well, mainly try starting the demo with both cables plugged and check the HPD signal. Also check if the TX test pattern works.
I'm not sure if the upgrade screwed to 2018.3 screwed anything, but if it still doesn't work try the demo in 2018.2.