Unfortunately, refining tools and flows requires incorporation of lessons learned, and this is true for almost every new process node. It's a real conundrum, because you don't want to be the first one to tape out a big SoC in the latest process, but time to market pressures don't give you much leeway to let others blaze the trail ahead of you.
For current synthesis and analysis tools, they haven't addressed critical issues for nanotechnology For example, the product leakage is often 2X-4X higher than estimation because it is due to incorrect power model. The high design margin (20%-30%) in current SSTA is due to improper DFM setup, the actual margin can be reduced by half.
Perhaps I could be even bolder and suggest that verification is much like the drug industry. Even if there were a cure, it is more profitable to sell things that work on the symptoms which keeps the customer coming back for more.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.