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 & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
    About the element14 Community
  • 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
      •  Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      •  Vietnam
      • 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 & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
MicroZed Hardware Design How does Zynq/MicroZed look for SD
  • 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 362 subscribers
  • Views 492 views
  • Users 0 members are here
Related

How does Zynq/MicroZed look for SD

hai.bi
hai.bi over 10 years ago

I have a MicroZed and use the jumper to let it boot from SD.  MicroZed configures to use MIO40-45 but how does the Zynq knows it is 40-45 before it loads FSBL from SD?

Does it look through all SD possible connections to see where SD card is there and to see whether the file is in the SD card?  So what if I have two SD slots does it mean it will use the first FSBL it finds?  Regards,

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

    The Zynq device, as detailed in the Zynq Technical Reference Manual, chapter 6 ( http://www.xilinx.com/support/documentation/user_guides/ug585-Zynq-7000-TRM.pdf ) reads the mode pins at boot time and selects one of five predetermined boot devices: NOR, NAND, Quad-SPI, SD Card, or JTAG.

     

    The MicroZed implements three of these options: QSPI, SD Card, and JTAG. Take a look at the MicroZed HW Users Guide for details: 

    http://zedboard.org/support/documentation/1519

     

    The SD Card interface on the MicroZed is implemented on the default MIO pins so that the Zynq knows where to access and boot from. You can implement an additional SD Card interface using the MicroZed expansion connectors but the primary boot device must be either the QSPI Flash, the default SD Card interface, or the JTAG interface as determined by the configuration mode jumpers.

     

    You could use a secondary SD Card interface as a secondary boot device if your FSBL code were to configure it and start a Second Stage Boot Loader.

     

    You might want to take a look at the Avnet Zynq SW and HW Speedway workshop material, it will give you a detailed description of the Zynq internals. There are also hands on labs that target the ZedBoard and the MicroZed.

    Developing ZynqRegistered-7000 All Programmable SoC Software (Vivado 2013.3 and 2014.4.1)
    Developing ZynqRegistered-7000 All Programmable SoC Hardware (Vivado 2013.3 and 2014.4.1)
     

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • hai.bi
    0 hai.bi over 10 years ago in reply to Former Member

    So the default SD IOs are 40-46.  If that is the case, then I understood now.  It is kind of bad luck to me then, since I need USB1 as well so I have to move the SD to elsewhere.  Then you are saying the Zynq will not find my new SD0 since it is on EMIO and it has to get the FSBL to know where it is while the FSBL is on my new SD card.

    So is there any way I can have both USB, and boot from SD card?

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

    It is the multiplexed nature of the Zynq MIO pins that you cannot have all of the peripherals at one time. Take a look at Table 2-4 in the Zynq Technical Reference manual or the Zynq Speedway material for an illustration.

     

    You are going to be constrained to the trade-offs we made for the MicroZed. We would have needed to give up either QSPI or Ethernet to implement two USB ports on the MIO ports. For most customers this is the best trade-off. So the hardware implemented on the MicroZed will not support USB1 via MIO in any case. The SD0 interface is hardwired on the MicroZed.

     

    You might be able to implement USB1 on a Carrier Card via EMIO but you would need to be very careful to meet the very stringent layout requirements for the signals to a USB PHY.

     

    -Gary

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • hai.bi
    0 hai.bi over 10 years ago

    Gary, appreciate your help here.  I printed the Table 2-4 which is definitely helping a lot. 

    Looks like MicroZed is still a good candidate for my project, and PicoZed a potential one.  I like Gigabit Ethernet0 and USB0 device on MicroZed.  I hope to  use second Ethernet (10/100 through eMIO).

    • 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 © 2026 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