I am used pks tool from candence very well and now using soc encounter.
I think lot of people faced problems in timing closure with different modes in design. Because if we meet timing in one mode it can violate other modes. so multi modes helps a lot in this situation.
There is one more point about multi mode is that we can do area recovery at stage if we define all modes in a design. This helps in routing congestion a lot.
I have eone question about the run times of soc in while doing multi mode timing optimization if design is large.
Hi Anil,Encounter's MMMC capabilities are pointed at solving the exact problems you describe. I hope you give it a try.Regarding run times, I'd generally expect to see run-time scale linearly for each additional view you add. So, if it takes 2 hours for optimization of 1 view, I'd expect it to take 10 hours (or perhaps a little less) for optimization of 5 views. Compared to how cumbersome it is to manage optimization incrementally across multiple views without disrupting timing in inactive views, I think most users would agree that MMMC adds value in excess of the run-time required.Hope this helps,Bob
Hi Anil,Adding to the point made by Bob, SOCE 6.2 certainly does a very good job in reducing the run time for multi-mode multi-corner optimization. For one of my recent implementation (ARM core) with 3 active views, run time is lower than 3 times one view opto run time.Thanks,Niket
Hello All , Thanks for giving run-time information. I already used MMMC capabilities of SOC and other tools just i want to know th latest run-time of 6.2 version.
SOCE 6.1 USR3 should be up to date with the latest performance improvements.