Actions
Engagement
  • Author Author: tariq.ahmad
  • Date Created: Date Created
  • Last Updated Last Updated:
  • Views 4928 views
  • Likes 2 likes
  • Comments 74 comments
Related
Recommended

Webinar Poll:  What Programming Language Do You Like to Use?

Sign up for our Upcoming Webinar and Zero to Hero Workshop Series on PYNQ. 

 

PYNQ is an open source project started by Xilinx, which fuses the productivity of Python with the acceleration provided by programmable logic within the Zynq / Zynq MPSoC. Until recently, a programmable logic solution required advanced digital design skills which limited its accessibility to software developers.  PYNQ is a game-changer because it enables the performance of programmable logic provided by Xilinx heterogeneous SoCs to be leveraged using Python, without the need to learn the digital design skills.  Python is one of the most popular programming languages in the world, and a language that is very familiar to Pi enthusiasts.   Its also the second most popular language on the community, according to the poll below, trailing the C programming language and just ahead of the Arduino programming environment.

 

Python Productivity for Zynq, or PYNQ, has the ability to present programmable logic circuits as hardware libraries called overlays. These overlays are analogous to software libraries. A software engineer can select the overlay that best matches their application. The overlay can be accessed through an application programming interface (API). Using existing community overlays, this course will examine how a beginner can experiment with neural networks using PYNQ on Ultra96. The course will then point you to the best resources to begin your own PYNQ journey!

 

On April 8th, 2020 at 11 AM CT //  4 PM GMT: Join us as to learn more about Using Python Overlays to Experiment with Neural Networks from Fred Kellerman and Bryan Fletcher from Avnet:

 

Join us for a hands-on workshop with Adam Taylor, author of the MicroZed Chronicles, who will take you from Zero to Hero with using the PYNQ-Z2 board.  Over the course of three sessions, you'll learn everything you need to know to get started and build an embedded vision application.  No experience required.

 

What You'll Need to Participate:

 

This workshop combines 3 build-along workshops with Adam Taylor with "homework" assignments to do in between each session.   This gives you a chance to apply what you learned during the workshop while preparing you the next session.  Along the way you can earn badges for participation and a prize for the best finished project after the last session. You'll need the following tools to get started:

 

 

Win a $200 Gift Card:

 

In-between sessions, blog about your learning experience to win badges, free swag, and a chance to win one of three $200 Gift Card for completing your own embedded vision application.  To qualify you will need to do the following:

 

  • Attend all 3 sessions with Adam Taylor
  • Complete the build yourself
  • Create a project showing a unique application on top of the end workshop build

 

Session 1:

 

On May 5th, 2020 at 11 AM CT //  4 PM GMT: Join us for Part 1 of the PYNQ-Z2 Workshop: Getting Started with PYNQ:

 

Session 2:

 

On May 19th, 2020 at 11 AM CT //  4 PM GMT: Join us for Part 2 of the PYNQ-Z2 Workshop: Getting Up and Running with PYNQ:

 

Session 3:

 

On June 2nd, 2020 at 11 AM CT //  4 PM GMT: Join us for Part 2 of the PYNQ-Z2 Workshop: Getting Up and Running with PYNQ:

Parents

  • Python story for those who like to kill time reading random stuff that has a rant feel to it (all others ignore):

     

    I've picked up the main stream languages as they popped out since 82 or so.  When Python came along, I didn't mess with it for years.  I saw it in Blender, the 3D awesomeness program, as its script language, but it actually seemed intimidating from afar.  Little did I know, that was Blender that was intimidating - not as much Python.

     

    So, then I started working with the Raspberry Pi and found Python was everywhere.  I read about its current state and found it had developed a die hard following.  I thought, "what gives, good ole' VB could easily do all this if people made the libraries for it".  Also, VB is more friendly for the beginner - yet they are claiming Python is the easiest language to learn for beginners.  I thought "says, who?  The creator of Python?  Why are people spreading this propaganda?" 

     

    It stumped me for a few years why folks liked it until the coder for the Matrix Creator Raspberry Pi Daughter Board made Python work with it.  He made the statement "the code is just a big wrapper around the C++ code".  A light bulb went off. That's when I dug deeper.

     

    It finally hit me - Python IS just a wrapper on C/C++.  The dude back in the 90's just slapped a simple interpreter to make C library calls to libraries that had been around for years.  It was no different than the simple markup language style interpreter I wrote for my Amiga Genlock video overlay software back then.  It made it much faster to produce something, but relied 100% on the software that came with it.

     

    To me, Python got its fame by bootlegging of all the hard work those people who made the C libraries to immediately claim fame as a new "language".  Yes, if you have no helper functions to help be proficient with common tasks that you made over the years, it is quicker to script up calls to awesome library functions with Python- but it's really just a dirty little, slow processing hack.

     

    Regardless, I now accept that it is here to stay that is for sure.  I wish BASIC would have just held it's own.  So, now, for me, when I cobble a solution from Python examples, the end goal is to port to C or C++ and compile for the final solution.

     

    Thanks - had to get that off my chest so I stop talking about it so much at the dinner table.  :-)

     

    -Sean

  • in reply to Sean_Miller

    An interesting interpretation of Python (...get it image).

     

    That's why I'm intrigued about Go:

     

    from their documentation...

    Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language.

Comment
  • in reply to Sean_Miller

    An interesting interpretation of Python (...get it image).

     

    That's why I'm intrigued about Go:

     

    from their documentation...

    Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language.

Children
No Data