CN117033107A - Debugging method, device, storage medium and equipment supporting different interfaces - Google Patents
Debugging method, device, storage medium and equipment supporting different interfaces Download PDFInfo
- Publication number
- CN117033107A CN117033107A CN202311264946.4A CN202311264946A CN117033107A CN 117033107 A CN117033107 A CN 117033107A CN 202311264946 A CN202311264946 A CN 202311264946A CN 117033107 A CN117033107 A CN 117033107A
- Authority
- CN
- China
- Prior art keywords
- unified
- command
- debugging
- interfaces
- task request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000012545 processing Methods 0.000 claims abstract description 26
- 238000004458 analytical method Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 13
- 238000004806 packaging method and process Methods 0.000 claims description 6
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 239000000284 extract Substances 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012005 ligant binding assay Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
- G06F11/2221—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested to test input/output devices or peripheral units
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
According to the debugging method, device, storage medium and equipment supporting different interfaces, after the debugging commands corresponding to the different interfaces are received, the different types of debugging commands are converted into unified task requests in a unified format, and the unified task requests are marked according to the different types of debugging commands, so that the unified task requests can be processed based on one set of processing logic.
Description
Technical Field
The present application relates to the field of information processing technologies, and in particular, to a method, an apparatus, a storage medium, and a device for supporting different interfaces.
Background
Currently, the custom debug interfaces of the mainstream flash memory storage products include interfaces with different physical forms, such as UFS (Universal Flash Storage, universal flash) interfaces, UART (Universal Asynchronous Receiver/Transmitter, asynchronous transceiver) serial interfaces, and other physical interfaces. The UFS performs debugging by sending a Vendor Command, and the UART sends a Cli Command to perform debugging.
Because of the limitation of resources such as storage device code space, the common storage device is only suitable for a single interface, such as UFS or UART, and if the UFS and UART need to be supported simultaneously, different processing codes need to be developed in the storage device for the UFS and UART respectively. Not only increases the complexity of code development, but also increases the occupation of storage device resource space.
Disclosure of Invention
The technical problems to be solved by the application are as follows: the method, the device, the storage medium and the equipment for supporting the debugging of different interfaces are provided, and the occupation of resource space is reduced while the sharing of different interfaces is realized through unified processing logic.
In order to solve the technical problems, the application adopts the following technical scheme:
a method of debugging supporting different interfaces, comprising:
receiving debug commands from at least two interfaces, wherein the interfaces are different in interface types;
generating a unified task request according to the debug command, and attaching an interface type of an interface corresponding to the debug command to the unified task request;
and executing the unified task request through the unified request node to complete debugging.
In order to solve the technical problems, the application adopts another technical scheme that:
a debug apparatus supporting different interfaces, comprising:
the analysis module is used for receiving debugging commands from at least two interfaces, and the interfaces are different in interface types; generating a unified task request according to the debug command, and attaching an interface type of an interface corresponding to the debug command to the unified task request;
and the processing module is used for executing the unified task request through the unified request node to complete debugging.
In order to solve the technical problems, the application adopts another technical scheme that:
a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of a debug method supporting different interfaces as described above.
In order to solve the technical problems, the application adopts another technical scheme that:
an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing steps in a debug method supporting different interfaces as described above when the computer program is executed.
The application has the beneficial effects that: after receiving the debug commands corresponding to different interfaces, the different types of debug commands are converted into unified task requests in a unified format, and the unified task requests are marked according to the different types of debug commands, so that the unified task requests can be processed based on a set of processing logic.
Drawings
FIG. 1 is a flow chart of steps of a method for supporting debugging of different interfaces according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a debugging device supporting different interfaces according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to describe the technical contents, the achieved objects and effects of the present application in detail, the following description will be made with reference to the embodiments in conjunction with the accompanying drawings.
Referring to fig. 1, a debug method supporting different interfaces includes:
receiving debug commands from at least two interfaces, wherein the interfaces are different in interface types;
generating a unified task request according to the debug command, and attaching an interface type of an interface corresponding to the debug command to the unified task request;
and executing the unified task request through the unified request node to complete debugging.
From the above description, the beneficial effects of the application are as follows: after receiving the debug commands corresponding to different interfaces, the different types of debug commands are converted into unified task requests in a unified format, and the unified task requests are marked according to the different types of debug commands, so that the unified task requests can be processed based on a set of processing logic.
Further, the interface comprises a UFS interface;
the receiving debug commands from at least two interfaces includes:
and acquiring the UFS command from the UFS interface in a query mode.
As is apparent from the above description, by acquiring the debug command of the UFS interface by means of a query, the debug command input from the UFS interface can be effectively acquired and identified.
Further, the generating a unified task request according to the debug command, and attaching the interface type of the interface corresponding to the debug command to the unified task request includes:
analyzing the UFS command according to a preset data requirement to obtain target parameter information;
and packaging the target parameter information into the unified task request, and attaching a corresponding interface type as a UFS interface to the unified task request.
As can be seen from the above description, the UFS command is parsed according to the preset data requirement to obtain the target parameter information, the target parameter information is packaged into the unified task request, and the unified task request is marked as the UFS interface, so that the conversion from the UFS command to the unified task request is realized, and the debug command received by the UFS can be processed based on unified logic.
Further, the analyzing the UFS command according to the preset data requirement, and obtaining the target parameter information includes:
and acquiring the UFS command according to a UFS protocol, and acquiring the position of a preset data demand in the UFS command through the UFS protocol to obtain the target parameter information.
As can be seen from the above description, the parameter information in the UFS command can be effectively extracted based on the UFS protocol to acquire and parse the UFS command, thereby generating the target parameter information.
Further, the interface includes a UART interface;
the receiving debug commands from at least two interfaces includes:
and acquiring the UART command from the UART interface in an interrupt mode.
As can be seen from the above description, by acquiring the debug command of the UART interface in an interrupt manner, the debug command input from the UART interface can be effectively acquired and identified.
Further, the obtaining, by an interrupt, the UART command from the UART interface includes:
acquiring a debugging command from the UART interface and identifying a character string corresponding to the debugging command;
judging whether the character string contains characters corresponding to the UART interface, if so, the debugging command is the UART command.
As can be seen from the above description, after obtaining the debug command from the UART interface, the character string in the debug command is identified, so as to accurately determine whether the input debug command is the UART command corresponding to the UART interface, avoid that an effective unified task request cannot be generated, and improve the processing precision of the debug command.
Further, the generating a unified task request according to the debug command, and attaching the interface type of the interface corresponding to the debug command to the unified task request includes:
extracting target parameter information in the character string according to preset data requirements;
and packaging the target parameter information into the unified task request, and attaching a corresponding interface type to the unified task request as a UART interface.
As can be seen from the above description, the target parameter information corresponding to the UART command is obtained by presetting the data requirement and extracting the character string, so that the conversion from the second type of command to the unified task request is realized based on the target parameter information.
Further, after generating the unified task request according to the debug command, the method further comprises:
and mounting the unified task request to a task list.
As can be seen from the above description, the generated unified task request is mounted on the task list, so that the task request is cached, and thus, the corresponding unified task request can be obtained according to the actual debugging requirement for debugging.
Further, before the unified task request is executed by the unified request node, the method further includes:
scanning the task list;
judging whether at least one unified task request is mounted in the task list, if yes, sequentially acquiring the unified task requests, and executing the unified task requests;
if not, stopping scanning.
As can be seen from the above description, the unified task request in the task list is obtained by scanning, so that the unified task request in the task list can be timely processed, and when the unified task request does not exist in the task list, scanning is stopped, so that unnecessary energy consumption is avoided.
Further, the scanning the task list includes:
judging whether a preset scanning period is reached, if so, executing the step of scanning the task list.
As can be seen from the above description, the task list is scanned through the preset period, so that the task list can be scanned according to the scan period corresponding to the actual debug scene setting.
Further, the executing the unified task request by the unified request node includes:
invoking business logic corresponding to the unified task request;
and executing the unified task request according to the business logic.
As can be seen from the above description, the unified task request can be accurately executed by calling the service logic corresponding to the unified task request to execute, so as to process the debug commands input by different interfaces based on the same set of processing logic.
Another embodiment of the present application provides a debug apparatus supporting different interfaces, including:
the analysis module is used for receiving debugging commands from at least two interfaces, and the interfaces are different in interface types; generating a unified task request according to the debug command, and attaching an interface type of an interface corresponding to the debug command to the unified task request;
and the processing module is used for executing the unified task request through the unified request node to complete debugging.
Further, the analysis module comprises a UFS analysis module; the UFS parsing module is configured to execute each step of the above-described debugging method supporting different interfaces.
Further, the analysis module comprises a UART analysis module; the UART analysis module is used for executing the steps of the debugging method supporting different interfaces.
Further, the processing module is configured to perform the steps of a debugging method supporting different interfaces as described above.
Another embodiment of the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of a debug method supporting different interfaces as described above.
Another embodiment of the present application provides an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing steps in a debugging method supporting different interfaces as described above when the computer program is executed.
The debugging method, device, storage medium and equipment supporting different interfaces can be suitable for debugging various types of interfaces, and can simultaneously execute more than two debugging interfaces, namely interfaces compatible with different physical forms, and the following description is given by taking a UFS interface and a UART as examples:
example 1
Referring to fig. 1, a debug method supporting different interfaces includes:
s0, setting the format of the UFS device processing debugging command as follows: cmdOpcode (1 Byte) +parameter1 (4 Byte) +parameter2 (4 Byte) +parameter3 (4 Byte) +parameter4 (4 Byte); taking opcode+4x parameter= 5/11/22/33/44 as an example, i.e. cmdpode=5, parameter1=11, parameter2=22, parameter3=33, parameter4=44; wherein, the function corresponding to the definition of opcode=5 in the UFS device is to write a specific address of the UFS device as a specific data pattern (data pattern); the functional meaning of parameters parameter1-parameter4 is: starting from logical block address (Logical Block Address, LBA) 11, write data pattern (3344), the write data length is 22 LBAs;
for the UFS interface, the system receives a Command received from a host interface (UFS interface) in a query mode, judges whether the Command is a Vendor Command, and if so, receives relevant parameters from the host, and analyzes and extracts the parameters; and assigning the extracted parameter information (such as the type of the Vendor Command, the data length of the operation, etc.) to a newly generated unified task request, and processing the unified task request through a unified request node (ReqNode).
For UART interfaces, the system judges whether commands received from the UART interfaces exist in an interrupt mode, judges whether the commands are Cli commands, if so, extracts and assigns information of the Cli commands to a newly generated unified task request, and processes the unified task request through a unified request node (Reqnode), and the method is specific:
s1, receiving debugging commands from at least two interfaces, wherein the interfaces are different in interface type;
s11, sending a UFS interface debugging command: the host (host) sends a standard UFS command to the UFS device over the UFS interface: a Write Buffer (Write Buffer) Command (0 x 3B) is written, and the payload data of the Command is appended with the pending vector Command information (i.e. 5/11/22/33/44 is packed into a specific field of the payload data), and the total packet size after the packing is 512 bytes. And when the UFS equipment receives the debugging command from the UFS interface, acquiring the UFS command from the UFS interface in a query mode.
S12, transmitting a UART interface debugging command, wherein the user inputs a character string through a UART interface, and the input character string is 'UartCmd 5 11 22 33 44'; the "UartCmd" is a custom recognition character, by which an input character string is recognized as a valid CLI Command, and the recognition character can be modified according to the actual situation of the user. When receiving a debugging command from a UART interface, acquiring the UART command from the UART interface in an interrupt mode.
S2, generating a unified task request according to the debug command, and attaching an interface type of an interface corresponding to the debug command to the unified task request;
s21, for a debugging command from a UFS interface, after analyzing the UFS command according to a preset data requirement to obtain target parameter information, packaging the target parameter information into the unified task request, and attaching a corresponding interface type as the UFS interface in the unified task request; specific:
s211, acquiring the UFS command according to a UFS protocol, namely, UFS equipment receives 512 bytes of data through a standard UFS protocol;
s212, acquiring the position of the preset data requirement in the UFS Command through the UFS protocol to obtain the target parameter information, namely acquiring the Vendor Command effective information: opcode+4 x parameter= 5/11/22/33/44;
s213, mounting the unified task request to a task list, and specifically: the UFS equipment creates a unified task request, gives the target parameter information to the unified task request, and sets the Type (Type) of the unified task request as UFS, wherein the Type UFS can be defined as 1, if Reqnode.Type=1 is obtained, the source is UFS; then the unified task request is mounted to a task list (PendingList) to be processed by the unified request node;
s22, for a debugging command from a UART interface, the method comprises the following steps:
s221, acquiring a debugging command from the UART interface, and identifying a character string corresponding to the debugging command;
s222, judging whether the character string contains characters corresponding to the UART interface or not, if so, the debugging command is the UART command; the resulting string is "urartcmd 5 11 22 33 44", and the string contains the identification character "urartcmd", which identifies a valid CLI Command;
s223, extracting target parameter information in the character string according to preset data requirements; namely extracting '5 11 22 33 44' in the character string;
s224, packaging the target parameter information into the unified task request, and attaching a corresponding interface type to the unified task request as a UART interface, wherein the specific interface type is: the UFS equipment creates a unified task request, gives the target parameter information to the unified task request, and sets the Type (Type) of the unified task request as UART, wherein the Type UART can be defined as 2, if reqnode.Tyoe=2 is obtained, and the source is UART; then the unified task request is mounted to a task list (PendingList) to be processed by the unified request node;
s3, executing the unified task request through a unified request node to finish debugging; specific:
s31, judging whether a preset scanning period is reached, if so, executing the step of scanning the task list, namely, the step S31;
s32, scanning the task list, judging whether at least one unified task request is mounted in the task list, and if yes, executing the step S32; if not, stopping the scanning exit flow;
s33, sequentially acquiring the unified task requests and executing the unified task requests; and if the unified task request is opcode+4x parameter= 5/11/22/33/44, calling service logic corresponding to the unified task request, namely calling corresponding write logic, and realizing write operation of an address corresponding to the UFS according to the write logic to complete the unified task request and debug.
Example two
Referring to fig. 2, a debugging device supporting different interfaces includes:
the analysis module is used for receiving debugging commands from at least two interfaces, and the interfaces are different in interface types; generating a unified task request according to the debug command, and attaching an interface type of an interface corresponding to the debug command to the unified task request; the analysis module comprises a UFS analysis module and a UART analysis module; the UFS parsing module is configured to perform command collection and processing steps corresponding to the UFS interface in a debug method supporting different interfaces as described in the first embodiment; namely: adding a host interface (UFS interface) Vendor Command analysis module, specifically analyzing the debug Command initiated by the UFS interface, and generating the unified task request for processing by a subsequent processing module;
the UART parsing module is configured to execute the steps of collecting and processing the commands corresponding to the UART interface in the debugging method supporting different interfaces according to the first embodiment; namely: adding a UART interface Cli Command analysis module, specifically analyzing a debugging Command initiated by the UART interface, and generating the unified task request for processing by a subsequent processing module; and the processing module is used for executing the unified task request through the unified request node to complete debugging. The processing module is used for executing the step of uniformly requesting the node to process the debugging command in the debugging method supporting different interfaces according to the first embodiment; namely: and a Reqnode processing module is added to specially process the request nodes generated by different interfaces, and the Reqnode generated by two interfaces is processed by using the same set of processing logic.
Example III
A computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of a debug method supporting different interfaces as described in embodiment one.
Example IV
Referring to fig. 3, an electronic device includes a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements steps in a debugging method supporting different interfaces according to the first embodiment when the computer program is executed.
In summary, according to the method, the device, the storage medium and the equipment for supporting the debugging of the different interfaces provided by the application, after the debugging commands corresponding to the different interfaces are received, the different types of debugging commands are converted into the unified task requests in the unified format, and the unified task requests are marked according to the different types of debugging commands, so that the unified task requests can be processed based on a set of processing logic.
In the foregoing embodiments of the present application, it should be understood that the disclosed method, apparatus, computer readable storage medium and electronic device may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple components or modules may be combined or integrated into another apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with respect to each other may be an indirect coupling or communication connection via some interfaces, devices or components or modules, which may be in electrical, mechanical, or other forms.
The components illustrated as separate components may or may not be physically separate, and components shown as components may or may not be physical modules, i.e., may be located in one place, or may be distributed over multiple network modules. Some or all of the components may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each component may exist alone physically, or two or more modules may be integrated into one module. The integrated modules may be implemented in hardware or in software functional modules.
The integrated modules, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It should be noted that, for the sake of simplicity of description, the foregoing method embodiments are all expressed as a series of combinations of actions, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily all required for the present application.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to the related descriptions of other embodiments.
The foregoing description is only illustrative of the present application and is not intended to limit the scope of the application, and all equivalent changes made by the specification and drawings of the present application, or direct or indirect application in the relevant art, are included in the scope of the present application.
Claims (17)
1. A method of debugging supporting different interfaces, comprising:
receiving debug commands from at least two interfaces, wherein the interfaces are different in interface types;
generating a unified task request according to the debug command, and attaching an interface type of an interface corresponding to the debug command to the unified task request;
and executing the unified task request through the unified request node to complete debugging.
2. A method of debugging in support of disparate interfaces in accordance with claim 1, wherein the interfaces comprise UFS interfaces;
the receiving debug commands from at least two interfaces includes:
and acquiring the UFS command from the UFS interface in a query mode.
3. The method for supporting different interfaces according to claim 2, wherein generating a unified task request according to the debug command, and attaching the interface type of the interface corresponding to the debug command to the unified task request includes:
analyzing the UFS command according to a preset data requirement to obtain target parameter information;
and packaging the target parameter information into the unified task request, and attaching a corresponding interface type as a UFS interface to the unified task request.
4. A method for supporting different interfaces according to claim 3, wherein said parsing the UFS command according to a preset data requirement to obtain target parameter information includes:
and acquiring the UFS command according to a UFS protocol, and acquiring the position of a preset data demand in the UFS command through the UFS protocol to obtain the target parameter information.
5. A method of debugging in support of different interfaces according to claim 1, wherein the interfaces comprise UART interfaces;
the receiving debug commands from at least two interfaces includes:
and acquiring the UART command from the UART interface in an interrupt mode.
6. The method according to claim 5, wherein the obtaining UART commands from the UART interface by interrupt includes:
acquiring a debugging command from the UART interface and identifying a character string corresponding to the debugging command;
judging whether the character string contains characters corresponding to the UART interface, if so, the debugging command is the UART command.
7. The method for supporting different interfaces according to claim 6, wherein generating a unified task request according to the debug command, and attaching the interface type of the interface corresponding to the debug command to the unified task request comprises:
extracting target parameter information in the character string according to preset data requirements;
and packaging the target parameter information into the unified task request, and attaching a corresponding interface type to the unified task request as a UART interface.
8. The method for supporting different interfaces according to claim 1, wherein after generating a unified task request according to the debug command, further comprises:
and mounting the unified task request to a task list.
9. The method for supporting different interfaces according to claim 8, wherein before said executing said unified task request by a unified request node further comprises:
scanning the task list;
judging whether at least one unified task request is mounted in the task list, if yes, sequentially acquiring the unified task requests, and executing the unified task requests;
if not, stopping scanning.
10. The method of claim 9, wherein scanning the task list comprises:
judging whether a preset scanning period is reached, if so, executing the step of scanning the task list.
11. A method of debugging in support of disparate interfaces according to claim 1, wherein the performing the unified task request by the unified request node comprises:
invoking business logic corresponding to the unified task request;
and executing the unified task request according to the business logic.
12. A debug apparatus supporting different interfaces, comprising:
the analysis module is used for receiving debugging commands from at least two interfaces, and the interfaces are different in interface types; generating a unified task request according to the debug command, and attaching an interface type of an interface corresponding to the debug command to the unified task request;
and the processing module is used for executing the unified task request through the unified request node to complete debugging.
13. The debugging apparatus supporting different interfaces according to claim 12, wherein the parsing module comprises a UFS parsing module;
the UFS parsing module is configured to perform the steps of a debugging method supporting different interfaces as claimed in any one of claims 2-4.
14. The debugging apparatus supporting different interfaces according to claim 12, wherein the parsing module comprises a UART parsing module;
the UART parsing module is configured to perform the steps of a debugging method supporting different interfaces according to any one of claims 5-7.
15. A debug apparatus supporting different interfaces as claimed in claim 12, wherein said processing module is arranged to perform the steps of a debug method supporting different interfaces as claimed in any one of claims 8 to 11.
16. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the steps of a method of debugging supporting different interfaces as claimed in any one of claims 1-11.
17. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of a method of debugging supporting different interfaces as claimed in any one of claims 1-11 when the computer program is executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311264946.4A CN117033107A (en) | 2023-09-28 | 2023-09-28 | Debugging method, device, storage medium and equipment supporting different interfaces |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311264946.4A CN117033107A (en) | 2023-09-28 | 2023-09-28 | Debugging method, device, storage medium and equipment supporting different interfaces |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117033107A true CN117033107A (en) | 2023-11-10 |
Family
ID=88632035
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311264946.4A Pending CN117033107A (en) | 2023-09-28 | 2023-09-28 | Debugging method, device, storage medium and equipment supporting different interfaces |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117033107A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050138644A1 (en) * | 2003-12-19 | 2005-06-23 | Montecalvo Mark V. | Method, apparatus, system, and article of manufacture for interfacing a device |
| CN101788888A (en) * | 2010-02-09 | 2010-07-28 | 中兴通讯股份有限公司 | Method for realizing target end driver and target end driver |
| CN108027755A (en) * | 2015-10-23 | 2018-05-11 | 英特尔Ip公司 | Support using external input/output interface to testing, debugging or the devices, systems, and methods of the transmission of tracked information |
| CN208141371U (en) * | 2018-05-18 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of multi-functional UART debugging board |
| CN110727420A (en) * | 2019-09-06 | 2020-01-24 | 广东宝莱特医用科技股份有限公司 | Serial port compatible method and system |
| CN113179330A (en) * | 2021-05-25 | 2021-07-27 | 浙江浙大西投脑机智能科技有限公司 | External equipment connection management system compatible with multiple hardware interface specifications and hardware communication protocols |
| CN113918132A (en) * | 2021-12-13 | 2022-01-11 | 珠海市新德汇信息技术有限公司 | Equipment standardization management method, system, working method, device and storage medium |
| CN114546736A (en) * | 2022-01-13 | 2022-05-27 | 宁波小匠物联网科技有限公司 | Automatic serial port testing method |
| CN116795435A (en) * | 2022-03-15 | 2023-09-22 | 华为技术有限公司 | Compatibility management and control method and related equipment |
-
2023
- 2023-09-28 CN CN202311264946.4A patent/CN117033107A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050138644A1 (en) * | 2003-12-19 | 2005-06-23 | Montecalvo Mark V. | Method, apparatus, system, and article of manufacture for interfacing a device |
| CN101788888A (en) * | 2010-02-09 | 2010-07-28 | 中兴通讯股份有限公司 | Method for realizing target end driver and target end driver |
| CN108027755A (en) * | 2015-10-23 | 2018-05-11 | 英特尔Ip公司 | Support using external input/output interface to testing, debugging or the devices, systems, and methods of the transmission of tracked information |
| CN208141371U (en) * | 2018-05-18 | 2018-11-23 | 郑州云海信息技术有限公司 | A kind of multi-functional UART debugging board |
| CN110727420A (en) * | 2019-09-06 | 2020-01-24 | 广东宝莱特医用科技股份有限公司 | Serial port compatible method and system |
| CN113179330A (en) * | 2021-05-25 | 2021-07-27 | 浙江浙大西投脑机智能科技有限公司 | External equipment connection management system compatible with multiple hardware interface specifications and hardware communication protocols |
| CN113918132A (en) * | 2021-12-13 | 2022-01-11 | 珠海市新德汇信息技术有限公司 | Equipment standardization management method, system, working method, device and storage medium |
| CN114546736A (en) * | 2022-01-13 | 2022-05-27 | 宁波小匠物联网科技有限公司 | Automatic serial port testing method |
| CN116795435A (en) * | 2022-03-15 | 2023-09-22 | 华为技术有限公司 | Compatibility management and control method and related equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108959127B (en) | Address translation method, device and system | |
| US20140033262A1 (en) | Parsing Single Source Content for Multi-Channel Publishing | |
| EP2947582A1 (en) | Computing device and method for executing database operation command | |
| CN113067866B (en) | Batch file transmission method and device between heterogeneous systems | |
| CN111625585B (en) | Access method, device, host and storage medium of hardware acceleration database | |
| US10621124B2 (en) | Method, device and computer program product for enabling SR-IOV functions in endpoint device | |
| CN112764946B (en) | Cross-process data transmission method and device, electronic equipment and storage medium | |
| CN115657553A (en) | PCIE topology and PCIE equipment simulation method, device, equipment and medium | |
| CN112286643B (en) | Transaction processing method, device, equipment and medium for Ether house virtual machine | |
| CN109656844A (en) | A kind of AT24xx EEPROM driving method and device | |
| CN113641700A (en) | Data processing method and device based on Spring boot frame | |
| CN115794437A (en) | Calling method and device of microservice, computer equipment and storage medium | |
| CN113923259B (en) | Data processing method and system | |
| CN112286641B (en) | Transaction processing method, device, equipment and medium for Ether house virtual machine | |
| JP2009031960A (en) | Technology for relaying communication between client device and server device | |
| CN112883088B (en) | Data processing method, device, equipment and storage medium | |
| CN117033107A (en) | Debugging method, device, storage medium and equipment supporting different interfaces | |
| CN117331663A (en) | Debugging method, device, storage medium and equipment supporting different interfaces | |
| CN116055576A (en) | Data transmission method, system, electronic equipment and storage medium | |
| CN112231409B (en) | Database synchronization initialization loading method, device, equipment and storage medium | |
| CN112559478B (en) | Log generation method and device, terminal equipment and storage medium | |
| CN114385947B (en) | Webpage publishing method, system, device and medium | |
| CN115277393B (en) | Method, device and medium for transmitting configuration information | |
| KR101231054B1 (en) | Parser Accelerator having hardware engine and method | |
| CN117033748B (en) | Service query information acquisition method, service data query method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20231110 |