close

Вход

Забыли?

вход по аккаунту

?

DESCRIPTION JP2011066848

код для вставкиСкачать
Patent Translate
Powered by EPO and Google
Notice
This translation is machine-generated. It cannot be guaranteed that it is intelligible, accurate,
complete, reliable or fit for specific purposes. Critical decisions, such as commercially relevant or
financial decisions, should not be based on machine-translation output.
DESCRIPTION JP2011066848
PROBLEM TO BE SOLVED: To reliably and easily manage firmware version of each device when
an acoustic signal processing system used in a concert hall or the like is configured by a plurality
of devices connected via a network. SOLUTION: A plurality of devices each belong to any one of a
plurality of device groups, and some devices in each device group are interfaces (partial bridges)
for communicating with other device groups Is equipped. The check box 182 is used to specify
whether to update the firmware of the partial bridge. In this way, while maintaining the firmware
related to the partial bridge in a version that can communicate with other device groups, other
firmware can be updated automatically, and different versions of firmware can be applied to each
device group. be able to. [Selected figure] Figure 6
Firmware update device and program
[0001]
The present invention relates to a firmware update device and program suitable for use in mixing
audio signals in a concert hall or a recording studio.
[0002]
In recent years, among audio signal processing systems in a concert hall or a recording studio,
there has been known one which exchanges audio signals and control signals between devices
(devices) constituting the system via a network.
10-04-2019
1
An example is disclosed in Patent Document 1. The devices constituting the system are a console
for the user to operate, an engine for performing processing such as mixing on an audio signal,
and an I / O unit for controlling a microphone, a speaker, etc. A memory that is controlled by and
stores firmware for that purpose is provided. These firmwares are often updated to fix bugs and
add new features. The maker of the device provides the latest firmware via the Internet or the
like, but the owner of the device independently decides whether to actually download the
firmware and update the firmware.
[0003]
In order to upgrade the firmware version of each device, it is necessary to execute so as to
prevent inconsistency (conflict). For example, if the console and engine firmware versions are
both "1.00", the console and engine operate normally, and even if both firmware versions are
"2.00", both are normal. Shall operate. However, for example, if the firmware version of the
console is "1.00" and the engine firmware version is "2.00", the console may not operate
normally. When the maker of the device provides the latest firmware via the Internet etc., that is
of course taken into consideration, and as long as the latest firmware is applied to all the devices,
the firmware conflicts with the firmware. There is no room for
[0004]
JP, 2008-17084, A
[0005]
However, even if the manufacturer provides the latest firmware for each device, there are cases
where the user does not (or can not) align all devices with the latest firmware. .
This is generally due to the following reasons. (1) First, the latest version of firmware may
contain bugs that were not found in past versions. As a result, the user does not want to upgrade
the firmware if the function which has been regularly used in the past version can not be used.
(2) Moreover, even if it is not clear whether the latest version contains a bug, the danger always
exists. For example, at a time when the concert production is approaching, if the old version of
the firmware is operating stably, the user often requests to keep using the old version.
10-04-2019
2
[0006]
(3) There is also a problem that it takes a long time to upgrade a large number of devices. That is,
although the update time per device is not very long, hundreds of devices are used in a large
event. In such a case, it is rare that the vendor owns all necessary devices, and in most cases, the
devices will be borrowed from a plurality of rental companies. Since these devices are owned by
different companies (rental companies), there is no guarantee that the integrity of the firmware
has been ensured. Usually, in order to reduce rental costs, device borrowing is often immediately
before a concert or the like, and sufficient time can not be secured for firmware upgrade. (4)
Further, there may be cases where the owner (rental company) 's consent can not be obtained for
upgrading the firmware of the borrowed device.
[0007]
For the reasons described above, there has conventionally been a demand for suppressing
firmware updates to a range where no conflict occurs, rather than aligning the firmware of all
devices constituting the audio signal processing system to the latest version. However, in order to
realize this, it is necessary for the user to manage the firmware version so as not to cause a
conflict, which is extremely troublesome for the user. The present invention has been made in
view of the above-described circumstances, and it is an object of the present invention to provide
a firmware updating apparatus and program capable of easily and surely performing a partial
version upgrade of firmware.
[0008]
In order to solve the above problems, the present invention is characterized by comprising the
following configuration. In addition, the inside of a parenthesis is an illustration. In the firmware
update device according to claim 1, the plurality of sound processing devices (1502 to 1510)
communicate with a plurality of sound processing devices (1502 to 1510) that belong to any of a
plurality of device groups. A firmware updater (1000) for updating firmware, which is a control
program stored in the control unit and controlling each sound processing device, wherein each
sound processing device is another sound processing device in the device group to which each
belongs. A first network interface (a network card in the first slot) for communicating with each
other, and transmitting or receiving voice signals to each other via the first network interface; At
least one of the sound processing devices A second network interface (a network card of a
second slot) for communicating with the sound processing device belonging to the plurality of
10-04-2019
3
the plurality by transmitting or receiving voice signals to each other via the second network
interface Communication of voice signals between the device groups of the device group, and one
of the plurality of device groups to which the firmware is to be updated is designated as the
device group to be updated based on the user's operation. Device group specifying means (152),
update target device selection means (172) for selecting an update target device which is one or
more acoustic processing devices belonging to the update target device group based on the
user's operation, and a user Based on the operation of the second The inter-group interface
update designating means (182) for designating whether or not the firmware related to the
network interface (the network card of the second slot) is to be updated, and the second intergroup interface update designating means (182) An update that instructs to update the firmware
of each of the devices to be updated, including the firmware related to the second network
interface, on the condition that the update related to the firmware related to the network
interface is specified On the condition that the command is sent to each of the devices to be
updated while the inter-group interface update designating means (182) designates that the
firmware relating to the second network interface is not to be updated. Ne Firmware update
command means (SP32, SP34) for transmitting an update command instructing that the
firmware of each of the update target devices should be updated excluding the firmware related
to the network interface to the respective update target devices It is characterized by being
equipped.
Furthermore, in the configuration according to claim 2, in the firmware update device according
to claim 1, an acoustic processing device among the plurality of acoustic processing devices
belonging to the update target device group based on a user operation. Reference device
specifying means (154) for specifying the device as a reference device, and version number
acquisition for acquiring version numbers of firmware stored in the respective sound processing
devices belonging to the update target device group from the respective sound processing
devices Means (SP8) and matching table storage means (24) for storing a matching table (70) for
determining a combination having consistency among combinations of version numbers of the
respective firmware, and stored in the reference device Based on firmware And displaying, from
among the sound processing devices belonging to the update target device group, a sound
processing device storing firmware not satisfying the consistency defined in the matching table
(70). And a matching device display means (156). Further, in the program according to claim 3,
each of the plurality of sound processing devices (1502 to 1510) which communicate with the
plurality of sound processing devices (1502 to 1510) belonging to any of the plurality of device
groups A program applied to a firmware updating apparatus (1000) for updating firmware,
which is a control program for storing and controlling each sound processing device, wherein
each of the sound processing devices is a device group to which each belongs. A first network
interface (a network card of a first slot) for communicating with the sound processing device of
the second aspect, and transmitting or receiving voice signals to each other via the first network
interface, At least one sound processing device in each device group By having a second network
10-04-2019
4
interface (network card of second slot) for communicating with an audio processing device
belonging to the device group, by transmitting or receiving voice signals to each other via the
second network interface Communication of an audio signal between the plurality of device
groups is performed, and the firmware updating device (1000) is configured to be compatible
with the processing device (10) and the combination of the version numbers of the respective
firmware. And a matching table storage means (24) for storing a matching table (70) for defining
a certain combination, and one of the plurality of device groups to be updated with the firmware
based on a user operation. Update target device group Group selection step (152) for specifying
a group as an update target device selection step (172) for selecting an update target device
which is one or more acoustic processing devices belonging to the update target device group
based on the user's operation An inter-group interface update specifying step (182) for
specifying whether to update the firmware related to the second network interface (the network
card in the second slot) based on the user's operation and the user's operation; Each update,
including the firmware related to the second network interface, on condition that it is specified
that the firmware related to the second network interface is updated in the inter-group interface
update specification step (182) Firmware of target device Is sent to each of the devices to be
updated, the update command instructing that the update should be performed, while the intergroup interface update specification step (182) specifies that the firmware pertaining to the
second network interface is not to be updated. Firmware update that transmits an update
command instructing that the firmware of each update target device should be updated
excluding the firmware related to the second network interface on the condition that A command
process (SP32, SP34) is performed by the processing device (10).
[0009]
According to the present invention, since the inter-group interface update designating means can
designate whether or not the firmware relating to the second network interface used for
communication between device groups is to be updated, the second network interface The other
firmware can be updated automatically while keeping the firmware related to the version that
can communicate with the other device group. As a result, it is possible to easily and reliably
execute a partial version upgrade of firmware such that different versions of firmware are
applied to each device group.
[0010]
FIG. 1 is a block diagram showing an overall configuration of an acoustic signal processing
system according to an embodiment of the present invention. FIG. 2 is a block diagram showing a
10-04-2019
5
network configuration and a detailed configuration of each device. FIG. 2 is a block diagram of a
PC (personal computer) 1000. It is explanatory drawing of the module structure of firmware. FIG.
6 is a view showing a device group setting window 100 displayed on the PC 1000. It is a figure
which shows the window 150 displayed on PC1000. It is a flowchart of a reference change event
processing routine. It is a flowchart of an update start event processing routine.
[0011]
1.
Configuration of Example 1.1. Overall Configuration Next, the overall configuration of an acoustic
signal processing system according to an embodiment of the present invention will be described
with reference to FIG. The acoustic signal processing system of this embodiment is configured by
connecting a plurality of devices by a network. These devices are classified into any one of three
types of "device type": "console", "engine", or "I / O unit". The “console” is provided with a large
number of faders, knobs and the like operated by the user, and mainly outputs control signals
based on these operation states through the network. Also, "engine" mainly performs mixing
processing and equalizing processing on an audio signal supplied via a network, based on a
control signal supplied from the console, and outputs the result via the network It is In addition,
the “I / O unit” converts an audio signal input from a microphone or the like into a packet and
outputs the packet through the network, converts a packet supplied through the network into an
audio signal, and transmits it through an amplifier. To the speakers.
[0012]
In the example of FIG. 1, 1502, 1510 and 1606 are consoles, 1504 and 1604 are engines, and
1506, 1508 and 1602 are I / O units. All of these devices 1502-1510, 1602-1606 need to be
equipped with one or two network cards in order to connect to the network. Therefore, first and
second slots (Slot 1 and Slot 2) are provided as slots for mounting the network card. Here, a
group of devices connected via each first slot is referred to as a "device group". In the illustrated
example, the devices 1502-1510 are connected via their respective first slots, so they constitute
a device group, which is referred to as a "first device group 1500". Similarly, the devices 16021606 make up a second device group 1600.
[0013]
10-04-2019
6
The console 1510 and the I / O unit 1602 have a network card attached to not only the first slot
but also the second slot, and transmit and receive packets via this second slot. As described
above, the state of a device that transmits and receives packets via the second slot is referred to
as "configure a partial bridge". The first and second device groups 1500 and 1600 each process
a certain range of audio signals, and each of the first and second device groups 1500 and 1600
processes "100 channels" of audio signals, for example. In order for both device groups to
cooperate, it is necessary to mutually input and output audio signals, but it is not necessary to
supply all audio signals to each other, and some audio signals, for example, “10 channels” of
each other You can cooperate if you provide audio signals. As described above, since the audio
signals input and output between device groups are partial, they are referred to as "partial
bridges".
[0014]
A plurality of device groups connected via a partial bridge form a "zone". In the illustrated
example, the zone 1400 is formed by the first and second device groups 1500 and 1600.
However, the number of device groups belonging to one zone can be “3” or more. In this case,
a network card may be attached to the second slot in each one device belonging to each device
group, and the network cards in these second slots may be connected to each other. The device
group is configured to perform various "integral roles" (e.g. back chorus mixing, instrument
sound mixing etc) as well as the device owner (e.g. vendor themselves, rental company A, rental
company B etc.) It is preferable to configure them together.
[0015]
Reference numeral 1000 denotes a PC (personal computer), which can be connected to any
device. The PC 1000 can obtain information of the entire zone (for example, firmware version
information of all devices connected to the zone 1400) via the connected devices, and can select
any device belonging to the zone 1400. In response to this, an update command (a command for
instructing update of firmware together with binary data of firmware) can be transmitted.
Acquisition of information on other device groups to which the device connected to the PC 1000
does not belong, and transmission of an update command to the other device groups are realized
via the partial bridge. Note that "update" in the present embodiment is a concept including not
only updating of firmware to a new version but also returning of firmware to an old version (socalled down date).
10-04-2019
7
[0016]
1.2.
Network Configuration In the present embodiment, the devices belonging to each device group
constitute a token ring type network by mutually connecting the network cards mounted in the
first slot. An exemplary configuration of the network 1520 in the first device group 1500 is
shown in FIG. In a token ring type network, any one device (I / O unit 1508 in the illustrated
example) becomes a master node and generates a signal called "token". This token is cyclically
transmitted to each device belonging to the first device group 1500 in a predetermined order.
[0017]
Here, only the device that has obtained the token has the right to transmit data. That is, the
device which is going to transmit data first captures an empty token, converts it into a frame,
carries and transmits data. Each device monitors the incoming frames, fetches the contents only
when the address of the own machine is specified as the receiver, and sends the frame not
addressed to the own machine to the next node as it is It has become. Thus, data communication
can be performed between the devices without causing a data collision. Although the network
configuration of the first device group 1500 has been described above, the network of the
second device group 1600 is similarly configured, and the network attached to the second slot
also between the devices forming the partial bridge. A token ring type network is similarly
formed by connecting cards. As described above, it is also possible to exchange data between
device groups by interconnecting a plurality of networks via a partial bridge.
[0018]
1.3.
Configuration of Each Device Next, the detailed configuration of each device will be described.
First, the configuration of the "console" will be described with reference to FIG. 1 (b). In the
figure, reference numeral 1110 denotes a panel display unit which is constituted by a large dot
matrix display and a touch panel, and displays various information to the user. Reference
numeral 1112 denotes a panel operator, which is composed of operators such as knobs and
buttons. An electric fader 1122 is used to adjust the volume of input / output channels. A
memory 1116 is composed of a flash ROM and a RAM, and the flash ROM stores firmware which
is a control program of the console. A CPU 1114 controls each unit in the console via a CPU bus
1120 based on the firmware. Reference numeral 1118 denotes a PCIO unit, which is provided
10-04-2019
8
with an interface for communicating with the PC 1000. An audio I / O unit 1124 inputs and
outputs small-scale audio signals such as monitoring signals for communication between
workers.
[0019]
Reference numeral 1126 denotes a network I / O unit, in which the first and second slots
described above are provided, and by installing a network card in these slots, it is possible to
communicate with another device via one or two networks. Data can be sent and received
between. That is, the network I / O unit 1126 converts the control signal supplied from the CPU
bus 1120 and the audio signal supplied from the audio bus 1130 into packets, transmits them to
the network, and transmits the packets supplied from the network. Are converted into control
signals or audio signals, and output through the CPU bus 1120 or the audio bus 1130.
[0020]
Next, the configuration of the "engine" will be described with reference to FIG. 1 (c). A memory
1212 includes a flash ROM and a RAM. The flash ROM stores firmware that is a control program
of the engine. A CPU 1210 controls each unit in the engine via a CPU bus 1220 based on the
firmware. Reference numeral 1214 denotes a PCIO unit, which is provided with an interface for
communicating with the PC 1000. A simple UI unit 1216 includes an operator operated by the
user and a display for displaying various information to the user. An audio I / O unit 1218 inputs
and outputs small-scale audio signals for communication between workers. Reference numeral
1222 denotes a DSP, which performs mixing processing or equalizing processing on an audio
signal received via the audio bus 1230, and outputs the result via the audio bus 1230. The
microprogram for controlling the DSP 1222 is also included in the firmware.
[0021]
Reference numeral 1226 denotes a network I / O unit, in which the first and second slots
described above are provided, and by installing a network card in these slots, it is possible to
communicate with another device via one or two networks. Data can be sent and received
between. That is, in the network I / O unit 1226, the control signal supplied from the CPU bus
1220 and the audio signal supplied from the audio bus 1230 are converted into packets,
transmitted to the network, and packets supplied from the network Are converted into control
10-04-2019
9
signals or audio signals and output through the CPU bus 1220 or the audio bus 1230.
[0022]
Next, the configuration of the "I / O unit" will be described with reference to FIG. 1 (d). A memory
1312 is composed of a flash ROM and a RAM, and the flash ROM stores firmware which is a
control program of the I / O unit. A CPU 1310 controls each unit in the I / O unit via a CPU bus
1320 based on the firmware. A PCIO unit 1314 is provided with an interface for communicating
with the PC 1000. A simple UI unit 1316 includes an operator operated by the user and a display
for displaying various information to the user. An audio I / O unit 1324 converts an audio signal
received through the audio bus 1330 into an analog signal or a digital signal compatible with the
target amplifier, and outputs the converted audio signal, while an audio signal input from a
microphone or the like Are converted into digital signals and supplied to the network I / O unit
1326 via the audio bus 1330.
[0023]
Reference numeral 1326 denotes a network I / O unit, which is provided with the first and
second slots described above, and by installing a network card in these slots, it is possible to
communicate with another device via one or two networks. Data can be sent and received
between. That is, in the network I / O unit 1326, the control signal supplied from the CPU bus
1320 and the audio signal supplied from the audio bus 1330 are converted into packets,
transmitted to the network, and the packets supplied from the network Are converted into
control signals or audio signals, and output through the CPU bus 1320 or the audio bus 1330.
[0024]
1.4.
Configuration of PC Next, the configuration of the PC 1000 will be described with reference to
FIG. In the figure, reference numeral 2 denotes a communication interface, which communicates
with a file server or the like via the Internet for downloading firmware, etc., and communicates
with PCIO units 1118, 1214 and 1314 of any device for controlling the zone 1400. It is provided
to An input device 4 comprises a character input keyboard, a mouse and the like. A display 8
displays various information to the user. A CPU 10 controls other components via the CPU bus
16 based on a program described later. A ROM 12 stores an initial program loader and the like. A
10-04-2019
10
removable disk drive 18 reads / writes to a removable disk 20 such as a CD-ROM or MO. A hard
disk 24 stores an operating system, firmware of devices in the zone 1400, an application
program for updating the firmware, and the like. A RAM 30 is used as a work memory of the CPU
10.
[0025]
2.
Configuration of firmware 2.1. Configuration of Firmware Module in Device As described above,
the memory 1116, 1212, 1312 (flash ROM) of each device stores firmware for controlling each
device. It is composed of multiple modules. The contents will be described with reference to FIG.
4 (a). First, the firmware 40 in the console is mounted in the first and second slots and the panel
module 41 for controlling the panel operator 1112 and the electric fader 1122 and the like, the
display module 44 for controlling the panel display 1110 and the like. The network module 46,
48 controls the network card, and the CPU module 42 performs other control.
[0026]
Also, the firmware 50 in the engine includes a DSP module 54 which is a microprogram of the
DSP 1222, network modules 56 and 58 for controlling the network cards mounted in the first
and second slots, and a CPU for performing other control. And a module 52. Also, the firmware
60 in the I / O unit includes an audio I / O module 64 that controls the function of the audio I / O
unit 1324 and a network module that controls the network card installed in the first and second
slots. It comprises 66, 68 and a CPU module 62 which performs other control.
[0027]
In the example of FIG. 4A, although it is assumed that the network card is attached to both the
first and second slots in any device, the network card is attached to the second slot. If not, the
corresponding modules 48, 58, 68 are not included in the firmware in these devices. In these
devices, one of two types of network cards (for example, 1 Gbps and 2 Gbps) having different
transmission capacities (hereinafter referred to as type A and type B) can be selected and
mounted. Therefore, as a mode of adoption of the network card, when only one or two type A
network cards are installed, when only one or two type B network cards are installed, and It is
conceivable that one type of network card of type A or B is installed.
10-04-2019
11
[0028]
2.2.
Firmware / module configuration in PC In addition, in the predetermined folder of hard disk 24
of PC 1000, firmware for updating is stored corresponding to each device type, and these
firmwares are also each of a plurality of modules It is configured. The contents will be described
with reference to FIG. 4 (b). First, the firmware 240 for the console corresponds to the modules
41, 42, and 44 in the firmware 40 in the console described above, and the panel module 241, the
CPU module 242, and the display module for updating them. And 244 are included. Also, the
firmware 240 includes a type A network module 246 and a type B network module 248
corresponding to the type A and B network cards.
[0029]
Whether or not both of the network modules 246 and 248 are necessary depends on the
configuration of the actual device (in this case, the console), but the modules included in the PC
1000 include all the modules that may be necessary. When actually updating the firmware of the
device, only the necessary modules are selected and transferred to each device. As each module
241-248 in firmware 240 is updated according to different circumstances, as shown, the version
numbers of these individual modules (eg "1.0", "2.0", " Etc.) are different. Also, as illustrated, the
firmware 240 for console is assigned a version number of “2.0”. This version number is, in
other words, a version number assigned to the entire set of modules 241 to 248 shown.
[0030]
The engine firmware 250 also includes a CPU module 252 and a DSP module 254 for updating
the modules 52 and 54 in the engine firmware 50 described above. , And network modules 256
and 258 for types A and B, respectively. The network modules 256 and 258 are similar to the
console network modules 246 and 248 described above. Then, a version number of “2.5” is
assigned to the engine firmware 250 (in other words, to a set of all modules for the engine).
[0031]
10-04-2019
12
Further, the firmware 260 for the I / O unit corresponds to the modules 62 and 64 in the
firmware 60 in the above-described I / O unit, and the CPU module 262 for updating these and
the audio I / O. O module 264 is included, and further, network modules 266 and 268 for types
A and B are included. The network modules 266 and 268 are similar to the network modules
246 and 248 for consoles described above. Then, a version number of “1.5” is assigned to the
firmware 260 for the I / O unit (in other words, for the entire set of modules for the I / O unit).
The version number for each module and the version number as a set of modules for each device
are transmitted from the PC 1000 to each device when updating the firmware, and the flash
ROM of the memory 1116 1212 1312 in each device These version numbers are also stored in.
[0032]
2.3.
Matching Table In the predetermined folder of the hard disk 24 of the PC 1000, a matching table
70 shown in FIG. 4C is stored. This table defines combinations that do not cause inconsistencies
(conflicts) for the firmware version (device version) of each device. For example, according to the
top column of FIG. 4C, if the version of the firmware 40 in the console is "2.0", the version of the
firmware 50 in the engine cooperating with the console is "2". Must be "1.5" or "2.0" and the
version of firmware 60 in the I / O unit working with this console must be "1.5".
[0033]
3.
Operation of Example 3.1. Processing in Device Group Setting Window Next, the operation of this
embodiment will be described. First, in the hard disk 24 of the PC 1000, data (device group data)
in which the configuration of each device group in the zone 1400 is recorded is stored. When the
user performs a predetermined operation on the PC 1000, a device group setting window 100
shown in FIG. 5 is displayed on the display 8 in order to edit device group data. In FIG. 5,
reference numeral 102 denotes a device group selection list box, which selects one device group
to be set. A device setting field 103 displays a list of devices belonging to the device group. Inside
the device setting field 103, an identification number display field 104 displays a unique
identification number (ID) automatically assigned to each device belonging to the selected device
group. A device name display unit 106 displays the name of each device.
[0034]
10-04-2019
13
A device type display unit 108 displays the device type to which each device belongs. A partial
bridge setting unit 110 includes check boxes for setting whether or not each device is a device
forming a partial bridge. In the illustrated example, the console of "ID = 5" constitutes a partial
bridge. A device type selection unit 112 includes radio buttons for selecting the type of device to
be newly added. Reference numeral 114 denotes an Add button. When the mouse is clicked, a
device of the type selected in the device type selection unit 112 is added to the current device
group.
[0035]
A renaming button 116 is provided to change the name of any device. That is, when the user
selects an arbitrary device in the device setting column 103 and clicks the rename button 116
with a mouse, the corresponding device column in the device name display unit 106 is changed
to a text box, and the user The name of the device can be changed. A remove button 118 is
provided to remove any device. That is, when the user selects an arbitrary device in the device
setting section 103 and clicks the remove button 118 with a mouse, the device is deleted from
the currently selected device group. An OK button 122 is clicked on with a mouse to update the
device group data in the hard disk 24 based on the setting contents in the device group setting
window 100, and the window 100 is closed. A cancel button 120 is clicked on with a mouse to
discard the settings in the window 100 and close the window 100 without updating the device
group data.
[0036]
The contents of the device setting field 103 in FIG. 5 correspond to the configuration of the first
device group 1500 shown in FIG. That is, each device of ID "1"-"5" respond | corresponds to the
devices 1502-1510. Since the device group setting window 100 is for editing the device group
data stored in the hard disk 24 of the PC 1000, the device group data can be edited differently
from the actual device group configuration. Device group data can be edited even when the PC
1000 is not connected to any device.
[0037]
10-04-2019
14
Thereafter, when the user connects the PC 1000 to any of the devices and performs a
predetermined operation on the PC 1000, the device group data in the PC 1000 is compared
with the state of the device group actually configured, and the difference between the two is In
some cases, an error message is displayed on the PC 1000 to correct one or the other. On the
other hand, if there is no contradiction between the device group data in the PC 1000 and the
actual device group status, the firmware version numbers in all the devices in the zone 1400 will
be through the connected devices. It is acquired, and the result is incorporated into device group
data.
[0038]
3.2.
Display of the firmware update window After the version number of the device in the zone 1400
is taken into the device group data in the PC 1000, when the user performs a predetermined
operation on the PC 1000, the firmware update window 150 shown in FIG. 6 is displayed Be
done. In FIG. 6, reference numeral 152 denotes a device group selection list box, which selects a
device group to be a target of firmware update based on a user operation. In this embodiment, by
providing the device group selection list box 152, for example, when there is no time to upgrade
all devices, it is possible to upgrade only the device groups that need to be upgraded. It can be
carried out. In addition, for devices for which firmware version upgrade is prohibited due to the
owner (rental company) 's convenience, etc., another (version upgrade) is performed by
configuring a device group using only such devices. It is possible to prevent conflicts with
devices.
[0039]
A device setting field 153 displays a list of devices belonging to the device group. The contents of
the device setting field 153 in FIG. 6 correspond to the configuration of the first device group
1500 shown in FIG. 1 and the contents of the device setting field 103 in FIG. A reference setting
unit 154 in the device setting field 153 selectively sets one of the devices in the device group as
a “reference device” based on the user's operation. The "reference device" is a device which is
a reference in determining whether there is a firmware version conflict. A conflict display unit
156 displays on the reference device whether or not a conflict has occurred. A device name
display unit 158 displays the name of the device. A device type display unit 160 displays the type
of the device. A partial bridge display unit 162 is lit when the device constitutes a partial bridge.
A current version display unit 164 displays the version of firmware currently stored in each
device.
10-04-2019
15
[0040]
Here, specific contents of the display contents in the device setting field 153 will be described. In
the illustrated example, the reference device is the device on the first line in the device setting
field 153, which has the name "Main Console", and the device type is "console". Then, according
to the current version display unit 164, the current version of the firmware is "2.0". Then,
according to the matching table 70 previously shown in FIG. 4C, if the firmware version of the
console is “2.0”, the firmware version of the engine cooperating with the console is “0. It
must be 2.5 "or" 2.0 "and the firmware version of the I / O unit working with the console must
be" 1.5 ".
[0041]
However, since the versions of the I / O unit in the third and fourth lines of the device setting
field 153 shown in the figure are “1.2” and “1.1”, the contents of the matching table 70 are
not followed. That is, the firmware of these I / O units is in conflict with the firmware of the
reference device. As a result, in the device setting field 153, the conflict display unit 156
corresponding to these I / O units is in the lit state. A firmware folder setting unit 168 includes a
text box for specifying a folder in which the firmware (firmware 240, 250, and 260 in FIG. 4B) is
stored in the hard disk 24. Reference numeral 170 denotes a browse button. When the mouse is
clicked with a mouse, a browse window is opened, and a folder name to be described in the
firmware folder setting unit 168 can be input by a browse operation. The firmwares 240, 250,
and 260 are the latest versions, but if firmware of an older version than these is stored in the
same folder, an older version of the firmware can also be selected as the update destination.
Become.
[0042]
An update setting field 171 includes a plurality of lines each corresponding to a device type.
Inside the update setting field 171, 176 is a device type name display section, and the device
type names "Console", "Engine" and "I / O unit (I / O)" corresponding to each row are displayed.
Is displayed. An update target device selection unit 172 includes check boxes for each device
type, and selects (checks) the device type for which firmware is to be updated based on the user's
operation. Reference numeral 174 denotes a conflict display unit, which displays the type of
10-04-2019
16
device in which a conflict has occurred in the lighted state. If a conflict occurs in at least one
device among the devices belonging to the device type, it means that the conflict occurs in the
device type.
[0043]
A version selection list box 178 is used to select the version number of the update destination for
each device type based on the user's operation from one or more version numbers compatible
with the reference device. The options listed in these list boxes are as described in the matching
table 70. That is, if the firmware version in the console which is the reference device is "2.0", the
firmware version in other consoles must also be "2.0", so the version number for the console
Only "2.0" is selectable. Also, as for the engine, since both of the firmware versions “2.5” and
“2.0” match, both are set in the list box as options. Also, for the I / O unit, since the firmware
version must be "1.5", only "1.5" is selectable.
[0044]
As described above, in this embodiment, the user can specify the version of the firmware update
destination for each “device type”. Therefore, even if the number of devices in the device
group is large, the update destination of these devices Specification of version can be easily
specified with few operations. As described above, the reason for specifying the version for each
device type is that, in general, there is no reason to differentiate firmware versions for devices of
the same type belonging to the same device group. Further, according to the present
embodiment, since the firmware version is selected in the version selection list box 178, the user
can surely select the version having consistency (no conflict) with the reference device. can do.
[0045]
A status display unit 180 displays the progress of the update. "Rebooting" in the figure indicates
a state in which each device is restarted after the firmware update is completed. "Complete"
refers to the state in which the relaunch is complete. Also, "Updating" indicates that the firmware
is being written to the flash ROM. Reference numeral 182 denotes a partial bridge exclusion
check box, which sets whether firmware for a network card attached to the second slot for a
partial bridge is to be excluded from update targets based on the user's operation. That is, when
the check box is checked, the network card is excluded from the target of the update.
10-04-2019
17
[0046]
184 is an update start button, and when it is clicked with the mouse, according to the
specification of the update setting field 171 and the check box 182, the update command
(firmware along with the binary data of the firmware) The transmission of a command
instructing update is started. As described above, the display content of the status display unit
180 is appropriately updated according to the progress of the update. A cancel button 186 is
clicked on with the mouse to discard the setting contents in the firmware update window 150
and then close the window 150. A close button 188 is used to close the window 150 after the
device group data has been updated based on the settings in the window 150. Once the update
start button 184 is clicked, the update itself is executed in a separate process, so the update will
continue even if the window 150 is closed.
[0047]
Here, the meaning of the partial bridge exclusion check box 182 described above will be
described with reference to FIG. 1 again. In FIG. 1, the devices 1502-1510 belonging to the first
device group 1500 are devices owned by a certain vendor in their own company, and the devices
1602-1606 belonging to the second device group 1600 are those which the vendor borrowed
from a rental company Suppose that there is. For these borrowed devices, as described above,
situations such as “cannot secure time for updating firmware” or “firmware updating is
prohibited” often occur. In that case, first check the firmware version of the network card
(rental product) installed in the second slot of the I / O unit 1602, and install the network card
installed in the second slot of the console 1510 (trader Update (or downdate) manually (without
using the application program according to FIG. 6) to match the firmware version of
[0048]
As a result, since the version numbers of the network cards in the second slot constituting the
partial bridge are aligned, communication between the console 1510 and the I / O unit 1602
should not be disturbed. After that, the application program according to FIG. 6 may be started,
the check box 182 may be checked, and the firmware of the portion excluding the network card
may be updated. As a result, communication between the first and second device groups 1500
and 1600 becomes possible without performing any firmware update for the second device
10-04-2019
18
group 1600.
[0049]
3.3.
Reference Change Event Processing (FIG. 7) Next, details of processing executed when the
reference setting unit 154 is operated in FIG. 6 and the reference device is changed will be
described. When the operation is detected, a reference change event processing routine shown in
FIG. 7 is started. In the figure, when the process proceeds to step SP2, one device checked in the
reference setting unit 154, that is, a reference device is identified. Next, when the process
proceeds to step SP4, the device type of the reference device and the firmware version are
acquired. Next, when the process proceeds to step SP6, the content of the field corresponding to
the acquired version is acquired from the matching table 70 (see FIG. 4C).
[0050]
Next, when the process proceeds to step SP8, version numbers are acquired for all other devices
than the reference device. Then, it is determined whether or not there is a version mismatch
(conflict) with respect to the reference device and all other devices, and based on the result, the
display content corresponding to each device in the conflict display unit 174 Is updated. Next,
when the process goes to step SP10, a list of versions which cause no version inconsistency is set
as an option in the version selection list box 178 for the reference device and all other devices.
Thus, the processing of this routine ends.
[0051]
3.4.
Update Start Event Processing (FIG. 8) Next, details of processing executed when the update start
button 184 is clicked on with a mouse in FIG. 6 will be described. When the operation is
detected, an update start event processing routine shown in FIG. 8 is started. In FIG. 8, when the
process proceeds to step SP20, it is determined whether the transmission start process (steps
SP32 and SP34 described later) of the update command has been completed for all device types
to be updated. Here, if the determination is "NO", the process proceeds to step SP22, and one of
the unprocessed device types is selected. Next, when the process proceeds to step SP24, it is
determined whether the transmission start process of the update command is completed for all
10-04-2019
19
devices belonging to the selected device type. Here, if it is determined as "NO", the process
proceeds to step SP26, and one device is selected from devices belonging to the type. The device
selected here is called "target device".
[0052]
Next, when the process proceeds to step SP28, it is determined whether a network card for
partial bridge is attached to the second slot of the target device. Here, if it is determined as "NO"
(not installed), the process proceeds to step SP34, and for all modules stored in the target device,
in the version specified in the version selection list box 178 earlier. An update command is sent
to update the module. That is, a new process for sending an update command is launched, and
sending of the update command is performed in the process. On the other hand, if a network
card for partial bridge is attached to the second slot of the target device, "YES" is determined in
step SP28, and the process proceeds to step SP30. Whether the network card for the partial
bridge installed in this second slot is also targeted for firmware update based on whether or not
the partial bridge exclusion check box 182 described above is checked here. It is determined
whether or not. Here, if "YES" is determined, the process proceeds to step SP34, and transmission
of an update command so as to update all modules stored in the target device to modules in the
specified version as described above Is started.
[0053]
On the other hand, if the partial bridge exclusion check box 182 described above is checked, it is
determined as “NO” (outside of update target) in step SP30, and the process proceeds to step
SP32. Here, without updating the network card in the second slot for partial bridge, all other
modules are targeted to be updated to modules in the version specified in the version selection
list box 178 first. Transmission of the update command to the device is started. When the
process of step SP32 or SP34 ends, the process returns to step SP24, and whether the
transmission start process (SP32, SP34) of the update command has been completed for all
devices belonging to the device type selected in step SP22 earlier It is determined whether or
not. Here, if the determination is "NO", the processing of steps SP26 to SP34 is repeated, and
transmission of an update command to a new target device is started each time via steps SP32
and SP34.
[0054]
10-04-2019
20
On the other hand, when the transmission start process of the update command to all devices
belonging to the selected device type is completed, “YES” is determined in step SP24, and the
process returns to step SP20. Here, if the transmission start process of the update command has
not been completed for all device types to be updated, "NO" is determined in step SP20, and the
processes of steps SP22 to SP34 are repeated. Then, when the transmission start process of the
update command to all devices belonging to the device group to be updated and to the device
type to be updated is completed, "YES" is determined in step SP20, and the process of this
routine is performed. finish.
[0055]
4.
Modifications The present invention is not limited to the embodiments described above, and
various modifications can be made, for example, as follows. (1)In the above embodiment,
processing such as updating is performed by an application program operating on the PC 1000,
but only this application program is stored and distributed in a recording medium such as a CDROM or a memory card, or distributed through a transmission path You can also
[0056]
(2)
In the above embodiment, “specify the firmware version for each device type in the version
selection list box 178 (feature 1)” “partial bridge exclusion check box 182” for the network
of the second slot pertaining to the partial bridge Although both of the two features of
“prohibiting card update (feature 2)” are included, only one feature may be applied. When
only “feature 1” is to be applied, the check box 182 may simply be removed from the window
150. When only “feature 2” is applied, a row is provided for each “device” like the device
setting field 153 instead of the “device type” for the update setting field 171, and the version
number of the update destination for each device It is good to specify
[0057]
2: Communication interface 4: Input device 8: Display 10: CPU (processing device) 12: ROM 16:
CPU bus 18: removable disk drive device 20: removable disk 24: hard disk 30: RAM , 40, 50, 60:
firmware, 41: panel module, 42: CPU module, 44: display module, 46, 48: network module, 52:
CPU module, 54: DSP module, 56, 58: network module, 62 : CPU module, 64: voice I / O module,
10-04-2019
21
66, 68: network module, 70: matching table, 100: device group setting window, 102: device
group selection list box, 103: device setting field 104: identification number display column, 106:
device name display unit, 108: device type display unit, 110: partial bridge setting unit, 112:
device type selection unit, 114: Add button, 116: rename button, 118: remove / remove Button
120: Cancel button 122: OK button 150: window 150: firmware update window 152: device
group selection list box (device group specification means) 153: device setting field 154:
reference setting unit 156: conflict display unit (mismatched device display means), 158: device
name display unit, 160: device type display unit, 162: partial bridge display unit, 164: current
version display unit, 168: firmware folder setting unit, 170: B Use button 171: update setting
field (update target device selection means) 172: update target device selection portion (update
target type selection means) 174: conflict display portion 176: device type name display portion
178: version selection List box (version number selection means) 180: status display section 182:
check box 182: partial bridge exclusion check box 184: update start button 186: cancel button
188: close button 240, 250, 260: Firmware, 241: panel module, 242, 252, 262: CPU module,
244: display module, 246, 248, 256, 258, 266, 268: network module, 254: DSP module , 264:
voice I / O module, 1000: PC (firmware update device), 1400: zone, 1500: first device group,
1600: second device group, 1502-1510, 1602-1606: devices.
10-04-2019
22
Документ
Категория
Без категории
Просмотров
0
Размер файла
40 Кб
Теги
description, jp2011066848
1/--страниц
Пожаловаться на содержимое документа