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 IDT Programming Using Avnet Reference Design
  • 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 7 replies
  • Subscribers 322 subscribers
  • Views 785 views
  • Users 0 members are here
Related

IDT Programming Using Avnet Reference Design

nima_taie
nima_taie over 8 years ago

I am following Avnet reference design from Github to change the frequency of the U13 which is IDT 8T49N242. Everything goes OK, and I get the message IIC EEPROM Test: PASSED message at the end, however, after I power cycle, I still don’t have new clock frequency from the IDT device.

The reference design is programming the EEPROM which is U14, and it is at address 0xA0. However, the  slave address which is indicated in the pzcc_iic_eeprom_test.c source file is at 0x50. I tried to change it to 0xA0, but then the EEROM test fails. After programming the EEPROM, is there anything else I need to do? Why am I not getting the frequency which I want?

I am using Vivado 2015.4 as the reference design requires.

  • Sign in to reply
  • Cancel
Parents
  • nima_taie
    0 nima_taie over 8 years ago

    Hi Dan,

    Let me give you more background on what I am trying to do with the Picozed, and V2 Carrier Board. 

    I am using Picozed board as a PCIe root complex - however, the carrier board is designed to be an end-point PCIe for Picozed. The PCIe REFCLK on PCIe edge are inputs to the IDT and FPGA high speed transceivers. I need to provide a reference clock to both FPGA pins, and also PCIe Edge connector. 

    I was hoping to use the output from IDT device to provide a clock to both FPGA and PCIe. I wanted to route TP33/34 or TP35/36 to the pads of R106 after removing R106. The reason for removing it was that PCIe end point devices has the 50Ohm termination. 

    I see your point in using different clock values at output of Q0-Q2. However, I don't see any activity. Not even a glitch. I have also changed the output type from HCSL to LVDS, but still no activity. 

    I noticed on IDT's data sheet for the clock device, Q0 and Q1 are using CLK0 and CLK1 as reference inputs. I don't have CLK0 and CLK1, but I have changed their input source using Timing Commander to be Q3 rather than Q0 in the PLL section. 

    Anyway, I am planning to go off-board to a PCIe end-point device hence the need to for HCSL output. 

    What is your recommendation for PCIe REF Clk then? I need to pair of clocks for FPGA MGTs, and one pair for PCIe reference clock on edge? 

    Thanks,

    Nima

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

    Hi Dan,

    Let me give you more background on what I am trying to do with the Picozed, and V2 Carrier Board. 

    I am using Picozed board as a PCIe root complex - however, the carrier board is designed to be an end-point PCIe for Picozed. The PCIe REFCLK on PCIe edge are inputs to the IDT and FPGA high speed transceivers. I need to provide a reference clock to both FPGA pins, and also PCIe Edge connector. 

    I was hoping to use the output from IDT device to provide a clock to both FPGA and PCIe. I wanted to route TP33/34 or TP35/36 to the pads of R106 after removing R106. The reason for removing it was that PCIe end point devices has the 50Ohm termination. 

    I see your point in using different clock values at output of Q0-Q2. However, I don't see any activity. Not even a glitch. I have also changed the output type from HCSL to LVDS, but still no activity. 

    I noticed on IDT's data sheet for the clock device, Q0 and Q1 are using CLK0 and CLK1 as reference inputs. I don't have CLK0 and CLK1, but I have changed their input source using Timing Commander to be Q3 rather than Q0 in the PLL section. 

    Anyway, I am planning to go off-board to a PCIe end-point device hence the need to for HCSL output. 

    What is your recommendation for PCIe REF Clk then? I need to pair of clocks for FPGA MGTs, and one pair for PCIe reference clock on edge? 

    Thanks,

    Nima

    • 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