EDA, AVs Find Common Language
By Junko Yoshida, EEtimes
August 12, 2019
Complex systems — whether a system-on-chip or autonomous vehicles — can frustrate design engineers who, after months of painstaking work, have to go back and verify that the system they just designed actually performs the way they intended.
SoCs and autonomous vehicles (AVs) are both built in a “black box,” which by nature makes it hard to find bugs “hiding in places that you don’t think about,” said Ziv Binyamini, CEO and co-founder of a Tel Aviv-based startup called Foretellix.
In testing and verifying an SoC, two measures are deemed essential: “code coverage,” which tells how well the code is tested by stimulus, and “functional coverage,” a way for the user to write certain instrumentation logic that monitor how well the stimulus is covering various functions.
Foretellix believes that similar coverage-driven disciplines should apply to AVs when car OEMs test safety.
To read the full article, click here
Related Semiconductor IP
- RDMA IP
- PCIe Controller
- USB Controller
- MTP (Multi-Time Programmable) IP
- OTP (One-Time Programmable) IP
Related News
- STARC Selects Verisity's e Verification Language for IP Reuse <!-- verification --> --> "Arial,Helvetica" size=-1 > Headline News
- Engineer offers open-source verification language <!-- verification -->
- Industry Support Builds for Intel"s Formal Property Verification Language Initiative
- Intel pushes assertion language as EDA standard <!-- verification -->
Latest News
- Top 10 Global Fabless IC Design Houses Post 73% YoY Revenue Growth in 2Q26; AMD Breaks into Top Three
- Arasan furthers MIPI I3C® compliance with its participation at the I3C® interop in Taipei
- TSMC August 2026 Revenue Report
- Qualitas Semiconductor Signs MIPI IP Integrated Solution Licensing Agreement with CoAsia SEMI
- Alliance for Open Media Members Showcase AV2 Ecosystem Developments at IBC 2026