IC Firmware Update Method
By converting the contractual requirement commands to USVDM and transmitting them through the USB Type-C interface, the issue of USB PD IC firmware update interface restrictions that do not support the USB PD 3.0 protocol is solved, and the feasibility of firmware updates is achieved.
Patent Information
- Application Number
- CN201910655055.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-07-19
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2039-07-19
AI Technical Summary
The prior art is difficult to update firmware through a non-USB Type-C interface for USB PD ICs that do not support the USB PD 3.0 protocol, and there is a problem of interface limitation.
The protocol request command of the host circuit is converted into unstructured vendor-defined message (USVDM) through the intermediary circuit and transmitted to the target circuit through the USB Type-C interface to realize firmware update operation and convert the responded USVDM into the protocol response command Return to the host circuit.
It implements IC firmware updates through the USB Type-C interface without supporting the USB PD 3.0 protocol, solves the interface restriction problem and ensures the feasibility of firmware updates.
Smart Images

Figure CN112241277B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an IC firmware update method, and more particularly to an IC firmware update method using an Unstructured Vendor Defined Message (USVDM). Background Art
[0002] For USB Power Delivery (USB PD) ICs that use a USB Type-C interface, the most convenient way to update the firmware is to perform the firmware update through the USB Type-C port according to the USB PD 3.0 protocol; if the firmware update is performed on the USB PD IC using other interfaces, various limitations will be encountered. For example, if the firmware update is performed through the System Management Bus (Smbus) / Inter-Integrated Circuit (I2C) interface or a traditional USB interface (non-USB Type-C interface), the USB PD IC may not be able to perform the firmware update because it does not support such an interface.
[0003] As described above, for a USB PD IC that does not support the USB PD 3.0 protocol but needs to perform firmware update through the Configuration Channel (CC) of the USB Type-C interface, the USB PD IC requires an appropriate firmware update method. Summary of the invention
[0004] An object of the present invention is to provide an IC firmware updating method to avoid the problems of the prior art.
[0005] An embodiment of the IC firmware update method of the present invention is performed by an intermediate circuit, and the embodiment includes the following steps: communicating with a target circuit to enter a preset mode; sending a status response message to the host circuit according to a status inquiry message of a host circuit to indicate entering the preset mode; after sending the status response message, receiving a first protocol request command of the host circuit; converting the first protocol request command into N request-end unstructured vendor defined messages (USVDM), and sending the N request-end USVDMs to the target circuit for the target circuit to perform a firmware update operation, wherein N is a positive integer; receiving N response-end USVDMs of the target circuit, the N response-end USVDMs corresponding to the N request-end USVDMs; and converting the N response-end USVDMs into a first protocol response command, and sending the first protocol response command to the host circuit.
[0006] Another embodiment of the IC firmware update method of the present invention is performed by a target circuit, and the embodiment includes the following steps: communicating with a host circuit to enter a preset mode; receiving N request-end USVDMs, where N is a positive integer; and performing a firmware update operation based on the N request-end USVDMs to generate N response-end USVDMs, and transmitting the N response-end USVDMs to the host circuit.
[0007] Another embodiment of the IC firmware update method of the present invention is performed by a host circuit, and the embodiment includes the following steps: communicating with an intermediate circuit to determine that the intermediate circuit enters a default mode; generating X first protocol request commands according to a firmware update program, and transmitting the X first protocol request commands to the intermediate circuit for the intermediate circuit to access a target circuit, where X is a positive integer; and receiving X first protocol response commands from the intermediate circuit, where the content of the X first protocol response commands originates from the target circuit. When the access data amount associated with the firmware update program is greater than K bytes, the step of generating the X first protocol request commands includes: generating a plurality of first protocol request commands as the X first protocol request commands according to the firmware update program, so that the access data amount associated with each of the X first protocol request commands is not greater than K bytes.
[0008] Another embodiment of the IC firmware update method of the present invention is performed by a host circuit, and the embodiment includes the following steps: communicating with a target circuit through a USB Type-C interface to enter a preset mode; generating N request ends USVDM according to a firmware update program, and transmitting the N request ends USVDM to the target circuit for the target circuit to perform a firmware update operation, wherein N is a positive integer; and receiving N response ends USVDM of the target circuit, wherein the N response ends USVDM correspond to the N request ends USVDM, wherein the N request ends USVDM and the N response ends USVDM comply with the USB Power Delivery (USB PD) 2.0 protocol.
[0009] The features, implementation and technical effects of the present invention are described in detail below with reference to the accompanying drawings as preferred embodiments. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 An embodiment of the IC firmware update device disclosed in the present invention is shown;
[0011] Figure 2 show Figure 1 An embodiment of the intermediate circuit;
[0012] Figure 3 Another embodiment of the IC firmware update device disclosed in the present invention is shown;
[0013] Figure 4 An embodiment of the IC firmware update method of the present invention is shown;
[0014] Figure 5 show Figure 4 A flowchart of the method;
[0015] Figure 6 show Figure 4 An example of the format of N requester / responder USVDMs used for write operations;
[0016] Figure 7 show Figure 4 An example of the format of N requester / responder USVDMs used for read operations;
[0017] Figure 8 Another embodiment of the IC firmware update method of the present invention is shown;
[0018] Fig. 9 Another embodiment of the IC firmware update method of the present invention is shown;
[0019] Fig.10 Another embodiment of the IC firmware update method of the present invention is shown; and
[0020] Fig.11 show Fig.10 Flowchart of the method.
[0021] Description of reference numerals:
[0022] 100 IC firmware update device
[0023] 110 Host circuit
[0024] 120 Intermediary Circuit
[0025] 130 Target Circuit
[0026] 210 First transceiver circuit
[0027] 220 first conversion circuit
[0028] 230 Second transmission and receiving circuit
[0029] 240 Second conversion circuit
[0030] 300 IC firmware update device
[0031] 310 Host circuit
[0032] 320 Target Circuit
[0033] Steps S410 to S460
[0034] Discover Identity (request)
[0035] Discover Identity (ack) Response to identity verification
[0036] Discover SVID(request) Find out the SVID request
[0037] Discover SVID(ack) Find the reply of SVID
[0038] Discover Mode (request) Discover mode request
[0039] Discover Mode (ack) Response to the discovery mode
[0040] Enter Mode (request) Enter mode request
[0041] Enter Mode (ack) Response to enter mode
[0042] USB / SMBUS CMD (Get IC Status request) USB / SMBUS status request command
[0043] USB / SMBUS CMD (Get IC status response) USB / SMBUS status response command
[0044] USB / SMBUS CMD(request) USB / SMBUS request command
[0045] PD USVDM (request) N request end USVDM
[0046] PD USVDM (response) N responding end USVDM
[0047] USB / SMBUS CMD(response) USB / SMBUS response command
[0048] Steps S810 to S830
[0049] Steps S910 to S930
[0050] Steps S1010 to S1030 DETAILED DESCRIPTION
[0051] The present disclosure includes an integrated circuit (IC) firmware update device and an IC firmware update method. The device and method can perform firmware update based on the USB Power Delivery (USB PD) 2.0 protocol and utilize an unstructured vendor defined message (USVDM) to perform firmware update through a configuration channel (Configuration Channel) of a USB Type-C interface; however, the implementation of the device and method is not limited to the above-mentioned protocol, message, and interface type, provided that the implementation is possible.
[0052] Figure 1 An embodiment of the IC firmware update device disclosed in the present invention is shown. Figure 1The IC firmware update device 100 includes a host circuit 110, an intermediate circuit 120, and a target circuit 130. The host circuit 110 is a circuit of a known or self-developed device (e.g., a computer), supporting a first interface (e.g., a non-USB Type-C interface) in accordance with a first protocol; the host circuit 110 is used to generate a first protocol request command according to a firmware update program, and transmit the first protocol request command to the intermediate circuit 120; an example of the first interface is one of the following interfaces: a USB Type-A interface; a USB Type-B interface; a USB Mini-A interface; a USB Mini-B interface; a USB Micro-A interface; a USB Micro-B interface; and a System Management Bus (SMBUS) interface. The intermediate circuit 120 is used to convert the first protocol request command into N request terminals USVDM, and transmit the N request terminals USVDM to the target circuit 130; the details of the intermediate circuit 120 are described below. The target circuit 130 is a circuit of a known or self-developed device (e.g., a power supply of an electronic device), supporting a second interface (e.g., a USB Type-C interface) in accordance with a second protocol (e.g., USB PD 2.0 protocol); the target circuit 130 performs a firmware update operation including a read / write operation according to the N request end USVDMs, and generates N response end USVDMs, and then transmits the N response end USVDMs to the intermediate circuit 120; in this embodiment, the target circuit 130 does not support the USB PD 3.0 protocol, but this is not an implementation limitation of the present invention. The operation details of the firmware update device 100 are shown in the method embodiment described later.
[0053] Figure 2 show Figure 1 An embodiment of the intermediate circuit 120 includes: a first transceiver circuit 210, used to receive a first protocol request command from the host circuit 110 through the first interface, and transmit a first protocol response command to the host circuit 110 through the first interface; a first conversion circuit 220, used to convert the first protocol request command into N request end USVDMs according to the first protocol and the second protocol, wherein N is a positive integer; a second transceiver circuit 230, used to transmit the N request end USVDMs to the target circuit 130 through the second interface, and receive N response end USVDMs from the target circuit 130 through the second interface; and a second conversion circuit 240, used to convert the N response end USVDMs into the first protocol response command according to the second protocol and the first protocol. The operation details of the intermediate circuit 120 are shown in the method embodiment described later.
[0054] Figure 3Another embodiment of the IC firmware updating device disclosed in the present invention is shown. Figure 3 The IC firmware update device 300 includes a host circuit 310 and a target circuit 320. The host circuit 310 is a circuit of a known or self-developed device (e.g., a computer), supporting a second interface (e.g., a USB Type-C interface) and complying with a second protocol (e.g., USB PD 2.0 protocol); the host circuit 310 is used to generate N request end USVDMs according to a firmware update procedure, and transmit the N request end USVDMs to the target circuit 320. The target circuit 320 is a circuit of a known or self-developed device (e.g., a power supply of an electronic device), supporting the second interface; the target circuit 320 performs a firmware update operation including a read / write operation according to the N request end USVDMs, and generates N response end USVDMs, and then transmits the N response end USVDMs to the host circuit 310; in this embodiment, the target circuit 320 does not support the USB PD 3.0 protocol, but this is not an implementation limitation of the present invention. The operation details of the firmware update device 300 are shown in the method embodiment described later.
[0055] Figure 4 An embodiment of the IC firmware update method of the present invention is shown. This embodiment can be implemented by an intermediate circuit (for example: Figure 2 The intermediate circuit 120) is executed, comprising the following steps:
[0056] Step S410: Communicate with a target circuit to enter a preset mode. An example of the target circuit is Figure 1 In one implementation example, the default mode is a modal operation mode; in order to enter the modal operation mode, the process of communicating with the target circuit is as follows: Figure 5 As shown, it includes: a request for identity discovery (Discover Identity(request)); a response for identity discovery (Discover Identity(ack)); a request for standard or vendor ID (SVID) discovery (Discover SVID(request)); a response for standard or vendor ID (Discover SVID(ack)); a request for mode discovery (Discover Mode(request)); a response for mode discovery (Discover Mode(ack)); a request for entering mode (Enter Mode(request)); and a response for entering mode (Enter Mode(ack)).
[0057] Step S420: According to a status inquiry message of a host circuit, a status reply message is sent to the host circuit to indicate entering the default mode. An example of the host circuit is Figure 1 In an implementation example, the status inquiry message is a USB / SMBUS status request command (USB / SMBUS CMD (Get IC Status request)) and the status reply message is a USB / SMBUS status response command (USB / SMBUS CMD (Get IC status response)). Figure 5 As shown, the term "USB" refers to a conventional USB other than USB Type-C. Since those skilled in the art can process the status inquiry message and generate the status reply message according to a known communication protocol (e.g., USB / SMBUS protocol) and a known communication technology (e.g., technology for generating packets according to the protocol) between the intermediate circuit and the host circuit, redundant descriptions are omitted here.
[0058] Step S430: After sending the status reply message, a first protocol request command of the host circuit is received. In an implementation example, the first protocol request command is a USB / SMBUS request command (USB / SMBUS CMD (request)). Figure 5 As shown, it is used to request data writing / reading. Since those skilled in the art can process the first protocol request command according to the known communication protocol (e.g., USB / SMBUS protocol) and known communication technology (e.g., technology for generating packets according to the protocol) between the intermediate circuit and the host circuit, redundant description is omitted here.
[0059] Step S440: convert the first protocol request command into N request terminals USVDM, and transmit the N request terminals USVDM to the target circuit, so that the target circuit can perform a firmware update operation, wherein N is a positive integer. In an implementation example, the N request terminals USVDM are USVDMs (PD USVDM (request)) that comply with the USB PD 2.0 protocol, such as Figure 5 shown.
[0060] Figure 6 An example of the format of each of the N request side USVDMs for a write operation is shown, including a request side USVDM header for carrying message information, a request side first vendor defined data object (VDO) for carrying write parameters, and M VDOs for carrying write data. Figure 6In an implementation example, the length of the request end USVDM header is four bytes, wherein the 16th to 31st bits are used to indicate the vendor identity (Vendor ID), the 15th bit is used to indicate the vendor defined message type (VDMType), the 8th to 14th bits are reserved bits, and the 0th to 7th bits are used to indicate the request command for writing into the storage circuit (e.g., flash memory) of the target circuit; the length of the first VDO of the request end is four bytes, wherein the 24th to 31st bits are used to indicate the length (Length) of the written data, and the 0th to 23rd bits are used to indicate the address at which writing starts; the length of each of the M VDOs is four bytes, wherein M is a positive integer, such as a positive integer not greater than five, so that the length of the M VDOs is not greater than 20 bytes to comply with the USB PD 2.0 specification.
[0061] Figure 7 An example of the format of each of the N request-side USVDMs for a read operation is shown, including a request-side USVDM header for carrying message information and a request-side first VDO for carrying read parameters. Figure 7 In an implementation example, the length of the request end USVDM header is four bytes, wherein the 16th to 31st bits are used to indicate the vendor identity (Vendor ID), the 15th bit is used to indicate the vendor defined message type (VDM Type), the 8th to 14th bits are reserved bits (Reserved Bits), and the 0th to 7th bits are used to indicate the request command for reading the storage circuit (e.g., flash memory) of the target circuit; the length of the first VDO of the request end is four bytes, wherein the 24th to 31st bits are used to indicate the length (Length) of the read data, and the 0th to 23rd bits are used to indicate the address from which reading starts.
[0062] Step S450: Receive N response terminals USVDM of the target circuit, the N response terminals USVDM corresponding to the N request terminals USVDM. In an implementation example, the N response terminals USVDM are USVDMs (PD USVDM (response)) that comply with the USB PD 2.0 protocol, such as Figure 5 shown.
[0063] Figure 6 An example of the format of each of the N responder USVDMs used for a write operation is shown, including a responder USVDM header for carrying message information and a responder first VDO for carrying write parameters. Figure 6In an implementation example, the response end USVDM header is similar to the request end USVDM header used for the write operation, with the only difference being that bits 0 to 7 of the response end USVDM header are used to indicate a response command for writing into the target circuit; the length of the first VDO of the response end is four bytes, bits 8 to 31 of which are reserved bits, and bits 0 to 7 are used to indicate a write result.
[0064] Figure 7 An example of the format of each of the N responder USVDMs for a read operation is shown, including a responder USVDM header for carrying message information, a responder first VDO for carrying read parameters, and M VDOs for carrying read data. Figure 7 In an implementation example, the response end USVDM header is similar to the request end USVDM header used for the read operation, except that bits 0 to 7 of the response end USVDM header are used to indicate a response command for reading the target circuit; the length of the first VDO of the response end is four bytes, wherein bits 24 to 31 are used to indicate the length of the read data, bits 8 to 23 are reserved bits, and bits 0 to 7 are used to indicate the read result; each of the M VDOs has a length of four bytes, where M is a positive integer, such as a positive integer not greater than five, so that the length of the M VDOs is not greater than 20 bytes to comply with the USB PD 2.0 specification.
[0065] Step S460: Convert the N response terminals USVDM into a first protocol response command, and transmit the first protocol response command to the host circuit. In an implementation example, the first protocol response command is a USB / SMBUS response command (USB / SMBUS CMD (response)). Figure 5 As shown, it is used to respond to the request of data writing / reading; after the host circuit receives the first protocol response command, it can prepare to start the next program. Since those skilled in the art can generate the first protocol response command according to the known communication protocol (e.g., USB / SMBUS protocol) and known communication technology (e.g., technology for generating packets according to the protocol) between the intermediate circuit and the host circuit, redundant descriptions are omitted here.
[0066] See also Figures 4-5. In an implementation example, the intermediate circuit communicates with the target circuit through a configuration channel of a USB Type-C interface, and the encoding of the above communication is a bi-phase mark code (Bi-Phase Mark Code). Therefore, the encoding of the N request end USVDM and the N response end USVDM is a bi-phase mark code. In an implementation example, when the access data amount associated with the first protocol request command is greater than K bytes (for example, 20 bytes), in order to make the access data amount associated with each of the N request end USVDMs not greater than K bytes to comply with the agreement between the target circuit and the intermediate circuit (for example, USB PD 2.0 agreement), the intermediate circuit executes Figure 4 In addition to the step of, further performing the following steps: splitting the first protocol request command to generate a plurality of local commands; and then converting the plurality of local commands into the N request end USVDMs, wherein K is greater than one, the access data amount associated with each of the plurality of local commands is not greater than K bytes, and N is an integer greater than one, and the N response end USVDMs correspond to the N request end USVDMs respectively. In an implementation example, the target circuit does not support the USB PD3.0 protocol, but supports the USB PD 2.0 protocol; the intermediate circuit and the target circuit serve as a downstream data flow end (Downstream Facing Port, DFP) and an upstream data flow end (Upstream Facing Port, UFP) respectively.
[0067] Figure 8 Another embodiment of the IC firmware update method of the present invention is shown. This embodiment can be performed by a target circuit (for example: Figure 1 or Figure 3 The target circuit 130) is executed, comprising the following steps:
[0068] Step S810: Communicate with a host circuit (eg: Figure 1 The intermediate circuit 120 or Figure 3 The host circuit 310) communicates to enter a preset mode (eg, a modal operation mode).
[0069] Step S820: Receive N request-end USVDMs, where N is a positive integer.
[0070] Step S830: Execute a firmware update operation according to the N request-end USVDMs to generate N response-end USVDMs, and transmit the N response-end USVDMs to the master-end circuit.
[0071] Fig. 9 Another embodiment of the IC firmware update method of the present invention is shown. This embodiment can be performed by a host circuit (for example: Figure 1The host circuit 110) is executed, comprising the following steps:
[0072] Step S910: Communicate with an intermediate circuit (eg: Figure 1 The intermediate circuit 120) communicates with the intermediate circuit to determine that the intermediate circuit enters a preset mode (for example, a modal operation mode).
[0073] Step S920: Generate X first protocol request commands according to a firmware update program, and transmit the X first protocol request commands to the intermediate circuit for the intermediate circuit to access a target circuit accordingly, wherein X is a positive integer. When the access data amount associated with the firmware update program is greater than K bytes, the step of generating the X first protocol request commands includes: generating a plurality of first protocol request commands according to the firmware update program as the X first protocol request commands, so that the access data amount associated with each of the X first protocol request commands is not greater than K bytes.
[0074] Step S930: Receive X first protocol response commands from the intermediate circuit, where contents of the X first protocol response commands originate from the target circuit.
[0075] Fig.10 Another embodiment of the IC firmware update method of the present invention is shown. This embodiment can be performed by a host circuit (for example: Figure 3 The host circuit 310) is executed, comprising the following steps:
[0076] Step S1010: Connecting to a target circuit (eg, Figure 3 The target circuit 320 of FIG. 10 is used to communicate with the target circuit 320 to enter a preset mode (eg, a modal operation mode). It is worth noting that in order to enter the modal operation mode, the process of communicating with the target circuit is as follows: Fig.11 As shown, the process is the same as Figure 5 The process from "Discover Identity (request)" to "Enter Mode (ack)" in the process.
[0077] Step S1020: Generate N request end USVDM requests according to a firmware update procedure, and transmit the N request end USVDMs to the target circuit for the target circuit to perform a firmware update operation, wherein N is a positive integer. In an implementation example, the N request end USVDMs are USVDMs (PD USVDM (request)) that comply with the USB PD 2.0 protocol, such as Fig.11 shown.
[0078] Step S1030: Receive N response terminals USVDM of the target circuit, the N response terminals USVDM correspond to the N request terminals USVDM, wherein the N request terminals USVDM and the N response terminals USVDM comply with the USB PD 2.0 protocol. In an implementation example, the N response terminals are USVDMs (PD USVDM (response)) that comply with the USB PD 2.0 protocol, such as Fig.11 shown.
[0079] Since those skilled in the art can refer to Figures 1 to 7 The disclosure of the embodiments of the present invention is to understand Figures 8 to 11 Details and variations of the embodiments of Figures 1 to 7 The technical features of the embodiments can be reasonably applied to Figures 8 to 11 In the embodiment of the present invention, therefore, repeated and redundant descriptions are omitted. In addition, some terms used in this specification (e.g., USVDM, configuration channel, SMBUS, modal operation, VDO, bidirectional marking code, DFP, UFP, etc.) are known and defined terms in the art, and the details can be found in the USB PD 2.0 / 3.0 specification and related documents.
[0080] It is worth noting that, under the premise that implementation is possible, technicians in this technical field may selectively implement some or all of the technical features in any of the aforementioned embodiments, or selectively implement a combination of some or all of the technical features in the aforementioned multiple embodiments, thereby increasing the flexibility of the implementation of the present invention.
[0081] In summary, the present invention can perform firmware update for a target circuit that does not support the USB PD 3.0 protocol based on the USB PD 2.0 protocol and using the USVDM defined by the present invention through the configuration channel of the USB Type-C interface.
[0082] Although the embodiments of the present invention are described above, these embodiments are not intended to limit the present invention. Those skilled in the art may make changes to the technical features of the present invention based on the explicit or implicit contents of the present invention. All such changes may fall within the scope of patent protection sought by the present invention. In other words, the scope of patent protection of the present invention shall be subject to that defined by the claims of this specification.
Claims
1. An IC firmware update method is performed by an intermediate circuit, comprising: communicating with a target circuit to enter a preset mode; According to a status inquiry message of a host circuit, a status reply message is sent to the host circuit to indicate entering the default mode; After sending the status reply message, receiving a first protocol request command from the host circuit; Converting the first protocol request command into N request-side unstructured vendor-defined messages, and transmitting the N request-side unstructured vendor-defined messages to the target circuit, so that the target circuit performs a firmware update operation, wherein N is a positive integer; Receiving N responder-end unstructured vendor-defined messages of the target circuit, the N responder-end unstructured vendor-defined messages corresponding to the N requester-end unstructured vendor-defined messages; as well as The N responder-end unstructured vendor-defined messages are converted into a first protocol response command, and the first protocol response command is transmitted to the host circuit.
2. The method of claim 1, wherein the intermediate circuit communicates with the target circuit via a USB Type-C interface, and the intermediate circuit communicates with the host circuit via a non-USB Type-C interface.
3. The method as claimed in claim 1 further comprises: when the access data amount associated with the first protocol request command is greater than K bytes, splitting the first protocol request command to generate a plurality of partial commands; and then converting the plurality of partial commands into the N request-side unstructured vendor-defined messages, respectively, wherein K is greater than one, the access data amount associated with each of the plurality of partial commands is not greater than K bytes, N is an integer greater than one, and the N response-side unstructured vendor-defined messages correspond to the N request-side unstructured vendor-defined messages, respectively.
4. The method of claim 1, wherein when the N request-side unstructured vendor-defined messages are write messages, the formats of the N request-side unstructured vendor-defined messages include a request-side unstructured vendor-defined message header, a request-side first vendor-defined data object for carrying write parameters, and M VDOs for carrying data; and the formats of the N response-side unstructured vendor-defined messages include a response-side unstructured vendor-defined message header and a response-side first VDO for carrying write parameters, wherein M is a positive integer.
5. The method of claim 1, wherein when the N request-end unstructured vendor-defined messages are read messages, the formats of the N request-end unstructured vendor-defined messages include a request-end unstructured vendor-defined message header and a request-end first vendor-defined data object for carrying read parameters; and the formats of the N response-end unstructured vendor-defined messages include a response-end unstructured vendor-defined message header, a response-end first VDO for carrying read parameters, and M VDOs for carrying data, wherein M is a positive integer.
6. A method for updating IC firmware, executed by a host circuit, comprising: Communicating with an intermediate circuit to determine that the intermediate circuit enters a preset mode; Generate X first protocol request commands according to a firmware update program, and transmit the X first protocol request commands to the intermediate circuit so that the intermediate circuit can access a target circuit accordingly, where X is a positive integer; and receiving X first protocol response commands from the intermediate circuit, the contents of the X first protocol response commands originating from the target circuit, When the access data amount associated with the firmware update program is greater than K bytes, the step of generating the X first protocol request commands includes: generating a plurality of first protocol request commands as the X first protocol request commands according to the firmware update program, so that the access data amount associated with each of the X first protocol request commands is not greater than K bytes.
