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
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
Using Xilinx Tools Forum Pmod using SDK
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Avnet Boards Forums to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 335 subscribers
  • Views 355 views
  • Users 0 members are here
Related

Pmod using SDK

Former Member
Former Member over 12 years ago

Hi all,

I am trying to access PMODs which are connected to PL. Which header files am I suppose to include in Xilinx SDK 14.2? Any other header files should I look? I will appericiate any other information regarding accessing PMODs.

  • Sign in to reply
  • Cancel
  • bhfletcher
    0 bhfletcher over 12 years ago

    The default hardware platform built into the Xilinx tools for ZedBoard does not include any Pmod information.  Given the diversity of available Pmods out there, it's a bit unpredictable as to what people might plug in.  To add a Pmod to ZedBoard will require you to modify the hardware platform with IP in the PL to interface to the Pmod of your choice.  You will also need to modify the UCF.  After doing this, when you export the new hardware platform, it will include the drivers in the BSP for the new Pmod peripheral assuming you have either used a built-in IP or properly added your custom driver to the project.

     

    Do you have a particular Pmod in mind?  I'm curious what you would find useful.  Perhaps we would add this to the list of example projects we are creating.

     

    Bryan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 12 years ago in reply to bhfletcher

    Hi Bryan,

    I am thinking either JA1 or JB1. All I want to do is to use a simple LED module and make it work on either of those 2 PMODs. All PMODs are included in UCF file. I need to map PMODs in XPS and then after exporting hardware to SDK I just need to include correct header files(I'm guessing xgpio.h and xparameters.h) and write a C code. Am I right? I don't have any tutorial or some reference on how to do this.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • bhfletcher
    0 bhfletcher over 12 years ago

    The I/Os on JA1 and JB1 come from the PL.  The hardware to drive an LED is a GPIO.  Here is the process to do what you want.  I would highly recommend you go through the Zynq Intro course that we have posted on this website.  It goes through this process nearly identically with the exception that the GPIO gets tied to on-board LEDs and push-buttons.  Starting from the design provided in the Intro, you would just need to change the pin mapping in the UCF for the LEDs to be the Pmod I/Os rather than the on-board LEDs.

     

    If you have a basic "Hello World" platform up and running, here are the steps to add an LED controllable by the ARM:

    1.   From PlanAhead, edit your embedded system, which will launch XPS
    2.   In XPS, add the GPIO hardware that will drive the LED.  You have two choices here  
          
      •     Use the PS GPIO mapped through EMIO to the PL I/Os on the Pmods.  This method is probably the most logical as it uses the built-in GPIO controller.  However, our Intro tutorial had an objective to show a peripheral in PL, so it uses the next method.
      •   
      •     Instantiate a GPIO peripheral in the PL and configure it to drive outputs
      •  
    3.   Back in PlanAhead, edit your top-level HDL (system_stub in the Intro course) to connect your GPIO peripheral ports to top-level ports
    4.   Edit the UCF.  Rename the JA1/JB1 I/Os to match your top-level ports.
    5.   Export the design to SDK
    6.   SDK should recognize the new hardware platform and rebuild the BSP.  Since you have used the Xilinx built-in GPIO peripheral (either the PS GPIO or the axi_gpio in PL) the BSP will automatically include a driver.  If you ever design your own custom peripheral in hardware, you would also have to write your own driver
    7.   Write your software to exercise the GPIO

    Hopefully that helps.  Again, the Intro training goes through all of this step-by-step.  The only exception would be you would change the LED mapping in the UCF to the Pmod, and modify the software.

     

    Bryan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 11 years ago

    Hello,
    was just wondering if you could post a demo with 4 PMOD MICs on a zedboard with the ADC linked to the PL and PS.
    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
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