Forum Discussion

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

SignalTap II File is not compatible with the file programmed in the device.

Hi,

I am having SignalTap II problem for a while.

I get following error message when I try to program the device.

Error: Can't run SignalTap II Logic Analyzer -- SignalTap II File is not compatible with the file programmed in the device. The expected compatibility checksum value is 0xB7C250B2; the value read from device is 0x7512BA8C

I add a signal to signaltap and save it. Then I go to Quartun II (version 11.0 Build 208). I recompile, then going back to SignalTap II and program the device but I get above error message.

I have done following so far but i still get error:

- closing SignalTap II and reopen it

- removing db and incrememtal db file.

- deleting .sof file

- even renaming the stp file to something new and changed the file name in qsf file

Some have proposed to do following but I don't know how to do it:

1- .stp file is cached which needs to cleared. How can i clear the cache?

2- Disabling the on-board configuration controller. What is it and how can I do it?

Please let me know any solution you may think of.

Thanks

Alex

2 Replies

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

    Hi Alex,

    Here are a couple of different approaches to the problem.

    1) Does the sld_hub and sld_signaltap instance appear in the Project Navigator?

    ) Try browsing to the SignalTap file using Assignments -> Settings -> SignalTap II Logic Analyzer just in case there's a path issue.

    2) Try disabling the project and compiling to ensure the Signaltap instance disappears from the Project Navigator. The enable it again and make sure it comes back.

    Hope this helps. It looks like you are looking at the right things.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    14 years ago

    I had something similar one before.

    In my case, just power cycling the board fixed the problem.

    Hope this help.