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.

What does this mean in RC?

Status
Not open for further replies.

liletian

Full Member level 6
Joined
Mar 5, 2008
Messages
337
Helped
2
Reputation
4
Reaction score
2
Trophy points
1,298
Activity points
3,790
Hi Guys

I got this info after the irun. Can anyone please explain?

Thanks


Code dot - [expand]
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Info    : Both 'pos_unate' and 'neg_unate' timing_sense arcs have been processed. [LBR-162]
        : Non_unate 'timing_sense' inferred between pin 'B' and 'S' in libcell 'ADDFHX1'.
Info    : Both 'pos_unate' and 'neg_unate' timing_sense arcs have been processed. [LBR-162]
        : Non_unate 'timing_sense' inferred between pin 'A' and 'S' in libcell 'ADDFHX1'.
 
[COLOR="silver"]- --------------------[/COLOR]
 
Info    : Promoting a setup arc to recovery. [LBR-30]
        : The asynchronous input pin is DFFNSRX2/RN
 
[COLOR="silver"]--------------------------[/COLOR]
 
Info    : Promoting a setup arc to recovery. [LBR-30]
        : The asynchronous input pin is DFFNSRX2/RN


what does this mean?
 
Last edited by a moderator:

Hi Guys

I got this info after the irun. Can anyone please explain?

Thanks


Code dot - [expand]
1
2
3
4
5
6
7
8
9
10
11
12
13
14
Info    : Both 'pos_unate' and 'neg_unate' timing_sense arcs have been processed. [LBR-162]
        : Non_unate 'timing_sense' inferred between pin 'B' and 'S' in libcell 'ADDFHX1'.
Info    : Both 'pos_unate' and 'neg_unate' timing_sense arcs have been processed. [LBR-162]
        : Non_unate 'timing_sense' inferred between pin 'A' and 'S' in libcell 'ADDFHX1'.
 
[COLOR="silver"]- --------------------[/COLOR]
 
Info    : Promoting a setup arc to recovery. [LBR-30]
        : The asynchronous input pin is DFFNSRX2/RN
 
[COLOR="silver"]--------------------------[/COLOR]
 
Info    : Promoting a setup arc to recovery. [LBR-30]
        : The asynchronous input pin is DFFNSRX2/RN


what does this mean?

It's a benign message, saying that although the liberty file has a setup constraint on the reset pin, the tool will handle it as a recovery constraint (which is correct since it is a reset pin)
 

It's a benign message, saying that although the liberty file has a setup constraint on the reset pin, the tool will handle it as a recovery constraint (which is correct since it is a reset pin)

Thanks for the message.
the following case is not recoverable, correct?



416373) Clock pin absent in sequential cell(s) (RSLATX4)
Warning : Missing clock pin in the sequential cell. [LBR-525]
: (sage-x_tsmc_cl018g_rvt_tt_1p8v_25c.lib, block starting at: 416773) Clock pin absent in sequential cell(s) (RSLATXL)


Info : Mismatch in unateness between 'timing_sense' attribute and the function. [LBR-155]
: 'timing_sense' attribute between pin 'WB' and 'RB' in libcell 'RF1R1WX2' is 'neg_unate', but unateness determined from function is 'non_unate'.
 

Thanks for the message.
the following case is not recoverable, correct?



416373) Clock pin absent in sequential cell(s) (RSLATX4)
Warning : Missing clock pin in the sequential cell. [LBR-525]
: (sage-x_tsmc_cl018g_rvt_tt_1p8v_25c.lib, block starting at: 416773) Clock pin absent in sequential cell(s) (RSLATXL)


Info : Mismatch in unateness between 'timing_sense' attribute and the function. [LBR-155]
: 'timing_sense' attribute between pin 'WB' and 'RB' in libcell 'RF1R1WX2' is 'neg_unate', but unateness determined from function is 'non_unate'.

this one is more severe but could still be ok. really hard to tell, the liberty format is too complex and the tool that generate the liberty might have used something that RTLCompiler can't understand or interpret. I would recommend reporting a few paths that use the aforementioned cell and checking if it looks reasonable
 

this one is more severe but could still be ok. really hard to tell, the liberty format is too complex and the tool that generate the liberty might have used something that RTLCompiler can't understand or interpret. I would recommend reporting a few paths that use the aforementioned cell and checking if it looks reasonable


how can I find the path with this cell? Is there an easy way to do it?

Thanks,
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top