Integration and Testing the Integration
The US National Highway Traffic Safety Administration (NHTSA) recently released a deep report into last year's issue with "unintended acceleration" on certain Toyota cars. They actually employed a team from NASA who analyzed the throttle control software using a wide range of cutting-edge tools. Reading their report gives a good idea for how embedded control software is developed, and the challenges inherent in validating it.
The conclusion is that the software is not a likely cause of the problems. The real meat of the report (and its appendixes) is just how this conclusions is reached, and what it says about the tools that could be applied to develop embedded software with greater confidence about its correctness.
To read the full article, click here
Related Semiconductor IP
- CXL 3 Controller IP
- PCIe GEN6 PHY IP
- FPGA Proven PCIe Gen6 Controller IP
- Real-Time Microcontroller - Ultra-low latency control loops for real-time computing
- AI inference engine for real-time edge intelligence
Related Blogs
- I3C IP: Enabling Efficient Communication and Sensor Integration
- Navigating Integration Challenges for the RISC-V Ecosystem with Networks-on-Chips (NoCs)
- IP Integration : What is the difference between stitching and weaving?
- Heard at DAC: is IP integration the real high-level design?
Latest Blogs
- Arm Compute Platform at the Heart of Malaysia’s Silicon Vision
- IEEE 802.1ASdm-2024 Becomes an IEEE Standard – Advancing Time-Sensitive Networking
- Introducing the MIPS Atlas Portfolio for Physical AI
- Real-Time Intelligence for Physical AI at the Edge
- Moving the World with MIPS M8500 Real-Time Compute Solutions