Electronic equipment, firmware updating method and computer readable storage medium

By setting up confirmation, sending, and instruction components in electronic devices, the firmware of electronic musical instruments can be automatically updated, solving the problem of cumbersome user operations and realizing the convenience and automation of firmware updates.

CN121597237APending Publication Date: 2026-03-03ROLAND CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202511048633.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-08-20
Filing Date
2025-07-29
Publication Date
2026-03-03

AI Technical Summary

Technical Problem

Updating the firmware of electronic musical instruments from a PC is a cumbersome process for users, requiring them to manually obtain and specify the appropriate firmware.

Method used

By setting up confirmation, sending, and instruction components in the electronic device, the system automatically confirms whether the firmware of the electronic musical instrument is suitable, sends the appropriate firmware, and instructs for an update.

Benefits of technology

It simplifies the firmware update process for electronic musical instruments, reduces user operations, and ensures the automation and convenience of firmware updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121597237A_ABST
    Figure CN121597237A_ABST
Patent Text Reader

Abstract

The invention provides an electronic device, a firmware updating method, and a computer readable storage medium capable of reducing the time of a user for updating the firmware of an electronic musical instrument. When an electronic musical instrument is attached to an external input / output device (13) of a sound source device (1), type information and a version of firmware are received from the electronic musical instrument as a target, and the received version is compared with a non-corresponding version in a firmware table (11b). If the acquired version is a non-corresponding version or less, update data for the target electronic musical instrument in the firmware table (11b) is acquired, and the update data and an instruction to update using the update data are transmitted to the target electronic musical instrument. Therefore, the user (H) can update the firmware of the electronic musical instrument to the firmware suitable for the sound source device (1) only by connecting the sound source device (1) to the target electronic musical instrument, so that the time of the user (H) spent on updating the firmware of the electronic musical instrument can be reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to an electronic device, a firmware update method, and a computer-readable storage medium. Background Technology

[0002] Firmware is incorporated into electronic musical instruments such as electronic drums that are connected to a sound source device. Conventionally, for example, as shown in Non-Patent Document 1, a personal computer (PC) is connected to the electronic percussion instrument, and the firmware of the electronic instrument is updated from the PC application.

[0003] [Existing Technical Documents]

[0004] [Non-patent literature]

[0005] [Non-Patent Document 1] UpdSMF, a dedicated simple SMF player, [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

[0006] [The problem the invention aims to solve]

[0007] However, when updating electronic musical instruments from a PC, it is necessary to obtain firmware suitable for the instrument and specify that firmware in the application. Therefore, the user experience becomes cumbersome when updating firmware.

[0008] The present invention was made to solve the aforementioned problems, and its purpose is to provide an electronic device, a firmware update method, and a computer-readable storage medium that can reduce the time spent by users on firmware updates for electronic musical instruments.

[0009] [Technical means to solve the problem]

[0010] To achieve the aforementioned objective, the electronic device of the present invention is connected to an electronic musical instrument and includes: a confirmation component that, upon confirming the connection of the electronic musical instrument, confirms whether the firmware of the electronic musical instrument is suitable for the electronic device; a transmission component that, if the confirmation component confirms that the firmware of the electronic musical instrument is not suitable for the electronic device, transmits firmware suitable for the electronic device to the electronic musical instrument; and an instruction component that transmits an instruction for updating the firmware, transmitted by the transmission component, to the electronic musical instrument.

[0011] The firmware update method of the present invention is performed by an electronic device connected to an electronic musical instrument, and includes: a confirmation step, in which, if the connection of the electronic musical instrument is confirmed, the firmware of the electronic musical instrument is confirmed to be suitable for the electronic device; a sending step, in which, if the confirmation step confirms that the firmware of the electronic musical instrument is not suitable for the electronic device, firmware suitable for the electronic device is sent to the electronic musical instrument; and an instruction step, in which an instruction for firmware update sent in the sending step is sent to the electronic musical instrument.

[0012] Furthermore, the computer-readable storage medium of the present invention stores a firmware update program. The firmware update program is a program that causes a computer connected to an electronic musical instrument to perform firmware update processing for the electronic musical instrument, and causes the computer to perform: a confirmation step, in which, if the connection of the electronic musical instrument is confirmed, confirms whether the firmware of the electronic musical instrument is suitable; a sending step, in which, if the confirmation step confirms that the firmware of the electronic musical instrument is unsuitable, sends suitable firmware to the electronic musical instrument; and an instruction step, in which an instruction for firmware update sent in the sending step is sent to the electronic musical instrument. Attached Figure Description

[0013] Figure 1 It is a diagram showing the appearance of the sound source device.

[0014] Figure 2A This is a block diagram showing the electrical structure of the sound source device. Figure 2B This is a schematic diagram illustrating the firmware table.

[0015] Figure 3 This is a block diagram showing the electrical structure of the electronic drum.

[0016] Figure 4 This is a functional block diagram of the sound source device.

[0017] Figure 5 This is a flowchart of the attachment process.

[0018] Figure 6 This is a flowchart of the update process.

[0019] Figure 7 This is a flowchart of the attack and handling process.

[0020] Explanation of icon numbers

[0021] 1: Audio source device (electronic device)

[0022] 11a: Control program (firmware updater)

[0023] 11b: Firmware Table (Storage Component)

[0024] 30: Electronic drums (electronic musical instruments)

[0025] 40: Electronic cymbals (electronic musical instruments)

[0026] S3: Confirm components, update omitted components, confirm steps

[0027] S23: Identification Components

[0028] S26: Transmitting component, indicating component, transmitting step, indicating step

[0029] S41: Ignore components Detailed Implementation

[0030] The preferred embodiments will now be described with reference to the accompanying drawings. Figure 1 An overview of the sound source device 1 in this embodiment will be described. Figure 1 This is a diagram showing the appearance of the sound source device 1. The sound source device 1 is an electronic device that outputs (emits) musical sounds based on performance information received from electronic musical instruments such as the electronic drum 30. The sound source device 1 is equipped with a liquid crystal display (LCD) 2 for displaying various settings and other parameters, and a setting key 3 for inputting instructions from the user H.

[0031] 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 sends performance information corresponding to the user H's striking the percussion surface to the sound source device 1. The electronic cymbal 40 is an electronic percussion instrument (electronic musical instrument) that sends performance information corresponding to the user H's striking the percussion surface to the sound source device 1. In this embodiment, an electronic hi-hat that imitates the hi-hat is used as the electronic cymbal 40, but it is not limited to this. Electronic cymbals that imitate other cymbals such as the ride cymbal can also be used as the electronic cymbal 40.

[0032] Firmware is stored in the electronic drum 30 and electronic cymbals 40 respectively. Various processes are performed using this firmware, such as generating performance information upon being struck or sending the generated performance information to the sound source device 1. Furthermore, since the sound source device 1 operates collaboratively with the connected electronic drum 30 or electronic cymbals 40, there is a concern that if firmware unsuitable for the sound source device 1 is stored in the electronic drum 30 or electronic cymbals 40, the sound source device 1 may malfunction due to the generation of performance information that the electronic drum 30 or electronic cymbals 40 cannot analyze.

[0033] Therefore, in this embodiment, when the electronic drum 30 or electronic cymbal 40 is connected to the sound source device 1 and their firmware is not suitable for the sound source device 1, the user H's time spent on firmware updates can be reduced by updating the firmware of the electronic drum 30 or electronic cymbal 40 to firmware suitable for the sound source device 1.

[0034] Next, refer to Figure 2A , Figure 2B , Figure 3 The electrical structure of the sound source device 1 and the electronic drum 30 will be explained. First, refer to... Figure 2A , Figure 2B The electrical structure of the sound source device 1 will be explained. Figure 2A This is a block diagram showing the electrical structure of the audio source device 1. The audio source device 1 includes a central processing unit (CPU) 10, a read-only memory (ROM) 11, a random access memory (RAM) 12, the LCD 2 and setting keys 3, an external input / output device 13, an audio source 14, and a digital signal processor (DSP) 15, all connected via a bus 16. A digital-to-analog converter (DAC) 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.

[0035] CPU 10 is a computing device that controls the various components connected via bus 16. Flash ROM 11 is a rewritable non-volatile memory and contains a control program 11a and a firmware table 11b. When CPU 10 executes control program 11a, it executes... Figure 5 Attachment handling. See [reference]. Figure 2B The firmware table 11b is explained.

[0036] Figure 2B This is a schematic diagram illustrating firmware table 11b. In firmware table 11b, corresponding storage is established for each electronic musical instrument, including model information, non-corresponding versions, and update data. Model information is uniquely assigned to each electronic musical instrument. Based on this model information, the type of electronic musical instrument being tested is identified.

[0037] The firmware version of the electronic musical instrument, which is not suitable for the sound source device 1, is stored in the non-corresponding version. In this embodiment, the firmware version is assigned an ascending number, with a higher version indicating a newer firmware. Since the latest firmware version that is not suitable for the sound source device 1 is stored in the non-corresponding version, firmware versions below the non-corresponding version are considered unsuitable for the sound source device 1.

[0038] The update data stores data that combines firmware suitable for the sound source device 1 in the electronic musical instrument with commands (hereinafter referred to as "update commands") for updating the firmware in the electronic musical instrument. In this embodiment, the update data consists of a Standard Musical Instrument Digital Interface File (SMF) that incorporates the firmware and the update command.

[0039] Furthermore, the firmware version is not limited to using numbers assigned in ascending order; for example, numbers assigned in descending order or random numbers can be used. Additionally, the firmware version is not limited to using numbers; it can use letters, Chinese characters, or other types of characters, or a mixture of numbers, letters, or Chinese characters.

[0040] Furthermore, the update data is not limited to data composed of SMF; it can also be other forms of data that incorporate firmware and update commands. Alternatively, update commands can be pre-stored in the electronic instrument, with only the update data set as firmware.

[0041] Return to Figure 2A RAM 12 is a memory that can be rewritten to store various workpiece data or flags when the CPU 10 executes programs such as control program 11a. External input / output device 13 is a device for inputting / outputting information from connected external devices. When an electronic musical instrument such as electronic drum 30 or electronic cymbals 40 is connected to external input / output device 13, firmware is sent from sound source device 1 to the electronic musical instrument, or sound source device 1 receives performance information from the electronic musical instrument.

[0042] 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 also be configured to use other communication standards, or to input / output information from external devices via wireless communication.

[0043] Sound source 14 is a device that outputs waveform data corresponding to the performance information input from CPU 10. DSP 15 is a computing device for processing the waveform data input from sound source 14. DAC 17 is a conversion device that converts the waveform data input from DSP 15 into analog waveform data. Amplifier 18 is an amplification device that amplifies the analog waveform data output from DAC 17 with a specified gain. Speaker 19 is an output device that emits (outputs) the analog waveform data amplified by amplifier 18 in the form of musical sounds.

[0044] Next, refer to Figure 3 The electrical structure of the electronic drum 30 is explained. Figure 3 This is a block diagram showing the electrical structure of the electronic drum 30. The electrical structure of the electronic drum 30 will be explained here, but since the electrical structures of other electronic musical instruments such as the electronic cymbals 40 are also the same, detailed descriptions of their electrical structures are omitted.

[0045] The electronic drum 30 has a CPU 31, a flash ROM 32, a RAM 33, a strike sensor 34 for detecting the impact on the striking surface, and an external input / output device 35, all connected via a bus 36. The CPU 31 is a computing device that controls the various components connected via the bus 36.

[0046] The flash ROM 32 is a rewritable non-volatile memory and includes: firmware 32a, storing firmware that controls various parts of the electronic drum 30; version information 32b, storing the version of the firmware; model information 32c, storing model information of the electronic drum 30; and serial number 32d. The serial number 32d stores a unique number assigned to each electronic instrument, such as the electronic drum 30 or the electronic cymbals 40.

[0047] RAM 33 is a memory that stores various workpiece data or flags that can be rewritten when the CPU 31 executes firmware or other programs. External input / output device 35 is a device for inputting / outputting information from connected external devices. In this embodiment, USB (registered trademark), the same communication standard as the external input / output device 13 of the audio source device 1, is used as the external input / output device 35; however, other communication standards may be used as long as they are the same as those of the external input / output device 13.

[0048] Next, refer to Figure 4 The function of the sound source device 1 will be explained. Figure 4 This is a functional block diagram of the sound source device 1. For example... Figure 4 As shown, the sound source device 1 has a confirmation component 500, a transmission component 501, and an indication component 502.

[0049] The confirmation component 500, implemented by the CPU 10 and the external input / output device 1, verifies whether the firmware of the electronic musical instrument 550, such as the electronic drum 30 or electronic cymbals 40, is suitable for the sound source device 1 when the connection of the electronic musical instrument 550 is confirmed. The sending component 501, implemented by the CPU 10 and the external input / output device 13, sends firmware suitable for the sound source device 1 to the electronic musical instrument 550 when the confirmation component 500 determines that the firmware of the electronic musical instrument 550 is not suitable for the sound source device 1. Furthermore, the instruction component 502 sends the firmware update instruction sent by the sending component 501 to the electronic musical instrument 550, implemented by the CPU 10 and the external input / output device 13.

[0050] That is, in the sound source device 1 connected to the electronic musical instrument 550, upon confirming the connection of the electronic musical instrument 550, it is determined whether the firmware of the electronic musical instrument 550 is suitable for the sound source device 1. If the firmware of the electronic musical instrument 550 is not suitable for the sound source device 1, firmware suitable for the sound source device 1 is sent to the electronic musical instrument 550, and the electronic musical instrument 550 is instructed to update the firmware. Thus, by simply connecting the sound source device 1 to the electronic musical instrument 550, the firmware of the electronic musical instrument 550 is updated to be suitable for the sound source device 1, thereby reducing the time spent by the user H on firmware updates of the electronic musical instrument 550.

[0051] Next, refer to Figures 5-7 The processing performed by the CPU 10 of the audio source device 1 will be described. Figure 5 This is a flowchart of the attachment process. The attachment process is an event that is executed when an electronic musical instrument, such as the electronic drum 30 or electronic cymbal 40, is attached (connected) to an external input / output device 13 after the power of the sound source device 1 is turned on, and an attachment event of the electronic musical instrument is detected.

[0052] During attachment, the process first receives model information, version, and serial number from the attached electronic instrument via external input / output device 13 (S1). Specifically, electronic instruments such as the electronic drum 30 attached to the sound source device 1 send the version information 32b, model information 32c, and serial number 32d stored in the external input / output device 35 to the sound source device 1 (see reference). Figure 3 The audio source device 1 receives the model information, version, and serial number from the attached electronic musical instrument via the external input / output device 13.

[0053] After processing in S1, a non-corresponding version matching the device information received in processing in S1 is obtained from firmware table 11b (S2), and it is confirmed whether the version received in processing in S1 is a non-corresponding version or lower than the version obtained in processing in S2 (S3).

[0054] In the S3 process, if it is confirmed that the received version is a version below the one that was not obtained (S3: Yes), the trigger cancellation flag corresponding to the serial number received in the S1 process is set to on (S4).

[0055] The trigger cancellation flag is a flag set for each serial number of an electronic musical instrument. When the trigger cancellation flag is off, if performance information is received from the electronic musical instrument of that serial number, processing based on the performance information (e.g., the production of musical notes based on the performance information) is performed. On the other hand, when the trigger cancellation flag is on, even if performance information is received from the electronic musical instrument of that serial number, the performance information is ignored, and no processing based on the performance information is performed.

[0056] After processing S4, a message reminding the attached electronic instrument to update its firmware is displayed on LCD 2 (S5). After processing S5, it is confirmed whether the user H has entered an instruction to update the firmware of the attached electronic instrument via setting key 3 (S6).

[0057] In the S6 process, if it is confirmed that user H has input an instruction to update the firmware of the attached electronic instrument (S6: Yes), the serial number received in the S1 process is set as the update serial number. The update serial number is the serial number of the electronic instrument whose firmware is to be updated. After the S7 process, execution... Figure 6 The update process described later (S8).

[0058] In step S3, if it is confirmed that the received version is greater than the non-corresponding version obtained (S3: No), steps S4 to S8 are skipped. Additionally, in step S7, if it is confirmed that no instruction to update the firmware of the attached electronic instrument has been input by user H (S6: No), steps S7 and S8 are skipped. After steps S3, S6, and S8, the attachment process ends.

[0059] Here, refer to Figure 6 The update process for S8 is explained. Figure 6 This is a flowchart of the update process. The update process first... Figure 5 During the attachment process, the attached electronic instrument is instructed to transition to update mode (S20). Update mode is a mode used for firmware updates in the electronic instrument. The electronic instrument instructed to transition to update mode restarts in update mode and is reattached to the sound source device 1.

[0060] After processing S20, it is confirmed whether an electronic musical instrument attachment event has been detected (S21). In processing S21, if the detection of an electronic musical instrument attachment event is confirmed (S21: Yes), model information and serial number are received from the attached electronic musical instrument via the external input / output device 13 (S22). Furthermore, in this embodiment, if an electronic musical instrument attachment event is detected in processing S21, the process is configured to not repeat. Figure 5 Attachment processing.

[0061] After processing in S22, confirm whether the sequence number received in S22 processing matches... Figure 5 The updated serial number set in S7 is consistent with the updated serial number (S23). In the process of S23, if it is confirmed that the received serial number is consistent with the updated serial number (S23: Yes), it is confirmed whether the electronic musical instrument reattached in the process of S21 is in update mode (S24).

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

[0063] Upon receiving update data and an update instruction, the electronic musical instrument updates its firmware to the firmware contained in the received update data, according to the update command included in the update data. If the firmware update is successful, the electronic musical instrument sends a message indicating successful update to the sound source device 1; if the firmware update fails, it sends a message indicating update failure to the sound source device 1.

[0064] After processing S26, it is confirmed whether the electronic instrument reattached in S21 has received a successful update (S27). In processing S27, if the update is successful from the reattached electronic instrument (S27: Yes), the trigger cancellation flag for the update serial number (i.e., the serial number of the reattached electronic instrument) is set to off (S28). After processing S28, a message indicating that the firmware update was successful is displayed on LCD 2 (S29).

[0065] If the detection of the electronic instrument attachment event is not confirmed in the process of S21 (S21: No), if it is confirmed in the process of S24 that the reattached electronic instrument is not in update mode (S24: No), or if an update failure is received from the reattached electronic instrument in the process of S27 (S27: No), a message indicating that the firmware update has failed is displayed on LCD 2 (S30).

[0066] In the process of S23, if it is confirmed that the received sequence number does not match the updated sequence number (S23: No), the processes of S24 to S30 are skipped. After the processes of S23, S29, and S30, the update process ends and returns to the previous state. Figure 5 Attachment processing.

[0067] Next, refer to Figure 7 Explanation of the handling of the crackdown. Figure 7 This is a flowchart of the percussion processing. Percussion processing is an event processing that is performed after the power of the sound source device 1 is turned on and the playing information is received from the electronic musical instrument via the external input / output device 13. It is a process of emitting musical sounds based on the received playing information.

[0068] The striking process first receives the sequence number from the electronic instrument that received the performance information (S40). After processing in S40, it is confirmed whether the trigger cancellation flag corresponding to the received sequence number is off (S41).

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

[0070] On the other hand, in the S41 process, if it is confirmed that the trigger cancellation flag corresponding to the received sequence number is on (S41: No), the S42 process is skipped. Therefore, the performance information received from the electronic instrument whose trigger cancellation flag is on and whose firmware is unsuitable for the sound source device 1 is ignored, and the generation and output of musical tones based on the performance information are not performed. Furthermore, apart from the generation and output of musical tones, the processing using the performance information received from the electronic instrument whose trigger cancellation flag is on is also ignored.

[0071] After processing S41 and S42, the strike process ends.

[0072] As explained above, in this embodiment, when the electronic musical instrument is attached to the external input / output device 13 of the sound source device 1, the model information and firmware version are received from the electronic musical instrument, and the received version is compared with the non-corresponding version that matches the model information obtained in the firmware table 11b.

[0073] If it is determined that the received version is a non-corresponding version or lower, that is, the firmware stored in the electronic musical instrument being targeted is not suitable for the sound source device 1 ( Figure 5 S3: Yes), retrieve the update data for the target electronic instrument from firmware table 11b, and send it along with an instruction to perform an update using the update data to the target electronic instrument (S4-S8). In the target electronic instrument, update the firmware to the firmware in the update data sent from the sound source device 1 according to the update command in the update data.

[0074] That is, user H can update the firmware of the electronic instrument to be compatible with the sound source device 1 simply by connecting the sound source device 1 to the electronic instrument. Therefore, for example, user H does not need to obtain the firmware of the electronic instrument and operate a PC application to update the firmware of the electronic instrument, thus reducing the time spent by user H on updating the firmware of the electronic instrument.

[0075] Additionally, if the received version is a version lower than the corresponding version, the trigger cancellation flag corresponding to the serial number of the electronic instrument being targeted will be set to "on". Figure 5 S4), until the trigger cancellation flag is set to off, that is, until the firmware of the electronic musical instrument being tested is updated to be suitable for the sound source device 1. Figure 6 S28), does not produce musical notes based on performance information received from the electronic musical instrument being targeted, that is, ignores the performance information ( Figure 7 (S41). Thus, the situation where the sound source device 1 malfunctions due to improper playing information received from an electronic musical instrument whose firmware is not suitable for the sound source device 1 can be suppressed.

[0076] Furthermore, if it is determined that the received version is greater than the non-corresponding version and the firmware stored in the electronic musical instrument being targeted is suitable for the sound source device 1 ( Figure 5 S3: No), firmware updates for the electronic musical instrument based on the sound source device 1 are omitted. That is, by omitting firmware updates in the electronic musical instrument that stores firmware suitable for the sound source device 1, the period during which user H is unable to use the electronic musical instrument due to unnecessary firmware updates can be avoided, thus suppressing the reduction in the ease of use of the electronic musical instrument by user H.

[0077] The above description is based on the described embodiments, but it is easy to deduce that various improvements and modifications can be made.

[0078] In the described embodiment, if the version of the attached electronic instrument is a non-corresponding version or lower, the firmware of the electronic instrument is updated using the update data stored in firmware table 11b, but this is not a limitation. For example, regardless of the version of the attached electronic instrument, the firmware of the attached electronic instrument can always be updated using the update data stored in firmware table 11b.

[0079] In this embodiment, performance information received from an electronic instrument with the trigger cancellation flag set to "on" is ignored, and musical notes based on said performance information are not produced, but this is not a limitation. For example, musical notes based on performance information received from the electronic instrument can be produced regardless of the state of the trigger cancellation flag.

[0080] In the described embodiment, an electronic percussion instrument such as an electronic drum 30 and an electronic cymbal 40 is connected to the sound source device 1 as an electronic musical instrument, but it is not limited to this. For example, it may also be configured to connect other electronic musical instruments such as an electronic tambourine or an electronic shaker to the sound source device 1, and the firmware of these instruments can be updated from the sound source device 1.

[0081] Furthermore, in the described embodiment, the electronic device is configured as the sound source device 1, but it is not limited to this. For example, it may be configured as an electronic piano connected to a damper pedal, from which the firmware of the damper pedal can be updated. Alternatively, it may be configured as a wireless transmitter for an electric guitar connected to wireless headphones, from which the firmware of the wireless headphones can be updated.

[0082] In the described embodiment, update data containing firmware suitable for the electronic musical instrument is stored in firmware table 11b, but this is not a limitation. For example, update data may also be stored in a server on the Internet, and update data containing suitable firmware may be received from the server if the firmware of the electronic musical instrument is not suitable for the sound source device 1.

[0083] In the described embodiment, the control program 11a is configured to be stored in the flash memory ROM 11 of the sound source device 1 and run on the sound source device 1. However, it is not limited to this and may also be configured to run the control program 11a on other computers such as PCs (personal computers), mobile phones, smartphones, or tablets. In this case, it is sufficient as long as a device identical to the external input / output device 13 is provided in the PC or mobile phone and can be connected to an electronic musical instrument such as the electronic drum 30.

Claims

1. An electronic device connected to an electronic musical instrument, characterized in that it comprises: The verification component, upon confirming the connection of the electronic musical instrument, verifies whether the firmware of the electronic musical instrument is suitable for the electronic device. The sending component, if the confirmation component confirms that the firmware of the electronic instrument is not suitable for the electronic device, sends firmware suitable for the electronic device to the electronic instrument; as well as The instruction component sends an instruction for firmware update, which is sent by the transmission component, to the electronic musical instrument.

2. The electronic device according to claim 1, characterized in that, Includes a storage component that stores suitable firmware for each of the connected electronic musical instruments. The transmitting component sends the firmware corresponding to the connected electronic musical instrument from the firmware stored in the storage component to the electronic musical instrument.

3. The electronic device according to claim 1, characterized in that, The system includes an update omission component, which, when the confirmation component confirms that the firmware of the electronic musical instrument is suitable for the electronic device, omits the transmission of firmware based on the transmission component and the transmission of an update instruction based on the indication component.

4. The electronic device according to any one of claims 1 to 3, characterized in that, The system includes an ignore component that ignores performance information received from the electronic instrument if the confirmation component determines that the firmware of the electronic instrument is not suitable for the electronic device.

5. The electronic device according to claim 1, characterized in that, The electronic device is composed of an electronic musical instrument that is different from the connected electronic musical instrument.

6. The electronic device according to claim 1, characterized in that, The system includes an identification component that identifies the electronic instrument as the object to be updated in the firmware based on a serial number assigned to each instrument. When the confirmation component confirms that the firmware of the electronic instrument is not suitable for the electronic device, and the identification component identifies the electronic instrument as the object to be updated, the sending component sends firmware suitable for the electronic device to the electronic instrument.

7. A firmware update method, performed by an electronic device connected to an electronic musical instrument, the firmware update method being characterized by comprising: The confirmation step involves verifying whether the firmware of the electronic musical instrument is suitable for the electronic device, provided that the connection to the electronic musical instrument has been confirmed. In the sending step, if the confirmation step confirms that the firmware of the electronic instrument is not suitable for the electronic device, firmware suitable for the electronic device is sent to the electronic instrument. as well as The instruction step sends the firmware update instruction sent in the sending step to the electronic musical instrument.

8. A computer-readable storage medium storing a firmware update program that causes a computer connected to an electronic musical instrument to perform a firmware update process for the electronic musical instrument, characterized in that the firmware update program causes the computer to perform: The confirmation step involves verifying whether the firmware of the electronic instrument is suitable, provided that the connection to the electronic instrument has been confirmed. In the sending step, if the confirmation step confirms that the firmware of the electronic instrument is not suitable, a suitable firmware is sent to the electronic instrument. as well as The instruction step sends the firmware update instruction sent in the sending step to the electronic musical instrument.