User`s guide

KwikNet System Construction

DAK

103

3. KwikNet System Construction

3.1 Building an Application

If you are using KwikNet with AMX or have ported KwikNet to your operating

environment, you are now ready to construct the

KwikNet Library and build an actual

KwikNet application. The sample program(s) provided with KwikNet and its optional

components are working examples which you can use either for guidance or as a starting

point for your own application.

To build a KwikNet application you must perform the following steps.

1. If none of the available KwikNet device drivers meet your needs, create a custom

device driver as described in the KwikNet Device Driver Technical Reference Manual.

2. If necessary, adapt the KwikNet board driver KN_BOARD.C to accommodate your target

processor, device interfaces and interrupt management scheme. The board driver is

also described in the KwikNet Device Driver Technical Reference Manual.

3. Using the KwikNet Configuration Builder, create and/or edit a Network Parameter File

to select the KwikNet features which your application requires and to describe your

network interfaces and their associated device drivers. On the Debug property page,

enable some or all of KwikNet's debug features to assist you during initial testing. Use

the builder to generate your KwikNet Library Make File.

4. Using the KwikNet Library Make File generated in step 3, create your KwikNet Library

following the procedure to be described in Chapter 3.2.

5. Finally, create a make file which your make utility can use to build your application.

It must compile your application modules, your KwikNet device drivers and your

KwikNet board driver. It can then link the resulting object modules with your KwikNet

Library, your RT/OS libraries and your C run-time library to create an executable

load module. Follow the compilation and linking recommendations presented in

Chapters 3.3, 3.4 and 3.5.

6. Use your software debugger and/or in-circuit emulator tools to transfer your load

module to your target hardware. When testing, you should execute your application

with a breakpoint on KwikNet procedure kn_bphit() so that you can readily detect

fatal configuration or programming errors or unusual operation of the

KwikNet TCP/IP

Stack. Follow the testing guidelines presented in Chapter 1.9.