Automotive System & Software Development Challenges - Part 1
Frank Schirrmeister, Cadence Design Systems
EDN (November 5, 2013)
Today’s high-end cars contain between 70 and 100 embedded processors and run up to 100 million lines of code according to the IEEE Spectrum article “This Car runs on Code.” Specialized cars, like Indy cars can have many more sensors and data acquisition/telemetry components to optimize for racing. Integration of all the hardware and software needed to make any car perform correctly is no small task. It takes a lot of simulation, modeling, verification and IP.
This article will summarize the development challenges from analog-mixed-signal simulation to proper system configuration as well as hardware software co-design and outline some solutions that are essential to successful system development across the design chain.
To read the full article, click here
Related Semiconductor IP
- Post-Quantum Digital Signature IP Core
- Compact Embedded RISC-V Processor
- Power-OK Monitor
- RISC-V-Based, Open Source AI Accelerator for the Edge
- Securyzr™ neo Core Platform
Related White Papers
- Automotive System & Software Development Challenges - Part 2
- Using model-driven development to reduce system software security vulnerabilities
- Dealing with automotive software complexity with virtual prototyping - Part 1: Virtual HIL development basics
- CANDoSA: A Hardware Performance Counter-Based Intrusion Detection System for DoS Attacks on Automotive CAN bus
Latest White Papers
- DRsam: Detection of Fault-Based Microarchitectural Side-Channel Attacks in RISC-V Using Statistical Preprocessing and Association Rule Mining
- ShuffleV: A Microarchitectural Defense Strategy against Electromagnetic Side-Channel Attacks in Microprocessors
- Practical Considerations of LDPC Decoder Design in Communications Systems
- A Direct Memory Access Controller (DMAC) for Irregular Data Transfers on RISC-V Linux Systems
- A logically correct SoC design isn’t an optimized design