Signals(nodes) in Signal Tap Node Window Disappear

[WShep1]

All of a sudden, the signals in in the Signal Window started disappearing whenever I change the view from "Data" to "Setup" or vica versa.  I can get them to reappear by going down tothe "Hierarchy Display" window a clicking the box for the module that the signals are from.  For example, if I have selected signals from and module called "mono_out", there is a "mono_out" entry in the "Hierarchy Display" window with a check box next to it.  If this box is checked the signals from the "mono_out" module show up in the Signal Window.  This box now always gets unchecked when I switch between "Data" and "Setup" and the corresponding signals disappear in the Signal Window.  This did not happen until today when I switched to Quartus Prime Version 22.1std.2.  How do I stop this from happening? 

[sstrell]

Have you tried saving the .stp file when the box is checked and then closing and reopening the .stp file to see if it now sticks?

I've never seen that happen.  If it continues, it's possible the .stp file is corrupted somehow.

[RichardTanSY_Intel]

Could you try to re-create the .stp file and see if the issue still persists?

Best Regards,

Richard Tan

[WShep1]

I tried creating a brand new *.stp file, and I get the same results.  Hence, if there is a problem with the *.stp file then it is a problem that comes with a newly created *.stp file.

I thought that I had replied with the above comment, but I guess it never got sent as a reply.  I am still awaiting an answer to this question as it is still happening and I n=have not received an answer that stops the signals from disappearing.  Hence, I would like to reopen this case and keep it open until I get an answer.   I am not sure how to reopen this case.  I tried but was not able to do so.

[RichardTanSY_Intel]

We noticed that we haven't received a response from you regarding the latest previous question/reply/answer, and will now transition your inquiry to our community support. We apologize for any inconvenience this may cause and we appreciate your understanding. If you have any further questions or concerns, please don't hesitate to let us know. Thank you for reaching out to us!

Best Regards,

Richard Tan

p/s: If you find any answers from the community or Intel Support to be helpful, we encourage you to mark them as the best answer or rate them 4/5 in the survey. 

[FvM]

Hi,
I want to confirm that Signaltap was updated with new features that are not necessarily helpful, at least when you aren't aware of it.
I'm presently working with 22.4 Pro in a bigger project.
1. I also experienced the said the "disappearing" nodes (automatically disabled in hierarchy display), but didn't yet fully understand if it's a bug or feature.
2. More annoying, I repeatedly found newly added nodes hidden somewhere inside an existing data structure. I learned to consider carefully which line has the focus before adding new nodes. If I forgot to do so, I better go back to a safety copy than start searching the hidden nodes...
I believe it's intended as feature, definitely it never happened in older Signaltap versions.
Not specific to new version, a wrong mouse move sometimes makes Signaltap crash, e.g. when editing alias fields.
Nevertheless I love the powerful tool.

[WShep1]

Thank you for your response.  Your response makes much more sense than any of the other responses from Intel employees.  I expected that this was a bug (or as you say - a new feature).  I to love Signal Tap, but it is very frustrating when it crashes or adds a new feature that cause one hours of time trying to figure out what is happening. 

[WShep1]

I tried creating a brand new *.stp file, and I get the same results.  Hence, if there is a problem with the *.stp file then it is a problem that comes with a newly created *.stp file.

I thought that I had replied with the above comment, but I guess it never got sent as a reply.  I am still awaiting an answer to this question as it is still happening and I n=have not received an answer that stops the signals from disappearing.  Hence, I would like to reopen this case and keep it open until I get an answer.   I am not sure how to reopen this case.  I tried but was not able to do so.

[RichardTanSY_Intel]

Could you please share your design by archiving the project (Project > Archive Project) so that I can investigate it further?

Please kindly provide the steps to duplicate the error, enabling me to debug the issue promptly. 

Best Regards,

Richard Tan

[WShep1]

I have attached an archive of my project.

Steps to duplicate the Signal Tap Signals Disappearing problem are:

1. load the "XTest1_HyperRam.sof" file (to be found in the "...\output_files" subdirectory into a Cyclone 10LP (10CL025YU256i7G) device.

2. open up Signal Tap from the "tools" Menu.  Notice that only 3 signals are shown in the Data Signals Window

3. In the Hierarchy Display Window, click on the box by the "spi_mstr_write_wrappper...." module name

4. Observe that an additional 9 signals magically appear

5. Run the analyser and when it doesn't terminate, click on the Stop button and watch the 9 signals disappear.

6. Repeat Steps 3 and 4 above

7. I have also attached a *.docx file showing the Signal Tap Window with and without the disappearing signals.

Thank you for your support,

William Sheppard

Saguaro Systems, Inc

8520 E Kael St

Mesa, Arizona 85207

480-225-7731

wdsheppard@earthlink.net

[WShep1]

FYI, I am using Quartus Prime Version 22.1std.2 Build 922 07/20/2023 SC Lite Edition

[RichardTanSY_Intel]

Apologies for the delayed response. I was out of the office last week.

Could you please share the .sof file? The provided .qar seems to fail at the Analysis & Synthesis stage, preventing me from generating the .sof file.

You can include the 'Programming output files' by going to (Project > Archive Project > Advanced... > Tick the "Programming Output Files" option )

Best Regards,

Richard Tan

[WShep1]

Here is a project archive with the *.sof file.

[RichardTanSY_Intel]

I attempted to follow the steps you provided, but I couldn't successfully duplicate the issue. Here are the steps I took and my observations:

1. load the "XTest1_HyperRam.sof" file (to be found in the "...\output_files" subdirectory into a Cyclone 10LP (10CL025YU256i7G) device. (encounter no issue)

2. open up Signal Tap from the "tools" Menu. Notice that only 3 signals are shown in the Data Signals Window (there are 9 signals instead of 3)

3. In the Hierarchy Display Window, click on the box by the "spi_mstr_write_wrappper...." module name (unchecking it hid the 9 signals, leaving 3 nodes from "spi_lw_master_wds:u1" )

4. Observe that an additional 9 signals magically appear (is this during check or uncheck the box? ) 

5. Run the analyser and when it doesn't terminate, click on the Stop button and watch the 9 signals disappear. (all 12 signals remained after stop ) 

6. Repeat Steps 3 and 4 above (regardless of whether there were 3 or 12 signals, they remained after clicking the stop button.)

7. I have also attached a *.docx file showing the Signal Tap Window with and without the disappearing signals.

According to the provided document, the 'Hierarchy Display' was unchecked when the signals disappeared. The 'Hierarchy Display' window should allows you to show or hide hierarchies of nodes in the selected instance in the Signal Tap Logic Analyzer. So, all nodes in the "spi_mstr_write_wrapper:\I_SPI_MSTR_WRITE_WRAPPER_ACTIVE_GEN:u13" hierarchy will be hidden when it is unchecked.

Kindly confirm if this aligns with your observations. Let me know if I misunderstood any details.

Best Regards,

Richard Tan

[WShep1]

As it turns out the archive file that I sent yesterday with the date of ...20231016.qar did not have the same Signal Tap file loaded into it, but it exhibited the same problem in that the signals in the signal window would appear and disappear as the triggering event occurred and the appropriate box in the Hierarchy Display Window was checked and unchecked.  Basically what happens is that after a trigger event the box in the Hierarchy Display Window gets unchecked by itself and as a result the signals disappear that were showing before the trigger event.  Checking the box will allow the signals to reappear.

I hae attached a new archive that has the "spi_wrapper.stp" Signal Tap File loaded and which also contains the  *.sof file.  This file will correspond directly to the instructions that I previously sent on how to create the problem.  The file that I sent yesterday contained a different *.stp file.

Both of the archive files that I sent yesterday, ...20231016.qar, and today, ...20231017.qar,  exhibit the same problem. 

1.  If I open either archive in Quartus Lite 20.1.1, they work correctly and the signals do not disappear when there is a trigger event.  

2. If I open either archive in Quartus Lite 22.1.2, the check box in the Hierarchy Display gets unchecked and the signals disappear when a trigger event occurs.  Rechecking the box again allows the signals to reappear.

3.  I have no idea what the difference between 20.1.1 and 22.1.2, but I can verify that they work differently with the same archive projects.

4. My question to you is what version of Quartus are you using the investigate the problem.  This might be the difference between what you are seeing and what is I am seeing.  Or maybe there is some Option Setting in Signal Tap 22.1.2 that causes the box to get unchecked when a trigger event happens.

5.  I have had a remote debugging session with Intel previously to debug previous problems.  I am more than willing to have you dial into my computer to witness the problem occuring if that is appropriate.

Thanks for your assistance with this problem,

Bill

[RichardTanSY_Intel]

I am using Quartus Standard 22.1.2 Build 922 but I'm not able to duplicate the issue.

I'll arrange a team meeting with you through email; please check for an email from me.

Prior to the call, could you please try the troubleshooting steps to eliminate any potential root causes:

1. Try disabling any antivirus or firewall software temporarily, as they may be interfering with Quartus.
2. Restart Quartus and your computer. This can help clear any temporary issues that may be causing the error.
3. Verify that Quartus is installed with all the devices.
4. Run Quartus as an administrator

Best Regards,

Richard Tan

[RichardTanSY_Intel]

I have not received any update from the engineering team. 

I will continue to follow up with the engineering team and provide you with an update as soon as possible.

Thank you for your patience and understanding.

Best Regards,

Richard Tan

[RichardTanSY_Intel]

The engineering team is still investigating on this.

We appreciate your understanding and patience regarding this matter.

Best Regards,

Richard Tan

[RichardTanSY_Intel]

Hi,

I've successfully replicated the issue, and it appears to be specific to the Windows 10 operating system. The engineering team has acknowledged the problem and intends to address it in a future Quartus release.

The current plan is to include the fix in Quartus 24.1std (subject to change), scheduled for release by the end of 2024. Are you comfortable with this timeline?

For your reference, the HSDES ticket is [15014572807].

Thank you for your feedback, and I apologize for any inconvenience caused.

Best Regards,

Richard Tan

[RichardTanSY_Intel]

As this issue is planned to be addressed in a future Quartus release, I will transition this thread to community support.

If you have any further questions or concerns, please don't hesitate to reach out.

Thank you and have a great day!

Best Regards,

Richard Tan

[FvM]

Hello,
it seems that the bug is fixed in Quartus 24.2 Pro version. I checked with Signaltap from 24.2 stand-alone tools. It can be also used for Quartus std targets.

Regards
Frank