Remote updating method for extension machine and point screen system

Abstract

The application relates to an extension machine remote updating method and a point screen system. The method is executed by a host computer, the host computer is connected with at least one extension machine as an image signal source, and the method comprises the following steps: in the case that a firmware updating file from an upper computer is acquired, transmitting the firmware updating file to the extension machine through a high-speed interface between the host computer and the extension machine for transmitting images; and in response to receiving a firmware updating instruction from the upper computer, transmitting the firmware updating instruction to the extension machine through a low-speed interface or an idle time slot of a multiplexed high-speed interface, so as to instruct the extension machine to update a firmware program of the extension machine by using the firmware updating file. According to the application, the efficient remote updating of the firmware of the extension machine can be realized, and the updating and maintenance cost of the extension machine is saved.

Description

Technical Field

[0001] This application relates to the field of display screen testing technology, and in particular to a remote update method for an expansion machine and a screen display system. Background Technology

[0002] In recent years, LCD modules have been widely used in large-screen TVs and small-to-medium-sized terminal devices. Large-screen TVs use LCD panels with higher resolution and refresh rates, requiring higher image transmission bandwidth. Small-to-medium-sized LCD screens need to undergo high-temperature and high-humidity aging tests before leaving the factory, both of which utilize separate display testing equipment for static image testing. Due to the diverse types of LCD modules that the display testing equipment needs to test, firmware driver issues inevitably arise, necessitating firmware updates for the display testing equipment. Traditional methods typically rely on hardware programming ports (such as JTAG) for local firmware updates, which is inefficient.

[0003] For display testing equipment using a split architecture, it typically includes an early-developed low-end host (which can be called an image signal unit). Apart from the high-speed channel for transmitting images and some low-speed interfaces for transmitting control signals, there is no reserved data channel for updating firmware between the host and the expansion units. Therefore, it is usually possible to only update the host remotely. The expansion units either cannot be updated or can only use low-speed interfaces for slow transmission. The remote update speed is very slow. For medium and large screen production and testing lines with dozens of expansion units or high temperature and humidity aging tests with hundreds of expansion units, remote updates of expansion units become a time-consuming and costly problem. Summary of the Invention

[0004] In view of this, the present application provides a remote update method for an extender and a screen-pointing system to solve at least one problem existing in the background art.

[0005] In a first aspect, embodiments of this application provide a remote update method for an extender, the method being executed by a host, the host acting as an image signal source connected to at least one extender, the method comprising:

[0006] Upon receiving the firmware update file from the host computer, the firmware update file is transmitted to the expansion machine via the high-speed interface used for image transmission between the host and the expansion machine.

[0007] In response to receiving a firmware update command from the host computer, the firmware update command is transmitted to the expansion machine via the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so as to instruct the expansion machine to update its firmware program using the firmware update file.

[0008] In conjunction with the first aspect, in an optional embodiment, the host has a first application program and a first underlying program; the extended machine has a second application program and a second underlying program; the step of transmitting the firmware update file to the extended machine via a high-speed interface for image transmission between the host and the extended machine, upon receiving a firmware update file from the host computer, includes:

[0009] When the host is running on the first low-level program and the expansion machine is running on the second low-level program, the first low-level program, in response to receiving the firmware update file from the host computer, transmits the firmware update file to the second low-level program through the high-speed interface between the host and the expansion machine.

[0010] The step of responding to receiving a firmware update command from a host computer by transmitting the firmware update command to the expansion machine via a low-speed interface between the host and the expansion machine or by reusing an idle time slot of the high-speed interface includes:

[0011] In response to the received firmware update command, the first underlying program transmits the address parameters of the firmware to be updated carried by the firmware update command to the second underlying program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface.

[0012] Secondly, embodiments of this application provide a remote update method for an extender, the method being executed by an extender connected to a host, the host being configured as an image signal source, the method comprising:

[0013] The host computer receives firmware update files from the host computer via a high-speed interface for image transmission between the host and the extended machine.

[0014] The host receives firmware update commands from the host computer via the low-speed interface between the host and the expansion unit or by reusing the idle time slots of the high-speed interface.

[0015] In response to the firmware update instruction, the firmware program of the expansion machine is updated using the firmware update file.

[0016] In conjunction with the second aspect, in an optional implementation, the host has a first application program and a first underlying program; the extension machine has a second application program and a second underlying program;

[0017] The step of receiving firmware update files from the host computer transmitted by the host computer via the high-speed interface for image transmission between the host and the extended machine includes:

[0018] When the host is running on the first low-level program and the expansion machine is running on the second low-level program, the second low-level program receives the firmware update file from the host computer transmitted by the first low-level program through the high-speed interface between the host and the expansion machine.

[0019] The step of receiving firmware update instructions from the host computer transmitted by the first underlying program through the low-speed interface between the host and the expansion unit or by reusing the idle time slot of the high-speed interface includes:

[0020] The second underlying program receives firmware update instructions from the host computer transmitted by the first underlying program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface.

[0021] Thirdly, embodiments of this application provide a remote update method for an extended machine, the method being executed by a host computer, the host computer being communicatively connected to a host computer, the host computer being connected to at least one extended machine as an image signal source, the method comprising:

[0022] Send a firmware update file to the host, the firmware update file being transmitted to the extender via a high-speed interface for image transmission between the host and the extender;

[0023] A firmware update command is sent to the host. The firmware update command is transmitted to the expansion machine through a low-speed interface between the host and the expansion machine or by reusing an idle time slot of the high-speed interface, so as to instruct the expansion machine to update its firmware program using the firmware update file.

[0024] In conjunction with the third aspect, in an optional implementation, the host has a first application program and a first underlying program; the extension machine has a second application program and a second underlying program;

[0025] Sending the firmware update file to the host includes:

[0026] When the host is running on the first low-level program and the extension machine is running on the second low-level program, the firmware update file is sent to the first low-level program. The firmware update file is transmitted from the first low-level program to the second low-level program of the extension machine through the high-speed interface for image transmission between the host and the extension machine.

[0027] Sending the firmware update command to the host includes:

[0028] The firmware update command is sent to the first underlying program. The firmware update command is transmitted by the first underlying program to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, and then to the second underlying program of the expansion machine.

[0029] Fourthly, embodiments of this application provide a dot-screen system, including a host computer, a host computer serving as an image signal source, and at least one extender connected to the host computer:

[0030] The host computer is configured to execute the remote update method for the extended machine as described in any of the third aspects;

[0031] The host is configured to perform the extended machine remote update method as described in any of the first aspects;

[0032] The extended machine is configured to perform the extended machine remote update method as described in any of the second aspects.

[0033] Fifthly, embodiments of this application provide an electronic device including a processor, the processor being configured to invoke instructions to cause the electronic device to execute the remote update method for an extended machine as described in any of the first, second, or third aspects.

[0034] In a sixth aspect, embodiments of this application provide a storage medium storing an executable program thereon, wherein the executable program, when executed by a processor, implements the remote update method for an extended machine as described in any of the first aspects, or the remote update method for an extended machine as described in any of the second aspects, or the remote update method for an extended machine as described in any of the third aspects.

[0035] This application provides a remote update method and screen display system for an expansion unit. It utilizes a high-speed channel between the host and the expansion unit for transmitting image data to transmit firmware update files, while using only a low-speed interface to transmit control commands. Furthermore, the control commands can be embedded within the blanking interval of the image transmitted via the high-speed interface. As long as the host and the expansion unit have a high-speed interface for image transmission, efficient remote firmware updates for the expansion unit can be achieved without additional data cables. Moreover, no hardware modifications are required, and for split-type devices employing a multi-device architecture, simultaneous updates of multiple expansion units can be achieved, significantly reducing the update and maintenance costs of the expansion units. Attached Figure Description

[0036] Figure 1 This is a flowchart illustrating the remote update method for the extended machine provided in the first embodiment of this application.

[0037] Figure 2A schematic diagram of the interaction architecture between the host and the expansion machine provided in an embodiment of this application. Figure 1 .

[0038] Figure 3 A schematic diagram of the interaction architecture between the host and the expansion machine provided in an embodiment of this application. Figure 2 .

[0039] Figure 4 This is a flowchart illustrating the remote update method for the extended machine provided in the second embodiment of this application.

[0040] Figure 5 This is a flowchart illustrating the remote update method for the extended machine provided in the third embodiment of this application.

[0041] Figure 6 This is a flowchart illustrating the remote update method for the extended machine provided in the fourth embodiment of this application.

[0042] Figure 7 This is a flowchart illustrating the remote update method for the extended machine provided in the fifth embodiment of this application. Detailed Implementation

[0043] To make the technical solution and beneficial effects of this application more apparent and understandable, a detailed description is provided below by listing specific embodiments. The accompanying drawings are not necessarily drawn to scale, and local features may be enlarged or reduced to more clearly show the details of the local features; unless otherwise defined, the technical and scientific terms used herein have the same meanings as those in the technical field to which this application pertains.

[0044] The embodiments in this application are not exhaustive, but merely illustrative of some embodiments, and are not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0045] In each embodiment of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0046] In the description of the embodiments of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0047] In related technologies, LCD modules require static image testing using a split-architecture display testing device. Due to the diverse types of display panels, the display testing device needs to be compatible with multiple panel types. Therefore, the firmware programs in the host and expansion units of the display testing device need to be updated to ensure compatibility with new models, fix driver defects, or improve stability. For display testing devices using a split-architecture design, most are early-developed, low-end host units. Besides high-speed channels for image transmission and some low-speed interfaces for control signal transmission, no data channel is reserved between the host and expansion units for firmware updates. Therefore, updates are usually only possible remotely to the host unit; the expansion units either cannot be updated or only use low-speed interfaces for slow transmission, resulting in very slow remote update speeds. For production lines with dozens of expansion units for medium to large screens, or for high-temperature and high-humidity aging tests on hundreds of expansion units, remote updates of the expansion units become a very time-consuming and costly problem.

[0048] This application provides a remote update method for an expansion unit, which is used to update the expansion unit in a display testing device. It can be applied to the screen testing scenario of liquid crystal display modules, or it can also be used in other scenarios that require firmware updates for the expansion unit. The display testing device adopts a split architecture, including a host and at least one expansion unit, with the host serving as an image signal source.

[0049] During screen testing, the host computer generates image signals and distributes them to at least one expansion unit. The expansion unit converts the image signals into specific interface signals to drive the display module under test (DUT) for screen testing. Specifically, the host computer acts as the central control unit of the split-type display testing equipment, responsible for running the main control software, managing the test task flow, and distributing processed image signals to one or more expansion units via a high-speed interface. The expansion unit acts as the signal adapter terminal of the split-type display testing equipment system, directly connecting to and driving the DUT. During screen testing, the expansion unit converts the image signals from the host computer into the interface protocol and specific timing supported by the DUT to drive the DUT to complete the screen testing.

[0050] Figure 1 This is a flowchart illustrating the remote update method for the extended machine provided in the first embodiment of this application.

[0051] See Figure 1 As shown in the figure, this application embodiment provides a remote update method for an extension machine, including the following steps:

[0052] S101: The host computer sends a firmware update file to the host computer;

[0053] S102: When the host computer receives the firmware update file from the host computer, it transmits the firmware update file to the expansion unit through the high-speed interface used for image transmission between the host computer and the expansion unit.

[0054] S103: The host computer sends a firmware update command to the host computer;

[0055] S104: Upon receiving a firmware update command from the host computer, the host computer transmits the firmware update command to the expansion unit through the low-speed interface between the host computer and the expansion unit or by reusing the idle time slot of the high-speed interface.

[0056] S105: The expansion unit responds to the firmware update command and updates the expansion unit's firmware program using the firmware update file.

[0057] In this embodiment, the host computer in the display test device communicates with the host computer and can receive firmware update files sent by the host computer. The host computer can be a client running on a terminal device. The terminal device may include, but is not limited to, personal computers (PCs), industrial control computers (IPCs), servers, or mobile terminals.

[0058] The host computer can obtain firmware update files through local storage, import from external devices, or download from a firmware server over a network. Firmware update files include a set of data used for firmware upgrades or repairs on the expansion device, such as, but not limited to, application code and configuration files.

[0059] Firmware (or "firmware program") is a software program embedded in a hardware device (such as an image signal receiver, an extender, etc.) to control the basic functions and operation of the device. In this embodiment, the firmware is stored in an external non-volatile memory (such as FLASH memory) and supports dynamic upgrades or repairs through a remote update mechanism to ensure that the device adapts to diverse display module testing requirements.

[0060] In this embodiment, both the host and the expansion unit support dynamic switching between screen-based testing mode and firmware update mode. In screen-based testing mode, the host and the expansion unit collaboratively perform screen-based testing of the display module under test; in firmware update mode, the host and the expansion unit collaboratively perform firmware updates for the expansion unit.

[0061] In some embodiments, when both the host and the expansion unit are running in firmware update mode, the host computer sends a firmware update file to the host. For example, the host computer first sends a control command to the host to trigger the host to switch itself to firmware update mode, and the host transmits a switching command to the expansion unit through a low-speed interface or a time slot of a multiplexed high-speed interface, causing the expansion unit to switch to firmware update mode; when both the host and the expansion unit are running in firmware update mode, the host computer sends the firmware update file to the host.

[0062] The host computer can transfer firmware update files to the host computer via standard network communication protocols, such as TCP / IP (Transmission Control Protocol / Internet Protocol).

[0063] In this embodiment, after receiving the firmware update file from the host computer, the host no longer relies on the low-speed interface. Instead, it utilizes the existing high-speed interface between the host and the expansion unit, which is used for transmitting image data, to send the firmware update file to the expansion unit. The high-speed interface includes, but is not limited to, LVDS (Low-Voltage Differential Signaling), eDP (embedded Display Port), or V-By-One HS (V-By-One High Speed), etc., with transmission rates reaching hundreds of Mbps to several Gbps, far exceeding the transmission rate of low-speed interfaces, enabling efficient transmission of firmware update files.

[0064] In some examples, the host can encapsulate the firmware update file into a data frame conforming to the high-speed interface protocol for transmission as image data; for example, when the host switches from normal screen-on mode to firmware update mode, it transmits the firmware update file to the expansion unit using a dedicated high-speed channel.

[0065] The firmware update command sent from the host computer to the main unit can be used to trigger the firmware update process of the expansion unit. After receiving the firmware update command, the host computer can transmit the firmware update command to the expansion unit in one of the following two ways:

[0066] One method is to transmit data via a low-speed interface between the host and the expansion unit. This low-speed interface may include, but is not limited to, interfaces such as UART (Universal Asynchronous Receiver / Transmitter), I²C (Inter-Integrated Circuit), or SPI (Serial Peripheral Interface). These low-speed interfaces have low transmission rates (usually below 10Mbps), but are sufficient to carry the transmission of instruction data (such as firmware update instructions, which can carry address parameters indicating the firmware update range).

[0067] Method two involves reusing the idle time slots of the high-speed interface (i.e., the time intervals in the high-speed channel that are not occupied by image data) to transmit firmware update instructions in non-image data form to the expansion unit. For example, the idle time slots of the high-speed interface can be blanking intervals of the image signal, such as the vertical blanking interval (VBI) or the horizontal blanking interval (HBI) of the image signal.

[0068] The "reuse" mentioned in this application refers to using the idle time slots that exist during the transmission of image signals through a high-speed interface to additionally transmit firmware update instructions without affecting the normal transmission of image signals.

[0069] By using this method of reusing idle time slots of high-speed interfaces, no additional hardware wiring is required. This not only improves the utilization rate of high-speed channels but also ensures the reliability of control command transmission.

[0070] It should be noted that both the host and expansion device applications support screen-on mode. If both applications are configured to support firmware update mode, they can be switched to firmware update mode. In firmware update mode, efficient firmware updates for the expansion device are performed through interaction between the host and expansion device applications, thus preventing firmware updates from interfering with normal business functions.

[0071] Upon receiving a firmware update command, the expansion device can update its firmware program using a firmware update file, based on the address parameters indicating the firmware update range carried in the firmware update command. For example, in firmware update mode, the expansion device can load the firmware update file into a designated storage area, where the firmware program is, for example, the expansion device's application program. The designated storage area is, for example, the application partition of the expansion device's Flash memory, to overwrite the old version of the application program.

[0072] In this embodiment, for a multi-extension deployment scenario, the host supports a parallel transmission mechanism. It can simultaneously transmit the same firmware update file to multiple extensions via the high-speed interface between the host and each extension, and send relevant control commands separately via the low-speed interface between the host and each extension (or reuse the idle time slots of the high-speed interface), thus achieving efficient updates for batch extensions. For a specific target extension (e.g., an extension indicating a firmware driver issue needs fixing as indicated by the host computer), the host sends the firmware update file to the target extension via the high-speed interface, and sends relevant control commands via the low-speed interface between the host and the target extension (or reuse the idle time slots of the high-speed interface), achieving efficient updates for the specified extension.

[0073] In the aforementioned remote update method for the expansion unit, the firmware update file is transmitted by utilizing the high-speed channel used for image data transmission between the host and the expansion unit, while only a low-speed interface is used to transmit control commands. Furthermore, the control commands can even be embedded within the blanking interval of the image transmitted through the high-speed interface. As long as there is a high-speed interface for image transmission between the host and the expansion unit, efficient remote firmware updates for the expansion unit can be achieved without additional data cables. Moreover, no hardware modifications are required, and multiple expansion units can be updated simultaneously for split-type devices with a one-to-many architecture, greatly saving on the update and maintenance costs of the expansion units.

[0074] In some embodiments, the host can be implemented based on an FPGA (Field-Programmable Gate Array) architecture, with its firmware stored in an external FLASH memory. This external FLASH memory can store multiple firmware programs. To facilitate firmware management and updates, the FLASH storage space is logically divided into several partitions. The partition used to store the underlying program with remote update capabilities is defined as the golden mirror area, and the partition used to store applications with screen-click functionality is defined as the application mirror area. There can be one golden mirror area, while multiple application mirror areas can be set to support flexible application updates and multi-version management.

[0075] For each expansion unit connected to the host, its firmware is also stored in an external FLASH memory, including applications with specific business functions (such as screen tapping function) and underlying programs with remote update function.

[0076] For ease of description, for multiple firmware programs on the host machine, the application with screen-click functionality is called the first application (also known as the host application image), and the underlying program with remote update functionality is called the first underlying program (also known as the host gold image). For multiple firmware programs on the expansion machine, the application with screen-click functionality is called the second application (also known as the expansion machine application image), and the underlying program with remote update functionality is called the second underlying program (also known as the expansion machine gold image).

[0077] To improve the reliability of firmware updates for the expansion machine, in this embodiment, the remote update method for the expansion machine can achieve efficient firmware updates through the interaction between the first underlying program of the host and the second underlying program of the expansion machine. Thus, even if the application image is corrupted, if a remote firmware update fails, the underlying program stored in the golden image area can still be invoked for a subsequent remote update. For example, when the expansion machine detects data corruption in the application image area, it automatically loads the second underlying program from the golden image area and reports an error status to the host computer through the low-speed interface between the host and the expansion machine, so as to receive the resent firmware update file from the host computer and execute the update operation.

[0078] Figure 2 A schematic diagram of the interaction architecture between the host and the expansion machine provided in an embodiment of this application. Figure 1 . Figure 3 A schematic diagram of the interaction architecture between the host and the expansion machine provided in an embodiment of this application. Figure 2 See also Figure 2 and Figure 3 As shown, the first underlying program (i.e., the host gold image) has a remote update control module, an output module, and a second program switching module. The second underlying program (i.e., the expansion unit gold image) has a receiving module, a control module, and a second program switching module. The first application program (i.e., the host application image) has a first program switching module, and the second application program (i.e., the expansion unit application image) has a first program switching module. The host is connected to a first storage chip, and the expansion unit is connected to an external non-volatile memory.

[0079] In some embodiments, the first program jump module is triggered in response to a first program jump instruction from the host computer, so that the host switches from running the first application to running the first underlying program.

[0080] In some embodiments, the first program switching module is triggered in response to a first program switching instruction sent by the host from the host computer, so that the extended machine switches from running the second application to running the second underlying program.

[0081] In some embodiments, see Figure 2The remote update control module is used to: transmit the first program switching instruction from the host computer to the output module; cache the firmware update file from the host computer into the first storage chip; transmit the firmware update instruction from the host computer to the output module; transmit the second program switching instruction from the host computer to the output module; and transmit the second program jump instruction from the host computer to the second program jump module.

[0082] The output module is used to: transmit a first program switching instruction to the expansion unit through an idle time slot of the high-speed interface between the host and the expansion unit; read a firmware update file from the first storage chip and transmit the firmware update file to the second low-level program of the expansion unit through the high-speed interface between the host and the expansion unit used for image transmission; transmit a firmware update instruction to the expansion unit through an idle time slot of the high-speed interface between the host and the expansion unit; and transmit a second program switching instruction to the expansion unit through an idle time slot of the high-speed interface between the host and the expansion unit.

[0083] In other embodiments, see Figure 3 The remote update control module is used to: transmit the first program switching command from the host computer to the expansion machine through the low-speed interface between the host and the expansion machine; cache the firmware update file from the host computer into the first storage chip; transmit the firmware update command from the host computer to the second low-level program of the expansion machine through the low-speed interface between the host and the expansion machine; transmit the second program switching command from the host computer to the second low-level program of the expansion machine through the low-speed interface between the host and the expansion machine; and transmit the second program jump command from the host computer to the second program jump module.

[0084] The output module is used to: read the firmware update file from the first storage chip and transmit the firmware update file to the second low-level program of the expansion unit through the high-speed interface used for image transmission between the host and the expansion unit.

[0085] In some embodiments, the second program jump module is triggered in response to receiving a second program jump instruction, so that the host switches from running the first underlying program to running the first application.

[0086] In some embodiments, see Figure 2 The receiving module is used to: receive firmware update files through the high-speed interface between the host and the expansion unit for image transmission, and store them in the second storage chip; transmit firmware update instructions received through the idle time slot of the high-speed interface between the host and the expansion unit to the control module; and transmit second program switching instructions received through the idle time slot of the high-speed interface between the host and the expansion unit to the second program switching module.

[0087] The control module is used to: read the firmware update file from the second storage chip, and write the firmware update file into the application image area of ​​a non-volatile memory (e.g., external FLASH) based on the start and end addresses of the firmware update carried in the firmware update instruction.

[0088] In other embodiments, see Figure 3 The receiving module is used to receive firmware update files through a high-speed interface between the host and the expansion unit for image transmission, and store them in the second storage chip.

[0089] The control module is used to: receive firmware update instructions from the host computer through the low-speed interface between the host and the expansion unit; read the firmware update file from the second storage chip; and write the firmware update file into the application mirror area of ​​the non-volatile memory based on the start and end addresses of the firmware update carried in the firmware update instructions.

[0090] In some embodiments, the second program switching module is triggered in response to receiving a second program switching instruction, so that the extension machine switches from running a second application to running a second underlying program.

[0091] The first and second memory chips mentioned above can both be dynamic random access memory, such as DDR SDRAM (Double Data Rate Synchronous Dynamic Random-Access Memory), including but not limited to DDR3, DDR4 or DDR5 types. These memories have high read and write speeds and large storage capacity.

[0092] Understandable, Figure 2 and Figure 3 The host and expansion machine interaction architecture shown is only illustrative and can be flexibly adjusted according to hardware configuration in actual deployment. The control commands transmitted between the host and expansion machine can dynamically mix the idle time slots of low-speed and high-speed interfaces. For example, the low-speed interface transmits the first program switching command and the second program switching command, and the idle time slot of the high-speed interface transmits the firmware update command. Or, for example, the idle time slot of the high-speed interface transmits the first program switching command and the second program switching command, and the low-speed interface transmits the firmware update command. However, this application is not limited to this.

[0093] Figure 4 This is a schematic flowchart illustrating the remote update method for the extended machine provided in the second embodiment of this application. (See attached diagram.) Figure 4 As shown, the remote update method for the extended machine includes the following steps:

[0094] S200: The host computer sends the first program jump instruction to the first application program of the host computer.

[0095] S201: The host switches from running the first application to running the first underlying program.

[0096] For example, the first application has a first program jump module, which is triggered in response to a first program jump instruction from the host computer, so that the host switches from running the first application to running the first underlying program.

[0097] S202: The host computer sends configuration information to the first underlying program of the host computer to configure the first underlying program to have data transmission function.

[0098] The host's first-level program has data transmission capabilities, meaning that the first-level program can transmit firmware update files and related control commands to the second-level program of the expansion unit during the firmware update process.

[0099] S203: The host computer sends the first program switching instruction to the first underlying program of the host computer.

[0100] For example, the remote update control module in the first underlying program receives the first program switching instruction sent by the host computer.

[0101] S204: The host's first low-level program transmits the first program switching instruction to the expansion machine through the low-speed interface between the host and the expansion machine or the idle time slot of the multiplexed high-speed interface.

[0102] For example, the remote update control module in the first underlying program transmits the first program switching instruction to the output module. The output module transmits the first program switching instruction to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface.

[0103] S205: In response to receiving the first program switching instruction, the extended machine switches from running the second application program to running the second underlying program.

[0104] For example, the second application of the expansion machine has a first program switching module, which is triggered in response to a first program switching instruction to switch the expansion machine from running the second application to running the second underlying program.

[0105] S206: The host computer sends a firmware update file to the host's first-level program.

[0106] For example, the remote update control module in the first underlying program receives the firmware update file sent by the host computer and caches the firmware update file in the first storage chip (e.g., an external storage chip).

[0107] S207: The host's first low-level program transmits firmware update files to the expansion unit's second low-level program through the high-speed interface used for image transmission between the host and the expansion unit.

[0108] For example, the output module in the first underlying program reads the firmware update file from the first storage chip and transmits the firmware update file to the expansion unit through the high-speed interface between the host and the expansion unit for transmitting images.

[0109] S208: The second-level program cache firmware update file of the expansion unit.

[0110] For example, the receiving module in the second underlying program receives the firmware update file through a high-speed interface between the host and the extension machine for transmitting images, and stores the firmware update file in a second storage chip (e.g., an external storage chip).

[0111] S209: The host computer sends a firmware update command to the host's first-level program.

[0112] For example, the remote update control module in the first underlying program receives the firmware update command sent by the host computer and transmits it to the output module in the first underlying program.

[0113] S210: The host's first low-level program transmits firmware update instructions to the expansion unit's second low-level program through the low-speed interface between the host and the expansion unit or by reusing the idle time slot of the high-speed interface.

[0114] For example, the output module in the first low-level program transmits firmware update instructions to the second low-level program of the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface.

[0115] S211: The second low-level program of the expansion unit responds to the firmware update command and updates the firmware program of the expansion unit using the firmware update file.

[0116] For example, the receiving module in the second low-level program receives the firmware update instruction through the low-speed interface between the host and the expansion unit or by reusing the idle time slot of the high-speed interface, and passes it to the control module in the second low-level program. The control module reads the firmware update file from the second storage chip and writes the firmware update file into the application mirror area of ​​non-volatile memory (e.g., external FLASH) based on the start and end addresses of the firmware update carried in the firmware update instruction.

[0117] S212: The host computer sends a second program switching instruction to the first underlying program of the host computer.

[0118] For example, the remote update control module in the first underlying program receives a second program switching instruction sent by the host computer.

[0119] For example, the host computer can obtain the update progress of the expansion device through the low-speed interface between the host and the expansion device. When the update progress of the expansion device indicates that the update is complete, the host computer sends a second program switching command to the first underlying program of the host. The host computer can visualize the update progress of the expansion device, for example, by displaying it as a progress bar. Alternatively, the host computer can also send a second program switching command to the first underlying program of the host when a preset time has elapsed since sending the firmware update command.

[0120] S213: The host's first low-level program transmits the second program switching instruction to the expansion machine through the low-speed interface between the host and the expansion machine or the idle time slot of the multiplexed high-speed interface.

[0121] For example, the remote update control module in the first underlying program transmits the second program switching instruction to the output module. The output module transmits the second program switching instruction to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface.

[0122] S214: In response to the second underlying program of the extension machine receiving a second program switching instruction, the extension machine switches from running the second underlying program to running the second application program.

[0123] For example, the receiving module in the second underlying program receives the second program switching instruction through the low-speed interface between the host and the expansion machine or by multiplexing the idle time slot of the high-speed interface, and transmits it to the second program switching module in the second underlying program. The second program switching module is triggered in response to receiving the second program switching instruction, so that the expansion machine switches from running the second underlying program to running the second application program.

[0124] S215: The host computer sends a second program jump instruction to the first low-level program of the host computer.

[0125] S216: The host switches from running the first underlying program to running the first application program.

[0126] For example, the second program jump module in the first underlying program is triggered in response to a second program jump instruction from the host computer, so that the host switches from running the first underlying program to running the first application.

[0127] In the above-mentioned expansion machine update method, through the interaction between the first low-level program of the host computer and the host and the second low-level program of the expansion machine, the firmware update operation of the expansion machine can be achieved efficiently. Thus, when the remote update of the expansion machine firmware fails, even if the application image is corrupted, it can still automatically start from the golden image area and perform remote update by calling the low-level program stored in the golden image area.

[0128] The remote update method for the extended machine involved in the embodiments of this application may include at least one of steps S200 to S216. Unless otherwise specified, each step may be implemented as an independent embodiment, and the steps may be arbitrarily combined.

[0129] In some embodiments, steps S200 to S205 are optional. Besides triggering with a host computer instruction, other methods can be used to implement the host running in the first low-level program and the expansion unit running in the second low-level program. For example, hardware signal triggering or a timing mechanism can be used. As an example, after detecting a continuous press signal of its preset button, the host forces itself to run in the second low-level program (i.e., the host runs in firmware update mode) and transmits a switching instruction to the expansion unit via a low-speed interface (or reuses the idle time slot of a high-speed interface) to trigger the expansion unit to run in the second low-level program (i.e., the expansion unit runs in firmware update mode). Alternatively, the expansion unit can also directly run in the second low-level program after detecting its preset button signal. Correspondingly, steps S212 to S216 are optional. Besides triggering with a host computer instruction, hardware signal triggering can also be used to switch the host and expansion unit from running in the low-level program to running in the application program.

[0130] Figure 5 This is a flowchart illustrating the remote update method for an extender provided in the third embodiment of this application. The remote update method is executed by a host computer, which acts as an image signal source connected to at least one extender computer. (See attached diagram.) Figure 5 As shown, the method includes the following steps:

[0131] S301: Upon receiving the firmware update file from the host computer, the firmware update file is transferred to the expansion unit via the high-speed interface used for image transmission between the host and the expansion unit.

[0132] S302: In response to receiving a firmware update command from the host computer, the firmware update command is transmitted to the expansion unit through the low-speed interface between the host and the expansion unit or by using the idle time slot of the high-speed interface to instruct the expansion unit to update its firmware program using the firmware update file.

[0133] In some embodiments, optional implementations of step S301 can be found in [reference needed]. Figure 1 Optional implementation methods of steps S101 to S102, and Figure 1 Other related parts in the embodiments involved will not be described in detail here.

[0134] In some embodiments, optional implementations of step S302 can be found in [reference needed]. Figure 1 Optional implementation methods for steps S103 to S105, and Figure 1Other related parts in the embodiments involved will not be described in detail here.

[0135] In some embodiments, the host has a first application and a first underlying program; the extension machine has a second application and a second underlying program.

[0136] In step S301 above, when a firmware update file is obtained from the host computer, the firmware update file is transmitted to the extended computer via the high-speed interface used for image transmission between the host computer and the extended computer. This may include the following steps:

[0137] S3011: When the host is running in the first low-level program and the expansion machine is running in the second low-level program, the first low-level program, in response to receiving the firmware update file from the host computer, transmits the firmware update file to the second low-level program through the high-speed interface between the host and the expansion machine.

[0138] In some embodiments, optional implementations of step S3011 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S206 to S208, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0139] In step S302 above, in response to receiving a firmware update command from the host computer, transmitting the firmware update command to the expansion machine via the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface may include the following steps:

[0140] S3021: In response to the received firmware update command, the first underlying program transmits the address parameters of the firmware update command to the second underlying program through the low-speed interface between the host and the expansion unit or by reusing the idle time slot of the high-speed interface.

[0141] In some embodiments, optional implementations of step S3021 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of steps S209 to S210, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0142] In some embodiments, prior to performing step S3011, the method may further include the step of:

[0143] S303: In response to the first application receiving a first program jump instruction from the host computer, the host switches from running the first application to running the first underlying program, and configures the underlying program to have data transmission function according to the configuration information from the host computer;

[0144] S304: In response to receiving a first program switching instruction from the host computer, the first underlying program transmits the first program switching instruction to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second application program to running the second underlying program.

[0145] In some embodiments, optional implementations of step S303 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S201 to S202, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0146] In some embodiments, optional implementations of step S304 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S203 to S205, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0147] In some embodiments, after performing step S3021, the method may further include the step of:

[0148] S305: In response to receiving a second program switching instruction from the host computer, the first underlying program transmits the second program switching instruction to the second underlying program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second underlying program to running the second application program.

[0149] S306: In response to the first underlying program receiving a second program jump instruction from the host computer, the host switches from running the first underlying program to running the first application program.

[0150] In some embodiments, optional implementations of step S305 may be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S212 to S214, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0151] In some embodiments, optional implementations of step S306 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S216, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0152] In some embodiments, prior to performing step S305, the method may further include the step of:

[0153] S307: The first underlying program obtains the update progress of the expansion machine through the low-speed interface between the host and the expansion machine, and sends the update progress of the expansion machine to the host computer, so that the host computer can send the second program switching instruction to the first underlying program after determining that the expansion machine update is completed.

[0154] In some embodiments, optional implementations of step S307 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S212, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0155] In some embodiments, the idle time slot of the high-speed interface is the blanking interval of a specific image signal transmitted by the high-speed interface.

[0156] For example, a specific image signal is a preset image signal specifically used for updating the firmware of the expansion machine, and the blanking interval can be, for example, the vertical blanking period of the specific image signal, the horizontal blanking period of the image signal, etc.

[0157] By using this method of reusing idle time slots of high-speed interfaces, no additional hardware wiring is required. This not only improves the utilization rate of high-speed channels but also ensures the reliability of control command transmission.

[0158] It should be understood that, for the sake of simplicity of the illustrations, steps S3011, S3021, S303, S304, S305, S306 and S307 are not shown in the drawings, but they all belong to the preferred embodiments of this application, and their specific implementations have been described in detail in the specification, which does not affect the understanding and implementation of this application by those skilled in the art.

[0159] Figure 6 This is a flowchart illustrating the remote update method for an extender provided in the fourth embodiment of this application. The remote update method is executed by an extender connected to a host computer, which is configured as an image signal source. (See attached diagram.) Figure 6 As shown, the method includes the following steps:

[0160] S401: Receives firmware update files from the host computer via a high-speed interface used for image transmission between the host and the expansion unit;

[0161] S402: Receives firmware update commands from the host computer via the low-speed interface between the host and the expansion unit or by reusing the idle time slot of the high-speed interface.

[0162] S403: In response to a firmware update command, update the firmware of the extension device using a firmware update file.

[0163] In some embodiments, optional implementations of step S401 can be found in [reference needed]. Figure 1 Optional implementation methods of step S102, and Figure 1 Other related parts in the embodiments involved will not be described in detail here.

[0164] In some embodiments, optional implementations of step S402 can be found in [reference needed]. Figure 1 Optional implementation methods of step S104, and Figure 1 Other related parts in the embodiments involved will not be described in detail here.

[0165] In some embodiments, optional implementations of step S403 can be found in [reference needed]. Figure 1 Optional implementation methods of step S105, and Figure 1 Other related parts in the embodiments involved will not be described in detail here.

[0166] In some embodiments, the host has a first application and a first underlying program; the extension machine has a second application and a second underlying program.

[0167] In step S401 above, receiving the firmware update file from the host computer transmitted by the host through the high-speed interface for image transmission between the host and the extended machine may include the following steps:

[0168] S4011: When the host is running on the first low-level program and the expansion machine is running on the second low-level program, the second low-level program receives the firmware update file from the host computer transmitted by the first low-level program through the high-speed interface between the host and the expansion machine.

[0169] In step S402 above, receiving the firmware update command from the host computer transmitted by the first underlying program through the low-speed interface between the host and the expansion unit or by multiplexing the idle time slot of the high-speed interface may include the following steps:

[0170] S4021: The second underlying program receives the firmware update command from the host computer transmitted by the first underlying program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface.

[0171] In some embodiments, optional implementations of step S4011 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S207 to S208, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0172] In some embodiments, optional implementations of step S4021 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S210, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0173] In some embodiments, the method may further include the steps of:

[0174] S404: In response to the second application receiving a first program switching instruction through a low-speed interface between the host and the expansion machine or by multiplexing an idle time slot of the high-speed interface, the expansion machine switches from running the second application to running the second underlying program;

[0175] S405: In response to the second underlying program receiving a second program switching instruction through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, the expansion machine switches from running the second underlying program to running the second application program.

[0176] In some embodiments, step S404 is performed before step S4011. Optional implementations of step S404 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S204 to S205, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0177] In some embodiments, step S405 is executed after step S4021. Optional implementations of step S405 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S213 to S214, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0178] In some embodiments, step S403 above, in response to the firmware update instruction, updating the firmware program of the expansion machine using the firmware update file, may include the following steps:

[0179] S4031: The second underlying program writes the firmware update file into the application mirror area of ​​the non-volatile memory through a low-speed interface or a preset configuration module, according to the address parameters of the updated firmware carried by the firmware update instruction.

[0180] Here, the preset configuration module can be a preset configuration interface provided by the chip manufacturer, such as a dedicated configuration interface for non-volatile memory.

[0181] In some embodiments, optional implementations of step S4031 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S211, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0182] In some embodiments, the idle time slot of the high-speed interface is the blanking interval of a specific image signal transmitted by the high-speed interface.

[0183] For example, a specific image signal is a preset image signal specifically used for updating the firmware of the expansion machine, and the blanking interval can be, for example, the vertical blanking period of the specific image signal, the horizontal blanking period of the image signal, etc.

[0184] By using this method of reusing idle time slots of high-speed interfaces, no additional hardware wiring is required. This not only improves the utilization rate of high-speed channels but also ensures the reliability of control command transmission.

[0185] It should be understood that, for the sake of simplicity of the illustrations, steps S4011, S4021, S404, S405 and S4031 are not shown in the drawings, but they all belong to the preferred embodiments of this application, and their specific implementations have been described in detail in the specification, which does not affect the understanding and implementation of this application by those skilled in the art.

[0186] Figure 7 This is a flowchart illustrating the remote update method for an extender provided in the fifth embodiment of this application. The remote update method is executed by a host computer, which is communicatively connected to a host computer. The host computer acts as an image signal source and is connected to at least one extender. (See attached diagram.) Figure 7 As shown, the method includes the following steps:

[0187] S501: Sends a firmware update file to the host, which is used to transmit the firmware update file to the expansion unit through the high-speed interface used for image transmission between the host and the expansion unit;

[0188] S502: Sends a firmware update command to the host. The firmware update command is transmitted to the expansion unit through the low-speed interface between the host and the expansion unit or through the idle time slot of the multiplexed high-speed interface, so as to instruct the expansion unit to update the expansion unit's firmware program using the firmware update file.

[0189] In some embodiments, optional implementations of step S501 can be found in [reference needed]. Figure 1 Optional implementation methods of step S101, and Figure 1 Other related parts in the embodiments involved will not be described in detail here.

[0190] In some embodiments, optional implementations of step S502 can be found in [reference needed]. Figure 1 Optional implementation methods of step S103, and Figure 1 Other related parts in the embodiments involved will not be described in detail here.

[0191] In some embodiments, the host has a first application and a first underlying program; the extension machine has a second application and a second underlying program.

[0192] In step S501 above, sending the firmware update file to the host may include the following steps:

[0193] S5011: When the host is running in the first low-level program and the extension machine is running in the second low-level program, the firmware update file is sent to the first low-level program. The firmware update file is transmitted by the first low-level program to the second low-level program of the extension machine through the high-speed interface for image transmission between the host and the extension machine.

[0194] In step S502 above, sending the firmware update command to the host may include the following steps:

[0195] S5021: Send the firmware update command to the first underlying program. The firmware update command is transmitted by the first underlying program to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, and then to the second underlying program of the expansion machine.

[0196] In some embodiments, optional implementations of step S5011 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S206 to S207, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0197] In some embodiments, optional implementations of step S5021 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of steps S209 to S210, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0198] In some embodiments, the method may further include the steps of:

[0199] S503: Send a first program jump instruction to the first application to cause the host to switch from running the first application to running the first underlying program;

[0200] S504: Send configuration information to the first underlying program to configure the first underlying program to have data transmission function;

[0201] S505: Send a first program switching instruction to the first underlying program. The first program switching instruction is transmitted from the first underlying program to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second application program to running the second underlying program.

[0202] S506: Send a second program switching instruction to the first underlying program. The second program switching instruction is transmitted from the first underlying program to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second underlying program to running the second application program.

[0203] S507: Send a second program jump instruction to the first underlying program to switch the host from running the first underlying program to running the first application.

[0204] In some embodiments, steps S503 to S505 are performed before step S5011. Steps S506 to S507 are performed after step S5021.

[0205] In some embodiments, optional implementations of step S503 may be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S200, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0206] In some embodiments, optional implementations of step S504 may refer to [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S202, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0207] In some embodiments, optional implementations of step S505 may be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S203, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0208] In some embodiments, optional implementations of step S506 may refer to [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods for steps S213 to S214, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0209] In some embodiments, optional implementations of step S507 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S215, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0210] In some embodiments, step S506 above, sending the second program switching instruction to the first underlying program, may include the following steps:

[0211] S5061: When the time elapsed after sending the firmware update command reaches a preset time, send the second program switching command to the first underlying program; or, obtain the update progress of the expansion machine through the low-speed interface between the host and the expansion machine, and send the second program switching command to the first underlying program after determining that the expansion machine update is completed.

[0212] In some embodiments, optional implementations of step S5061 can be found in [reference needed]. Figure 2 , Figure 3 and Figure 4 Optional implementation methods of step S212, and Figure 2 , Figure 3 , Figure 4 Other related parts in the embodiments involved will not be described in detail here.

[0213] In some embodiments, the idle time slot of the high-speed interface is the blanking interval of a specific image signal transmitted by the high-speed interface.

[0214] For example, a specific image signal is a preset image signal specifically used for updating the firmware of the expansion machine, and the blanking interval can be, for example, the vertical blanking period of the specific image signal, the horizontal blanking period of the image signal, etc.

[0215] By using this method of reusing idle time slots of high-speed interfaces, no additional hardware wiring is required. This not only improves the utilization rate of high-speed channels but also ensures the reliability of control command transmission.

[0216] It should be understood that, for the sake of simplicity of the illustrations, steps S5011, S5021, S503, S504, S505, S506, S507 to S5061 are not shown in the accompanying drawings, but they all belong to the preferred embodiments of this application. Their specific implementations have been described in detail in the specification and do not affect the understanding and implementation of this application by those skilled in the art.

[0217] The various embodiments or implementation methods described in this specification are presented in a progressive manner. Each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other.

[0218] In the various embodiments of the specification, some or all of the steps and their optional implementations can be arbitrarily combined with some or all of the steps in other embodiments, or arbitrarily combined with the optional implementations in other embodiments.

[0219] This application also provides a screen dot display system, including a host computer, a host computer as an image signal source, and at least one extender connected to the host computer:

[0220] The host computer is configured to send a firmware update file to the host computer.

[0221] The host is configured to, upon receiving a firmware update file from a host computer, transmit the firmware update file to the expansion machine via a high-speed interface for image transmission between the host and the expansion machine.

[0222] The host is also configured to, in response to receiving a firmware update command from a host computer, transmit the firmware update command to the expansion machine via a low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface;

[0223] The expansion unit is configured to update its firmware using the firmware update file in response to the firmware update command.

[0224] In some embodiments, the host has a first application and a first underlying program; the extended machine has a second application and a second underlying program; the host is configured to:

[0225] When the host is running on the first low-level program and the expansion machine is running on the second low-level program, the first low-level program, in response to receiving the firmware update file from the host computer, transmits the firmware update file to the second low-level program through the high-speed interface between the host and the expansion machine.

[0226] In response to the received firmware update command, the first underlying program transmits the address parameters of the firmware to be updated carried by the firmware update command to the second underlying program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface.

[0227] In some embodiments, the host is configured to:

[0228] In response to the first application receiving a first program jump instruction from the host computer, the host switches from running the first application to running the first underlying program, and configures the underlying program to have data transmission function according to the configuration information from the host computer;

[0229] In response to receiving a first program switching instruction from the host computer, the first underlying program transmits the first program switching instruction to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second application program to running the second underlying program.

[0230] In some embodiments, the host is configured to:

[0231] In response to receiving a second program switching instruction from the host computer, the first underlying program transmits the second program switching instruction to the second underlying program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second underlying program to running the second application program.

[0232] In response to the first underlying program receiving a second program jump instruction from the host computer, the host switches from running the first underlying program to running the first application program.

[0233] In some embodiments, the expansion unit is configured as follows:

[0234] The second low-level program writes the firmware update file into the application mirror area of ​​the non-volatile memory through a low-speed interface or a preset configuration module, based on the address parameters of the firmware update instruction.

[0235] In some embodiments, the host is configured to:

[0236] The first underlying program obtains the update progress of the expansion machine through the low-speed interface between the host and the expansion machine, and sends the update progress of the expansion machine to the host computer, so that the host computer can send the second program switching instruction to the first underlying program after determining that the expansion machine update is completed.

[0237] In some embodiments, the host computer is configured to:

[0238] When a preset time has elapsed since the firmware update command was sent, a second program switching command is sent to the first underlying program; or...

[0239] The update progress of the expansion machine is obtained through the low-speed interface between the host and the expansion machine, and after determining that the expansion machine update is completed, the second program switching instruction is sent to the first underlying program.

[0240] In some embodiments, the idle time slot of the high-speed interface is the blanking interval of a specific image signal transmitted by the high-speed interface.

[0241] This application also provides an electronic device, including a processor and instructions for invoking instructions to cause the electronic device to perform the steps of the remote update method for an extended machine as provided in any of the foregoing embodiments.

[0242] This application also provides a storage medium, including an executable program stored thereon, which, when executed by a processor, implements the steps of the remote update method for the extended machine as provided in any of the foregoing embodiments.

[0243] For ease of understanding, the following focuses on explaining the terminology used in this embodiment:

[0244] In this application embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a Graphics Processing Unit (GPU) (which can be understood as a type of microprocessor), or a Digital Signal Processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconstructable. For example, the processor is a hardware circuit implemented using an Application-Specific Integrated Circuit (ASIC) or a Programmable Logic Device (PLD), such as an FPGA. In a reconstructable hardware circuit, the processor loads a configuration document, implementing a cyclical process of hardware circuit configuration. This can be understood as the processor loading instructions to implement the functions of some or all of the above units or modules in a cyclical process. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), a Deep Learning Processing Unit (DPU), etc.

[0245] The computer-readable storage medium provided in this embodiment can execute the remote update method of the extended machine in the above embodiment. Its implementation principle and technical effect are similar to those in the above embodiment, and will not be repeated here.

[0246] The aforementioned computer-readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0247] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in an electronic device or a host device.

[0248] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0249] The various embodiments or implementation methods described in this specification are presented in a progressive manner. Each embodiment focuses on the differences from other embodiments, and the same or similar parts between the embodiments can be referred to each other.

[0250] In the description of this specification, references to "one embodiment," "some embodiments," "illustrative embodiment," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with an embodiment or example is included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0251] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A remote update method for an extended machine, characterized in that, The method is executed by a host computer, which acts as an image signal source connected to at least one extender. The host computer has a first application program and a first underlying program; the extender has a second application program and a second underlying program; the method includes: When the host is running on the first low-level program and the expansion machine is running on the second low-level program, the first low-level program, in response to receiving a firmware update file from the host computer, transmits the firmware update file to the second low-level program through the high-speed interface between the host and the expansion machine. In response to the received firmware update command, the first underlying program transmits the address parameters of the firmware to be updated carried by the firmware update command to the second underlying program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface.

2. The remote update method for the extended machine according to claim 1, characterized in that, The method further includes: In response to the first application receiving a first program jump instruction from the host computer, the host switches from running the first application to running the first underlying program, and configures the underlying program to have data transmission function according to the configuration information from the host computer; In response to receiving a first program switching instruction from the host computer, the first underlying program transmits the first program switching instruction to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second application program to running the second underlying program.

3. The remote update method for the extended machine according to claim 1, characterized in that, The method further includes: In response to receiving a second program switching instruction from the host computer, the first underlying program transmits the second program switching instruction to the second underlying program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second underlying program to running the second application program. In response to the first underlying program receiving a second program jump instruction from the host computer, the host switches from running the first underlying program to running the first application program.

4. The remote update method for the extended machine according to claim 3, characterized in that, The method further includes: The first underlying program obtains the update progress of the expansion machine through the low-speed interface between the host and the expansion machine, and sends the update progress of the expansion machine to the host computer, so that the host computer can send the second program switching instruction to the first underlying program after determining that the expansion machine update is completed.

5. The remote update method for the extended machine according to any one of claims 1 to 4, characterized in that, The idle time slot of the high-speed interface is the blanking interval of a specific image signal transmitted by the high-speed interface.

6. A method for remotely updating an extended machine, characterized in that, The method is executed by an extender connected to a host computer, the host computer being configured as an image signal source, the host computer having a first application program and a first underlying program; the extender computer having a second application program and a second underlying program; the method includes: When the host is running on the first low-level program and the expansion machine is running on the second low-level program, the second low-level program receives the firmware update file from the host computer transmitted by the first low-level program through the high-speed interface between the host and the expansion machine. The second low-level program receives the firmware update command from the host computer transmitted by the first low-level program through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface. In response to the firmware update instruction, the firmware program of the expansion machine is updated using the firmware update file.

7. The remote update method for the extended machine according to claim 6, characterized in that, The method further includes: In response to the second application receiving a first program switching instruction through a low-speed interface between the host and the expansion machine or by reusing an idle time slot of the high-speed interface, the expansion machine switches from running the second application to running the second underlying program; In response to the second underlying program receiving a second program switching instruction through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, the expansion machine switches from running the second underlying program to running the second application program.

8. The remote update method for the extended machine according to claim 7, characterized in that, The step of updating the firmware of the expansion device using the firmware update file in response to the firmware update command includes: The second low-level program writes the firmware update file into the application mirror area of ​​the non-volatile memory through a low-speed interface or a preset configuration module, based on the address parameters of the firmware update instruction.

9. A remote update method for an extended machine, characterized in that, The method is executed by a host computer, which is communicatively connected to a host computer. The host computer is connected to at least one extender as an image signal source. The host computer has a first application program and a first underlying program. The extended machine has a second application program and a second underlying program; the method includes: When the host is running a first low-level program and the extension machine is running a second low-level program, a firmware update file is sent to the first low-level program. The firmware update file is transmitted from the first low-level program to the second low-level program of the extension machine through a high-speed interface for image transmission between the host and the extension machine. A firmware update command is sent to the first underlying program. The firmware update command is transmitted by the first underlying program to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, and then to the second underlying program of the expansion machine, so as to instruct the expansion machine to update the firmware program of the expansion machine using the firmware update file.

10. The remote update method for the extended machine according to claim 9, characterized in that, The method further includes: Send a first program jump instruction to the first application to switch the host from running the first application to running the first underlying program; Send configuration information to the first underlying program to configure the first underlying program to have data transmission function; Send a first program switching instruction to the first underlying program. The first program switching instruction is transmitted from the first underlying program to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second application program to running the second underlying program. Send a second program switching instruction to the first underlying program. The second program switching instruction is transmitted from the first underlying program to the expansion machine through the low-speed interface between the host and the expansion machine or by reusing the idle time slot of the high-speed interface, so that the expansion machine switches from running the second underlying program to running the second application program. Send a second program jump instruction to the first underlying program to switch the host from running the first underlying program to running the first application.

11. The remote update method for the extended machine according to claim 10, characterized in that, Sending the second program switching instruction to the first underlying program includes: When a preset time has elapsed since the firmware update command was sent, a second program switching command is sent to the first underlying program; or... The update progress of the expansion machine is obtained through the low-speed interface between the host and the expansion machine, and after determining that the expansion machine update is completed, the second program switching instruction is sent to the first underlying program.

12. A dot-screen system, characterized in that, It includes a host computer, a main unit serving as the image signal source, and at least one expansion unit connected to the main unit: The host computer is configured to execute the remote update method for the extended machine as described in any one of claims 9 to 11; The host is configured to perform the remote update method for the extended machine as described in any one of claims 1 to 5; The extended machine is configured to perform the extended machine remote update method as described in any one of claims 6 to 8.

Images