TBOX Bootloader Segmentation for Reliable Startup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The risk of a vehicle-mounted Tbox failing to start up due to abnormal interruptions such as power failure or device restarting during the BOOTLOADER upgrading process, which is not addressed by existing solutions.
Innovation Solution
The introduction of a new software architecture that splits the conventional BOOTLOADER+APP into BOOTLOADER1+BOOTLOADER2+APP, where BOOTLOADER1 only stores power-on initialization code, and BOOTLOADER2 stores control logic and diagnostic protocol stack, allowing version upgrading to start from BOOTLOADER2 and ensuring that BOOTLOADER1 remains unaffected by abnormal interruptions, enabling self-repair and reliable startup.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the conventional BOOTLOADER+APP architecture is used, then the device can be upgraded via FOTA, but the device may fail to start up if abnormal interruption occurs during BOOTLOADER upgrading
Solution Approach 1:
The patent divides the BOOTLOADER into two separate modules: BOOTLOADER1 (containing only power-on initialization code) and BOOTLOADER2 (containing control logic and diagnostic protocol stack). This segmentation ensures that upgrading BOOTLOADER2 does not affect BOOTLOADER1, so even if abnormal interruption occurs during BOOTLOADER2 upgrading, the device can still start up normally via BOOTLOADER1, thus resolving the contradiction between upgrading capability and startup reliability.
2Reliability
If the BOOTLOADER is split into BOOTLOADER1 and BOOTLOADER2, then startup reliability is improved, but the device complexity increases
Solution Approach 1:
The BOOTLOADER is segmented into two functional modules with distinct responsibilities. BOOTLOADER1 handles only power-on initialization, while BOOTLOADER2 handles control logic and diagnostics. This segmentation improves reliability by isolating upgrade risks to BOOTLOADER2 only, while the modular design actually simplifies maintenance and upgrading operations despite increasing structural complexity.
3Adaptability or versatility
If full-version upgrading is performed on the MCU, then all components are updated, but the device fails to start up if abnormal termination occurs during upgrading
Solution Approach 1:
The patent segments the upgrading process into two independent phases: first upgrading BOOTLOADER2 (control logic and diagnostics), then upgrading APP. This segmented approach allows the system to maintain a functional state during upgrading, and if abnormal termination occurs, the device can still start up using the unupgraded BOOTLOADER1 and existing APP, thus resolving the contradiction between comprehensive upgrading and startup reliability.
Solution Approach 2:
The patent performs preliminary action by first upgrading BOOTLOADER2 before upgrading APP. This sequence ensures that even if the APP upgrade fails or is interrupted, the device can still start up using the upgraded BOOTLOADER2 and existing APP, while the BOOTLOADER1 remains as a backup for critical power-on initialization.
Data Source
Figure 1~2
Figure 3~4
Figure 5~7
AI summary
A method, apparatus, device, and a storage medium for upgrading a vehicle-mounted Tbox, which relate to the technical field of vehicle-mounted Tbox. The method comprises: when using a BOOTLOADER1 module that is used to store a power-on initial code for power-on startup, a vehicle-mounted Tbox determines whether version upgrading needs to be carried out (S401); and when it is determined that version upgrading needs to be carried out, the vehicle-mounted Tbox sequentially carries out version upgrading on a BOOTLOADER2 module for storing control logic and a diagnostic protocol stack code and app module (S402).