CN114817115A - Serial port communication method and related device - Google Patents

Abstract

The embodiment of the application provides a serial port communication method and a related device, wherein the method comprises the following steps: determining a service type corresponding to a first sub-function node, wherein the first sub-function node is one of a plurality of sub-function nodes generated by peripheral equipment high-speed connection standard PCIE equipment, the PCIE equipment is equipment supporting PCIE, and one sub-function node corresponds to one service type; creating a read-write interface corresponding to the service type for the first sub-function node; and controlling the first sub-function node to carry out serial port communication based on the read-write interface. Through the method and the device, the development cost of the PCIE equipment for realizing serial port communication can be reduced.

Description

Serial communication method and related device

technical field

The embodiments of the present application relate to the field of communication technologies, and in particular, to a serial communication method and a related device.

Background technique

Peripheral component interconnect express (PCIE) can be understood as a high-speed serial computer expansion bus standard. PCIE devices that support PCIE need serial drivers to realize serial communication, such as capturing logs, sending and receiving AT commands ( attention, an instruction applied to the connection and communication between terminal devices and computer applications) and other functions.

Exemplarily, when a PCIE device is inserted into electronic device A, electronic device A can identify the inserted device as a PCIE device, and then install a PCIE device driver. Since different functions correspond to different data channels, the PCIE device driver will generate sub-function nodes according to the requirements of the PCIE device, and different sub-function nodes are used to implement different functions.

At present, in order to realize the serial port communication of PCIE devices, it is necessary to develop corresponding serial port drivers for each sub-function node. However, the development cost of realizing serial communication in the above-mentioned manner is high.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a serial port communication method and a related device, and through the present application, the development cost of realizing serial port communication by a PCIE device can be reduced.

In a first aspect, the present application provides a serial communication method, including:

Determine the service type corresponding to the first sub-function node, the first sub-function node is a sub-function node in a plurality of sub-function nodes generated by the peripheral equipment high-speed connection standard PCIE device, the above-mentioned PCIE device is a device supporting PCIE, and one of the above-mentioned sub-function nodes. The function node corresponds to one of the above service types;

Create a read-write interface corresponding to the above-mentioned service type for the above-mentioned first sub-function node;

Control the above-mentioned first sub-function node to perform serial communication based on the above-mentioned read-write interface.

The serial communication method provided by the present application firstly determines the service type corresponding to the first sub-function node, and then creates a corresponding read-write interface according to the service type corresponding to the first sub-function node. Since the read-write interface of the first sub-function node are created according to their corresponding business types, then the created read-write interface can well realize the function of the first sub-function node, and then realize serial communication. It can be understood that other sub-function nodes (for example, the second sub-function node, the third sub-function node, etc.) can use the above method to create a read-write interface, thereby realizing serial communication. Through the present application, it is not necessary to develop each sub-function node separately, but to create corresponding read and write interfaces for each sub-function node of the PCIE device at one time, thereby reducing development costs and maintenance workload of developers.

In a possible implementation manner, different above-mentioned sub-function nodes correspond to different identification information, and the above-mentioned determination of the service type corresponding to the first sub-function node includes:

Obtain the identification information of the above-mentioned first sub-function node;

The service type corresponding to the above-mentioned first sub-function node is determined according to the above-mentioned identification information.

In a possible implementation manner, before the above-mentioned determination of the service type corresponding to the above-mentioned first sub-function node according to the above-mentioned identification information, the above-mentioned method further includes:

Numbering all service types corresponding to the above-mentioned multiple sub-function nodes, and different above-mentioned service types correspond to different numbers;

establishing the correspondence between the identification information corresponding to the above-mentioned multiple sub-function nodes and the above-mentioned number, and one of the above-mentioned identification information corresponds to one of the above-mentioned numbers;

The above-mentioned determination of the service type corresponding to the above-mentioned first sub-function node according to the above-mentioned identification information includes:

The service type corresponding to the first sub-function node is determined according to the serial number corresponding to the identification information.

In a possible implementation manner, the first service type corresponds to the first read/write interface, and the second service type corresponds to the second read/write interface; the first service type and the second service type are at least one of the following Different items: different data formats are processed, and different data sources are processed.

In a possible implementation manner, the above service types include capturing logs, sending and receiving AT commands, and ports used as debugging tools.

In a possible implementation manner, the above identification information includes a hardware identification number ID.

In a second aspect, the present application provides a serial communication device, including:

The determining unit is used to determine the service type corresponding to the first sub-function node, the first sub-function node is a sub-function node in a plurality of sub-function nodes generated by the peripheral equipment high-speed connection standard PCIE device, and the above-mentioned PCIE device is a PCIE-supporting device. equipment, one of the above-mentioned sub-function nodes corresponds to one of the above-mentioned service types;

A creation unit is used to create a read-write interface corresponding to the above-mentioned service type for the above-mentioned first sub-function node;

A control unit, configured to control the first sub-function node to perform serial communication based on the read-write interface.

In a possible implementation manner, different above-mentioned sub-function nodes correspond to different identification information, and the above-mentioned apparatus further includes an obtaining unit, configured to obtain the identification information of the above-mentioned first sub-function node;

The determining unit is specifically configured to determine the service type corresponding to the above-mentioned first sub-function node according to the above-mentioned identification information.

In a possible implementation manner, the above-mentioned apparatus further includes a numbering unit for numbering all the service types corresponding to the above-mentioned multiple sub-function nodes, and different above-mentioned service types correspond to different numbers;

The above-mentioned device further includes a corresponding relationship establishing unit, which is used to establish a corresponding relationship between the identification information corresponding to the above-mentioned multiple sub-function nodes and the above-mentioned number, and one of the above-mentioned identification information corresponds to one of the above-mentioned numbers;

The determining unit is specifically configured to determine the service type corresponding to the first sub-function node according to the serial number corresponding to the identification information.

In a possible implementation, the first service type corresponds to the first read/write interface, and the second service type corresponds to the second read/write interface; the first service type and the second service type are different in at least one of the following: processing The data formats are different, and the data sources processed are different.

In a possible implementation manner, the above-mentioned service types include capturing logs, sending and receiving AT commands, and ports used as debugging tools.

In a possible implementation manner, the above-mentioned identification information includes a hardware identification number ID.

In a third aspect, an embodiment of the present application provides a serial communication device, including: a processor and a memory, wherein a computer program is stored in the memory, and the processor calls the computer program stored in the memory to execute the program as described in the first The method in an aspect or any one of the possible implementations of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program runs on one or more processors, the first aspect is Or the method in any possible implementation manner of the first aspect is performed.

In a fifth aspect, embodiments of the present application provide a computer program product, where the computer program product includes program instructions, and when executed by a processor, the program instructions cause the processor to execute the first aspect or any one of the first aspect Methods in possible implementations.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the following briefly introduces the accompanying drawings that are required in the embodiments or the background technology of the present application.

1 is a schematic flowchart of a serial port communication method provided by an embodiment of the present application;

2 is a schematic diagram of a data flow provided by an embodiment of the present application;

3 is a schematic structural diagram of a serial communication device provided by an embodiment of the present application;

FIG. 4 is a schematic structural diagram of another serial communication device provided by an embodiment of the present application.

Detailed ways

The terms used in the following embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to be used as limitations of the present application. As used in the specification of this application and the appended claims, the singular expressions "a," "an," "above," "the" and "the" are intended to include the plural expressions as well, unless the context clearly dictates otherwise. It will also be understood that, as used in this application, the term "and/or" refers to and includes any and all possible combinations of one or more of the listed items. The terms "first", "second" and the like in the description and claims of the present application and the above drawings are used to distinguish different objects, rather than to describe a specific order.

Universal serial bus (universal serial bus, USB) is an external bus standard, which is an interface technology applied in the computer field, and is used to standardize the connection and communication between computers and external devices. In the embodiments of the present application, the USB interface can be understood as an interface supporting the USB standard, and the USB interface has a hot-plug function and can be connected to various peripheral devices. Exemplarily, the computer can be connected to devices such as a mouse, a keyboard and the like through its own USB interface.

The communication device class (CDC) can be understood as a USB subclass used by various communication devices. It can be understood that through the USB communication device class (CDC), the USB interface can be regarded as a virtual interface use. According to different communication devices, CDC can be divided into different models, such as a USB transmission analog telephone service (plain old telephone service, POTS) model, a USB integrated services digital network (Integrated services digital network, ISDN) model and a USB network model and so on. The USB transmission analog telephone service can be classified into a direct line control model (DLCM), an abstract control model (ACM) and a USB telephone model (UTM).

In this embodiment of the present application, a USB device may be understood as a device supporting the USB standard. At present, USB devices can use the CDC-ACM driver to realize serial communication, which is used to capture logs, send and receive AT commands (attention, a command applied to the connection and communication between terminal devices and computer applications), or provide other debugging tools. port, etc.

With the continuous development of communication technology, in addition to the above-mentioned USB interface standard, a peripheral component interconnect express (PCIE) interface standard also appears. PCIE can be understood as a high-speed serial computer expansion bus standard, which belongs to high-speed serial point-to-point dual-channel high-bandwidth transmission, and supports functions such as hot-plugging and quality of service (QoS). In this embodiment of the present application, a PCIE device may be understood as a device that supports the high-speed connection standard of peripheral devices.

In the Windows operating system, after the PCIE device is recognized by other electronic devices, the PCIE device driver will be installed. For example, when a PCIE device is inserted into a notebook, the notebook can recognize that the inserted device is a PCIE device, and then install the PCIE device driver. A PCIE device can use the serial port to realize different functions, therefore, the PCIE device driver will adaptively generate multiple sub-function nodes, and each sub-function node is used to realize different functions.

In this embodiment of the present application, a sub-function node may be understood as a sub-node generated by a PCIE device, and different sub-function nodes are used to implement different functions. Optionally, the sub-function node can also be understood as a virtual node. In this embodiment of the present application, the service type may be understood as a function implemented by a sub-function node. It can be understood that each sub-function node corresponds to a service type, and different sub-function nodes correspond to different service types.

At present, PCIE devices do not have a unified serial port driver to realize serial communication, and different chip manufacturers have specific data transmission protocols for their own chip platforms. PCIE devices from different chip manufacturers support different data transmission protocols. Therefore, , Manufacturers of PCIE devices need to provide their own serial port drivers. In addition, the different sub-function nodes generated by the PCIE device are used for processing different services. Therefore, in order to make each sub-function node work normally, that is, to realize the serial port communication of the PCIE device, it is necessary to develop a corresponding serial port for each sub-function node. drive.

Exemplarily, device A is a PCIE device, and the functions to be implemented by device A are set to be function A, function B, and function C. Therefore, device A will generate sub-function node 1, sub-function node 2 and sub-function node 3, wherein sub-function node 1 is used to realize function A, sub-function node 2 is used to realize function B, and sub-function node 3 is used to realize Function 3. In order to make the above sub-function node 1, sub-function node 2 and sub-function node 3 work normally, developers need to develop sub-function node 1 separately to realize function A, and then develop sub-function node 2 separately to achieve Implement function B, and develop sub-function node 3 separately to realize function 3. It is understandable that the way to develop a corresponding serial port driver for each sub-function node to realize serial port communication leads to a large amount of development cost and maintenance workload for the developer for the serial port driver.

Based on the above problems, an embodiment of the present application provides a serial port communication method, through which the developer's development cost and maintenance workload for serial port drivers can be reduced. It can be understood that the above method can be executed by a serial communication device, and the serial communication device can be any device that needs to realize serial communication for PCIE devices. Illustratively, please refer to FIG. 1 , which is a schematic flowchart of a serial port communication method provided by an embodiment of the present application. As shown in Figure 1, the method includes:

101. Determine a service type corresponding to a first sub-function node, where the first sub-function node is a sub-function node in a plurality of sub-function nodes generated by a peripheral device high-speed connection standard PCIE device, the PCIE device is a device supporting PCIE, and a The sub-function node corresponds to one of the service types.

In this embodiment of the present application, the serial communication device may belong to a PCIE device, and serial communication is implemented through the control of the serial communication device. In this embodiment of the present application, the above-mentioned service types may also be referred to as service modes, service functions, and the like. Since the functions implemented by each sub-function node are different, the above service types can also be understood as the function types implemented correspondingly by the sub-function nodes. Therefore, in this step, one sub-function node corresponds to one type of service.

It can be understood that, after the PCIE device is installed, multiple sub-function nodes will be generated according to requirements, and the ultimate goal is to allow each sub-function node to implement corresponding functions. In this step, the serial communication device determines the service type corresponding to the first sub-function node. In a possible implementation manner, the serial communication device may determine the service type corresponding to the first sub-function node according to the configuration information of the PCIE device. . It can be understood that, for a certain PCIE device, the function to be implemented, that is, the sub-function node to be established is fixed. Therefore, the service type corresponding to the first sub-function node can be determined through the configuration information of the PCIE device.

In another possible implementation manner, the serial communication apparatus may receive indication information of other devices to determine the service type corresponding to the first sub-function node. In another possible implementation, all functions that need to be implemented by the PCIE device, that is, all service types can be preset in the code in advance. For a PCIE device, according to the corresponding relationship between its sub-function nodes and service types to determine the service type corresponding to the first sub-function node.

In some embodiments, in the method shown in FIG. 1, different sub-function nodes correspond to different identification information, and step 101 includes:

1011. Obtain the identification information of the first sub-function node;

1012. Determine a service type corresponding to the first sub-function node according to the identification information.

In this embodiment, different sub-function nodes are marked with identification information, and different sub-function nodes correspond to different identification information. The above identification information may be understood as any information used to identify the sub-function node. Exemplarily, the identification information may be the location information of the sub-function node in the storage device, or the generated time information, or the generated order, or the name of the sub-function node, or It is an artificial number, etc.

In some embodiments, the identification information includes a hardware identity document (ID). It can be understood that when the PCIE device generates the above-mentioned multiple sub-function nodes, the corresponding hardware ID will be determined for each sub-function node, and each hardware ID can be understood as a character string. A correspondence.

In this embodiment, the corresponding relationship between the identification information and the service type may be determined in the code in advance, for example, a relationship mapping table may be used to record the corresponding relationship between the two.

For the convenience of development, the service type can be numbered, and after the identification information of the child node is determined, the corresponding service type can be determined by the number corresponding to the identification information. Therefore, in some embodiments, before the above step 1012, the method further includes:

1013. Number all service types corresponding to the multiple sub-function nodes, and different service types correspond to different numbers.

In this step, the serial communication device numbers each service type. Exemplarily, the numbering may be performed according to the priority of the service type, the numbering may be performed according to the service quality of the service type, or the numbering may be random to ensure that different service types correspond to each other. A different number will do.

1014. Establish a correspondence between the identification information corresponding to the plurality of sub-function nodes and the serial number, and each piece of the identification information corresponds to one of the serial numbers.

The above step 1012 includes:

1015. Determine the service type corresponding to the first sub-function node according to the serial number corresponding to the identification information.

After the business type is numbered, the identification information and the number are corresponded. It can be understood that there is a correspondence between the sub-function node and the identification information. By matching the identification information with the number of the service type, it can be understood that the identification information corresponds to the service type. Finally, through the identification information of the sub-function node. The corresponding service type number can be determined, and then the service type corresponding to the sub-function node can be determined through the service type number.

102: Create a read-write interface corresponding to the service type for the first sub-function node.

In this embodiment of the present application, the read-write interface may be a read interface, a write interface, or a read interface and a write interface, which is specifically determined according to the service type.

It can be understood that different sub-function nodes correspond to different service types, and can also be understood as being used to implement different functions. Therefore, the read-write interfaces corresponding to different sub-function nodes are different. In this step, the serial communication device creates a read-write interface for the first sub-function node, and the read-write interface is created according to the service type of the first sub-function node. Exemplarily, the first sub-function node is sub-function node 1, and the corresponding service type is service type A. When creating a read-write interface for sub-function node 1, a read-write interface for realizing service type A will be created. Also exemplarily, the first sub-function node is sub-function node 2, and the corresponding business type is business type B, then when creating a read-write interface for sub-function node 2, a read-write interface for realizing business type B will be created. .

In this embodiment of the present application, different service types correspond to different read and write interfaces. That is, in some embodiments, the first service type corresponds to the first read/write interface, and the second service type corresponds to the second read/write interface; the first service type and the second service type are different in at least one of the following: The data formats processed are different, and the data sources processed are different.

It can be understood that different sub-function nodes are used to implement different functions, and in different functions, different data are processed. In this embodiment of the present application, the difference in service types includes at least different formats of data to be processed, or different sources of data to be processed. Exemplarily, if the data transmission protocols supported in different functions are different, the processed data formats are different; if the data in different functions comes from different data sources, the processed data sources are different.

In some embodiments, service types include scraping logs, sending and receiving AT commands, and ports used as debugging tools.

In the Windows operating system, logs can be understood as files used to record operation-related content, such as application logs, security logs, and system logs. The AT command can be understood as the command applied to the connection and communication between the serial communication device and the application. It can be understood that the sub-function nodes used to capture logs, the sub-function nodes used to send and receive AT commands, and the sub-function nodes used as ports for debugging tools each process different data types, and their corresponding read The write interface is also different. Through the method provided in the present application, a corresponding read and write interface can be created for each sub-function node, which is used to respectively realize the port for capturing logs, sending and receiving AT commands, and serving as a debugging tool.

103: Control the first sub-function node to perform serial communication based on the read-write interface.

It can be understood that after the serial communication device creates a corresponding read-write interface for the first sub-function node, the first sub-function node can realize serial communication based on its corresponding read-write interface under the control of the serial communication device. .

To sum up, the serial communication method provided by this application firstly determines the service type corresponding to the first sub-function node, and then creates the corresponding read-write interface according to the service type corresponding to the first sub-function node. The read and write interfaces are created according to their corresponding business types, so the created read and write interfaces can well realize the function of the first sub-function node, and then realize serial communication. It can be understood that other sub-function nodes (for example, the second sub-function node, the third sub-function node, etc.) can use the above method to create a read-write interface, thereby realizing serial communication. Through the present application, it is not necessary to develop each sub-function node separately, but to create corresponding read and write interfaces for each sub-function node of the PCIE device at one time, thereby reducing development costs and maintenance workload of developers.

In order to understand the solution more clearly, the method provided by the present application is explained next with reference to FIG. 2 .

It can be understood that the method provided in this application is used to realize serial communication of PCIE devices, that is, each sub-function node can realize its own function. Therefore, the above serial communication device can be understood as a serial port driver. In the prior art, a serial port driver must be provided separately for each sub-function node, but with the present application, the serial port communication of all the sub-function nodes can be realized through one serial port driver.

Since different sub-function nodes are generated by the PCIE device driver, the names and hardware IDs will be different. First, set different hardware IDs in the installation file to provide serial port drivers for multiple sub-function nodes, and then use the serial port driver business logic. , it is set to generate independent read and write interfaces for different sub-function nodes according to different hardware IDs, as well as special data configuration contexts. When the serial port driver is installed on the node according to the hardware ID, the internal driver logic will also call different data transmission interfaces according to the sub-function nodes, that is, read and write interfaces, which can ensure that the same driver is suitable for different platforms, and the same platform is different data transmission channel.

Illustratively, please refer to FIG. 2 , which is a schematic diagram of a data flow provided by an embodiment of the present application. As shown in Figure 2, it includes the following steps:

201. Serial driver installation.

In this step, the serial port driver is a serial port driver, and the serial port driver is installed on the sub-function node according to the hardware ID. It can be understood that the serial port driver is installed on each sub-function node according to the hardware ID. For example, the first sub-function above node, and other sub-function nodes.

It can be understood that the hardware IDs of all transmission service interfaces are configured in the device information file (INF) of the serial port driver, so that the serial port driver can be installed on different platforms or different service channels of the same platform. In this embodiment, after the serial port driver is installed, the following steps 202 to 205 are used to make each sub-function node operate normally.

202. The serial port driver is loaded.

In this step, the serial port driver has been installed on the sub-function node, and for each sub-function node, the hardware properties of the sub-function node are obtained. Exemplarily, when the serial port driver is loaded, the interface function provided by the WDF framework (windows driver foundation, a driver model) can be used to obtain the hardware attribute of the PCIE device, and the hardware ID of the sub-function node can be obtained.

203. Serial port driver service type configuration.

In this step, the service type is set according to the hardware attribute. The service type is defined in the context description structure of the serial port driver. After the serial port driver is loaded, the correspondingly defined service type is assigned to the service type variable according to the hardware ID. At the same time, the variables required by all platform business channels are defined in the context description structure. For different business channels, when the variables have nothing to do with themselves, it will not affect the business logic of the serial port driver. That is to say, each sub-function node determines the corresponding service type according to the corresponding hardware ID, and the service type unrelated to itself will not be affected.

Optionally, all service types may be numbered, so that different service types have different numbers, and further, different numbers may correspond to different data channels.

204. The serial port driver creates a read and write queue.

In this step, when creating a read-write queue, create a read-write interface according to the service type. The serial port driver loaded into each sub-function node creates its own read and/or write interface for data reading and writing according to the service type. Therefore, the serial port driver can be used to load the different service types obtained, and then create different read and write interfaces.

Finally, when a serial port driver is loaded into different sub-function nodes, different read and write interfaces can be called to realize serial communication. Through the above method, the same serial port driver can be used on different platforms and different service channels. Can carry out data transmission of different data packets.

205. Other variables or data definitions.

It can be understood that some sub-function nodes may require special configuration. In this step, threads or special variables are separately created for some specific interfaces to better adapt to the functions required by the sub-function nodes.

It can be understood that by constructing the basic model of the above serial port driver, it is easy to expand and reuse, and can be adapted to other platforms. It is not necessary to re-develop the serial port driver, and only needs to do a simple adaptation.

The methods provided by the embodiments of the present application are described in detail above, and the apparatuses provided by the embodiments of the present application are introduced below.

Please refer to FIG. 3 , which is a schematic structural diagram of a serial communication device provided by an embodiment of the present application. The serial communication device 30 is used to execute the above serial communication method. It should be understood that any device capable of implementing the serial communication method provided by the present application belongs to the protection scope of the present application. As shown in FIG. 3 , the serial communication device 30 includes a determination unit 301 , a creation unit 302 and a control unit 303 . Optionally, the serial communication device 30 may further include an obtaining unit 304 , a numbering unit 305 and a corresponding relationship establishing unit 306 . Among them, the description of each unit is as follows:

The determining unit 301 is configured to determine a service type corresponding to a first sub-function node, where the first sub-function node is a sub-function node in a plurality of sub-function nodes generated by a peripheral device high-speed connection standard PCIE device, and the above-mentioned PCIE device supports PCIE equipment, one of the above-mentioned sub-function nodes corresponds to one of the above-mentioned service types;

A creation unit 302 is configured to create a read-write interface corresponding to the above-mentioned service type for the above-mentioned first sub-function node;

The control unit 303 is configured to control the above-mentioned first sub-function node to perform serial communication based on the above-mentioned read-write interface.

In a possible implementation manner, different above-mentioned sub-function nodes correspond to different identification information, and the above-mentioned apparatus further includes an obtaining unit 304, configured to obtain the identification information of the above-mentioned first sub-function node;

The determining unit 301 is specifically configured to determine the service type corresponding to the above-mentioned first sub-function node according to the above-mentioned identification information.

In a possible implementation manner, the above-mentioned apparatus further includes a numbering unit 305, which is used for numbering all service types corresponding to the above-mentioned multiple sub-function nodes, and different above-mentioned service types correspond to different numbers;

The above-mentioned device also includes a corresponding relationship establishing unit 306, which is used to establish a corresponding relationship between the identification information corresponding to the above-mentioned multiple sub-function nodes and the above-mentioned number, and one of the above-mentioned identification information corresponds to one of the above-mentioned numbers;

The determining unit 301 is specifically configured to determine the service type corresponding to the first sub-function node according to the serial number corresponding to the identification information.

In a possible implementation, the first service type corresponds to the first read/write interface, and the second service type corresponds to the second read/write interface; the first service type and the second service type are different in at least one of the following: processing The data formats are different, and the data sources processed are different.

In a possible implementation manner, the above-mentioned service types include capturing logs, sending and receiving AT commands, and ports used as debugging tools.

In a possible implementation manner, the above-mentioned identification information includes a hardware identification number ID.

Please refer to FIG. 4. FIG. 4 is a schematic structural diagram of another serial communication device provided by an embodiment of the present application. As shown in FIG. 4 , the above-mentioned serial communication device 40 includes a memory 401 and a processor 402 . Further optionally, a communication interface 403 and a bus 404 may also be included, wherein the memory 401 , the processor 402 and the communication interface 403 are communicated with each other through the bus 404 .

Among them, the memory 401 is used to provide a storage space, and data such as an operating system and a computer program can be stored in the storage space. The memory 401 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable readonly memory (EPROM), or portable Read-only memory (compact disc read-only memory, CD-ROM).

The processor 402 is a module that performs arithmetic operations and logical operations, and may be a processing module such as a central processing unit (CPU), a graphics processing unit (GPU), or a microprocessor (MPU). one or more combinations.

A computer program is stored in the memory 401, and the processor 402 calls the computer program stored in the memory 401 to execute the above-mentioned serial communication method.

The present application also provides a computer-readable storage medium, where computer codes are stored in the computer-readable storage medium, and when the computer codes are executed on the computer, the computer is made to execute the methods of the above embodiments.

The present application also provides a computer program product, the computer program product includes computer code or a computer program, when the computer code or computer program is run on a computer, the method in the above embodiment is executed.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited to this. should be covered within the scope of protection of this application. Therefore, the protection scope of the present application shall be subject to the protection scope of the above claims.

Claims (10)

1. A serial port communication method is characterized by comprising the following steps:

determining a service type corresponding to a first sub-function node, wherein the first sub-function node is one of a plurality of sub-function nodes generated by peripheral equipment high-speed connection standard PCIE equipment, the PCIE equipment is equipment supporting PCIE, and one sub-function node corresponds to one service type;

creating a read-write interface corresponding to the service type for the first sub-function node;

and controlling the first sub-function node to carry out serial port communication based on the read-write interface.

2. The method of claim 1, wherein different sub-function nodes correspond to different identification information, and wherein the determining the service type corresponding to the first sub-function node comprises:

acquiring identification information of the first sub-function node;

and determining the service type corresponding to the first sub-function node according to the identification information.

3. The method according to claim 2, wherein before determining the service type corresponding to the first sub-function node according to the identification information, the method further comprises:

numbering all service types corresponding to the sub-function nodes, wherein different service types correspond to different numbers;

establishing a corresponding relation between identification information corresponding to the plurality of sub-function nodes and the number, wherein one identification information corresponds to one number;

the determining the service type corresponding to the first sub-function node according to the identification information includes:

and determining the service type corresponding to the first sub-function node according to the number corresponding to the identification information.

4. The method according to any of claims 1-3, wherein the first traffic type corresponds to a first read-write interface and the second traffic type corresponds to a second read-write interface; the first service type and the second service type are different by at least one of the following items: the processed data has different formats and different processed data sources.

5. The method of claim 4, wherein the traffic types include logging, transceiving AT commands, and port used as a debugging tool.

6. The method according to any of claims 2-5, wherein the identification information comprises a hardware identification number, ID.

7. A serial communication device, the device comprising:

a determining unit, configured to determine a service type corresponding to a first sub-function node, where the first sub-function node is one of multiple sub-function nodes generated by a peripheral device high-speed connection standard PCIE device, the PCIE device is a device supporting PCIE, and one sub-function node corresponds to one service type;

a creating unit, configured to create, for the first sub-function node, a read-write interface corresponding to the service type;

and the control unit is used for controlling the first sub-function node to carry out serial port communication based on the read-write interface.

8. The apparatus according to claim 7, wherein different sub-function nodes correspond to different identification information, the apparatus further comprising an obtaining unit configured to obtain the identification information of the first sub-function node;

the determining unit is specifically configured to determine, according to the identification information, a service type corresponding to the first sub-function node.

9. An electronic device comprising a processor and a memory, the memory for storing a computer program comprising program instructions, the processor being configured to invoke the program instructions to perform the method of any of claims 1-6.

10. A computer-readable storage medium, in which a computer program is stored which, when run on one or more processors, causes the method of any one of claims 1-6 to be performed.

Images