Stats

  • Locked Locked
  • Replies 6
  • Subscribers 62
  • Views 14867
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Long Run Times

sureshm

 Hi

   I am using EDI-09.12.00 version for my synthesis. 

I am not aware of the total design size, but the total number of the flops in the design are around 365k. 

I am wondering if the tool has the capability of handling such high instance count.

I am seeing a lot of run times being there.. it stops after 

Synthesizing to gates
Tue Feb 01 21:33:19 IST 2011
Mapping mydesign to gates.
      Mapping 'mydesign'...
        Preparing the circuit
          Pruning unused logic
 

 I am not sure whether

1) The tool is proecssing any data internally 

2) or the tool got hung there.. 

 

how do i debug the reason for the long run times. 

Thanks

suresh 

 

Parents

  •  Hi Suresh,

    I am on the third time replying to this message due to my fabulous browser, NOT :(

    Anyhow, 365K flops is certainly doable for RC. In fact, I am currently working on a design of 1.3M flops and 9M instances so not a problem. That being said, there are other reason why you MAY want to split it. This will improve your turnaround time at the possible expense of QoR as well as the need for add'l scripts.

    As per you debug questions, it would be helpful if you can provide more detail as follows

    (1) Are you using N2N or your own scripts ?

    (2) Starting from netlist or HDL ?

    (3) if netlist, were you meeting timing ?

    (4) What is your information_level set to ?

    (5) You say hung but what does that exactly mean ? 1 hour ? 10 hours ? 10 days ?

    (6) what runtime did you expect ? Memory ?

    (7) what version of RC are you using (found at top of log) ?

    (8) what effort level are you running for syn -to_gen ? syn -to_map ? syn -to_placed ?

    (9) what are your runtime for some of the stages that complete ?

     Not trying to flood you with questions but there is not much that we can do to help without answers to some of those questions

    regards,

    gh-

Reply

  •  Hi Suresh,

    I am on the third time replying to this message due to my fabulous browser, NOT :(

    Anyhow, 365K flops is certainly doable for RC. In fact, I am currently working on a design of 1.3M flops and 9M instances so not a problem. That being said, there are other reason why you MAY want to split it. This will improve your turnaround time at the possible expense of QoR as well as the need for add'l scripts.

    As per you debug questions, it would be helpful if you can provide more detail as follows

    (1) Are you using N2N or your own scripts ?

    (2) Starting from netlist or HDL ?

    (3) if netlist, were you meeting timing ?

    (4) What is your information_level set to ?

    (5) You say hung but what does that exactly mean ? 1 hour ? 10 hours ? 10 days ?

    (6) what runtime did you expect ? Memory ?

    (7) what version of RC are you using (found at top of log) ?

    (8) what effort level are you running for syn -to_gen ? syn -to_map ? syn -to_placed ?

    (9) what are your runtime for some of the stages that complete ?

     Not trying to flood you with questions but there is not much that we can do to help without answers to some of those questions

    regards,

    gh-

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.