ContributorRe-installing the Quartus on the new OS solved the problem, so thank you for your support.
Super ContributorDid you try a new .stp file? Like I said, this one could be corrupted.
Contributoryes, sure, tried a NEW STP with just a single wire... doesn't work... It seems the SignalTap GUI cannot access the programmed device, but Programmer can do this...
As for the new STP, I opened the old one, saved it with another name, deleted all the signals, added just a single wire, renamed the stp instance, replaced the old stp with the new stp in Project Settings, recompiled, programmed with Programmer, then opened the SignalTap GUI, scanned the chain, device was not recognized (the same as with previous stp), tried to program the device with SOF from SignalTap GUI ... all the same ... It seems SignalTap GUI cannot access the device while Programmer can do this... Probably I'm wrong... Please advice ...
Super ContributorContributorOk, here is what I did now:
- disabled the stp in the project settings
- opened SignalTap GUI from Quartus -> Tools -> SignalTap (new SignalTap GUI opened, without signals, blank)
- from SignalTap GUI: File -> New
- added a signal to this new STP, added clock, saved the STP and enabled it in the Project Settings
- recompiling now... will be back with the results soon...
BTW, could I use the Rapid Recompile? How much time could the Rapid Recompile save? Is it always better to recompile from the scratch each time?
ContributorOK, as described above, I created a fresh new STP file... Still the results are same...
Anyway, no matter what STP is, SignalTap GUI should read the programmed device, recognize the device number and also be able to program the device, correct? It seems that is not happening.
Anyway, I'm ready to following your instructions. What are the next steps?
