CN115134426A - Data conversion method from SRIO protocol to aurora protocol - Google Patents

Abstract

The invention discloses a data conversion method from an SRIO protocol to an aurora protocol, which mainly comprises the steps of extracting packet header information, detecting the packet header, filtering the packet header information, finding out an initial packet and an end packet, splicing data and converting data. The invention filters the packet header information, splices the small packets of the SRIO protocol, and restores the small packets into original big frame data, thereby ensuring the integrity of the data when the SRIO protocol is transmitted.

Description

Data conversion method from SRIO protocol to aurora protocol

Technical Field

The invention belongs to the field of data transmission equipment, and particularly relates to a data conversion method from an SRIO protocol to an aurora protocol.

Background

The SRIO, i.e., the serial RapidIO bus, is an interconnect architecture with high performance, low pin count and based on packet switching, has a routing function, and is an open interconnect technology standard designed to meet the requirements of a high-performance embedded system. The SRIO is mainly applied to system internal interconnection, supports communication between a chip and between boards, uses a back board for interconnection in a physical layer, and is widely applied to various naval vessel data exchange equipment. The aurora protocol is a small link layer protocol with high openness, strong reliability, upgradability and no routing function, and can solve the communication problem of point-to-point high-speed serial signals.

The existing technology for converting the RIO protocol to the aurora protocol adopts a transparent transmission mode, namely, when receiving a packet of SRIO data, the SRIO data is processed as a frame of data, because the maximum number of the SRIO data is 256 bytes, if the frame length of the data at the transmitting end exceeds 256 bytes, the original frame of data is divided into multi-frame data at the receiving end, the data format is changed, and the subsequent data processing is influenced.

Disclosure of Invention

In order to solve the technical defects in the prior art, the invention provides a data conversion method from an SRIO protocol to an aurora protocol.

The technical scheme for realizing the purpose of the invention is as follows: a data conversion method from SRIO protocol to aurora protocol includes the following steps:

step 1: the SRIO sending end divides the big frame data into packets for transmission, and the receiving end extracts packet header information when receiving each packet data;

step 2: detecting the packet head, and determining whether the packet is correctly received and the transmission format of the packet;

and step 3: filtering the packet header information;

and 4, step 4: distinguishing a start packet and an end packet of the data packet, judging whether the packet is complete data of one frame according to a distinguishing result, if so, performing a step 6, and otherwise, performing a step 5;

and 5: splicing the initial packet, a plurality of packets between the initial packet and the end packet together according to the sequence to be used as a frame of complete data, and restoring the big frame data;

step 6: SOF, EOF, DATA and VALID signals are constructed from the DATA packets.

Preferably, when the SRIO sending end performs transmission, the transmission format is determined by whether the transmitted packet is the last packet of data of the big frame data, and specifically: and if the packet is the last packet of data of the big frame data, transmitting the packet in a write operation format with response, otherwise, transmitting the packet in the write operation format.

Preferably, the first 64 bits of each packet of data is storage packet header information, and the packet header information includes address information, node information, and routing information packet length information.

Preferably, the specific method for detecting the packet header and determining whether the packet is correctly received is as follows: and judging according to the fault bit information, if the fault bit information is 1, indicating that the packet is in an error state, sending a fault state information alarm outwards, and if the fault bit information is 0, indicating that the packet is correctly received, and not responding.

Preferably, the specific method for detecting the packet header and determining the transmission format of the packet is as follows: and judging whether the packet is in a write operation format or a write operation format transmission format with response according to the transmission format bit information.

Preferably, a start packet and an end packet of the data packet are distinguished, with the received first packet data and a next packet of the write operation transport format packet as a start packet, and with a packet of the write operation transport format with a response as an end packet.

Preferably, the specific method for constructing the SOF, EOF, DATA and VALID signals is:

pulling up the SOF signal when the first DATA of the start packet is received, pulling down the EOF signal at the rest moments, pulling up the EOF signal when the last DATA of the end packet is received, pulling down the EOF signal at the rest moments, pulling up the VALID signal when the DATA is received, pulling down the VALID signal at the rest moments, and enabling the DATA to be consistent with the received DATA information.

Compared with the prior art, the invention has the remarkable advantages that:

(1) the invention filters the packet header information, splices the small packets of the SRIO protocol to restore the original large frame data, and ensures the integrity of the data when the data is transmitted by the SRIO protocol;

(2) the invention processes the received data, constructs the interface data of the standard AXI-Stream bus protocol, and completes the conversion of the high-speed data from the SRIO protocol with the routing function to the aurora protocol without the routing function.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Drawings

The drawings are only for purposes of illustrating particular embodiments and are not to be construed as limiting the invention, wherein like reference numerals are used to designate like parts throughout.

Fig. 1 is a schematic structural diagram of a data conversion method from SRIO protocol to aurora protocol according to the present invention.

Detailed Description

It is easily understood that various embodiments of the present invention can be conceived by those skilled in the art according to the technical solution of the present invention without changing the essential spirit of the present invention. Therefore, the following detailed description and the accompanying drawings are merely illustrative of the technical aspects of the present invention, and should not be construed as limiting or restricting the technical aspects of the present invention in its entirety or as limiting the technical aspects of the present invention. Rather, these embodiments are provided so that this disclosure will be thorough and complete. The preferred embodiments of the present invention will now be described in detail with reference to the accompanying drawings, which form a part hereof, and which together with the embodiments of the invention serve to explain the innovative concepts of the invention.

The concept of the present invention is that, as shown in fig. 1, a data conversion method from SRIO protocol to aurora protocol mainly includes extracting header information, detecting header, filtering header information, finding out start packet and end packet, splicing data and converting data, and specifically includes the following steps:

the method comprises the following steps: extracting packet header information;

the method includes the steps that an SRIO sending end splits big frame data into packets and then transmits the packets, in the transmission process, the transmission format of the SRIO sending end is determined by whether the packets are the last packet data of the big frame data, if the packets are the last packet data of the big frame data, the SRIO sending end transmits the packets in a WRITE operation format with response (namely an N _ WRITE _ R transmission format, the transaction type Ttype in a packet head is set to be '0101'), and otherwise, the SRIO sending end transmits the packets in the WRITE operation format (namely an N _ WRITE transmission format, the transaction type Ttype in the packet head is set to be '0100').

When receiving each packet data, the receiving end extracts the packet header information. According to the SRIO communication protocol, the first 64 bits of each packet of data are storage packet header information, the packet header information comprises address information, node information, routing information packet length information and the like, and the fault bit information of the 36 th bit and the transmission format bit information of 4 bits in total of the 52 th bit to the 49 th bit are extracted.

Step two: detecting a packet head;

firstly, judging according to fault bit information, if the fault bit information is 1, indicating that the packet is in an error state, then sending a fault state information alarm outwards, if the fault bit information is 0, indicating that the packet is correctly received, and then not responding;

and then, judging according to the transmission format bit information, if the transaction type Ttype in the packet header is '0100', the packet is in an N _ WRITE transmission format, and if the transaction type Ttype in the packet header is '0101', the packet is in an N _ WRITE _ R transmission format.

Step three: header information filtering

Removing the first 64bit packet header information of each packet data, and only retaining the data information;

step four: distinguishing a start packet and an end packet;

dividing the data packet, taking the received first packet data and the next packet using the N _ WRITE _ R transmission format packet as a starting packet, and taking the packet using the N _ WRITE _ R transmission format as an ending packet;

if the initial packet and the end packet are the same packet, the packet is a frame of complete data, splicing processing is not needed, step 6 is carried out, and if the initial packet and the end packet are not the same packet, step 5 is carried out;

step five: data splicing;

splicing the initial packet, a plurality of packets between the initial packet and the end packet together according to the sequence to be used as a frame of complete data, and restoring the big frame data;

step six: data conversion;

constructing SOF (Start), EOF (end), DATA (DATA) and VALID (DATA VALID) signals;

pulling up the SOF signal when the first DATA of the start packet is received, pulling down the EOF signal at the rest moments, pulling up the EOF signal when the last DATA of the end packet is received, pulling down the EOF signal at the rest moments, pulling up the VALID signal when the DATA is received, pulling down the VALID signal at the rest moments, and enabling the DATA to be consistent with the received DATA information. These four signals constitute a standard AXI-Stream bus protocol interface, which can be used for data transmission of the subsequent aurora protocol.

The above description is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto,

any changes or substitutions that may be easily made by those skilled in the art within the technical scope of the present disclosure are also intended to be covered by the scope of the present invention.

It should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes described in a single embodiment or with reference to a single figure, for the purpose of streamlining the disclosure and aiding in the understanding of various aspects of the invention by those skilled in the art. However, the present invention should not be construed such that the features included in the exemplary embodiments are all the essential technical features of the patent claims.

It should be understood that the modules, units, components, etc. included in the device of one embodiment of the present invention may be adaptively changed to be provided in a device different from the embodiment. The different modules, units or components comprised by the apparatus of an embodiment may be combined into one module, unit or component or they may be divided into a plurality of sub-modules, sub-units or sub-components.

Claims (7)

1. A data conversion method from SRIO protocol to aurora protocol is characterized by comprising the following specific steps:

step 1: the SRIO sending end divides the big frame data into packets for transmission, and the receiving end extracts the packet header information when receiving each packet data;

and 2, step: detecting the packet head, and determining whether the packet is correctly received and the transmission format of the packet;

and 3, step 3: filtering the packet header information;

and 4, step 4: distinguishing a start packet and an end packet of the data packet, judging whether the packet is complete data of one frame according to a distinguishing result, if so, performing a step 6, and otherwise, performing a step 5;

and 5: splicing the initial packet, a plurality of packets between the initial packet and the end packet together according to the sequence to be used as a frame of complete data, and restoring the big frame data;

and 6: SOF, EOF, DATA, and VALID signals are constructed from the DATA packets.

2. The method for data conversion from SRIO protocol to aurora protocol according to claim 1, wherein when the SRIO sending end performs transmission, the transmission format is determined by whether the packet to be transmitted is the last packet of data of the big frame data, specifically: and if the packet is the last packet of data of the big frame data, transmitting the packet in a write operation format with response, otherwise, transmitting the packet in the write operation format.

3. The method of claim 1, wherein the first 64 bits of each packet of data is a header information, and the header information includes address information, node information, and routing information packet length information.

4. The method for converting data from SRIO protocol to aurora protocol according to claim 1, wherein the specific method for detecting the packet header and determining whether the packet is correctly received is as follows: and judging according to the fault bit information, if the fault bit information is 1, indicating that the packet is in an error state, sending a fault state information alarm outwards, and if the fault bit information is 0, indicating that the packet is correctly received, and not responding.

5. The method for data conversion from SRIO protocol to aurora protocol according to claim 1, wherein the specific method for detecting the packet header and determining the transmission format of the packet is as follows: and judging whether the packet is in a write operation format or a write operation format transmission format with response according to the transmission format bit information.

6. The method of claim 1, wherein the first packet data received and the next packet using the write operation transport format packet are distinguished as the start packet, and the next packet using the write operation transport format packet with response are distinguished as the end packet.

7. The method for DATA conversion from SRIO protocol to aurora protocol as claimed in claim 1, wherein the specific method for constructing SOF, EOF, DATA and VALID signals is:

pulling up the SOF signal when the first DATA of the start packet is received, pulling down the EOF signal at the rest moments, pulling up the EOF signal when the last DATA of the end packet is received, pulling down the EOF signal at the rest moments, pulling up the VALID signal when the DATA is received, pulling down the VALID signal at the rest moments, and enabling the DATA to be consistent with the received DATA information.

Images