JP6401070B2 - Software rewriting device - Google Patents

Description

  The present invention relates to a software rewriting apparatus for writing software in a memory.

  In recent years, it has become common to operate devices with embedded systems. In such an embedded system, when the control software is updated, new software is written in a memory such as a flash ROM. Further, in such software writing, it is also checked whether or not the software has been written normally. For example, it is determined whether a value is written at the beginning and whether a normal value is written at the end.

  As a related technique, there is known a technique that makes it possible to recognize the end of a file when a system down or the like occurs during data writing and the end processing is not properly performed (for example, patents). Reference 1).

JP-A-6-236307

  In the conventional software rewriting, when the end address is fixed, the capacity of the software to be written can be changed, so that the assumed maximum address is used as the end address. In such a case, at the time of software writing, data is written in all areas up to the fixed end address, so there is a problem that it takes a very long time to write software. For example, if the built-in system is a welding power source and the operator has to rewrite the software of 100 welding power sources, the rewriting time per unit is increased by 1 minute, and the overall work time It will be 1 hour and 40 minutes long. Therefore, there has been a demand for shortening the software writing time as much as possible.

  In addition, when software writing is inappropriate, devices such as a welding power source that operates by executing the software may perform unexpected operations, so software writing is performed normally. There was also a request to judge whether or not.

  The present invention has been made to solve the above-described problem, and provides a software rewriting device capable of reducing the time for writing software to the memory and determining whether the software has been written normally. The purpose is to do.

To achieve the above object, a software rewriting apparatus according to the present invention includes a memory in which software is stored, a reception unit that receives software to be written to the memory, a recording unit that writes software received by the reception unit into the memory, And a determination unit that determines whether the writing of software by the recording unit is normal. The recording unit writes a predetermined value at the end of the software to be written in the memory, and uses an address of the predetermined value. A certain end address is written to a specific address in the memory, and the determination unit determines that when the data at the specific address is an address within the range of the memory and the data at the end address indicated by the data is a predetermined value, It is determined that the software writing is normal. .
With such a configuration, since it is not necessary to write data up to a fixed end address, the time required for software writing can be shortened. Further, by determining whether or not the software has been normally written, for example, the software can be executed only when the software has been normally written. In the determination, in order to determine whether the data at a specific address is an address within the memory range, for example, when the data is an address outside the memory range, By trying to read data, the possibility that an execution unit such as a CPU malfunctions can be reduced.

Further, in the software rewriting device according to the present invention, the determination unit has data written at the start address of the memory, the data at the specific address is an address within the range of the memory, and the data at the end address indicated by the data is When the value is determined in advance, it may be determined that the software writing is normal.
With such a configuration, since it is also determined whether or not data is written at the start address of the memory, a more strict determination can be made.

In the software rewriting apparatus according to the present invention, the recording unit writes the end address to a plurality of specific addresses in the memory, and the determination unit writes the software incorrectly when the data of the plurality of specific addresses do not match. You may judge.
With such a configuration, it is possible to make redundant the location where the end address is written, and to make a more strict determination.

Further, in the software rewriting device according to the present invention, the predetermined value is written to a plurality of consecutive addresses at the end of the software to be written in the memory, and the determination unit includes a continuous address including the end address. If the data at the plurality of addresses is not a predetermined value, it may be determined that the software writing is not normal.
With such a configuration, it becomes possible to make a predetermined value corresponding to the end address longer data, and it is possible to reduce the possibility that the predetermined value coincides with other data by chance. it can.

Moreover, in the software rewriting apparatus according to the present invention, the software may be software related to the control of the welding power source.
With such a configuration, when rewriting the software of the welding power source, it is possible to reduce the time required for writing the software and to determine whether the software has been normally written. And, for example, the safety of the welding power source can be improved by executing the rewritten software only when it is normally written.

  According to the software rewriting apparatus of the present invention, the time required for software writing can be shortened. Further, in order to determine whether or not the software has been normally written, for example, the software can be executed only when the software has been normally written.

The block diagram which shows the structure of the welding power supply containing the software rewriting apparatus by embodiment of this invention Flowchart showing the operation of the welding power source according to the embodiment Flowchart showing the operation of the welding power source according to the embodiment The figure which shows an example of the address map in the embodiment The figure which shows an example of the address map in the embodiment The figure which shows an example of the address map in the embodiment The figure which shows an example of the address map in the embodiment The figure for demonstrating the writing of the software in the embodiment

  Hereinafter, a software rewriting apparatus according to the present invention will be described using embodiments. In the following embodiments, components and steps denoted by the same reference numerals are the same or equivalent, and repetitive description may be omitted. The software rewriting apparatus according to the present embodiment rewrites software stored in a memory.

  FIG. 1 is a block diagram showing a configuration of a welding power source 1 according to the present embodiment. A welding power source 1 according to the present embodiment is a device that supplies electric power for performing welding such as arc welding, and includes a software rewriting device 2, a power source 11, and an execution unit 12. The software rewriting device 2 includes a memory 21, a reception unit 22, a recording unit 23, and a determination unit 24.

  In the memory 21, software (program) is stored. The software is software related to the control of the welding power source 1. The welding power source 1 operates in accordance with the software, so that welding control and processing are executed. The memory 21 may be, for example, a flash ROM (flash memory), another non-volatile semiconductor memory, or another non-volatile recording medium. In the present embodiment, the case where the memory 21 is a flash ROM will be mainly described.

  The accepting unit 22 accepts software to be written to the memory 21. The accepting unit 22 may accept, for example, software read from a predetermined recording medium (for example, an optical disk, a magnetic disk, a semiconductor memory such as a USB memory), and is transmitted via a wired or wireless communication line. Software may be received. The receiving unit 22 may or may not include a device for receiving (for example, a modem or a network card). The receiving unit 22 may be realized by hardware, or may be realized by software such as a driver that drives a predetermined device.

  The recording unit 23 writes the software received by the receiving unit 22 in the memory 21. In the writing of the software, the recording unit 23 writes a predetermined value at the end of the software to be written in the memory 21, and the end address that is the address of the predetermined value becomes a specific address in the memory 21. Shall be written. For example, as shown in the address map of FIG. 4A, the software to be written is written in the area other than the specific address 0x00000050 from the start address 0x00000000 to the address 0x000FFFFB immediately before the end address, and the end address 0x000FFFFC The predetermined value 0x12345678 may be written, and the end address 0x000FFFFC may be written to the specific address 0x00000050. The specific address is usually one of addresses from the beginning to the end in the area of the memory 21 where the software is written, as shown in FIG. 4A, but this need not be the case. The specific address is preferably a fixed value. The predetermined value written to the end address may be a fixed value such as 0x12345678, a checksum of the software to be written, or any other value. Also good. Therefore, “predetermined” may be determined at the time of designing or assembling the apparatus or the like, or may be determined at the time of writing the software. The specific address may be stored in a recording medium (not shown). Also, when the predetermined value is a fixed value, the value may be stored in a recording medium (not shown). If the predetermined value is a checksum or the like, a rule or the like for determining the value may be stored in a recording medium (not shown). Then, the recording unit 23 may acquire a specific address or the like by accessing the recording medium. The recording unit 23 may erase the data in the memory 21 before writing software or the like. The erasure may be performed on the entire memory 21 or not. In the latter case, for example, the recording unit 23 may read a terminal address stored at a specific address and erase data from the head address to the terminal address, or may be related to software to be written. Data up to the end address may be erased. In the former case, currently stored data relating to the software is erased, and in the latter case, data in a range where the software to be written is written is erased. When the memory 21 is a recording medium that erases data in units of blocks in erasing the data, the recording unit 23 may perform erasure processing on all blocks including the data to be erased. Good.

  The determination unit 24 determines whether the software writing by the recording unit 23 is normal. The determination unit 24 writes data at the head address in the area where the software to be written is stored, and the data at the specific address is an address within the range of the memory 21 and is indicated by the data. When the end address data to be read is a predetermined value, it is determined that the software writing is normal. Therefore, the determination unit 24 may determine that the software writing is not normal, for example, when data is not written at the head address in the area where the software to be written is stored. For example, the determination unit 24 may determine that the software writing is not normal when the data at a specific address is not an address within the range of the memory 21. For example, the determination unit 24 may determine that the software writing is not normal when the data at the end address indicated by the data at the specific address is not a predetermined value.

  In the determination, the determination unit 24 determines whether the data at the specific address is an address within the range of the memory 21 before determining whether the data at the end address is a predetermined value. It is preferable to do. If the data at the specific address is not within the range of the memory 21, the determination unit 24 does not need to read the data at the end address that is the data at the specific address. By doing so, for example, when software writing is not normally completed and data at a specific address indicates outside the address range of the memory 21, data outside the range is mistakenly displayed. Reading can be avoided, and malfunction can be prevented.

  Further, the head address in the area where the software to be written is stored may be the head address of the memory 21. In that case, whether or not data is written at the head address in the area where the software to be written is stored is determined whether or not data is written at the head address of the memory 21. In the present embodiment, the case where the head address in the area where the software to be written is stored is the head address of the memory 21 will be mainly described.

  Further, as described above, when data is written to the memory 21 such as a flash ROM, the data is first erased before writing. Therefore, the determination unit 24 determines that data is written at the address when the data at the head address in the area where the software to be written is stored is not erased data (for example, 0xFFFFFFFF). Also good. In addition, when it is determined that a predetermined value is written at the head address in the area where the software to be written is stored, the determination unit 24 sets the data at the head address in the area where the software to be written is stored. Instead of determining whether or not is written, it may be determined whether or not a predetermined value is written to the address.

  Further, the timing of determination by the determination unit 24 does not matter, but for example, the determination may be performed at the timing when the welding power source 1 is started after writing the software, or the determination may be performed after writing the software. Since there is a possibility that the data in the memory 21 is erroneously rewritten during the operation of the welding power source 1, the determination unit 24 may make the determination every time the welding power source 1 is activated (when the power is turned on). . In this embodiment, this case will be mainly described.

The power source 11 is a power source for supplying electric power necessary for welding. The power supply 11 normally supplies a high voltage and a high current for arc welding or the like.
The execution unit 12 reads and executes the software stored in the memory 21 when the determination result by the determination unit 24 indicates that the software has been normally written. The execution unit 12 may be a CPU or an MPU, for example. Since the software is software related to the control of the welding power source 1, the software is executed so that the control related to the power source 11 is performed.

  Note that the determination unit 24 may be realized, for example, by hardware, or may be realized by executing software. In the latter case, the CPU or the like that executes the software may or may not be the same as the CPU or the like that implements the execution unit 12.

Next, operation | movement of the welding power supply 1 is demonstrated using the flowchart of FIG. The flowchart of FIG. 2 is a flowchart showing processing from when the power source of the welding power source 1 is turned on to when the power source is turned off.
(Step S101) The determination unit 24 determines whether the software stored in the memory 21 has been normally written after the power is turned on. Details of the determination process will be described later with reference to the flowchart of FIG.

  (Step S102) The execution unit 12 determines whether or not the result of determination in step S101 indicates that the software has been written normally. If the determination result indicates that the software has been written normally, the process proceeds to step S103. If not, the activation of the welding power source 1 is terminated and the power is turned off.

  (Step S103) The execution unit 12 reads and executes the software stored in the memory 21. As a result, the welding power source 1 operates as a device that supplies electric power for welding.

  (Step S104) The execution unit 12 determines whether or not the welding power source 1 has received an input such as an instruction from the outside. If accepted, the process proceeds to step S105, and if not, the process proceeds to step S106. The input may be performed by a user, for example, or may be performed by a control device of a welding robot.

  (Step S105) The execution unit 12 performs processing according to the accepted input. Then, the process returns to step S104. The processing may be, for example, controlling the power supply 11 so as to output voltage and current in accordance with the input instruction.

  (Step S106) The accepting unit 22 determines whether software to be rewritten has been accepted. If accepted, the process proceeds to step S107, and if not, the process proceeds to step S108.

  (Step S107) As shown in FIG. 5, the recording unit 23 adds predetermined termination data to the end of the received software, and also adds an address of the termination data to a specific address. The data to be recorded to which the end address is added is configured, and the data to be recorded is written into the memory 21. Note that the software data 1 and 2 in FIG. 5 are data obtained by dividing the received software data. When the writing is completed, the execution unit 12 restarts the welding power source 1. Then, the process returns to step S101.

  (Step S108) The execution part 12 judges whether the process of the welding power supply 1 is complete | finished. And when a process is complete | finished, the power supply of the welding power supply 1 is turned off. On the other hand, if the process is not terminated, the process returns to step S104. Note that the execution unit 12 may determine that the process is to be ended when, for example, an instruction to turn off the welding power source 1 is received from the user, or a predetermined error or the like occurs and the process is continued. When it becomes impossible, it may be determined that the processing is to be ended.

FIG. 3 is a flowchart showing details of the determination process (step S101) in the flowchart of FIG.
(Step S <b> 201) The determination unit 24 determines whether data is written at the top address of the memory 21. If it is written, the process proceeds to step S202. If not, the process proceeds to step S205.

  (Step S <b> 202) The determination unit 24 reads data stored at a specific address, and determines whether the data is within the address range of the memory 21. If the data is within the address range of the memory 21, the process proceeds to step S203, and if not, the process proceeds to step S205.

  (Step S203) The determination unit 24 reads the termination data stored at the termination address indicated by the data stored at the specific address, and determines whether the termination data is a predetermined value. If the end data is a predetermined value, the process proceeds to step S204. If not, the process proceeds to step S205.

  (Step S <b> 204) The determination unit 24 determines that software writing to the memory 21 is normal. And it returns to the flowchart of FIG.

(Step S205) The determination unit 24 determines that the software writing to the memory 21 is not normal. And it returns to the flowchart of FIG.
Note that the order of processing in the flowchart of FIG. 2 is an example, and if the processing in step S202 is performed before the processing in step S203 and the same result can be obtained, the order of the steps is changed. May be.

  Next, operation | movement of the welding power supply 1 by this Embodiment is demonstrated using a specific example. In this specific example, it is assumed that the specific address is 0x00000050 and the predetermined value (termination data) is 0x12345678. The address range of the memory 21 is assumed to be 0x00000000 to 0x00200000.

  Assume that an operator who rewrites software attaches a USB memory in which new software is recorded to the welding power source 1 while the welding power source 1 is operating. Then, the reception unit 22 detects this, reads the software from the USB memory, and passes it to the recording unit 23 (step S106). When the recording unit 23 receives the software, as shown in FIG. 5, the recording unit 23 secures a predetermined storage area at a specific address position, and adds the end data 0x12345678 to the end of the software data. Then, the data to be recorded is configured by adding the end address which is the address of the end data to the position of the specific address. The recording unit 23 erases all data corresponding to each address in the memory 21 before writing the data to be recorded in the memory 21. Specifically, all the data is set to 0xFFFFFFFF. Thereafter, the recording unit 23 writes data to be recorded in order from the top address of the memory 21. As a result, it is assumed that the relationship between the data written in the memory 21 and the address is as shown in FIG. 4A (step S107).

  Next, the execution unit 12 restarts the welding power source 1. At the time of the restart, the determination unit 24 determines whether the software has been normally written (step S101). Specifically, the determination unit 24 determines whether the data of the start address 0x00000000 of the memory 21 is 0xFFFFFFFF (step S201). In this case, since it is 0x469500CD and not 0xFFFFFFFF, data is written at the head address. Therefore, the determination unit 24 reads the data 0x000FFFFC stored at the specific address 0x00000050, and determines whether it is within the address range of the memory 21 (step S202). In this case, since the data 0x000FFFFC is included in the address range 0x00000000 to 0x00200000, the data at a specific address is within the address range of the memory 21. Therefore, the determination unit 24 reads the data 0x12345678 of the end address 0x000FFFFC and determines whether the data is a predetermined value 0x12345678 (step S203). In this case, since the read data is a predetermined value, the end address data is a predetermined value. Therefore, the determination unit 24 determines that the software has been written normally, and passes the determination result to the execution unit 12 (step S204). Then, the execution unit 12 executes the software written in the memory 21, and as a result, processing for supplying power for welding is performed in the welding power source 1 (steps S103 to S105).

  For example, when the data of the start address 0x00000000 is 0xFFFFFFFF, the end address stored in the specific address is out of the address range of the memory 21 (out of the range of 0x00000000 to 0x00200000), or the end data is 0x12345678. If the data is other than (for example, 0x23456789), the determination unit 24 determines that the software rewriting has not been performed normally (step S205). In that case, for example, it is considered that some trouble such as a power failure occurs during rewriting of software.

  As described above, according to the software rewriting device 2 according to the present embodiment, when rewriting software, it is only necessary to write data from the start address to the end address. Therefore, compared to the case where the end address is fixed, Write time is shortened. Also, only when it is determined that the software has been written normally, by executing the software, the software that has been written normally is executed, and the welding power source 1 operates appropriately. Become. Further, in the determination, after confirming whether or not the end address which is the data of the specific address is an address within the range of the memory 21, the software is appropriately written in order to read the data of the end address. Even if the end address is an address outside the range of the memory 21, it is possible to prevent malfunction. In addition, since the end address written in the specific address can be used to check whether the end process for storing a predetermined value at the end of the software has been properly performed, as described above, the end address is It does not have to be fixed. In Patent Document 1, an identification code is added to each record so that the end of the file can be recognized. However, the software rewriting apparatus 2 according to the present embodiment adds such an identification code. Since there is no need, more data can be written into the memory 21.

  In the present embodiment, the case where there is one specific address in which the termination address is stored has been described, but this need not be the case. The recording unit 23 may write the end address to a plurality of specific addresses in the memory 21. The number of the specific addresses is not limited, but may be two or three, for example. In this case, for example, as shown in FIG. 4B, end addresses may be written in the first specific address 0x00000050 and the second specific address 0x00000200. As described above, when the termination address is written to a plurality of specific addresses, for example, the determination unit 24, for example, has the data (terminal addresses) of the plurality of specific addresses all match and is written. Data is written at the head address in the area where the target software is stored, the data at the specific address is an address within the range of the memory 21, and the data at the end address indicated by the data is When the value is determined in advance, it may be determined that the software writing is normal. That is, the determination unit 24 may determine that the software writing is not normal when the data of the plurality of specific addresses do not match. The case where the data of a plurality of specific addresses do not match may be the case where at least some of the data of the plurality of specific addresses do not match. Specifically, among the first to third data stored in the first to third specific addresses, respectively, the first data and the second data match, but the first data and If the data does not match the third data, the determination unit 24 may determine that the software writing is not normal.

  Further, in the present embodiment, the case where the end data, which is a predetermined value, is stored in the area corresponding to one address, that is, the case where the end data is 4 bytes has been described in the above specific example. It does n’t have to be. The end data may be written to a plurality of consecutive addresses at the end of the software to be written in the memory 21. That is, the end data may have a data amount exceeding 4 bytes. In that case, for example, as shown in FIG. 4C, data 0x12345678 and 0x9ABCDEF0 of the end address 0x000FFFFC and the next address 0x000FFFFD may be predetermined values (end data). That is, the termination data may be 8-byte data, for example. By increasing the data amount of the end data, it is possible to reduce the possibility that the data corresponding to the end address coincides with a predetermined value accidentally when the software is not written normally. As described above, when the predetermined value is written to a plurality of continuous addresses at the end of the software to be written in the memory 21, the determination unit 24 determines whether the software to be written is, for example, Data is written at the head address in the area to be stored, the data at a specific address is an address within the range of the memory 21, and a plurality of continuous addresses including the end address indicated by the data If the data at the address is a predetermined value, it may be determined that the software writing is normal. In other words, the determination unit 24 determines that the software writing is not normal when the data of a plurality of consecutive addresses including the end address stored in the specific address is not a predetermined value. Good.

  Although FIG. 4C shows the case where the head addresses of a plurality of consecutive addresses, which are the addresses of the termination data, are stored at specific addresses, this need not be the case. For example, the rear end addresses of a plurality of consecutive addresses that are end data addresses may be stored in a specific address, and may be the start address or the rear end address of a plurality of consecutive addresses that are end data addresses. No address may be stored at a specific address.

  Further, in the present embodiment, a case has been described in which the determination unit 24 determines whether or not data is written at the head address in the area in which the software to be written is stored. The determination unit 24 may not perform the determination. In this case, the determination unit 24, for example, when the data at a specific address is an address within the range of the memory 21 and the terminal address data indicated by the data is a predetermined value, It may be determined that the software writing is normal.

  In the present embodiment, it is determined whether or not the software has been written normally after the software has been written. If the software has been written normally, the software to be written is stored in another area of the memory 21. May be. The software stored in the other area is used as a backup. Therefore, for example, when the software is subsequently rewritten, if the software cannot be written normally, the software stored in the backup area can be used. It is possible to avoid a situation where the operation stops. After that, when the software is normally rewritten, the software in the backup area is also rewritten so as to have the same contents as the software after the rewriting. For example, as shown in FIG. 4D, when the determination unit 24 determines that a series of software has been normally written from addresses 0x00000000 to 0x000FFFFC, the recording unit 23 stores the software in the memory 21 as a backup of the software. It shall also be written in the area. In the software backup area, the end address in the backup area may be written at a specific address or not. In the latter case, the end address of the backup area may be stored in an area different from the backup area. In order to be able to specify the backup area, the start address of the backup area may be fixed, or the start address may be stored in an area other than the backup area. Further, the backup of software written normally may be written on a recording medium different from the memory 21.

  Moreover, although the case where the software rewriting apparatus 2 was included in the welding power supply 1 was demonstrated in this Embodiment, it may not be so. The software rewriting device 2 may be included in an embedded device other than the welding power source 1. Even in such a case, it is preferable that the device including the software rewriting device 2 executes the software written in the memory 21 when the determination unit 24 determines that the software rewriting has been normally performed. is there. The execution of the software is usually performed for the control and operation of the device including the software rewriting device 2.

  In the above embodiment, each process or each function may be realized by centralized processing by a single device or a single system, or may be distributedly processed by a plurality of devices or a plurality of systems. It may be realized by doing.

  In the above embodiment, the information exchange between the components is performed by one component when, for example, the two components that exchange the information are physically different from each other. It may be performed by outputting information and receiving information by the other component, or when two components that exchange information are physically the same, one component May be performed by moving from the phase of the process corresponding to to the phase of the process corresponding to the other component.

  In the above embodiment, information related to processing executed by each component, for example, information received, acquired, selected, generated, transmitted, or received by each component In addition, information such as threshold values, mathematical formulas, addresses, and the like used by each constituent element in processing may be temporarily or for a long time held in a recording medium (not shown), even if not specified in the above description. Further, the storage of information on the recording medium (not shown) may be performed by each component or a storage unit (not shown). Further, reading of information from the recording medium (not shown) may be performed by each component or a reading unit (not shown).

  In the above embodiment, when information used by each component, for example, information such as a threshold value, an address, and various setting values used by each component may be changed by the user, Even if it is not specified in the description, the user may be able to change the information as appropriate, or may not be so. If the information can be changed by the user, the change is realized by, for example, a not-shown receiving unit that receives a change instruction from the user and a changing unit (not shown) that changes the information in accordance with the change instruction. May be. The change instruction received by the receiving unit (not shown) may be received from an input device, information received via a communication line, or information read from a predetermined recording medium, for example. .

  In the above-described embodiment, each component may be configured by dedicated hardware, or a component that can be realized by software may be realized by executing a program. For example, each component can be realized by a program execution unit such as a CPU reading and executing a software program recorded on a recording medium such as a hard disk or a semiconductor memory. At the time of execution, the program execution unit may execute the program while accessing the storage unit or the recording medium. The program may be executed by being downloaded from a server or the like, or may be executed by reading a program recorded on a predetermined recording medium (for example, an optical disk, a magnetic disk, a semiconductor memory, or the like). Good. Further, this program may be used as a program constituting a program product. Further, the computer that executes the program may be singular or plural. That is, centralized processing may be performed, or distributed processing may be performed.

  Further, the present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these are also included in the scope of the present invention.

  As described above, according to the software rewriting apparatus of the present invention, the effect of speeding up the rewriting of software stored in the memory can be obtained, which is useful as an apparatus for rewriting software used in an embedded system, for example.

DESCRIPTION OF SYMBOLS 1 Welding power supply 2 Software rewriting apparatus 11 Power supply 12 Execution part 21 Memory 22 Reception part 23 Recording part 24 Judgment part

Claims (3)

A memory for storing software;
A reception unit for receiving software to be written to the memory;
A recording unit for writing the software received by the receiving unit into the memory;
A determination unit that determines whether writing of software by the recording unit is normal,
The recording unit writes a predetermined value at the end of the software to be written in the memory, writes a terminal address that is an address of the predetermined value to a plurality of specific addresses in the memory,
The determination unit determines that the software writing is normal when the data at the specific address is an address within the range of the memory and the data at the end address indicated by the data is a predetermined value. A software rewriting device that determines and determines that software writing is not normal when the data at the plurality of specific addresses do not match . The determination unit has data written at the start address of the memory, the data at the specific address is an address within the range of the memory, and the end address data indicated by the data is a predetermined value. 2. The software rewriting apparatus according to claim 1, wherein the software rewriting apparatus determines that the software writing is normal. The software is a software related to the control of the welding power source, the software rewriting apparatus according to claim 1 or claim 2, wherein.

Images