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
  • 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 & Tria Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
PicoZed Hardware Design Picozed 7015 + Carrier Card + Gig SFP
  • 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 6 replies
  • Subscribers 338 subscribers
  • Views 1177 views
  • Users 0 members are here
Related

Picozed 7015 + Carrier Card + Gig SFP

Former Member
Former Member over 10 years ago

Hello All,

I'm attempting to use the Xilinx 1g/2.5g PCS/PMA to connect a Finisar SFP module in the SFP slot of the carrier card to the PS GEM1 on a Picozed 7015. My design is similar to that of xapp1082 but adapted to the picozed.

I'm using Vivado 2015.2, and a new picozed 7015 and carrier card.

The carrier card has been configured to output a 125Mhz clock (mgtrefclk1). The independent clock for the core is being provided by the PS oscillator (200MHz). Both clocks have been verified by externally connecting a scope.

I've been working on this for several weeks and am encountering a persistent issue where the transceiver GTP PLL0 fails to stay locked ONLY when the SFP is inserted in the slot.

I originally thought the core was sending a reset signal to the PLL so i implemented the PLL in the example design and removed the reset connection between the PCS/PMA and the PLL and tied it to gpio so that I could manually reset the PLL. In this configuration, I can reset the PLL and it is again stable until the SFP is inserted, at which point the PLL locked signal will begin to toggle.

I have 2 carrier cards and 2 picozeds, and this behavior is exhibited on both.

I've also got several SFP's. The finisar copper sfp's cause the pll to disconnect instantly upon being connected. (or the pll never maintains a lock if the sfp was in the slot when the board was powered on). The finisar fiber (850nm) sfp's can be inserted without disrupting the lock but will once an optical input is tied to the sfp rx port, then the lock will be lost. I have dozens of SFP's and I've connected several different ones and the behavior is the same with every one I've tried.

At this point, I'm wondering if anyone out there has managed to use the SFP port on the carrier card (I can't possibly be the first?!). I'm a computer programmer and relatively new to FPGA design and I therefore don't discount the possibility that there may be a flaw in my bitstream.

Any wisdom would be appreciated. 





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

    Mark,

    The video was very helpful.  Thank you for posting that.
    I notice you are running the Linux version of the tools.  Just out of curiosity, what is the default language of your operating system?  We've see the non-refreshing issue and it seemed to be more prevalent with Linux using a non-English, however can be an issue under Windows again, without English as it's default.

    Can you tell me what position JP6 is setup as?  Is there a jumper installed?  That MUX would prohibit the clock 1 from getting to the PicoZed if configured incorrectly.  The Jitter Attenuator has a straight shot into the PicoZed MGTREFCLK0. (this is on page 3 of the PicoZed Rev C Carrier card schematic).
    [ http://picozed.org/support/documentation/4701 search Schematics ] I am mostly asking to get the complete picture as you stated your PZ7030 is working just fine.

    Were you able to perform the rework listed in the Errata? Same webpage as above, search [PicoZed FMC Carrier Card Rev C Errata].  I searched our thread and do not see the word Errata, so I think I did not mention it and you may not have had the rework performed.

    There is a possibility that something went wrong when hot plugging the SFP module.  I have not personally tested that, as I always turn the power off before plugging/unplugging anything.

    I am rather happy to see that your 7030 is working fine.  Keep in mind, that board has the Zynq 7030 SoC on it, which uses the MUCH more robust GTX transceivers.  As such my proposed poor quality clock suggestion might be why you have a 7015/7030 difference (see errata doc).

    A few of the reworks listed will include some signal integrity issues but most related to the transceivers are for clock quality issues.  Without those reworks my 7015 would struggle to work as well.

    I think we should be getting close to the end at this point.  Let me know what you find and if needed, we can take the next step.

    --Dan

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

    Mark,

    The video was very helpful.  Thank you for posting that.
    I notice you are running the Linux version of the tools.  Just out of curiosity, what is the default language of your operating system?  We've see the non-refreshing issue and it seemed to be more prevalent with Linux using a non-English, however can be an issue under Windows again, without English as it's default.

    Can you tell me what position JP6 is setup as?  Is there a jumper installed?  That MUX would prohibit the clock 1 from getting to the PicoZed if configured incorrectly.  The Jitter Attenuator has a straight shot into the PicoZed MGTREFCLK0. (this is on page 3 of the PicoZed Rev C Carrier card schematic).
    [ http://picozed.org/support/documentation/4701 search Schematics ] I am mostly asking to get the complete picture as you stated your PZ7030 is working just fine.

    Were you able to perform the rework listed in the Errata? Same webpage as above, search [PicoZed FMC Carrier Card Rev C Errata].  I searched our thread and do not see the word Errata, so I think I did not mention it and you may not have had the rework performed.

    There is a possibility that something went wrong when hot plugging the SFP module.  I have not personally tested that, as I always turn the power off before plugging/unplugging anything.

    I am rather happy to see that your 7030 is working fine.  Keep in mind, that board has the Zynq 7030 SoC on it, which uses the MUCH more robust GTX transceivers.  As such my proposed poor quality clock suggestion might be why you have a 7015/7030 difference (see errata doc).

    A few of the reworks listed will include some signal integrity issues but most related to the transceivers are for clock quality issues.  Without those reworks my 7015 would struggle to work as well.

    I think we should be getting close to the end at this point.  Let me know what you find and if needed, we can take the next step.

    --Dan

    • 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