I have a Cyclone IV design with 3 ROMs in it. Each ROM is 256 words by 256 bits. After I compile the design the RTL netlist viewer shows all 3 ROMs and the compilation report shows that the memory resources for all 3 ROMs was used. If I look for the ROM outputs with the Quartus node finder I can see the ROM outputs, all 256 of them, for each ROM. I do this in the post-compilation view, so I know these nets are in there and didn't get merged or dropped. The problem is that in the timing analyzer only a few of the ROM outputs can be found and for one of the three ROMs nothing at all can be found. If I add a reference to the missing ROM in the SDC file the timing analyzer flags it as an error because it can't find that ROM. Has anyone had a similar problem with the timing analyzer? Is this a known bug?

What options are you using in Report Timing to try to find the nets? Is your design fully constrained for timing with a .sdc file (clocks and I/O at a minimum)?

The only options I'm using in Report Timing are the "from" clock and "To" clocks, "Setup" is selected, "Detail level" is "Full path". In the Targets section, I then click the From search button. In the Name Finder that pops up, I select get_pins and a filter of *rom*. My ROMs have instance names of rom0, rom1 and rom2. When I click the List button I get the data outputs for rom0 and rom1 and nothing for rom2. I should see 256 data outputs for each ROM, but I only get the outputs for rom0 and rom1. Yes, I have my SDC file setup with clocks and I/O ports.

Where is the output of that third ROM going? Other logic or to output pins? There must be something incorrect in your filtering for the report to not be seeing these paths. I presume you are using the post-fit (Standard edition) or final (Pro) timing netlist.

All three ROMs are at the start of very similar signal chains, only the ROM contents are different. I'm using the ROMs without an output register and they all parallel load some shift registers. Yes, I'm using the post-fit timing netlist. Like I said, the Quartus Node Finder finds the ROM outputs for all 3 ROMs in the post-fit netlist.

I'm posting some screen shots showing what I'm seeing. These images show searching for rom2 in the timing analyzer and in the Quartus node finder. Note that rom2 appears in the node finder but not in the timing analyzer.

Can't find nets in timing analyzer

17 Replies

sstrell
Super Contributor
5 years ago
What options are you using in Report Timing to try to find the nets? Is your design fully constrained for timing with a .sdc file (clocks and I/O at a minimum)?
- KittyBumpkins
  New Contributor
  5 years ago
  The only options I'm using in Report Timing are the "from" clock and "To" clocks, "Setup" is selected, "Detail level" is "Full path". In the Targets section, I then click the From search button.
  
  In the Name Finder that pops up, I select get_pins and a filter of *rom*. My ROMs have instance names of rom0, rom1 and rom2. When I click the List button I get the data outputs for rom0 and rom1 and nothing for rom2. I should see 256 data outputs for each ROM, but I only get the outputs for rom0 and rom1.
  
  Yes, I have my SDC file setup with clocks and I/O ports.
  - sstrell
    Super Contributor
    5 years ago
    Where is the output of that third ROM going? Other logic or to output pins? There must be something incorrect in your filtering for the report to not be seeing these paths.
    
    I presume you are using the post-fit (Standard edition) or final (Pro) timing netlist.
KittyBumpkins
New Contributor
5 years ago
I'm posting some screen shots showing what I'm seeing. These images show searching for rom2 in the timing analyzer and in the Quartus node finder. Note that rom2 appears in the node finder but not in the timing analyzer.
- sstrell
  Super Contributor
  5 years ago
  Try turning on the Hierarchical option in the Name Finder. Without that, wildcards only search the current hierarchical level you've specified (you'd have to do something like *|*|* etc. to search further down). It looks like that 3rd ROM might be further down in the hierarchy.
  - KittyBumpkins
    New Contributor
    5 years ago
    With Hierarchical on, Compatibility mode gets turned off and wild cards don't work. But if I clear the filter and select get_pins it seems to list all pins in the design in alphabetical order. Still no rom2.
    
    In any case, all 3 ROMs are in the same Verilog module and therefore should be at the same hierarchical level.
SyafieqS
Super Contributor
5 years ago
Hi Nuno,

Can you double confirm the net in TA node finder and can you use latest Quartus as well if it is possible. It has a lot of fixes there.
- KittyBumpkins
  New Contributor
  5 years ago
  I'm using Quartus Lite 20.1.1. I checked the Quartus download webpage this morning and 20.1.1 is the latest available download. I checked again TA name finder with the same results as before, please see attached screen shots. I also attached the fitter RAM summary report that shows that all three ROMs in the design post-fit.
SyafieqS
Super Contributor
5 years ago
Hi Nuno,

Can you attach the qar here and step to reproduce it. This could be a bug but need to check it first.
- KittyBumpkins
  New Contributor
  5 years ago
  Project QAR is attached.
  
  Steps to reproduce:
  
  Compile project with Quartus 20.1.1 (Build 720 11/11/2020 SJ Lite Edition)
  
  Open Timing Analyzer
  
  In Timing Analyzer: create timing netlist, read SDC file, update timing net list
  
  In Timing Analyzer: View->Name Finder...
  
  In Name Finder: Set collection to get_pins
  
  In Name Finder: Set filter to *rom0* and click "List" button
  
  Note that pins for rom0 are shown
  
  Change filter to *rom2* and click "List" button
  
  Note that no pins are shown and "No matches found" is displayed.
  
  In Quartus main window compilation report: Fitter->Resource Section->RAM Summary
  
  Note that rom0, rom1 and rom2 are all present
  
  Additional note: In the Quartus main window, using View->Utility Windows->Node Finder and selecting the "Pins: all & Registers: post-fitting" filter produces similar results, i.e. rom0 and rom1 can be found but not rom2.
  TA_Missing_ROM.qar74 KB
SyafieqS
Super Contributor
5 years ago
Hi Nuno,

I can reproduce the issue. Seem this Quartus Standard is also affected by this. In TMV post fit as well, filter for pin rom0 and rom1 can be searched but not rom2. I will forward this to developer and probably will take sometime due to legacy device. I will put this to close pending and you may create new case refer to this case asking for update.
KittyBumpkins
New Contributor
5 years ago
Thanks for looking into this. I don't know what you mean by "create a new case", there is no way of creating support cases with Intel. I had to call Intel corporate to get this issue escalated and I just got lucky.

Forum Discussion

Can't find nets in timing analyzer

17 Replies

Recent Discussions

Agilex 5 IOPLL Max Numbers and Tool Display Mismatch

[Agilex 7F] How to setup my EMIF IPs for the toolkit?

Realistic values for set_max_skew

Failing IO buffer

Fitter stalls on "Advanced Physical Optimization" on Windows 10