[RFSoC 4x2] issue with the notebook display_port_introduction

Support
1

Hi Everyone,

I want to execute the provided notebook of the display port for the RFSoC 4x2:
(RFSoC-PYNQ/boards/RFSoC4x2/notebooks/common/display_port_introduction.ipynb at master · Xilinx/RFSoC-PYNQ · GitHub)

But I have an error with cv2.VideoCapture(0).

cv2 error
cv2 error1566×240 56.8 KB

Did someone also meet this error?

It might be related to that issue:

(python - OpenCv error can't open camera through video capture - Stack Overflow)

Thank you in advance for your help

2

Do you have a camera connected and is it recognized?
Try running:
ls /dev/video*

If the camera is recognized, but has a different index, you can modify the code.

Cathal

3

I ran ls /dev/video*, I got /dev/video0 and /dev/video1. I ran lsusb, and my webcam was correctly detected:

camera
camera781×243 5.86 KB

My webcam is a Microsoft LifeCamHD-3000:
(Microsoft LifeCam HD-3000 review | Digital Camera World)

Its datasheet can be downloaded here: (https://download.microsoft.com/documents/uk/hardware/TDS_LifeCamHD-3000_1103A.pdf)

What did you mean by “If the camera is recognized, but has a different index, you can modify the code.” If it is about the index 0, 1 or -1 of cv2.VideoCapture, I changed it but I still got the issue.

Is pynq support the correct entity to ask for a possible modification of the jupyter notebook available online? Or would I have to contact another entity?

Sincerely

4

Hi @matthew,

Can you try passing some flags to OpenCV when opening the camera. Try both index 0 and 1

index = 0
index += cv2.CAP_V4L2
capture = cv2.VideoCapture(index)

Alternatively, you can try with different flag

flag = cv2.CAP_DSHOW # or cv2.CAP_MSMF
index = 0
capture = cv2.VideoCapture(index, flag)

Can you also report ?

ls -la /dev/video*

Mario

1 Like
5

Hi,

This part of the notebook is working with capture = cv2.VideoCapture(0, cv2.CAP_V4L2).

ls -la /dev/video* is displaying:
ls la

I have another problem at the end of the notebook. I want to send the capture of the webcam on the minidisplay port.
The end of the notebook is executing, but nothing is displayed on a screen connected to the minidisplay port.
I did a print(frame), and the frame was empty:

empty frame
empty frame1372×632 18.6 KB

The screen is correctly connected to the minidisplay port because the start of the notebook is working: I have a blue alternation on the screen. My webcam was also tested and validated from the notebook usb_webcam:
(RFSoC-PYNQ/boards/RFSoC4x2/notebooks/common/usb_webcam.ipynb at master · Xilinx/RFSoC-PYNQ · GitHub)

Does someone have this issue too, or can reproduce it?

Sincerely

6

Looks like the camera capture is empty. Did you try with index 1?

Can you try capture = cv2.VideoCapture(0+ cv2.CAP_V4L2)?

7

I tried capture = cv2.VideoCapture(0+ cv2.CAP_V4L2), but the frame was still empty. Same thing with an index of 1.

I think that the error is in capture.read(frame), because in the notebook usb_webcam, another method was used to fill the frame, and worked: ret, frame = capture.read()

Can you check this possibility, please?

Sincerely

8

In the failing notebook can you try?

for _ in range(number_frames):
    frame = displayport.newframe()
    ret, img = capture.read()
    frame[:] = img
    displayport.writeframe(frame)
9

I tried that ret, img = capture.read() and frame[:] = img and it worked: my stream was displayed on my screen. Thank you for the indication.
I just had to modify the resolution of capture.set, because capture.set(3,1280) showed me a lower resolution. But that is a cv2 strange issue.

To sum up this request, is it possible to modify the notebook in two ways: change
capture = cv2.VideoCapture(0) into capture = cv2.VideoCapture(0, cv2.CAP_V4L2) and change
capture.read(frame)
into
ret, img = capture.read()
frame[:] = img

I thank everyone who helped with these issues once again.

1 Like
10

I encourage you to do a PR with these changes. :grinning:

11

To who should I do a personal request? To the responsible of the github of the Jupyter notebook?

I just don’t understand if this Pynq support forum is managed by AMD, and to who adress these jupyter issues

12

It is managed by the PYNQ team. These issues belong to the forum, but since there is a solution, I appreciate if you could contribute it back to the repo with a PR,

13

What is a PR? Is it a Partial Reconfiguration? I am sorry, I do not know how to do it.

From what I see online, a PR is related to the bitstream. But the issues are not with the bitstream, the PL. The issues are with the jupyter notebook, the PS.

14

Pull Request in GitHub with the changes that fixes the issue.

15

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.