element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • 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
MicroZed Hardware Design MicroZed Microheader Configuration
  • 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 3 replies
  • Subscribers 308 subscribers
  • Views 303 views
  • Users 0 members are here
Related

MicroZed Microheader Configuration

Former Member
Former Member over 9 years ago

Hi Guys,

Apologies for asking a stupid question but I have tried searching everywhere and cannot find an answer.

I want to control the PL GPIO from Xilinx SDK. All tutorials show how to do similar using PS MIO which is nice and easy. I can't work out how to configure the hardware design so that I can access JX1 and JX2 microheaders. My understanding leads me to believe that I will need an AXI_GPIO block, but I am unsure of how to configure it such that it points to JX1 or JX2.

Thanks in advance for any help,

Stephen

  • Sign in to reply
  • Cancel
  • Former Member
    0 Former Member over 9 years ago

    I think I worked it out through perseverance. Posting my (hopeful) basic solution for if anyone else stumbles across this stuck. Please correct me if I am wrong.


    Ok. The microheaders, JX1 and JX2 are I/O connected to the PROGRAMMABLE LOGIC. In a Zynq, to control programmable logic I/O with the processing system, you need an AXI interface, and an AXI GPIO module. That GPIO module must then have a port connected to it, and that port must be mapped (in the VIVADO PROJECT CONSTRAINTS) to the actual physical pin on JX1 or JX2. 'http://imgur.com/0ap9eQx' shows what the Vivado hardware block diagram must look like, to enable the use of a SINGLE port on JX1. The constraints file must contain the following HDL:

    set_property PACKAGE_PIN R19 [get_ports {GPIO_Out}];
    set_property IOSTANDARD LVCMOS18 [get_ports -filter { IOBANK == 34 }]

    IOBANK == 34 is because JX1 is connected to Bank 34. Pin R19 was arbitrarily chosen. GPIO_Out is the name of the port in the Vivado HW schematic. IOSTANDARD LVCMOS18 means the VccIO will be 1.8V, so the VccIO jumper on the breakout board must be placed to reflect this.

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

    http://i.imgur.com/0ap9eQx.jpg

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

    Stephen,

      Thanks for sharing your results! Also, I think this same topic is one of many topics covered in the free Zynq Intro trainings available here:

       http://microzed.org/support/trainings-and-videos

     

    Bryan

    • 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