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.

About primetime's case analysis

Status
Not open for further replies.

hgby2209

Full Member level 2
Full Member level 2
Joined
Mar 7, 2003
Messages
134
Helped
8
Reputation
16
Reaction score
8
Trophy points
1,298
Activity points
1,105
case analysis primetime site:edaboard.com

In primetime, if report_timing can report all timing path, why need to use case analysis or mode analysis?
 

No, the report_timing comand reports the worst slack path in the current design defaultly.We use the case and mode analysis to set TEST_SE and TEST_MODE to logic zero.This can tell primetime that it is not test mode.
 

Hi ! horzonbluz,
Sorry !! I still don't know why need to tell primetime that it is test mode or not ?

What I know is using report_timing to analyze setup & hold time for every timing path and using report_constraint -all_violators to check violation of design rule & constraint.
 

Hi, hgby2209:

Test mode might run at a totally different speed from the operation mode. So you need to disable the test mode to run the normal function first, then disable the normal function, then check your testing condition again.

Good Luck,
 

Hi ! sandusty,
Thanks a lot for your answer!!
So I can use case analysis to simulate the real world's test mode, and analyze the max. working frequency in test mode.
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top