A method, system and apparatus for embedded cloud debugging

Abstract

The application relates to a method, system and device for embedded cloud debugging, and belongs to the technical field of software debugging. The method comprises the following steps: monitoring a plurality of embedded devices in real time to obtain device states; determining at least one embedded software to be debugged based on a debugging task; determining at least one target device for debugging from the plurality of embedded devices based on the embedded software to be debugged, related information of the embedded devices and the device states; loading each embedded software to be debugged to the corresponding target device; establishing a corresponding cloud debugging channel between an operation terminal initiating debugging and the embedded software to be debugged of the target device; and debugging the embedded software to be debugged based on each cloud debugging channel, sending debugging instructions from the operation terminal, obtaining debugging data and performing parallel debugging on the embedded software to be debugged. The application realizes concurrent debugging of a plurality of embedded software by using a web browser of a working PC.

Description

Technical Field

[0001] This invention belongs to the field of software debugging technology, and in particular relates to a method, system and device for embedded cloud debugging. Background Technology

[0002] A new round of technological revolution and industrial transformation is in full swing. Embedded software development, as one of the best carriers for the integration and application of new technologies, is also accelerating its transformation towards cloud integration. Embedded software has become a core growth driver for the development of intelligent industrial industries. The functional complexity of electronic systems in the military industry is increasing exponentially, and the proportion of software continues to grow. Front-end embedded integration online development environments will become a new breakthrough point in the research and development and deployment of embedded software.

[0003] Traditional embedded operating system software debuggers can only perform one-to-one debugging of a single embedded device from a single PC locally. Embedded software debugging is strongly restricted by spatial location; the target device must be physically wired to the working PC, and the working PC needs to have the corresponding platform's (Mac, Linux, Windows) debugging software installed. This is very inconvenient and cannot meet the functional requirements of online development and online debugging. Therefore, a device and method that supports online debugging is needed to work with online development software to realize the online debugging process. Summary of the Invention

[0004] Based on the above analysis, the present invention aims to provide a method, system, and apparatus for embedded cloud debugging, enabling concurrent debugging of multiple embedded software programs via an operating terminal, i.e., a working PC, using a web browser.

[0005] On the one hand, the present invention provides a method for embedded cloud debugging, specifically including the following steps:

[0006] Real-time monitoring of multiple embedded devices to obtain device status;

[0007] Based on the debugging task, identify at least one embedded software to be debugged;

[0008] Based on the embedded software to be debugged, the relevant information of the embedded device, and the device status, at least one target device for debugging is determined from multiple embedded devices;

[0009] Load each embedded software to be debugged onto the corresponding target device;

[0010] Establish a corresponding cloud debugging channel between the operating terminal that initiates the debugging and the embedded software to be debugged in the target device;

[0011] Based on each of the cloud debugging channels, debugging commands are sent from the operation terminal to debug the embedded software to be debugged, debugging data is obtained, and the embedded software to be debugged is debugged in parallel.

[0012] Furthermore, the device status includes the device's online status, offline status, and operating status; the relevant information includes the device identifier, the maximum number of software debugs required by the device, and the number of debugging software programs occupied by the device.

[0013] Furthermore, determining at least one target device for debugging from multiple embedded devices based on the embedded software to be debugged, the relevant information of the embedded device, and the device status includes:

[0014] The available devices are determined based on the online and offline status of the embedded device;

[0015] Based on the available devices, obtain the maximum number of software debuggers for the corresponding device, the number of debugging software programs used by the device, and the device's operating status; wherein, the operating status includes the device's CPU utilization and memory utilization.

[0016] The available devices are traversed, and when a device that meets preset conditions is encountered, that device is determined as one of the target devices. The target device is determined based on the embedded software to be debugged, the maximum number of software to be debugged on the device, and the number of debugging software occupied by the device. 4. The embedded cloud debugging method according to claim 3, wherein the preset conditions include:

[0017] The number of devices requiring debugging software is less than the maximum number of devices that can be debugged.

[0018] The CPU utilization rate of the device is less than the preset CPU threshold;

[0019] The device's memory occupancy rate is less than the preset memory threshold.

[0020] Furthermore, establishing a corresponding cloud debugging channel between the operating terminal initiating the debugging and the embedded software to be debugged on the target device includes:

[0021] The operating terminal and the device debugging software located on the cloud server communicate via HTTP and WebSocket, and establish a cloud debugging channel through the device debugging software based on the target device identifier and the embedded software identifier to be debugged;

[0022] The establishment of a cloud debugging channel through the device debugging software includes: the device debugging software establishing a cloud debugging channel based on the target device identifier and the embedded software identifier to be debugged, through a packaged GDB and a GDB-Server installed on the target device.

[0023] Furthermore, the encapsulated GDB refers to the encapsulation of GDB-Client, including:

[0024] The device debugging software establishes a communication channel with GDB-Client through CMD and obtains the input and output streams of CMD. The input handle of CMD is used to send debugging commands to GDB-Client, and the output handle of CMD is used to obtain debugging information from GDB-Client.

[0025] The device debugging software listens to the output stream of CMD and obtains the debugging command response information from GDB-Client.

[0026] Furthermore, based on each of the cloud debugging channels, debugging commands are sent from the operation terminal to debug the embedded software to be debugged, debugging data is obtained, and parallel debugging of the embedded software to be debugged is performed, including:

[0027] Based on each of the cloud debugging channels, the operating terminal sends debugging instructions to the device debugging software;

[0028] The device debugging software sends the debugging command to the GDB-Client via CMD;

[0029] The GDB-Client uses the debugging commands to debug the embedded software through the GDB-Server installed on the target device;

[0030] The target device's GDB-Server returns the debugging results to the GDB-Client;

[0031] The GDB-Client sends debugging data to the device debugging software via CMD;

[0032] The device debugging software feeds back the debugging data to the operating terminal.

[0033] On the other hand, the present invention also provides an embedded cloud debugging system, the system comprising an operating terminal and a cloud server:

[0034] The operation terminal is used to send debugging commands to multiple embedded software programs to be debugged in parallel through the cloud server and to receive debugging data through the cloud server.

[0035] The cloud server is used to debug the embedded software loaded on the target device in parallel based on the debugging instructions of the operating terminal, and to feed back the debugging data to the operating terminal.

[0036] Furthermore, the cloud server includes: device management software, device monitoring software, and device debugging software;

[0037] The device monitoring software is used to monitor embedded devices in real time and obtain device status.

[0038] The device management software is used to manage relevant information about the device. Based on at least one embedded software to be debugged, the device status, and the relevant information, it determines at least one target device for debugging from multiple embedded devices and loads each embedded software to be debugged onto the corresponding target device.

[0039] The device debugging software is used to receive debugging instructions from the operating terminal, debug the embedded software to be debugged, acquire debugging data, and provide feedback to the operating terminal.

[0040] On the other hand, the present invention provides an implementation apparatus for an embedded cloud debugging method, comprising:

[0041] Memory, used to store computer programs;

[0042] A processor, used to execute computer programs, implements the embedded cloud debugging method.

[0043] The present invention can achieve at least one of the following beneficial effects:

[0044] By centrally managing multiple embedded devices and monitoring their status in real time, the system can identify target devices for debugging based on the devices' operating status and the embedded software to be debugged, thereby enabling centralized and rational utilization of device resources for embedded software debugging.

[0045] By establishing a cloud debugging channel between the operating terminal and the embedded software to be debugged on the target device, users can debug the embedded software on the target device without installing other software. They only need to use a web browser on the operating terminal (i.e., the working PC) and complete the authentication process; there is no need to directly connect the target device and the working PC.

[0046] By establishing a cloud debugging channel based on the target device identifier and the embedded software identifier to be debugged, users can concurrently debug multiple embedded software programs through an operating terminal, solving the problem that traditional embedded software debugging can only be performed one-to-one.

[0047] Other features and advantages of the invention will be set forth in the following description, and some advantages may become apparent from the description or be learned by practicing the invention. The objects and other advantages of the invention may be realized and obtained from what is particularly pointed out in the description, claims, and drawings. Attached Figure Description

[0048] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Throughout the drawings, the same reference numerals denote the same parts.

[0049] Figure 1 This is a flowchart of an embodiment of the method of the present invention;

[0050] Figure 2 This is a schematic diagram of the cloud debugging channel in an embodiment of the method of the present invention;

[0051] Figure 3 This is a schematic diagram of the GDB principle encapsulated in the method embodiment of the present invention;

[0052] Figure 4 This is a schematic diagram illustrating the process of the operating terminal initiating debugging of the embedded software to be debugged in an embodiment of the method of the present invention;

[0053] Figure 5 This is a system architecture diagram for embedded cloud debugging in an embodiment of the present invention;

[0054] Figure 6 This is a comparison diagram between the implementation device of the embedded cloud debugging method in the embodiment of the present invention and a traditional embedded debugging device. Detailed Implementation

[0055] Preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which form part of this application and are used together with the embodiments of the present invention to illustrate the principles of the present invention, but are not intended to limit the scope of the present invention.

[0056] Method Implementation Examples

[0057] Example 1

[0058] A specific embodiment of the present invention discloses a method for embedded cloud debugging, which specifically includes the following steps:

[0059] Step S01: Monitor multiple embedded devices in real time and obtain device status.

[0060] Specifically, embedded devices refer to devices equipped with embedded operating systems, used for debugging embedded software. Multiple embedded devices are monitored in real time using device monitoring software located on a cloud server. Device status includes online status, offline status, and operating status.

[0061] Optionally, the device monitoring software attempts to establish Telnet channels with each of the multiple embedded devices, and determines whether the device is online or offline based on the establishment status of the Telnet channels.

[0062] Specifically, for devices that are online, their operating status can be obtained by executing commands through the established Telnet channel.

[0063] Specifically, the device's operating status includes its CPU utilization and memory utilization. Optionally, based on the established Telnet channel, the "ps" command is executed to obtain the process running information of the device's embedded operating system, including PID, CPU utilization, memory utilization, process status, and priority; optionally, the total CPU utilization and memory utilization of the device are calculated based on the CPU utilization and memory utilization of each process.

[0064] Step S02: Identify at least one embedded software to be debugged based on the debugging task.

[0065] Specifically, the debugging task includes one or more embedded software programs to be debugged. The embedded software runs on an embedded operating system, which is an operating system installed on the embedded device. Preferably, the embedded operating system used is the Haiying Yihui operating system.

[0066] Specifically, based on the debugging task, one or more embedded software programs to be debugged are identified.

[0067] Step S03: Based on the embedded software to be debugged, the relevant information of the embedded device, and the device status, determine at least one target device for debugging from multiple embedded devices.

[0068] Specifically, relevant information about embedded devices includes device identifier, maximum number of software debuggers, and the amount of debugging software required.

[0069] Specifically, the maximum number of software programs a device can debug refers to the maximum number of embedded software programs that the device can load and debug.

[0070] Optionally, the maximum number of software debuggers for the device, appMax, is a preset value; preferably, 2≤appMax≤5.

[0071] Specifically, the number of device debugging software occupied refers to the number of embedded software currently loaded on the device and being debugged, appSize, where appSize≤appMax.

[0072] S03-1. Determine available devices based on the online and offline status of the embedded device.

[0073] Specifically, when a device is online, it is considered a usable device.

[0074] S03-2. Based on the available devices, obtain the maximum number of software debuggers for the corresponding device, the number of debugging software occupied by the device, and the operating status of the device; wherein, the operating status includes the CPU utilization rate and memory utilization rate of the device.

[0075] S03-3. Traverse the available devices. When a device that meets the preset conditions is encountered, determine that device as one of the target devices. Determine the target device based on the embedded software to be debugged and the device that meets the preset conditions.

[0076] Specifically, the available devices are traversed, and when a traversed device meets preset conditions, that device is determined to be one of the target devices; the preset conditions include:

[0077] The number of devices requiring debugging software is less than the maximum number of devices that can be debugged.

[0078] The CPU utilization rate of the device is less than the preset CPU threshold;

[0079] Optionally, the preset CPU threshold is set based on empirical values; preferably, the preset CPU threshold is 80%.

[0080] The device's memory occupancy rate is less than a preset memory threshold;

[0081] Optionally, the preset memory threshold is set based on empirical values; preferably, the preset memory threshold is 80% of the total memory.

[0082] Specifically, the number of debuggable embedded software programs for a device that meets the preset conditions = the maximum number of debuggable software programs for the device - the number of debuggable software programs required by the device.

[0083] The target device is determined based on the number of debuggable embedded software programs for the embedded software to be debugged and the number of debuggable embedded software programs for devices that meet preset conditions.

[0084] S04. Load each embedded software to be debugged onto the corresponding target device.

[0085] Specifically, the software to be debugged is loaded onto the corresponding target device through the device management software on the cloud server.

[0086] S05. Establish a corresponding cloud debugging channel between the operation terminal that initiates the debugging and the embedded software to be debugged in the target device;

[0087] The operating terminal and the device debugging software located on the cloud server communicate via HTTP and WebSocket, and establish a cloud debugging channel through the device debugging software based on the target device identifier and the embedded software identifier to be debugged;

[0088] The establishment of a cloud debugging channel through the device debugging software includes: the device debugging software establishing a cloud debugging channel based on the target device identifier and the embedded software identifier to be debugged, through a packaged GDB and a GDB-Server installed on the target device.

[0089] like Figure 2 This diagram illustrates how multiple cloud debugging channels are established between an operating terminal and a target device for various embedded software programs to be debugged. Specifically, each operating terminal can establish at least one cloud debugging channel or multiple cloud debugging channels with the embedded software programs to be debugged on the target device.

[0090] Specifically, the encapsulated GDB refers to the encapsulation of GDB-Client, including:

[0091] The device debugging software establishes a communication channel with GDB-Client through CMD and obtains the input and output streams of CMD. The input handle of CMD is used to send debugging commands to GDB-Client, and the output handle of CMD is used to obtain debugging information from GDB-Client.

[0092] The device debugging software listens to the output stream of CMD and obtains the debugging command response information from GDB-Client.

[0093] like Figure 3 The diagram shown is a schematic of the encapsulated GDB principle.

[0094] Specifically, the GDB-Client and the GDB-Server installed on the target device establish a communication channel via the Telnet protocol.

[0095] For example, Table 1 provides some of the GDB debugging commands.

[0096]

[0097]

[0098] Table 1. Some GDB debugging commands

[0099] S06. Based on each of the cloud debugging channels, send debugging instructions from the operation terminal to debug the embedded software to be debugged, obtain debugging data, and perform parallel debugging on the embedded software to be debugged.

[0100] Specifically, including:

[0101] Based on each of the cloud debugging channels, the operating terminal uses a web browser to send debugging commands to the device debugging software; specifically, the operating terminal communicates with the device debugging software via HTTP and WebSocket.

[0102] The device debugging software sends the debugging command to the GDB-Client via CMD;

[0103] The GDB-Client uses debugging commands to debug the embedded software via the GDB-Server installed on the target device; the GDB-Client and GDB-Server communicate via the Telnet protocol.

[0104] The target device's GDB-Server returns the debugging results to the GDB-Client;

[0105] GDB-Client sends debugging data back to the device debugging software via CMD;

[0106] The device debugging software sends debugging data back to the operating terminal via HTTP and WebSocket.

[0107] Figure 4 The process of initiating debugging of the embedded software to be debugged from the operating terminal is illustrated.

[0108] Optional debugging functions include start debugging, breakpoint operation, step-in / step-out, and stop debugging.

[0109] This embodiment discloses an embedded cloud debugging method. By centrally managing multiple embedded devices and monitoring their status in real time, and based on the device's operating status and the embedded software to be debugged, a target device suitable for debugging is determined from multiple embedded devices, thus achieving centralized and rational utilization of device resources for embedded software debugging. By establishing a cloud debugging channel between the operating terminal and the embedded software to be debugged on the target device, users do not need to install other software when debugging embedded software. They only need to send debugging commands and receive debugging data to the embedded software through the cloud debugging channel on the operating terminal, i.e., the working PC, using a web browser.

[0110] In this embodiment, by establishing a cloud debugging channel based on the target device identifier and the embedded software identifier to be debugged, users can concurrently debug multiple embedded software programs to be debugged through an operating terminal.

[0111] System Implementation Examples

[0112] An embedded cloud debugging system, the system adopting a B / S architecture, includes an operating terminal and a cloud server:

[0113] Specifically, the operating terminal, i.e., the working PC, is used to send debugging commands and receive debugging data in parallel to multiple embedded software programs to be debugged through the cloud server; the cloud server is used to debug the embedded software loaded on the target device in parallel based on the debugging commands of the operating terminal, and to feed back the debugging data to the operating terminal.

[0114] Specifically, the operating terminal uses a web browser to communicate with the cloud server via HTTP and WebSocket. Users log in to the cloud server using a web browser after authentication, and then send debugging commands and receive debugging data from the embedded software to be debugged through the web browser.

[0115] Specifically, cloud servers include device management software, device monitoring software, and device debugging software:

[0116] The device monitoring software is used to monitor embedded devices in real time and obtain device status; after obtaining the device status, the device monitoring software registers the device status with the device management software.

[0117] Device management software is used to manage relevant information about devices, identify target devices for debugging, and load the embedded software to be tested onto the target devices.

[0118] Specifically, the relevant information includes the device identifier, the maximum number of software debugs required for the device, and the number of debugging software programs required for the device.

[0119] Specifically, the device management software determines at least one target device for debugging from multiple embedded devices based on at least one embedded software to be debugged, the device status, and the relevant information, and loads each embedded software to be debugged onto the corresponding target device.

[0120] The device debugging software is used to receive debugging instructions from the operating terminal, debug the embedded software to be debugged, acquire debugging data, and provide feedback to the operating terminal.

[0121] Figure 5 The system architecture diagram for embedded cloud debugging is shown.

[0122] This embodiment discloses an embedded cloud debugging system that enables users to debug embedded software without installing other software. They can simply use a web browser on their operating terminal (work PC) and complete authentication to debug the embedded software on the target device via a cloud server.

[0123] Device Examples

[0124] An apparatus for implementing an embedded cloud debugging method includes:

[0125] Memory, used to store computer programs;

[0126] A processor, used to execute a computer program, implements the embedded cloud debugging method described in the method embodiments.

[0127] like Figure 6 The diagram shows the implementation device of the embedded cloud debugging method of the present invention, and a comparison diagram with a traditional embedded debugging device.

[0128] This embodiment discloses an implementation device for an embedded cloud debugging method. By establishing a cloud debugging channel based on the target device identifier and the embedded software identifier to be debugged, users can concurrently debug multiple embedded software programs to be debugged through an operating terminal, solving the problem that traditional embedded software debugging can only be performed one-to-one.

[0129] It should be noted that the above embodiments are based on the same inventive concept, and any parts not described repeatedly can be referenced from each other.

[0130] The above description is only a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for embedded cloud debugging, characterized in that, include: Real-time monitoring of multiple embedded devices to obtain device status; Based on the debugging task, identify at least one embedded software to be debugged; Based on the embedded software to be debugged, the relevant information of the embedded device, and the device status, at least one target device for debugging is determined from multiple embedded devices; Load each embedded software to be debugged onto the corresponding target device; A corresponding cloud debugging channel is established between the operating terminal initiating the debugging and the embedded software to be debugged on the target device, including: The operating terminal and the device debugging software located on the cloud server communicate via HTTP and WebSocket, and establish a cloud debugging channel through the device debugging software based on the target device identifier and the embedded software identifier to be debugged; The device debugging software establishes a cloud debugging channel based on the target device identifier and the embedded software identifier to be debugged, through the encapsulated GDB and the GDB-Server installed on the target device; The encapsulated GDB refers to the encapsulation of GDB-Client, including: the device debugging software establishes a communication channel with GDB-Client through CMD and obtains the input and output streams of CMD. The input handle of CMD is used to send debugging commands to GDB-Client, and the output handle of CMD is used to obtain debugging information from GDB-Client. The device debugging software listens to the output stream of CMD and obtains the debugging command response information from GDB-Client; The GDB-Client and the GDB-Server installed on the target device establish a communication channel via the Telnet protocol; Based on each of the cloud debugging channels, debugging commands are sent from the operation terminal to debug the embedded software to be debugged, debugging data is obtained, and the embedded software to be debugged is debugged in parallel. The operating terminal does not require the installation of debugging software. After authentication via a web browser, it sends debugging commands to the device debugging software via HTTP and WebSocket, and receives debugging data from the device debugging software via HTTP and WebSocket.

2. The embedded cloud debugging method according to claim 1, characterized in that, The device status includes the device's online status, offline status, and operating status; the relevant information includes the device identifier, the maximum number of software debugs the device can perform, and the number of debugging software programs required.

3. The embedded cloud debugging method according to claim 2, characterized in that, The step of determining at least one target device for debugging from multiple embedded devices based on the embedded software to be debugged, the relevant information of the embedded device, and the device status includes: The available devices are determined based on the online and offline status of the embedded device; Based on the available devices, obtain the maximum number of software debuggers for the corresponding device, the number of debugging software programs used by the device, and the device's operating status; wherein, the operating status includes the device's CPU utilization and memory utilization. The available devices are traversed, and when a device that meets the preset conditions is found, it is determined as one of the target devices. The target device is determined based on the embedded software to be debugged, the maximum number of software to be debugged on the device, and the number of debugging software occupied by the device.

4. The embedded cloud debugging method according to claim 3, characterized in that, The preset conditions include: The number of devices requiring debugging software is less than the maximum number of devices that can be debugged. The CPU utilization rate of the device is less than the preset CPU threshold; The device's memory occupancy rate is less than the preset memory threshold.

5. The embedded cloud debugging method according to any one of claims 1-4, characterized in that, Based on each of the cloud debugging channels, debugging commands are sent from the operation terminal to debug the embedded software to be debugged, debugging data is obtained, and parallel debugging of the embedded software to be debugged is performed, including: Based on each of the cloud debugging channels, the operating terminal sends debugging instructions to the device debugging software; The device debugging software sends the debugging command to the GDB-Client via CMD; The GDB-Client uses the debugging commands to debug the embedded software through the GDB-Server installed on the target device; The target device's GDB-Server returns the debugging results to the GDB-Client; The GDB-Client sends debugging data to the device debugging software via CMD; The device debugging software feeds back the debugging data to the operating terminal.

6. An embedded cloud debugging system, characterized in that, The system includes an operating terminal and a cloud server: The operation terminal is used to send debugging commands to multiple embedded software programs to be debugged in parallel through the cloud server and to receive debugging data through the cloud server. The cloud server is used to debug the embedded software loaded on the target device in parallel based on the debugging instructions of the operating terminal, and to feed back the debugging data to the operating terminal. The cloud server includes: device management software, device monitoring software, and device debugging software; The device monitoring software is used to monitor embedded devices in real time and obtain device status. The device management software is used to manage relevant information about the device. Based on at least one embedded software to be debugged, the device status, and the relevant information, it determines at least one target device for debugging from multiple embedded devices and loads each embedded software to be debugged onto the corresponding target device. The device debugging software is used to receive debugging instructions from the operating terminal, debug the embedded software to be debugged, acquire debugging data, and feed it back to the operating terminal. The operating terminal and the device debugging software located on the cloud server communicate via HTTP and WebSocket, and establish a cloud debugging channel through the device debugging software based on the target device identifier and the embedded software identifier to be debugged; The device debugging software establishes a cloud debugging channel based on the target device identifier and the embedded software identifier to be debugged, through the encapsulated GDB and the GDB-Server installed on the target device; The encapsulated GDB refers to the encapsulation of GDB-Client, including: the device debugging software establishes a communication channel with GDB-Client through CMD and obtains the input and output streams of CMD. The input handle of CMD is used to send debugging commands to GDB-Client, and the output handle of CMD is used to obtain debugging information from GDB-Client. The device debugging software listens to the output stream of CMD and obtains the debugging command response information from GDB-Client; The GDB-Client and the GDB-Server installed on the target device establish a communication channel via the Telnet protocol; The operating terminal does not require the installation of debugging software. After authentication via a web browser, it sends debugging commands to the device debugging software via HTTP and WebSocket, and receives debugging data from the device debugging software via HTTP and WebSocket.

7. An implementation device for an embedded cloud debugging method, characterized in that, The device includes: Memory, used to store computer programs; A processor, when executing a computer program, implements the embedded cloud debugging method as described in any one of claims 1-5.

Images