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 SDR Software-Defined Radio PicoZed SDR 7035/AD9361 SOM / Sync'ing multiple AD9361 devices
  • 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 6 replies
  • Subscribers 323 subscribers
  • Views 886 views
  • Users 0 members are here
Related

PicoZed SDR 7035/AD9361 SOM / Sync'ing multiple AD9361 devices

Former Member
Former Member over 10 years ago

Many applications call for synchronized multiple RF inputs/outputs (MIMO), including phase array processing, beamforming, adaptive antennas, etc.

As described in http://wiki.analog.com/resources/eval/user-guides/ad-fmcomms5-ebz/multi-chip-sync, there are (2) aspects to synchronizing multiple AD9361u2019s across PicoZed SDR SOMs.

u2022tSample clock Synchronization

otEach AD9361 includes its own baseband PLL that generates sampling and data clocks from the reference clock input. A logical SYNC_IN pulse input is needed to align each deviceu2019s data clock with a common reference. On PicoZed 7035/AD9361 SOM, the AD9361 'SYNC_IN' (pin H5) is connected to / driven from Z7035 IO_L10_35_SYNC_IN (pin G15).

u2022tRF (LO) Synchronization
otThe AD9361 does not include RF synchronization internally. Techniques to resolve phase difference of the RF PLLs across different AD9361 are discussed in http://wiki.analog.com/resources/eval/user-guides/ad-fmcomms5-ebz/multi-chip-sync.

At this time the PicoZed SDR FMC carrier card is not intended to have more than one SOM. Therefore there is no (simple) connection to drive a common SYNC_IN to multiple SOMs / AD9361. Future PicoZed SDR carriers may provide such functionality.

It might be possible to drive a replica of u2018SYNC_INu2019 from the Zynq down through a custom PMOD output on a u2018masteru2019 carrier, then over a custom cable to a PMOD input of a u2018slaveu2019 carrier, and finally from Zynq to the u2018slaveu2019 AD9361 SYNC_IN. Skew would need to be somehow matched across the master / slave SYNC_IN signals. However, this isnu2019t a use case that we have specifically planned for. The user would need to do some experimentation.

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

    Forgive my ignorance in this field, and take note that I don't have any experience with clocking multiple devices yet.

    With that being said, I was just starting to look into this kind of thing today (syncing event timing across multiple devices). I'm wondering if you couldn't just use IEEE 1588 (Precision Time Protocol) in order to generate a SYNC_IN pulse across multiple devices.

    reference: http://www.wiki.xilinx.com/Zynq-7000+AP+SoC+-+Precision+Timing+with+IEEE1588+v2+Protocol+Tech+Tip

    Perhaps this is meant for use across "devices" of a higher computational order with greater (spatial?) separation, or maybe only using an ethernet-type link... but if they've already solved this problem before, I figure the logic of how to do it might be very similar.

    Just some thoughts in the off chance that it helps.

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

    Forgive my ignorance in this field, and take note that I don't have any experience with clocking multiple devices yet.

    With that being said, I was just starting to look into this kind of thing today (syncing event timing across multiple devices). I'm wondering if you couldn't just use IEEE 1588 (Precision Time Protocol) in order to generate a SYNC_IN pulse across multiple devices.

    reference: http://www.wiki.xilinx.com/Zynq-7000+AP+SoC+-+Precision+Timing+with+IEEE1588+v2+Protocol+Tech+Tip

    Perhaps this is meant for use across "devices" of a higher computational order with greater (spatial?) separation, or maybe only using an ethernet-type link... but if they've already solved this problem before, I figure the logic of how to do it might be very similar.

    Just some thoughts in the off chance that it helps.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
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