PKS timing

Discussion in 'Cadence' started by Giovanni, Oct 9, 2003.

  1. Giovanni

    Giovanni Guest

    Hi,

    I've a serious timing problem using Cadence PKS 5.0.
    After synthesis with Buildgates the tool seems to generate a correct
    timing report.
    Just after the Qplace step, (using the "do_optimize" command)
    PKS gives a timing report with a lot of "NaN" values both in
    "required time" and "arrival time".
    This error affects all the clocked modules.
    Can anybody help me?

    Thanks
     
    Giovanni, Oct 9, 2003
    #1
Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Ambit/PKS - Timing problem

  2. Why my timing parametrs don't show up in my verilog netlist

  3. Timing library (TLF) files problem

  4. Timing Optimization in Encounter

  5. problem about timing analysis in soc encounter

  6. NCELAB complains about 'negative timing check'

  7. How to eliminating timing violating paths?

  8. Modeling a twisted timing belt

Loading...