Forum Discussion
7 Replies
- Altera_Forum
Honored Contributor
.stp files are not "part" of the .sof. The .sof includes the bitstream for including a Signal Tap instance when you program the FPGA. The .stp file is used to configure (before compilation) and control (after compilation and device programming) that instance.
So program your device with the .sof using the programmer or the JTAG configuration section of the .stp file. If the Signal Tap instance defined in the .stp is present in the programmed device, you'll see in the status at the top of the .stp file that you are ready for capture. - Altera_Forum
Honored Contributor
Ok, let's say I have a single SOF file and many STP files. Let's say do not know what STP file was included to the project while its compilation and generation of the SOF file. What's the shortest way to know this?
Could several STP files be included to the same project? As far as I understand, as many STP files as many SignalTap instances in the project... Correct? Could I all of them simultaneously during the debug cycle? - Altera_Forum
Honored Contributor
You can enable only one Signaltap file for a Quartus project, it can optionally contain more than one Signaltap instance.
There's nor unique ID identifying a Signaltap instance, it's apparently matched by the number of JTAG in- and output bits. Means you can't be absolutely sure that you are using the right .stp file, you need to remember it. - Altera_Forum
Honored Contributor
OK, thanks
- Altera_Forum
Honored Contributor
Archiving compilation reports and .stp files along with programming file seems appropriate.
- Altera_Forum
Honored Contributor
Actually, in the JTAG configuration section of a .stp file, you can "attach" a programming file (little paperclip icon) to check its compatibility with the current .stp file settings to make sure you can use the current settings with the current device programming.
- Altera_Forum
Honored Contributor
It is explicitly set by quartus in the qsf file (set_global_assignment -name USE_SIGTAP_FILE file_that_will_be_used_during_compilation.stp)