CN116566817A - FC-Ethernet bridging network card adaptation method for partition real-time operating system - Google Patents
FC-Ethernet bridging network card adaptation method for partition real-time operating system Download PDFInfo
- Publication number
- CN116566817A CN116566817A CN202310631310.2A CN202310631310A CN116566817A CN 116566817 A CN116566817 A CN 116566817A CN 202310631310 A CN202310631310 A CN 202310631310A CN 116566817 A CN116566817 A CN 116566817A
- Authority
- CN
- China
- Prior art keywords
- ethernet
- network card
- operating system
- core layer
- pci
- 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 20
- 230000006978 adaptation Effects 0.000 title claims abstract description 17
- 238000005192 partition Methods 0.000 title claims abstract description 14
- 238000004891 communication Methods 0.000 claims abstract description 33
- 239000012792 core layer Substances 0.000 claims abstract description 28
- 230000006870 function Effects 0.000 claims description 29
- 230000003068 static effect Effects 0.000 claims description 9
- 238000013507 mapping Methods 0.000 claims description 8
- 230000004048 modification Effects 0.000 claims description 7
- 238000012986 modification Methods 0.000 claims description 7
- 238000005538 encapsulation Methods 0.000 claims description 5
- 239000013307 optical fiber Substances 0.000 abstract description 7
- 239000000835 fiber Substances 0.000 abstract description 6
- 238000011161 development Methods 0.000 abstract description 4
- 238000002054 transplantation Methods 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 5
- 239000010410 layer Substances 0.000 description 4
- 238000012360 testing method Methods 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 239000000306 component Substances 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000002955 isolation Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000000638 solvent extraction Methods 0.000 description 2
- 101000699762 Homo sapiens RNA 3'-terminal phosphate cyclase Proteins 0.000 description 1
- 102100029143 RNA 3'-terminal phosphate cyclase Human genes 0.000 description 1
- IWUCXVSUMQZMFG-AFCXAGJDSA-N Ribavirin Chemical compound N1=C(C(=O)N)N=CN1[C@H]1[C@H](O)[C@H](O)[C@@H](CO)O1 IWUCXVSUMQZMFG-AFCXAGJDSA-N 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000036541 health Effects 0.000 description 1
- 238000002536 laser-induced breakdown spectroscopy Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 239000012925 reference material Substances 0.000 description 1
- 238000007430 reference method Methods 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- 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/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Abstract
The invention relates to a method for adapting an FC-Ethernet bridging network card of a partition real-time operating system. The invention uses PCI-E bus to register FC device as a virtual Ethernet network card in core layer user code segment by modifying partition real-time system core layer relative system file, configuring relative system environment, adapting and compiling relative drive library and link library, to solve the problem of incompatibility between the current FC device and operation system, to make the upper Ethernet application directly based on Ethernet interface function to directly transmit the data of fiber channel. The adaptation method of the FC-Ethernet bridging network card can solve the compatibility problem of the partitioned real-time operation system to the communication equipment, provide direct support for the existing Ethernet application transplantation and system platform function expansion, and provide an implementation thought which meets the requirements of an open architecture better for the development and the communication architecture design of the avionics system based on the partitioned real-time system. Experimental results show that the invention can effectively realize compatible identification of the operating system and the application to the FC communication equipment, and the upper application can directly communicate on the optical fiber network based on the Ethernet interface function.
Description
Technical Field
The invention relates to development of a partitioned real-time embedded operating system and network communication of an FC protocol and an Ethernet protocol, in particular to a realization method of FC-Ethernet protocol bridging communication under the partitioned real-time operating system.
Background
In 1997, the united states avionics committee defined a set of software security specifications for integrated modular avionics systems for civil aircraft, named ARINC653, formulated a standard interface between the operating system layer and the application software layer, introduced a partitioning concept to achieve space-time isolation between applications, and currently the ARINC653 standard has become an important specification for the mainstream open-type avionics system to follow. The VxWorks653 is a core component of an ARINC653 platform which is a safety key of America Feng River (Wind River) company, is an advanced isolation real-time operating system in the embedded industry, ensures the safety key of an application program through space-time resource allocation of partitions, has good instantaneity and stability by adopting a strict two-stage scheduling mechanism, and completely meets the requirements of the ARINC653 and the RTCA/DO-178. At present, vxWorks653 has been successfully applied to more than 100 companies worldwide, and more than 180 subsystems of more than 40 aircraft.
The Ethernet protocol (Ethernet) is the most widely used network communication protocol at present, and is proposed in 1973 at the earliest, and in 1983, the Ethernet II protocol has been jointly released by three companies Xerox, intel, DEC, which have become the implementation technology of the mainstream network based on the characteristics of low cost, easy networking and strong expandability, and many mature application programs and communication middleware are developed by adopting the technology at present.
The Fibre Channel (FC) protocol is a high-speed serial transmission protocol proposed by the X3T11 group of the american standardization committee in 1988, solving the technical bottleneck encountered by parallel bus SCSI, and is an effective solution for efficient transmission of large-scale dense storage systems. The FC protocol is more complex than the Ethernet protocol, but has the advantages of channel and network dual, high bandwidth, high reliability, high stability, high electromagnetic interference resistance and the like, can provide very stable and reliable communication connection, is suitable for constructing a large-scale data transmission and communication network, and supports bandwidth connection rates of 1x, 2x, 4x and 8 x. Therefore, the FC protocol is also widely used in the airborne avionics system to construct a high-speed airborne communication network, and corresponding Fibre Channel-avionics environment (FC-AE) series standards are also created, and the common standard protocol is FC-AE-ASM.
Realizing FC-Ethernet bridging communication is beneficial to expanding the application of the existing Ethernet on the optical fiber network, but because the Ethernet protocol and the FC protocol have great difference, the realization of the communication scheme needs to relate to a plurality of aspects such as hardware driving, an operating system and the like, and the problem that partial system FC equipment cannot be directly identified exists, especially for the bridging communication equipment of the FC-Ethernet, the added conversion module needs to be compatible with an upper operating system; for the VxWorks653 system, software and hardware interfaces related to the VxWorks653 system are required to meet ARINC653 standard, the system API call authority limit and the health management during the system operation are strict, the bridge communication scheme is designed to avoid the influence on the upper Ethernet application, and the corresponding standard specification is required to be met; in addition, compared with the main stream embedded operating system such as VxWorks, linux, the current VxWorks653 has fewer domestic researches and reference materials and lack thereof, so that a research blank is left for the FC-Ethernet bridging network card adaptation of the VxWorks653 system.
However, for the development of an onboard computer in an avionics system, FC-Ethernet bridging communication on a VxWorks653 system platform is realized, the advantages of the FC-Ethernet bridging communication, the VxWorks653 system and the FC-Ethernet bridging communication are combined, the openness, the instantaneity and the reliability of the avionics system are improved, the VxWorks653 operation system is adopted to ensure reliable real-time response of onboard application, the onboard optical fiber channel is utilized for high-efficiency real-time transmission of data, and the mature application developed based on an Ethernet protocol is adopted to reduce the research and development cost of the system and improve the reliability. The combination of the three components enables the avionics system, so that the key real-time system can greatly enrich the system functions by means of the existing mature application, and provides a wider development prospect for the avionics system under the trend of an open architecture.
Disclosure of Invention
The invention provides an adaptation method of a partitioned real-time operating system FC-Ethernet bridging network card, which aims to solve the problems of FC equipment identification, optical fiber communication of Ethernet application and the like. In the invention, a VxWorks653 2.5 system is adopted as a partition real-time operating system, a P2020 RDB-PCA board is adopted as an integral hardware deployment platform, and an FCE-1221A sub-card (called as an FC sub-card for short) is adopted as an FC-Ethernet bridging network card to construct a specific example.
Based on the method for identifying the FC daughter card as the virtual Ethernet network card through the PCI-E, the invention realizes the FC-Ethernet bridging communication of the VxWorks653 partition real-time operating system, and the specific steps are as follows, and the flow chart is shown in figure 1:
step S1: and (3) completing PCI-E environment configuration through system file modification, calling a core layer system function, and completing system registration for the FC equipment.
Step S2: and modifying the FC drive library to complete mapping association of the FC protocol and the Ethernet protocol address, and then performing adaptation addition aiming at an operating system.
Step S3: and (3) finishing the registration of the system equipment of the FC sub-card, identifying the FC sub-card as a virtual Ethernet network card, initializing a bridging network card at a system core layer, and finishing the parameter configuration of the bridging network card.
The setting of the FC-Ethernet bridging network card in the VxWorks653 core layer system is completed, the FC sub-card is identified as a virtual Ethernet network card, and the application in the upper layer partition can directly call the FC equipment to carry out data receiving and transmitting operation on the optical fiber channel through the Ethernet function interface.
The beneficial effects of the invention are as follows: the method realizes compatible identification of the partitioned real-time embedded operating system to the FC equipment, so that the FC equipment can be directly used for upper Ethernet protocol application, and basic communication support is provided for function expansion of a safety key system. The thought provided by the invention can provide a universal thought and reference method for the aspects of communication architecture construction, communication protocol compatibility, application component transplanting and the like based on the partition real-time operating system.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, and it will be obvious to a person skilled in the art that other drawings can be obtained from these drawings without inventive effort.
FIG. 1 is a flow chart of a method for partitioning FC-Ethernet bridging communication of a real-time operating system
FIG. 2 is a schematic diagram of a system platform architecture according to the present invention
FIG. 3 is a diagram showing the memory pool entry setting for PCI-E devices in a system configuration file according to an embodiment of the present invention
FIG. 4 is a diagram of the result of identifying FC daughter cards based on PCI-E in an embodiment of the invention
FIG. 5 is a schematic diagram of an FC-Ethernet data frame encapsulation and decapsulation flow according to an embodiment of the invention
FIG. 6 is a schematic diagram of an FC drive module modified according to an embodiment of the present invention
FIG. 7 is a diagram of an FC driven source file executable compilation process according to an embodiment of the present invention
FIG. 8 is a chart of test results of fibre channel Ethernet command communications in accordance with an embodiment of the present invention
Detailed Description
In order to make the technical solution of the present invention and the description of the achievement of the object clearer and more obvious, the following specific description of the implementation steps of the present invention will be given.
The embodiment of the invention adopts a software and hardware environment that a P2020 RDB-PCA hardware board card of Feikel company is adopted to carry a VxWorks653 2.5 operating system; the FCE-1221A node card (FC sub card) of the optical communication company is connected with the hardware board card through PCI-E to provide optical fiber transmission support, and the system platform architecture is shown in figure 2. This example is an explanation of specific embodiments of the present invention to fully demonstrate the implementation concept of the present invention, and the implementation examples thereof are not limited to this example.
The invention provides an adaptation method of an FC-Ethernet bridging network card around a VxWorks653 partition real-time operating system, which comprises the following specific adaptation methods:
step S1: PCI-E environment configuration is completed through system file modification, and system registration is completed for the FC equipment by means of core layer system functions.
Step S1.1: and modifying the configuration file of the core layer system to finish adding the PCI-E core IO memory pool.
First, in the system configuration file of the core layer, the addition of the core IO memory pool of the PCI-E device is completed, and the memory pool provides space for data from the PCI-E device. The corresponding fsl _p2020_rdb.xml file in this example is added with a "kernel IO3" entry with a size of 256M after the original core IO memory pool of the system, and the configuration result is shown in figure 3.
And S1.2, modifying a core layer system configuration header file, and adding or modifying macro variables related to PCI-E equipment basic information.
In the core layer system configuration header file, macro variable definitions of basic information about PCI-E device memory space base address, memory size, PCI-E bridge and the like need to be added, and the information corresponds to the memory pool information and is used as parameters when the drive registration and PCI-E drive library functions are used. The corresponding system configuration header files in this example are config.h and fsl _p2020_rdb.h, and the added basic information macro variables include pcie_law_base, pcie_law_size1, pcie_mmu_tlb_sz, pcie_mmu_adrs, pcie_mmu_size, pcie_io_adrs, pcie_io_size, pcie_mmu_memio_adrs, pcie_mmu_memio_size, and the like, and these memory SIZEs and register addresses are modified to be consistent with the values in the description file in the board-level support packet.
And S1.3, modifying the function file of the core layer system library, and finishing PCI-E driving registration.
And adding a source file, a header file and the like of a referenced driver library operation library function into a core layer system library function file, enabling a PCI-E driver interface to be integrated into a core layer operation system, completing the registration of a PCI-E device driver by utilizing a corresponding initialization function, and providing interface support for the read-write data operation of the FC sub-card device based on PCI-E connection. The corresponding core layer library function file in this example is sysLib.c, and the added header/source file includes < drv/pcb/m 85xxPci.h >, < speLib.h >, < pcb/pciexConfigShow.c >, < pcb/pciexAutoConfigLib.c >, < drv/m85xxtimer c >, < drv/picTmrDrv.c >, etc., after which the device driver registration of PCI-E is completed in the sysLib.c file using the sysHwInit function, so that the system automatically completes the loading of the PCI-E driver library at the time of loading, and data reading and writing can be performed through the PCI-E operation FC sub-card.
And S1.4, completing parameter configuration of the PCI-E equipment and realizing identification of the FC equipment.
The user code section of the core operating system completes corresponding parameter setting by using a PCI-E configuration function, and completes identification of the connected FC sub-card after the system is loaded, thereby being the basis for realizing operation of the FC equipment. In this example, in the user code section of the usrAppInit.c file of the VxWorks653 core layer operating system, the automatic configuration of the PCI-E device is completed by using the sysPciExpressAutoConfig function, after the system is loaded, the Host Shell is called on the Host to execute the pciExDeviceShow command to query the PCI-E mounted device, so that the FC sub-card with the vector number (vendorID) of 0x10ee can be successfully queried, and the identification result of the FC sub-card is shown in fig. 4.
Step S2: and modifying the FC drive library to complete mapping association of the FC protocol and the Ethernet protocol address, and then performing adaptation addition aiming at an operating system.
Step S2.1: and modifying the FC drive library, adding a protocol encapsulation interface, and completing address mapping association of the FC protocol and the Ethernet protocol.
The Domain ID, the Area ID and the Port ID in the FC-ID are respectively corresponding to MAC, IP, port addresses in the Ethernet addresses, so that a one-to-one mapping relation between the FC and the Ethernet addresses is established, a corresponding interface is added in the FC drive, and an Ethernet data frame from an upper system is packaged into the FC frame as a data segment, so that bridging communication of the FC-Ethernet is realized. In this example, a TCP/IP four-layer network protocol model is used as the encapsulation base of the ethernet data frame, the protocol encapsulation flow is shown in fig. 5, and the schematic diagram of the modified FC driving module is shown in fig. 6.
Step S2.2: and completing the adaptation and modification of the FC drive library function, and compiling the FC drive library function into a static link library by utilizing a compiler corresponding to an operating system.
Checking the interface of the FC drive library function, PCI-E of the operating system and Ethernet function to ensure consistency, so that the system Ethernet application can operate the FC equipment through the PCI-E; and compiling the source file of the FC driving library into a plurality of executable files in a compiler corresponding to the operating system, compiling the executable files into a static link library by adopting a corresponding compiling tool, adding the static link library into the system for operation, and realizing the function call of the FC driving library through system configuration. In the embodiment, gnu related instructions are operated in VxWorks653 2.5Development Shell of the Workbench to complete executable file compiling work of the FC drive library, and the executable file compiling and compiling result of the source file is shown in figure 7; the several executables were then unified into an FC driven static link library PCI 6553.A using the arrpc and ranlibpc tools.
Step S2.3: the FC driver static link library is added to the system image.
In the system compiling configuration option, setting corresponding parameters, so that the FC-driven static link library is added into the compiling flow of the system image. In the core layer project compiling attribute tab of the Workbench, the compiled FC drive static link library is added into the system running image by adding an EXTRA_LIBS+ = $ (PRJ_DIR)/PCI_6553. A statement in a Build Command box.
Step S3: and (3) finishing the registration of the system equipment of the FC sub-card, identifying the FC sub-card as a virtual Ethernet network card, initializing a bridging network card at a system core layer, and finishing the parameter configuration of the bridging network card.
Step S3.1: the core layer system offloads the existing ethernet network card.
And the user code section of the core layer system uses corresponding functions to finish the unloading of relevant configurations such as equipment and protocol stacks of the existing Ethernet network card, and reserves corresponding space for mounting the FC sub-card. In the present example, in the user code section of the core layer usrAppInit.c file, the unloading of the existing Ethernet network card is completed by using ipDetech and muxDev Unload functions, and the unloading of the Ethernet host and the path related configuration information is completed by using hostDelete and routeDelete functions.
Step S3.2: and completing parameter configuration of the FC equipment and realizing initialization of the virtual network card.
And the user code section of the core layer system uses a corresponding function to complete parameter configuration of the FC equipment, simultaneously completes mapping relation establishment of the FC-ID and the Ethernet address, and recognizes the FC equipment as an Ethernet network card through the PCI-E, thereby realizing mounting of the virtual network card and enabling the virtual network card to be directly used by an upper Ethernet application. In the embodiment, in a user code section of a core layer usrAppInit.c file, the configuration of a user-defined network card, namely a virtual network card, is completed by sequentially utilizing the iptach and usrNetIfConfig functions, simultaneously, the initialization of FC equipment is realized by utilizing a netInit interface and a pciConfig interface, and the reading of a configuration file storing an FC-ID Ethernet address mapping relation is completed, so that the whole adaptation process of the FC-bridge network card is completed, two P2020 RDB boards are connected with an FCE-1221A sub-card on a fiber channel, a VxWorks653 2.5 version partition real-time operating system is loaded, and an Ethernet ping command is mutually operated in an upper computer Host Shell to carry out communication test, wherein the test result is shown in an attached figure 8, and the result proves that the embodiment of the invention successfully realizes the adaptation of the FC-Ethernet bridge and can directly operate the Ethernet command on the fiber channel.
As described above, the embodiment of the invention recognizes the FC daughter card with the FC-Ethernet bridging function as a virtual Ethernet network card based on PCI-E by modifying the system configuration and adapting the corresponding driver library, so that the upper Ethernet application can directly communicate on the optical fiber channel, the FC equipment recognition compatibility problem is solved, and the adaptation of the FC-Ethernet bridging network card of the partitioned real-time operating system is realized.
The adaptation method of the partitioned real-time operating system FC-Ethernet bridging network card provided by the invention realizes compatible identification of FC communication equipment based on bus equipment, enables upper-layer application to directly call an FC communication equipment interface through corresponding system configuration and code modification, can complete compatible identification of FC protocol communication equipment on different hardware platforms based on the invention, and provides basic support for transplanting of Ethernet application and functional expansion of a system platform.
Any obvious modifications, or equivalent substitutions, or further optimization of the details set forth above, without departing from the basic technical spirit and principles of the present invention, are intended to be included within the scope of the claims.
Claims (4)
1. The method is characterized in that through modifying system files and configuring system environments, FC communication equipment is identified as a virtual Ethernet network card by utilizing a hardware bus, and the compatibility of the FC bridging communication network card is realized, so that an upper Ethernet application can directly call a corresponding interface; in addition, the method can be customized and adjusted according to different application scenes and requirements so as to realize bridging communication of different software and hardware environments; the adaptation method comprises the following steps:
step S1: PCI-E environment configuration is completed through system file modification, a core layer system function is called, and system registration is completed for the FC equipment;
step S2: modifying the FC drive library to complete mapping association of the FC protocol and the Ethernet protocol address, and then performing adaptation addition aiming at an operating system;
step S3: and (3) finishing the registration of the system equipment of the FC sub-card, identifying the FC sub-card as a virtual Ethernet network card, initializing a bridging network card at a system core layer, and finishing the parameter configuration of the bridging network card.
2. The method for adapting the FC-ethernet bridging network card of the partition real-time operating system according to claim 1, wherein in the step S1, the specific steps are as follows:
step S1.1: modifying the configuration file of the core layer system to finish adding the PCI-E core IO memory pool;
step S1.2: modifying a core layer system configuration header file, and adding or modifying macro variables related to basic information of PCI-E equipment;
step S1.3: modifying a core layer system library function file and finishing PCI-E driving registration;
step S1.4: and completing the parameter configuration of the PCI-E equipment and realizing the identification of the FC equipment.
3. The method for adapting the FC-ethernet bridging network card of the partition real-time operating system according to claim 1, wherein in the step S2, the specific steps are as follows:
step S2.1: modifying an FC drive library, adding a protocol encapsulation interface, and completing address mapping association of an FC protocol and an Ethernet protocol;
step S2.2: completing the adaptation and modification of the FC drive library function, and compiling the FC drive library function into a static link library by utilizing a compiler corresponding to an operating system;
step S2.3: the FC driver static link library is added to the system image.
4. The method for adapting the FC-ethernet bridging network card of the partition real-time operating system according to claim 1, wherein in the step S3, the specific steps are as follows:
step S3.1: the core layer system uninstalls the existing Ethernet network card;
step S3.2: and completing parameter configuration of the FC equipment and realizing initialization of the virtual network card.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310631310.2A CN116566817A (en) | 2023-05-31 | 2023-05-31 | FC-Ethernet bridging network card adaptation method for partition real-time operating system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310631310.2A CN116566817A (en) | 2023-05-31 | 2023-05-31 | FC-Ethernet bridging network card adaptation method for partition real-time operating system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116566817A true CN116566817A (en) | 2023-08-08 |
Family
ID=87498207
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310631310.2A Pending CN116566817A (en) | 2023-05-31 | 2023-05-31 | FC-Ethernet bridging network card adaptation method for partition real-time operating system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116566817A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116743587A (en) * | 2023-08-11 | 2023-09-12 | 太初(无锡)电子科技有限公司 | Virtual network interface implementation method and device based on heterogeneous computing accelerator card |
-
2023
- 2023-05-31 CN CN202310631310.2A patent/CN116566817A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116743587A (en) * | 2023-08-11 | 2023-09-12 | 太初(无锡)电子科技有限公司 | Virtual network interface implementation method and device based on heterogeneous computing accelerator card |
| CN116743587B (en) * | 2023-08-11 | 2024-01-26 | 太初(无锡)电子科技有限公司 | Virtual network interface implementation method and device based on heterogeneous computing accelerator card |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108023952B (en) | Cloud and mist combination-based modularized Internet of things application rapid construction platform | |
| AU613248B2 (en) | Translation technique | |
| JP2020184375A (en) | Dynamic reconfiguration of applications on multiprocessor embedded system | |
| CN116566817A (en) | FC-Ethernet bridging network card adaptation method for partition real-time operating system | |
| CN104965700B (en) | The method and system of driving SPI equipment is realized under vxworks operating system | |
| CN111459605A (en) | Edge computing gateway virtualization method based on Docker | |
| CN110704070B (en) | Method for constructing DDS communication middleware under partitioned real-time operating system | |
| CN114077462A (en) | Method, device, equipment and medium for calling Android HIDL interface by software operating system | |
| WO2021107179A1 (en) | Method and device for automatic generation of setting code of autosar-based application software | |
| CN110187909A (en) | A kind of single-chip microcontroller firmware upgrade method based on android system | |
| CN100428171C (en) | Communication method between data plane and control plane | |
| CN114721719B (en) | Method and system for containerized deployment of heterogeneous applications in cluster | |
| CN104391726A (en) | SFP (Small Form-Factor Pluggable) optical module upgrading method based on Bootloader | |
| CN111443919B (en) | Method for realizing SCA core framework on DSP multi-core processor | |
| CN109684148B (en) | Airborne embedded software virtual bus communication construction method based on ARINC653 | |
| US6651104B1 (en) | Multi-layered interface for interconnecting application programs to system bus lines for electronic devices | |
| CN110221867A (en) | Pulse I/O function cartoon letters drive system and method under a kind of XP system | |
| CN100370764C (en) | Protocol test device and method for realizing protocol test | |
| CN1744055A (en) | Software test method | |
| CN116819992A (en) | STM32 EtherCAT-based embedded numerical control system | |
| CN110413311A (en) | ' In System Reconfiguration Method and server | |
| CN116450109A (en) | Modbus communication library adaptation method under MATLAB and CCS combined development mode | |
| CN113282378B (en) | Vehicle-mounted system based on environment isolation subsystem | |
| CN112445728B (en) | Robot development board ROS communication system supporting multiple hardware interfaces | |
| CN113014453B (en) | DPDK-based data packet playback method, system and medium in k8s |
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 |