Adam Taylor’s MicroZed Chronicles – Pmods!

If you haven’t heard of Adam Taylor’s MicroZed Chronicles, it’s a tutorial-style blog series hosted by the Xcell Daily Blog that’s all about using, you guessed it, the MicroZed board! With a staggering 200 posts and counting, the series covers a very wide range of topics and now includes a dedicated post on using Pmods!

Because Pmods appear frequently throughout the MicroZed Chronicles, Adam decided to dedicate a tutorial solely to illustrating their use. He writes,

“Over the length of this series, we have looked at several different development boards. One thing that is common to many of these boards: they provide one or more Pmod (Peripheral module) connections that allow us to connect small peripherals to our boards. Pmods expand our prototype designs to create final systems. We have not looked in much detail at Pmods but they are an important aspect of many developments. As such, it would be remiss for me not to address them.”

He goes on to discuss the Digilent Pmod Standard as an open source and very useful standard for expanding the functionality of development boards, pointing to the wide range of Pmods available as one of their useful features.

Another useful feature of Pmods that Adam points to is the support, noting that there is a wide range of existing drivers for use with both PL (programmable logic) and PS (processing system) designs. He writes,

“This Digilent Vivado library contains several Pmod drivers and DVI sinks and sources plus other very useful IP blocks that can accelerate our design.”

If you’re interested in Adam’s brief tutorial on how to get Pmods up and running quickly on Zynq-based boards using Digilent’s Pmod IP cores, see his post here. For a more step by step tutorial on how to start a Zynq or Microblaze design and integrate Pmods, see Digilent’s tutorial titled Using Pmod IP’s.

For any questions or comments please use the comment section below or visit the Digilent Forum!


Be the 1st to vote.

Leave a Reply

Your email address will not be published. Required fields are marked *