3 ms·
Tesla's doing OTA pretty robustly. Maybe there just isn't enough space in a door lock to do it properly. If a system can go back the last working version if t
by stretchwithme 9y ago
Tesla's doing OTA pretty robustly. Maybe there just isn't enough space in a door lock to do it properly.
If a system can go back the last working version if the latest fails to work, even a bad version shouldn't brick the device.
- com2kid 9y ago> Maybe there just isn't enough space in a door lock to do it properly. Doubtful, dead simple OTA with recovery requires a 2x allocation of space. $2 or so of parts covers it for 99% of embedded scenarios, and if the product doesn't have enough storage to do a recovery OTA then the product wasn't spec'd properly. More clever but just as robust systems can get away with less (however much a recovery partition takes up, if doing WiFi that can be a lot). > If a system can go back the last working version if the latest fails to work, even a bad version shouldn't brick the device. Knowing when the current version has failed can be hard. If the system comes up 99% of the way but one driver fails, that can be hard to determine programmatically. Obviously the manufacturer here didn't have that robust of tests running at startup to determine if there was a need to rollback. To be fair, most software updates don't have that level of rigor. Pre-release testing catches the majority of issues, as it should. Now days, phased rollouts to opt-in beta testers is standard to try and catch any remaining issues.