How to Safeguard Automotive OTA Updates at Scale
Imagine driving down a scenic country road at night and seeing the gleam of a deer’s eyes ahead. Before you can react, the car slows and steers away from the deer and avoids the car in the next lane. This is the power of driver assist and AI-powered autonomous driving. Now imagine the same scenario a few days later, and the vehicle does not respond. Not only is the vehicle damaged, but there is also wildlife and passenger injury. What happened?
This is where the power of automotive over-the-air (OTA) updates comes into play. Manufacturers can now determine not only how the vehicle reacted but why. Was it a software error, a bad software update, or simply an adjustment in operating parameters that led to the event? Never have manufacturers had such insight into a vehicle’s operation. Never have they had the ability to fix issues at such large scale without a service visit. OTA update capabilities provide great benefits and bottom-line savings, but poor implementation or bad software development practices could lead to costly mistakes.
To read the full article, click here
Related Semiconductor IP
- Rad-Hard GPIO, ODIO & LVDS in SkyWater 90nm
- 1.22V/1uA Reference voltage and current source
- 1.2V SLVS Transceiver in UMC 110nm
- 1.8V/3.3V GPIO With I2C Compliant ODIO in GF 55nm
- Verification IP for UALink
Related Blogs
- What is OTA in automotive? Over the air updates explained.
- A Look Under the Hood at MIPI CSI-2 and MIPI DSI-2 in Automotive
- How Imagination is steering the automotive industry to a safer future
- How Software-Defined Vehicles Expand the Automotive Revenue Stream