Lynx

About a month and a half ago, I wrote a 5 part series of blog posts on the newly introduced Lynx Design System from Synopsys: Part 1 - Synopsys Lynx Design System Debuts at SNUG Part 2 - Lynx Design System? - It’s The Flow, Stupid! Part 3 - Strongest Lynx Part 4 - The Weakest Lynx Part 5 - The Mising Lynx - The ASIC Cloud One key feature, the inclusion of pre-qualified technology and node specific libraries in the flow, was something I had pushed for when I was previously involved with Lynx (then called Pilot).

I know. I know. I know. I said that I was going to publish the final post in a 3-part series on Synopsys Lynx last Friday. However, as I put my notes together, I realized how much there is to say. So, I’m breaking up the last post into 3 separate posts: The Strongest Lynx, The Weakest Lynx, and The Missing Lynx (clever, huh?).  First, the Strongest Lynx. I think that the best way to understand the strengths of Lynx is to consider who is Synopsys’ intended customer for this flow offering. After all, the offering is designed for them.