ContributorRe-installing the Quartus on the new OS solved the problem, so thank you for your support.
Super ContributorWhat are you seeing in Signal Tap when you select your programming cable? Screenshot of the issue?
ContributorHere is how the devices in the chain are detected:
So, the second device in the chain is Cyclone 10 GX, which is not correctly detected (detected as UNKNOWN).
--------------------------------------------------------------------------------
After loading the SOF file, the second device is correctly updated to Cyclone 10.
--------------------------------------------------------------------------------
But, when loading the same SOF to the SignalTap GUI, the target device is detected as 0x002E72000 (not as Cyclone 10). After burning the SOF through SignalTap, the detected devices stays 0x002E72000:
--------------------------------------------------------------------------------
Anyway, when I'm trying to run the SignalTap Instance after programming the device, I'm receiving a warning "Instance not found". This is very strange since the STP is enabled in the Project settings. I also tried to recompile the device through the SignalTap GUI, but are there result is the same.
So, please advice on the next steps...
Super ContributorSo just to reiterate, you can successfully program the device in the Programmer and when you go back to the .stp file (did you try opening the .stp file after programming the device in the Programmer?), the device still appears there as 0x002E720DD (even after clicking Scan Chain?) and attempting to start the logic analyzer (even with the status and error shown), it will not start.
Plus, you are saying that you have tried recompiling from scratch, verifying that this .stp file is selected and enabled in the project settings, and you get the same results.
Hmm.
In rare situations, I have seen corrupted .stp files. At this point, I'd try creating a new .stp, configuring it the same as this one, maybe with a different name to make sure you don't accidentally re-add the old one to your project, and then recompiling from scratch.
ContributorYes, I can successfully program the device in the Programmer.
Yes, when I go back to the .stp file (I opened the SignalTap GUI after programming the device in the Programmer), the device still appears there as 0x002E720DD (yes, even after clicking Scan Chain)
One more thing... after clicking on the Scan Chain bottom and selection the 0x002E720DD device (which should be Cyclone 10), the STP file starts appearing as "modified" - a star sign (*) appears next to the stp file name. When I try to close the SignalTap GUI, a window pop ups asking whether I want to save the modified STP file... But I did not modified it, just scanned the chain!
Here is one more thing... At the end of the programming of the 0x002E720DD device through SignalTap GUI (with the same file as was used in Programmer), the red highlighted message "Program the device to continue" appears:
Yes, tried recompile the Project from scratch, verifying that this .stp file is selected and enabled in the project settings, yes got the same results.
Just right now I tried to re-compile the Project with STP, which includes just one wire - the result is the same...
I suspect that the problem is so that SignalTap GUI cannot access the device and read it correctly. Honestly I don't know what to do from this point... Any suggestions?
