Please note as of Wednesday, August 15th, 2018 this wiki has been set to read only. If you are a TI Employee and require Edit ability please contact x0211426 from the company directory.
Processor SDK RTOS ICSS-EMAC FIRMWARES
Starting in v4.3, Processor SDK documentation is no longer hosted on processors wiki.
Please bookmark the new links:
- Linux, RT-Linux: http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/index.html
- RTOS: http://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index.html
- Android: http://software-dl.ti.com/processor-sdk-android/esd/docs/latest/android/index.html
|RTOS Software Developer Guide||→||ICSS-EMAC_FIRMWARES|
The ICSS FIRMWARES serves as example to implement various network functionalities. Package includes source release for Dual_emac and basic switch firmwares.
ICSS DUAL EMAC FIRMWARE is a single port Ethernet MAC (Media Access Control) i.e. Layer 2 of OSI Model. It implements a 2 port ethernet mac supporting 10/100 Mbps. DUAL EMAC FIRMWARE is standardized to IEEE 802.1 Ethernet Standards. Primary use case of the protocol is to demonstrate basic ethernet functionality via both PRU cores on 10/100 Mbit Ethernet cable. ICSS DUAL EMAC FIRMWARE can be used independently on two PRU's to implement two independent MAC's with two different MAC addresses and two different IP addresses. To provide an analogy, this is somewhat similar to a two port Ethernet PCIe NIC card on a PC.Ethernet interface in this case is available along with Host processor on a single SoC. Following are high level features:
|1 ms buffering per port||Supported|
|Ethernet QoS||With 2 queues instead of 8. So, it is not a standard Ethernet QoS implementation.|
|TTS (Time Triggered Send)||Supported|
ICSS SWITCH FIRMWARE is a three port learning Ethernet switch i.e. Layer 2 of OSI Model. It implements a 2 port cut through ethernet switch supporting at 100 Mbps. SWITCH FIRMWARE is standardized to IEEE 802.1 Ethernet Standards. The primary use case of the protocol is to use Ethernet to automate applications which require short cut-through latency and low hardware costs. ICSS SWITCH FIRMWARE uses two PRU to implement three port Ethernet switch with one single MAC and IP address. To provide an analogy, this is somewhat standard network switch only here the network functionality is available to the host core within the single SOC. The following are the high level features it supports.
|Store and Forward||Supported|
|1 ms buffering per port||Supported|
|Ethernet QoS||With 4 queues instead of 8. So, it is not a standard Ethernet QoS implementation.|
|802.1 learning switch||Supported|
|Queue-Contention Handling on each port||Supported|
|Common baseline code||<PDK>/packages/ti/drv/icss_emac/firmware/icss_dualemac||common code for dual_emac and switch|
|DUAL_EMAC||<PDK>/packages/ti/drv/icss_emac/firmware/icss_dualemac||dual_emac firmware specific code|
|SWITCH||<PDK>/packages/ti/drv/icss_emac/firmware/icss_switch||switch firmware specific code|
Firmware Build Instruction
Build instruction from Processor SDK Release package
Pre-requisites to Building
Refer to the Processor SDK RTOS Building page for information on setting up build environment.
Compiling ICSS-EMAC FIRMWARES
- cd <PDK>/packages/ti/drv/icss_emac
- make firm
Firmware binaries at the end of the build will be located at:
- <FIRMWARE_TYPE> indicates the firmware type i.e. icss_dualemac for DUAL_EMAC or icss_switch for SWITCH
- <SOC> indicates the SOC type.
- <HOST_CORE> indicates the Host core type on which the built binary can be loaded.
- <REVISION> indicates the revision of the firmware binary based on core. (There are 2 revision of PRU ICSS core)
Build instruction from GIT
Following are the steps for building firmware from any external environment outside PROC SDK RTOS.
- Creation of directories
- Create a working directory e.g. <WORK_DIR>
- Create a new directory named ti inside working directory. i.e. <WORK_DIR/ti>
- Create a new directory called drv inside ti. i.e. <WORK_DIR/ti/drv>
- Clone of Repos
- Git clone pdk build repo into ti directory. i.e. <WORK_DIR/ti/build>
- Git clone icss_emac repo into ti/drv directory. i.e. <WORK_DIR/ti/drv/icss_emac>
- Setting Environment Variables
- Export CLPRU install path. i.e. export CL_PRU_INSTALL_PATH=clpru toolchain directory
- Export pdk install path. i.e. export PDK_INSTALL_PATH=<WORK_DIR>
- Export LIMIT_SOCS Variable i.e. LIMIT_SOCS=<SOC> [Optional for limiting to some SOCs]
- Build command
- Run make firm/firm_clean to build/clean firmware from icss_emac directory i.e. <WORK_DIR/ti/drv/icss_emac>
- Generated binaries
- the firmware binaries which will be located in <WORK_DIR/ti/drv/icss_emac/firmware/<FIRMWARE_TYPE>/bin/<SOC>/<HOST_CORE>/<REVISION>>
The following is a list of EVMS supported and the PRU-ICSS ethernet ports to be used:
|EVM Name||PRU-ICSS Instance||Supported PRU ICSS core revision|
|icev2AM335x||PRU-ICSS instance 1||REV1|
|idkAM437x||PRU-ICSS instance 2||REV1|
|idkAM571x||PRU-ICSS instance 2||REV2|
|idkAM572x||PRU-ICSS instance 2||REV1 & REV2 (Earlier version of AM572x soc had REV1 pru cores while later had REV2 pru cores)|
|iceK2G||PRU-ICSS instance 2||REV2|
Running ICSS-EMAC FIRMWARES Example
Please go through the following page for example demonstrating the use of the firmware via icss-emac driver. 
Firmware Design Guide
|ICSS DUAL EMAC FIRMWARE Design Guide||<PDK>/packages/ti/drv/icss_emac/firmware/icss_dualemac/docs/ICSS_DUAL_EMAC_Firmware_Design_Guide.pdf|
|ICSS SWITCH FIRMWARE Design Guide||<PDK>/packages/ti/drv/icss_emac/firmware/icss_switch/docs/ICSS_SWITCH_Firmware_Design_Guide.pdf|
NOTE: For normal use case, there is no need to refer this document. Unless you wish to go through the internal working for firmware and/or wanted to modify it.