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 in the chain manually.

But in the SignalTap there is no such option... Even if I'm attaching the SOF file there, the device that I want to program appears as unknown with some strange serial number.

So, what's the solution? How can I manually define devices in the chain in SignalTap?

Thanks!

  • amildm's avatar
    amildm
    3 years ago

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

19 Replies

  • sstrell's avatar
    sstrell
    Icon for Super Contributor rankSuper Contributor

    You can't. The chain configuration section of the .stp file is for simple programming of a selected device in the JTAG chain for running the logic analyzer. If you have a more complicated setup, you need to use the Programmer. You can come back to the .stp window after you program the device in the Programmer.

    • amildm's avatar
      amildm
      Icon for Contributor rankContributor

      This doesn't help... Even after programming the device with SOF (with STP included) via Programmer, the SignalTap GUI doesn't read the target device correctly. It "sees" the SignalTap signals, but also says that the programmed device doesn't match the SignalTap signals... Usually, this "warning" is solved by programming the device via SignalTap GUI, but in this case, this is impossible since the target device is not detected correctly by the SignalTap GUI and the programming is fail... This is just like some vicious circle... What's the solution?

      I'm not sure whether this is important, but there are two devices in the chain - MAX10 (first) and Cyclone 10 (second). The MAX10 is detected correctly, but C10 doesn't ...

  • sstrell's avatar
    sstrell
    Icon for Super Contributor rankSuper Contributor

    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

      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

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

  • sstrell's avatar
    sstrell
    Icon for Super Contributor rankSuper Contributor

    Did you try a new .stp file? Like I said, this one could be corrupted.

    • amildm's avatar
      amildm
      Icon for Contributor rankContributor

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

      • sstrell's avatar
        sstrell
        Icon for Super Contributor rankSuper Contributor
        That’s not really a new file. I mean create a brand new one from the File menu. You just edited the existing one which could be corrupted like I said.
  • Hi amildm,


    Just wanted to check with you, is your concern has been addressed?

    If yes , kindly do let me know.

    Thank You


    • amildm's avatar
      amildm
      Icon for Contributor rankContributor

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

  • I’m glad that your question has been addressed, I now transition this thread to community support.

    If you have a new question, feel free to open a new thread to get the support from Intel experts.

    Otherwise, the community users will continue to help you on this thread.

    Thank you.