Hello, ich have the Spartan3 StarterKit from Digilent. When I start the programming process in impact, all LEDs on the board go red, and on the screen an progress dialog appears. When the progress is at about 98%, it stalls for 8 seconds, and then the message appears : "'1' : Programming terminated. DONE did not go high" Can you help me ? Regards Thorsten
Problem with Spartan 3 StarterKit
Started by ●March 13, 2008
Reply by ●March 13, 20082008-03-13
On Mar 13, 10:22 am, Thorsten Kiefer <webmas...@nillakaes.de> wrote:> Hello, > ich have the Spartan3 StarterKit from Digilent. > When I start the programming process in impact, > all LEDs on the board go red, and on the screen > an progress dialog appears. When the progress is at > about 98%, it stalls for 8 seconds, and then the message > appears : "'1' : Programming terminated. DONE did not go high" > Can you help me ? > > Regards > ThorstenMore data please: * Which starter kit? * What file are you trying to load? * What are you trying to load it with? Are you confident that the file you are trying to load is correct for the device you are trying to load? It may be that you're trying to load a file for the "next smaller" FPGA. G.
Reply by ●March 13, 20082008-03-13
ghelbig@lycos.com wrote:> More data please: > * Which starter kit?The one with the Xilinx XC3S200> * What file are you trying to load?eq2.bit (A 2 bit comparator. 4 switches are input, and 1 led is ouput.)> * What are you trying to load it with?impact> > Are you confident that the file you are trying to load is correct for > the device you are trying to load? It may be that you're trying to > load a file for the "next smaller" FPGA.i created the project for exactly that device> > G.TK
Reply by ●March 13, 20082008-03-13
Thorsten Kiefer wrote:> Hello, > ich have the Spartan3 StarterKit from Digilent. > When I start the programming process in impact, > all LEDs on the board go red, and on the screen > an progress dialog appears. When the progress is at > about 98%, it stalls for 8 seconds, and then the message > appears : "'1' : Programming terminated. DONE did not go high" > Can you help me ? > > Regards > Thorsten >Can you successfully load the example project, s3demo.bit? If so, then there must some problem with your generated .bit file.
Reply by ●March 13, 20082008-03-13
> Can you successfully load the example project, s3demo.bit?Is it shipped with WebPack ? I cannot find it in my ISE WebPack installation.
Reply by ●March 13, 20082008-03-13
Reply by ●March 13, 20082008-03-13
www.digilentinc.com Thorsten Kiefer schrieb:>> Can you successfully load the example project, s3demo.bit? > Is it shipped with WebPack ? > I cannot find it in my ISE WebPack installation. >
Reply by ●March 13, 20082008-03-13
Thorsten Kiefer wrote:> Hello, > ich have the Spartan3 StarterKit from Digilent. > When I start the programming process in impact, > all LEDs on the board go red, and on the screen > an progress dialog appears. When the progress is at > about 98%, it stalls for 8 seconds, and then the message > appears : "'1' : Programming terminated. DONE did not go high" > Can you help me ? > > Regards > ThorstenOK I got it. The configuration mode jumpers were set to "master serial". I set them to "Jtag". But the program is not persistent. How can I make it persistent. The JTAG chain shows a second device : xcf02s. Is that the flash prom ?
Reply by ●March 13, 20082008-03-13
Thorsten Kiefer wrote:> Thorsten Kiefer wrote: > >> Hello, >> ich have the Spartan3 StarterKit from Digilent. >> When I start the programming process in impact, >> all LEDs on the board go red, and on the screen >> an progress dialog appears. When the progress is at >> about 98%, it stalls for 8 seconds, and then the message >> appears : "'1' : Programming terminated. DONE did not go high" >> Can you help me ? >> >> Regards >> Thorsten > > OK I got it. > The configuration mode jumpers were set to "master serial". > I set them to "Jtag". > But the program is not persistent. > How can I make it persistent. > The JTAG chain shows a second device : xcf02s. > Is that the flash prom ?You are correct - the memory in the FPGA is volatile (it's SRAM) and your program will vanish when power is removed. Correct also on the second point - you must program the platform flash (xcf02s) with your fpga code. However, to do so you must first run the IMPACT tool to generate a programming file (I like to use the .mcs format). *IMPORTANT* When you set the properties for generating your .bit file, make sure that you select the configuration clock as CCLK, as this is the clock that drives the xcf02s during configuration. There is no need to change this to JTAG clock while you are developing your code, as the IMPACT will recognize this mismatch and change the configuration clock from CCLK to JTAG whenever you load the .bit file directly into the FPGA.
Reply by ●March 13, 20082008-03-13
Paul Urbanus wrote:> Thorsten Kiefer wrote: >> Thorsten Kiefer wrote: >> >>> Hello, >>> ich have the Spartan3 StarterKit from Digilent. >>> When I start the programming process in impact, >>> all LEDs on the board go red, and on the screen >>> an progress dialog appears. When the progress is at >>> about 98%, it stalls for 8 seconds, and then the message >>> appears : "'1' : Programming terminated. DONE did not go high" >>> Can you help me ? >>> >>> Regards >>> Thorsten >> >> OK I got it. >> The configuration mode jumpers were set to "master serial". >> I set them to "Jtag". >> But the program is not persistent. >> How can I make it persistent. >> The JTAG chain shows a second device : xcf02s. >> Is that the flash prom ? > > You are correct - the memory in the FPGA is volatile (it's SRAM) and > your program will vanish when power is removed. > > Correct also on the second point - you must program the platform flash > (xcf02s) with your fpga code. However, to do so you must first run the > IMPACT tool to generate a programming file (I like to use the .mcs format). > > *IMPORTANT* When you set the properties for generating your .bit file, > make sure that you select the configuration clock as CCLK, as this is > the clock that drives the xcf02s during configuration. There is no need > to change this to JTAG clock while you are developing your code, as the > IMPACT will recognize this mismatch and change the configuration clock > from CCLK to JTAG whenever you load the .bit file directly into the FPGA.Also, don't forget to change the configuration mode back to master serial after you have programmed the platform flash. Oh, you have to either cycle power or press the 'FGPA program' switch (if this is one on the board) before the FPGA will be loaded from the platform flash.
