At the Design and Verification Conference last February, there was a panel ("Where Does Design End and Verification Begin?") that discussed the impact of new verification tools that focus on just one problem area and thereby enable more effective verifcation. Engineers no longer have to create a solution out of their own dynamic simulator, static analyzer, or ABV tools.
In the example of Meridian clock-domain-crossing (CDC) verification, a mix of structural, formal and dynamic methods operating under-the-hood, ensure that an SoC will not fail with a metastability issue. Other examples are state-of-the art Lint analysis, and X-propagation and reset verfication / optimization.
At Real Intent, we call this new category Static Verfication. Gary Smith calls them Verification Apps. I see these as important addition to our tool chest so engineers don't design SoCs that we cannot verify.
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.