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.

Query regarding timing from faster to slower clock domain

Status
Not open for further replies.

jjean

Newbie level 5
Joined
Feb 24, 2009
Messages
9
Helped
1
Reputation
2
Reaction score
1
Trophy points
1,283
Activity points
1,360
Hi all,

I had a question regarding timing from a faster clock domain to a slower clock domain, say clkA to clkB.

Consider the launching clock to be of period 2 (0,1) and the capturing clock to be of period 4 (0,2).
So, the base period is 4.
The most constraining setup check is between launch edge at 2 and capturing edge at 4.
The hold check is relative to the setup.For the setup check between 2 and 4 the possible hold checks are between
1) 2 and 0
2) 4 and 4
The most constraining is between 2 and 0 and so, this is the hold check.

But,when I report timing I see that although setup check is done correctly, hold check is done between 4 and 4, not between 2 and 0.
Is this correct? Could somebody explain this tool behaviour?

Appreciate any help.

Thanks,
jean
 

Re: Query regarding timing from faster to slower clock domai

jjean said:
Hi all,

I had a question regarding timing from a faster clock domain to a slower clock domain, say clkA to clkB.

Consider the launching clock to be of period 2 (0,1) and the capturing clock to be of period 4 (0,2).
So, the base period is 4.
The most constraining setup check is between launch edge at 2 and capturing edge at 4.
The hold check is relative to the setup.For the setup check between 2 and 4 the possible hold checks are between
1) 2 and 0
2) 4 and 4
The most constraining is between 2 and 0 and so, this is the hold check.

But,when I report timing I see that although setup check is done correctly, hold check is done between 4 and 4, not between 2 and 0.
Is this correct? Could somebody explain this tool behaviour?

Appreciate any help.

Thanks,
jean


Hi Jean,
I think you are wrong. The tool's behavior is correct.
Yes, there are two relations for hold timing check. 4->4 and 2->0.
But the most restrictive one is 4->4.
hold timing requirement is:
data arrival time > data required time
data arrival time = launch clock start time + data path delay
data required time = latch clock start time + hold time

Right?
 

    jjean

    Points: 2
    Helpful Answer Positive Rating
Re: Query regarding timing from faster to slower clock domai

Hi Gavinsun,

You're right. 4 and 4 is more constraining.

Thanks,
Jean
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top