|
Post by account_disabled on Jan 1, 2018 6:03:15 GMT -8
Hi, I am seeing big clock skew on our designs with EDI flow (we are using foundation flow). After debugging this skew problem, I found that clock skew is due to miscorrelation between timing engines at different stages. For example on a routed database (a) IQRC extraction with "default" timing engine reports 230ps skew (b) IQRC extraction with "signal storm" timing engine reports 305ps skew But if I run "ckECO -postRoute -useSpecFileCellsOnly", tool starts skew optimization from 190ps skew. So looks like CTS uses a totally different timing engine and its hard to achieve good skew until ckECO sees correct skew. Please let me know if there are any tricks/workaround to run ckECO based on signoff timing engine or optimizing skew. Any suggestions? Please help. Thanks! I didn't find the right solution from the Internet. References: community.cadence.com/cadence_technology_forums/f/digital-implementation/21412/clock-skew-issue-due-to-timing-enginesDigital Transformation Marketing Examples
|
|
|
Post by Jasper Richten on Dec 18, 2018 7:17:52 GMT -8
Toyota Corolla 2019 is very nice car! I prefer brand Tayota iversta.com/ at all also for rent. Who is from Canada, does this brand popular in Canada or not? thanks a lot)
|
|
|
Post by Mastroe on Aug 12, 2019 4:41:52 GMT -8
BTW, you can do all these operations with an OBD scanner. I recommend using it especially if you have any kind of repair service - it's the fastest way to read the engine parameter or find the faulty part. You can simply download it here: play.google.com/store/apps/details?id=com.motordata.obd
|
|