KwikNet MPC5200 FEC Device Driver
K
A
DAK
1
KwikNet MPC5200 FEC Device Driver
1. Introduction
The Motorola PowerPC MPC5200 includes a single channel Fast Ethernet Controller
(FEC) that supports 10Mbps and 100Mbps data transfer rates. The FEC can operate only
in conjunction with the MPC5200 BestComm DMA Engine that provides DMA services
to a number of MPC5200 subsystems.
The BestComm engine is driven by its private tasks which execute from microcode
located in the MPC5200 static RAM memory. These tasks are not to be confused with
tasks managed by an RTOS such as KADAK's AMX kernel. Within this document, the
term task will be assumed to reference a BestComm task unless otherwise specified.
The BestComm API and microcode modules are supplied by Freescale Semiconductor,
Inc. You must refer to the following Freescale documents for guidance in the proper
setup and use of the BestComm DMA Engine.
MPC5200 User Manual
BestComm API User’s Guide
Application Notes 2251, 2604, 2609
Getting Started
The KwikNet MPC5200 FEC Ethernet Device Driver consists of a number of components
which collectively support a single Ethernet network interface managed by the KwikNet
TCP/IP Stack. These components must be compiled and the resulting object modules
must be merged into a library module which will be referred to as the KwikNet MPC5200
BestComm Library. The device driver can be used with KwikNet PPC32 (PN383-2) and
AMX PPC32 (PN382-1) or with the KwikNet Porting Kit (PN713-2).
To add the MPC5200 FEC device driver to your application, proceed as follows. Install
the driver in its own directory, separate from KwikNet, as described in Chapter 2.
The MPC5200 FEC device driver must be attached to a KwikNet network interface. The
network interface is defined as described in Chapter 3. The device driver is then attached
to the network interface as described in Chapter 4. The device driver parameters required
to configure the driver are specified in the data sheet provided in Appendix A.
Once you have defined the operating characteristics of the network interface and the
MPC5200 FEC device driver, you can build your KwikNet Library. You must build the
KwikNet Library prior to compiling the driver source modules. By building the KwikNet
Library first, you will ensure that all of the required KwikNet header files have been
collected together and are ready for your use.
The MPC5200 FEC device driver components must be compiled and the resulting object
modules must be merged into the KwikNet MPC5200 BestComm Library. Your
application is then compiled and linked with this library and the KwikNet Library as
described in Chapter 5.