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
- CAN XL Verification IP
- Rad-Hard GPIO, ODIO & LVDS in SkyWater 90nm
- 1.22V/1uA Reference voltage and current source
- 1.2V SLVS Transceiver in UMC 110nm
- Neuromorphic Processor IP
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
- OmniSim: Simulating Hardware with C Speed and RTL Accuracy for High-Level Synthesis Designs
- Balancing Power and Performance With Task Dependencies in Multi-Core Systems
- LLM Inference with Codebook-based Q4X Quantization using the Llama.cpp Framework on RISC-V Vector CPUs
- PCIe 5.0: The universal high-speed interconnect for High Bandwidth and Low Latency Applications Design Challenges & Solutions
- Basilisk: A 34 mm2 End-to-End Open-Source 64-bit Linux-Capable RISC-V SoC in 130nm BiCMOS