Cloud-based hardware signal debugging method and device, equipment and medium
By binding the target hardware debugging device and the host machine in the cloud platform, generating a virtual machine debugging environment and transmitting the device, the problem of additional physical machine configuration in hardware cloud debugging methods is solved, achieving low-cost, high-stability and high-efficiency hardware signal debugging.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-01
- Publication Date
- 2026-03-13
AI Technical Summary
Existing hardware cloud-based remote debugging methods require additional configuration of a separate physical machine with a server service program installed, increasing hardware deployment costs and space usage. Furthermore, users are prone to selecting the wrong device, affecting the testing process and resulting in high maintenance complexity.
By defining the binding relationship of the target hardware debugging environment in the cloud platform, calling the IaaS service to generate a virtual machine debugging environment on the target host machine, and passing the target debugging device to the virtual machine, users can remotely access the virtual machine debugging environment in the cloud platform to perform signal debugging, avoiding the need to configure an additional independent physical machine.
It reduces hardware costs, improves debugging stability and user experience, avoids the impact of network latency and bandwidth limitations, reduces maintenance workload, and allows users to see only the equipment required for the current debugging session without interference from other devices.
Smart Images
Figure CN121658147A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of distributed technology, and in particular to cloud-based hardware signal debugging methods, apparatus, devices, and media. Background Technology
[0002] The cloud-based remote debugging process for hardware relies on various peripheral devices such as logic analyzers, oscilloscopes, and JTAG (Joint Test Action Group). To improve the efficiency of remote hardware debugging, it is necessary to ensure efficient and stable connection between the cloud platform and the offline physical debugging equipment.
[0003] Currently, cloud-based hardware debugging solutions require configuring a separate physical machine as a peripheral connection carrier, connecting debugging equipment such as logic analyzers and oscilloscopes to the physical machine, and then deploying a server service on the physical machine. In the virtual machine environment generated by the cloud platform, users establish a connection with the server service via TCP (Transmission Control Protocol) through a client program, thereby indirectly accessing the debugging equipment on the physical machine and completing remote debugging operations of hardware signals.
[0004] However, existing cloud-based remote debugging methods for hardware require additional configuration of a separate physical machine with a server service program installed to connect to peripherals, which increases hardware deployment costs and space usage. Furthermore, all users connect to the server service on the physical machine, and when there are many similar devices on the physical machine, users are more likely to select the wrong device, thereby affecting the testing process of other users. In addition, in order to run the server service program, the physical machine also needs to install the dependency libraries and installation packages required by the server service, which increases maintenance complexity. Summary of the Invention
[0005] This invention provides a cloud-based hardware signal debugging method, apparatus, device, and medium that can directly connect to the debugging device via a cloud platform host, reducing hardware costs. The cloud platform can flexibly control access to the debugging device, resulting in higher stability for user debugging, reduced operational complexity, and effectively improved user experience.
[0006] According to one aspect of the present invention, a cloud-based hardware signal debugging method is provided, comprising:
[0007] When a user initiates a call request to the target hardware debugging environment in the cloud platform, at least one target debugging device that is bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs are identified.
[0008] The IaaS service is invoked to generate a virtual machine debugging environment on the target host machine, and a pass-through command is sent to the target host machine so that the target host machine can pass-through the target debugging device to the virtual machine debugging environment.
[0009] In response to a user's access request to the virtual machine debugging environment initiated in the cloud platform, a connection is established between the cloud platform and the virtual machine debugging environment, allowing the user to remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging in the virtual machine debugging environment.
[0010] According to another aspect of the present invention, a cloud-based hardware signal debugging device is provided, comprising:
[0011] The debugging environment invocation module is used to determine at least one target debugging device that is bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs when a user initiates a request to invoke the target hardware debugging environment in the cloud platform.
[0012] The debugging device pass-through module is used to call the IaaS service to generate a virtual machine debugging environment in the target host machine, and send a pass-through command to the target host machine so that the target host machine can pass-through the target debugging device to the virtual machine debugging environment.
[0013] The signal debugging module is used to respond to the user's access request to the virtual machine debugging environment initiated in the cloud platform, establish a connection between the cloud platform and the virtual machine debugging environment, so that the user can remotely access the virtual machine debugging environment in the cloud platform and perform hardware signal debugging in the virtual machine debugging environment.
[0014] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:
[0015] At least one processor; and
[0016] A memory communicatively connected to the at least one processor; wherein,
[0017] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the cloud-based hardware signal debugging method according to any embodiment of the present invention.
[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the cloud-based hardware signal debugging method according to any embodiment of the present invention.
[0019] The technical solution of this invention, when a user initiates a request to access a target hardware debugging environment in a cloud platform, determines at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs. It then invokes an IaaS service to generate a virtual machine debugging environment on the target host machine and sends a pass-through instruction to the target host machine, allowing the target host machine to pass-through the target debugging device to the virtual machine debugging environment. In response to a user's access request to the virtual machine debugging environment in the cloud platform, a connection is established between the cloud platform and the virtual machine debugging environment, allowing the user to remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging within the virtual machine debugging environment. This method eliminates the need for additional dedicated physical machines, allowing direct connection of debugging equipment to the cloud platform's host machine. This reduces hardware costs, and users only see the debugging equipment required for the current task, avoiding interference from other devices. It eliminates the need for shared server services, ensuring that even if other users encounter problems, the current hardware debugging remains unaffected, significantly improving stability. Furthermore, it avoids the impact of network latency and bandwidth limitations. The host machine does not require the installation of server service dependencies and packages, reducing maintenance workload and avoiding software compatibility issues. The cloud platform can flexibly control virtual machine access to devices, virtual machine device allocation, and resource reclamation, all of which can be adjusted as needed.
[0020] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description
[0021] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0022] Figure 1 This is a flowchart of a cloud-based hardware signal debugging method according to Embodiment 1 of the present invention;
[0023] Figure 2 This is a schematic diagram illustrating the binding relationship between a hardware debugging environment and a debugging device according to an embodiment of the present invention;
[0024] Figure 3 This is a flowchart of another cloud-based hardware signal debugging method provided according to Embodiment 2 of the present invention;
[0025] Figure 4This is a schematic diagram of a cloud-based hardware signal debugging device according to Embodiment 3 of the present invention;
[0026] Figure 5 This is a schematic diagram of the structure of an electronic device that implements the cloud-based hardware signal debugging method of this invention. Detailed Implementation
[0027] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.
[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0029] Example 1
[0030] Figure 1 This is a flowchart of a cloud-based hardware signal debugging method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where users perform signal debugging on hardware on a cloud platform. The method can be executed by a cloud-based hardware signal debugging device, which can be implemented in hardware and / or software and is generally configured in a cloud server or cloud processor with data processing capabilities. Figure 1 As shown, the method includes:
[0031] S110. When a user initiates a call request to the target hardware debugging environment in the cloud platform, at least one target debugging device that is bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs are determined.
[0032] Optionally, multiple hardware debugging environments can be pre-established in the cloud platform. A hardware debugging environment can be used to complete a specific debugging scenario. When a user initiates a hardware debugging request in the cloud platform, the cloud platform can display all currently available hardware debugging environments for the user to choose from, and the target hardware debugging environment is the debugging environment currently selected by the user.
[0033] Optionally, when creating a hardware debugging environment on the cloud platform, a debugging device attribute list is created in the hardware debugging environment. The debugging device attribute list maintains the device identifiers of all debugging devices required for the hardware debugging environment and the host machine identifiers to which the devices belong.
[0034] Optionally, after the user selects the target hardware debugging environment in the cloud platform, the cloud platform confirms that the user has initiated a call request to the target hardware debugging environment in the cloud platform. Then, based on the debugging device attribute list of the target hardware debugging environment, the platform reads the debugging device identifier, determines the target debugging device that is bound to the target hardware debugging environment based on the debugging device identifier, and reads the host machine identifier to which the target debugging device belongs.
[0035] Specifically, before determining at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs when a user initiates a call request to the target hardware debugging environment in the cloud platform, the following may also be included:
[0036] Based on the user's hardware debugging needs, multiple hardware debugging environments are established in the cloud platform, and the debugging equipment required for each hardware debugging environment is determined.
[0037] In each hardware debugging environment, a debugging device attribute list is created, and the device identifier of the debugging device required by the hardware debugging environment and the host machine identifier to which the device belongs are maintained in the debugging device attribute list, so as to bind the debugging device and the host machine to which the debugging device belongs to the hardware debugging environment.
[0038] Optionally, hardware can refer to physical hardware that supports remote debugging in fields such as electronic engineering, industrial automation, and embedded development. This may include, but is not limited to, FPGA (Field-Programmable Gate Array), MCU (Microcontroller Unit), DSP (Digital Signal Processor), and SoC (System on a Chip).
[0039] Figure 2 This is a schematic diagram illustrating the binding relationship between an optional hardware debugging environment and debugging equipment. For example... Figure 2 As shown, taking FPGA as an example, FPGA1, FPGA2, and FPGAn represent multiple different FPGA debugging environments. Each FPGA debugging environment points to a list of debugging device attributes. In the list, Vendor ID is the manufacturer identifier, Product ID is the product identifier, Serial Num is the debugging device serial number, and Host IP is the host machine's Internet Protocol address. Figure 2 This is for illustrative purposes only.
[0040] Optionally, after determining the debugging devices required for each hardware debugging environment, a USB device information viewing command, such as the lsusb -v command, can be invoked to view the device identification information and the actual host information of each debugging device currently being maintained. Then, the device identification of the debugging device required by the hardware debugging environment and the host identification to which the device belongs can be read and written into the debugging device attribute list. Once the device identification and the host identification to which the device belongs are written into the list, it means that the debugging device has been bound to the hardware debugging environment. A bound debugging device does not support being bound to other hardware debugging devices.
[0041] Specifically, when a user initiates a request to access the target hardware debugging environment on the cloud platform, identifying at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs may include:
[0042] When a user initiates a call request to the target hardware debugging environment in the cloud platform, the device identifier and host identifier maintained in the device attribute list of the target hardware debugging environment are read.
[0043] Based on the device identifier and host identifier maintained in the device attribute list, determine the target debugging device that is bound to the target hardware debugging environment and the target host to which the target debugging device belongs.
[0044] Specifically, before determining at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs when a user initiates a call request to the target hardware debugging environment in the cloud platform, the following may also be included:
[0045] When a user accesses the hardware signal debugging function in the cloud platform, the system displays unoccupied, available hardware debugging environments for the user to choose from, based on the current occupancy status of each hardware debugging environment in the cloud platform.
[0046] Optionally, the current occupancy status can refer to the usage status of each hardware debugging environment recorded in real time by the cloud platform, including whether the environment has been invoked by the user, whether the corresponding target debugging device has been passed through, and whether the virtual machine debugging environment is running. The usage status of each hardware debugging environment can include occupancy status and idle status.
[0047] Optionally, when a user logs into the cloud platform and clicks the hardware signal debugging function entry, the cloud platform automatically queries the hardware debugging environment status database. The hardware debugging environment status database updates the current occupancy status of each hardware debugging environment in real time. Based on the query results, the cloud platform filters out idle hardware debugging environments, i.e., environments that have not been called by any user, where the target debugging device is in an untransparent idle state and has no associated running virtual machine. The cloud platform displays the filtered idle hardware debugging environments to the user in the form of a list. The list may include information such as environment name, associated debugging device type, and host machine location, allowing the user to select according to their own debugging needs. If all environments are occupied, the cloud platform will prompt the user that there are currently no idle environments to avoid operation conflicts caused by the user selecting an already occupied environment.
[0048] S120. Call the IaaS service to generate a virtual machine debugging environment in the target host machine, and send a pass-through instruction to the target host machine so that the target host machine can pass-through the target debugging device to the virtual machine debugging environment.
[0049] Optionally, IaaS service refers to Infrastructure as a Service, which is a basic resource service module provided by the cloud platform. IaaS service can create and manage virtual machines on a specified host machine according to needs, and at the same time complete the basic environment initialization required for virtual machine debugging.
[0050] Optionally, the virtual machine debugging environment is a temporary virtual machine environment generated by the IaaS service on the target host machine. It has the software foundation required for hardware debugging and can identify the target debugging device through pass-through technology. The user operation experience is consistent with local debugging.
[0051] Optionally, the pass-through command is a control command sent by the cloud platform to the target host machine to trigger the device pass-through operation of the host machine. The command contains the unique identifier of the target debugging device and the identifier of the hardware virtual machine debugging environment, thereby ensuring that the host machine accurately maps the specified device to the virtual machine.
[0052] The process of calling IaaS services to generate a virtual machine debugging environment on the target host and sending a pass-through command to the target host so that the target host can pass-through the target debugging device to the virtual machine debugging environment may include:
[0053] The IaaS service is invoked to generate a temporary virtual machine on the target host machine, and the basic environment required for hardware debugging is initialized in the temporary virtual machine to generate the virtual machine debugging environment;
[0054] Send a pass-through command to the target host machine so that the target host machine can capture the pass-through command through the cloud platform listening service and pass the target debugging device to the virtual machine debugging environment according to the pass-through command.
[0055] Optionally, a temporary virtual machine refers to a virtual machine dynamically created by an IaaS service on a target host machine for a single hardware debugging session. It will be recycled after the debugging is completed to avoid resource waste and has an independent operating system and debugging environment.
[0056] Optionally, the IaaS service can automatically configure the basic environment in the temporary virtual machine. The basic environment initialization may include installing the drivers required for debugging software, system dependency libraries, and basic debugging tools, ensuring that the virtual machine can be used directly for debugging.
[0057] Optionally, the cloud platform monitoring service can refer to a service program deployed on the target host machine, which is used to monitor the instructions sent by the cloud platform in real time, and trigger the corresponding device operation after receiving the instructions.
[0058] Optionally, after receiving the pass-through instruction, the target host machine can pass-through the target debugging device to the virtual machine debugging environment, thereby making the virtual machine debugging environment believe that it is a physical device directly connected to the target debugging device. The virtual machine debugging environment will display that these target debugging devices are connected, and then these target debugging devices can be used directly in the virtual machine debugging environment.
[0059] S130. In response to the user's access request for the virtual machine debugging environment initiated in the cloud platform, establish a connection between the cloud platform and the virtual machine debugging environment so that the user can remotely access the virtual machine debugging environment in the cloud platform and perform hardware signal debugging in the virtual machine debugging environment.
[0060] In response to a user's access request to the virtual machine debugging environment initiated on the cloud platform, after establishing a connection between the cloud platform and the virtual machine debugging environment so that the user can remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging in the virtual machine debugging environment, it may further include:
[0061] When it is determined that the user has completed the current hardware signal debugging, disconnect the pass-through connection between the virtual machine debugging environment and the target debugging device, and reclaim the target debugging device.
[0062] Optionally, the pass-through connection can be a device mapping channel between the target debugging device and the virtual machine debugging environment. Through this channel, the virtual machine can control the device as if it were a local connection. If the connection is broken, the virtual machine will not be able to recognize the device.
[0063] Optionally, after the transparent connection is disconnected, the target debugging device can be unloaded from the virtual machine debugging environment and the device resources can be released to ensure that the device resources can be recycled.
[0064] Optionally, after receiving the user's end-of-debugging operation, the cloud platform first confirms the pass-through status between the current virtual machine debugging environment and the target debugging device. Then, it sends a command to the target host to disconnect the pass-through connection. The command includes the virtual machine identifier of the virtual machine debugging environment and the device identifier of the target debugging device. After receiving the command, the cloud platform listening service on the target host calls the command to unload the virtual machine pass-through device, disconnecting the pass-through connection between the target debugging device and the virtual machine debugging environment. At this time, executing the lsusb command in the virtual machine debugging environment will no longer display the target debugging device, indicating that the pass-through connection has been disconnected. After confirming that the pass-through connection is disconnected, the cloud platform sends a virtual machine reclamation request to the IaaS service. The IaaS service reclaims the CPU, memory, storage, and other resources of the temporary virtual machine, and marks the target debugging device as idle, updating the device status database of the cloud platform to complete the reclamation of device resources.
[0065] The technical solution of this invention, when a user initiates a request to access a target hardware debugging environment in a cloud platform, determines at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs. It then invokes an IaaS service to generate a virtual machine debugging environment on the target host machine and sends a pass-through instruction to the target host machine, allowing the target host machine to pass-through the target debugging device to the virtual machine debugging environment. In response to a user's access request to the virtual machine debugging environment in the cloud platform, a connection is established between the cloud platform and the virtual machine debugging environment, allowing the user to remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging within the virtual machine debugging environment. This method eliminates the need for additional dedicated physical machines, allowing direct connection of debugging equipment to the cloud platform's host machine. This reduces hardware costs, and users only see the debugging equipment required for the current task, avoiding interference from other devices. It eliminates the need for shared server services, ensuring that even if other users encounter problems, the current hardware debugging remains unaffected, significantly improving stability. Furthermore, it avoids the impact of network latency and bandwidth limitations. The host machine does not require the installation of server service dependencies and packages, reducing maintenance workload and avoiding software compatibility issues. The cloud platform can flexibly control virtual machine access to devices, virtual machine device allocation, and resource reclamation, all of which can be adjusted as needed.
[0066] Example 2
[0067] Figure 3 This is a flowchart illustrating a cloud-based hardware signal debugging method according to Embodiment 2 of the present invention. Based on the above embodiments, this embodiment specifically describes a cloud-based hardware signal debugging method. Figure 3 As shown, the method includes:
[0068] S210. Based on the user's hardware debugging needs, establish multiple hardware debugging environments in the cloud platform and determine the debugging equipment required for each hardware debugging environment.
[0069] S220. In each hardware debugging environment, create a debugging device attribute list and maintain the device identifier of the debugging device required by the hardware debugging environment and the host machine identifier to which the device belongs in the debugging device attribute list, so as to bind the debugging device and the host machine to which the debugging device belongs to the hardware debugging environment.
[0070] The device identifier includes at least the manufacturer identifier, product identifier, and serial number; the host machine identifier to which the device belongs includes at least the host machine's Internet Protocol address and hostname; and the debugging device is connected to the host machine via USB protocol.
[0071] S230. When a user initiates a call request to the target hardware debugging environment in the cloud platform, the device identifier and host identifier maintained in the device attribute list of the target hardware debugging environment are read.
[0072] S240. Based on the device identifier and host identifier maintained in the device attribute list, determine the target debugging device that is bound to the target hardware debugging environment and the target host to which the target debugging device belongs.
[0073] S250: Call the IaaS service to generate a temporary virtual machine in the target host machine, and initialize the basic environment required for hardware debugging in the temporary virtual machine to generate the virtual machine debugging environment.
[0074] S260. Send a pass-through instruction to the target host machine so that the target host machine can capture the pass-through instruction through the cloud platform listening service and pass-through the target debugging device to the virtual machine debugging environment according to the pass-through instruction.
[0075] S270: In response to the user's access request for the virtual machine debugging environment initiated in the cloud platform, establish a connection between the cloud platform and the virtual machine debugging environment so that the user can remotely access the virtual machine debugging environment in the cloud platform and perform hardware signal debugging in the virtual machine debugging environment.
[0076] S280. When it is determined that the user has completed the current hardware signal debugging, disconnect the transparent connection between the virtual machine debugging environment and the target debugging device, and reclaim the target debugging device.
[0077] The technical solution of this invention, when a user initiates a request to access a target hardware debugging environment in a cloud platform, determines at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs. It then invokes an IaaS service to generate a virtual machine debugging environment on the target host machine and sends a pass-through instruction to the target host machine, allowing the target host machine to pass-through the target debugging device to the virtual machine debugging environment. In response to a user's access request to the virtual machine debugging environment in the cloud platform, a connection is established between the cloud platform and the virtual machine debugging environment, allowing the user to remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging within the virtual machine debugging environment. This method eliminates the need for additional dedicated physical machines, allowing direct connection of debugging equipment to the cloud platform's host machine. This reduces hardware costs, and users only see the debugging equipment required for the current task, avoiding interference from other devices. It eliminates the need for shared server services, ensuring that even if other users encounter problems, the current hardware debugging remains unaffected, significantly improving stability. Furthermore, it avoids the impact of network latency and bandwidth limitations. The host machine does not require the installation of server service dependencies and packages, reducing maintenance workload and avoiding software compatibility issues. The cloud platform can flexibly control virtual machine access to devices, virtual machine device allocation, and resource reclamation, all of which can be adjusted as needed.
[0078] Example 3
[0079] Figure 4 This is a schematic diagram of a cloud-based hardware signal debugging device provided in Embodiment 3 of the present invention. Figure 4 As shown, the device includes: a debugging environment calling module 310, a debugging equipment transparent transmission module 320, and a signal debugging module 330.
[0080] The debugging environment invocation module 310 is used to determine at least one target debugging device that is bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs when a user initiates a request to invoke the target hardware debugging environment in the cloud platform.
[0081] The debugging device pass-through module 320 is used to call the IaaS service to generate a virtual machine debugging environment in the target host machine, and send a pass-through command to the target host machine so that the target host machine can pass-through the target debugging device to the virtual machine debugging environment.
[0082] The signal debugging module 330 is used to respond to the user's access request for the virtual machine debugging environment initiated in the cloud platform, establish a connection between the cloud platform and the virtual machine debugging environment, so that the user can remotely access the virtual machine debugging environment in the cloud platform and perform hardware signal debugging in the virtual machine debugging environment.
[0083] The technical solution of this invention, when a user initiates a request to access a target hardware debugging environment in a cloud platform, determines at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs. It then invokes an IaaS service to generate a virtual machine debugging environment on the target host machine and sends a pass-through instruction to the target host machine, allowing the target host machine to pass-through the target debugging device to the virtual machine debugging environment. In response to a user's access request to the virtual machine debugging environment in the cloud platform, a connection is established between the cloud platform and the virtual machine debugging environment, allowing the user to remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging within the virtual machine debugging environment. This method eliminates the need for additional dedicated physical machines, allowing direct connection of debugging equipment to the cloud platform's host machine. This reduces hardware costs, and users only see the debugging equipment required for the current task, avoiding interference from other devices. It eliminates the need for shared server services, ensuring that even if other users encounter problems, the current hardware debugging remains unaffected, significantly improving stability. Furthermore, it avoids the impact of network latency and bandwidth limitations. The host machine does not require the installation of server service dependencies and packages, reducing maintenance workload and avoiding software compatibility issues. The cloud platform can flexibly control virtual machine access to devices, virtual machine device allocation, and resource reclamation, all of which can be adjusted as needed.
[0084] Based on the above embodiments, a debugging device binding module may also be included, used for:
[0085] Based on the user's hardware debugging needs, multiple hardware debugging environments are established in the cloud platform, and the debugging equipment required for each hardware debugging environment is determined.
[0086] In each hardware debugging environment, a debugging device attribute list is created, and the device identifier of the debugging device required by the hardware debugging environment and the host machine identifier to which the device belongs are maintained in the debugging device attribute list, so as to bind the debugging device and the host machine to which the debugging device belongs to the hardware debugging environment.
[0087] Based on the above embodiments, the device identifier includes at least the manufacturer identifier, product identifier, and serial number, and the host machine identifier to which the device belongs includes at least the host machine's Internet Protocol address and hostname; wherein, the debugging device is connected to the host machine via USB protocol.
[0088] Based on the above embodiments, the debugging environment calling module 310 can be specifically used for:
[0089] When a user initiates a call request to the target hardware debugging environment in the cloud platform, the device identifier and host identifier maintained in the device attribute list of the target hardware debugging environment are read.
[0090] Based on the device identifier and host identifier maintained in the device attribute list, determine the target debugging device that is bound to the target hardware debugging environment and the target host to which the target debugging device belongs.
[0091] Based on the above embodiments, the debugging equipment transparent transmission module 320 can be specifically used for:
[0092] The IaaS service is invoked to generate a temporary virtual machine on the target host machine, and the basic environment required for hardware debugging is initialized in the temporary virtual machine to generate the virtual machine debugging environment;
[0093] Send a pass-through command to the target host machine so that the target host machine can capture the pass-through command through the cloud platform listening service and pass the target debugging device to the virtual machine debugging environment according to the pass-through command.
[0094] Based on the above embodiments, a resource recycling module may also be included, for:
[0095] When it is determined that the user has completed the current hardware signal debugging, disconnect the pass-through connection between the virtual machine debugging environment and the target debugging device, and reclaim the target debugging device.
[0096] Based on the above embodiments, a debugging environment display module may also be included, used for:
[0097] When a user accesses the hardware signal debugging function in the cloud platform, the system displays unoccupied, available hardware debugging environments for the user to choose from, based on the current occupancy status of each hardware debugging environment in the cloud platform.
[0098] The cloud-based hardware signal debugging device provided in this embodiment of the invention can execute the cloud-based hardware signal debugging method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.
[0099] Example 4
[0100] Figure 5 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.
[0101] like Figure 5As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0102] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0103] Processor 11 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, central processing unit (CPU), graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the cloud-based hardware signal debugging method described in the embodiments of the present invention. That is:
[0104] When a user initiates a call request to the target hardware debugging environment in the cloud platform, at least one target debugging device that is bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs are identified.
[0105] The IaaS service is invoked to generate a virtual machine debugging environment on the target host machine, and a pass-through command is sent to the target host machine so that the target host machine can pass-through the target debugging device to the virtual machine debugging environment.
[0106] In response to a user's access request to the virtual machine debugging environment initiated in the cloud platform, a connection is established between the cloud platform and the virtual machine debugging environment, allowing the user to remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging in the virtual machine debugging environment.
[0107] In some embodiments, the cloud-based hardware signal debugging method can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the cloud-based hardware signal debugging method described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to perform the cloud-based hardware signal debugging method by any other suitable means (e.g., by means of firmware).
[0108] Various implementations of the systems and techniques described above herein can be realized in digital electronic circuit systems, integrated circuit systems, (hardware), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include: implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0109] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0110] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0111] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0112] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.
[0113] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.
[0114] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.
[0115] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.
Claims
1. A cloud-based hardware signal debugging method, characterized in that, include: When a user initiates a call request to the target hardware debugging environment in the cloud platform, at least one target debugging device that is bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs are identified. The IaaS service is invoked to generate a virtual machine debugging environment on the target host machine, and a pass-through command is sent to the target host machine so that the target host machine can pass-through the target debugging device to the virtual machine debugging environment. In response to a user's access request to the virtual machine debugging environment initiated in the cloud platform, a connection is established between the cloud platform and the virtual machine debugging environment, allowing the user to remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging in the virtual machine debugging environment.
2. The method according to claim 1, characterized in that, Before determining at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs when a user initiates a call request to the target hardware debugging environment in the cloud platform, the process also includes: Based on the user's hardware debugging needs, multiple hardware debugging environments are established in the cloud platform, and the debugging equipment required for each hardware debugging environment is determined. In each hardware debugging environment, a debugging device attribute list is created, and the device identifier of the debugging device required by the hardware debugging environment and the host machine identifier to which the device belongs are maintained in the debugging device attribute list, so as to bind the debugging device and the host machine to which the debugging device belongs to the hardware debugging environment.
3. The method according to claim 2, characterized in that, The device identifier includes at least the manufacturer identifier, product identifier, and serial number, and the host machine identifier to which the device belongs includes at least the host machine's Internet Protocol address and hostname; wherein, the debugging device is connected to the host machine via USB protocol.
4. The method according to claim 1, characterized in that, When a user initiates a request to access the target hardware debugging environment on the cloud platform, at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs are identified, including: When a user initiates a call request to the target hardware debugging environment in the cloud platform, the device identifier and host identifier maintained in the device attribute list of the target hardware debugging environment are read. Based on the device identifier and host identifier maintained in the device attribute list, determine the target debugging device that is bound to the target hardware debugging environment and the target host to which the target debugging device belongs.
5. The method according to claim 1, characterized in that, The process involves invoking IaaS services to generate a virtual machine debugging environment on the target host machine and sending a pass-through command to the target host machine, enabling the target host machine to pass-through the target debugging device to the virtual machine debugging environment. This includes: The IaaS service is invoked to generate a temporary virtual machine on the target host machine, and the basic environment required for hardware debugging is initialized in the temporary virtual machine to generate the virtual machine debugging environment; Send a pass-through command to the target host machine so that the target host machine can capture the pass-through command through the cloud platform listening service and pass the target debugging device to the virtual machine debugging environment according to the pass-through command.
6. The method according to claim 1, characterized in that, After responding to a user's access request to the virtual machine debugging environment initiated in the cloud platform, establishing a connection between the cloud platform and the virtual machine debugging environment so that the user can remotely access the virtual machine debugging environment from the cloud platform and perform hardware signal debugging in the virtual machine debugging environment, the process also includes: When it is determined that the user has completed the current hardware signal debugging, disconnect the pass-through connection between the virtual machine debugging environment and the target debugging device, and reclaim the target debugging device.
7. The method according to claim 1, characterized in that, Before determining at least one target debugging device bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs when a user initiates a call request to the target hardware debugging environment in the cloud platform, the process also includes: When a user accesses the hardware signal debugging function in the cloud platform, the system displays unoccupied, available hardware debugging environments for the user to choose from, based on the current occupancy status of each hardware debugging environment in the cloud platform.
8. A cloud-based hardware signal debugging device, characterized in that, include: The debugging environment invocation module is used to determine at least one target debugging device that is bound to the target hardware debugging environment and the target host machine to which the target debugging device belongs when a user initiates a request to invoke the target hardware debugging environment in the cloud platform. The debugging device pass-through module is used to call the IaaS service to generate a virtual machine debugging environment in the target host machine, and send a pass-through command to the target host machine so that the target host machine can pass-through the target debugging device to the virtual machine debugging environment. The signal debugging module is used to respond to the user's access request to the virtual machine debugging environment initiated in the cloud platform, establish a connection between the cloud platform and the virtual machine debugging environment, so that the user can remotely access the virtual machine debugging environment in the cloud platform and perform hardware signal debugging in the virtual machine debugging environment.
9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the cloud-based hardware signal debugging method according to any one of claims 1-7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the cloud-based hardware signal debugging method according to any one of claims 1-7.