JP2012230529A - Remote maintenance system of fpga loaded device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a remote maintenance system of FPGA loaded devices for performing FPGA rewrite of a plurality of FPGA loaded devices connected with one another via a network without installing an exclusive management device.SOLUTION: Each FPGA loaded device 100 has master/slave setting means 11 and FPGA rewrite means 12 in its FPGA 1, any of n (n≥2) FPGA loaded devices 100 connected via a network 10 can be a master device, and all slave devices can be made to execute FPGA rewrite from a maintenance terminal 200-2 connected to the master device. Thus, cost reduction and simplification of a system can be contrived, an influence to be given to original data transfer on the network 10 is suppressed, and data transfer is stably performed since it is unnecessary to install an exclusive management device 300.

Description

  The present invention relates to a remote maintenance system for an FPGA-mounted device capable of remotely performing an FPGA rewrite maintenance work for a plurality of FPGA-mounted devices connected via a network.

  As a system for a device equipped with an FPGA (Field Programmable Gate Array) (hereinafter referred to as an FPGA-equipped device), in Patent Document 1, a plurality of FPGA-equipped devices and a management device are connected via a network to develop / operate the FPGA. / Something to do maintenance is presented. In this example, the management apparatus is connected to a development terminal, an operation terminal, and a maintenance terminal as accessible terminals via a network, and an FPGA existing on the network at the time of development, operation, and maintenance of the FPGA-mounted apparatus. It is possible to provide FPGA data to the FPGA of the on-board device and confirm the operation status of the FPGA.

JP 2001-306343 A

  As described above, in a system for a conventional FPGA-equipped device, a dedicated management device that operates and maintains the FPGA of the FPGA-equipped device is provided on the network, which increases the cost of the system. There was a problem. Further, it has affected the original data transfer on the network, causing a delay in data transfer.

  In addition, when data transfer is realized by directly connecting the FPGA of the FPGA-equipped device to the network interface, it is necessary to initialize the FPGA after rewriting the FPGA via the network. Was inadvertently initialized, and there was a problem that data transfer was not performed stably.

  The present invention has been made to solve the above-described problems, and performs FPGA rewrite maintenance work of a plurality of FPGA-mounted devices connected via a network without installing a dedicated management device. An object of the present invention is to provide a remote maintenance system for an FPGA-equipped device capable of stably transferring data on a network.

  In the remote maintenance system for an FPGA-equipped device according to the present invention, n (n ≧ 2) FPGA-equipped devices having at least one FPGA, CPU, and memory are connected to each other via a network, and one of them is connected. A remote maintenance system of an FPGA-equipped device that performs rewrite maintenance work on a master device and other (n-1) units as slave devices from a maintenance terminal device connected to the master device to the FPGA of the slave device, The FPGA-installed device includes a network interface that connects the network and the FPGA, a terminal interface that connects the CPU and the maintenance terminal device, and a master / slave that is provided in the FPGA and sets the device as either a master device or a slave device. When the setting unit is provided in the FPGA and the own device is the master device And it has a FPGA rewriting means for executing the rewriting of the FPGA to the own device and the slave device.

  According to the remote maintenance system for FPGA-equipped devices according to the present invention, the FPGA of each FPGA-equipped device has master / slave setting means and FPGA rewriting means, so that n units connected to each other via a network. Any of the (n ≧ 2) FPGA-equipped devices can be the master device, and the maintenance terminal device connected to the master device can rewrite and maintain the FPGA of the slave device. In addition, since it is not necessary to install a dedicated management device, the cost of the system can be reduced and simplified, the influence on the original data transfer on the network can be suppressed, and the data transfer can be performed stably. it can.

It is a figure which shows the structure of the remote maintenance system of the FPGA mounting apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the structure of the remote maintenance system of the conventional FPGA mounting apparatus which is a comparative example of this invention. It is a figure which shows the internal structure of the FPGA mounting apparatus which concerns on Embodiment 1 of this invention. It is a figure which shows the internal structure of the memory mounted in the FPGA mounting apparatus which concerns on Embodiment 2 of this invention. It is a figure which shows the data format example on the network in the remote maintenance system of the FPGA mounting apparatus which concerns on Embodiment 3 of this invention. It is a figure which shows the flow of a process of the master apparatus in the remote maintenance system of the FPGA mounting apparatus which concerns on Embodiment 3 of this invention. It is a figure which shows the flow of a process between the master apparatus and the slave apparatus in the remote maintenance system of the FPGA mounting apparatus which concerns on Embodiment 3 of this invention. It is a figure which shows the internal structure of the FPGA mounting apparatus which concerns on Embodiment 4 of this invention.

Embodiment 1 FIG.
Below, the remote maintenance system of the FPGA mounting apparatus which concerns on Embodiment 1 of this invention is demonstrated based on drawing. FIG. 1 shows a configuration of a remote maintenance system for an FPGA-mounted device according to Embodiment 1 of the present invention. FIG. 2 shows the configuration of a conventional remote maintenance system for FPGA-equipped devices as a comparative example of the present invention. In the drawing, the same and corresponding parts are denoted by the same reference numerals.

  As shown in FIG. 1, the remote maintenance system for an FPGA mounting device according to the first embodiment includes n (n ≧ 2) FPGA mounting devices 100-1, 100-2, 100-3, 100-4, ... 100-n (collectively, the FPGA device 100) are connected via the network 10. Each of these FPGA-equipped devices 100 can be connected to maintenance terminals 200-1, 200-2, 200-3, 200-4,... 200-n (collectively maintenance terminals 200) which are maintenance terminal devices. In FIG. 1, a maintenance terminal 200-2 is connected to the FPGA mounting apparatus 100-2.

  In the remote maintenance system for FPGA-mounted devices according to the first embodiment, any one of n (n ≧ 2) FPGA-mounted devices 100 is used as a master device (in FIG. 1, the FPGA-mounted device 100-2 is used as the master device). The maintenance device 200-2 connected to the master device performs rewriting maintenance work on the FPGA of each slave device with the other (n-1) units as slave devices.

  In FIG. 1, the FPGA mounting apparatus 100-2 is the master apparatus, but any of the FPGA mounting apparatuses 100 can be the master apparatus. By adopting such a system configuration, this system executes FPGA rewriting of all target slave devices without installing the dedicated management device 300 required in the conventional system shown in FIG. Is.

  The internal configuration of each FPGA mounting device 100 according to the first embodiment will be described with reference to FIG. The FPGA-equipped device 100 mainly includes at least one FPGA 1, a CPU 2, a memory 3, a network interface 4 (hereinafter referred to as a network I / F 4), and a terminal interface 5 (hereinafter referred to as a terminal I / F 5). .

  The FPGA 1 is a master / slave setting unit 11 for setting the own device (the FPGA-equipped device 100) as either the master device or the slave device, and when the own device is the master device, the FPGA 1 is rewritten to the own device and the slave device. FPGA rewriting means 12 for executing Specifically, the master / slave setting unit 11 and the FPGA rewriting unit 12 are circuits in which circuits having respective functions are embedded in the FPGA 1.

  The CPU 2 controls the entire FPGA-mounted device 100 and is connected to the FPGA 1 and the memory 3 that stores data for rewriting the FPGA 1. The network I / F 4 connects the network 10 and the FPGA 1, and the terminal I / F 5 connects the CPU 2 and the maintenance terminal 200. As its main operation, the CPU 2 once fetches control transfer data flowing on the network 10 into the FPGA 1 via the network I / F 4, performs data analysis processing, processes the data as necessary, and then returns to the network 10. Sending out.

  Next, the flow of processing at the time of FPGA rewriting will be briefly described with reference to FIGS. 1 and 3 (details will be described in a third embodiment to be described later). The case where the FPGA-equipped device 100-2 is used as a master device will be described as an example. The user can access the master from the master / slave setting screen displayed on the maintenance terminal 200-2 via the terminal I / F 5 and the CPU 2. / Slave setting means 11 is accessed.

  By selecting “master” on the master / slave setting screen, the FPGA-mounted device 100-2 to which the maintenance terminal 200-2 is connected is set as the master device. The other FPGA-equipped devices 100-1, 100-3, 100-4,... 100-n automatically recognize that the FPGA-equipped device 100-2 has become the master device via the network 10, and automatically Therefore, it is not necessary for all the FPGA-equipped devices 100 to set the master / slave.

  The FPGA rewriting means 12 of the FPGA mounting device 100-2 that has become the master device executes the FPGA rewriting of the slave device. Note that since the master device also executes FPGA rewriting of its own device, it can be said that the master device is also a single slave device. When executing the FPGA rewriting of the slave device, the FPGA rewriting means 12 of the master device reads the FPGA rewriting data stored in the memory 3 of the own device, and transmits the data to all the slave devices via the network 10. Thereafter, an instruction to rewrite FPGA 1 is transmitted to each slave device. The CPU 2 of the slave device temporarily stores the received FPGA rewrite data in the memory 3 of the own device. Thereafter, the FPGA 1 of the slave device reads out the FPGA rewrite data from the memory 3 and writes it into the FPGA 1.

  As described above, according to the remote maintenance system for FPGA-mounted devices according to the first embodiment, each FPGA-mounted device 100 has the master / slave setting unit 11 and the FPGA rewriting unit 12 in the FPGA 1. Therefore, any of the n (n ≧ 2) FPGA-equipped devices 100 connected via the network 10 can be the master device, and the slave device FPGA 1 can be connected from the maintenance terminal 200-2 connected to the master device. Can be rewritten and maintained. Thereby, the position of the master device on the network 10 is not limited, and the master device can be easily changed due to a failure of the device or the convenience of a maintenance worker, so that efficient maintenance management can be performed.

  Further, since there is no need to install a dedicated management device 300 (FIG. 2), the cost of the system can be reduced and the simplification can be achieved, and the influence on the original data transfer on the network 10 can be suppressed, and the data transfer can be performed. It can be performed stably.

Embodiment 2. FIG.
The configuration of the remote maintenance system of the FPGA mounting device according to the second embodiment of the present invention and the internal configuration of each FPGA mounting device are the same as those of the first embodiment, so that FIG. 1 and FIG. To do. In the second embodiment, a plurality of data storage areas for storing FPGA rewrite data are provided in the memory 3 mounted on each FPGA mounting device 100, and different FPGA rewrite data is stored in each data storage area. It is what you do.

  FIG. 4 shows an example of the internal configuration of the memory 3 in the second embodiment. In the example shown in FIG. 4, the memory 3 includes at least three data storage areas 3a, 3b, and 3c as data storage areas for storing FPGA rewrite data. FPGA rewrite data 0 is stored in the data storage area 3a. Similarly, FPGA rewrite data 1 is stored in the data storage area 3b, and FPGA rewrite data 2 is stored in the data storage area 3c.

  The FPGA rewriting data 0 is emergency fixed data (initial data) that enables network connection, prepared as a countermeasure when an abnormality occurs in the network or when an abnormality occurs during the FPGA rewriting operation, for example. . Further, the FPGA rewriting data 1 and the FPGA rewriting data 2 are, for example, FPGA data written in the currently operating FPGA 1 (referred to as FPGA data (old)), and for modification and functional improvement. New FPGA data to be rewritten (referred to as FPGA data (new)).

  An operation method of the data storage area 3b and the data storage area 3c will be described. The FPGA rewriting data transmitted from the FPGA device 100-2 as the master device is sent to all the slave devices (FPGA devices 100-1, 100-3, 100-4... 100-n). The CPU 2 of each slave device stores the currently operating FPGA data (old) in the data storage area 3b of the memory 3, and stores the FPGA data (new) captured via the network 10 in the data storage area 3c. . The data storage areas 3b and 3c are operated by using them alternately.

  When the CPU 2 of the slave device executes rewriting of the FPGA 1, the CPU 3 switches the memory 3 to a data storage area corresponding to the FPGA rewriting data designated by the master device. For example, in the example shown in FIG. 4, the data is switched to the data storage area 3c in which the FPGA data (new) is stored as the FPGA rewriting data 2. The FPGA 1 of the slave device reads out the FPGA data (new) stored in the data storage area 3c and writes it into the FPGA 1.

  According to the second embodiment, in addition to the same effects as those of the first embodiment, a plurality of data storage areas 3a, 3b, 3c,... For storing FPGA rewrite data 0, 1, 2,. Thus, either of the FPGA rewriting data 1 and 2 can be immediately written into the FPGA 1 in accordance with an instruction from the master device. As a result, when there is an abnormality in the FPGA data (new), or when an abnormality occurs at the time of FPGA rewriting, it can be restored to the FPGA data (old) by an instruction from the master device.

  Further, when an abnormality occurs in the network 10 or when an abnormality occurs at the time of FPGA rewriting, the CPU 2 in each slave device transfers the FPGA 1 of its own device to the data in the memory 3 without an instruction from the master device. The data can be rewritten to the FPGA rewriting data 0 stored in the storage area 3a. As a result, the FPGA 1 connected to the network 10 can be quickly operated even in an emergency or when an abnormality occurs, and the influence on the network system can be significantly reduced.

Embodiment 3 FIG.
The configuration of the remote maintenance system of the FPGA mounting device according to the third embodiment of the present invention and the internal configuration of each FPGA mounting device are the same as those in the first embodiment, and therefore, description will be given with reference to FIGS. To do. In the third embodiment, as a data frame format of data flowing on the network 10, an FPGA management data frame is defined in addition to a control transfer data frame.

  FIG. 5 shows an example of a data format in the remote maintenance system for the FPGA-mounted device according to the third embodiment. As shown in FIG. 5A, the data frame format according to the third embodiment is a frame for each device data (for device 1 data, for device 2 data,... For device X data) as a control transfer data frame. At the end, a frame for FPGA management data is added. The device 1, the device 2,... The device X correspond to the FPGA-mounted devices 100-1, 100-2,.

  As shown in FIG. 5B, the frame for FPGA management data further includes information for master device (master number) information, slave device information (slave device number and FPGA information), and FPGA data (for FPGA rewriting). Data + CRC) and command type information frames are defined.

  As the command type information, as shown in FIG. 5C, the version information of the FPGA of all devices and the status information are collected as the command 000, the FPGA rewrite data is distributed as the command 001, the FPGA rewrite instruction as the command 011, and the command 111. Are defined as master change.

  Next, the flow of processing when the master device causes the slave device to execute FPGA rewriting using the FPGA management data shown in FIG. 5 will be described. 6 shows a flow of processing in which the FPGA-equipped device 100-2 becomes the master device and causes the slave device to execute FPGA rewriting. FIG. 7 shows the master when the master device starts FPGA rewriting for each slave device. The flow of processing between a device and a slave device is shown. 6 and 7, S1, S2,... Indicate processing steps.

  When an arbitrary FPGA-equipped device 100-2 intends to execute FPGA rewriting of other FPGA-equipped devices 100-1, 100-3, 100-4,... 100-n, the FPGA management of all the FPGA-equipped devices 100 The data is confirmed (S1). Since the FPGA management data shown in FIG. 5 is constantly flowing on the network 10, each FPGA-mounted device 100 knows that its own device is a master or a slave. In addition, version information and the like of the FPGA 1 of all the FPGA mounting devices 100 are also taken in.

  The FPGA-equipped device 100-2 confirms whether the master is other than itself (S2), and if the master is other than itself (S2, Yes), a master declaration notifying other devices that the master is the master is issued. Perform (S3). More specifically, the device number is distributed as the master number by the master change command 111 of the FPGA management data. After that, the slave device numbers and FPGA information of the other FPGA-equipped devices 100-1, 100-3, 100-4,... 100-n are confirmed with the FPGA management data, and all other devices have become slave devices. Confirm (S4). If all the other devices are not slave devices (S4, No), it waits for all to become slave devices.

  When all the other devices are slave devices (S4, Yes), they become the master (S5), and transmit the FPGA management data in which the FPGA rewrite data is placed on the FPGA data frame to all the slave devices (S7). ). At this time, the data is divided and transmitted at least twice, so as not to affect the original control transfer data flowing on the network 10.

  If all the FPGA rewriting data is not divided and transmitted (S7, No), the transmission is continued. When all the FPGA rewrite data is divided and transmitted (S7, Yes), it is confirmed by the FPGA information of each slave device that all the target slave devices have received the FPGA rewrite data and stored in each memory 3. (S8).

  Thereafter, an FPGA rewrite version is designated for all slave devices (S9), and FPGA rewrite is started (S10). Further, it is confirmed whether or not all slave devices have performed a write instruction from the master device. If it has been performed (Yes in S11), the FPGA rewriting is terminated. When not implemented (S11, No), it waits until it confirms that it was implemented. In S2, if the master is himself (S2, No), the processing steps of S3 to S5 are omitted and the process proceeds to S6.

  Next, the flow of processing at the time of FPGA rewrite activation (S10) will be described with reference to FIG. After confirming that all target slave devices have received the data for FPGA rewriting, the master device activates FPGA rewriting for each slave device. Specifically, an FPGA rewrite instruction command 011 designating the slave device number is transmitted to the target slave device, and the FPGA rewrite version is designated. The CPU 2 of the slave device switches the memory 3 to the data storage area corresponding to the FPGA rewrite version designated by the master device (S101).

  Subsequently, the CPU 2 of the slave device resets the own device when the FPGA is rewritten (S102). By this reset, the slave device is disconnected from the network 10, and the master device recognizes that the target slave device is disconnected from the network 10 (S103). Thereafter, the FPGA 1 of the slave device writes the data, and after the configuration is completed (S104), the CPU 2 of the slave device re-enters the network 10 (network disconnection / entry processing).

  The master device recognizes that the target slave device has re-entered the network 10 (S105). After that, a notification of completion of FPGA rewriting is received from the target slave device, the FPGA version is confirmed (S106), and it is recognized as rewriting completion. The master device performs the above-described FPGA rewriting activation individually for all the slave devices to be processed. That is, the network disconnection / entry process of the slave devices is sequentially performed one by one on all the slave devices to be processed.

  According to the third embodiment, in addition to the same effect as the first embodiment, an FPGA management data frame is defined in addition to a control transfer data frame as a data frame format of data flowing on the network 10. Therefore, it is possible to realize a network system in which the influence on the transfer of the original control transfer data is smaller and the data transfer can be performed stably.

  In addition, since the master device performs the FPGA rewrite activation (instruction) individually for all the slave devices that are targeted, the slave device is always disconnected from the network 10 at any one time. The FPGA rewriting of all the FPGA-equipped devices 100 can be sequentially executed while minimizing the influence on the transfer of the control transfer data.

Embodiment 4 FIG.
The configuration of the remote maintenance system for the FPGA-mounted device according to the fourth embodiment of the present invention is the same as that of the first embodiment, and will be described with reference to FIG. FIG. 8 shows an internal configuration of the FPGA mounting apparatus 100 according to the fourth embodiment. 8 that are the same as or equivalent to those in FIG. 3 are assigned the same reference numerals, and descriptions thereof are omitted.

  Each FPGA-equipped device 100 according to the fourth embodiment includes two FPGA 1-1 and FPGA 1-2 in which different FPGA data is written, and a network I / F 4 among these two FPGA 1-1 and 1-2. A changeover switch 6 for selecting a connected FPGA is provided. That is, the FPGA 1-1 and the FPGA 1-2 are connected to the network 10 via the changeover switch 6 and the network I / F 4. In addition, in FIG. 8, although it was set as the structure which has two FPGA1-1 and FPGA1-2, two or more FPGAs may be sufficient.

  In these two FPGA 1-1 and FPGA 1-2, for example, the FPGA data (old) stored in the data storage area 3b of the memory 3 in the second embodiment (see FIG. 4) and the data storage area 3c are stored. FPGA data (new) is written. The CPU 2 of the slave device operates the changeover switch 6 in response to the FPGA rewrite instruction from the master device, and connects the FPGA 1-1 (or FPGA 1-2) corresponding to the FPGA data designated by the master device to the network I / F 4. To do.

  In the remote maintenance system for an FPGA-mounted device according to the fourth embodiment, the flow of processing when the master device causes the slave device to execute FPGA rewriting will be described. The FPGA-equipped device 100 that is a slave device receives two types of FPGA data (old and new) from the master device via the network 10, and each of them receives data storage areas 3b and 3c that are predetermined areas of the memory 3 (FIG. 4). ) Once. Thereafter, the CPU 2 writes the FPGA data (old) in the FPGA 1-1 and the FPGA data (new) in the FPGA 1-2.

  Thereafter, in response to the FPGA rewrite instruction from the master device, the CPU 2 operates the changeover switch 6 so that the FPGA 1-1 (or FPGA 1-2) in which the FPGA data corresponding to the instruction is written is connected to the network I / F 4. To.

  According to the fourth embodiment, in addition to the same effects as those of the first embodiment, each FPGA mounting apparatus 100 is mounted with a plurality of FPGAs 1-1, 1-2. Since the FPGA connected to the network I / F 4 is selected by the changeover switch 6, the FPGA rewrite maintenance work can be performed quickly and efficiently.

  The present invention can be used as a remote maintenance system that remotely performs FPGA rewrite maintenance work of a plurality of FPGA-mounted devices connected via a network.

1 FPGA, 2 CPU, 3 memory, 3a, 3b, 3c data storage area,
4 network interface, 5 terminal interface, 6 selector switch,
10 network, 11 master / slave setting means, 12 FPGA rewriting means,
100, 100-1, 100-2, 100-3, 100-4, 100-n FPGA mounted device, 200, 200-1, 200-2, 200-3, 200-4, 200-n maintenance terminal, 300 Management device.

Claims (11)

N (n ≧ 2) FPGA-equipped devices including at least one FPGA, CPU and memory are connected to each other via a network, one of which is a master device and the other (n−1) are slaves As a device, a remote maintenance system of an FPGA mounted device that performs rewrite maintenance work on the FPGA of the slave device from a maintenance terminal device connected to the master device, wherein each FPGA mounted device is:
A network interface connecting the network and the FPGA;
A terminal interface for connecting the CPU and the maintenance terminal device;
A master / slave setting unit provided in the FPGA and configured to set the own device as one of the master device and the slave device;
A remote maintenance system for an FPGA-installed apparatus, comprising: an FPGA rewriting unit that is provided in the FPGA and causes the self apparatus and the slave apparatus to rewrite the FPGA when the self apparatus is the master apparatus.   2. The remote maintenance system for an FPGA-mounted device according to claim 1, wherein a user accesses the master / slave setting means via the CPU from a master / slave setting screen displayed on the maintenance terminal device. A remote maintenance system for an FPGA-equipped device, wherein the FPGA-equipped device to which the maintenance terminal device is connected is set to either the master device or the slave device.   2. The remote maintenance system for an FPGA-mounted device according to claim 1, wherein the FPGA rewriting unit of the master device executes an FPGA stored in the memory of the own device when the slave device rewrites the FPGA. 3. After reading the data for rewriting and sending it to all the slave devices that are the target via the network, the CPU of the slave device received the FPGA rewriting instruction to each slave device. The FPGA rewrite data is stored in the memory of its own device, and the FPGA of the slave device reads out the FPGA rewrite data from the memory and writes it into the FPGA. .   4. The remote maintenance system for an FPGA-equipped device according to claim 3, wherein the memory has a plurality of data storage areas for storing FPGA rewrite data, and each of the data storage areas has a different FPGA rewrite area. A remote maintenance system for FPGA-equipped devices, characterized in that data is stored.   5. The remote maintenance system for an FPGA-equipped device according to claim 4, wherein the CPU of the slave device corresponds to the FPGA rewrite data designated by the master device when the CPU rewrites the FPGA. And switching to the data storage area, and the FPGA of the slave device reads out and rewrites the FPGA rewrite data stored in the data storage area into the FPGA.   The remote maintenance system for an FPGA-mounted device according to claim 3, wherein the master device transmits the data for FPGA rewriting to the slave device by dividing the data into at least two times. A remote maintenance system for FPGA-equipped devices.   2. The remote maintenance system for an FPGA-mounted device according to claim 1, wherein when the CPU of the slave device performs rewriting of the FPGA, the CPU resets the device itself and disconnects from the network. A remote maintenance system for an FPGA-equipped device, which performs network disconnection / entry processing to re-enter the network after configuration is completed.   8. The remote-maintenance system for an FPGA-mounted device according to claim 7, wherein the network disconnection / entry process is sequentially performed one by one in all the slave devices to be processed. Remote maintenance system.   2. The remote maintenance system for an FPGA-equipped device according to claim 1, wherein a control transfer data frame and an FPGA management data frame are defined as a data frame format of data flowing on the network. Remote maintenance system for on-board equipment.   The remote maintenance system for an FPGA-mounted device according to claim 9, wherein the FPGA management data frame further includes frames for master device information, slave device information, FPGA rewrite data, and command type information. A remote maintenance system for FPGA-equipped devices, characterized in that each is defined.   2. The remote maintenance system for an FPGA-mounted device according to claim 1, wherein each of the FPGA-mounted devices is connected to a plurality of FPGAs in which different FPGA data are written and the network interface from among the plurality of FPGAs. The CPU of the slave device that has received the FPGA rewrite instruction from the master device operates the changeover switch to the FPGA data designated by the master device. A remote maintenance system for an FPGA-mounted apparatus, wherein the corresponding FPGA is connected to the network interface.

Images