EthFw Release Notes

Version: 11.02.00

Introduction

This release notes provides important information that will assist you in using the EthFw component. This document provides the product information and known issues with respect to EthFw software component. The EthFw component consists of firmware for Ethernet switch, profiling tools and demos/applications for J722S silicon platforms.

Licensing

Refer to Processor SDK RTOS top-level manifest.

Getting Started

The Ethernet Firmware User's Guide provides the documentation and references necessary to run EthFw demos and begin development on TI's platforms.

Documentation

Refer to following documentation for further details:

Ethernet Firmware User Guide	Build instructions, Demos	User Guide
Ethernet Firmware API Guide	API Guide	API Guide

Device Support

Below table shows device support for EthFw.

SoC	HOST (OS)	Target (OS)	Test Platform
J722S	Linux	FreeRTOS	J722S EVM

Refer Processor SDK RTOS release notes for SDK device support.

Validation Information

This release was built and validated using the following tools. Refer to the EthFw User's Guide for additional instructions to install and setup the dependencies.

Build Tools (included in Processor SDK)

TI ARM CLANG: 4.0.4.LTS
lwIP stack: 2.2.1
FreeRTOS Kernel: 11.1.0

Limitations

MAC Port 2 supports SGMII mode via MAC-to-MAC connectivity to another Jacinto device (e.g., J721E) through an Ethernet Expander Bridge, as J722S lacks integrated SGMII PHY support.

Dependencies

All Ethernet Firmware dependencies are also part of the SDK, please refer to the User's Guide for details.

Technical Support

For technical support and additional assistance, contact local TI Field Application Engineer

Package Versioning

Each package version is composed of 4 period-delimited numbers - represented here by the letters M, m, p and b [M.m.p.b]. The table below provides a descriptive reference regarding package version numbering.

Digit	Meaning	Description
1 (M=Major)	Major revision	Incremented when the new version is substantially different from the previous For example, a new module added or an existing module's algorithm significantly altered.
2 (m=minor)	Minor revision	Incremented when the new version has changed but not in a major way. For example, some minor changes in the API or feature set.
3 (p=patch)	Patch number	Incremented for all other source code changes. This include any packaging support code.
4 (b=build)	Build number	Incremented for each release delivery to CM. Reset for any change to M, m or p.