Skip to content
This repository was archived by the owner on Jun 17, 2026. It is now read-only.

Latest commit

 

History

History
47 lines (35 loc) · 2.71 KB

File metadata and controls

47 lines (35 loc) · 2.71 KB

UDP Shell Interface (USIF)

This page describes the UDP front-end process of the cFp_HelloKale/Role_BrinUp to the cFp_HelloKale/Shell_Kale.

Overview

The UDP Shell Interface (USIF) handles the control flow interface between the SHELL and the ROLE. The main purpose of the USIF is to provide a placeholder for the opening of one or multiple listening port(s). The use of such a dedicated layer is not a prerequisite but it is provided here for sake of clarity and simplicity.

A block diagram of the UDP Shell Interface is depicted in Figure 1. It features:

  • a Listen (LSn) process to request the SHELL/NTS/UOE to start listening for incoming connections on a specific port. Although the notion of 'listening' does not exist for the unconnected UDP mode, we keep that name for this process because it puts an FPGA receive port on hold and ready to accept incoming traffic (.i.e, it opens a connection in server mode).
  • a Close (CLs) process to request the SHELL/NTS/UOE to close a previously opened port.
  • a Read Path (RDp) process that waits for new data segments from SHELL/NTS/UOE and forwards them to the UDP Application Flash (UAF) core.
  • a Write Path (WRp) process that waits for new data segments from the ROLE/UAF and forwards them to SHELL/NTS/UOE.

Block diagram of cFp_HelloKale/ROLE/USIF

Figure-1: Block diagram of the UDP Shell Interface


List of Interfaces

Acronym Description File
SHELL UDP application interface to shell Kale. Shell
UAF UDP Application Flash interface udp_app_flash

List of HLS Components

Acronym Description Filename
CLs Close process udp_shell_if
LSn Listen process udp_shell_if
RDp Read Path process udp_shell_if
WRp Write Path process udp_shell_if