User guide

34 DC 900-1338I
Protocol Software Toolkit Programmer Guide
• A module containing the source-level debug monitor for the ICP2424
(
icp2424c.mem), ICP2432 (icp2432c.mem), or ICP6000 (icp6000c.mem), used only
with the Software Development Systems’ SingleStep debugger
In general, the toolkit programmer develops or modifies one or more application mod-
ules or tasks that run with Protogate’s system-services module. Application tasks can
run concurrently.
Modules are downloaded to the ICP as individual entities as described in Chapter 4.
They are not linked with one another. Any shared information must be made available
to a module when it is created (in other words, during compilation or assembly) or
must be obtained by the module at the time of execution. Modules designed to execute
in the OS/Impact environment access system services through the use of software traps
and, in general, communicate with other tasks through OS/Impact services, using pub-
lic task and queue IDs.
For these reasons, and because there are no provisions in the OS/Impact environment
for memory protection, it is essential to document the system resources required by a
module if it is to execute in combination with other modules. The following informa-
tion is provided for each module developed by Protogate and defined in the
*.spc files:
• Reserved areas of memory for code, data, and stack space
• Reserved exception vector table entries
• Dependencies on, or conflicts with, other modules
• Configuration requirements (number of tasks, priorities, queues, alarms,
resources, and partitions for the configuration table parameter list)
• Task initialization structures to be included in the configuration table
• Reserved task, queue, alarm, resource, and partition IDs (to avoid conflict with
user-added modules and as public information for intertask communication)