Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
Intel Support hours are Monday-Fridays, 8am-5pm PST, except Holidays. Thanks to our community members who provide support during our down time or before we get to your questions. We appreciate you!

Need Forum Guidance? Click here
Search our FPGA Knowledge Articles here.
15469 Discussions

Why does "Signal Probe Pins" take 3 times as long as normal project compilation?

gyuunyuu
New Contributor II
280 Views

The signal probe pins is an ECO change. It takes 1h to complete while the project itself may compile between 20min to 25min.

 

Why does it take so long? Is there a way to speed it up?

 

Also, the "pins" all get disabled when I compile the project. Why can't these pins stay in place so I don't have to run the Signal Probe Pins' "Start Check & Save All Netlist Changes" after each project compilation!?

 

 

0 Kudos
1 Reply
sstrell
Honored Contributor III
81 Views

If you are trying to probe deep signals in a design that uses a lot of routing, it may take longer to find a way of routing the signals out, but 1 hour is pretty excessive. How many signals are you trying to bring out and how big is the design? Is the Signal Probe compilation successful after that hour?

 

Signal Probe pins are lost after a recompilation of the project because, as you mention, this is an ECO change based on the final compiled netlist, which changes after you recompile. You can run the signalprobe_qsf.tcl script generated by the tool to restore them. If you are using the Standard edition of Quartus and if you use the incremental compilation feature, you can also maintain Signal Probe pins if you put the Signal Probe nodes in a design partition and choose to reuse the post-fit netlist.

 

#iwork4intel

Reply