Electronic device, firmware updating method, and firmware updating program

Abstract

To provide an electronic device, a firmware update method, and a firmware update program capable of reducing time and effort of a user required for updating firmware of an electronic musical instrument.SOLUTION: When the electronic musical instrument is attached to the external input / output device 13 of the sound source device 1, the model information and the version of the firmware are received from the electronic musical instrument as the object, and the received version is compared with the non-corresponding version in the firmware table 11b. When the acquired version is equal to or lower than the non-corresponding version, the update data of the target electronic musical instrument in the firm table 11b is acquired and transmitted to the target electronic musical instrument together with an instruction to perform update using the update data. Since the firmware of the electronic musical instrument is updated to the one suitable for the sound source device 1 only by connecting the sound source device 1 to the target electronic musical instrument, the labor of the user H for updating the firmware of the electronic musical instrument can be reduced.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to an electronic device, a firmware updating method, and a firmware updating program. [Background technology]

[0002] Firmware is built into electronic musical instruments, such as electronic drums, that are connected to a sound source device. Conventionally, as shown in Non-Patent Document 1, for example, a PC is connected to the electronic percussion instrument, and the firmware of the electronic musical instrument is updated from an application on the PC. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] UpdSMF, a simple SMF player for updating, [online], [searched August 19, 2024], Internet <URL:https: / / www.roland.com / jp / support / by_product / tm-1 / updates_drivers / 47e64fda-6e5f-483d-a95e-efbe369b3031 / > Summary of the Invention [Problem to be solved by the invention]

[0004] However, when updating an electronic musical instrument from a PC, it is necessary to obtain firmware compatible with the electronic musical instrument and specify that firmware in the application, which poses the problem of complicated user operations required for firmware updates.

[0005] The present invention has been made to solve the above-mentioned problems, and aims to provide an electronic device, a firmware update method, and a firmware update program that can reduce the user's effort required to update the firmware of an electronic musical instrument. [Means for solving the problem]

[0006] In order to achieve this object, the electronic device of the present invention is one to which an electronic musical instrument is connected, and is equipped with a confirmation means for confirming, when the connection of the electronic musical instrument is confirmed, whether the firmware of the electronic musical instrument is compatible with the electronic device, a transmission means for transmitting firmware compatible with the electronic device to the electronic musical instrument if the confirmation means determines that the firmware of the electronic musical instrument is not compatible with the electronic device, and an instruction means for transmitting to the electronic musical instrument an instruction to update the firmware transmitted by the transmission means.

[0007] The firmware update method of the present invention is a method executed by an electronic device to which an electronic musical instrument is connected, and includes a confirmation step for confirming, when the connection of the electronic musical instrument is confirmed, whether the firmware of the electronic musical instrument is compatible with the electronic device; a transmission step for transmitting firmware compatible with the electronic device to the electronic musical instrument if the firmware of the electronic musical instrument is not compatible with the electronic device in the confirmation step; and an instruction step for transmitting an instruction to the electronic musical instrument to update the firmware transmitted in the transmission step.

[0008] The firmware update program of the present invention is a program that causes a computer to which an electronic musical instrument is connected to execute a firmware update process for the electronic musical instrument, and causes the computer to execute the following steps when the connection of the electronic musical instrument is confirmed: a confirmation step of confirming whether the firmware of the electronic musical instrument is compatible; a transmission step of transmitting compatible firmware to the electronic musical instrument if the firmware of the electronic musical instrument is not compatible in the confirmation step; and an instruction step of transmitting an instruction to the electronic musical instrument to update the firmware transmitted in the transmission step. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 2 is a diagram illustrating the appearance of a sound source device. [Figure 2]FIG. 2A is a block diagram showing the electrical configuration of a sound source device, and FIG. 2B is a diagram showing a model of a firm table. [Figure 3] FIG. 2 is a block diagram showing the electrical configuration of the electronic drum. [Figure 4] FIG. 2 is a functional block diagram of the sound source device. [Figure 5] 10 is a flowchart of a process at the time of attachment. [Figure 6] 10 is a flowchart of an update process. [Figure 7] 10 is a flowchart of a hitting process. DETAILED DESCRIPTION OF THE INVENTION

[0010] Preferred embodiments will be described below with reference to the accompanying drawings. An overview of a sound source device 1 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing the external appearance of the sound source device 1. The sound source device 1 is an electronic device that outputs (emits) musical tones based on performance information received from an electronic musical instrument such as an electronic drum 30. The sound source device 1 is provided with an LCD 2 that displays various setting values ​​and the like, and setting keys 3 through which instructions from the user H are input.

[0011] An electronic drum 30 and an electronic cymbal 40 are connected to the sound source device 1. The electronic drum 30 is an electronic percussion instrument (electronic musical instrument) that transmits performance information corresponding to strikes on the striking surface by the user H to the sound source device 1, and the electronic cymbal 40 is an electronic percussion instrument (electronic musical instrument) that transmits performance information corresponding to strikes on the striking surface by the user H to the sound source device 1. In this embodiment, an electronic hi-hat that imitates a hi-hat is used as the electronic cymbal 40, but this is not limiting, and an electronic cymbal that imitates another cymbal, such as a ride cymbal, may also be used as the electronic cymbal 40.

[0012] The electronic drum 30 and the electronic cymbal 40 each store firmware, and the firmware performs various processes, such as creating performance information when struck and transmitting the created performance information to the sound source device 1. However, since the electronic drum 30 or the electronic cymbal 40 connected to the sound source device 1 operate in cooperation with each other, if the electronic drum 30 or the electronic cymbal 40 stores firmware that is not compatible with the sound source device 1, the electronic drum 30 or the electronic cymbal 40 will generate performance information that the sound source device 1 cannot analyze and transmit it to the sound source device 1, which could cause the sound source device 1 to malfunction.

[0013] Therefore, in this embodiment, when an electronic drum 30 or an electronic cymbal 40 is connected to a sound source device 1 and the firmware for these is not compatible with the sound source device 1, the firmware for the electronic drum 30 or the electronic cymbal 40 is updated to one that is compatible with the sound source device 1, thereby reducing the effort required for user H to update the firmware.

[0014] Next, the electrical configuration of the sound source device 1 and the electronic drum 30 will be described with reference to Figures 2 and 3. First, the electrical configuration of the sound source device 1 will be described with reference to Figure 2. Figure 2(a) is a block diagram showing the electrical configuration of the sound source device 1. The sound source device 1 has a CPU 10, a flash ROM 11, a RAM 12, the LCD 2 and setting keys 3, an external input / output device 13, a sound source 14, and a DSP (Digital Signal Processor) 15, all of which are connected via a bus line 16. A DAC (Digital Analog Converter) 17 is connected to the DSP 15, an amplifier 18 is connected to the DAC 17, and a speaker 19 is connected to the amplifier 18.

[0015] The CPU 10 is a computing device that controls each unit connected by the bus line 16. The flash ROM 11 is a rewritable nonvolatile memory that has a control program 11a and a firmware table 11b. When the control program 11a is executed by the CPU 10, the attach process shown in Fig. 5 is executed. The firmware table 11b will be described with reference to Fig. 2(b).

[0016] 2(b) is a diagram showing a model of the firmware table 11b. The firmware table 11b stores, for each electronic musical instrument, model information, incompatible versions, and update data in association with each other. The model information is information that is uniquely assigned to each model of electronic musical instrument. The type of electronic musical instrument in question is identified based on this model information.

[0017] The incompatible version stores the latest firmware version of the electronic musical instrument that is incompatible with the sound source device 1. In this embodiment, firmware versions are numbered in ascending order, with larger versions representing newer firmware. Since the incompatible version stores the latest firmware version that is incompatible with the sound source device 1, firmware versions lower than the incompatible version are considered to be incompatible with the sound source device 1.

[0018] The update data stores a combination of firmware compatible with the sound source device 1 in the electronic musical instrument and a command (hereinafter referred to as an "update command") for updating the firmware in the electronic musical instrument. In this embodiment, the update data is configured as an SMF (Standard MIDI File) file incorporating the firmware and the update command.

[0019] Note that the firmware version is not limited to using numbers assigned in ascending order, but may also use numbers assigned in descending order, or random numbers.Furthermore, the firmware version is not limited to using numbers, but may also use other types of characters such as alphabets or kanji, or may use a mixture of numbers, alphabets, and kanji.

[0020] Furthermore, the update data is not limited to SMF files, but may be other types of data incorporating firmware and update instructions. Also, the update instructions may be stored in the electronic musical instrument in advance, and the update data may consist of firmware only.

[0021] Returning to Figure 2(a), the RAM 12 is a memory that stores various types of work data, flags, etc. in a rewritable manner when the CPU 10 executes programs such as the control program 11a. The external input / output device 13 is a device that inputs and outputs information from connected external devices. Electronic musical instruments such as an electronic drum 30 and an electronic cymbal 40 are connected to the external input / output device 13, and firmware is transmitted from the sound source device 1 to the electronic musical instruments via the external input / output device 13, and performance information from the electronic musical instruments is received by the sound source device 1.

[0022] In this embodiment, USB (registered trademark) is used as the communication standard for the external input / output device 13, but the external input / output device 13 may be configured to use another communication standard, or may be configured to input and output information from external devices via wireless communication.

[0023] The sound source 14 is a device that outputs waveform data corresponding to performance information input from the CPU 10. The DSP 15 is a calculation device that processes the waveform data input from the sound source 14. The DAC 17 is a conversion device that converts the waveform data input from the DSP 15 into analog waveform data. The amplifier 18 is an amplification device that amplifies the analog waveform data output from the DAC 17 with a predetermined gain. The speaker 19 is an output device that emits (outputs) the analog waveform data amplified by the amplifier 18 as musical tones.

[0024] Next, the electrical configuration of the electronic drum 30 will be described with reference to Fig. 3. Fig. 3 is a block diagram showing the electrical configuration of the electronic drum 30. Here, the electrical configuration of the electronic drum 30 will be described, but since the electrical configurations of other electronic musical instruments such as the electronic cymbal 40 are similar, detailed descriptions of these electrical configurations will be omitted.

[0025] Electronic drum 30 has a CPU 31, flash ROM 32, RAM 33, a strike sensor 34 that detects strikes on the striking surface, and an external input / output device 35, all of which are connected via a bus line 36. CPU 31 is a calculation device that controls each part connected via bus line 36.

[0026] Flash ROM 32 is a rewritable non-volatile memory that stores firmware 32a that controls each component of electronic drum 30, version information 32b that stores the version of that firmware, model information 32c that stores model information for electronic drum 30, and serial number 32d. Serial number 32d stores a serial number that is assigned individually to each electronic musical instrument, such as electronic drum 30 or electronic cymbal 40.

[0027] The RAM 33 is a memory that stores various types of work data, flags, etc. in a rewritable manner when the CPU 31 executes programs such as firmware. The external input / output device 35 is a device that inputs and outputs information from connected external devices. In this embodiment, the external input / output device 35 uses USB (registered trademark), which is the same communication standard as the external input / output device 13 of the sound source device 1 described above. However, other communication standards similar to those of the external input / output device 13 may also be used.

[0028] Next, the function of the sound source device 1 will be described with reference to Fig. 4. Fig. 4 is a functional block diagram of the sound source device 1. As shown in Fig. 4, the sound source device 1 has a confirmation means 500, a transmission means 501, and an instruction means 502.

[0029] The confirmation means 500 is a means for confirming whether the firmware of an electronic musical instrument 550, such as an electronic drum 30 or an electronic cymbal 40, is compatible with the sound source device 1 when the connection of the electronic musical instrument 550 is confirmed, and is realized by the CPU 10 and the external input / output device 13. The transmission means 501 is a means for transmitting firmware compatible with the sound source device 1 to the electronic musical instrument 550 when the confirmation means 500 determines that the firmware of the electronic musical instrument 550 is not compatible with the sound source device 1, and is realized by the CPU 10 and the external input / output device 13. The instruction means 502 is a means for transmitting an instruction to the electronic musical instrument 550 to update the firmware transmitted by the transmission means 501, and is realized by the CPU 10 and the external input / output device 13.

[0030] That is, when the sound source device 1 to which the electronic musical instrument 550 is connected confirms the connection of the electronic musical instrument 550, it checks whether the firmware of the electronic musical instrument 550 is compatible with the sound source device 1, and if the firmware of the electronic musical instrument 550 is not compatible with the sound source device 1, firmware compatible with the sound source device 1 is sent to the electronic musical instrument 550, and an instruction to update to that firmware is given to the electronic musical instrument 550. In this way, simply by connecting the sound source device 1 to the electronic musical instrument 550, the firmware of the electronic musical instrument 550 is updated to that compatible with the sound source device 1, thereby reducing the effort required of the user H to update the firmware of the electronic musical instrument 550.

[0031] Next, the processing executed by the CPU 10 of the sound source device 1 will be described with reference to Figures 5 to 7. Figure 5 is a flowchart of the attach processing. The attach processing is an event processing executed when an attach event of an electronic musical instrument, such as an electronic drum 30 or electronic cymbal 40, is detected after the sound source device 1 is powered on and an electronic musical instrument is attached (connected) to the external input / output device 13.

[0032] The attach process begins with receiving model information, version information, and serial number from the attached electronic musical instrument via the external input / output device 13 (S1). Specifically, an electronic musical instrument such as an electronic drum 30 attached to the sound source device 1 transmits the version, model information, and serial number stored in version information 32b, model information 32c, and serial number 32d (see FIG. 3), respectively, to the sound source device 1 via the external input / output device 35. The sound source device 1 receives the model information, version information, and serial number transmitted from the attached electronic musical instrument via the external input / output device 13.

[0033] After processing S1, the non-compatible version corresponding to the model information received in processing S1 is obtained from the firmware table 11b (S2), and it is confirmed whether the version received in processing S1 is equal to or lower than the non-compatible version obtained in processing S2 (S3).

[0034] In the process of S3, if it is confirmed that the received version is equal to or lower than the acquired non-compatible version (S3: Yes), the trigger cancel flag corresponding to the serial number received in the process of S1 is set to on (S4).

[0035] The trigger cancel flag is a flag provided for each serial number of an electronic musical instrument. If the trigger cancel flag is off, when performance information is received from an electronic musical instrument with that serial number, processing based on that performance information (for example, sounding of a musical tone based on that performance information) is carried out. On the other hand, if the trigger cancel flag is on, even if performance information is received from an electronic musical instrument with that serial number, that performance information is ignored and no processing based on that performance information is carried out.

[0036] After the process of S4, a message prompting the user to update the firmware of the attached electronic musical instrument is displayed on the LCD 2 (S5). After the process of S5, it is confirmed whether a command to update the firmware of the attached electronic musical instrument has been input from the user H via the setting key 3 (S6).

[0037] If it is confirmed in the process of S6 that a command to update the firmware of the attached electronic musical instrument has been input by user H (S6: Yes), the serial number received in the process of S1 is set as the update serial number. The update serial number is the serial number of the electronic musical instrument whose firmware is to be updated. After the process of S7, the update process (S8), which will be described later in FIG. 6, is executed.

[0038] If it is confirmed in the process of S3 that the received version is larger than the acquired incompatible version (S3: No), the processes of S4 to S8 are skipped. Also, if it is confirmed in the process of S7 that a command to update the firmware of the attached electronic musical instrument has not been input from user H (S6: No), the processes of S7 and S8 are skipped. After the processes of S3, S6, and S8, the attach process ends.

[0039] The update process of S8 will now be described with reference to Fig. 6. Fig. 6 is a flowchart of the update process. The update process begins by instructing the electronic musical instrument attached in the attach process of Fig. 5 to transition to update mode (S20). Update mode is a mode for updating firmware in the electronic musical instrument. The electronic musical instrument instructed to transition to update mode restarts in update mode and is attached to the sound source device 1 again.

[0040] After the process of S20, it is confirmed whether an attach event of an electronic musical instrument has been detected (S21). If the detection of an attach event of an electronic musical instrument is confirmed in the process of S21 (S21: Yes), model information and serial number are received from the attached electronic musical instrument via the external input / output device 13 (S22). Note that in this embodiment, if an attach event of an electronic musical instrument is detected in the process of S21, the attach process of Fig. 5 is configured not to be executed redundantly.

[0041] After the process of S22, it is checked (S23) whether the serial number received in the process of S22 matches the update serial number set in the process of S7 in Fig. 5. If it is checked in the process of S23 that the received serial number matches the update serial number (S23: Yes), it is checked whether the electronic musical instrument reattached in the process of S21 is in update mode (S24).

[0042] If it is confirmed in the process of S24 that the reattached electronic musical instrument is in update mode (S24: Yes), update data corresponding to the model information received in the process of S22 is obtained from the firmware table 11b (S25), and the obtained update data and an instruction to update the firmware using the update data are sent to the electronic musical instrument reattached in the process of S21 via the external input / output device 13 (S26).

[0043] The electronic musical instrument, having received the update data and the update instruction, updates its own firmware to the firmware included in the received update data in accordance with the update instruction included in the update data. If the firmware update is successful, the electronic musical instrument transmits an update success message to the sound source device 1 indicating this, and if the firmware update is unsuccessful, the electronic musical instrument transmits an update failure message to the sound source device 1 indicating this.

[0044] After the process of S26, it is checked whether a notification of update success has been received from the electronic musical instrument that was reattached in the process of S21 (S27). If a notification of update success has been received from the electronic musical instrument that was reattached in the process of S27 (S27: Yes), the trigger cancel flag for the update serial number (i.e., the serial number of the electronic musical instrument that was reattached) is set to OFF (S28). After the process of S28, a message indicating that the firmware update was successful is displayed on LCD 2 (S29).

[0045] If the process of S21 does not confirm the detection of an attach event of the electronic musical instrument (S21: No), if the process of S24 confirms that the reattached electronic musical instrument is not in update mode (S24: No), or if the process of S27 receives a notice of update failure from the reattached electronic musical instrument (S27: No), a message indicating that the firmware update has failed is displayed on LCD2 (S30).

[0046] In the process of S23, if it is confirmed that the received serial number does not match the updated serial number (S23: No), the processes of S24 to S30 are skipped. After the processes of S23, S29, and S30, the update process ends and the process returns to the attach process of FIG.

[0047] Next, the striking process will be described with reference to Fig. 7. Fig. 7 is a flowchart of the striking process. The striking process is an event process that is executed when performance information is received from an electronic musical instrument via the external input / output device 13 after the power of the sound source device 1 is turned on, and is a process that produces musical tones based on the received performance information.

[0048] The striking process begins by receiving a serial number from the electronic musical instrument that has received the performance information (S40). After the process of S40, it is determined whether the trigger cancel flag corresponding to the received serial number is off (S41).

[0049] In the process of S41, if it is confirmed that the trigger cancel flag corresponding to the received serial number is off (S41: Yes), a musical tone is generated based on the received performance information and the generated musical tone is output (S42).

[0050] On the other hand, if it is confirmed in the process of S41 that the trigger cancel flag corresponding to the received serial number is on (S41: No), the process of S42 is skipped. As a result, performance information received from an electronic musical instrument with firmware incompatible with the sound source device 1 and with the trigger cancel flag on is ignored, and musical tones are not generated or output based on that performance information. Note that, even in cases other than the generation and output of musical tones, any processing using performance information received from an electronic musical instrument with the trigger cancel flag on is ignored.

[0051] After the processing of S41 and S42, the hitting processing ends.

[0052] As described above, in this embodiment, when an electronic musical instrument is attached to the external input / output device 13 of the sound source device 1, model information and firmware version are received from the target electronic musical instrument, and the received version is compared with the incompatible version corresponding to the acquired model information in the firmware table 11b.

[0053] If the received version is lower than the incompatible version, i.e., if it is determined that the firmware stored in the target electronic musical instrument is not compatible with the sound source device 1 (FIG. 5, S3: Yes), update data for the target electronic musical instrument in firmware table 11b is obtained and sent to the target electronic musical instrument together with an instruction to perform an update using the update data (S4-S8). The target electronic musical instrument updates its firmware to the firmware in the update data sent from the sound source device 1 in accordance with the update command in the update data.

[0054] That is, when user H simply connects the sound source device 1 to the electronic musical instrument, the firmware of the electronic musical instrument is updated to be compatible with the sound source device 1. This eliminates the need for user H to obtain firmware for the electronic musical instrument and then update the firmware of the electronic musical instrument by operating a PC application or the like, thereby reducing the effort required for user H to update the firmware of the electronic musical instrument.

[0055] Furthermore, if the received version is an incompatible version or lower, the trigger cancel flag corresponding to the serial number of the target electronic musical instrument is set to ON (FIG. 5, S4), and the trigger cancel flag is set to OFF, i.e., musical tones based on the performance information received from the target electronic musical instrument are not produced, and the performance information is ignored (FIG. 7, S41) until the firmware of the target electronic musical instrument is updated to one compatible with the sound source device 1 (FIG. 6, S28). This makes it possible to prevent the sound source device 1 from malfunctioning due to invalid performance information received from an electronic musical instrument with firmware that is incompatible with the sound source device 1.

[0056] Furthermore, if the received version is greater than the incompatible version and it is determined that the firmware stored in the target electronic musical instrument is compatible with the sound source device 1 (FIG. 5, S3: No), the firmware update of the target electronic musical instrument by the sound source device 1 is omitted. That is, firmware updates are omitted for electronic musical instruments in which firmware compatible with the sound source device 1 is stored, and the period during which user H is unable to use the electronic musical instrument due to unnecessary firmware updates can be avoided, thereby preventing a decrease in usability of the electronic musical instrument for user H.

[0057] The above has been explained based on the above embodiment, but it can be easily imagined that various improvements and modifications are possible.

[0058] In the above embodiment, when the version of the attached electronic musical instrument is equal to or lower than the incompatible version, the firmware of the electronic musical instrument is updated using the update data stored in the firmware table 11b, but this is not limited to this. For example, regardless of the version of the attached electronic musical instrument, the firmware of the attached electronic musical instrument may always be updated using the update data stored in the firmware table 11b.

[0059] In the above embodiment, the performance information received from an electronic musical instrument whose trigger cancel flag is set to on is ignored, and no musical tones are generated based on that performance information, but this is not limited to this. For example, musical tones may be generated based on the performance information received from the electronic musical instrument regardless of the state of the trigger cancel flag.

[0060] In the above embodiment, electronic percussion instruments such as the electronic drum 30 and the electronic cymbal 40 are connected to the sound source device 1 as electronic musical instruments, but this is not limiting. For example, other electronic musical instruments such as an electronic tambourine or an electronic shaker may be connected to the sound source device 1, and the firmware of these may be updated from the sound source device 1.

[0061] In the above embodiment, the electronic device is the sound source device 1, but this is not limiting. For example, the electronic device may be an electronic piano to which a damper pedal is connected, and the firmware of the damper pedal may be updated from the electronic piano. Alternatively, the electronic device may be a wireless transmitter for an electric guitar to which wireless headphones are connected, and the firmware of the wireless headphones may be updated from the wireless transmitter.

[0062] In the above embodiment, update data including firmware compatible with the electronic musical instrument is stored in the firmware table 11b, but this is not limited to this. For example, update data may be stored on a server on the Internet, and if the firmware of the electronic musical instrument is not compatible with the sound source device 1, update data including compatible firmware may be received from the server.

[0063] In the above embodiment, the control program 11a is stored in the flash ROM 11 of the sound source device 1 and is configured to run on the sound source device 1. However, this is not necessarily limited to this, and the control program 11a may also be configured to run on other computers such as a PC (personal computer), a mobile phone, a smartphone, or a tablet terminal. In this case, the PC, mobile phone, or the like may be provided with a device similar to the external input / output device 13 so that it can be connected to an electronic musical instrument such as the electronic drum 30. [Explanation of symbols]

[0064] 1 Sound source device (electronic equipment) 11a Control program (firmware update program) 11b Farm table (storage means) 30 Electronic Drums (Electronic Instruments) 40 Electronic Cymbal (Electronic Instrument) S3 Confirmation method, update omission method, confirmation step S23 Identification means S26: Transmission means, instruction means, transmission step, instruction step S41 Ignoring measures

Claims

1. An electronic device to which an electronic musical instrument is connected, a confirmation means for confirming whether firmware of the electronic musical instrument is compatible with the electronic device when the connection of the electronic musical instrument is confirmed; a transmitting means for transmitting firmware compatible with the electronic device to the electronic musical instrument when the verifying means determines that the firmware of the electronic musical instrument is not compatible with the electronic device; an instruction unit for transmitting an instruction to update the firmware transmitted by the transmission unit to the electronic musical instrument;

2. a storage means for storing firmware suitable for each of the electronic musical instruments to be connected; 2. The electronic device according to claim 1, wherein the transmitting means transmits firmware corresponding to the connected electronic musical instrument from among firmware stored in the storage means to the electronic musical instrument.

3. 2. The electronic device according to claim 1, further comprising an update omission means for omitting the transmission of the firmware by the transmission means and the transmission of the update instruction by the instruction means when the confirmation means determines that the firmware of the electronic musical instrument is compatible with the electronic device.

4. 4. The electronic device according to claim 1, further comprising: an ignoring means for ignoring performance information received from the electronic musical instrument if the confirmation means determines that the firmware of the electronic musical instrument is not compatible with the electronic device.

5. 2. The electronic device according to claim 1, wherein the electronic device is configured as an electronic musical instrument separate from the electronic musical instrument to which it is connected.

6. an identification unit for identifying the electronic musical instrument for which the firmware is to be updated based on a serial number assigned to each electronic musical instrument; 2. The electronic device according to claim 1, wherein the transmitting means transmits firmware compatible with the electronic device to the electronic musical instrument when the confirmation means determines that the firmware of the electronic musical instrument is incompatible with the electronic device and the identification means identifies the electronic musical instrument as being subject to a firmware update.

7. A firmware update method executed in an electronic device to which an electronic musical instrument is connected, comprising: a confirmation step of confirming whether firmware of the electronic musical instrument is compatible with the electronic device when the connection of the electronic musical instrument is confirmed; a transmitting step of transmitting firmware compatible with the electronic device to the electronic musical instrument if the firmware of the electronic musical instrument is not compatible with the electronic device in the checking step; a command step of transmitting to the electronic musical instrument a command to update the firmware transmitted in the transmitting step;

8. 1. A firmware update program for causing a computer to which an electronic musical instrument is connected to execute a firmware update process for the electronic musical instrument, the program comprising: a confirmation step of confirming whether firmware of the electronic musical instrument is compatible when the connection of the electronic musical instrument is confirmed; a transmitting step of transmitting compatible firmware to the electronic musical instrument if the firmware of the electronic musical instrument is not compatible in the checking step; and an instruction step of transmitting to the electronic musical instrument an instruction to update the firmware transmitted in the transmitting step.

Images