KR20210064994A - Method for updating vehicular control unit - Google Patents

Abstract

A method for updating a vehicle controller according to a preferred embodiment of the present invention comprises: a step of generating low difference data by comparing data of an old version and a new version; a step of generating divided difference data by dividing the low difference data for each memory sector; and a step of updating the old version to the new version using the divided difference data. Therefore, the present invention is capable of having an effect of enabling an effective and fast differential update.

Description

How to update a vehicle controller {METHOD FOR UPDATING VEHICULAR CONTROL UNIT}

The present invention relates to a method for updating a vehicle controller. More particularly, the present invention relates to an update method of a vehicle controller for updating software or information of the vehicle controller in a differential update method.

Currently, various electronic devices for user convenience are applied to vehicles according to technological development, and an update technology for updating software or information of a micro controller unit (MCU) for controlling various electronic devices is required.

In response to this demand, over-the-air (OTA) update technology that can update software or information of a vehicle controller wirelessly rather than wiredly is being developed.

On the other hand, in the case of the update technology, there is a differential update technology that updates only a changed part of all data for software update of various electronic devices, and the differential update technology requires a large-capacity memory and support from a high-end CPU.

This differential update technique is a technique commonly used in Android or Linux file systems that operate on the basis of a high-spec application processor (AP).

However, in the case of a vehicle controller, it has a relatively low-spec CPU and low-capacity memory, and there is a problem in that a general differential update technique cannot be applied due to the characteristics of a flash memory for storing software or information.

Republic of Korea Patent Publication No. 2019-0074346 (Title of the invention: vehicle software update method and vehicle using the same)

Accordingly, the present invention has been devised in view of the above circumstances, and an object of the present invention is to provide an update method for a vehicle controller capable of effectively updating software or information of a vehicle controller using a differential update method.

According to a preferred embodiment of the present invention for achieving the above object, there is provided a method for updating a vehicle controller, comprising: generating low difference data by comparing data of an old version and a new version; generating divided difference data by dividing the row difference data for each memory sector; and updating the old version to the new version using the divided difference data.

The row difference data may include identical, added, changed, and deleted data.

The same data and the deleted data may include size information, and the additional data and the changed data may include size information and data information.

The generating of the divided difference data may include sequentially loading the raw differential data in sector order, calculating old version addresses and new version addresses of the loaded data, and a memory corresponding to the new version address. It may include moving the loaded data to a sector.

The generating of the divided difference data may include additionally dividing the overlapped data when the loaded data is the same data, additional data, or changed data and overlaps two or more memory sectors.

The generating of the divided difference data may include determining a difference cancellation order for each sector in a reverse order of data movement in consideration of data moved to the memory sector.

The generating of the divided difference data may include determining a sector address of the old version of the data moved to the memory sector as a reference location of the old version.

The generating of the divided difference data may include including the difference cancellation order and the reference position of the old version in the divided difference data.

The memory sector may be applied to a memory device different from the old version and the raw difference data.

The memory sector may constitute a flash memory or SRAM as a difference release buffer.

The step of updating to the new version includes: obtaining an address value of the old version by referring to a reference position of the old version in order to de-differentiate the divided difference data; starting a difference cancellation buffer in which the divided difference data is stored obtaining an address as an address value of the new version; and de-differentiating the divided difference data according to the data type of the divided difference data, the old version address value, and the address value of the new version .

In the step of canceling the difference, the divided difference data may be released in consideration of a predetermined difference canceling procedure.

The updating to the new version may include increasing the address value of the old version and the address value of the new version by the size of the same data when the data type of the divided difference data is the same data. .

The updating to the new version may include increasing the address value of the new version by a size of the additional data when the data type of the divided difference data is additional data.

The updating to the new version may include increasing the address value of the old version and the address value of the new version by the size of the changed data when the data type of the divided difference data is changed data. .

The updating to the new version may include increasing the address value of the old version by the size of the deleted data when the data type of the divided difference data is deleted data.

The old version and the raw difference data may be stored in the same flash memory.

According to the update method of the vehicle controller according to the preferred embodiment of the present invention, there is an effect of enabling effective and fast differential update for the vehicle controller having a low-spec processing device and a low-capacity memory.

1 is a view for explaining a system configuration for updating a vehicle controller.
2 is a view for explaining a process of generating difference data in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
3 is a diagram illustrating difference data generated in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
4 illustrates an example of generating difference data in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
5 is a flowchart illustrating a process of generating difference data in a method of updating a vehicle controller according to a preferred embodiment of the present invention.
6 is a diagram illustrating divided difference data divided by sectors in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
7 is a diagram illustrating expected data movement according to data addition in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
FIG. 8 is a diagram for explaining a problematic situation that occurs when an order of releasing a difference for each sector is a forward direction when adding data in a method for updating a controller for a vehicle according to a preferred embodiment of the present invention.
FIG. 9 is a diagram showing that the problem situation of FIG. 9 can be solved in the case in which the order of releasing difference for each sector is reversed when data is added in the update method of the vehicle controller according to the preferred embodiment of the present invention.
10 is a diagram illustrating expected data movement according to data deletion in a method of updating a vehicle controller according to a preferred embodiment of the present invention.
11 is a diagram for explaining a problem that occurs when the order of releasing difference for each sector is reversed when data is deleted in the updating method of the vehicle controller according to the preferred embodiment of the present invention.
FIG. 12 is a diagram showing that the problem situation of FIG. 11 can be solved when the order of releasing difference for each sector is in the forward direction when data is deleted in the updating method of the vehicle controller according to the preferred embodiment of the present invention.
13 is a diagram illustrating expected data movement according to data addition and deletion in a method of updating a vehicle controller according to a preferred embodiment of the present invention.
14 is a diagram illustrating data movement for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
15 is a diagram illustrating a difference canceling procedure for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
16 is a flowchart illustrating a method of releasing differential data for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
17 is a first diagram illustrating data stored in each memory area in a method of updating a vehicle controller according to a preferred embodiment of the present invention.
18 is a second diagram illustrating data stored in each memory area in a method of updating a vehicle controller according to a preferred embodiment of the present invention.
19 is a first embodiment of releasing a difference by changing a difference canceling order for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.
20 is a second embodiment of releasing a difference by changing a difference canceling order for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. First, in adding reference numerals to the components of each drawing, it should be noted that the same components are given the same reference numerals as much as possible even though they are indicated on different drawings. In addition, preferred embodiments of the present invention will be described below, but the technical spirit of the present invention is not limited thereto and may be variously implemented by those skilled in the art without being limited thereto.

1 is a view for explaining a system configuration for updating a vehicle controller.

As a system configuration for updating a vehicle controller, it includes a server 1 that provides update information and a vehicle 10 that communicates with the server 1 to update software or information of the controller 20 provided therein. . The server 1 and the vehicle 10 may be connected in a wired manner, but may be connected in a wireless manner for over-the-air (OTA) update.

The vehicle 10 includes at least one controller 20 , and the controller 20 may perform a function to electrically control a specific part of the vehicle or to provide specific information to the driver.

The controller 20 includes a main control unit 30 that controls the functions of the controller 20 , a communication unit 40 that communicates with the outside of the controller 20 , and software or information for performing the functions of the controller 20 . It may include a first memory 100 for storing the. In addition, the controller 20 may further include an additional second memory 200 in addition to the first memory 100 . In an embodiment, the first memory 100 may be a flash memory, which is a type of non-volatile storage medium, and the second memory 200 may be a random access memory (RAM). Also, the second memory 200 may be a static random access memory (SRAM). However, it goes without saying that the first memory 100 and the second memory 200 are not limited to the above-described embodiments of the present invention.

When it is desired to update software or information stored in the first memory 100 , data from the server 1 is transmitted to the main control unit 30 through the communication unit 40 , and the main control unit 30 transmits the data. It is used to update software or information stored in the first memory 100 . In this case, it may be possible for the main controller 30 to temporarily store and utilize some data in the second memory 200 when updating software or information of the first memory 100 .

Meanwhile, in the present invention, the update of the vehicle controller 20 may be performed using a differential update method. In the present invention, the differential update refers to updating software or information using a difference between the file information pre-stored in the controller 20 and the file information to be updated, that is, the difference. In the method for updating a vehicle controller according to the present invention, difference data is generated by comparing the old version software or information stored in the controller 20 with the new version software or information to be updated, and the update is performed using the difference data.

The updating method of the vehicle controller according to the preferred embodiment of the present invention may update a new version of software or information in a sector of the first memory 100 in which software or information is stored without using a large-capacity memory.

Generation of difference data

A flash memory having a sector structure has a characteristic that, unlike a RAM in which read/write is free, writing is possible only after erasing a sector at a desired location for writing in the flash memory. As a method of erasing sectors of the flash memory, there are a chip erase method of erasing all sectors at once and a sector erase method of erasing each sector. If the controller 20 has excellent computing power and has a storage medium capable of storing all of the program or information of the new version to be updated, the old version of the program or information (hereinafter simply referred to as 'old version') It can be used) and update the new version of the program or information (hereafter, the term 'new version' may be used for simplicity). However, as described above, in the case of the vehicle controller 20 , it is not preferable from the viewpoint of cost or design to sufficiently secure the arithmetic capability or memory. In response to this problem, in the present invention, effective update is possible by using a method of generating difference data by comparing the old version with the new version and updating the controller 20 using the difference data.

Meanwhile, in the following description, updating an individual sector in which an old version is stored to a new version using difference data will be referred to as 'differential release'. Depending on the type of difference data and the size of the difference data, additional sectors are needed to secure a storage space or some sectors are simply erased, so it is necessary to consider the order for releasing the difference.

2 is a view for explaining a process of generating difference data in a method for updating a vehicle controller according to a preferred embodiment of the present invention, and FIG. 3 is a view for explaining a process of generating difference data in a method for updating a vehicle controller according to a preferred embodiment of the present invention. It is a figure which shows difference data.

The difference data is generated by comparing the old version of software or information (old version) and the new version of software or information (new version) stored in the sector SA of the first memory 100 of the controller 20 . Referring to FIG. 2 , the first memory 100 includes a plurality of sectors SA including a first sector SA1 , a second sector SA2 , and a third sector SA3 .

The difference data is generated by comparing the old version and the new version for each sector. The difference data may be sequentially configured by the same, addition, deletion, and change data. The comparison between the old version and the new version may be performed by the main control unit 30 of the controller 20 .

‘Same’ means that the old version and the new version are the same, so that the old version data is maintained. In the case of 'same', since the old version is not changed, only the size information of the old version data is included in the difference data.

‘Added’ means that there is data added to the new version along with the old version information. In the case of ‘addition’, new data that does not exist in the old version is included, so both size and data are included in the difference data.

‘Delete’ means that there is no old version data in the new version, so the old version data must be deleted. In the case of ‘delete’, since the old version is deleted, only the size is included in the difference data.

‘Change’ means that the old version data should be changed to the new version data. In the case of ‘change’, since the old version needs to be replaced with the new version, both the size and data are included in the difference data.

However, in the practice of the present invention, 'addition' and 'change' are not separately distinguished, and it may be possible to integrate and manage as 'change'.

Referring to FIG. 3B , the structure of the generated difference data is shown. The header of the difference data includes the size of the difference data for each sector and the reference location (address) of the old version for each sector. The data block of the difference data includes data according to the difference for each sector. Such difference data may be sorted according to the order of difference cancellation, which will be described later.

4 illustrates an example of generating difference data in a method for updating a vehicle controller according to a preferred embodiment of the present invention.

FIG. 4A shows an example of raw difference data (RDD) in which difference data is generated in the order of the sectors SA of the first memory 100 . The raw difference data RDD is a compilation of attributes and data obtained by comparing the old version and the new version in the order of the sectors SA. FIG. 4C shows an example of divided difference data (DDD) divided so that it can be stored in a sector of the first memory 100 after the update using the raw difference data RDD. In FIGS. 4A and 4C , the first sector SA1 is physically the same before and after the update, but for convenience of explanation, the first sector of the old version before the update is 'SA1', and the new version after the update is 'SA1'. The first sector of 'SA1_U' is indicated.

Since the first sector SA1 is 'same' and the second sector SA2 is 'deleted', there is only attribute information and data about size, respectively. The third sector SA3 corresponds to 'addition' and includes all data to be included in the third sector SA including the size, previous data, and data to be added. In this order, the difference data of the first to tenth sectors SA1 to SA10 are exemplified in the row differential data RDD.

In order to efficiently use the first memory 100 in updating to a new version, it is preferable to record deleted, added, or changed data in a sector of the first memory 100 reflecting the data.

A process of processing raw difference data will be described with reference to the example of FIG. 4 . In the updated first sector SA1_U of the first memory 100 , the data of the previous first sector SA1 is stored as it is. Since the data of the second sector SA2 is deleted, data according to the previous third sector SA3 may be input into the updated second sector SA2_U, but the third sector SA3 is updated due to the added data. Consider a case where all of the data cannot be stored in the second sector SA2_U. In this case, the data of the third sector SA3 is divided into the 3-1 sector data SA3-1 and the 3-th sector data SA3-1 by considering the new sector address for the new version as shown in FIG. 4B. It is created with 2 sector data (SA3-2). As shown in FIG. 4C , the 3-1 th sector data SA3-1 is allocated to the updated second sector SA2_U, and the 3-2 th sector data SA3-2 is allocated to the third sector SA3_U. ) and data of the fourth sector SA4 are allocated.

That is, in the present invention, the raw differential data RDD may be divided based on the position of the data sector to be located when the difference is released. Here, when data corresponding to the same, changed, and additional information overlaps at least two sectors, the overlapping data may be further divided based on the sector.

5 is a flowchart illustrating a process of generating difference data in a method of updating a vehicle controller according to a preferred embodiment of the present invention.

The method of generating the new version reference sector division differential data (DDD) sequentially loads the raw differential data (RDD) to detect the start sector addresses of the old version and the new version, and determine the sector position according to the start sector address of the new version It is calculated and the raw differential data RDD is input to the corresponding sector.

At this time, since the raw differential data RDD corresponding to the same, addition, and change change the address value of the new version, data may overlap in different sectors. In this case, the overlapping data is separated according to the sector size. is stored in each sector.

The calculation of the old version address value is to store the old version address when the sector is transitioned. The address value of the old version is derived to be used as the reference location of the old version when the sector-by-sector differential is released.

Referring to FIG. 5 , the process of generating the divided difference data will be described in detail. First, the data type of the row difference data RDD is determined for each sector order of the first memory 100 ( S10 ). Here, when the type of the row difference data RDD is the same, addition, or change, step S12 may be performed, and if the type of the row difference data RDD is deleted, step S32 may be performed.

When the data type of the raw differential data (RDD) is 'same', 'addition', or 'change', it is converted into a start sector based on the sector address of the new version, and the end sector is converted according to the sector address and size of the new version. converted to (S12).

It is determined whether there is a difference by comparing the start sector and the end sector (S14). Here, when the start sector and the end sector are different, step S16 may be performed, and if the start sector and the end sector are the same, step S21 may be performed.

When the start sector and the end sector are different, the size and data are divided according to the sector boundary from the start sector to the end sector (S16).

When the sector-by-sector divisional differential data DDD is located at the beginning of the sector, the address of the old version is stored (S18). Here, the old version address corresponds to the old version start address for each sector.

The divided raw differential data RDD is stored as sector-by-sector division differential data DDD (S20).

When the start sector and the end sector are the same, the old version address (the old version start address for each sector) is stored when the sector-by-sector divisional differential data DDD is located at the beginning of the sector (S21).

A start sector is added to the sector-by-sector divisional differential data DDD (S22).

After steps S20 and S22, the data type of the row difference data RDD is determined (S24).

When the data type of the raw difference data (RDD) is 'same', the old version address and size information are included in the old version reference address of the divided difference data (DDD), and the data is stored in the new version address of the divided difference data (DDD) The type 'same' and size information are included (S26).

When the data type of the raw difference data RDD is 'addition', the data type 'addition', size information, and data content are included in the new version address of the divided differential data DDD (S28).

When the data type of the raw difference data (RDD) is 'change', the old version address and size information are included in the old version reference address of the divided difference data (DDD), and data is stored in the new version address of the divided difference data (DDD) The type 'change', size information, and data content are included (S30).

On the other hand, returning to step S10, when the data type of the row differential data RDD is 'delete', the sector of the new version address is converted into a start sector (S32).

The transformed start sector is added to the divided difference data DDD (S34).

The old version address is included in the old version reference address of the divided difference data DDD, and the data type 'delete' and size information are included in the start sector of the divided differential data DDD (S36).

After steps S26, S28, S30, and S36, it is determined whether the sector-by-sector division of the row difference data RDD is completed (S38). When the sector-by-sector division of the row differential data RDD is not completed, the steps after step S10 may be continuously performed.

6 is a diagram illustrating divided difference data divided by sectors in a method for updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 6 , the raw differential data RDD includes a first sector (sector 1 difference), a second sector (sector 2 difference), a third sector (sector 3 difference), and a fourth sector (sector 4 difference), respectively. can be divided into In this case, when overlapping differential data occurs in a sector, the overlapping differential data may be further divided.

Through this, the new version reference divided difference data DDD1 may be generated. The new version reference divided difference data DDD1 may be obtained by dividing differential data based on a data sector position to be located when the difference is released.

The new version reference divided difference data DDD1 may be converted into divided difference data DDD2 including the reference position of the old version for each sector and a difference cancellation order. The divided difference data DDD2 including the difference cancellation order can preserve data of other sectors by including the reference position of the old version for each sector, and differential cancellation is possible without a separate large-capacity temporary storage memory.

Order of difference release (update by sector)

7 is a diagram for explaining expected data movement according to data addition in a method of updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 7 , in the first sector of the old version, the same data information as the new version is stored in the A address area (sector 1_A) and the B address area (sector 1_B), and the second sector of the old version is stored in the A address area ( The same data information as the new version is stored in the sector 2_A) and the B address area (sector 2_B). In this case, additional data information and the same data information as the address area A (sector 1_A) of the first sector of the old version are stored in the first sector of the new version. In addition, the same data information as the B address area (sector 1_B) of the first sector and the A address area (sector 2_A) of the second sector of the old version is stored in the second sector of the new version.

Hereinafter, data movement expected when the new version of data having additional data is moved to the sector in which the old version is stored will be described with reference to FIGS. 8 and 9 .

FIG. 8 is a diagram for explaining a problematic situation that occurs when an order of releasing a difference for each sector is a forward direction when adding data in a method for updating a controller for a vehicle according to a preferred embodiment of the present invention.

Referring to FIG. 8, if the total size of the ROM data is the same size as that of the difference cancellation buffer or there is no room for the storage space when the difference is released, only the storage space corresponding to one sector needs to be secured and processed. When the difference is released from sector 1 to sector 2 in the forward direction, the same data information (sector 1_B) in the address area A is lost in the second sector of the new version.

FIG. 9 is a diagram showing that the problem situation of FIG. 9 can be solved in the case in which the difference release order for each sector is reversed when data is added in the update method of the vehicle controller according to the preferred embodiment of the present invention.

Referring to FIG. 9 , when the total size of the ROM data is the same size as that of the difference cancellation buffer or there is no room for the storage space, when the difference is released in the reverse direction from the second sector to the first sector, the second sector In the second sector of the new version, the same data information (sector 1_B) of the address area A exists without a problem of loss when the difference is released.

10 is a diagram illustrating expected data movement according to data deletion in a method of updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 10 , in the first sector of the old version, data in the A address area (sector 1_A) is deleted in the new version, and the same data information as the new version is stored in the B address area (sector 1_B). In the second sector of the old version, the same data information as that of the new version is stored in the A address area (sector 2_A) and the B address area (sector 2_B). In this case, data information identical to the B address area (sector 1_A) of the first sector of the old version and data information identical to the address area A (sector 2_A) of the second sector of the old version are stored in the first sector of the new version. . In addition, the same data information as the B address area (sector 2_B) of the second sector of the old version is stored in the second sector of the new version.

In this way, data may be pushed due to data addition or the like, but data may be pulled due to data deletion or the like.

Hereinafter, the expected data movement when the new version of data is moved to the sector in which the old version is stored according to data deletion will be described with reference to FIGS. 11 and 12 .

11 is a diagram for explaining a problem that occurs when the order of releasing difference for each sector is reversed when data is deleted in the updating method of the vehicle controller according to the preferred embodiment of the present invention.

Referring to FIG. 11 , when the difference is released in the reverse direction from the second sector to the first sector, the same data information (sector 2_A) in the B address area is lost in the first sector of the new version.

FIG. 12 is a diagram showing that the problem situation of FIG. 11 can be solved in the case in which the difference release order for each sector is forward when data is deleted in the update method of the vehicle controller according to the preferred embodiment of the present invention.

Referring to FIG. 12 , when the difference is released in the forward direction from the first sector to the second sector, when the second sector is released, all data information (sector 2_A) of the address area B is lost in the new version of the first sector without a problem. come to exist

13 is a diagram illustrating expected data movement according to data addition and deletion in a method of updating a vehicle controller according to a preferred embodiment of the present invention.

Data movement may occur in the old version of data L from the new version to the data L', but data movement such as data M' from the old version data L to the new version data M', or the old version data M to the new version data N', etc. cannot occur That is, if the data location of the old version is in the order of L, M, N, the location of the new version data copied from it is also in the order of L', M', N'.

14 is a diagram illustrating data movement for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 14 , when the data movement of FIG. 13 is applied to each sector, it can be seen that the N-th sector has a unidirectional data movement relation with other sectors. When N is 4, if data movement occurs in the order of sector 5, sector 4, and sector 3, the reversed data movement cannot exist at the same time. For example, data movement cannot occur from sector 4 to sector 5, data movement from sector 3 to sector 4 cannot occur, and data movement from sector 3 to sector 5 cannot occur.

15 is a diagram illustrating a difference canceling procedure for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 15 , data may be moved between sectors by adding or deleting data.

Data in a sector may move, for example, from sector 2 to sector 1, sector 3, and sector 4 unidirectional left-to-right, and from sector 7 to sector 6 unidirectional left-to-right movement, for example. In addition, sector data may move from sector 3 to sector 4, sector 5, and sector 6 in a unidirectional left to right direction. However, data in the sector cannot be moved from sector 1 to sector 2 and from sector 7 to sector 3 cannot be moved.

The difference cancellation order can be set by setting a sector that emits difference data as a low priority and a sector that receives difference data as a high priority. In an embodiment, sector 2 and sector 7 are sectors for exporting differential data, and the lowest priority may be set. Sector 1 and sector 3 are sectors for receiving differential data, and a higher priority than sector 2 and sector 7 may be set. Meanwhile, sector 3 is a sector that emits difference data, and a lower priority than sector 1 may be set. Sector 4, sector 5, and sector 6 are sectors that receive differential data, and the highest priority may be set.

If differential cancellation is performed opposite to data movement, differential cancellation of all sectors is possible without data loss. Here, the sectors on the same vertical line are irrespective of the order.

The update method of the vehicle controller according to the present invention is that differential data for each sector can be released according to the difference canceling order, data of other sectors to be referenced is preserved, and differential data can be released without a separate large-capacity memory. characterized.

16 is a flowchart illustrating a method of releasing differential data for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 16 , difference data and old version data are required to cancel the difference. In addition, in the case of differential data divided for each sector, the reference position of the old version is required.

The starting address value of the old version is set from the old version reference position calculated when generating the difference data. Since the start address value of the new version is the start address of the difference cancellation buffer, it is initialized to 0 (S101).

The difference data is loaded (S103).

The type of the loaded difference data is determined (S105).

When the types of difference data are the same, the data of the old version is loaded (S107). Here, the old version data includes the old version sector address and size information.

The loaded old version data is stored in the difference cancellation buffer (S109). Here, the difference release buffer may be a flash memory or an SRAM.

The sector address of the old version is increased by the size from the current sector address value of the old version, and the sector address of the new version is increased by the size from the sector address value of the current version (S111). At this time, the sector address of the old version and the sector address of the new version are stored in the difference cancellation buffer.

When the type of difference data is additional, difference data including size information is loaded (S113).

The loaded difference data is stored in the difference cancellation buffer (S115). Here, the difference release buffer may be a flash memory or an SRAM.

The sector address of the new version increases by a size from the current sector address value of the new version (S117). At this time, the sector address of the new version is stored in the de-differential buffer. Sector addresses of older versions are not incremented.

When the type of difference data is change, the difference data including size information is loaded ( S119 ).

The loaded difference data is stored in the difference cancellation buffer (S121). Here, the difference release buffer may be a flash memory or an SRAM.

The address of the old version increases by the size from the address value of the current version, and the address of the new version increases by the size from the address value of the current version (S123). At this time, the address of the old version and the address of the new version are stored in the difference cancellation buffer.

When the type of difference data is deletion, the address of the old version increases by the size of the deleted data from the address value of the current old version (S125). At this time, the address of the old version is stored in the difference cancellation buffer.

This is repeated until the difference cancellation of the difference data for each sector is completed (S127).

When the difference release of the differential data for each sector is completed, the differential data of the corresponding sector is stored in the flash memory (S120).

It is determined whether the difference between the sectors in the last order has been released (S131). When all sectors have been de-differentiated, the process ends.

If it is not the last order, difference release is performed on the difference data for each next sector according to the pre-interpreted order (S133).

17 is a first diagram illustrating data stored in each memory area in a method of updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 17 , according to a general method of releasing difference data, various types of data may be stored separately for each memory area as shown in FIGS. 17A and 17B .

In FIG. 17A , for example, the flash memory area of the vehicle controller corresponds to twice or more of the ROM data, the old version and the difference data are stored in the flash memory area, and the new memory area of the flash memory area A new version may be stored in .

In (b) of FIG. 17 , for example, a difference cancellation buffer corresponding to a single sector and a temporary storage buffer for data movement may be provided. The difference release buffer and temporary storage buffer can be configured with new flash memory or SRAM. In this case, when the difference release buffer and the temporary storage buffer are configured by flash memory instead of SRAM, the difference release time may be excessive. In addition, there is a capacity problem to be configured with SRAM.

18 is a second diagram illustrating data stored in each memory area in a method of updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 18 , according to the update method of the vehicle controller according to the preferred embodiment of the present invention, original data and difference data are stored in a flash memory area, and a difference release buffer may be stored in a separate flash memory or SRAM area. have.

This shows that, as shown in (a) of FIG. 17 , a flash memory area twice as large as that of ROM data is not required, and a temporary storage buffer is not required as in (b) of FIG. 17 .

In addition, even if the difference cancellation buffer is configured in the flash memory, the erase and write time for the flash memory area is reduced as shown in FIG. 17(b), and since a relatively small memory is required, the difference cancellation buffer using SRAM is used. It can be configured, and in this case, the speed of releasing the difference is the fastest.

19 is a first embodiment of releasing a difference by changing a difference canceling order for each sector in a method of updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 19 , the present invention is characterized in that the difference canceling order is changed according to the movement of data by sector. According to the first embodiment, the difference canceling order of sectors may be included in the difference data itself.

20 is a second embodiment of releasing a difference by changing a difference releasing order for each sector in a method for updating a vehicle controller according to a preferred embodiment of the present invention.

Referring to FIG. 20 , according to the second embodiment of the present invention, although the difference canceling order is not included in the difference data, there is a method in which the main controller of the vehicle controller grasps the corresponding order to perform the sector-by-sector differential cancellation.

As described above, the update method of the vehicle controller according to the preferred embodiment of the present invention supplements the characteristics of the flash memory sector (sector-unit deletion, data writing sequentially, very slow deletion and writing speed), and a low-capacity memory ( In order to enable differential update using SRAM), it is a method of generating sector-by-sector differential data, arranging the differential data in a movement order, and then releasing sector-by-sector differential data in the reverse order.

The method of updating a vehicle controller according to a preferred embodiment of the present invention has an effect that differential update is possible without using additional memory according to the movement of difference data using only a low-capacity memory (single sector size) constituting the difference cancellation buffer.

The above description is merely illustrative of the technical idea of the present invention, and those of ordinary skill in the art to which the present invention pertains may make various modifications, changes, and substitutions within the scope without departing from the essential characteristics of the present invention. will be. Accordingly, the embodiments disclosed in the present invention and the accompanying drawings are for explaining, not limiting, the technical spirit of the present invention, and the scope of the technical spirit of the present invention is not limited by these embodiments and the accompanying drawings. .

Steps and/or operations according to the present invention may occur concurrently in different embodiments, in a different order, or in parallel, or for different epochs, etc., as would be understood by one of ordinary skill in the art. can

Depending on the embodiment, some or all of the steps and/or operations run instructions, programs, interactive data structures, clients and/or servers stored in one or more non-transitory computer-readable media. At least some may be implemented or performed using one or more processors. The one or more non-transitory computer-readable media may be illustratively software, firmware, hardware, and/or any combination thereof. Further, the functionality of a “module” discussed herein may be implemented in software, firmware, hardware, and/or any combination thereof.

1: Server
10: vehicle
20: controller
30: main fisherman
40: communication department
100: first memory
200: second memory

Claims (17)

generating raw difference data by comparing the data of the old version and the new version;
generating divided difference data by dividing the row difference data for each memory sector; and
updating the old version to the new version using the divided difference data;
An update method of a vehicle controller comprising a. The method of claim 1,
The raw difference data, the updating method of the vehicle controller, characterized in that configured to include the same, addition, change, and deletion data. 3. The method of claim 2,
The same data and the deleted data include size information, and the additional data and the changed data include size information and data information. 3. The method of claim 2,
The step of generating the divided difference data includes:
Sequentially loading the raw differential data in sector order, calculating an old version address and a new version address of the loaded data, and moving the loaded data to a memory sector corresponding to the new version address. An update method of a vehicle controller comprising a. 5. The method of claim 4,
The step of generating the divided difference data includes:
and dividing the overlapped data further when the loaded data is the same data, additional data, or changed data and overlaps two or more memory sectors. 5. The method of claim 4,
The step of generating the divided difference data includes:
and determining a difference cancellation order for each sector in a reverse order of data movement in consideration of data moved to the memory sector. 7. The method of claim 6,
The step of generating the divided difference data includes:
and determining a sector address of the old version of the data moved to the memory sector as a reference location of the old version. 8. The method of claim 7,
The step of generating the divided difference data includes:
and including the difference release order and the reference position of the old version in the divided difference data. 5. The method of claim 4,
and the memory sector is applied to a memory device different from the old version and the raw difference data. 10. The method of claim 9,
and the memory sector constitutes a flash memory or an SRAM as a difference release buffer. The method of claim 1,
The step of updating to the new version is,
obtaining an address value of the old version with reference to the reference position of the old version in order to de-differentiate the divided difference data;
obtaining a start address of a difference release buffer in which the divided difference data is stored as an address value of a new version; and
and de-differentiating the divided difference data according to a data type of the divided difference data, the old version address value, and the new version address value. 12. The method of claim 11,
The step of canceling the difference is
An update method of a vehicle controller, characterized in that the divided difference data is released in consideration of a predetermined difference cancellation order. 12. The method of claim 11,
The step of updating to the new version is,
and increasing the address value of the old version and the address value of the new version by the size of the same data when the data type of the divided difference data is the same data. 12. The method of claim 11,
The step of updating to the new version is,
and increasing the address value of the new version by the size of the additional data when the data type of the divided difference data is additional data. 12. The method of claim 11,
The step of updating to the new version is,
and increasing the address value of the old version and the address value of the new version by the size of the changed data when the data type of the divided difference data is changed data. 12. The method of claim 11,
The step of updating to the new version is,
and increasing the address value of the old version by the size of the deleted data when the data type of the divided difference data is deleted data. The method of claim 1,
and the old version and the raw difference data are stored in the same flash memory.

Images