WO2009103728A1

WO2009103728A1 - Method and device for storing information data

Info

Publication number: WO2009103728A1
Application number: PCT/EP2009/051902
Authority: WO
Inventors: Wanli Sheng; Uwe Werner; Frank Boehland; Jens Liebehenschel
Original assignee: Robert Bosch Gmbh
Priority date: 2008-02-22
Filing date: 2009-02-18
Publication date: 2009-08-27
Also published as: DE102008010556A1

Abstract

The invention relates to a method for storing information data (106) in a memory (104) having at least two memory areas. According to said method, the information data (106) and a first section of the operating program are written into one of the at least two memory areas of the memory (104) and the information data (106) and a second section of the operating program are written into the other of the at least two memory areas of the memory (104).

Description

description

Title Method and device for storing information data

The invention relates to a method for storing information data according to the preamble of claim 1, an apparatus for carrying out this method, a computer program and a computer program product.

State of the art

Many automotive ECUs are updateable, which means that a new software version can be installed. This process is also referred to as flashing because the code of a new software version is stored in the flash ROM (Read OnIy Memory). Usually there are two separate, executable programs in the flash memory, namely the bootloader and the driving software.

Usually it is required or due to the development that data has to be written in the bootloader, which can also be read by the driving software and vice versa. In addition, this data may be relevant to a return analysis. This functionality has hitherto been realized by writing this data into a data memory, for example in the form of an EEPROM or flash ROM (data flash) by the boot loader. With the advent of Flash technology to store persistent, non-volatile data, file management systems have become necessary, with the data always being stored elsewhere. As a result, more complex management algorithms for data have become necessary in the software. In addition, some processors have experienced timing issues when using Flash to store data.

Against this background, the present invention provides a method for storing information data, furthermore a device which uses this method and finally a corresponding computer program and a computer program product according to the independent patent claims. Advantageous embodiments emerge from the respective subclaims and the following description.

Advantages of the invention

The present invention is based on the finding that information data can be stored as part of an operating program. As a result, required information data can be reliably stored and evaluated. Using the method in conjunction with a bootloader obviates the need for the bootloader to write non-volatile data to a data store as mentioned above. The present invention provides a method for storing information data in a memory having at least two memory areas, which is characterized in that the information data and a first portion of an operating program in one of the at least two memory areas of the memory and the information data and a second portion of the operating program another of the at least two memory areas of the memory are written.

According to one embodiment, already existing information data can be checked in one of the at least two memory areas before the further of the at least two memory areas is described. As a result, it can be ensured that no loss of the information data occurs even in the event of a failed write attempt.

Furthermore, an arrangement of the information data in the at least two memory areas may be predetermined. This makes it possible to control the writing of the information data and the operating program into the memory.

The operating program may have information about the arrangement of the information data in the at least two memory areas. This makes it easier for the operating program to access the information data.

According to one embodiment, the operating program may have gaps into which the information data may be written. Thus, appropriate sections can be predefined in the operating program to which the information data can be integrated. - A -

The method can have the following steps:

Clearing a first memory area of the memory;

Writing the information data in the first memory area;

Writing the first section of the operating program into the first memory area;

Clearing a second memory area of the memory;

Writing the information data in the second memory area; and

Writing the second section of the operating program to the second memory area.

This procedure is suitable for the case that the information data in the second memory area are intact.

Alternatively, the method may include the following steps:

Clearing a second memory area of the memory;

Writing the information data in the second memory area;

Clearing a first memory area of the memory;

Writing the information data in the first memory area; Writing the second section of the operating program to the second memory area; and

Writing the first section of the operating program to the first memory area.

This procedure is suitable, for example, in the event that the information data in the second memory area are not intact.

Furthermore, a third memory area may have previous information data. This allows the memory to have both new and previous informational data.

At least the information data written in one of the at least two memory areas can be compared with further information data. Thus, for example, conclusions can be drawn on failed attempts to write.

The method can be executed by a start program of a control unit and the operating program can be operating software of the control unit and the information data can be non-volatile data. This avoids that the writing of non-volatile data in the bootloader of a controller leads to difficulties with the architecture of the controller or problems with the system behavior.

The memory may be a flash memory and the memory areas may be sectors of the flash memory. A device according to the invention performs all the steps of the method according to the invention.

The computer program with program code means according to the invention is designed to perform all the steps of the method according to the invention when this computer program is carried out on a computer or a corresponding computing unit, in particular a device according to the invention.

The computer program product according to the invention with program code means which are stored on a computer-readable data carrier is provided for carrying out the method according to the invention when this computer program is carried out on a computer or a corresponding arithmetic unit, in particular a device according to the invention.

Further advantages and embodiments of the invention will become apparent from the description and the accompanying drawings.

It is understood that the features mentioned above and those yet to be explained not only in the particular combination given, but also in other combinations or alone, without departing from the scope of the present invention.

The invention is illustrated schematically by means of exemplary embodiments in the drawings and will be described in detail below with reference to the drawings. figure description

Figure 1 shows a schematic representation of an embodiment of the device according to the invention;

Figure 2 shows a schematic representation of a memory according to an embodiment of the invention;

FIG. 3 shows a schematic representation of memory areas according to an embodiment of the invention; and

FIG. 4 shows a schematic representation of an embodiment of the method according to the invention.

Fig. 1 shows a device with a writing device 102 and a memory 104 according to an embodiment of the present invention. The writing device is configured to write information data 106 into the memory 104. Further, the writing device 102 is configured to write an operating program to the memory 104. The memory 104 is configured to store the information data 106 and the operating program. The storage 104 has at least two storage areas. The information data 106 is stored in each of the at least two memory areas of the memory 104. The operating program can be divided into several sections, which can be distributed to the at least two memory areas of the memory.

The memory 104 may be a flash memory. The flash memory is divided into a plurality of areas or sectors. A sector generally has a size of a few hundred bytes to a few kilobytes in an automotive memory. Each sector has a plurality of memory cells. Each memory cell in a sector can be described once. Before the next writing, the entire sector must be deleted.

The device may be part of an automotive control device, for example. In this case, the operating program may be a driving software which is written into the memory 104, for example, by a boot program in the form of a bootloaf. The writing device 102 may be a processor configured to execute the bootloader.

The boot loader may have the task of deciding after a system start whether the driving software should be started or replaced and if necessary, replace the driving software. The bootloader can either be executed directly after the system start or can be called up by the driving software. It may also be possible to replace the bootloader with a new software version. Since the boot loader is generally not to be replaced, it should be designed simply so that it contains as possible no errors.

The driving software can fulfill a functionality required by the control unit.

The information data 106 may be nonvolatile data. Such data may include, for example, information about the identification of a workshop and of a workshop tester, eg a diagnostic device, a date and type of update, a software version or software versions and a version of data statuses as well as a number of all, unsuccessful or successful software updates.

FIG. 2 shows a schematic representation of a flash memory 104. According to this embodiment, the memory 104 has eight sectors. Of the sectors, the first four and the seventh sector are provided with reference numerals 206a, 206b, 206c, 206d, 206g.

The sectors 206a, 206b, 206c, 206d, 206g are indicated by vertical lines. In the first sector 206a, the boot loader may be arranged. When a new driving software is stored, it is generally stored in several sectors of the flash memory 104. For example, the driving software can be stored in another five sectors 206c, 206d ... 206g. For this purpose, the driving software can be subdivided into individual sections driving SW 1,..., Driving SW 5. For example, the driving SW 1 section in the third sector 206 c and the driving SW 5 section may be stored in the seventh sector 206 g of the memory 104.

FIG. 3 shows the sectors 206c, 206d of the memory 104 shown in FIG. 2. In both sectors 206c, 206d, the information data 106 is stored. The first section of the driving software driving SW 1 314 is stored in the sector 206 c. The second section of the driving software driving SW 2 316 is stored in the sector 206d. According to this exemplary embodiment, the information data 106 are respectively arranged at the beginning of a sector 206c, 206d and the sections 312, 314 of the driving software fill the sectors 206c, 206d on. It should be noted that the data 106 may also be at the end of the sectors 206c and / or 206d. In addition, other sectors may be inserted before and / or in between.

The inventive method for storing information data in a memory based on the storage of the data by the boot loader as part of the driving software and a subsequent comparison of this data by the driving software with their previously stored data.

According to one embodiment, there are no intended unused locations in the driving software. In this case, the bootloader does not use the full sector size to store the driving software 314, 316. In the unused areas, the data 106 are stored. These places of information storage should be known to the driving software, if they should access it. Furthermore, the compilation, the linking and the integration should ensure that the driving software works with these "gaps".

According to an alternative embodiment, gaps may be present in the driving software known to the boot loader. The gaps can be fixed size. Corresponding data are entered in the gaps as part of the software update.

In both embodiments, the boot loader places certain data 106 at previously known locations along with the driving software 314, 316 into at least two sectors 206c, 206d of the flash 104, as illustrated in FIG. 3 for the two sectors 206c, 206d. In Fig. 2, the embodiment is shown, in which there are no gaps in the driving software. In the other embodiment, in which the driving software has gaps, the data 106 can be stored at one or more locations in the driving software. Of course, the data 106 may also be located at other locations, such as at the end of the sectors 206c, 206d.

The method according to the invention is a secure method in which data 106 are stored in two sectors 206c, 206d together with the driving software 314, 316. For the reliability of the method according to the invention, the order of the writing operations is important, in which in particular the information data 106 are written into the memory 104. An important scenario to consider is several consecutive power outages. These must not result in information being lost, such as the number of unsuccessful update attempts that may be included in data 106.

4 shows a flow chart with steps of the method according to the invention according to an exemplary embodiment of the present invention. A first method step 452 may comprise the instruction "delete sector 1", which may be the sector 206c shown in Fig. 3. A second method step 454 may comprise the instruction "write data in sector 1". A third method step 456 may include the instruction "write driving software in sector 1." A fourth method step 458 may include the instruction "delete sector 2". It can be about act the sector 206d shown in Fig. 3. A fifth method step 460 may include the instruction "write data in sector 2." A sixth method step 462 may include the instruction "write driving software in sector 2".

This sequence of method steps 452, 454, 456, 458, 460, 462 should only be used if the data 106 in sector 2 are intact. This can be checked for example by a checksum. If the data 106 in sector 2 are not intact, the sequence of method steps 452, 454, 456, 458, 460, 462 should be changed.

For example, in this case, the step "Delete sector 2", then the step "Write data in sector 2", then the step "Delete sector 1", then the step "Write data in sector 1", then the step "Write Driving software in sector 1 "and finally the step" Write driving software in sector 2 "are executed. In this order, the new data 106 are already present on the storage medium 104 after the second step. They can be determined by a control unit software or by a readout of the memory 104, for example by a feedback analysis.

According to further embodiments, other sequences of the method steps are possible. In particular, if several sectors are required for storing the code of the driving software. When multiple sectors are needed, the data 106 may be stored in other than the first two sectors. According to a further embodiment, sequences of the method steps are defined which leave the new and the previous data 106 simultaneously on the flash memory 104.

The approach according to the invention includes, in addition to the layout on the flash memory, also a comparison of the data with existing persistent data by the driving software. After successfully flashing the driving software, it can draw conclusions by comparing the data written by the bootloader during the update and the persistent data in the data flash. For example, data transmitted by the bootloader, such as the number of unsuccessful update attempts, can be processed and transferred to the area in the data flash containing the persistent data.

In addition to the advantages already described, the inventive method has a number of other advantages. In particular, the bootloader and the software architecture can be simpler since the bootloader does not have to store any persistent data in the data flash. Timing issues that can arise from using Flash technology for data storage do not exist in the boot loader. In particular, there is no waiting for the state change. Furthermore, it is not necessary for the boot loader to contain code for this functionality. Thus, less memory can be used. The protocols of the ECUs with the testers can remain unchanged. The code can be transmitted as a data stream from "front to back" from the tester to the ECU. The described embodiments are chosen only by way of example and can be combined with each other. In particular, the method steps described can also be carried out in sequences other than those described, provided that secure storage of the information data remains ensured. In addition, any memory can be used which are suitable for the application for which the inventive method is used.

Claims

claims

A method of storing information data (106) in a memory (104) having at least two memory areas

(206c, 206d), characterized in that

the information data (106) and a first portion (314) of an operating program are written into one of the at least two memory areas of the memory and the information data (106) and a second portion (316) of the operating program are written to another of the at least two memory areas of the memory.

2. Method claim 1, characterized in that in one of the at least two memory areas (206c, 206d) already existing information data are checked before the further of the at least two memory areas is described.

3. The method according to any one of the preceding claims, characterized in that an arrangement of the information data (106) in the at least two memory areas (206c, 206d) is predetermined.

4. The method according to claim 3, characterized in that the operating program has information about the arrangement of the information data in the at least two memory areas (206c, 206d).

5. The method according to any one of the preceding claims, characterized in that the operating program has gaps into which the information data (106) are written.

6. The method according to any one of the preceding claims, characterized in that it comprises the following steps:

Clearing (452) a first memory area of the memory;

Writing (454) the information data to the first memory area;

Writing (456) the first portion of the operating program to the first memory area;

Clearing (458) a second memory area of the memory;

Writing (460) the information data into the second storage area; and

Writing (462) the second portion of the operating program to the second memory area.

7. The method according to any one of claims 1 to 5, characterized in that it comprises the following steps:

Clearing a second memory area of the memory; Writing the information data in the second memory area;

Clearing a first memory area of the memory;

Writing the information data in the first memory area;

Writing the second section of the operating program to the second memory area; and

Writing the first section of the operating program to the first memory area.

8. The method according to any one of the preceding claims, characterized in that a third memory area (206g) has previous information data.

9. The method according to any one of the preceding claims, characterized in that at least the information data (106) written in one of the at least two memory areas (206c, 206d) are compared with further information data.

10. The method according to any one of the preceding claims, characterized in that the method is executable by a start program of a control unit and it is the operating program to an operating software of Steuerge device and the information data (106) is non-volatile data.

A method according to any one of the preceding claims, characterized in that the memory (104) is a flash memory and the memory areas

(206c, 206d) is about sectors of the flash memory.

12. Device for carrying out all the steps of a method according to one of claims 1 to 11.

A computer program with program code means for carrying out all steps of a method according to one of claims 1 to

11 if the computer program is executed on a computer or a corresponding computer unit.

A computer program product having program code means stored on a computer readable medium for carrying out all the steps of a method as claimed in any one of claims 1 to 11 when the computer program product is executed on a computer or on a corresponding computer unit.