Vehicle ECU Software Update Swap Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Modern vehicles face efficiency issues and security flaws due to improper firmware updates, which can lead to malfunctioning or unauthorized vehicle operation, as existing update procedures do not effectively detect errors until the next key-on cycle.
Innovation Solution
A two-stage software update process where the update is first downloaded to an inactive storage and then swapped to active storage during an ECU reset, with verification at key-off to ensure proper functioning before shutdown, allowing for automatic rollback if issues arise.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If software updates are applied manually at the dealership while the vehicle is inoperable, then software updates can be performed, but vehicle availability and operational efficiency are reduced
Solution Approach 1:
The system downloads and installs software updates to inactive storage in advance during normal vehicle operation, preparing the update before it is needed. This allows the swap to active storage to occur quickly during key-off events without requiring extended vehicle downtime at the dealership.
Solution Approach 2:
The storage system is divided into multiple partitions including active storage and inactive storage. This segmentation allows the update process to occur in the inactive partition while the active partition continues to support vehicle operation, enabling updates without complete system shutdown.
2Productivity
If software updates are applied without verification, then update speed is improved, but reliability and detection of improper updates are reduced
Solution Approach 1:
The system implements a verification process where the ECU attempts to reboot using the newly installed software from inactive storage before finalizing the swap to active storage. This feedback mechanism confirms whether the update was applied correctly and the software functions properly, providing reliability verification without significantly delaying the update process.
Solution Approach 2:
The verification through reboot attempt is performed as a preliminary check before committing to the final swap. This preliminary action ensures update reliability is confirmed before the inactive storage becomes active, preventing improper updates from taking effect.
3Reliability
If the ECU reboots using new software from inactive storage at key-off, then errors can be detected before next key-on, but the shutdown process is extended
Solution Approach 1:
The ECU performs self-verification by attempting to reboot using the new software during the key-off event. This self-service approach allows the system to verify update integrity autonomously without requiring external testing or extended dealership involvement, detecting errors efficiently within the normal shutdown window.
Data Source
AI summary
A system includes a first storage, a second storage, and a vehicle electronic control unit (ECU). The ECU is programmed to download a software update received from a server to the first storage, at keyoff, attempt a reboot of the ECU before vehicle shutdown, and confirm the first storage as being active for booting instead of the second storage, responsive to the vehicle ECU successfully booting to the first storage.