Forum Discussion
ContributorSignalTap -> how to re-define the device chain (auto-detect doesn't work well)?
Re-installing the Quartus on the new OS solved the problem, so thank you for your support.
Super ContributorIgnore the warning. After programming the device in the Programmer, just select the device in the .stp window. If you still have the warning, just start the logic analyzer instance. It will work.
amildmthis is the issue... I cannot select the target device in the SignalTap GUI since the device is not correctly detected ...
- sstrell
What are you seeing in Signal Tap when you select your programming cable? Screenshot of the issue?
- amildm
Here 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...
