Forum Discussion

BeB's avatar
BeB
Icon for Occasional Contributor rankOccasional Contributor
4 years ago

Signal tap: Program the device to continue

Hello,

I am using Quartus 19.1 for a Stratix S10 1SX280LN3. After successfully compiling my project with the latest .stp file created from signal tap analyzer (no warnings other than some registers pruned away) and programming the device, I keep getting the message "program the device to continue" when launching signal tap. Of course if I program the device, I keep getting the same message.

That makes it impossible to debug my project.

Many thanks for any input you may have,

Regards,

BeB

12 Replies

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

    That status message isn't always 100% accurate, especially if you program the device in the Programmer instead of directly from the JTAG Configuration section of the .stp file window. Just try starting the logic analyzer after programming the device. If it works, great. If not, you may get a message about why it won't run.

    • BeB's avatar
      BeB
      Icon for Occasional Contributor rankOccasional Contributor
      4 years ago

      Hello,

      Thanks for the feedback. The same issue arises whether I use the programmer or directly program the .sof from the signal tap analyzer window.

      On top of that, I would like to enable signal tap to debug some faulty behavior at power up that happens once in a while, therefore I do not want to re-program the device once the faulty behavior happens.

      Thanks again,

      BeB

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

        For that, you need to set up a power-up trigger that does exactly what you need: look for a trigger event to occur after device programming but before you can manually start the logic analyzer. See the debug tools user guide for details on setting up a power-on trigger.

  • BeB's avatar
    BeB
    Icon for Occasional Contributor rankOccasional Contributor
    4 years ago

    Hi,

    Thank you for your input, but the cable is definitely plugged since I can flash the device, and the device has not changed, it's always been the same (and the correct one) and it used to work just fine.

    BeB

    • RichardT_altera's avatar
      RichardT_altera
      Icon for Super Contributor rankSuper Contributor
      4 years ago

      Hi @BeB

      I can't figure out what could go wrong for your issue.

      One thing to try is to reduce the clock frequency. That may help with detecting the signal taps.

      You could try to install the latest Quartus Pro 21.1 and check if the issue still persist.

      Best Regards,
      Richard Tan

      p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.

  • RichardT_altera's avatar
    RichardT_altera
    Icon for Super Contributor rankSuper Contributor
    4 years ago

    I have yet to receive any response from you to the previous question/reply/answer that I have provided.


    With that, I will 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.

    Best Regards,
    Richard Tan

    p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.

  • SurakshaNadig's avatar
    SurakshaNadig
    Icon for New Contributor rankNew Contributor
    11 months ago

    I had this issue and thought I could post what worked for me in case someone else faces the same problem as me.

    In my case, the issue was due to a mismatch in the Configuration via Protocol (CVP) setting.

    I had enabled CVP in Quartus (under device settings), but was programming the device using a .sof file without CVP support. This caused problems with Signal Tap not running as expected.

    Solution:

    To fix this, make sure CVP is disabled if you're not using it. Here are the steps:

    1. On Quartus Prime, Go to Assignments > Settings > Device/Board > Device and Pin Options

    2. Under Configuration via Protocol (CVP) – set it to Off

    3. Also, under the same section, find Enable CONF_DONE pin and uncheck it if it's not needed.

    After making these changes and recompiling, Signal Tap worked as expected using the regular .sof.