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.

Register Log in

Error in Delay Measurement ---- Spice

Status
Not open for further replies.
rahdirs

rahdirs

Advanced Member level 1
Joined
May 22, 2013
Messages
424
Helped
93
Reputation
192
Reaction score
91
Trophy points
1,308
Location
Mordor
Activity points
4,492
Hi,

I'm trying to measure the delay in hspice for an inverter by using .measure command.

Code: 
**Test inverter 
.TEMP 110 
**Use high temperature to simulate worst case delay and leakage power 
.OPTION 
+            ARTIST=2 
+            INGOLD=2 
+            MEASOUT=1 
+            PARHIER=LOCAL 
+            PSF=2 
+            POST 
.inc '/home/**/NMOS_VTL.inc'  ** I've hid the directory path while posting 
.inc '/home/**/PMOS_VTL.inc' 
.include inverter.sp 
v1 vdd! 0 1.1v 
v2 vin 0 PULSE(0 1.1V 1ns 0.02ns 0.02ns 1ns 3ns) 

.op 
.tran 10p 20ns 

.MEASURE TRAN tdlay TRIG Vout VAL = 0.5 TD = 10n RISE = 2
+ TARG Vin VAL = 0.5  FALL = 2

.end


I've got an error --
**error** Measure statement failure;
rise, fall, or cross must be specified if
at=val was not specified in trigger
Click to expand...

I've specified TD = 10n in the trigger, why is it still pointing to at = val ?

Regards,
rahdirs
 

ThisIsNotSam said:
try using RISE=LAST
Click to expand...

I've tried this & this:

Code: 
.MEASURE TRAN tdlay TRIG Vout VAL = 0.5 AT = 10n RISE = LAST
+ TARG Vin VAL = 0.5  FALL = LAST

.MEASURE TRAN tdlay TRIG Vout VAL = 0.5 TD = 10n RISE = LAST
+ TARG Vin VAL = 0.5  FALL = LAST

But both of them give the same error:

**error** Measure statement failure;
rise, fall, or cross must be specified if
at=val was not specified in target
Click to expand...
 

step1 : when you simulate it, do you see the waveforms? do they look like what they should?

step 2: simplify the trigger. take TD out of the command.
 

ThisIsNotSam said:
step1 : when you simulate it, do you see the waveforms? do they look like what they should?

step 2: simplify the trigger. take TD out of the command.
Click to expand...

1. Yes, the o/p waveforms are as they should be.
2. I've removed TD = 10ns/ AT = 10ns, even then it gives same error.
 

Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top