STRIDE Runtime
Overview
The Runtime Developer's Guide
Click [here] to view the STRIDE Runtime Developer's Guide PDF document.
The Platform Abstraction Layer Specification
The PAL defines the set of OS functionality required by the platform to support the
STRIDE Runtime. The pal.h header file defines the PAL functionality. The PAL also
defines functionality required by the STRIDE Runtime to transmit and receive packets of
data (called I-blocks) using the platform’s transport mechanism. These PAL routines
enable the STRIDE Runtime to be installed on diverse environments without changing its
internal design.
Click [here] to view the STRIDE Platform Abstraction Layer (PAL) Specification PDF document.
OR
The PAL, or Platform Abstraction Layer, provides a consistent interface for the STRIDE Runtime regardless of the operating system or data transport used. This interface layer is necessary given the broad variety of operating systems and data transports that exist within embedded systems today.
A small set of functions, written according to the PAL specification, provides a virtual link between your operating system and platform transport mechanism to the STRIDE Runtime. Through the Platform Abstraction Layer, the STRIDE Runtime becomes independent of any specific operating system or transport. The PAL is designed to use standard concepts and services present in almost all operating systems and transport mechanisms. To complete the PAL, you’ll need to be familiar with concepts such as event signaling, scheduling, timers, critical section protection, memory allocation and data transfers, all of which are described in detail in the STRIDE Platform Abstraction Layer Specification .
The “pal.h” header file provided with the STRIDE installation contains all the function prototypes necessary for writing the PAL. The pal.h header file is provided [here] in the STRIDE Platform Abstraction Layer Specification.
The Host Transport Specification
Click [here] to view the STRIDE Host Runtime Transport Specification PDF document.
The Transport Server Object Model
Follow this link for a discussion of the Transport Server Object Model.