element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
AMD
  • Products
  • Manufacturers
  • AMD
  • More
  • Cancel
AMD
Forum Problem with PYNZ-Z2 and HDMI output from camera
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join AMD to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Suggested Answer
  • Replies 26 replies
  • Answers 16 answers
  • Subscribers 23 subscribers
  • Views 7724 views
  • Users 0 members are here
  • pynq z2
  • hdmi
  • pynq
  • pynqstarter
Related

Problem with PYNZ-Z2 and HDMI output from camera

Fred27
Fred27 over 5 years ago

I'm currently making sure I'm in a good position to hit the ground running with the upcoming PYNQ-Z2 workshops. I bought the recommended kit including an Apeman A77 camera and thought I'd just have a quick poke around in advance. I ran through the "getting started" and the Pynq 2.5 image includes some simple HDMI examples. (I hope I'm not jumping too far ahead, but like to be prepared.)

 

Anyway, as I start to run the HDMI example I get a kernel died error (as shown). You can see on screen what's been run. This is just wiring HDMI out to show what's on HDMI in. The error is completely repeatable. Nothing noteworthy in /var/log/jupyter.log to give any clue.

image

 

As quick Google suggested that maybe the image is too high resolution, and when I checked the camera on my TV it outputs 1080p at 60fps regardless of the resolution of video being captured. Could 1080p be too much?  Time to switch to a Raspberry Pi 4 where I can change resolution properly. The above example ran quite happily with the Pi at a lower resolution, but surprised me when it also ran using the Pi at 1920x1080 at 60fps too.

 

Is this camera (Apeman A77) compatible with the HDMI on the PYNQ-Z2? I'd have expected it to be as it was the recommended kit and the Crosstour one listed now is essentially the same model.

 

I'll try to do more digging into any subtle differences between the HDMI output of the Pi and the camera, but all I have is a TV that shows some info on the input. Anyone else have any ideas?

  • Sign in to reply
  • Cancel

Top Replies

  • beacon_dave
    beacon_dave over 5 years ago +3 suggested
    Are you aware that the HDMI out IP provided in the PYNQ-Z2 the base overlay doesn't fully support 1080p video ? https://pynq.readthedocs.io/en/v2.5.1/pynq_overlays/pynqz2/pynqz2_base_overlay.html#hdmi…
  • Fred27
    Fred27 over 5 years ago +3
    Thanks for all your help beacon_dave My TV reports that the Pi and the camera are outputting the same format - 1080p60, sYCC601 colourspace, 8-bit depth, and YCbCr 4:2:2 pixel format. I tried connecting…
  • Fred27
    Fred27 over 5 years ago in reply to beacon_dave +2 suggested
    I wasn't aware of those details. Maybe that's it - a borderline implementation of 1080p where output from the Pi 4 works and the camera doesn't. If that's the case it's frustrating that a recommended camera…
Parents
  • beacon_dave
    0 beacon_dave over 5 years ago

    Are you aware that the HDMI out IP provided in the PYNQ-Z2 the base overlay doesn't fully support 1080p video ?

     

    https://pynq.readthedocs.io/en/v2.5.1/pynq_overlays/pynqz2/pynqz2_base_overlay.html#hdmi

    HDMI Out¶

    The HDMI out IP supports the following resolutions:

    • 640x480
    • 800x600
    • 1280x720 (720p)
    • 1280x1024
    • 1920x1080 (1080p)*

    *While the Pynq-Z2 cannot meet the official HDMI specification for 1080p, some HDMI devices at this resolution may work.

    • Cancel
    • Vote Up +3 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • Fred27
    0 Fred27 over 5 years ago in reply to beacon_dave

    I wasn't aware of those details. Maybe that's it - a borderline implementation of 1080p where output from the Pi 4 works and the camera doesn't. If that's the case it's frustrating that a recommended camera (although the exact model Apeman camera wasn't specified) is one that doesn't work.

     

    If it's output that's a problem, maybe after processing the frames it could work? That simple example streams straight from HDMI in to HDMI out. I'll dig a bit more later, but right now I've promised to play football with the kids and put up a tent so we can camp in the garden tonight and pretend we're on holiday!

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
  • beacon_dave
    0 beacon_dave over 5 years ago in reply to Fred27

    I think that the base overlay supplied is pretty much a basic routing of the IO pins connected to the PL fabric to the input to the PS. So no real 'heavy lifting' being done with FPGA IP at this stage.

     

    There appears to be a video processing overlay available however which starts to make use of the PL for IP blocks to provide video processing off-load, especially when using OpenCV on the PS side of things.

     

    The two HDMI ports on the PYNQ-Z2 although labelled as input and output appear to be are wired directly to the FPGA fabric, so their true direction is presumably only defined by the configuration of the IP blocks. If the input IP meets the 1080p spec but the output IP doesn't, it perhaps suggests that it is some sort of marginal timing or memory limitation with the base overlay implementation.

     

    The camera may be outputting component YPbPr colour space whereas the R-PI component RGB.

     

    Perhaps good questions for Adam in the workshop sessions.

     

    If the HDMI input IP in the base overly fully meets the HDMI spec for 1080p, then the recommended Apeman camera output may not be an issue. The workshop may never route the HDMI input directly to the HDMI output using the base overlay as you are doing here.

     

    Another potential interesting issue with HDMI projects using FPGA devices is the storage of EDID information as this is supposed to be available from an HDMI sink device even in the powered off state. The HDMI source actively provides power to the sink device EEPROM in order to be able to return this EDID information. However with a FPGA device it typically needs to be powered up and the bitstream loaded to configure the fabric in order to create the memory to store the EDID information before it can be retrieved. So perhaps an external I2C EEPROM device still requires to be added to the design for this.

     

     

    I recall hearing stories of families doing the camping in the back garden thing, yet ending up spending most of their time too'ing and fro'ing between the tent and the house.  image  

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Reply
  • beacon_dave
    0 beacon_dave over 5 years ago in reply to Fred27

    I think that the base overlay supplied is pretty much a basic routing of the IO pins connected to the PL fabric to the input to the PS. So no real 'heavy lifting' being done with FPGA IP at this stage.

     

    There appears to be a video processing overlay available however which starts to make use of the PL for IP blocks to provide video processing off-load, especially when using OpenCV on the PS side of things.

     

    The two HDMI ports on the PYNQ-Z2 although labelled as input and output appear to be are wired directly to the FPGA fabric, so their true direction is presumably only defined by the configuration of the IP blocks. If the input IP meets the 1080p spec but the output IP doesn't, it perhaps suggests that it is some sort of marginal timing or memory limitation with the base overlay implementation.

     

    The camera may be outputting component YPbPr colour space whereas the R-PI component RGB.

     

    Perhaps good questions for Adam in the workshop sessions.

     

    If the HDMI input IP in the base overly fully meets the HDMI spec for 1080p, then the recommended Apeman camera output may not be an issue. The workshop may never route the HDMI input directly to the HDMI output using the base overlay as you are doing here.

     

    Another potential interesting issue with HDMI projects using FPGA devices is the storage of EDID information as this is supposed to be available from an HDMI sink device even in the powered off state. The HDMI source actively provides power to the sink device EEPROM in order to be able to return this EDID information. However with a FPGA device it typically needs to be powered up and the bitstream loaded to configure the fabric in order to create the memory to store the EDID information before it can be retrieved. So perhaps an external I2C EEPROM device still requires to be added to the design for this.

     

     

    I recall hearing stories of families doing the camping in the back garden thing, yet ending up spending most of their time too'ing and fro'ing between the tent and the house.  image  

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Verify Answer
    • Reject Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube