(Page 1 of 1 in this chapter) Version
Chapter 1
Introduction
- 1.1 Introduction
- 1.2 Development Environment
- 1.3 Loader API Overview
1.1 Introduction
- The TX Loader API Manual explains how to download executable images from the PC's hard disk to the TX board's memory.
1.2 Development Environment
- As Figure 1 illustrates, the host application development environment consists of API libraries that allow the application programmer to configure and control the protocol engines loaded on the TX board. This manual describes the Loader API. Refer to the appropriate API manual for further information on the other components illustrated here.
Figure 1. TX Series Development Environment
Note: Always use the compile option Structure Packing when compiling source code using these libraries and APIs.
1.3 Loader API Overview
- After a system reset, the TX boards are left in a reset state. The executable images must be downloaded from the PC's hard disk into the TX board's memory. This task is accomplished with the Loader API.
- Executables that are loaded to the TX boards consist of the NMS communications processor kernel (CPK), and various system and protocol tasks. The CPK must be the first executable loaded to the board; system and protocol tasks can follow.
Note: For PCI and CompactPCI-based TX boards (the TX 3220, TX 3220 C, and TX 3210) the kernel (CPK) is not downloaded to the board. For these board types the kernel image is located on FLASH memory (residing on the board). When one of these board types completes a reset (either at system boot time or any time the board is reset by an operator) the kernel is automatically loaded from FLASH into the board's dynamic memory. The kernel is fully booted before the TX board comes out of reset.
(Page 1 of 1 in this chapter) Version
tech_support@nmss.com
Copyright © 2000, Natural MicroSystems, Inc. All rights
reserved.