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
- Wi-Fi 7(be) RF Transceiver IP in TSMC 22nm
- PUF FPGA-Xilinx Premium with key wrap
- ASIL-B Ready PUF Hardware Premium with key wrap and certification support
- ASIL-B Ready PUF Hardware Base
- PUF Software Premium with key wrap and certification support
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
- RISC-V in 2025: Progress, Challenges,and What’s Next for Automotive & OpenHardware
Latest White Papers
- Boosting RISC-V SoC performance for AI and ML applications
- e-GPU: An Open-Source and Configurable RISC-V Graphic Processing Unit for TinyAI Applications
- How to design secure SoCs, Part II: Key Management
- Seven Key Advantages of Implementing eFPGA with Soft IP vs. Hard IP
- Hardware vs. Software Implementation of Warp-Level Features in Vortex RISC-V GPU