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 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 Boards Community
  • Avnet Boards Forums
  • More
  • Cancel
Avnet Boards Forums
MicroZed Hardware Design Program FPGA failed when FMC (DC1532A-L) plugged into FMC-Carrier Card
  • 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 11 replies
  • Subscribers 333 subscribers
  • Views 2292 views
  • Users 0 members are here
Related

Program FPGA failed when FMC (DC1532A-L) plugged into FMC-Carrier Card

nowksru
nowksru over 6 years ago

Hello,

I am trying to program the MicroZed through the FMC-Carrier Card via JTAG, while the FMC module DC1532A-L (Linear Technology) is plugged in the Carrier Card. But when I click on the Program FPGA button in Xilinx SDK (2017.4) I get the following error message:

"Could not find FPGA device on the board for connection 'Local'.

Troubleshooting hints:
1. Check whether board is connected to system properly.
1. In case of zynq board, check whether Digilent/Xilinx cable switch settings are correct.
1. If you are using Xilinx Platform Cable USB, ensure that status LED is green.
Program FPGA failed"

If I unplug the FMC module from the Carrier Card, SDK runs the programming without a problem --> board is connected to system properly and status LED is green in both cases (FMC module plugged in & unplugged). I guess the FMC module is somehow interfering with the JTAG pins?
 

I don't know if it is important, but my application is just reading registers on the FMC module through SPI.
 

-Urs


 

  • Sign in to reply
  • Cancel

Top Replies

  • jafoste4
    jafoste4 over 6 years ago +1
    Hi Urs, I believe your right. This makes sense. As far as the best way to tie these pins together. My suggestion would be to break out your soldering iron and modify the MicroZed FMC Carrier Card. Looking…
Parents
  • jafoste4
    0 jafoste4 over 6 years ago

    Hi Urs, 

    I see what you are saying now. Thanks for clarifying. Please make sure the VADJ is set correctly on your Carrier Card to account for the FMC's required IO voltage.

    -Josh

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

    Hi Josh,

    I already checked the VADJ and set it to 1V8 as the module expects 1.8V. I also checked my constraints in Vivado, which I set to 1.8V. But I still don't see how a plugged in module can block the programming sequence or even the detection of the MicroZed.

    By the way, this is the error (from the TCL console) I get from Vivado Hardware Manager when trying to program the Microzed on the FMC-CC:

    open_hw_target
    INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210299A56456
    ERROR: [Labtools 27-2269] No devices detected on target localhost:3121/xilinx_tcf/Digilent/210299A56456.
    Check cable connectivity and that the target board is powered up then
    use the disconnect_hw_server and connect_hw_server to re-register this hardware target.
    ERROR: [Common 17-39] 'open_hw_target' failed due to earlier errors.

     

    -Urs

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

    Hi Josh,

    I already checked the VADJ and set it to 1V8 as the module expects 1.8V. I also checked my constraints in Vivado, which I set to 1.8V. But I still don't see how a plugged in module can block the programming sequence or even the detection of the MicroZed.

    By the way, this is the error (from the TCL console) I get from Vivado Hardware Manager when trying to program the Microzed on the FMC-CC:

    open_hw_target
    INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Digilent/210299A56456
    ERROR: [Labtools 27-2269] No devices detected on target localhost:3121/xilinx_tcf/Digilent/210299A56456.
    Check cable connectivity and that the target board is powered up then
    use the disconnect_hw_server and connect_hw_server to re-register this hardware target.
    ERROR: [Common 17-39] 'open_hw_target' failed due to earlier errors.

     

    -Urs

    • 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