Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

[SOLVED] Pin Order Mismatch Between Quantus QRC Extracted Netlist and Maestro Subcircuit Instantiation

Status
Not open for further replies.

m.m.m

Newbie level 4
Newbie level 4
Joined
Jul 14, 2017
Messages
7
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,374
Hi everyone,

I’ve run into an issue with my design when using Quantus QRC (Assura) for parasitic extraction and simulating the design in Cadence Virtuoso with Maestro.

After running Quantus QRC on my layout, it generated a SPICE netlist for the extracted view. However, I’ve noticed that the pin order in the subcircuit within this SPICE netlist is different from the pin order used when Maestro instantiates the same subcircuit during simulation. As a result, my design doesn’t function properly in the simulation.

Here's the instance in the schematic view:
1726495904683.png

and the created netlist for simulation:
1726495853448.png
(net5 is connected to OUTB.)
But the extracted hspice subckt has the following port config:
1726495860475.png

And the layout pins have the same names and labels as the ones in schematic, and LVS gives no errors.
1726496124908.png


I can manually reorder the subckt pin order in the netlist but it would be rewritten each time I extract the netlist, which is not ideal at all.
So I'd appreciate your suggestions.
 

Hi @m.m.m ,
The first idea that comes into my mind is that you must have changed your symbol manually after modifying the schematic which may have led to the problems in pin order. You can try to open your schematic view, do Check and Save and after that go to Create -> Cellview -> From cellview and in pop-up menu click "modify". It should suggest you to update the CDF order as well and after that the port order should be fixed.
Alternatively, you might go to (in CIW): Tools -> CDF -> Edit.. and fix it directly from CDF manager.
Hopefully, that helps.
 

To my understand
Assura was used to generate SVDB.
Quantus to generate extracted view.
Questions:
1. What is the type of extracted view which was generated (selected QRC output)?
2. Does issue occurs for different output types?
3. Is CDF consistent with netlist?
 

Hi @m.m.m ,
The first idea that comes into my mind is that you must have changed your symbol manually after modifying the schematic which may have led to the problems in pin order. You can try to open your schematic view, do Check and Save and after that go to Create -> Cellview -> From cellview and in pop-up menu click "modify". It should suggest you to update the CDF order as well and after that the port order should be fixed.
Alternatively, you might go to (in CIW): Tools -> CDF -> Edit.. and fix it directly from CDF manager.
Hopefully, that helps.
Thank you, However recreating the cellview symbol didn't fix it either.

To my understand
Assura was used to generate SVDB.
Quantus to generate extracted view.
Questions:
1. What is the type of extracted view which was generated (selected QRC output)?
2. Does issue occurs for different output types?
3. Is CDF consistent with netlist?
Thank you Dominik for your response,
I'm extracting Spice output from QRC.
1726500210877.png

I tried the Dspf type and it had the same problem.
I haven't had experience with reading/configuring the CDF. Could you please tell me what I should be looking for? I couldn't find a proper tutorial.
--- Updated ---

I switched the netlist extraction option to av_extracted. now the problem is changed 😐
the instance in the netlist has an extra VDD pin for some reason. But this time the port order is correct at least.
instantiation:
1726507030349.png

subckt definition:
1726507038117.png
 
Last edited:


Maybe you can try providing the pin order file in your QRC setup... (but it's better to use dspf output I think)
Also, try creating extracted view and see if it helps:
Yeah, I ended up using the extracted view and it seems to be working fine.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top