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.

IBM cms9flp & Assura QRC strange problem

Status
Not open for further replies.

jimito13

Advanced Member level 1
Joined
Nov 17, 2008
Messages
464
Helped
130
Reputation
262
Reaction score
113
Trophy points
1,323
Location
Greece
Activity points
4,929
Hello all,

I will try to describe my problem the better i can.I have an op-amp design that consists of several cells (main opamp,gain boosters,cmfb,biasing).I have created the layout of all the above cells and i pass successfully from DRC and LVS runs (clean runs,no errors no warnings).The last step is to perform the parasitics' extraction and run post layout simulations.Well,here things become a little bit strange...Before i describe my problem in depth i must say that my design kit is IBM's cms9flp and the versions of cadence virtuoso and assura are IC6.1.3.500.13 and 3.2_USR2_HF11 respectively.

I run LVS for each cell successfully (clean results) and then i run successfully as well the assura QRC run (no errors-no warnings) for all my cells and the result is the well known message of assura with the av_extracted view's name and location in the library.

Next step is to simulate the av_extracted views.For this i create a schematic with all the above cells interconnected as symbols and i use the av_extracted declaration under Environment submenu of ADE L.

I run DC analysis at first and here is my issue.The currents in all branches of the circuit are far away from the designed values.From a quick thought you can say that i made mistake in transistor sizes during layout but this should be reported by LVS but in any case i double checked this by myself to be absolutely certain.Second thought is that i have not calculated correct the widths of all metals that make the interconnections in the design,i double checked this as well according to pdk's rules for metals and viases.With a more careful view in the values of the currents that dc analysis resulted i noticed that all of them are divided by the product (m*nf),where m is multiplicity and nf number of fingers!Looking at the vdd symbol i see that my circuit consumes X mA but if i add all the currents from the subcells i do not ever reach X/4 mA,so i ask myself where is the rest of the current consumed?!Another strange thing is that even though that all currents are wrong calculated the biasing voltages from the current mirrors are exact to the design values...

Has anybody else come up with such an issue with this or another IBM's pdk??Do you think that i should report this straightly in IBM's support??

PS. It is urgent for me since tape out date is close!!

Thanks in advance for any helpful answer.
 

... the currents ... are divided by the product (m*nf), where m is multiplicity and nf number of fingers!
... my circuit consumes X mA but if i add all the currents from the subcells i do not ever reach X/4 mA ...
Hi jimito,
your first remark suggests the currents are too low, whereas the second note gives the impression the total current is too high, seems somewhat contradictory, isn't it?
 

Hi erikl,

Yes it is absolutely contradictory and that's why i am wondering where is the problem...It seems that the circuit "burns" the desired value of total current (the same with the value i get when i simulate the schematic with the symbols not as av_extracted views but as schematic views) but when i add all currents "by hand" from all branches i am far away from this annotated value on the VDD symbol of schematics L.After some observation on the annotated values i noticed that the indicated current on the schematics L after the dc analysis is the current that flows into the one finger of a transistor even if it has multiplicity factor (bus more exactly) or not,that's why i wrote in my previous post that all values are divided by the product (m*nf).

On the other hand,i simulated a test case with the main opamp only and biases from ideal sources and an ideal cmfb circuit that i have created and the problem still remains when av_extracted view is the simulated...

Any other idea or you think that IBM will give the answer?

Thanks a lot in advance.

Regards,
Jimito13
 

After some observation on the annotated values i noticed that the indicated current on the schematics L after the dc analysis is the current that flows into the one finger of a transistor even if it has multiplicity factor (bus more exactly) or not, that's why i wrote in my previous post that all values are divided by the product (m*nf).
If you use the bus representation, the listed current is given extra for each of the "bus" transistors, i.e. it will list the individual currents for each transistor MN1<0>, MN1<1> ... and so on, which should be equal in the schematic representation.

... the problem still remains when av_extracted view is the simulated...
Any other idea or you think that IBM will give the answer?
Low threshold process with relatively high leakage currents, perhaps? Yes, better ask IBM !

Rgds, erikl
 

Hello erikl,

Well we contacted IBM and they admitted that there is an error while the total current is calculated when the av_extracted view is post simulated.They didn't give us any solution instead of proposing us to change all fets from my design to nfet_rf and pfet_rf (now i use the regular fets-nfet,pfet and the respective lvt versions)...Only in this case they said that the problem is solved...Anyway,this is the least annoying thing since if i multiply the multiplicity factor with the number of fingers and the simulation current i get the total correct current that i expected.So,i suppose that i am ok with it.But...

There is another more difficult issue that hasn't been solved up to now even from IBM's support (they proposed me the same solution i wrote above for this issue as well !!).After simulating my opamp i notice severe DC voltage mismatches at various symmetrical branches (20mV the one and 700mV for example the other !!!).We checked the layout with my professor and he admitted as well that everything is ok and that those mismatches cannot be explained...We made all the checks (parasitic resistances,identical transistors' parameters,width of interconnection cables,symmetries,distances etc...) that must be done and we didn't find any problem to my layout.My professor insists that i must change all fets to RF fets for a cell and post simulate it,if problem still exists then he says that we must report back to IBM.This is a little bit difficult to be done.Have you ever seen something like that happening during post simulation with a specific design kit and in this case what did you do to solve it??I upload a pic that illustrates the issue i report above

Thanks in advance,

Best Regards,

Jimito13
 

Attachments

  • mismatch.png
    mismatch.png
    36.1 KB · Views: 127
Last edited:

... i must change all fets to RF fets for a cell and post simulate it,if problem still exists then he says that we must report back to IBM.This is a little bit difficult to be done.
True. But you know that you can change all transistors of the same kind (same type, W/L, m, f) at the same time?

Have you ever seen something like that happening during post simulation with a specific design kit ...
Never!

I upload a pic that illustrates the issue i report above
I don't see the issue: "22.73m" is the drain voltage of the pMOS - like the node voltage "511m" of node Vb 15 at the pMOS to the left (T169<1:2>). What's the problem?
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top