element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Members
    Members
    • Achievement Levels
    • Benefits of Membership
    • Feedback and Support
    • Members Area
    • Personal Blogs
    • What's New on element14
  • Learn
    Learn
    • eBooks
    • Learning Center
    • Learning Groups
    • STEM Academy
    • Webinars, Training and Events
  • Technologies
    Technologies
    • 3D Printing
    • Experts & Guidance
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Arduino Projects
    • Design Challenges
    • element14 presents
    • Project14
    • Project Groups
    • Raspberry Pi Projects
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Or 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
Avnet Boards Forums
  • Products
  • Dev Tools
  • Avnet Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
MicroZed Hardware Design PUDC_B pin
  • Forum
  • Documents
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Avnet Boards Forums requires membership for participation - click to join
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 177 subscribers
  • Views 1619 views
  • Users 0 members are here
Related

PUDC_B pin

Former Member
Former Member over 7 years ago

Hello everyone,

 

According to Zynq TRM, the PUDC_B pin must not be left floating. I agree with that but I am understanding that it is for a design in which only the Zynq chip is used. Am I rigth?

In case of a custom carrier card for inserting a Microzed board, is there any problem to drive this specific pin in the microheader as an input signal? I have read that one must be careful but, in what way? I mean, all the commercial carriers have a specific circuit with a jumper to select the PUDC_B status, however, the Microzed already has its own circuit to pull this signal up or down, so what is the need to drive this signal on both boards instead of using this pin as an additional external signal as I have in mind?

 

Thank you

 

Víctor

  • Sign in to reply
  • Cancel
  • drozwood90
    0 drozwood90 over 7 years ago

    Victor,

    You will find this signal on every Xilinx chip that has PL (programmable logic).  All of the series 7 have that pin.  That pin is used to set the default boot settings of the PL pins.

    So to answer your question, no, you are not right, you will find that pin on any chip with PL.
    Please see this AR for more information:
    http://www.xilinx.com/support/answers/50802.html

    You can use this pin as an input, however there are complexities involved in this.  You need to take care to not drive the pin prior to the bank being powered, you also will need to ensure that the circuit driving the pin does not change the pull-up or down the pin is set to.
    Please see UG470 for more information regarding this pin:
    http://www.xilinx.com/support/documentation/user_guides/ug470_7Series_Config.pdf
    Take a look at Table 2-4 (document page 27).  You will see warnings and the complexities to use this pin listed in the description.

    There is no need to drive this pin on both boards.  The pin only needs to be set at boot.

    --Dan

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Former Member
    0 Former Member over 7 years ago
    Hello Dan,
     
    Thank you for your reply.  
     
    Now I understand that this pin requires a stable state in any point of the net at boot, so definitely it is better not to 
    use it as an input in my design.
     
    But now the doubt is: by default, on MicroZed, PUDC_B is pulled high via a resistor (JT4) disabling the pull-ups during configuration and according to what is commented in the following post about the PUDC_B signal:
     
    http://zedboard.org/content/zynq-pins-deep-dive
     
    It is indicated "If pulled high, then all pins will effectively be floating and external loading will dictate their state." then I would need an external signal to drive the I/O pins so that if I want them to be always low at boot, would I have to connect the PUDC_B pin in the Microheader to GND? Is it what is pretended for example, with the PUDC selection circuit in the IO carrier card?
     
    Regards
     
    Víctor
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • drozwood90
    0 drozwood90 over 7 years ago

    Victor,

    Per the AR listed above:
    "When PUDC_B is High, internal pull-up resistors are disabled on each SelectIO pin. The state of this pin effects the state of the I/O from power-on until configuration completes. Therefore, the I/Os will be 3-stated after power-on when PUDC is High."

    This means they are tri-stated.  They can be "set" easily by using external signaling.  Once configuration is complete, whatever you set the pins to in your bin file will dictate their state.  As such, tri-stated is the safer of the two options provided by the fabric for MOST cases.  In this case, it will be DRIVEN neither HIGH nor LOW.  It will be HIGH impedance with a VERY weak pull-up.  Once configuration is complete, the pin will be defined as whatever you set it to.

    If your circuit cannot accept the pins being tri-stated for a small period of time, and you need the signaling to be LOW, you will need to have something external to the signals pulling them low.  Only if you need the signals to be pulled high, would I suggest you modify the PUD_B signal.  Note that modifications to the board are done at your own risk, and I would suggest using a reputable Board House or In-House talent.

    For this, typically your circuit has a reset or similar signal, pulling that ONE signal to the proper level is typically all that is needed as data lines / etc. will not matter when the entire circuit is being held in reset.

    Typically you want signaling to be high impedance or pulled HIGH, as are the two choices provided.  Most reset signals are active low due to the use of open-collectors as well as the signal integrity provided through DRIVING a reset signal.  You gain noise immunity in both the hard DRIVE and the "short" to ground using an open-collector.  You also gain a resistance to capacitive effects due to the drive and shorting.

    --Dan

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

    Hello Dan,

     

    Thank you for your reply and your detailed description.

     

    Definitely, I am going to dedicate this pin for its specific function. Would the best solution be to leave this pin floating in the Microheader, making use of the by-default very weak pull-up in the MicroZed, avoiding in this way any additional external circuit?

     

    Víctor

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • drozwood90
    0 drozwood90 over 7 years ago

    Hi there,

    If you check on page 6 of the schematic, it is noted to be a 1K pull up to the bank voltage. 

    If you do not need to change the Power Up Default State, or utilize that pin, the MicroZed is setup to boot properly with or without a board.  As such, you can just NO connect that pin on your carrier, that is if you do not need to use that IO.

    --Dan

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