Observation: "[if you write buggy software], there's reason for you to get an off the shelf option"
Question: Are you saying if they used Android Automotive this could never have happened?
Reference: similar event for Android, last week: https://linustechtips.com/topic/1538248-pixel-phones-using-m...
Disclaimer: Former Googler, did not Work closely with Automotive, Worked closely with Android.
In this particular case, there's nothing particularly unique that Rivian is doing with their Infotainment system that couldn't already be handled by an incumbent in the space, (Android Automotive, QNX, etc.) especially given how modular the systems themselves are.
As State Farm says, "We know a thing or two because we've seen a thing or two".
That's Farmers, delivered by J.K. Simmons, not State Farm. State Farm is Jake, in his khakis.
They're garbage when it comes to their mobile app and some of the controls on the infotainment system.
> sometimes the HUD doesn't work(it's 50/50 if it will turn on).
You should definitely reach out to Hertz and ask for a car swap. Sounds like there's a bad connection between the display and the IHU. Both screens are operated by the same system, so it's unlikely to be a software failure.
Move over, Microsoft, I think I've found an update policy I hate even more...
As that was during a client emergency, I had a very happy client that day.
[0]: https://www.seattletimes.com/business/boeing-aerospace/faa-o...
All the controls related to driving are available. You can use turn signals, wipers, change lights, honk, shift gears, etc.
But you are correct that you don't see your speed during the reboot.
Also even on older Teslas lights are controlled exclusively via touchscreen.
Even the new stalkless cars have gear selectors.
And of course preventing people from modifying and controlling hardware that they own, having paid 6 figures for (in the case of the Polestar 3 anyway). But that's table stakes for embedded systems in this day and age. Security for me, not for thee.
> Maybe they've got a test fleet, but it accepts code signed with the test build key.
Polestar solves this by only delivering signed updates to their vehicles. The vehicle headunit will refuse to flash a partition that isn't signed by the private key held by Polestar. Pulls double duty to prevent someone from flashing a malicious update, as well as corruption detection.
> Maybe they've got a watchdog timer, but it doesn't get configured until later in the boot process.
Based on what the Rivian reports are showing (Speedometer, cameras, safety systems are working), they likely are running their infotainment as a "virtual machine" within their systems. Again, something that Polestar does.
Implementation of a watchdog with a "sub-system" like this is relatively braindead simple.
> Maybe they've got A/B boot partitions, but trouble counting their boot attempts - maybe they don't have any writable storage that early in the boot process.
Generally, A/B partitioning is part of the bootloader, the first program that executes after the reset (on many modern processors) pin is released. This also leads to reboot counters and such being stored as part of the NVRAM that is available at boot.
Opinion: Maybe I'm biased, but maybe if you can't develop something yourself, there's reason for you to get an off the shelf option that handles a lot of these things.
Disclaimer: Former Googler, Worked closely with Automotive.