Overview
UOE is high performance and highly customizable UDP/IP hardware stack compliant with RFC 768 (for UDP) and RFC 791 (for IPv4)/RFC 2460(for IPv6). As shown in the figure below, the UOE core includes:
* L4 UDP engine
* L3 IPv4/IPv6 engine
* L2 Mac engine
* Statistic counter blocks and user configurable registers
* ARP and ICMP buffers
UOE is designed to be integrated with any Ethernet Solutions that has AXI4-ST/Avalon-ST interface. User interface can be customized for AXI4-ST or Avalon-ST. Data path in addition supports a wide range of interface widths from 32-bit up to 512-bit. Single clock design provides easy manageability for the user.
32-bit user interface runs @ 312.5MHz clock for 10G, 64- bit user interface runs @ 156.25MHz for 10G, 128-bit user interface runs @ 312.5MHz for 40G, 256-bit user interface runs @ 156.25MHz for 40G, and 512-bit user interface runs @ 312.5MHz for 100G.
Core IP layer can be customized for IPv4 or IPv6 depending on the application.
The header fields can be configured once for point-topoint applications.
Our solution implements and delivers the low latency with highest throughput and minimum or no interpacket gap.
Learn more about Ethernet IP core
Building on its High-Speed Ethernet controller IP family, Cadence provides ESUN-ready controller IP for next-generation AI scale-up networking.
This blog post explores how the team verified a 10BASE-T1S automotive ethernet subsystem using a Cadence tools-based multi-platform verification, which unifies simulation, emulation, and formal verification techniques.
Learn how ESUN enhances Ethernet for lossless, predictable AI scale-up networking—cutting overhead, reducing tail latency, and improving efficiency.
Ethernet has evolved significantly from 10 Mbps shared media to today’s multi-hundred gigabit high-speed links. One foundational feature that has enabled this scalability and ease of deployment is Auto-Negotiation (AN).
Ethernet was originally designed for high-speed data transfer and interoperability between devices. However, traditional Ethernet does not provide built-in mechanisms for securing data traffic, such as encryption or authenticity protection. This is where MACsec comes into the picture.
This blog examines what separates truly automotive-grade Ethernet IP from generic implementations across functional safety, time-sensitive networking, security, observability, lifecycle management, and the integration disciplines that only become visible once a program is deep into development.