Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
15 years ago

SignalTap Megawizard Crashes

OS: Windows Vista 32-bit

Quartus: 10.0 webpack Build 218

The megawizard crashes whenever the number of trigger bits in a signaltap block is set higher than 1. I've worked around it by hand editing the generated .cmp and .vhd.

I generated the same megafunction on a linux installation of 10.0 and had no problems.

I'm going through all this because signaltap has stoppped working since I installed 10.0. The megafunctions were originally generated with 9.0, so I have regenerated them with 10.0 to avoid an version conflicts. Unfortunately, stp still recognizes the core and sees everything via JTAG, but it will not let me set triggers. I've tried both webpack and subscription edition on linux, and webpack on windows.

If anyone has had this problem and found a way around it, I'd love to hear about it.

4 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    Just downloaded and installed Quartus 9.1sp2 webpack. Its version of Signaltap works fine. Evidently quartus_stpw 10.0 is broken on all platforms.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    i just tested STPII in 10.0 Subscription on Linux and had no problems. i wonder if its isolated to Web Edition. is your TalkBack turned on?

    can you elaborate on whenever the number of trigger bits in a signaltap block is set higher than 1? i haven't had any crashes yet, but maybe i'm not doing it right. :)
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    15 years ago

    It may very well be a licensing issue. I obtained a new webpack license and verified talkback is enabled and still cannot set triggers.

    The .stp file I generated with 9.1sp2 on windows loads fine on with the linux 10.0 version. It even picks up the falling edge trigger I set and saved and uses it to do the capture. So for now I can hand edit the .stp file to set triggers. Not ideal, but I can make progress on my project.

    I plan on getting a brand new subscription license in the near future...hopefully that will fix the problem.