JP2000242487A - Device and method for updating program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable the reload of data only to the program block of an updating object when updating the data of a program block at one part of program data composed of plural program blocks stored in a flash memory. SOLUTION: Concerning the flash memory storing plural program blocks 41-45 for realizing each of functions A-E, the operating system(OS) data of the function D are updated, for example. In this case, before erasing the data of the fourth memory block 54, one part 46 of OS data of the function C and the data of one part 47 in the OS data of the function E stored in the fourth memory block 54 are temporarily saved in a personal computer 6 together with the OS data of the function D and after the data of the fourth memory block 54 are erased, saved data 46 and 47 are written at the original positions of the fourth memory block 54 together with new OS data 48 of the function D.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a plurality of memory blocks, each of which is stored in a so-called flash memory (ROM) which is electrically erasable and writable in units of memory blocks. Control device for updating a part of program data of program data, particularly a program controller (hereinafter referred to as a PC) system introduced in an industrial process for controlling a PC system The present invention relates to an update process of basic software called an operating system (hereinafter referred to as an OS) of a special unit for realizing a unit, a network function, a positioning device, and the like.

[0002]

2. Description of the Related Art In general, in a PC system introduced in an industrial process, program data of an OS of a control unit or a special unit is composed of a plurality of program blocks and stored in a flash memory in each unit.

FIG. 19 is an external view showing the configuration of a conventional PC system for writing an OS in a flash memory in a special unit. In the illustrated example, a power supply unit 11 for supplying power to the entire PC system, a control unit 12 for controlling the entire PC system, and a special unit 1 for realizing special functions such as a network function and a positioning function.
3 and OS for control unit 12 and special unit 13
Are connected to each other via an external bus (not shown) built in the base unit 15. The OS data for the special unit is stored in the memory card 16, and the memory card 16 is mounted on the OS download device 14.

FIG. 20 is a block diagram showing a configuration of a system for performing an OS write process. Special unit 13
Is connected to a CPU 131 which is a central processing unit composed of a microcomputer, a flash memory 132 for storing an OS, a two-port memory 133 used for data exchange with the control unit 12, and an external bus 151 in the base unit 15. Interface (I /
F) which is an external bus interface.

[0005] CPU 131, flash memory 132,
Two-port memory 133 and external bus interface 1
34 are connected to each other via an internal bus 135. On the other hand, the OS download device 14 includes a CPU 141 as a central processing unit composed of a microcomputer, a ROM 142 storing software for operating the OS download device 14, and an external bus interface 143 for connecting to the external bus 151. I have. C
PU 141, ROM 142, external bus interface 1
43 and the memory card 16 mounted on the OS download device 14 are interconnected via an internal bus 145.

When the power of the PC system is switched from off to on while the memory card 16 is mounted on the OS download device 14, the special unit 13 is turned on.
OS write processing is started for the special unit 1
OS data for the external bus 1 from the memory card 16
51, the flash memory 1 in the special unit 13
32 to be written.

The power supply unit 11 and the control unit 1
2 and the OS download device 14 are connected to the base unit 15, and the memory card storing the OS data for the control unit is attached to the OS download device 14.
When the power of the C system is switched from off to on, the OS is written into the control unit 12.

FIG. 21 is a schematic diagram for explaining a data structure of an OS and a conventional memory map of a flash memory storing the data structure. The data structure 20 of the OS of the special unit or the control unit includes functions A, B, C,
.., Consisting of a plurality of program blocks 21, 22, 23, and 24 for executing a plurality of functions called a function n, which are collectively written to the flash memory 25.

The memory space of the flash memory 25 is composed of a plurality of program blocks 26, 27, 28, 29 according to the program size of each function. Although the flash memory is a read-only memory, it is a storage medium composed of a plurality of memory blocks and erasable and writable in units of the memory blocks. However, since the plurality of program blocks 26, 27, 28, and 29 are not allocated in consideration of the memory blocks of the flash memory 25, they cannot be divided independently of each other.

That is, for example, like the conventional memory map of the flash memory schematically shown in FIG. 22, the OS data of the function C is stored in the third memory block 33 (memory block 3 in the figure) and the fourth memory block. Memory block 3
4 (memory block 4 in the figure),
The OS data of the function D is further allocated to the fourth memory block 34, and the OS data of the function E is stored in the remaining part of the fourth memory block 34 and the fifth memory block 35 (memory block 5 in the figure). May be assigned to

In FIG. 22, the OS data of the function A and the OS data of the function B are respectively stored in the first memory block 31 (memory block 1 in the figure) and the second memory block 32 (memory block in the figure). Assigned to 2).

[0012]

SUMMARY OF THE INVENTION A flash memory is
This is a configuration in which data can be written by adding a procedure for exchanging OS data in block units to the system. Therefore, a memory in which data cannot be written again to the area unless the written data is erased is used. is there. Therefore, the data is erased only in units of memory blocks. Therefore, for example, in the example of FIG. 22, the function D, the function A, the function C, and the function E are not rewritten, and the function D is not rewritten.
OS data 36 alone as a new version of data 3
In order to rewrite the data to 7, the OS data 37 of the new function D must be written after erasing the storage contents of the fourth memory block 34 to which the program block of the function D is allocated.

However, at this time, with the erasure of the fourth memory block 34, a part 3
8 (the memory area designated as "function C1" in FIG. 22) and a part 39 of the OS data of the function E (memory area designated as "function E1" in FIG. 22) are also lost. It is difficult to update the OS data alone, and it is necessary to rewrite the entire OS after all, and there is a problem that it takes time to update the data due to an OS version upgrade or the like.

Conventionally, even when updating the OS data of some program blocks, the entire OS is rewritten, so that the data of the entire OS is required. Therefore, when the data size of the entire OS is large, a plurality of memories are required. It is necessary to store the data separately on the card, which not only increases the cost but also complicates the handling and rewriting operation of the OS. On the other hand, if data of two or more different program blocks is not mixed in each memory block of the flash memory, it is possible to rewrite only the upgraded program block when updating the OS data of some program blocks. .

However, in this case, for example, referring to the example of FIG. 22, the OS data of the function C is stored in the third memory block 33 and the fourth memory block 34.
The OS data of the function D is allocated to the fifth memory block 35, and the OS data of the function E is allocated to the sixth memory block (not shown).
Then, the remaining portion of the fourth memory block 34, the remaining portion of the fifth memory block 35, and the sixth
The remaining storage area of the second memory block becomes a free area, and a useless memory area that is not used for storing data increases. Therefore, there is a disadvantage that a flash memory having a large storage capacity must be used.

Conventionally, the OS download device 14 must be prepared as a dedicated device for writing the OS, and the handling method differs depending on the model of the OS download device, so that the user may be confused.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problem. In updating data of a part of program data of a plurality of program blocks stored in a flash memory, the update is performed. An object of the present invention is to provide a program updating device and an updating method that can rewrite data only for a target program block.

Further, according to the present invention, in updating data of some program blocks of the program data composed of a plurality of program blocks stored in the flash memory, the update can be performed by obtaining only the difference data. It is an object to obtain a program updating device and an updating method.

Further, according to the present invention, when program data is written to a flash memory, a dedicated device is not used.
It is an object of the present invention to obtain a program updating apparatus and an updating method that can easily perform writing with a unified operation.

[0020]

FIG. 1 is a schematic diagram schematically showing the principle of the present invention. The present invention, as shown in FIG. 1, includes a plurality of functions, for example, function A, function B, function C,
For example, when updating the OS data of the function D in the flash memory storing a plurality of program blocks 41, 42, 43, 44, 45 for realizing the functions D and E, the fourth memory block Before erasing the data of the function 54, the OS of the function C stored in the fourth memory block 54 together with the OS data of the function D
Data of a part 46 of the data (memory area designated as “function C1” in FIG. 1) and a part 47 of the OS data of function E (memory area designated as “function E1” in FIG. 1) are stored in another storage medium. For example, after temporarily evacuating to the work memory of the personal computer 6 or a hard disk, floppy disk, or magneto-optical disk connected to the personal computer 6, erasing the data in the fourth memory block 54, the new function D The save data 46 and 47 are written to the original position of the fourth memory block 54 together with the OS data 48 of the fourth embodiment.

FIG. 1 shows an example in which a program block 44 storing original OS data of a function D and an OS of a new function D are stored.
This is the case when the size of the program block storing the data 48 is the same. The personal computer 6 is one of peripheral devices that execute OS installation software.

Further, according to the present invention, as shown in the principle diagram of FIG. 2, for example, the OS data of the function B stored in the flash memory is stored in an OS having a program size larger than the size of the second memory block 52. When updating to data, it is necessary to shift the allocation positions of the program blocks 43, 44 and 45 storing the respective OS data of the functions C, D and E. , Temporarily saved to another storage medium, for example, a work memory of the personal computer 6, a hard disk, a floppy disk, or a magneto-optical disk connected to the personal computer 6, and then each of the second to fifth memories After erasing the data of the blocks 52, 53, 54 and 55, the OS of the new function B The saved data 43 along with the over data 49,
44 and 45 are sequentially written from the second memory block 52.

In FIG. 1 and FIG. 2, a "function information block" is provided in the first memory block 51, which will be described later.

FIG. 3 is a schematic diagram for explaining a data structure of an OS according to the present invention and a memory map of a flash memory storing the data structure. The data structure 120 of the OS is as follows:
A plurality of program blocks 12 for executing a plurality of functions such as function A, function B, function C,.
1, 122, 123, and 124, and can be independently written into the flash memory 125, or can be collectively written as before.

The memory space of the flash memory 125 is divided into a plurality of program blocks 126, 127, 128, and 129 according to the program size of each function, whether partially or collectively. Conventionally, as described with reference to FIG. 21, each program block (reference numerals 26, 27, 28, 2 in FIG. 21) is used.
9) is not splittable.

The present invention also relates to a flash memory 125
The data structure of each function A, B,
Along with the OS data group 131 of C and n, each function A, B,
Management table 13 in which information 134 about C and n is aggregated
3 is included. Information 134 about each function A, B, C, n
Is composed of, for example, a function identifier (function No.), a start address of a memory area in which OS data of the function is stored, a data size, and other additional information. According to the management table 133, each function A, B,
It is possible to confirm the size and the start address of the OS data of C, D, and n.

The present invention also relates to a flash memory 125
As shown in FIG. 5, the OS data structure 120 written into the OS includes actual OS data 136 and function information 137 corresponding to the information 134 on the function. Therefore, the function information 137 includes, for example, a function identifier (function No.) and its actual data 136.
Is stored at the start address of the memory area of the flash memory 125, the data size, and other additional information. The actual data 136 is stored in the OS of a certain function.
If the data is to be updated, the function information 137
Is the start address value of the OS data of the corresponding function in the flash memory 125 before the update.

According to the function information 137, each function A,
The OS data of B, C, D, and n are stored in the flash memory 125.
To which memory block it belongs, or whether it actually belongs.

As described above, according to the present invention, the present invention is composed of a plurality of memory blocks, and is stored in a ROM capable of collectively erasing and writing in units of memory blocks.
An apparatus for updating a part of program blocks of program data composed of a plurality of program blocks, the storage medium being capable of arbitrarily writing and reading data, and a part or all of old program blocks to be updated. Stored in the same memory block,
Copying means for copying program data other than the update target to the storage medium; storage contents of a memory block in the ROM including at least a part or all of an old program block to be updated; ROM
Erasing means for erasing the storage contents of a memory block including at least a part of the program data to be copied to the storage medium, and storing the program block data newly written in the ROM in the storage medium. And writing means for writing the copied data in the ROM.

According to the present invention, a part of program data of a plurality of program blocks, which is stored in a ROM composed of a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks, is updated. Device, the non-update target program data stored in the same memory block together with part or all of the old program block to be updated is copied to a storage medium on which data can be freely written and read. After that, the storage contents of the memory block including at least a part or all of the old program block to be updated in the ROM and the copy target to the storage medium in the ROM In the memory block containing at least a part of the program data There is erased, and newly wherein R
The data of the program block to be written to the OM is written to the ROM together with the copy data stored in the storage medium.

Further, according to the present invention, a part of program data of a plurality of program blocks stored in a ROM comprising a plurality of memory blocks and capable of being collectively erased and written in memory block units is updated. A storage medium in which data can be arbitrarily written and read and a program block having a larger data size than an old program block to be updated can cause a shift in a storage position in the ROM. Copy means for copying program data other than the update target to the storage medium, and storage contents of a memory block in the ROM including at least a part or all of the old program block to be updated, and The program in the ROM that has been copied to the storage medium And erasing means for erasing the storage contents of the memory block containing at least in part over data, the data of the program block to be written to the new the ROM, together with the stored copy data in the storage medium ROM
Writing means for writing to

According to the present invention, a part of program data of a plurality of program blocks, which is stored in a ROM composed of a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks, is updated. The program data other than the update target may be arbitrarily written and read by a device that performs update of a program block having a data size larger than that of the old program block to be updated. Is copied to a storage medium capable of storing the old program block to be updated, and the storage contents of a memory block including at least a part or all of the old program block to be updated;
The storage contents of the memory block including at least a part of the program data to be copied to the storage medium in the OM are erased, and the data of the program block newly written in the ROM is stored in the storage medium. The data is written into the ROM together with the copied data.

In the present invention, the ROM also stores a starting address of a storage location of each of the program blocks and a data size of each.

According to the present invention, the head address of the storage location of each program block and the data size of each are also stored in the ROM.

In the present invention, the writing means includes:
In addition to the program block data to be newly written in the ROM, the head address and the data size of the storage location of the data in the ROM are written.

According to this invention, the head address and the data size of the storage location of the data in the ROM are written into the ROM along with the data of the program block to be newly written in the ROM.

Further, the present invention is an apparatus for writing program data comprising a plurality of program blocks to a ROM comprising a plurality of memory blocks and capable of collectively erasing and writing in units of memory blocks, Along with the data of each program block,
The head address and the data size of the storage location of each data in the OM are written.

According to the present invention, each program is written by a device for writing program data consisting of a plurality of program blocks to a ROM consisting of a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks. Along with the block data, a start address and a data size of a storage location of each data in the ROM are also written.

According to the present invention, a part of program data of a plurality of program blocks, which is stored in a ROM composed of a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks, is updated. In doing so, the program data other than the update target, which is stored in the same memory block together with part or all of the old program block to be updated, is copied to a storage medium in which data can be arbitrarily written and read. The copying step, the storage contents of the memory block including at least a part or all of the old program block to be updated in the ROM, and the copy target to the storage medium in the ROM Store the contents of the memory block that contains the program data at least in part. An erasing step of removed by, newly the RO
Writing the data of the program block to be written into M together with the copy data stored in the storage medium into the ROM.

According to the present invention, a part of program data of a plurality of program blocks, which is stored in a ROM composed of a plurality of memory blocks and capable of being collectively erased and written in memory block units, is updated. In doing so, the program data other than the update target stored in the same memory block together with part or all of the old program block to be updated is copied to a storage medium on which data can be written and read arbitrarily. Then, the storage contents of a memory block including at least a part or all of the old program block to be updated in the ROM, and the program to be copied to the storage medium in the ROM Erase the memory contents of the memory block containing data at least partially And, and the data of the program block to be written to the new the ROM, writes with the stored copy data in the storage medium in the ROM.

Further, according to the present invention, a part of program data of a plurality of program blocks stored in a ROM composed of a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks is updated. In doing so, it is possible to arbitrarily write and read program data other than the update target, which may cause a shift in the storage position in the ROM due to the update of the program block having a data size larger than the old program block to be updated. A copying step of copying to a possible storage medium, storage contents of a memory block in the ROM including at least a part or all of an old program block to be updated, and the ROM
An erasing step of erasing storage contents of a memory block including at least a part of program data to be copied to the storage medium, and storing the program block data newly written in the ROM in the storage medium. And writing the data to the ROM together with the copied data.

According to the present invention, a part of program data of a plurality of program blocks, which is stored in a ROM composed of a plurality of memory blocks and capable of being collectively erased and written in memory block units, is updated. In doing so, the program data that is stored in the same memory block together with part or all of the old program block to be updated, is not the update target, or has a larger data size than the old program block to be updated. The program data other than the update target may be copied to a storage medium in which the data can be written and read arbitrarily.
In the ROM, the storage contents of a memory block including at least a part or all of the old program block to be updated and the program data in the ROM to be copied to the storage medium are at least stored. The contents of a memory block included in a part of the program are erased, and data of a program block to be newly written to the ROM is written to the ROM together with copy data stored in the storage medium.

Further, according to the present invention, when writing program data consisting of a plurality of program blocks into a ROM comprising a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks, Together with the data of RO
And a step of writing a start address and a data size of the storage location of each of the data in M.

According to the present invention, when writing program data consisting of a plurality of program blocks to a ROM consisting of a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks, Together with the data of R
The head address and data size of the storage location of each data in the OM are written.

[0045]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of a program updating apparatus and a program updating method according to the present invention will be described in detail with reference to the drawings.

Embodiment 1 FIG. 6 is an external view showing a configuration of a PC system for writing an OS in a flash memory in a control unit according to the first embodiment of the present invention. The power supply unit 71, the control unit 72, and the special unit 73 are mutually connected via an external bus (not shown) in the base unit 75. Peripheral device on which OS installation software operates, for example,
The personal computer 6 is connected via a communication cable 60 to, for example, a communication port 76 provided in the control unit 72.

The personal computer 6 has built-in storage devices such as a floppy disk device, a hard disk device, a magneto-optical disk device, and a tape device, or is connected to these storage devices (not shown). By executing OS installation software stored on a floppy disk, a hard disk, or a magneto-optical disk, for example, an OS for a control unit stored on a floppy disk is sent to the control unit 72 via the communication cable 60 to perform installation. Therefore, the personal computer 6 has a function as a program updating device. This personal computer 6
After the installation of S is completed, it is removed together with the communication cable 60.

When the OS is installed in the control unit 72, the special unit 73 is not always necessary.
Note that the power supply unit 71, the control unit 72, the special unit 73, and the base unit 75 are the same units as those in the related art, and a description thereof will be omitted.

FIG. 7 is a block diagram showing the configuration of a system for performing an OS write process on the control unit 72. The control unit 72 includes a CPU 721 as a central processing unit including a microcomputer, a flash memory 722 for storing an OS, the communication port 76,
RAM (random access memory) 723 for providing a work memory or the like, and an external bus interface 724 for connecting to an external bus 751 in the base unit 75
It has.

CPU 721, flash memory 722,
The communication port 76, the RAM 723, and the external bus interface 724 are mutually connected via an internal bus 725. On the other hand, the personal computer 6 includes a CPU 61 as a central processing unit, a ROM 62, a RAM 63, and a communication port 64, which are mutually connected via an internal bus 65. The communication port 64 is a port for connecting the communication cable 60 connected to the control unit 72. Although not shown, the floppy disk storing the OS for the control unit is connected to the internal bus 65 of the personal computer 6 via a floppy disk device not shown.

FIG. 8 is a schematic diagram showing the data structure of the flash memory 722. The flash memory 722 is
OS data for executing a plurality of functions such as function A, function B, function C,..., Function n are divided for each function into a plurality of program blocks 701, 702, 703,
704.

The flash memory 722 has, for example, a management table in which information (hereinafter referred to as function information) 707 relating to functions A, B, C, and n is collected at the head of the program blocks 701, 702, 703, and 704. 7
A function information block 705 (which may be referred to as a function O) 705 for storing the information 06 is provided. Function information block 705
Is fixed, and the data size of the function information block 705 is fixed.

The function information 707 includes, for example, a function identifier (function No.) 707a, a function name 707b composed of 16 words, etc., and an installation source floppy disk number (FD) when OS data of the function is installed. No.) 707c, a version 707d of the OS data of the function, a date 707e when the OS data of the function was installed, a start address 707f of a memory area storing the OS data of the function, and a data size 707g. . Function information block 70
5 is, for example, a function No. Is set to “0”.

FIG. 9 shows an OS installed in a flash memory 722 from a floppy disk for updating.
It is a schematic diagram which shows the data structure of data. In the illustrated example, the data of the new function B is illustrated, but the same applies to other functions.

The OS data of the new function B (hereinafter, referred to as new data) is actual data (hereinafter, referred to as new actual data) 711.
And function information (hereinafter referred to as new function information) 712 corresponding to the function information 707. That is, the new function information 712 includes, for example, a function identifier (function No.) 7
A function name 712b composed of 12a, 16 words, etc.
It is composed of a floppy disk number (FD No.) 712c, version 712d, installation date 712e, installation start address 712f, and data size 712g.

Next, a process of updating the OS data to the operating control unit 72 will be described with reference to FIG. In the figure, reference numeral 6a denotes OS installation software (S / S) executed on the personal computer 6.
W) shows a processing step, and 72a shows a processing step of software (S / W) executed by the control unit 72.

The personal computer 6 is connected to the control unit 72 in normal operation via the communication cable 60, and a floppy disk or the like storing new data of a predetermined data configuration (see FIG. 9) is connected to the personal computer 6. When the personal computer 6 is attached and starts updating OS data to the control unit 72, first, the personal computer 6
The OS is sent to the control unit 72 via the communication cable 60.
Notify the start of the data writing process (step A
1).

Upon receiving the notification, the control unit 72 stops the control and the system, and saves the system data as a preparation process for writing the OS data. Then, the control unit 72 responds to the personal computer 6 with a result indicating that the OS writing process can be executed (step B1). When receiving the result, the personal computer 6 notifies the control unit 72 of information such as the data size of the new real data 711 of the new data and the address of the storage location of the new real data 711 in the flash memory 722. (Step A2). Hereinafter, this notification is referred to as a save OS function information read request.

When the control unit 72 receives the save OS function information read request, the start address 712 f of the new real data 711 and its data size 712 g and the start address in the function information 707 already stored in the flash memory 722 are obtained. 707f and data size 707g
Is calculated for each function to calculate the start address and data size of OS data (hereinafter referred to as “save data”) of a function that requires data saving,
The head address and data size of the save data are returned to the personal computer 6 (step B2).

When the personal computer 6 receives the head address and the size of the save data, it notifies the control unit 72 of a request to read the save data based on the received address and the size of the save data. Is saved as a file on the hard disk, for example, to save the data (step A3).

In response to step A3, the control unit 7
2 reads the save data from the flash memory 722 and sends it to the personal computer 6 (step B3). Subsequently, the personal computer 6 notifies the control unit 72 of a request to delete the memory block in the flash memory 722 in which the saved data is stored, and receives a deletion completion result in response to the request from the control unit 72 (step A4). In response to Step A4, the control unit 72 deletes the corresponding memory block (Step B4).

Subsequently, the personal computer 6 rearranges the saved data saved on the hard disk and the new real data 711 in the ascending order of the addresses, and until all the rearranged data is written to the flash memory 722.
The write data is output to the sequential control unit 72 in units of memory blocks together with the OS write execution request, and when all writing is completed, a write completion result and an OS verification execution request are received from the control unit 72 (step A5). In response to step A5, control unit 72 writes data to flash memory 722 (step B5).

Subsequently, the personal computer 6 notifies the control unit 72 of a request for reading the data actually written in the flash memory 722, receives the data sent from the control unit 72 in response thereto, and The data actually written in 722 is compared with the correct data, and their consistency is checked (step A6). That is, the flash memory 72
A check is made as to whether the data has been correctly written to the second. In response to Step A6, the control unit 72 reads the actually written data from the flash memory 722 (Step B6).

If the data has not been correctly written to the flash memory 722, the corresponding memory block is deleted, the corresponding data is written and collated until the correct data is written. Flash memory 722
Is written correctly, the personal computer 6 notifies the control unit 72 that the writing has been completed, and receives a notification of the completion of the writing end process from the control unit 72 in response thereto (step A7). In response to step A7, the control unit 72 performs a return of system data or the like as OS data write termination processing (step B7).

Upon receiving the write completion processing completion notification, the personal computer 6 notifies the control unit 72 of a remote reset request, receives a reset completion notification from the control unit 72 in response thereto, and ends the OS data update processing. (Step A8). Step A8
, The control unit 72 resets the entire PC system, starts up the updated OS data, and starts control of the PC system (step B8).

While the data is being deleted (step B4) or the data is being written (step B5) to the flash memory 722, the OS program in the flash memory 722 cannot be executed.

Therefore, in this embodiment, as shown in FIGS. 11 and 12, when accessing the flash memory 722, the flash memory 722 is stored in the flash memory write processing block 722a or the flash memory deletion processing block 722b. The copied program is copied to a work memory (RAM 723). The flash memory writing processing block 722a and the flash memory deletion processing block 722b store programs for performing data writing processing and memory block erasing processing with respect to the flash memory 722, respectively.

The processing copied to the work memory (RAM 723) is executed in the work memory, and performs writing and deletion processing on the flash memory 722. Then, after the processing of writing and deletion is completed, the execution of the program is returned to the original state.

In FIG. 11, 725a and 725b
Constitutes an internal bus 725, which is a data bus and an address bus, respectively.

According to the first embodiment, the flash memory 722 stores the start address 707 of the memory area storing the OS data of each function together with the OS data of each function.
function information 70 including f and its data size 707g
7, the program data composed of a plurality of program blocks 701, 702, 703, and 704 can be divided and written into the control unit 72 for each program block. Since the start address and the data size of the storage location of the new real data 711 in the flash memory 722 are updated at the same time as the update, the data can be rewritten only for the program block to be updated.

Therefore, according to the first embodiment, only the difference data needs to be obtained at the time of updating the program data.
The updating process can be completed in a short time, and the problem of cost when storing new data for updating on a plurality of floppy disks, for example, and the complexity of handling and updating processes can be eliminated. According to the first embodiment, since the personal computer 6 is connected to the control unit 72 and the personal computer 6 is operated to update data, a dedicated OS download device is not required.

Embodiment 2 Next, the flash memory 73 in the special unit 73 according to the second embodiment of the present invention.
1 will be described. The PC system for writing the OS in the flash memory 731 in the special unit 73 has the same configuration as that shown in FIG. That is, the power supply unit 71, the control unit 72, and the special unit 73 are connected to each other via an external bus (not shown) in the base unit 75.
Are connected to the communication port 76 of the control unit 72 via the communication cable 60, for example.

FIG. 13 shows that the special unit 73
FIG. 2 is a block diagram illustrating a configuration of a system that performs a writing process of FIG. The special unit 73 includes a CPU 731 as a central processing unit including a microcomputer, a flash memory 732 for storing an OS, a two-port memory 733 used for data exchange with the control unit 72, and an external bus 751 in the base unit 75. An external bus interface 734 is provided for connection with the external bus. CP
U731, flash memory 732, 2-port memory 7
The external bus interface 33 and the external bus interface 734 are connected to each other via an internal bus 735. Power supply unit 71,
The description of the control unit 72 and the personal computer 6 will be omitted because they are the same as in the first embodiment.

The data structure of the flash memory 732 and the data structure of the OS data installed in the flash memory 732 from the floppy disk for updating are the data structure of the flash memory 722 of the first embodiment (see FIG. 8). ), And the data configuration of OS data installed from the floppy disk to the flash memory 722 for updating (see FIG. 9).

Next, a description will be given, with reference to FIG. 14, of an OS data update process for the operating special unit 73. In the figure, reference numeral 6b denotes OS installation software (S / S) executed on the personal computer 6.
W) shows a processing step, and 72b shows a software (S / W) processing step executed by the control unit 72.
3b is software (S) executed by the special unit 73.
/ W).

The personal computer 6 is connected to the control unit 72 in normal operation via the communication cable 60, and a floppy disk or the like storing new data of a predetermined data configuration (see FIG. 9) is connected to the personal computer 6. When the personal computer 6 is attached and starts updating the OS data to the special unit 73, first, the personal computer 6
The OS is sent to the control unit 72 via the communication cable 60.
Notify the start of the data writing process (step C
1).

Upon receiving the notification, the control unit 72 relays the notification to the special unit 73,
The control and system are stopped, and system data is saved as a preparation process for writing OS data (step D1). The special unit 73 is
Upon receiving the notification of the start of writing the S data, the system data is saved as a preparation process for writing the OS data, and the result that the OS writing process can be executed is returned to the personal computer via the control unit 72. 6 (step E1).

Upon receiving the result, the personal computer 6 receives information (such as the data size of the new real data 711 of the new data and the address of the storage location of the new real data 711 in the flash memory 732 (the save OS function). An information reading request is notified to the control unit 72 (step C2). The control unit 72 relays the save OS function information read request to the special unit 73 (step D2).

Upon receiving the save OS function information read request, the special unit 73 receives the start address 712 f of the new real data 711 and its data size 712 g and the start address in the function information 707 already stored in the flash memory 732. 707f and data size 707g
Is compared for each function to calculate the head address and data size of the save data, and respond to the personal computer 6 via the control unit 72 with the head address and data size of the save data (step E2).

When the personal computer 6 receives the head address and the size of the save data, it notifies the control unit 72 of a request to read the save data based on the received address and the size of the save data. Data is saved by storing it as a file on the hard disk (step C3). The control unit 72 issues a request to read the save data to the special unit 7.
3 and the saved data to the personal computer 6 (step D3). In response to Step C3, the special unit 73
2, and reads the saved data from the control unit 72.
(Step E)
3).

Subsequently, the personal computer 6 notifies the control unit 72 of a request to delete the memory block in the flash memory 732 in which the saved data is stored.
Receive the deletion completion result in response (Step C
4). The control unit 72 sends the deletion request to the special unit 7
3 and the deletion completion result to the personal computer 6 (step D4). Step C4
, The special unit 73 deletes the corresponding memory block (step E4).

Subsequently, the personal computer 6 rearranges the saved data saved on the hard disk and the new real data 711 in the ascending order of the address, and until all the rearranged data is written to the flash memory 732.
The write data is output to the sequential control unit 72 in units of memory blocks together with the OS write execution request, and when all writing is completed, a write completion result and an OS verification execution request are received (step C5). The control unit 72 relays the OS write execution request and the write data to the special unit 73, and transmits the write completion result and the OS collation execution request to the personal computer 6.
(Step D5). In response to Step C5, the special unit 73 writes data to the flash memory 732 (Step E5).

Subsequently, the personal computer 6 notifies the control unit 72 of a read request for data actually written in the flash memory 732, receives the data transmitted in response thereto, and
2 is compared with the data actually written to correct data, and their consistency is checked (step C6). The control unit 72 relays the data read request to the special unit 73, and relays the read data to the personal computer 6 in response to the request (step D6).

In response to step C6, the special unit 7
3 reads the actually written data from the flash memory 732 and sends it to the personal computer 6 via the control unit 72 (step E6). If the data has not been correctly written to the flash memory 732, the corresponding memory block is deleted, and the corresponding data is written and collated until the correct data is written.

When the data has been correctly written to the flash memory 732, the personal computer 6 notifies the control unit 72 that the writing has been completed, and receives a notification of the completion of the writing end process in response thereto (step C7). The control unit 72 relays the write completion notification to the special unit 73, performs system data restoration as OS data write completion processing, and relays the write completion processing completion notification to the personal computer 6 (step D7). . In response to Step C7, the special unit 73 performs a return of system data or the like as OS data write end processing (Step E7).

When the personal computer 6 receives the write completion processing completion notification, it notifies the control unit 72 of a remote reset request. In response, the personal computer 6 receives a reset completion notification from the control unit 72 and ends the OS data update processing. (Step C8). Step C8
, The control unit 72 resets the entire PC system, starts updated OS data, and starts control of the PC system (step D8).

The method of executing the OS program while data is deleted (step E4) or data is written (step E5) in the flash memory 732 is described in the first embodiment with reference to FIG.
And the method described in connection with FIG.

According to the second embodiment, when installing program data in the special unit 73 or updating data of some of the program blocks, as in the first embodiment, each program block Data can be divided and written, and data can be rewritten only to the program block to be updated. Therefore, the effects of shortening the update processing time, reducing the cost, and facilitating the update processing can be obtained. .

According to the second embodiment, since the personal computer 6 is connected to the control unit 72 and the personal computer 6 is operated to update the data of the special unit 73, a dedicated OS download device is not required. Thus, even when the data of the special unit 73 is updated or when the data of the control unit 72 is updated, the operations can be performed by a unified operation.

As shown in FIG. 15, network units 77a and 77b are respectively attached to external buses of a plurality of base units 75a and 75b, and these network units 77a and 77b are connected to each other by a network cable 60a. To build a PC system network, and one base unit 7
The personal computer 6 serving as a program updating device is connected to the control unit 72 attached to the control unit 5a via the communication cable 60, and the other base unit 75
The program data may be updated for the special unit 73 to which the “b” is attached.

In this case, the exchange of data and the like between the personal computer 6 and the special unit 73 is performed by the communication cable 60, the control unit 72, and the base unit 75.
a, the network unit 77a, the network cable 60a, the network unit 77b, and the base unit 75b. Also, by transmitting the write data of the OS to the plurality of control units 72 and the special units 73 in the form of a command, the OSs can be simultaneously transmitted to the plurality of control units 72 and the special units 73.
Data writing can be performed.

Further, a serial number for managing a user license is stored in a floppy disk used for writing new OS data, and when a new OS data is to be written to the flash memories 722 and 732, the serial number is stored. The number of the floppy disk used for writing and the floppy disk number 707 in the function information 707 stored in the flash memories 722 and 732
The collation with c may be performed on the personal computer 6. Then, the user license of the program can be managed, and illegal installation can be prevented.

A version management table 100 for managing the compatibility of the versions of the functions of the units 72 and 73 with respect to the PC system as shown in FIG. 16 is provided in the OS installation software of the personal computer 6. Flash memory 722,
When attempting to write new OS data to the 732, the function information 70 stored in the flash memories 722 and 732
7 is compared with the version of the corresponding function of the corresponding unit 72 or 73 in the version management table 100 by the personal computer 6.
The above may be performed. Then, a version of the OS compatible with the PC system can be easily installed.

FIGS. 17 and 18 show the processing procedures of the personal computer 6 and the units 72 and 73 whose data is to be updated in this case.

When the update process of the OS data is started, the personal computer 6 first reads the management table 706 stored in the flash memories 722 and 732 of each unit 72 and 73, and sends the OS version to each unit 72 and 73. Is recognized (step S1), and it is checked against the version of the version management table 100 of each unit 72, 73 to check the consistency, and the rewritable O is checked.
The version of S is recognized (step S2). If the versions are consistent, an OS rewrite command (including OS data) is issued to the update target units 72 and 73 (step S3). If the versions are not consistent, the user is notified of the version mismatch. Then (step S4), for example, the user may be prompted to rewrite a different version of the OS.

On the other hand, the units 72 and 73 to be updated are:
When an OS rewrite command including OS data is received (step S11), the data in the flash memories 722 and 732 in the units 72 and 73 is rewritten (step S12).

[0097]

As described above, according to the present invention, according to the present invention, program data consisting of a plurality of memory blocks, and a plurality of program blocks stored in a ROM capable of being collectively erased and written in memory block units. By means of an apparatus for updating some program blocks, program data other than those to be updated, stored in the same memory block together with some or all of old program blocks to be updated, can be arbitrarily written and written. Copied to a readable storage medium, and then stored in a memory block including at least a part or all of an old program block to be updated in the ROM; and At least part of the program data copied to the storage medium is included The contents of the memory block are erased, and the data of the program block newly written in the ROM is written in the ROM together with the copy data stored in the storage medium. Can be rewritten, so that only the difference data for updating needs to be obtained.

According to the next invention, a part of the program data of the program data consisting of a plurality of memory blocks and stored in a ROM which can be collectively erased and written in units of memory blocks is used. By the device to be updated, the update of a program block having a larger data size than the old program block to be updated may cause a shift in the storage position in the ROM.
The contents of a memory block which is copied to a storage medium from which data can be written and read arbitrarily, and then contains at least a part or all of an old program block to be updated in the ROM, and The storage contents of a memory block including at least a part of the program data to be copied to the storage medium in the ROM are erased, and data of a program block newly written to the ROM is stored in the storage medium. Since the data is written into the ROM together with the copied data, the data can be rewritten only for the program block to be updated. Therefore, only the difference data for updating needs to be obtained.

According to the next invention, a general-purpose personal computer can be used as the program updating device, so that program data can be easily updated by a unified operation without using a dedicated device.

According to the next invention, the head address of the storage location of each of the program blocks and the respective data size are also stored in the ROM, so that the data size of the program block to be updated and the head of the storage location are stored. Since the address can be confirmed, data can be rewritten only in the program block to be updated.

According to the next invention, the head address and the data size of the storage location of the data in the ROM are written in the ROM together with the data of the program block to be newly written in the ROM.
Along with updating the data, the head address and data size of the storage location of the data can be updated.

According to the next invention, each device for writing program data comprising a plurality of program blocks to a ROM comprising a plurality of memory blocks and capable of collectively erasing and writing in units of memory blocks, Since the start address and the data size of the storage location of each data in the ROM are written together with the data of the program block, the program data composed of a plurality of program blocks can be divided and written for each program block.

According to the next invention, a part of the program data of a plurality of program blocks, which is stored in a ROM composed of a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks, is used. When updating, the program data other than the update target, which is stored in the same memory block together with part or all of the old program block to be updated, is copied to a storage medium on which data can be written and read arbitrarily. After that, the storage contents of the memory block including at least a part or all of the old program block to be updated in the ROM and the copy target to the storage medium in the ROM Store the contents of the memory block that contains the program data at least in part. Then, since the data of the program block to be newly written to the ROM is written to the ROM together with the copy data stored in the storage medium, the data can be rewritten only to the program block to be updated. .

According to the next invention, a part of the program data of a plurality of program blocks, which is stored in a ROM composed of a plurality of memory blocks and capable of being collectively erased and written in memory block units, is used. In updating, arbitrarily writing and reading of program data other than the update target, which may cause a shift in the storage position in the ROM due to the update of a program block having a data size larger than the old program block to be updated. And the storage contents of a memory block including at least a part or all of an old program block to be updated in the ROM, and the ROM
Of the memory block including at least a portion of the program data to be copied to the storage medium, and erasing the storage contents of the memory block, and newly writing the program block data to the ROM, storing the program data in the storage medium. Since the data is written in the ROM together with the copy data, the data can be rewritten only for the program block to be updated.

According to the next invention, when writing program data comprising a plurality of program blocks to a ROM comprising a plurality of memory blocks and capable of being collectively erased and written in units of memory blocks, Since the start address and the data size of the storage location of each data in the ROM are written together with the block data, the program data including a plurality of program blocks can be divided and written for each program block.

[Brief description of the drawings]

FIG. 1 is a schematic diagram schematically showing the principle of the present invention.

FIG. 2 is a schematic diagram schematically showing the principle of the present invention.

FIG. 3 is a schematic diagram for explaining a correspondence relationship between a data configuration of an OS according to the present invention and a memory map of a flash memory.

FIG. 4 is a schematic diagram showing an example of a data configuration of a flash memory according to the present invention.

FIG. 5 is a schematic diagram illustrating an example of a data configuration of an OS according to the present invention.

FIG. 6 shows a P for writing an OS to the flash memory.
1 is an external view illustrating a configuration of a first embodiment of a C system.

FIG. 7 is a block diagram illustrating a configuration of a system that performs a writing process of the OS.

FIG. 8 is a schematic diagram illustrating a data configuration of the flash memory according to the first embodiment;

FIG. 9 is a schematic diagram illustrating a data configuration of OS data according to the first embodiment;

FIG. 10 is a flowchart illustrating a flow of an OS data update process according to the first embodiment;

FIG. 11 is a schematic diagram for explaining a method of performing a data write process and a memory block erase process on a flash memory.

FIG. 12 is a schematic diagram for explaining a method of performing a data write process and a memory block erase process on a flash memory.

FIG. 13 is a block diagram illustrating a configuration of a system that performs an OS write process on a flash memory according to a second embodiment;

FIG. 14 is a flowchart illustrating a flow of an OS data update process according to the second embodiment;

FIG. 15 is an external view showing a configuration example when a network of a PC system is used.

FIG. 16 is a table showing an example of a version management table in OS installation software configured to check version consistency.

FIG. 17 is a flowchart illustrating a processing procedure of OS installation software configured to check version consistency;

FIG. 18 is a flowchart illustrating a processing procedure of an update target unit when checking version consistency.

FIG. 19 is an external view showing a configuration of a conventional PC system for writing an OS in a flash memory.

FIG. 20 is a block diagram illustrating a configuration of a system that performs the OS writing process.

FIG. 21 is a schematic diagram for explaining a data configuration of an OS and a conventional memory map of a flash memory storing the data configuration.

FIG. 22 is a schematic diagram showing a conventional memory map of a flash memory storing OS data.

[Explanation of symbols]

6. Personal computer (program updating apparatus including storage medium, copying means, erasing means and writing means), 51, 52, 53, 54, 55 memory blocks 41, 42, 43, 44, 45 program blocks, 722, 732 flash Memory (ROM capable of batch erasing and writing).

Claims (8)

[Claims] 1. An R comprising a plurality of memory blocks and capable of batch erasing and writing in units of memory blocks.
An apparatus for updating a part of program data of a plurality of program blocks stored in an OM, comprising: a storage medium on which data can be arbitrarily written and read; and an old program block to be updated Copying means for copying program data other than the update target stored in the same memory block together with part or all of the above to the storage medium; and a part of the old program block to be updated in the ROM Or erasing means for erasing the storage content of a memory block including at least a part of all the memory block, and erasing the storage content of a memory block including at least a part of program data to be copied to the storage medium in the ROM, The program block data newly written to the ROM is stored in the storage medium. Writing means for writing the copied data together with the copied data into the ROM. 2. An R comprising a plurality of memory blocks and capable of batch erasing and writing in units of memory blocks.
An apparatus for updating a part of program data of a plurality of program blocks stored in an OM, comprising: a storage medium on which data can be arbitrarily written and read; and an old program block to be updated By updating a program block with a larger data size than the RO
A copy unit that copies program data other than the update target, which may cause a shift in the storage position in M, to the storage medium; and at least one part or all of the old program block to be updated in the ROM. Erasing means for erasing the storage content of the memory block included in the memory section and the storage content of the memory block at least partially including the program data to be copied to the storage medium in the ROM; Writing means for writing the data of the program block to be written to the ROM together with the copy data stored in the storage medium. 3. The ROM according to claim 1, wherein the ROM stores a start address of a storage location of each of the program blocks and a data size of each of the program blocks.
A program updating device according to claim 1. 4. The ROM according to claim 4, wherein the writing unit newly stores the ROM.
4. The program updating apparatus according to claim 3, wherein a start address and a data size of a storage location of the data in the ROM are written together with data of a program block to be written in the ROM. 5. An R comprising a plurality of memory blocks and capable of batch erasing and writing in units of memory blocks.
An apparatus for writing program data including a plurality of program blocks to an OM, comprising writing a start address and a data size of a storage location of each of the data in the ROM along with data of each of the program blocks. Program updating device. 6. An R comprising a plurality of memory blocks and capable of collectively erasing and writing in units of memory blocks.
When updating some program blocks of the program data composed of a plurality of program blocks stored in the OM, the update stored in the same memory block together with some or all of the old program blocks to be updated A copying step of copying program data other than the target to a storage medium on which data can be arbitrarily written and read; and at least a part or all of the old program block to be updated in the ROM An erasing step of erasing the storage contents of the memory block and the storage contents of the memory block at least partially including the program data to be copied to the storage medium in the ROM; and a program block to be newly written to the ROM. And the copy data stored in the storage medium. Program update method characterized by including: a writing step of writing to said ROM also. 7. An R comprising a plurality of memory blocks and capable of batch erasing and writing in units of memory blocks.
When updating a part of program data of a plurality of program blocks stored in the OM, the program block having a larger data size than the old program block to be updated is updated by updating the RO.
A copy step of copying program data other than the update target, which may cause a shift in the storage position in M, to a storage medium that can arbitrarily write and read the data, and an old program to be updated in the ROM Erasing the storage contents of the memory block including at least a part or all of the block and the storage contents of the memory block including at least a part of the program data to be copied to the storage medium in the ROM A program updating method, comprising: an erasing step; and a writing step of writing data of a program block newly written in the ROM to the ROM together with copy data stored in the storage medium. 8. An R comprising a plurality of memory blocks and capable of batch erasing and writing in units of memory blocks.
When writing program data composed of a plurality of program blocks to the OM, the method includes a step of writing, together with the data of each program block, a start address and a data size of a storage location of each data in the ROM. How to update the program.