User`s guide

KwikNet System Construction
K
A
DAK
117
AMX Interrupt Stack
You may have to grow the size of your AMX Interrupt Stack, the stack used by all
Interrupt Service Procedures. The stack must be large enough to meet the needs of each
of the KwikNet device drivers which service your physical network connections. As a
good rule of thumb, choose a stack size which is approximately 500 bytes more than the
minimum required AMX Interrupt Stack size.
KwikNet Semaphores
KwikNet requires one semaphore for its operation. This semaphore will be created
dynamically by KwikNet during its initialization phase. You must include the AMX
Semaphore Manager in your AMX System Configuration Module by declaring a
requirement for at least one (1) semaphore. If you configure KwikNet to use standard C
for memory allocation with memory locking enabled, an additional semaphore will be
needed. If you use a file system other than AMX/FS and require file access locking,
allocate one more semaphore. Hence, the base requirement is for 1, 2 or 3 semaphores.
To the base requirement, you must add one semaphore for each application task that can
access KwikNet. For example, if your base requirement is 2 (one for KwikNet and one for
memory locking using standard C) and you have three tasks that concurrently use KwikNet
services, you must provide at least five semaphores for the KwikNet stack, over and above
any that you may require for your application.
KwikNet Memory Pool
If you configure KwikNet to use AMX memory management services, one AMX memory
pool will be required. The memory pool will be created dynamically by KwikNet during
its initialization phase. You must include the AMX Memory Manager in your AMX
System Configuration Module by declaring a requirement for at least one memory pool.
The memory for the pool must be allocated by you. Use the KwikNet Configuration
Builder to edit your Network Parameter File and select one of the memory assignment
techniques specified on the OS property page.
KwikNet Timer
KwikNet requires one AMX timer for its operation. This timer will be created
dynamically by
KwikNet during its initialization phase. You must include the AMX Timer
Manager in your AMX System Configuration Module by declaring a requirement for at
least one timer. Of course, to support timing you must also include an AMX Clock
Handler as part of your application.
The KwikNet timer operates at the network clock frequency defined by you in your
KwikNet Network Parameter File. The period of the network clock must correspond to an
integer multiple of AMX system ticks. For example, you may have a hardware clock
interrupt frequency of 1KHz with an AMX tick frequency of 100 Hz and a KwikNet
network frequency of 10 Hz. In this case, the KwikNet timer will operate at 100 ms
intervals measured with 10 ms resolution.