Actions
Engagement
  • Author Author: rscasny
  • Date Created: Date Created
  • Last Updated Last Updated:
  • Views 1815 views
  • Likes 0 likes
  • Comments 11 comments
Related
Recommended

Take the PYNQ Poll: You know Python, but Do You Know PYNQ?

If you are a member of element14 and you're an embedded developer (or learning the craft), you probably know Python.

 

But do you know PYNQ (as in PINK)?

 

PYNQ is an open-source framework that makes programmable SoCs easier-to-use and more accessible to new FPGA users through a browser-based development environment for Python.

 

Sound interesting?

 

Want to learn more?

 

Then attend our PYNQ webinar on May 8th, called: Unlock the Power of FPGAs through Python: Building Reconfigurable Embedded Systems with PYNQ

 

If you attend the webinar, you'll learn how to get a free PYNQ-Z2 boardPYNQ-Z2 board

 

 

Don't forget to take the PYNQ Poll!!!

Parents

  • I'm not a huge fan of Python and it does seen a strange match for FPGA development. I'll be watching the webinsr with interest to see if I can be convinced.

     

    The hardware looks nice, but I assume that the PYNQ framework will run on any Zync board such as the MiniZed

  • in reply to Fred27

    [Python] does seen a strange match for FPGA developmentIt does seem like a strange match up at first, but not so much when you see how it works together. Python isn't used for developing the FPGA, or what the Zynq calls the "programmable logic" layer. IP is still developed using the Xilinx Vivado toolchain.

     

    Python is used to load overlays which contain the FPGA/PL IP. It then acts as the glue between the hard ARM-A9 core and the FPGA core.

     

    In that context, Python makes much more sense. FPGA blocks are developed in VHDL/Verilog/RTL/HLS/etc. Code on the application processor, with the PYNQ image, runs Python under linux. The tight bindings accelerates gluing a hardware FPGA operation to a software function. The main example I looked at was OpenCV. The FPGA/PL layer communicates with HDMI and USB passing data over to the ARM processor. There, some Python code uses OpenCV to do facial recognition. It takes about 20 lines of Python code to make it work.

Comment
  • in reply to Fred27

    [Python] does seen a strange match for FPGA developmentIt does seem like a strange match up at first, but not so much when you see how it works together. Python isn't used for developing the FPGA, or what the Zynq calls the "programmable logic" layer. IP is still developed using the Xilinx Vivado toolchain.

     

    Python is used to load overlays which contain the FPGA/PL IP. It then acts as the glue between the hard ARM-A9 core and the FPGA core.

     

    In that context, Python makes much more sense. FPGA blocks are developed in VHDL/Verilog/RTL/HLS/etc. Code on the application processor, with the PYNQ image, runs Python under linux. The tight bindings accelerates gluing a hardware FPGA operation to a software function. The main example I looked at was OpenCV. The FPGA/PL layer communicates with HDMI and USB passing data over to the ARM processor. There, some Python code uses OpenCV to do facial recognition. It takes about 20 lines of Python code to make it work.

Children