Forum Discussion

amildm's avatar
amildm
Icon for Contributor rankContributor
4 years ago
Solved

SignalTap -> how to re-define the device chain (auto-detect doesn't work well)?

Hi All, The FPGA devices in the JTAG chain on my board are not auto-detected correctly. In Quartus Programmer, besides an auto-detection of the devices, there is an option to choose the devices ...
  • amildm's avatar
    amildm
    3 years ago

    Re-installing the Quartus on the new OS solved the problem, so thank you for your support.

sstrell's avatar
sstrell
Icon for Super Contributor rankSuper Contributor
4 years ago

Ignore 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.

amildm's avatar
amildm
Icon for Contributor rankContributor
3 years ago

this is the issue... I cannot select the target device in the SignalTap GUI since the device is not correctly detected ...

  • sstrell's avatar
    sstrell
    Icon for Super Contributor rankSuper Contributor
    3 years ago

    What are you seeing in Signal Tap when you select your programming cable? Screenshot of the issue?

    • amildm's avatar
      amildm
      Icon for Contributor rankContributor
      3 years ago

      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...

      • sstrell's avatar
        sstrell
        Icon for Super Contributor rankSuper Contributor
        3 years ago

        So 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.