CONTACT MLE
Please fill in the form and your requirements below, and our team will contact you soon.


    AMD (Xilinx)Altera (Intel)LatticeMicrochip (MicroSemi)Other


    *By submitting this form you are consenting to being contacted by the MLE via email and receiving marketing information.

    X
    CONTACT MLE

    1. NPAP Features

    1. NPAP Features With a focus on reliability and low, deterministic latency, HHI designed this for embeddable FPGA and ASIC systems with the following features: Interface to 1 / 2.5 / 5 / 10 / 25 / 40 / 50 / 100 / 200 / 400 Gigabit Ethernet (depending on the FPGA device and speedgrade.) Full-duplex with 128 bit wide bidirectional datapath  Full line rate of 70 Gbps, or more, per instance in FPGA Full line rate of over 100 Gbps per instance in ASIC Low one-way latency NPAP-to-NPAP (600 nanoseconds for 100 Bytes) Network diagnostics functions (optional) TCP session priority management (optional) Transport Layer Security (TLS) (optional) Time-Sensitive Networking (TSN) (optional) Network Impairment Generators (optional) Designed for maximum flexibility, NPAP implements in programmable logic the relevant network communication protocols: IPv4 The core of the most standards-based networking protocols TCP Reliable connectivity for direct secured connectivity UDP Widespread protocol to enable simple direct or multicast communication RRRRP Reliable, Rapid Request-Response Protocol based on Stanford HOMA ICMPv4 Diagnostic protocol to validate connections IGMPv4 Enables joining of multicast groups (optional) Due to the modularity NPAP can easily be enhanced by application specific protocols. The 128 bit wide datapath in combination with a pipelined architecture allows to scale throughput to line-rates of 50 GbE, and

    2. NPAP Applications

    2. NPAP Applications NPAP enhances your networked application with fast, scalable and reliable data connectivity. The powerful architecture of the underlying TCP/UDP/IPv4 Stack allows it to transfer data at line-rate with low processing latency without using any CPUs in the data path. The ubiquitous TCP/IPv4 and/or UDP/IPv4 communication protocol suite uses industry standard network infrastructure to address a wide-range of applications: High-Speed connectivity for distributed systems and Systems-of-Systems Scale-out datacenter connectivity Reliable, long-range chip-to-chip connectivity with backpressure FPGA-based SmartNICs High-Bandwidth Security with FPGA-based Smart Data Diodes  In-Network Compute Acceleration (INCA) Hardware-only implementation of TCP/IPv4 in FPGA PCIe Long Range Extension Networked storage, such as iSCSI or NVMe/TCP Test & Measurement connectivity Automotive backbone connectivity based on open standards High-speed, low-latency camera interfaces Video-over-IP for 3G / 6G / 12G transports Bring full TCP/UDP/IPv4 connectivity to FPGAs High-speed sensor data acquisition:stream data out of FPGAs into Network-Attached Storage (NAS)  High-speed robotics control and machine-to-machine:Stream data from servers via FPGA into actuators Hyper-converged computational storage acceleration for “over-Fabric” NVMe/TCP Deterministic low-latency, high-bandwidth, secure alternative to lwIP or Linux on embedded CPU 🌐 www.missinglinkelectronics.com MLE (Missing Link Electronics) is offering technologies and solutions for Domain-Specific Architectures, which focus on heterogeneous computing using FPGAs. MLE is headquartered in Silicon Valley with offices in Neu-Ulm and Berlin,

    3. NPAP Functionality Description

    3. NPAP Functionality Description NPAP is a complete subsystem of a high-performance programmable-logic based, standalone network stack featuring transparent handling of complete TCP/IPv4 and UDP/IPv4 protocol tasks, e.g. packet encoding, packet decoding, acknowledge generation, link supervision, timeout detection, retransmissions and fault recovery.  NPAP supports complete automatic connection control including tear up and tear down. Compute and manage retransmission timers as in RFC 6298. Transparent checksum generation and checksum checking, integrated flow control. RFC 9293 compatibility (TCP/IPv4 stack for Windows and Linux).  Depending on the project’s needs, deliverables can be: HDL source code or netlist Integrated FPGA system implementation Testbenches and scripts for real-life testing Comprehensive documentation and interfacing guide Development & design-in support NPAP has been optimized to ensure the best bandwidth-delay product performance for your application. To guarantee delivery of full performance and reliability Team MLE will support you in all engineering aspects: System-level architecture design where aspects such as mapping ingress / egress data streams to TCP sessions, or handling TCP’s congestion control, or optimizing the bandwidth-delay-product are handled in order to meet system-level bandwidth and latency requirements.  Chip-design, i.e. managing chip resources, interfacing with the Multi-Gigabit Transceivers (MGT), handling on-chip streaming (such as AXI beats) while integrating NPAP into your FPGA or ASIC device on your target hardware. Network

    3.1. NPAP Technical Features

    3.1. NPAP Technical Features FeatureSpecificationSupported on-chip Interfaces128 bit wide AXI4-StreamCompatibility with 3rd party Ethernet PHY interfacesStandard IEEE Ethernet PHYs with RMII, GMII, XGMII, etc via PCS/PMA via ASIC/FPGA Ethernet SubsystemCompatibility with 3rd party Ethernet Media Access ControllersFraunhofer HHI 10G/25G Low-Latency MACAMD/Xilinx 10G/25G Ethernet Subsystem (PG210)AMD/Xilinx 100G Ethernet Subsystem (PG165, PG203, PG314)Altera 10G / 25G Ethernet FPGA IPMicrochip PolarFire FPGA 10G Ethernet (UG0727)Lattice 10G / 25G Ethernet IP (FPGA-IPUG-02245)Supported protocols (Hardware based)Ethernet, ARP, IPv4, ICMPv4 (response only), IGMPv4, UDP & TCP, DHCP (client only)Number of simultaneous connectionsOne per TCP Core instantiation – see “Architecture Choices” below, a TCP Core in NPAP relates to a TCP socket in LinuxMessage SizesSupport for Ethernet Jumbo Frames of arbitrary lengthInterface to applicationDatapath via AXI4-Stream 128-bitand separate custom TCP command interfaceSupported FPGAs  Complete stack uses generic VHDL code (IEEE-1076 2002 or 2008, depending on NPAP version)AMD/Xilinx Virtex 4 to Virtex UltraScale+AMD/Xilinx Kintex to Kintex UltraScale+AMD/Xilinx Artix UltraScale+AMD/Xilinx Zynq-7000AMD/Xilinx Zynq UltraScale+ MPSoCAMD/Xilinx Zynq UltraScale+ RFSoCAMD/Xilinx Versal ACAP SeriesAltera Cyclone IV seriesAltera Cyclone 10 GX seriesAltera Stratix VAltera Stratix 10 GX seriesAltera Agilex 5 D, E SeriesAltera Agilex 7 F, I, M SeriesLattice Avant-G, Avant-XMicrochip Polarfire and PolarFire SoCPerformance70 Gbps line rate, or more, for single TCP/IPv4 session (depending on clock rate, see below)Typ. 600 ns transport delay (depending on

    3.2. NPAP Implementation Details

    3.2. NPAP Implementation Details NPAP implements a full accelerator, hence all network protocol processing is running as digital logic. Because NPAP does not rely on “soft” CPUs nor on external CPUs, NPAP shows very low and deterministic latency. Tradeoff cost vs performance over chip resources. Dataflow is full duplex 128 bits wide using AXI4 Stream. This enables high data throughput without “FPGA bloat” nor timing issues. Control-flow uses AXI4 Lite register interfaces, along with a hardware abstraction layer (HAL), Linux device drivers and Python scripts for NPAP administration. NPAP is intensively tested for performance and interoperability against many other TCP/UDP/IPv4 network stacks. NPAP brings its own 10G / 25G Low-Latency Ethernet MAC,but can interface with many Ethernet subsystems from the FPGA vendors. NPAP implements a complete TCP/UDP/IPv4 stack including functions like ARP, ICMPv4, IGMPv4, DHCP. NPAP is delivered with “Support IP blocks” including reference designs, design examples for setting MAC addresses and/or IPv4 addresses and/or TCP port numbers either from Programmable Logic / ASIC or via software running on a (Linux) host, either ARM or x86 based. For each TCP connection that remains open at the same time, there shall be a dedicated instance of a TCP Core. An AXI4-Lite interface may be used to prioritize TCP sessions during runtime. One and

    3.3. NPAP Dataflow and Block Diagram

    3.3. NPAP Dataflow and Block Diagram The following shows the dataflow view of an exemplary design integrating NPAP with one UDP core and multiple TCP cores (3 for user-level plus 2 for Netperf), each with an example user application, plus Netperf (for bandwidth and latency benchmarking), plus network impairment (for Bit Error Rate Testing), plus diagnostics counters: The example user applications serve as an example on how to send and/or receive data from programmable logic via TCP/UDP/IPv4. For TCP this logic is inside one (or more) TCP Wrappers which contain HDL code for handling the control and data flow: TCA – the TCP Command Application to open/close a TCP connection TDA – the TCP Demo Application which uses the TCA to control the TCP session and can forward data to and from external applications such as the DGC DGC – a Data Generator and Checker which can generate payload data for sending and at the same time can check received payload data Similarly, for UDP this logic is inside the one (or more) UDP Wrappers which contain HDL code for handling the control and data flow: UDA – the UDP Demo Application which handles the control and data flow for one UDP port  DGC – a Data Generator and Checker which can

    3.4. NPAP Control-Flow View and Hardware Abstraction Layer

    3.4. NPAP Control-Flow View and Hardware Abstraction Layer For administration and control at run-time, NPAP implements so-called Runtime Parameterization and administration via an AXI-Lite register space. Access to this interface is exported through the so-called NPAP Hardware Abstraction Layer (HAL). Along with a Python library, NPAP HAL provides a high-level API for Linux software, utilizing swappable backends to communicate with the hardware across diverse environments, from SOC processing systems to remote workstations. Here a list of connectivity choices for NPAP HAL: Via USB-UART or USB-JTAG or USB-IIC Via the FPGA-integrated Processing System which can be ARM, RISC-V, MicroBlaze, NIOS, etc Via PCIe connection with the host CPU  Via out-of-band Ethernet and UDP (on the roadmap) Via in-band Ethernet and UDP (on the roadmap) Besides NPAP HAL, MLE further provides a python based command-line tool, called npap-admin, that abstracts complex runtime parameterization into simple configuration file editing. Customers have been using npap-admin during evaluation and development, for Continuous Integration or in-the-field when NPAP-based products have been deployed. Good design examples for Runtime parameterization and administration of NPAP are the so-called NPAP Evaluation Reference Designs (ERD) running on many off-the-shelf FPGA platforms. Please read below for more information. 3.4.1. NPAP Admin via USB-UART or USB-JTAG This mode of administration is very useful when using