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
- UCIe Chiplet PHY & Controller
- MIPI D-PHY1.2 CSI/DSI TX and RX
- Low-Power ISP
- eMMC/SD/SDIO Combo IP
- DP/eDP
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
- Frontgrade Gaisler and wolfSSL Collaborate to Enhance Cybersecurity in Space Applications
- Digital Core Design Unveils DPSI5 - The Next-Generation IP Core for PSI5 Communication
- Matrox Video and intoPIX Expand Interoperable IPMX & ST 2110 Solutions with JPEG XS Innovation at NAB 2025
- HCLTech joins Samsung Advanced Foundry Ecosystem as a Design Solution Partner
- TeraSignal to Showcase Retimer-Less PCIe 6.0 over Optics Featuring Synopsys IP at OFC 2025