Satellite-borne multi-concurrent network file system implementation method based on Zynq-7000 platform

Abstract

The invention provides a satellite-borne multi-concurrent network file system implementation method based on a Zynq-7000 platform, and relates to the technical field of satellite-borne computer systems. The method comprises the following steps: a hardware platform adopts a Zynq-7000 SoC, and integrates an ARMCortex-A9 processor and an FPGA (Field Programmable Gate Array) logic resource; the interface supports a serial port and a network port, and the network port is in dual-redundancy configuration; the operating system adopts a BusyBox to construct a cutting version Linux system, comprises a ramdisk file system and runs at a PS (Packet Switch) end; a file system adopts ramdisk as a root file system, a Xilinx Vivado tool is used for configuring PL logic to generate a bitstream file, U-Boot, a device tree, a kernel, the file system, the PL bitstream and an FSBL are packaged into a single mirror image file to be stored in an SPI Flash, and an FSBL starting parameter is configured; the network file system module provides a standard network file system interface to the outside and supports concurrent access of multiple clients; during starting, the U-Boot is guided by the FSBL, and then the whole operating system is loaded by the U-Boot; and the storage medium is used for mounting NAND Flash through hardware and providing persistent storage capability.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of spaceborne computer systems, and particularly relates to a spaceborne multi-concurrent network file system implementation method based on a Zynq-7000 platform. BACKGROUND

[0002] With the complication and diversification of space missions, the reliability, real-time performance and concurrency of data storage and access of spaceborne systems are put forward with higher requirements. Traditional spaceborne file systems mostly adopt single client access mode, which is difficult to meet the demand of multi-task parallel processing. At the same time, there is strong radiation interference in the space environment, which is easy to cause single event effect (SEE), and then cause system abnormality or data error.

[0003] At present, the mainstream spaceborne operating system mostly adopts customized embedded system, lacks flexible file system interface, and has performance bottleneck when facing multi-client concurrent access. In addition, the existing system also has deficiencies in storage medium adaptation, system fault tolerance mechanism, etc., and it is difficult to realize fast transplantation and high reliability operation. In addition, the traditional network file system has some problems in the real-time performance and reliability of network reconnection. SUMMARY

[0004] In order to solve the problems existing in the prior art, the present application aims to realize a spaceborne multi-concurrent network file system based on Zynq-7000 platform, which has high reliability, high concurrency and good portability, can stably run in space environment, and supports multi-client concurrent access and data read-write operation.

[0005] To achieve the above purpose, the present application provides a spaceborne multi-concurrent network file system implementation method based on Zynq-7000 platform, which comprises: (1) System construction Hardware platform: Zynq-7000 SoC is adopted, which integrates ARMCortex-A9 processor and FPGA logic resource; Interface support: serial port, network port; Operating system: a trimmed version of Linux system is constructed by using BusyBox, which contains a ramdisk file system and runs on the PS end; File system: ramdisk is used as the root file system, Xilinx Vivado tool is used to configure PL logic to generate bitstream file, U-Boot, device tree, kernel, file system and PL bitstream are packaged into a single image file and stored in SPI Flash, and FSBL startup parameters are configured; Network file system module: a standard network file system interface is provided externally, and multi-client concurrent access is supported.

[0006] (2) System startup After power on, FSBL loads U-Boot from SPI Flash; U-Boot loads device tree, kernel and ramdisk file system; After Linux system starts, mount the NAND Flash as persistent storage; Start the network file system service and listen to the client connection request; (3) Multi-client access implementation The network file system module is implemented based on NFS or a custom protocol; Use multi-threading or asynchronous IO mechanism to handle concurrent requests; Introduce a locking mechanism to ensure data consistency; (4) Fault tolerance and refresh mechanism implementation The Linux system feeds the watchdog through GPIO timing, and triggers reset when an exception occurs; The serial port sends the PL refresh instruction at regular intervals, detects the PL state and reloads the logic; The file system introduces a verification mechanism to detect data integrity; The management and control data stream stored in the storage module is protected by RS encoding; Use dual-network backup mechanism for network switching; (5) Storage medium adaptation method Configure multiple storage drivers in the Linux kernel; Configure storage device parameters through device tree; The file system is decoupled from the underlying device through the mount point, enabling flexible adaptation.

[0007] Optionally, the network file system module is based on TCP for network connection, and a module named TCPR is used for connection establishment and communication. The functions of the TCPR module include: recording the established connections, automatically reconnecting after the connection is disconnected and recording the number of reconnections, disconnecting and ending the current NFS service after multiple reconnection failures.

[0008] Optionally, the dual-network backup mechanism is implemented at the physical layer as follows: The PL end realizes the kneading of two PHY chips, and the two PHY chips are cold standby for each other, forming a unified interface for the PS end. The PS end uses the same MDIO to initialize and control the two PHY chips, and uses the GMII interface to transmit and receive data from the PHY chip. The PL end switches when it receives the PHY switching signal. The PL end controls which PHY chip the PS end uses to interact with the outside world. BRIEF DESCRIPTION OF DRAWINGS

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0010] Figure 1 Network file system module client connection and data access path schematic diagram; Figure 2 Network file system startup flowchart; Figure 3 TCPR module function diagram; Figure 4 Dual-network-port redundancy design physical architecture diagram. DETAILED DESCRIPTION

[0011] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0012] The present disclosure provides a kind of based on Zynq-7000 platform's on-board multiple concurrent network file system implementation method, comprising: (1) System construction Hardware platform: Zynq-7000 SoC is used, integrates ARMCortex-A9 processor and FPGA logic resource; Interface support: serial port, network port; Operating system: the cut Linux system of BusyBox is used to build, contains ramdisk file system, and is run in PS end; File system: ramdisk is used as root file system, Xilinx Vivado tool is used to configure PL logic, generates bitstream file, U-Boot, device tree, kernel, file system and PL bitstream and FSBL are packaged into single image file and stored in SPI Flash, and FSBL startup parameter is configured; Network file system module: as shown in Figure 1 It provides standard network file system interface to the outside, and supports multiple client concurrent access; (2) System startup As shown in Figure 2As shown, after power on, the FSBL loads U-Boot from the SPI Flash; U-Boot loads the device tree, kernel and ramdisk file system; After the Linux system starts, the NAND Flash is mounted as persistent storage; Start the network file system service and listen for client connection requests; (3) Multi-client access implementation As shown in Figure 3 , the network file system module is implemented based on NFS or a custom protocol, network connection is based on TCP, and the TCPR module is used for connection establishment and communication. The functions of the TCPR module include: recording the established connections, automatically reconnecting after the connection is disconnected and recording the number of reconnections, disconnecting and ending the current NFS service after multiple reconnection failures; Use multi-threading or asynchronous IO mechanism to handle concurrent requests; Introduce a locking mechanism to ensure data consistency; (4) Fault tolerance and refresh mechanism implementation The Linux system feeds the watchdog through GPIO timing, and triggers reset when an exception occurs; The serial port sends the PL refresh instruction at regular intervals, detects the PL state and reloads the logic; The file system introduces a verification mechanism to detect data integrity; The management and control data stream stored in the storage module is protected by RS encoding; Use dual-network backup mechanism: In order to improve the reliability of the entire file system, on the basis of traditional on-board hardware watchdog mechanism and PL program refresh mechanism, implement dual-network redundancy design at the physical layer, as shown in Figure 4 , the PL end implements the kneading of two PHY chips, and the two PHY chips are cold standby for each other, forming a unified interface to the PS end, similar to a single-pole double-throw switch. The PS end uses the same MDIO to initialize and configure and control the two PHY chips, and uses the GMII interface to transmit and receive data from the PHY chip. When the PL end receives the PHY switching signal, it switches. The PL end controls which PHY chip the PS end uses to interact with the outside world, achieving a seamless network switch for the PS end. (5) Storage medium adaptation method Configure multiple storage drivers (such as MTD, MMC) in the Linux kernel; Configure storage device parameters through device tree; The file system is decoupled from the underlying device through the mounting point, enabling flexible adaptation.

[0013] Those skilled in the art can clearly understand the method of the above-mentioned embodiments can be realized by means of software and necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of software product, which is stored in a computer readable storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes a plurality of instructions to make a terminal device enter the method described in various embodiments of the present application.

[0014] In the description of the present specification, the description of the terms "one embodiment", "another embodiment", "other embodiments", or "first embodiment to Xth embodiment" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, method steps or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0015] It should be noted that in this paper, the term "include", "contain" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or system including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or includes elements inherent to such process, method, article or system. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or system including the element.

[0016] The above-mentioned embodiment numbers of the present application are only for description, not representing the advantages and disadvantages of the embodiments.

[0017] The above is only the preferred embodiment of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation, or direct or indirect application in other related technical fields based on the content of the present application specification and drawings, are also included in the patent protection scope of the present application.

Claims

1. A method for implementing a spaceborne multi-concurrent network file system based on a Zynq-7000 platform, characterized in that, Comprise: (1) System construction Hardware platform: Zynq-7000 SoC is adopted, which integrates ARMCortex-A9 processor and FPGA logic resources; Interface support: serial port, network port; Operating system: the trimmed version of Linux system is constructed by using BusyBox, which contains ramdisk file system and runs in PS end; File system: ramdisk is used as root file system, Xilinx Vivado tool is used to configure PL logic to generate bitstream file, U-Boot, device tree, kernel, file system and PL bitstream and FSBL are packaged into a single image file and stored in SPI Flash, and FSBL startup parameters are configured; Network file system module: standard network file system interface is provided to support multiple client concurrent access; (2) System startup After power on, FSBL loads U-Boot from SPI Flash; U-Boot loads device tree, kernel and ramdisk file system; After Linux system starts, mount NAND Flash as persistent storage; Start network file system service and listen to client connection request; (3) Multi-client access implementation Network file system module is implemented based on NFS or custom protocol; Use multi-thread or asynchronous IO mechanism to handle concurrent requests; Introduce lock mechanism to ensure data consistency; (4) Fault tolerance and refresh mechanism implementation Linux system feeds the watchdog through GPIO timing, triggers reset when abnormal; Serial port sends PL refresh instruction regularly, detects PL state and reloads logic; File system introduces verification mechanism to detect data integrity; The management and control data stream stored in the storage module are protected by RS encoding; Use dual network port backup mechanism for network switching; (5) Storage medium adaptation method Configure multiple storage drivers in Linux kernel; Configure storage device parameters through device tree; 2. The method for implementing a multi-concurrent network file system on a Zynq-7000 platform according to claim 1, wherein, File system is decoupled from underlying device through mounting point to achieve flexible adaptation.

3. The method of claim 1, wherein the Zynq-7000 platform-based implementation of a multi-concurrent network file system on a satellite is characterized by, The network file system module is based on TCP for network connection, and a module named TCPR is used for connection establishment and communication. The functions of TCPR module include: recording the established connections, automatically reconnecting after connection is disconnected and recording the number of reconnections, disconnecting and ending the current NFS service after multiple reconnection failures. The dual network port backup mechanism is implemented at the physical layer, and the specific way is as follows: Two PHY chips are kneaded in the PL end, two PHY chips are cold standby for each other, and a unified interface is formed for the PS end, the PS end uses the same MDIO to initialize and control the two PHY chips, and uses the GMII interface to transmit and receive data of the PHY chip, the PL end switches when receiving the PHY switching signal, and the PL end controls the PS end to use which PHY chip to interact with the outside world.

Images