Arm on Autonomous Automotive
Let me start this post with a brief history of autonomous driving. Most people date the start of the autonomous driving era to 2004, with the Grand Challenge in the Mojave Desert over a 150-mile course. That turned out to be 142 miles longer than necessary, since the furthest any vehicle got was eight miles and the $1M prize was not awarded. Perhaps a more auspicious year to pick as the start of the autonomous driving era would be 2005, when the second Grand Challenge took place, with the prize money up to $2M. Five vehicles finished the entire 132-mile course. (I wrote about this in one of my first blog posts here Ten Years Ago Self-Driving Cars Couldn't Go Ten Miles.) The third Grand Challenge a couple of years later involved all the vehicles, along with other vehicles with professional drivers, all driving around a disused US Air Force base at the same time. Many vehicles successfully negotiated the course, obeying traffic laws and avoiding other vehicles. In just a few years, the technology had advanced so fast that everyone assumed we'd all be driving autonomous cars within another ten years...by 2017 or so.
To read the full article, click here
Related Semiconductor IP
- TSMC 7nm 0V75 / 0V9 ESD Local Clamp – Low Cap
- TSMC 65nm 3V3 ESD Local Clamp – Rad Hard
- TSMC 5nm 1V8, 1.2V and 0.9V ESD Local Protection – Low Cap
- TSMC 3nm 3V3 ESD Local Clamp
- TSMC 3nm 1V2 ESD Local Clamp – Low Capacitance
Related Blogs
- Arm Mali-G78AE becomes world's first fully certified automotive grade GPU
- Cortex-M55: Functional Safety ready and fuelling the next generation of automotive microcontrollers
- Cortex-M23: Now Enhanced for Safety-critical Automotive Applications
- Virtual Platforms from Arm and Partners Available Now to Accelerate and Transform Automotive Development
Latest Blogs
- Beyond Trusted: What the NSA’s New Guidance Means for Hardware Security
- A scalable, shader-programmable vector graphics GPU core for low-power MCUs
- Navigating ISO 26262 Part 11: A Guide for Semiconductor Architects
- Embedded Security explained: Digital signatures
- Hardware security verification must go beyond functional testing