02-05-2014 08:12 PM
As far as I know, the program is fine. It worked on another computer with no issue. I go to load it onto the Basys2 board I have and everything works fine until impact opens. I click Boundary Scan and Initialize Chain, but when I click yes on "Auto Assign Configuration Files Query Dialog" like I was told, an error message comes up that says "_impact4.exe" has stopped working. I've reinstalled ISE Design Suite, I've restarted my computer, and I've tried rewriting it into a new program. I can't find any solutions online, can anyone help me?
02-05-2014 08:21 PM
02-11-2014 02:16 PM
I've had a similar problem. Been downloading code to the Spartan, typing in Verilog, all working fine - then one day (no re-install, no massive change, no lightning bolts, nothing other than phase of the moon...) - I get the "_impact4.exe has stopped working". Not very helpful. At all.... Fortunately, I have the Adept download program so I can continue, but I haven't been able to generate a PROM file through ISE. That's gonna be an issue soon...
02-13-2014 05:16 AM
What is the ISE/Vivado tools version are you using?
IN case of ISE 13.4 and 14.X tools this issue is local to using and saving a project with the Digilent cable. Customers are requested to use either the Platform USB or the Mini-USB JTAG cables as a work around. A change request has been filed to fix the issue. The fix will be implemented in one of the next few revisions.
07-23-2014 07:13 PM
I have this issue right now with ISE 14.7 and the Avnet LX9 board. Even after a clean install of ISE I still get this message.
Any advice is appreciated.
Michael Harpe, N4PLE
07-23-2014 08:29 PM
Did you try above suggestions?
If you still encounters the issue, create a separate .ipf (impact project) and check.
Also share impact.log file to debug the issue.
07-28-2014 09:56 AM
DISCLAIMER: I am not an FPGA engineer. I did not stay at a Holiday Inn Express last night.
For review: This is the Avnet Spartan-6 microboard just purchased this month. I am working on learning VHDL.
So far the issue with Impact does appear to be with saved project (.ipf) files. If I come back to Impact pointed to a saved project file I get the error. If I delete the .ipf file and start again it starts working once I tell it to ignore the error about the project file being gone.
Impact works fine if I start in Boundary Scan, Initialize the chain and then load a PROM config file. I can then program the part with no issues.
So the question is: is it the .ipf file being written improperly or is it not loading properly?
08-02-2014 04:18 AM
Just to expand on what Kodali says:
Once I have impact open and create a new project, initialize chain, add devices and files etc, then go to the output->cable setup menu and explicitly set the Digilent usb jtag setting (inexplicably not set) then save the project file to something.ipf
The next time I ran impact it did manage top open that project file, but then I noticed in output->cable setup the digilent usb jtag wasn't set this time. Still seemed to work though. Maybe have to explicitly set it every time before saving it?
At least I can run impact stand-alone now without having to reset-up the jtag chain every time
Just remember to set the cable to digilent usb before saving. (Or don't save when exiting.)
Also now seems to work properly if I set process properties to the saved .ipf file in the ISE design flow for Configure Target Device
Joy! I hope it continues to work...