TAAD08JU2 Datasheet, PDF (31/174 Pages) Agere Systems – T1/E1/J1 ATM Processor, Versions 2.1 and 3.1

Data Sheet
August 18, 2003
TAAD08JU2
T1/E1/J1 ATM Processor, Versions 2.1 and 3.1
9 Software Components (continued)
The user is encouraged to use the setup file utility to generate the sequence of setup commands and store them in
a setup file. The setup utility allows the user to choose the mode information by simply clicking on the GUI to select
options. It ensures that the user selects a valid combination of options by providing appropriate error messages
and, where possible, by restricting the available options to the appropriate ones. This methodology brings the great
advantage that the firmware is freed from having to perform error checking on all the provisioning parameters,
which reduces the embedded code size. In addition, the GUI handles the translation of provisioning parameters
into per-block provisioning parameters, also reducing the complexity of the initialization code.
Once the host via device manager has downloaded the setup file to TAAD08JU2, the provisioning of the device is
complete. The TAAD08JU2 waits for the next command from the host or provides an indication to the host if an
interrupt occurs or an alarm goes off.
See the TAAD08JU2 setup file utility software for more details on using this utility.
9.4 TAAD08JU2 Application Code
The TAAD08JU2 application code performs the actual initialization, configuration, control, and monitoring of
TAAD08JU2 through device manager API function calls (configuration that is done by the NSFU can also be
accomplished via the application code). This software is written by users to implement TAAD08JU2 in their system.
The device manager is not an autonomous program. It is only an interpreter between the user's application code
and TAAD08JU2. It is up to the application code to instruct device manager to initialize TAAD08JU2, download the
firmware, download the setup file, add connections, monitor alarms and statistics, etc. Therefore, the programmer
of TAAD08JU2 should be very familiar with all of the API functions and data types listed in the TAAD08JU2 device
manager API document.
The following application pseudocode demonstrates control of TAAD08JU2 using device manager API calls:
/* Reset the TAAD08JU2 chip - board specific */
lapiInitialize(..); /* Initialize DevMan */
/* User must allocate all memory used by DevMan *.
npGetNewportDeviceMemoryRequirement(..);
pDev1Handle = malloc(MemoryRequired);
lapiInitializeDevice(pDev1Handle, ..);
npLoadFirmware(..); /* download the 2 ARM firmware binary files */
lapiSetupDevice(..); /* Download NSFU file */
/* Now add connections, monitor stats, etc. etc. */
npAddConnection(..);
...
...
...
/* When all done, shutdown TAAD08JU2 and DevMan */
lapiFinalizeDevice(..);
/* Users must free memory they allocated for Device Manager */
free(pDev1Handle);
lapiFinalize();
Complete example applications illustrating the proper use of device manager API functions are provided in the
TAAD08JU2 software release documentation.
Agere Systems Inc.
Agere Systems - Proprietary
31