Electronic control unit, method and program

By expanding data from non-volatile to volatile memory using a margin area and valid part information, the ECU optimizes volatile memory usage, addressing inefficiencies in data rearrangement during software updates.

JP7593157B2Active Publication Date: 2024-12-03TOYOTA JIDOSHA KK
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2021018342
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-02-08
Publication Date
2024-12-03
Estimated Expiration
2041-02-08

AI Technical Summary

Technical Problem

Existing ECUs inefficiently utilize volatile memory storage capacity due to the provision of unused areas in non-volatile memory, which hinders efficient data rearrangement during software updates.

Method used

The ECU includes a volatile memory with a data portion and a non-volatile memory that has a storage area with a margin, utilizing valid part information to efficiently expand data from the non-volatile memory to the volatile memory, thereby optimizing storage capacity.

Benefits of technology

This approach allows for efficient use of volatile memory capacity by minimizing data rearrangement during software updates, enhancing the ECU's operational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007593157000001
    Figure 0007593157000001
  • Figure 0007593157000002
    Figure 0007593157000002
  • Figure 0007593157000003
    Figure 0007593157000003
Patent Text Reader

Abstract

To provide an ECU (electronic control unit) or the like capable of efficiently utilizing a storage capacity of a volatile memory.SOLUTION: An electronic control unit according to the present disclosure includes: a volatile memory; a non-volatile memory containing a storage area having a data section in which data to be developed into the volatile memory is written, and a margin area being an unused section corresponding to the data; and a control unit which develops the data in the non-volatile memory to the volatile memory. The non-volatile memory stores effective part information being information indicating the data section. The control unit develops the data in the non-volatile memory to the storage area of the volatile memory on the basis of the effective part information.SELECTED DRAWING: Figure 6
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present disclosure relates to an ECU (electronic control unit), a method, a program, etc., mounted on a vehicle. [Background technology]

[0002] A vehicle is equipped with multiple ECUs (electronic control units) for controlling the operation of the vehicle. Each ECU includes a processor, a volatile storage unit (volatile memory) such as a RAM, and a non-volatile storage unit (non-volatile memory) such as a flash ROM, and the processor deploys software stored in the non-volatile memory into the volatile memory and executes it to realize the control functions of the ECU. The software stored in the non-volatile memory of each ECU can be rewritten by wireless communication or the like, and by updating to a newer version of the software, it is possible to improve the functions of each ECU or add new vehicle control functions.

[0003] If the data constituting the software stored in the non-volatile memory of the ECU is written and arranged closely together in the storage area of ​​the non-volatile memory, even an update that changes part of the software content may require a large amount of data rewriting because many rearrangements of data that do not change the content occur. To solve this problem, a technology has been proposed that provides unused areas (margin areas) for each of the multiple applications constituting the software in the storage area of ​​the non-volatile memory, thereby limiting rearrangements of data that do not change the content to an application unit when updating the software and avoiding a large amount of data rewriting (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2020-24579 A Summary of the Invention [Problem to be solved by the invention]

[0005] As described above, if unused areas (margin areas) are provided in the storage area of ​​the non-volatile memory for each of the multiple applications that make up the software, it is possible to avoid rewriting large amounts of data. However, when the software in the non-volatile memory is expanded into the volatile memory and executed, this unused area may also be expanded, which may result in inefficient use of the storage capacity of the volatile memory.

[0006] Therefore, an object of the present disclosure is to provide an ECU (electronic control unit), a method, a program, etc., that can efficiently use the storage capacity of a volatile memory. [Means for solving the problem]

[0007] The electronic control unit of the present disclosure is an electronic control unit mounted on a vehicle and comprises a volatile memory, a non-volatile memory having a storage area including a data portion into which data to be expanded into the volatile memory is written and a margin portion which is an unused portion corresponding to the data, and a control unit which expands the data from the non-volatile memory into the volatile memory, the non-volatile memory storing valid portion information which is information indicating the data portion, and the control unit expanding the data from the non-volatile memory into the storage area of ​​the volatile memory based on the valid portion information.

[0008] The method disclosed herein is a method executed by a computer equipped with a processor, a volatile memory, and a non-volatile memory mounted on a vehicle, and includes an expansion step of expanding data from a non-volatile memory having a memory area including a data portion into which data to be expanded into the volatile memory is written and a margin portion which is an unused portion corresponding to the data, and in the expansion step, the data from the non-volatile memory is expanded into the memory area of ​​the volatile memory based on valid portion information which is information indicating the data portion stored in the non-volatile memory.

[0009] The program of the present disclosure is a program executed by a computer mounted on a vehicle and having a processor, a volatile memory, and a non-volatile memory, and causes the computer to execute an expansion step of expanding data from a non-volatile memory having a memory area including a data portion into which data to be expanded into the volatile memory is written and a margin portion which is an unused portion corresponding to the data, and in the expansion step, expands the data from the non-volatile memory into the memory area of ​​the volatile memory based on valid portion information which is information indicating the data portion stored in the non-volatile memory. Effect of the Invention

[0010] According to the present disclosure, it is possible to provide an ECU (electronic control unit), a method, a program, etc., that can efficiently use the storage capacity of a volatile memory. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 is a block diagram showing an example of an overall configuration of a network system according to an embodiment; [Diagram 2] FIG. 2 is a block diagram showing an example of a schematic configuration of the ECU shown in FIG. 1. [Diagram 3] A flowchart illustrating an example of a control process executed by an ECU according to an embodiment. [Figure 4] FIG. 4 is a schematic diagram for explaining a state in which data in a non-volatile memory is updated by the control process shown in FIG. 3; [Diagram 5] A flowchart illustrating an example of a control process executed by an ECU according to an embodiment. [Figure 6] FIG. 6 is a schematic diagram for explaining a state in which data in a non-volatile memory is expanded into a volatile memory by the control process shown in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] (One embodiment) Fig. 1 is a block diagram showing an example of an overall configuration of a network system according to a first embodiment of the present invention, Fig. 2 is a block diagram showing an example of a schematic configuration of an ECU shown in Fig. 1.

[0013] The network system shown in FIG. 1 is a system for updating software of ECUs (Electronic Control Units) 13a to 13d mounted on a vehicle, and includes an OTA center 1 and an in-vehicle network 2 mounted on the vehicle.

[0014] The OTA center 1 is capable of communicating wirelessly or otherwise with an OTA master 11 installed in a vehicle via a communication network 5 such as the Internet, and is equipped with, for example, a CPU, RAM, a storage device, and a communication device (not shown), and manages software updates for ECUs 13a to 13d installed in the vehicle.

[0015] As shown in FIG. 1, the in-vehicle network 2 includes an OTA master 11, a communication module 12, a plurality of ECUs 13a to 13d, and an HMI (Human Machine Interface; for example, a display device of a car navigation system that allows input operations) 14. The OTA master 11 is connected to the communication module 12 via a bus 15a, to the ECUs 13a and 13b via a bus 15b, to the ECUs 13c and 13d via a bus 15c, and to the HMI 14 via a bus 15d. The OTA master 11 can wirelessly communicate with the OTA center 1 via the communication module 12. The OTA master 11 controls software update of an ECU (sometimes referred to as a "target ECU") to be updated among the ECUs 13a to 13d based on update data acquired from the OTA center 1. The communication module 12 is a communication device that connects the in-vehicle network 2 and the OTA center 1. The ECUs 13a to 13d control the operation of each part of the vehicle. The HMI 14 is used to perform various displays during software update processing of the ECUs 13a to 13d, such as displaying the presence of update data, displaying a consent request screen for requesting consent to the software update from a user or administrator, displaying update results, etc. Note that, although four ECUs 13a to 13d are illustrated in FIG. 1, the number of ECUs is not limited.

[0016] 2, the ECU 13 includes a CPU 21 (Central Processing Unit; control unit), a volatile memory 22, a nonvolatile memory 23, and a communication device 24. The volatile memory 22 is, for example, a RAM (Random Access Memory), and the nonvolatile memory 23 is, for example, a flash ROM (Flash Read Only Memory). The CPU 21 loads software (programs, etc.) read from the nonvolatile memory 23 into the volatile memory 22, executes processing using the volatile memory 22 as a working area, and communicates with other devices via a bus using a communication device 45 as necessary, thereby realizing the functions of the ECU 13.

[0017] The CPU 21 and the volatile memory 22 are formed as a SoC (System on a chip) on one semiconductor chip. This has the advantage of speeding up the arithmetic processing. On the other hand, the non-volatile memory 23 is not formed on the semiconductor chip, but is connected to the semiconductor chip by being assembled thereon.

[0018] The OTA master 11 includes, for example, a microcomputer including a CPU, a RAM, a ROM, and a storage device, and a communication device (not shown) that communicates with the communication module 12, the ECUs 13a to 13d, and the HMI 14 via a bus.

[0019] Here, the software update process consists of a phase of downloading update data from the OTA center 1, a phase of transferring the downloaded update data to the target ECU to be updated and installing the update data in the memory area of ​​the target ECU, and an activation phase of enabling the updated version of the software installed in the target ECU.

[0020] Downloading is a process of receiving update data for updating the ECU software transmitted from the OTA center 1 and storing it in the storage device of the OTA master 11. The downloading phase includes not only receiving the update data but also controlling a series of processes related to the download, such as judging whether the download can be performed and verifying the update data. Installing is a process of writing an updated program (update software) to the non-volatile memory of the target ECU to be updated, based on the downloaded update data. The installing phase includes not only executing the installation but also controlling a series of processes related to the installation, such as judging whether the installation can be performed, transferring the update data and verifying the updated program. Activating is a process of activating (enabling) the installed updated program. The activating phase includes not only executing the activation but also controlling a series of processes related to the activation, such as judging whether the activation can be performed and verifying the execution results.

[0021] The update data transmitted from the OTA center 1 to the OTA master 11 may include any of update software for the ECU, compressed data obtained by compressing the update software, and divided data obtained by dividing the update software or the compressed data. The update data may also include an identifier (ECU ID) that identifies the target ECU to be updated, and an identifier (ECU software ID) that identifies the software before the update. The update data is downloaded as a distribution package, and the distribution package includes update data for a single or multiple ECUs.

[0022] If the update data includes the update software itself, in the installation phase, the OTA master 11 transfers the update data (i.e., the update software) to the target ECU. Also, if the update data includes compressed data, difference data, or divided data of the update software, the OTA master 11 may transfer the update data to the target ECU and the target ECU may generate the update software from the update data, or the OTA master 11 may generate the update software from the update data and then transfer the update software to the target ECU. Here, the update software can be generated by decompressing the compressed data and assembling the difference data or divided data.

[0023] The target ECU can install the update software based on an installation request (program update request) from the OTA master 11. Alternatively, the target ECU that receives the update data can autonomously install the software without receiving an explicit instruction from the OTA master 11.

[0024] In this embodiment, as an example, the OTA master 11 transfers update data, which is difference data of the update software, to the target ECU, and the target ECU generates the update software from the update data (difference data). Also, as an example, the target ECU installs the update software in response to an installation request (program update request) from the OTA master 11.

[0025] The activation of the update software can be performed by the target ECU based on an activation request from the OTA master 11. Alternatively, the target ECU that has received the update data may autonomously activate the software without receiving an explicit instruction from the OTA master 11.

[0026] Fig. 3 is a flowchart showing an example of a process in which the ECU 13 according to the present embodiment installs update data (performs software updates) in the non-volatile memory 23. Fig. 4 is a schematic diagram for explaining a state in which data in the non-volatile memory 23 is updated by the process shown in Fig. 3.

[0027] As shown in FIG. 4, the storage area of ​​the non-volatile memory 23 includes areas 0 to n. The areas 0 to n are not structural divisions but divisions based on the addresses of the storage areas. In each of the areas 1 to n, information used at the time of deployment 31 (31-1 to 31-n) that is information used when deploying data in the volatile memory 22 and program data 32 (32-1 to 32-n) for realizing the functions of the ECU 13 are stored, and an unused area (margin portion) 33 (33-1 to 33-n) is provided. The program data 32 is, for example, data of an application that realizes the functions of the ECU 13, but is not limited thereto. The information used at the time of deployment 31 includes security information used for security checks such as digital signatures and MACs (Message Authentication Codes), and valid portion information indicating the arrangement position (address) of the program data 32. The information used at the time of deployment 31-0 and program data 32-0 are stored in the area 0, but an unused area (margin portion) is not provided. Furthermore, the expansion use information 31-0 of area 0 includes security information but does not include valid portion information.

[0028] 3 and 4, a control process in which the ECU 13 installs update data in the non-volatile memory 23 (performs software update) will be described below. The process in FIG. 3 is started when the CPU 21 of the ECU 13 receives a program update request from the OTA master 11.

[0029] In step S1, the CPU 21 determines an update area of ​​the non-volatile memory 23. For example, the CPU 21 determines area 1 (area 1 where update processing has not been executed) in Fig. 4 as the area to be updated. After that, the process proceeds to step S2.

[0030] In step S2, the CPU 21 updates the program data in the update area determined in step S1. Specifically, the CPU 21 executes rewriting to change the changed or added portion (difference data) of the program data 32 in the update area, and also executes rewriting to change the layout of the portion whose layout is shifted due to the change. For example, as shown in area 1 of FIG. 4, the CPU 21 executes rewriting to change the changed or added portion (difference data) 40, and also executes rewriting to change the layout of the portion 41 whose layout is shifted due to the change. When the program data 32 is updated in this way, data rewriting occurs due to the layout change associated with the data change, but the amount of data rewriting can be suppressed by providing an unused area (margin portion) 33 as shown in FIG. 4. Thereafter, the process proceeds to step S3.

[0031] In step S3, CPU 21 updates the security information of the update area determined in step S1. Specifically, CPU 21 updates the data of the security information (digital signature, MAC, etc.) of the update area in accordance with the program update executed in step S2. For example, when area 1 in Fig. 4 is the update area, CPU 21 updates the security information for program data 32-1 in accordance with the update of program data 32-1 in area 1. Thereafter, the process proceeds to step S4.

[0032] In step S4, CPU 21 updates the valid portion information of the update area determined in step S1. Specifically, CPU 21 updates the valid portion information indicating the arrangement position (address) of program data 32 in the update area in response to the program update executed in step S2. For example, when area 1 in Fig. 4 is the update area, CPU 21 updates the valid portion information indicating the arrangement position (address) of program data 32-1 in response to the update of program data 32-1 in area 1. Thereafter, the process proceeds to step S5.

[0033] By the processes of steps S3 and S4, the security information and the valid portion information are updated for the update area determined in step S1, so that the deployment use information 31 is updated.

[0034] In step S5, the CPU 21 judges whether or not the process has been executed for all the update areas, and if the judgement is NO, the process returns to step S1, and if the judgement is YES, the process of Fig. 3 is terminated. In this way, the process is executed for all the update areas.

[0035] As described with reference to FIG. 4, the area 0 does not have an unused area (margin portion) 33, and the valid portion information is not stored. This is because the program data 32-0 in the area 0 is program data used to expand the data of the non-volatile memory 23 to the volatile memory 22, and the amount of data does not change due to software update, so the unused area 33 is not required, and therefore the valid portion information is not required. In this way, since the area 0 does not have the unused area (margin portion) 33 and the valid portion information, when the area 0 is an update area, the process of step S4 in FIG. 3 is omitted. When the amount of data of the program data 32-0 in the area 0 changes due to software update, the unused area 33 is provided in the area 0 as in the areas 1 to n, the valid portion information is stored, and the process of step S4 in FIG. 3 is executed.

[0036] Fig. 5 is a flowchart showing an example of a process in which the ECU 13 according to this embodiment loads software (programs, etc.) stored in the nonvolatile memory 23 into the volatile memory 22. Fig. 6 is a schematic diagram for explaining a state in which the software (programs, etc.) stored in the nonvolatile memory 23 is loaded into the volatile memory 22 by the process shown in Fig. 5. Fig. 6(1) shows a storage area of ​​the nonvolatile memory 23, and Fig. 6(2) shows a state in which the data (software) stored in the nonvolatile memory 23 is loaded into the storage area of ​​the volatile memory 22. Note that the storage area of ​​the nonvolatile memory 23 shown in Fig. 6(1) has been explained using Fig. 4, and therefore will not be explained again.

[0037] 5 and 6, a process in which the ECU 13 loads software (programs, etc.) stored in the nonvolatile memory 23 into the volatile memory 22 will be described. The process in Fig. 5 is started at a predetermined timing (when the ECU 13 is powered on or reset, etc.) at which the software in the nonvolatile memory 23 is loaded into the volatile memory 22.

[0038] In step S11, CPU 21 performs a security check on program data 32-0 in area 0 of non-volatile memory 23, and loads program data 32-0 in volatile memory 22. Specifically, as shown in Fig. 6, CPU 21 performs a security check on program data 32-0 in area 0 using security information included in load-time usage information 31-0 for area 0, and loads program data 32-0 in volatile memory 22. Program data 32-0 is data of a program for executing a process of loading data in non-volatile memory 23 in volatile memory 22. Thereafter, the process proceeds to step S12.

[0039] In step S12, the CPU 21 creates data of expansion area information in the volatile memory 22. Specifically, the CPU 21 executes the program data 32-0 expanded in the volatile memory 22 in step S11, creates expansion area information 34 as shown in Fig. 6(2), and stores it in the volatile memory 22. The expansion area information 34 is information that indicates the area (address) in the storage area of ​​the volatile memory 22 where the data of the non-volatile memory 23 has been expanded. Thereafter, the process proceeds to step S13.

[0040] In step S13, the CPU 21 determines a source area of ​​the non-volatile memory 23. Specifically, the CPU 21 determines an area for which the development process has not been executed among areas 1 to n of the non-volatile memory 23 as the source area. For example, the CPU 21 determines area 1 in Fig. 6(1) as the source area. After that, the process proceeds to step S14.

[0041] In step S14, the CPU 21 identifies the valid portion of the source area determined in step S13 based on the valid portion information. Specifically, the CPU 21 identifies the valid portion (the arrangement position (address) of the program data 32 in the source area) indicated by the valid portion information included in the during-extraction usage information of the source area determined in step S13. For example, when area 1 in FIG. 6(1) is the source area, the CPU 21 identifies the arrangement position (address) of the program data 32-1 as the valid portion based on the valid portion information included in the during-extraction usage information 31-1. Then, the process proceeds to step S15.

[0042] In step S15, the CPU 21 performs a security check on the valid portion identified in step S14. For example, when the CPU 21 identifies the arrangement position of the program data 32-1 in area 1 in Fig. 6(1) as the valid portion, the CPU 21 performs a security check on the program data 32-1 using the security information included in the deployment use information 31-1 in area 1. Thereafter, the process proceeds to step S16.

[0043] In step S16, the CPU 21 determines the destination address of the valid portion identified in step S14 based on the valid portion information and the development area information. A specific description will be given below with an example in which the arrangement position of the program data 32-2 in area 2 in FIG. 6(1) is identified as the valid portion. The CPU 21 determines the destination address of the program data 32-2 in the storage area of ​​the volatile memory 22 based on the arrangement position (address) of the program data 32-2 indicated by the valid portion information included in the development use information 31-2 in area 1. At this time, the CPU 21 determines the destination address of the program data 32-2 in the storage area of ​​the volatile memory 22 by filling the storage area of ​​the volatile memory 22 with no free space based on the development area information 34 (information indicating the area where the data of the non-volatile memory 23 has been developed), as shown in FIG. 6(2). Thereafter, the process proceeds to step S17.

[0044] In step S17, the CPU 21 loads the data of the valid portion identified in step S14 into the load destination address in the volatile memory 22 determined in step S16. After that, the process proceeds to step S18.

[0045] In step S18, the CPU 21 updates the development area information 34 of the volatile memory 22. For example, in FIG. 6(2), when the program data 32-1 and 32-2 have been developed in the storage area of ​​the volatile memory 22, the CPU 21 updates the development area information 34 to indicate the areas where these data have been developed. Then, the process proceeds to step S19.

[0046] In step S19, the CPU 21 judges whether or not the process has been executed for all source areas, and if the judgement is NO, the process returns to step S13, and if the judgement is YES, the process of Fig. 5 is terminated. In this manner, the process is executed for all source areas, and the data (software) in the non-volatile memory 23 is expanded in the volatile memory 22 as shown in Fig. 6.

[0047] As described above, according to this embodiment, by providing an unused area (margin portion) 33 for each program data 32 (for each area) in the storage area of ​​the non-volatile memory 23 (see Figures 3 and 4), it is possible to limit rearrangement of data whose contents are not changed during software update to program data units, thereby avoiding rewriting of a large amount of data.

[0048] Furthermore, according to this embodiment, when data in non-volatile memory 23 is expanded into volatile memory 22, a portion of program data 32 excluding unused area (margin portion) 33 can be expanded into volatile memory 22 using valid portion information indicating the location (address) of program data 32 (see Figures 5 and 6), thereby making it possible to effectively use the memory capacity of volatile memory 22.

[0049] Furthermore, according to this embodiment, the program data 32 can be written without leaving any free space based on the expansion area information indicating the area (address) where the data has already been expanded in the volatile memory 22, thereby making effective use of the memory capacity of the volatile memory 22.

[0050] In this embodiment, since the CPU 21 and the volatile memory 22 are formed on one semiconductor chip as a SoC (System on a chip), the arithmetic processing can be accelerated, but the capacity of the volatile memory 22 is relatively small, and it is difficult to expand the capacity. According to this embodiment, the memory capacity of the volatile memory 22 can be effectively used as described above, and therefore the above-mentioned disadvantages of the configuration in which the CPU 21 and the volatile memory 22 are formed on one semiconductor chip as a SoC can be overcome.

[0051] (Modification) In the above embodiment, an example has been described in which the program data 32 in the non-volatile memory 23 is loaded into the volatile memory 22 in order starting from area 1 (see FIG. 6). However, if the program data 32 is loaded into the volatile memory 22 in order, it is not necessary to load the program data 32 in order starting from area 1.

[0052] In the above embodiment, an example has been described in which the program data 32 in the nonvolatile memory 23 is packed and expanded in the volatile memory 22 in order starting from area 1 (see FIG. 6). However, it is also possible to determine the expansion destination addresses of all the program data 32 in areas 1 to n of the nonvolatile memory 23 to be packed arrangement positions, and then pack and expand all the program data 32 in areas 1 to n into the volatile memory 22. In this case, the expansion area information is information indicating the area (address) in the storage area of ​​the volatile memory 22 where the data of the nonvolatile memory 23 is to be expanded.

[0053] Furthermore, in the above embodiment, an example has been described in which the storage area of ​​the non-volatile memory 23 is divided into areas 0 to n on an application basis, but the present invention is not limited to this.

[0054] In addition, in the above embodiment, the ECU has been taken as an example for explanation, but the present invention is not limited to this.

[0055] In addition, the functions of the ECU exemplified in the above embodiments can also be realized as a method executed by a computer having a processor (CPU) and memory, or as a program executed by the computer, or as a computer-readable non-transitory storage medium storing the program. [Industrial Applicability]

[0056] The disclosed technology can be used in ECUs (electronic control units) and the like. [Explanation of symbols]

[0057] 1 OTA Center 2. In-vehicle network 5. Communication Network 11 OTA Master 12 Communication Module 13a~13d ECU 14 Human Machine Interface 15a~15d Bus 21 CPU 22 Volatile Memory 23 Non-volatile memory 24 Communication Equipment 31 Deployment usage information 32 Program Data 33 Unused area (margin area) 34 Expansion Area Information

Claims

1. An electronic control unit mounted on a vehicle, A volatile memory; a non-volatile memory having a plurality of areas each having a data portion in which data is written and an unused portion in which no data is written, and storing valid portion information which is information indicating the data portion of each of the areas; a control unit that expands data written in the nonvolatile memory into the volatile memory, The control unit is an electronic control unit that expands all of the data of the data portion in each of the areas of the non-volatile memory into a memory area of ​​the volatile memory in a packed state with no free space based on the valid portion information.

2. The control unit is storing in the volatile memory development area information indicating an area in which data has been developed in the storage area of ​​the volatile memory; 2. The electronic control unit according to claim 1, further comprising: a data storage unit configured to store data in said non-volatile memory in said storage area of ​​said volatile memory, said data storage unit storing ....

3. 3. The electronic control unit according to claim 1, wherein the control unit and the volatile memory are formed on a single semiconductor chip.

4. A method executed by a computer on board a vehicle, the computer having a processor, a volatile memory, and a non-volatile memory, the method comprising: a developing step of developing data written in the non-volatile memory, the non-volatile memory having a storage area including a plurality of areas each including a data portion in which data is written and an unused portion in which no data is written, in the volatile memory; In the expansion step, based on valid portion information, which is information indicating the data portion of each of the areas stored in the non-volatile memory, all data of the data portion in each of the areas of the non-volatile memory is expanded into the memory area of ​​the volatile memory in a packed state with no free space.

5. A program executed by a computer equipped with a processor, a volatile memory, and a non-volatile memory, the computer being mounted on a vehicle, a data storage step of storing data written in the non-volatile memory, the data storage step including a plurality of areas each including a data portion in which data is written and an unused portion in which no data is written, in the volatile memory; A program that, in the expansion step, expands all of the data of the data portion in each of the areas of the non-volatile memory into a memory area of ​​the volatile memory in a packed state with no free space based on valid portion information, which is information indicating the data portion of each of the areas stored in the non-volatile memory.

Citation Information

Patent Citations

  • Information processor, housing position management method, and program

    JP2005251045A

  • Rewriting method for firmware

    JP2005321843A

  • On-vehicle device

    JP2020024579A