Method for starting up a computer system for a vehicle using a multi-level (multi-stage) boot manager with multiple versions
The boot manager is divided into two parts to facilitate secure and uninterrupted updates, addressing the challenge of maintaining operation during updates in vehicle computer systems.
Patent Information
- Application Number
- PCT/EP2026/062190
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-13
- Filing Date
- 2026-04-28
- Publication Date
- 2026-11-19
AI Technical Summary
Existing boot managers in vehicle computer systems face challenges in updating while maintaining security-relevant functions without interrupting the operation or requiring shutdowns.
A method and device that divide the boot manager into two parts, with one part stored in fixed memory and multiple versions of the second part stored at different locations, allowing updates to be performed while the system operates by embedding the current version into the first part and updating the non-current versions without shutting down.
Enables secure and uninterrupted updates of the boot manager, ensuring security-relevant functions are maintained during the process, allowing the system to continue operating without restrictions.
Smart Images

Figure EP2026062190_19112026_PF_FP_ABST
Abstract
Description
[0001] R. 418177
[0002] - 1 -
[0003] Description
[0004] title
[0005] Method and apparatus for starting up a computer system for a vehicle using a boot manager
[0006] State of the art
[0007] The invention relates to a method and a device for starting up a computer system for a vehicle using a boot manager according to the preamble of the independent claims. The present invention also relates to a computer program.
[0008] Over-the-air (OTA) updates are becoming increasingly important in vehicle control units. Likewise, the security requirements for a hardware security module used in this context are rising, which also influences the complexity of a boot manager suitable for the control units.
[0009] Disclosure of the invention
[0010] Against this background, the approach presented here introduces an improved method for starting a computer system for a vehicle using a boot manager, an improved device that uses this method, and finally a corresponding computer program according to the main claims. Advantageous further developments and improvements of the device specified in the independent claim are possible through the measures listed in the dependent claims. R. 418177
[0011] - 2 -
[0012] Advantageously, the presented approach allows for updating the boot manager while simultaneously maintaining, for example, security-relevant functions. This means that the boot manager can be updated without restricting or interrupting the operation of the computer system. Advantageously, the boot manager, which is an entry point into a system, can be updated while remaining robust against shutdowns or restarts.
[0013] A method for booting a computer system for a vehicle using a boot manager is presented. The boot manager comprises a first part stored in a fixed memory location and several versions of a second part stored at different locations in the fixed memory location. The method includes a start step, a read step, an embed step, and an exit step. In the start step, an execution of the first part of the boot manager is initiated. In the read step, a reference is read from non-volatile memory during the execution of the first part, with the reference identifying one of the several versions of the second part as the current version. In the embed step, the current version of the second part is embedded into the execution of the first part when a special function is to be performed.In the exit step, the execution of the first part of the boot manager is terminated with a jump to a bootloader (BL = bootloader) or a main application of the computer system.
[0014] This method is preferably used for vehicles or systems with safety-relevant functions. Such computer systems can be controlled by boot managers. A boot manager can be configured to start the computer system or switch between computer systems. Advantageously, the presented approach allows the boot manager to be updated. The boot manager is divided into two parts, with at least two versions of the second part. Both versions can be identical or, during an update, at least temporarily different. For execution, R. 418177
[0015] - 3 -
[0016] Both parts can be loaded into main memory. The main memory can also be called read-only memory (ROM). Advantageously, data stored in the main memory remains even if the power supply is interrupted. The main memory can be implemented as volatile memory, also known as random-access memory (RAM). The first part can always be executed when the boot manager starts. The second part of the boot manager can preferably contain more complex program code and is only executed optionally when a special function needs to be performed. When the second part is executed, a current version of it can always be run.Different versions of the second part can be stored in different slots of the fixed memory, i.e., at different locations. A reference can specify which version is currently active and therefore, if the second part is to be embedded, is used in an execution of the first part. This reference can be kept up-to-date and stored in non-volatile memory. The reference can be read, for example, when the first part starts or when the second part is to be embedded.
[0017] According to one embodiment, during the embedding step, the current version can be transferred from the hard drive to a predetermined position in main memory known to the first part of the boot manager. Since, in this case, at least one other version of the second part, for example, designated as an outdated version, is not in use, this outdated version can be updated during operation. Advantageously, the entire system can thus be kept up to date. In particular, security-relevant functions can also be maintained during an update of the second part, as the computer system does not need to be shut down for the update.
[0018] According to one embodiment, the method may include a step of updating the version of the second part of the boot manager in the hard drive that is not the current version. R. 418177
[0019] - 4 -
[0020] In one step of the modification process, the reference in non-volatile memory can be changed to the version that was updated in the update step. Advantageously, this allows the data of the second part stored in fixed memory to be updated without interrupting or aborting any function controlled by the program code. Update data provided via a wireless interface, for example, can be used to update the second part.
[0021] Furthermore, the update process can be performed while the vehicle is in operation. Advantageously, all vehicle functions can continue to operate without restriction during the update. This also avoids any restrictions for the driver.
[0022] According to one embodiment, update data for updating the second part of the boot manager can be received via a radio interface of the vehicle during the update step.
[0023] The update data can be received wirelessly, for example from a cloud. This data can then be used to update the second part of the boot manager. This can advantageously avoid a visit to a repair shop.
[0024] This process can be implemented, for example, in software or hardware, or in a hybrid form of software and hardware, for example in a control unit.
[0025] The approach presented here further creates a device designed to carry out, control, and implement the steps of a variant of the method presented here in appropriate facilities. This embodiment of the invention in the form of a device also allows the problem underlying the invention to be solved quickly and efficiently. R. 418177
[0026] - 5 -
[0027] For this purpose, the device may have at least one processing unit for processing signals or data, at least one storage unit for storing signals or data, at least one interface to a sensor or actuator for reading sensor signals from the sensor or for outputting data or control signals to the actuator, and / or at least one communication interface for reading or outputting data embedded in a communication protocol. The processing unit may, for example, be a signal processor, a microcontroller, or the like, and the storage unit may be flash memory or a magnetic storage unit.The communication interface can be configured to read or output data wirelessly and / or via wired connections, whereby a communication interface that can read or output wired data can, for example, read this data electrically or optically from or output it into a corresponding data transmission line.
[0028] In this context, a device can be understood as an electrical device that processes sensor signals and outputs control and / or data signals accordingly. The device may have an interface, which can be implemented in hardware and / or software. In the case of a hardware-based interface, the interfaces can, for example, be part of a so-called system ASIC, which incorporates various functions of the device. However, it is also possible that the interfaces are separate integrated circuits or consist at least partially of discrete components. In the case of a software-based interface, the interfaces can be software modules, which, for example, are present on a microcontroller alongside other software modules.
[0029] The device may include a computing unit for carrying out process steps in one of the aforementioned variants, a fixed memory and a working memory.
[0030] Also advantageous is a computer program product or computer program with program code that is stored on a machine-readable medium or storage medium such as semiconductor memory, hard disk storage, or optical R. 418177
[0031] - 6 -
[0032] memory may be stored and used to carry out, implement and / or control the steps of the method according to one of the embodiments described above, in particular when the program product or program is executed on a computer or device.
[0033] The claimed method and / or device or computer program can be part of a vehicle's component control system. This includes, for example, airbag, drive, steering, and / or brake controls. Alternatively or additionally, the method / device / computer program can also be used in comfort function controls in the vehicle, for example, for seat adjustment, seatbelt tensioning, climate control, and / or the entertainment system. It should be expressly noted, however, that the claimed subject matter can be used not only in the automotive sector, but also, for example, in buildings, infrastructure facilities, aircraft, rail vehicles, electric bicycles, or mobile (end) devices.The claimed item can, for example, be used in all devices and equipment where an update of the operating or functional software is possible, in particular via wireless transmission.
[0034] Examples of the approach presented here are shown in the drawings and explained in more detail in the following description. It shows:
[0035] Fig. 1 shows a schematic representation of an exemplary embodiment of a vehicle;
[0036] Fig. 2 shows a flowchart of an exemplary embodiment of a method for starting up a computer system for a vehicle;
[0037] Fig. 3 shows a block diagram of a device according to an exemplary embodiment;
[0038] Fig. 4 is a schematic representation of a storage device according to an embodiment; R. 418177
[0039] - 7 -
[0040] Fig. 5 shows an embodiment of a method for starting up a computer system for a vehicle using a boot manager; and
[0041] Fig. 6 shows an embodiment of a method for starting up a computer system for a vehicle using a boot manager.
[0042] In the following description of favorable embodiments of the present invention, the same or similar reference numerals are used for the elements shown in the various figures and acting similarly, without repeating these elements.
[0043] Fig. 1 shows a schematic representation of an embodiment of a vehicle 100. According to this embodiment, the vehicle 100 is designed as a passenger car. Alternatively, the vehicle 100 can also be implemented as a commercial vehicle. The vehicle 100 has a computer system 102, which, according to this embodiment, in turn has a device 104. The device 104 has, for example, a processing unit 106, a fixed memory 108, and a working memory 110. The computer system 102 represents, for example, a control unit or part of a control unit of the vehicle 100.
[0044] The computing unit 106 is designed to access data stored in both the fixed memory 108 and the working memory 110.
[0045] For example, the computing unit 106, the fixed storage 108 and the main memory 110 are arranged on a common circuit board.
[0046] The hard disk memory 108 contains data for a boot manager used to start the computer system. The boot manager comprises a first part and a second part, with multiple versions of the second part being provided, for example, two versions. A first version is stored in a first slot 112 and a second version in a second slot 114 of the hard disk memory 108. The two slots 112 and 114 are separately addressable by the arithmetic unit 106. According to this embodiment, the hard disk memory R. 418177
[0047] - 8 -
[0048] 108 is implemented as a so-called read-only memory (ROM), in which stored data remains even when a power supply is interrupted.
[0049] Memory 110 is implemented as volatile memory, such as random-access memory (RAM). Advantageously, data stored in the boot manager's fixed memory 110 can be copied to memory 110 after the boot manager starts and then executed from memory 110 using the processing unit 106.
[0050] The device 104 is designed to control and / or perform a method for starting up the computer system 102, as described, for example, in Figure 2.
[0051] According to one embodiment, update data 120 is used to update the boot manager, for example, by replacing or supplementing existing boot manager data using the update data 120. Optionally, the vehicle 100 has a radio interface 122. In this case, for example, data containing the update data 120 is transmitted from an external unit and received via the vehicle 100's radio interface 122. The update data 120 contained in the transmitted data is then used, for example, by the processing unit 106 to update the boot manager. For this purpose, data stored in the fixed memory 108 is updated using the update data 120. The data updated in this way can subsequently be used when executing the boot manager, for example, when restarting the computer system 102.According to one embodiment, the update data 120 is used to update a version of the second part of the boot manager that is not a current version, i.e., not a currently running or intended-to-run version. R. 418177.
[0052] - 9 -
[0053] According to one embodiment, the device 104 comprises a non-volatile memory device 130 in which a reference 132 is stored that points to the currently active version of the second part. When the second part is to be embedded in an embodiment of the first part, the reference 132 can be used to determine which of the several versions of the second part is to be loaded from the fixed memory 108 into the working memory 110.
[0054] Fig. 2 shows a flowchart of an embodiment of method 200 for starting a computer system for a vehicle using a boot manager, wherein the vehicle corresponds, for example, to the one mentioned in Fig. 1. This means that method 200 can also be used for a vehicle corresponding to the vehicle described in Fig. 1. The boot manager comprises the first part, which is stored in the hard disk memory, and several versions, i.e., at least two versions, of a second part, which are stored at different positions in the hard disk memory.
[0055] Procedure 200 comprises a starting step (202), a reading step (204), an embedding step (206), and an exit step (208). Optionally, procedure 200 also includes an updating step (210) and a modifying step (212).
[0056] In step 202 of the start process, the execution of the first part of the boot manager is initiated. In step 204, the read process, a reference is read from non-volatile memory during the execution of the first part. This reference identifies one of the multiple versions of the second part as the current version. In step 206, the embed process, the current version of the second part is embedded into the execution of the first part if a special function needs to be performed. According to one embodiment, step 206 is skipped if no special function needs to be performed. In step 208, the exit process, the execution of the first part of the boot manager is terminated with a jump to a bootloader or a main application of the computer system. R. 418177
[0057] - 10 -
[0058] According to this embodiment, in step 206 of the embedding process, the current version, identified by the reference, is transferred from the hard drive to a predetermined position in working memory known to the first part of the boot manager. This predetermined position can be set independently of the selected version of the second part.
[0059] The procedure 200 optionally includes step 210, which updates the version of the second part of the boot manager in the persistent memory that is not the current version—that is, the version not currently marked as the current version by the reference. To ensure that the updated version can be used as the new current version after the update, step 212, the modification, changes the reference in the persistent memory to the version that was updated in step 210. For example, during the update, old data is completely or partially replaced with new data. After updating one version, the other versions of the second part can then be updated until all versions of the second part are up to date.After the update is complete, all versions of the second part may be identical, but stored in different locations on the hard drive.
[0060] Step 210 of the update process is performed, for example, during ferry operations. According to this example, update data for the second part of the boot manager can be received via a radio interface of the vehicle.
[0061] Fig. 3 shows a block diagram of a device 104 according to an embodiment, as already described, for example, in Fig. 1. The device 104 is configured to control and / or execute a process, as described, for example, in Fig. 2. The device 104, and in particular the computing unit 106, comprises a start unit 300, a read unit 302, an embed unit 304, and a termination unit 306, as well as optionally an update unit 308. 418177
[0062] - 11 -
[0063] a change unit 310, which can be operated, for example, by program data from the boot manager.
[0064] The start unit 300 is configured to initiate the execution of the first part of the boot manager. The read unit 302 is configured to retrieve a reference from non-volatile memory during the execution of the first part, where the reference identifies one of the multiple versions of the second part as the current version. The embed unit 304 embeds the current version of the second part into the execution of the first part when a special function needs to be performed, and the terminate unit 306 terminates the execution of the first part of the boot manager by jumping to a bootloader or a main application of the computer system. The update unit 308 is configured to update any of the multiple versions of the second part of the boot manager that is not the current version.The change unit 310 is designed to change the reference in the non-volatile memory to the one of the multiple versions that was previously updated by the update unit 308.
[0065] Fig. 4 shows a schematic representation of a storage device 400, which, according to this embodiment, comprises the fixed memory 108 and the working memory 110 as described or mentioned in at least one of Figures 1 to 3. According to this embodiment, the fixed memory 108 has the first slot 112 and the second slot 114.
[0066] For example, the first slot is also referred to as ROM L0 and the second slot as ROM L1, thus representing the 400 fixed memory as a two-level memory.
[0067] According to this embodiment, the first slot 112 and the second slot 114 are each subdivided into a plurality of blocks containing and / or representing different code segments. More precisely, according to this embodiment, the first slot 112 contains a first part of the boot manager, and the second slot 114 contains a second part.
[0068] Bootmanagers.R. 418177
[0069] - 12 -
[0070] For example, block 402 represents a start vector "StartVec". Block 404 represents a so-called common-use library "CommonUse LI B" and an independent code "IndependentCode". Furthermore, the first part of the boot manager comprises block 406 and block 408, which represents a second part of the "CommonUse LIB". According to this embodiment, program data from the first part of the boot manager is provided in block 410 for the execution of the second part of the boot manager, after which the jump from the first slot 112 to the second slot 114, as described in Fig. 3, takes place.
[0071] Following block 412, block 414 represents data relating to a ROM interface, which can be used to provide RAM functions. Block 416 provides data for RAM initialization, which is transferred to main memory 110. This block 416, for example, comprises 32 KB.
[0072] In RAM 110, the first 64 KB of block 418 are unused. These are available, for example, for an executable "BL part." Block 420, for instance, is an active part of RAM 110, used for L1 and a stack (15+11). According to this example, the data from block 416 is transferred to block 422, which then receives the executable code.
[0073] According to this embodiment, a final block 424, and thus the last 5KB of the main memory 110, is provided for a so-called BSS and data from the first slot 112.
[0074] In other words, the described approach provides a way to update a boot manager. The boot manager is an entry point into a system. According to this example, the boot manager is updated in a failsafe manner and compiled using position-variant methods. Furthermore, ROM components can be repaired. R. 418177
[0075] - 13 -
[0076] For example, the second slot 114, which can also be called the second level, contains the more complex code, and this failsafe can be updated using a dual-slot procedure. Dual-slot here means that one of the slots 112 or 114 always contains the old, functional code, and the other slot is only activated once this code is complete. The content of this slot is position-variable. This means that a second-level BM (BM = Boot Manager) can be located in either slot in the program flash. The content of this second-level BM can be represented in a flash container, through which the data for the logical block of the second-level BM is transferred to the device. This data can be transferred to the "free" slot depending on the situation. This means that the ROM position can vary. The second-level BM is intended to run primarily in RAM, specifically in memory slot 110.This is done, for example, with the exception of one interface function that operates independently of the code position and resides at a fixed location in the L2 BM. This also enables it to make corrections to the system. These corrections relate, for example, to repairing ROM portions. If, for instance, a fundamental component of the system is lost during a flash operation, this part of the L2 BM must be executed from RAM because no code from a physical bank can be executed while the physical bank is being modified. Manipulation of a fixed memory in a typical embedded microcontroller, a so-called embedded uC, can usually only be performed from RAM, provided a physical bank is present.
[0077] According to this embodiment, a second-level BM position variant is dynamically linked and embedded by the first-level BM. This means that the first-level BM receives enough information to dynamically link and directly use the "correct" second-level BM.
[0078] This allows the embedding of the second part of the boot manager to be carried out safely. R. 418177
[0079] - 14 -
[0080] Thus, the 2nd level BM failsafe becomes updateable without a so-called Trojan implementation as a "pseudo-application" that only serves to replace the boot manager.
[0081] According to this embodiment, the first-level BM now only loads the basic configuration to know the location of the application and the currently active second-level BM. RAM executables are dispatched from an interface in the second-level BM and loaded into RAM. Furthermore, according to this embodiment, the interfaces are provided to the first-level BM so that it can use the functions.
[0082] In summary, this means that the basic interface of the 2nd level BM can be called from either position because it only contains a trivial function that handles the dispatching, i.e., the execution.
[0083] This function also receives the offset, or actual starting position, of the interface so that it is copied into RAM from the correct location and the RAM function code is positioned correctly. Only this function knows where the functions required by the 1st level boot manager (BM) are located, because they belong to the 2nd level BM, and provides them in an interface. The RAM areas must be clearly separated to prevent them from interfering with each other. Because a part of the boot manager (2nd level) can now be executed in RAM, this part is also able to flash vital system components from a mirror and thus repair them. This is particularly important because a security component can repair a power interruption during the flashing process or activation by the boot manager, preventing the system from booting with a security-relevant limitation.
[0084] Fig. 5 shows an embodiment of a method 200 for starting up a computer system for a vehicle using a boot manager, which is similar, for example, to the method described in Fig. 2. The boot manager comprises a first part 502, which is stored in the fixed memory 108. R. 418177
[0085] - 15 -
[0086] is, and several versions 504, 506 of a second part 508, which are stored in different positions in the fixed memory 108.
[0087] Block 510 therefore represents the starting of the first part of the boot manager in the fixed memory 108. Block 512 causes a selection of a current version of the second part 508 of the boot manager. This means that, according to this embodiment, version 504 or version 506 is selected, which corresponds to the selection step described in Fig. 2. For this purpose, a reference from the non-volatile memory 108 is read in block 514 during the execution of the first part 502, the reference identifying one of the several versions 504, 506 of the second part 508 as a current version. This is done analogously to the read step described in Fig. 2. Block 516 represents the embedding of the current version of the second part 508 into the execution of the first part 502 when a decision is made in block 518 that a special function is to be performed.Block 520, which corresponds to the exit step, terminates the first part 502 of the boot manager with a jump to a bootloader or a main application of the computer system, as also already described in Fig. 2, when it is decided in block 518 that no special function is to be performed.
[0088] Fig. 6 shows an embodiment of a method 200 for starting up a computer system for a vehicle using a boot manager, similar, for example, to the method described in Fig. 2. The boot manager comprises a first part 502, which is stored in the hard disk memory, and several versions of a second part 508, which are stored at different locations in the hard disk memory. According to this embodiment, the second part 508 contains the more complex program code.
[0089] In block 510, the first part 502 of the boot manager is started. Following this, in block 518, a query is made as to whether a special function should be executed. If the special function is to be executed, reference is made to the second part 508. If no special function is to be executed, a normal start of a main application is anticipated, after which a query is made in block 600 as to whether any function is required. 418177
[0090] - 16 -
[0091] If no function needs to be terminated, the process jumps to the main application, which corresponds to block 520. If the check in block 600 indicates that any function needs to be terminated, a check is performed in block 602 to determine if the bootloader is active.
[0092] Block 520, which corresponds to the termination step, thus ends the first part 502 of the boot manager, according to this embodiment, with a jump to the main application of the computer system, as already described in Fig. 2, after the query in block 600. Block 520 is subdivided into a decision block 604, in which the starting of a bootloader is queried. If the bootloader is not to be started, the main application is started in a subblock 606 of block 520. If the bootloader is to be started, reference is made to the second part 508.
[0093] Block 516 corresponds, for example, to the embedding step described in Fig. 2. If, for instance, the query in block 518 determines that the special function is to be executed, the corresponding data is embedded into the second part 508 using block 516. For example, a query is performed in block 608 to check if "HSM in Boot". If the answer is "no", a jump to block 600 follows. If the answer is "yes", a recovery operation (Recover HSM from Mirror) is performed in block 610. According to this embodiment, a query is then performed in block 612 to check whether the recovery operation in block 610 was successful. If this is affirmative, a restart is performed using block 614. If, on the other hand, this is negative, the bootloader is started in block 616 to restore the current state.
Claims
R. 418177 - 17 - Claims 1. Method (200) for starting up a computer system (102) for a vehicle (100) using a boot manager, wherein the boot manager comprises a first part (502) stored in a solid memory (108) and several versions (504, 506) of a second part (508) stored at different locations in the solid memory (108), wherein the method (200) comprises the following steps: Starting (202) an execution of the first part (502) of the boot manager; Reading (204) a reference (132) from a non-volatile memory (130) during the execution of the first part (502), wherein the reference (132) identifies one of the multiple versions of the second part (508) as a current version; Embedding (206) the current version of the second part (508) into the execution of the first part (502) when a special function is to be performed; and Terminating (208) the execution of the first part (502) of the boot manager with a jump to a bootloader or main application of the computer system (102).
2. Method (200) according to claim 1, wherein in step (206) of embedding, the current version is transferred from the fixed memory (108) to a predetermined position in a working memory (110) known to the first part (502) of the boot manager. R. 418177 - 18 - 3. Method according to claim 1, comprising a step (210) of updating that of the multiple versions of the second part (508) of the boot manager which is not the current version and a step (212) of changing the reference (132) in the non-volatile memory to that of the multiple versions which was updated in step (210) of updating.
4. Method (200) according to claim 3, wherein the step (210) of updating is carried out during a ferry operation of the vehicle (100).
5. Method (200) according to one of claims 3 to 4, wherein in the step (210) of updating update data (120) for updating the second part (508) of the boot manager are received via a radio interface (122) of the vehicle (100).
6. Device (104) configured to perform and / or control the steps of the method (200) according to any of the preceding claims in corresponding units (300, 302, 304, 306, 308, 310).
7. Computer program configured to execute and / or control the steps (202, 204, 206, 208, 210, 212) of the method (200) according to any one of claims 1 to 5.
8. Machine-readable storage medium on which the computer program according to claim 7 is stored.
