Opportunistic software updates during select operational modes
Disclosed embodiments relate to opportunistically updating Electronic Control Unit (ECU) software in a vehicle. Operations may include receiving, at a controller in a vehicle, a wireless transmission indicating a need to update software running on at least one ECU in the vehicle; monitoring an operational status of the vehicle to determine whether the vehicle is in a first mode of operation in which an ECU software update is prohibited; delaying the ECU software update when the operational status is prohibited; continuing to monitor the operational status of the vehicle to determine whether the vehicle is in a second mode of operation in which the ECU software update is permitted; and enabling updating of the at least one ECU with the delayed ECU software update when it is determined that the vehicle is in the second mode of operations.
1. A non-transitory computer readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for opportunistically updating controller software, the operations comprising:
receiving, at a controller, a prompt to change current software on the controller, the controller controlling at least a portion of a device;
determining at a first time whether the device is in a first mode of operation;
delaying a controller software change when the device is in the first mode of operation;
determining at a second time whether the device is in a second mode of operation;
determining the device to be in the second mode of operation;
accessing the delayed controller software change based on determining that the device is in the second mode of operation, wherein:
the delayed controller software change is maintained on a remote server or on the device when the device is in the first mode of operation; and
the delayed controller software change comprises an executable delta file having at least one position-independent executable code segment; and
installing the delayed controller software change on the controller when the device is in the second mode of operation, wherein installing the delayed controller software change comprises linking execution of the at least one position-independent executable code segment to execution of the current software.
2. The non-transitory computer readable medium of claim 1 , wherein, after installing the delayed controller software, the controller is configured to update a program counter when executing the delayed controller software.
3. The non-transitory computer readable medium of claim 2 , wherein the delta file is multidimensional and comprises at least one of: a binary data dimension, a source attribute dimension, or a map file dimension.
4. The non-transitory computer readable medium of claim 1 , the operations further comprising monitoring, according to a preestablished interval, an operational status of the device.
5. The non-transitory computer readable medium of claim 1 , wherein delaying the controller software change comprises storing the controller software change on the controller.
6. The non-transitory computer readable medium of claim 1 , wherein delaying the controller software change comprises discarding the controller software change from the controller.
7. The non-transitory computer readable medium of claim 1 , the operations further comprising:
sending a message to the remote server when the device is in the second mode of operation;
receiving the delayed controller software change in reply to the message; and
installing the delayed controller software change on the controller when the device is in the second mode of operation.
8. The non-transitory computer readable medium of claim 1 , wherein:
the delayed controller software change is configured to change the software on the controller from a first version of controller software to a second version of controller software; and
installing the delayed controller software change comprises configuring the first version of controller software to become non-executable.
9. The non-transitory computer readable medium of claim 8 , wherein configuring the first version of controller software to become non-executable comprises updating memory addresses in a memory component of the device corresponding to one or more functional units managed by a virtual file system (VFS).
10. The non-transitory computer readable medium of claim 1 , wherein the second mode of operation comprises one of a plurality of predetermined safe operating conditions.
11. The non-transitory computer readable medium of claim 1 , wherein the second mode of operation comprises a power-down status of the device.
12. The non-transitory computer readable medium of claim 1 , wherein the prompt is received in response to activity data related to the controller deviating from expected controller activity data.
13. The non-transitory computer readable medium of claim 1 , wherein the second mode of operation comprises a period of wireless communications strength above a threshold of strength.
14. The non-transitory computer readable medium of claim 1 , wherein the second mode of operation comprises a preselected environmental condition of the device.
15. The non-transitory computer readable medium of claim 1 , wherein the second mode of operation comprises a network connection with an error rate below a threshold.
16. The non-transitory computer readable medium of claim 1 , wherein the operations further comprise identifying a wireless transmission indicating the need to update the software based on a determination of whether the update is with or without an override status.
17. The non-transitory computer readable medium of claim 16 , wherein the instructions further comprise:
updating the controller software regardless of whether the device is in the first mode of operation when the update is received with the override status.
18. A computer-implemented method for opportunistically updating controller software, the method comprising:
receiving, at a controller, a prompt to change software on the controller, the controller controlling at least a portion of a device;
determining whether the device is in a first mode of operation;
delaying a controller software change when the device is in the first mode of operation;
determining at a second time whether the device is in a second mode of operation;
determining the device to be in the second mode of operation;
accessing the delayed controller software change when it is determined that the device is in the second mode of operation, wherein:
the delayed controller software change is maintained on a remote server or on the device when the device is in the first mode of operation; and
the delayed controller software change comprises an executable delta file having at least one position-independent executable code segment; and
installing the delayed controller software change on the controller when the device is in the second mode of operation, wherein installing the delayed controller software change comprises linking execution of the at least one position-independent executable code segment to execution of the current software.
19. The method of claim 18 , wherein, after installing the delayed controller software, the controller is configured to update a program counter when executing the delayed controller software.
20. The method of claim 19 , wherein the delta file is multidimensional and comprises at least one of: a binary data dimension, a source attribute dimension, or a map file dimension.
21. The method of claim 18 , wherein:
the delayed controller software change is configured to change the software on the controller from a first version of controller software to a second version of controller software; and
installing the delayed controller software change comprises configuring the first version of controller software to become non-executable.