Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Next Blog
Create Blog
VLSI placement
This is a blog for people preparing for placement and company interviews in the field of vlsi and electronics. this blog contains important
questions which are generally asked in company written and interview exams
Home
Projects
Computer Programming
Company Papers
VLSI Testing
Analog basics
VHDL tutorial
Pageviews
49,178
CMOS part 3
Facebook Share
Share
View stats
Labels
Self heating occur in a bidirection wire while electromigration occur in single direction.
VVI Can both pmos and nmos transistors pass good 1 and good 0? Explain.
No, NMOS pass weak one. Vdd Vt
Vgs > Vt Therefore, Vs < Vdd - Vt always since after that transistor will be cut off.
----------------------- ----------------------- ----------------------- ----------------------How do you size PMOS and NMOS transistors to increase threshold?
As a designer you cant change NMOS and PMOS size in order to change Vt.
The only way you can change Vt as a designer is by changing the Body Bias.
What are the different methodologies used to reduce the charge sharing in dynamic logic?
Blog Archive
2014 (5)
2012 (63)
December (2)
November (9)
October (46)
Ques : Consider a system which works at a clock frequency of 100Mhz. Suppose you have a setup voilation of 0.2ns and
hold voilation of 0.8ns calculate the clock frequency at which the system work fine?
Hey guys, pls give me equations for tsetup and thold...also along with your answers.
Solution: For setup time,it's easy. The system can have a period about (10ns+0.2ns)=10.2ns, which means 98MHz. But for
hold time violation 0.8ns, I am rather confused. Slow down the system clock has no effect on hold time since hold time
compares the same clock edge. The only method to solve hold violation is adding buffers, not slow down the whole system
clock.
Another Answer:
How your are missing important point ... if Setup & hold are observed in same path, when you add buffer into the data to
provide porpagation delay of 0.8 ns for fixing hold violation, the setup violation will also increased by 0.8ns.
So the effective setup violation will be 1ns after fixing hold violation & you need to increase the clock period by 1ns to fix
the effective setup violation (10 + 1= 11ns). (Reduce the clock frequency = 1/11ns)
http://www.vlsiplacements.com/2012/10/cmos-part-3.html
Network basic - 1
hardware question - 1
1/5
28/04/2015
Answer is fix the hold time violation, because the setup violation can always be fixed by just slowing down the clock.
Generally hold time is not in the user control.
We try to avoid fixing hold time at the synthesis level.
CMOS part 7
Hold time is independant of clock speed which makes it a potential design killer. No matter how much you slow your clock
you may still have hold violations. They are easily fixed by inserting buffers or downsizing cells (but making sure not to
create any setup violations). Also a good idea to add some extra hold margin.
CMOS part 4
1)
CMOS part 6
CMOS part 5
CMOS part 3
CMOS interview and job questions
part 2
VLSI - STA advance terms
September (4)
August (2)
2011 (8)
Updates !!!
www.vlsiplacements.com
Any body want to be contributor to this blog :
contact :
sumit.raj.iiit@gmail.com
Followers
Members (15)
Hold violations are more critical than setup. bcoz for solving setup violation u can chage the operating frequency and can
make ur chip work. but if there is hold violations then the functionality cant be achieved. the chip function will be failed.
Setup and hold time violation for a latch
Latch Setup and Hold window appears on falling edge if it's high level sensitive latch or vice versa.
Once again, there are only recovery and removal times for a latch. not setup and hold times.
Subscribe To
Posts
Comments
Contributors
satish verma
RaJ
http://www.vlsiplacements.com/2012/10/cmos-part-3.html
2/5
28/04/2015
Popular Posts
Question : There are 100 setup and 100 hold violations in ur design. In order to have a successful chip which one do u
consider first and why ?
Answer1 : setup time violations can be taken care of by reducing the clock frequency. but the hold time violation is due to
unnecessary delays on the clock tree.(unwanted clock skew due to bad clock tree design or place and route).therefore
removing the hold time violation is a preferred option. this might as well require some changes in the design netlist...
Answer2 : first hold time violation should be sorted out.
even if u satify setup time requirements for a particular frequency, ur system will land up in metastable state if hold is not
met.
This hold time should be checked at every flop stage for proper operation of the ckt.
RACE condition
I think it is because there is a sufficient amount time for the inputs to settle down(TCLK/2) before the output voltage is
allowed to change(after TCLK/2). i.e if all the inputs cannot arrive at the processing unit at the same time, u should not
manipulate output with only few inputs.
i.e read everything -then process the output.
race condition and hold time violation is two different thing!
hold time violation and setup time violation mean you can't meet timing request!
race condition mean the code you write will cause uncertain for some state!
If "TClk-q+Tcomb < Thold" leads to a Race condition.
TClk-q = Clock to Q path Delay
Tcomb=Combinational path delay between two flip-flop
Thold = Flip-flop hold time
Race condition can lead to a Hold violation.
Race is of hardware and one race is in verilog
Race condition in Verilog context refers to a condition wherein the results are unpredictable. For e.g. consider:
always @(a)
b = ~a;
always @(a)
$display ("a %b b %b ",a,b);
race can be avoided in verilog using non-blocking stmts appropriatley.
Race condition: defines a condition when a device's output depends on two [or more] nearly simultaneous events to occur
at the input(s) of a device and cause the device's output to switch. One way to design in a race condition is to use the same
signal to perform two [opposing] functions. In some cases a race condition could also be a logic Hazard. Another case for a
race condition could be caused from floating inputs.
http://www.vlsiplacements.com/2012/10/cmos-part-3.html
3/5
28/04/2015
Imp
Let me add a "rule for the beginner":
Verilog blocking signal assignment ("=") is similar to VHDL variables,
while non-blockling signal assignment ("<=") is similar to VHDL signals.
No comments:
Post a Comment
http://www.vlsiplacements.com/2012/10/cmos-part-3.html
4/5
28/04/2015
Comment as:
Publish
Google Account
Preview
Newer Post
Home
Older Post
Fish
Share it
http://www.vlsiplacements.com/2012/10/cmos-part-3.html
5/5