ISIM 14.6 crashes when saving waveform

[milan_mian]

I have troubles saving wavefrom in ISIM 14.6. Whenever I try to save as the wcfg waveform file, ISIM crashes. ISIM log file contains : Exception at PC 0x00007FFEF9681F28.

Please help.

[vuppala]

Hi @milan_mian

Try reducing the number of signals added to the waveform window and save it.

Thanks,

Vinay

[milan_mian]

Hi @vuppala, thanks for your reply. I find it strange that there is no problem with another machine. But, I have problems with machine I use at my home. I am simulating DDR3 MIG example design by xilinx. I get "Test passed" message, but I when I try to save as the waveform. I get the problem. Please help as I do need lot of signals to be present for analysis.

[milan_mian]

Hi @vuppala. I tried simulation for example design for Block memory generator which has very less signals (5 signals). Yet, ISIM crashed. No of signals or duration of simuation is not the cause of crash. I got Exception at PC 0x00007FFEF9681F28. Please help.

[vuppala]

Hi @milan_mian

Which OS are you using? 32-bit or 64-bit?

If you are using 64-bit OS, I suggest you to try 32-bit ISE project Navigator, run simulation and save the wave configuration file and see if the same error occurs.

Thanks,

Vinay

[vijayak]

Hi @milan_mian

Looks to be machine specific issue as the example design also failing. Try reinstalling the software and see if that helps.

[milan_mian]

Hi @vijayak, I tried reinstalling entire ISE. But still the problem persists. Please help.

[milan_mian]

Hi, @vijayak and @vuppala. I found one more problem (possibly related to the same issue). When I run C:\Xilinx\14.6\ISE_DS\ISE\bin\nt64\isimgui.exe, it opens without any problem. But when I try to open (from file menu then open), it still crashes.  I also have tried using 32 bit version, yet still the problem persists. Please help.

[milan_mian · Accepted solution]

Most likely cause of the problem could be I am running ISIM in windows 10 and another machine runs windows 7.

[vijayak]

Hi @milan_mian

Windows-10 is not supported so we have not tested our tool in Windows 10. Unsupported OS could be the reason.

I see that you have a machine with Windows-7 and recommond to use that as it is supported OS.