Ndk Interrupt Manager; Data Alignment - Texas Instruments TMS320C6000 Design Manual

1.4.4

NDK Interrupt Manager

1.4.5

Data Alignment

implementation is provided in NDK OS AL; this implementation might
need customization according to the application needs and system's
memory constraints.
The PBM object, its related API, and the Jumbo PBM API are described
in the TMS320C6000 Network Developer's Kit (NDK) Software
Programmer's Reference Guide (SPRU524). The TMS320C6000
Network Developer's Kit (NDK) Software User's Guide (SPRU523) also
includes a section on adapting the PBM to a particular included software.
The NDK Interrupt Manager is a module in the NDK OS AL that abstracts
out the OS (BIOS) specific APIs and data structures required for interrupt
configuration and management. It exposes a simple interface to the
driver writer to configure EMAC interrupts into the DSP core. Interrupt
Setup (IntSetup) Object is a data structure defined by this module.
Depending on the system specification, there can be a single or multiple
system event/interrupt numbers defined for the EMAC module's Transmit
(Tx) and Receive (Rx) events. Also based on the system specification,
one could register a single Interrupt Service Routine (ISR) for both Tx and
Rx events or register separate ISRs for each event.
The following NDK Interrupt Manager APIs can be used by the Ethernet
driver in setting up the interrupts:
❏ Interrupt_add
❏ Interrupt_delete
❏ Interrupt_enable
❏ Interrupt_disable
Please see the sample Ethernet driver code packaged as the NDK
Support Package (NSP) for any C64x+ device for an illustration of
interrupt configuration using NDK Interrupt Manager APIs. The NDK
Interrupt Manager, along with its related API and data structures, are
described in the TMS320C6000 Network Developer's Kit (NDK) Software
Programmer's Reference Guide (SPRU524).
The NDK libraries have been built with the assumption that the IP header
in a data packet is 16-bit aligned. In other words, the first byte of the IP
packet (the version/length field) must start on an even 16-bit boundary.
In any fixed-length header protocol, this requirement can be met by
Architecture Overview
Background
1-9