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
ZUBoard Why is the ZUBoard not SYZYGY Compliant?
  • 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 0 replies
  • Subscribers 328 subscribers
  • Views 905 views
  • Users 0 members are here
  • syzygy
  • compliance
  • ZUBoard
Related

Why is the ZUBoard not SYZYGY Compliant?

TWMIV
TWMIV over 2 years ago

I am actively interested in purchasing this eval board, both for access to a ZU1CG along with SYZYGY compatibility with modules I am working on.

On the SYZYGY's group webpage as of Feb/18/2023 (https://syzygyfpga.io/carriers/), the ZUBoard 1CG has a note next to it stating:

" IMPORTANT: This product IS NOT SYZYGY Compliant. "

Can AVNET provide any insight into this, seeing as functionality with this ecosystem is a large selling point for this product and the trademark is used in the product description and marketing material? My take away is peripherals will work assuming the end user makes SURE that the voltages are compatible before plugging them in.

From what I have been able to ascertain, the compliance issue stems from the lack of "SmartVIO" support, see 4.2.1 VIO Supply in the SYZYGY specifications V1.1. The spec seems to require that the VIO that is provided to the SYZYGY peripherals be adjustable on the carrier side to match what is needed by the peripherals if required. The ZUBoard seems to just hook a voltage rail to the VIO pin 39, and provide a fixed voltage, 1.8 V to port A, and 1.2 V or 1.8 V to ports B and C, where these are required to be independent adjustable supplies.

Additionally, the spec requires that the VIO rails be the last supply provided to the peripherals in the start up sequence. This was likely done to ensure that too high a voltage was never given to a device. Section 4.3 of the specifications outlines this.

I looks like adding 3x adjustable fs1406's to the board near the SYZYGY ports and connecting them to the same i2c bus could allow the SYZYGY state machine to control the VIO supplies and seemingly obtain SYZYGY compliance.

Also, feedback on the schematics. Consider adding notes for expected current draw on different rails, Vdiv notes for fixed supplies, voltage drop information near beads and any high current planes, and beads to help keep noise out of different areas when one rails is feeding many different functional blocks (see power supply page).

  • Sign in to reply
  • 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