Forum Discussion

SparkyNZ's avatar
SparkyNZ
Icon for Contributor rankContributor
5 years ago

Capture signal with SignalTap II with Storage Qualifiers

I am struggling to get this to work. I have watched the Intel training videos about SignalTap triggers but they are so dry and don't really give any hands-on examples to follow.

I have a design which has a state machine. All I want to do is start capturing signal data when my state machine currState value becomes HANDLE_INPUT and stop capturing signal data when currState becomes RETURN_TO_IDLE.

What am I doing wrong? The trigger functionality makes no sense to me whatsoever.

3 Replies

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

    I'm not sure why you have the storage qualifier options set to Basic OR. They should be the default of Basic AND because the qualifier needs to match all the bits in your state register to the mnemonic I presume you've set up for the state names.

    Also, if you haven't already, try turning on "Disable storage qualifier" temporarily (no need to recompile for this option) to make sure your actual trigger is working.

    #iwork4intel

    • SparkyNZ's avatar
      SparkyNZ
      Icon for Contributor rankContributor
      5 years ago

      I'm not sure why either - I got desperate because I couldn't understand how it all worked :-) I did manage to figure it all out though. The biggest problem was that I had a 32bit value for my state and the mnemonic table values were defined as 5bit. I changed the state variable to 5bit and then the trigger began to work quite happily with Storage Qualifier disabled. I then enabled Storage Qualifier and it worked.

      However.. I still have issues with Storage Qualifier on occasion.. I think there is an intermittent issue in there somewhere but I can live with that.

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

    What kind of other issues with storage qual have you run into?

    #iwork4intel