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
PicoZed Hardware Design Changing the 33.33333MHz Oscillator
  • 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 Verified Answer
  • Replies 5 replies
  • Subscribers 323 subscribers
  • Views 1191 views
  • Users 0 members are here
Related

Changing the 33.33333MHz Oscillator

Former Member
Former Member over 7 years ago

We would like to remove the 33.33333 MHz oscillator to the Zynq and replace it with a better, pin compatible 40MHz oscillator. We've done the rework and the device boots up and we're getting the FPGA done light.

What I've noticed is that the UART clock now seems off, we're getting giberish on UART1 and ethernet no longer works. I presume the issue is that the FSBL and Linux don't know that the oscillator has chganged so something is messed up w/ the PLLs used to generate the baud and ethernet clocks.

I used the Zynq PS IP block to update the clock frequency to 40MHz, this in turn updated all of the dividers in the GUI. I re-generated the bitstream, exported to SDK to rebuild the FSBL, and re-imported the HDF file in petalinux and I am seeing the same problem. Checking the newly generated device tree shows 40MHz as the new clock frequency.

 

Did I miss a step somewhere? Do I need to update something else, besides the PS configuration? Attached is a screenshot of the PS configuration.

 

/sites/default/files/u14337/ClockConfig.PNG

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

    Hello rdemara,

    You say a 40MHz oscillator is better, more pin compatible. WIll you please point me to the documentation that suggest this for my own learning? Are you able to run hello world in baremetal witht he new clock?

    Thanks,

    Josh

    • 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 jafoste4

    Not "more pin compatible," I meant that the new oscillator is better (more stable) and is completely pin compatible with the 33.333 MHz osc. used on the picozed. The 33.333 MHz clock used on the picozed (according to the schematic) has a stability of +/-50ppm (if I'm reading the data sheet correctly), the 40MHz oscillator we replaced it with has a stability rating of +/- 2.5 ppm.

    Picozed Oscillator: ASDMB-33.333MHZ-LC-T (https://www.digikey.com/product-detail/en/abracon-llc/ASDMB-33.333MHZ-LC-T/535-13157-2-ND/2805071)

    Replaced Oscillator: 520-T2520-33-400 (https://www.digikey.com/product-detail/en/ecs-inc/ECS-TXO-2520-33-400-AN-TR/XC2260TR-ND/6578487)

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

    Hello rdemara,

    Looking at modifying the Zynq Parameters to account for this new clock. It shouldn't affect the Uart clock. This is quite strange. I am still looking into this.

    -Josh

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

    UART clocks are dependent on the frequency of the clocks that drive it.  If you are using the Board Definition File that Avnet generated, you will likely have issues as thet BDF is setup for 33.333MHz.  You will likely need to generate your own BDF or create a TCL that sets up all the processor / clock values based on your new clock frequency.

    You should also keep in mind that this clock feeds into a secondary PLL and clock tree that drives the Zynq PS and derives out to the PL clocks.  Without properly shifting that - separate from a BDF - there are likely going to be issues. 

    I would really suggest you go back to a 33.333MHz clock and if you do believe you need the +_2.5PPM, get a 33.33MHz clock that runs with that PPM drift.

    --Dan

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

    Super embarrassing... I discovered the issue. The problem was that the Picozed dip-switch settings were set to boot from QSPI/eMMC, not the SD card, which contained the new clock settings. Thanks for looking into this. Looks like updating the settings in the zynq configuration block and exporting to the SDK works fine.

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