Actions
Forum Thread Details
  • State Not Answered
  • Replies 2 replies
  • Subscribers 177 subscribers
  • Views 96 views
  • Users 0 members are here
Related

Programming MicroZed FPGA from SDK 14.7 fails

jesusmgonzalez


Hi!

Hi followed the previous steps to get a hardware design using old tools ISE14.7 from this link:
http://zedboard.com/node/add/forum/69

I worked around this proposal, and successfully got the bitstream to export to XSDK. Then, I tried to program the FPGA of the MicroZed board with the external programmer (driver correctly installed, green led), and got this error message (at the end of programming):

"Program FPGA Failed: Failed to download the bit file"
"DONE bit didn't go HIGH after programming FPGA"

Does anybody know how to overcome this problem?

  • 0

    The link you provided does not work, so it is difficult to determine the issue but there are a couple of things to look at.

     

    Verify that your design targets the MicroZed board that you are using (7010 vs 7020 MicroZed).

     

    Unlike the ZedBoard the MicroZed does require an external JTAG cable for JTAG operations.

    MicroZed is designed with the Platform Cable JTAG connector, Molex 87832-1420 which is a 2.0mm 2x7 shrouded, polarized header. On MicroZed, this is J3 and is compatible with Xilinx Platform Cables and Digilent JTAG HS1 or HS2 Programming Cables.

     

    If you are using the MicroZed with one of the Carrier Cards you need to connect the external JTAG cable to the connector on the carrier card and not the MicroZed.

     

    -Gary

  • 0

    Hi again!
    Sorry for the broken link, here it is:
    http://zedboard.org/content/microzed-development-edk

    I'm using the Xilinx external JTAG programmer. I've already programmed this board with newer tools, like Vivado. But everytime I try to upload the bitstream to the MicroZed using XSDK 14.7, messages:

    "DONE bit didn't go HIGH after programming FPGA
    Program FPGA failed
    Failed to download the bit file"

    appears. I know i'm just using the right external hardware, I suppouse the problem is software related. Any idea?