• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Glitch in Synthesized Netlist Simulation of SR Latch — Occurs...

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 92
  • Views 1198
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Glitch in Synthesized Netlist Simulation of SR Latch — Occurs Only in One Instance

SaranyaBalan
SaranyaBalan 3 months ago

Hi all,

I’m facing an unexpected glitch during post-synthesis netlist simulation of a design that includes multiple instances of an SR latch. I’ve attached both the netlist snapshot and the SimVision waveform for reference.

Originally, the latch was modelled at the gate level using NOR-based feedback:

The post layout netlist looks as follows

module SR_Latch_8 (

Q,

RESET,

SET);

output Q;

input RESET;

input SET;

// Internal wires

wire QBAR;

wire n_2;

BUFM2R cdn_unmapped_dis_arc_buf (.A(Q),

.Z(n_2));

NR2M12RA g22__7098 (.A(RESET),

.B(QBAR),

.Z(Q));

NR2M6R g23__6131 (.A(n_2),

.B(SET),

.Z(QBAR));

endmodule

   The glitch happens during synthesized netlist simulation, not in RTL simulation. It appears at a specific time where SET=0 and RESET=0, i.e., the latch should hold its previous value. The output (Q) transitions momentarily when it shouldn't, possibly violating the hold condition. Timing reports do not indicate setup/hold violations. Zero-delay simulation is being used, but even with gate delays inserted, the behavior remains. Initial values are correctly applied and testbench sequences are consistent. I suspect this might be related to the feedback handling or synthesis optimization — but I’m not sure why only one instance would misbehave.

To simplify and improve simulation behavior, I rewrote the latch in a behavioral style, avoiding explicit feedback and modeling expected functional output. However, the glitch still persists in the same instance, and only that one — all other identical SR latch instances simulate as expected with the same testbench.

 

Has anyone seen this type of issue before or can help pinpoint what's going wrong here?

 Any help or suggestions would be greatly appreciated!

Thanks
Saranya 

  • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information