Platform Abstraction Layer - Revision history

Ivailop: /* PAL Transport (I/O) Services */

2020-12-10T18:56:50Z

PAL Transport (I/O) Services

← Older revision		Revision as of 18:56, 10 December 2020
Line 156:		Line 156:
	The PAL Transport Services implement the target peer of the I/O services between the Host and Target. By convention, these services are implemented in a file called ''palIO.c''.		The PAL Transport Services implement the target peer of the I/O services between the Host and Target. By convention, these services are implemented in a file called ''palIO.c''.

	The pre-packaged PALs ~~below~~ provide both a Serial and a TCP/IP transport.		The pre-packaged PALs in the [[Posix SDK]] and [[Windows SDK]] provide both a Serial and a TCP/IP transport.

	;What about USB?: S2 does not yet provide a native USB transport. If you wish to use one of our prepackaged transports, then the USB can either be used to emulate a serial (COM) port, or can be used with TCP/IP by installing and using USBNet. USBNet is open software for Linux and Windows that permits TCP/IP connections over USB. Google "USBNet" to locate a driver for your systems.		;What about USB?: S2 does not yet provide a native USB transport. If you wish to use one of our prepackaged transports, then the USB can either be used to emulate a serial (COM) port, or can be used with TCP/IP by installing and using USBNet. USBNet is open software for Linux and Windows that permits TCP/IP connections over USB. Google "USBNet" to locate a driver for your systems.

Marku: /* Integrating the PAL */

2015-07-04T15:37:57Z

Integrating the PAL

← Older revision		Revision as of 15:37, 4 July 2015
Line 154:		Line 154:

	== PAL Transport (I/O) Services ==		== PAL Transport (I/O) Services ==
	The PAL Transport Services implement the target peer of the I/O services between the Host and Target. ~~Refer to [[STRIDE Studio]] and [[Stride Runner]] for host clients that connect and communicate with the target device~~.		The PAL Transport Services implement the target peer of the I/O services between the Host and Target. By convention, these services are implemented in a file called ''palIO.c''.

	~~Most of the~~ pre-packaged PALs below provide both a Serial and a TCP/IP transport.		The pre-packaged PALs below provide both a Serial and a TCP/IP transport.

	On the ~~Target side~~, ~~the Transport~~ is ~~usually implemented in file ''palIO~~.~~c''~~.		;What about USB?: S2 does not yet provide a native USB transport. If you wish to use one of our prepackaged transports, then the USB can either be used to emulate a serial (COM) port, or can be used with TCP/IP by installing and using USBNet. USBNet is open software for Linux and Windows that permits TCP/IP connections over USB. Google "USBNet" to locate a driver for your systems.

	;What about USB?: S2 does not yet provide a native USB transport. If you wish to use one of our prepackaged transports, then the USB can either be used to emulate a serial (COM) port, or can be used with TCP/IP by installing and using USBNet. USBNet is open software for Linux and Windows that permits TCP/IP connections over USB. Google "USBNet" to locate a driver for your systems.		;What if I need a custom transport?: A custom transport can be implemented. Your PAL implementation will need to implement the target side of the custom communication.
	;What if I need a custom transport?: A custom transport can be ~~readily written to your specific needs. Please [http://www.s2technologies.com/contact.html contact us] for assistance on creating a custom Host Transport~~. Your PAL implementation will need to implement the target side of the custom communication.

	== PAL Resource Requirements ==		== PAL Resource Requirements ==
Line 167:		Line 166:

	PAL memory usage is limited to a few dozen bytes for table and control block storage. The size of I/O buffers used by the reader task are Transport dependent but are usually in the 8KB range.		PAL memory usage is limited to a few dozen bytes for table and control block storage. The size of I/O buffers used by the reader task are Transport dependent but are usually in the 8KB range.

	~~== Using a Pre-Packaged PAL ==~~
	~~Current versions of STRIDE provides a [[:Category:SDKs\|set of Platform SDKs]] that package a ready to use PAL. Most contain support for both a serial and a TCP/IP transport.~~
	~~S2 can provide for other operating systems if necessary, please [http://www.s2technologies.com/contact.html contact us] for help in obtaining one.~~

	There is no "formal" mechanism required for initializing the PAL. That is, an initialization function is not required by the STRIDE Runtime or IM. In addition good practices require releasing resources on application exit. However, over time the convention of providing ''palInit()'' and ''palUninit()'' functions has developed. All of the Pre-Packaged PAL use this convention and their ''palInit()'' function must be called before any other STRIDE Runtime function and ''palUninit()'' on application shutdown.		There is no "formal" mechanism required for initializing the PAL. That is, an initialization function is not required by the STRIDE Runtime or IM. In addition good practices require releasing resources on application exit. However, over time the convention of providing ''palInit()'' and ''palUninit()'' functions has developed. All of the Pre-Packaged PAL use this convention and their ''palInit()'' function must be called before any other STRIDE Runtime function and ''palUninit()'' on application shutdown.

	~~== Creating your own PAL ==~~
	The PAL enables STRIDE to be completely agnostic to the underlying operating system and hardware. In fact, an operating system is not really required, so long as the PAL can provide the needed services. If there is no pre-packaged PAL for your system, you can use an existing one (part of any [[:Category:SDKs\|SDK package]]) as a starting point, or even write a new one from scratch. The PAL is designed to use standard concepts and services present in almost all operating systems and transport mechanisms. To complete a PAL, you’ll need to be familiar with concepts such as event signaling, scheduling, timers, critical section protection, memory allocation and data transfers. Past experience has shown that a PAL can usually be implemented in about two days.

	~~For more information on creating a custom PAL refer to [[Media:s2sPAL.pdf\|STRIDE Platform Abstraction Layer (PAL) Specification]].~~

	~~Please [http://www.s2technologies.com/contact.html contact us] for assistance on creating a custom Transport.~~

Marku at 15:28, 4 July 2015

2015-07-04T15:28:12Z

Show changes

Ivailop: /* PAL Operating System Services */

2010-05-16T01:34:21Z

PAL Operating System Services

← Older revision		Revision as of 01:34, 16 May 2010
Line 89:		Line 89:
	\|colspan="2" \| '''Timers'''		\|colspan="2" \| '''Timers'''
	\|-		\|-
	\| ~~palTimerCreate~~ \|\| Create a timer		\| palCreateTimer \|\| Create a timer
	\|-		\|-
	\| ~~palTimerDelete~~ \|\| Delete a timer		\| palDeleteTimer \|\| Delete a timer
	\|-		\|-
	\| ~~palTimerStart~~ \|\| Start a timer		\| palStartTimer \|\| Start a timer
	\|-		\|-
	\| ~~palTimerStop~~ \|\| Stop a timer		\| palStopTimer \|\| Stop a timer
	\|-		\|-
	\| palGetTime \|\| Return system time (e.g., tick count)		\| palGetTime \|\| Return system time (e.g., tick count)

Marku: /* Creating your own PAL */

2009-09-24T16:40:34Z

Creating your own PAL

← Older revision		Revision as of 16:40, 24 September 2009
Line 182:		Line 182:
	Please [http://www.s2technologies.com/contact.html contact us] for assistance on creating a custom Transport.		Please [http://www.s2technologies.com/contact.html contact us] for assistance on creating a custom Transport.


	~~[[Category:Deployment]]~~
	[[Category:Reference]]		[[Category:Reference]]

Ivailop: /* PAL Transport (I/O) Services */

2009-09-22T21:52:08Z

PAL Transport (I/O) Services

← Older revision		Revision as of 21:52, 22 September 2009
Line 162:		Line 162:

	;What about USB?: S2 does not yet provide a native USB transport. If you wish to use one of our prepackaged transports, then the USB can either be used to emulate a serial (COM) port, or can be used with TCP/IP by installing and using USBNet. USBNet is open software for Linux and Windows that permits TCP/IP connections over USB. Google "USBNet" to locate a driver for your systems.		;What about USB?: S2 does not yet provide a native USB transport. If you wish to use one of our prepackaged transports, then the USB can either be used to emulate a serial (COM) port, or can be used with TCP/IP by installing and using USBNet. USBNet is open software for Linux and Windows that permits TCP/IP connections over USB. Google "USBNet" to locate a driver for your systems.
	;What if I need a custom transport?: A custom transport can be readily written to your specific needs. Please ~~refer to~~ [~~[Target_Integration#The_Host_Transport\|Host Transport]~~] ~~section~~ for ~~more information~~ on creating custom Transport ~~DLLs for the host~~. Your PAL implementation will need to implement the target side of the custom communication.		;What if I need a custom transport?: A custom transport can be readily written to your specific needs. Please [http://www.s2technologies.com/contact.html contact us] for assistance on creating a custom Host Transport. Your PAL implementation will need to implement the target side of the custom communication.

	=== PAL Resource Requirements ===		=== PAL Resource Requirements ===

Ivailop: /* Creating your own PAL */

2009-09-22T21:51:10Z

Creating your own PAL

← Older revision		Revision as of 21:51, 22 September 2009
Line 176:		Line 176:

	=== Creating your own PAL ===		=== Creating your own PAL ===
	The PAL enables STRIDE to be completely agnostic to the underlying operating system and hardware. In fact, an operating system is not really required, so long as the PAL can provide the needed services. If there is no pre-packaged PAL for your system, you can use an existing one (part of any [[:Category:SDKs\|SDK package]]) as a starting point, or even write a new one from scratch. The PAL is designed to use standard concepts and services present in almost all operating systems and transport mechanisms. To complete a PAL, you’ll need to be familiar with concepts such as event signaling, scheduling, timers, critical section protection, memory allocation and data transfers. Past experience has shown that a PAL can usually be implemented in about two days.		The PAL enables STRIDE to be completely agnostic to the underlying operating system and hardware. In fact, an operating system is not really required, so long as the PAL can provide the needed services. If there is no pre-packaged PAL for your system, you can use an existing one (part of any [[:Category:SDKs\|SDK package]]) as a starting point, or even write a new one from scratch. The PAL is designed to use standard concepts and services present in almost all operating systems and transport mechanisms. To complete a PAL, you’ll need to be familiar with concepts such as event signaling, scheduling, timers, critical section protection, memory allocation and data transfers. Past experience has shown that a PAL can usually be implemented in about two days.

	For more information on creating a custom PAL refer to [[Media:s2sPAL.pdf\|STRIDE Platform Abstraction Layer (PAL) Specification]].		For more information on creating a custom PAL refer to [[Media:s2sPAL.pdf\|STRIDE Platform Abstraction Layer (PAL) Specification]].

	~~For more information~~ on creating a custom ~~Host~~ Transport ~~refer to [[Media:s2sTransport.pdf\|STRIDE Host Runtime Transport Specification]]~~.		Please [http://www.s2technologies.com/contact.html contact us] for assistance on creating a custom Transport.


	[[Category:Deployment]]		[[Category:Deployment]]
	[[Category:Reference]]		[[Category:Reference]]

Ivailop: /* PAL Transport (I/O) Services */

2009-09-22T21:42:29Z

PAL Transport (I/O) Services

← Older revision		Revision as of 21:42, 22 September 2009
Line 155:		Line 155:

	=== PAL Transport (I/O) Services ===		=== PAL Transport (I/O) Services ===
	The ~~[[Target_Integration#The_Host_Transport\|Host~~ Transport~~]] implements~~ the ~~host~~ peer of the I/O services between the Host and Target. Refer to [[STRIDE Studio]] and [[Stride Runner]] for host clients that connect and communicate with the target device.		The PAL Transport Services implement the target peer of the I/O services between the Host and Target. Refer to [[STRIDE Studio]] and [[Stride Runner]] for host clients that connect and communicate with the target device.

	Most of the pre-packaged PALs below provide both a ~~serial~~ and a TCP/IP transport.		Most of the pre-packaged PALs below provide both a Serial and a TCP/IP transport.

	On the Target side, the Transport is usually implemented in file ''palIO.c''.		On the Target side, the Transport is usually implemented in file ''palIO.c''.


	;What about USB?: S2 does not yet provide a native USB transport. If you wish to use one of our prepackaged transports, then the USB can either be used to emulate a serial (COM) port, or can be used with TCP/IP by installing and using USBNet. USBNet is open software for Linux and Windows that permits TCP/IP connections over USB. Google "USBNet" to locate a driver for your systems.		;What about USB?: S2 does not yet provide a native USB transport. If you wish to use one of our prepackaged transports, then the USB can either be used to emulate a serial (COM) port, or can be used with TCP/IP by installing and using USBNet. USBNet is open software for Linux and Windows that permits TCP/IP connections over USB. Google "USBNet" to locate a driver for your systems.

Ivailop: /* Overview */

2009-09-22T21:37:27Z

Overview

← Older revision		Revision as of 21:37, 22 September 2009
Line 6:		Line 6:
	The '''pal.h''' header file provided with the STRIDE Runtime contains all the function prototypes necessary for writing the PAL.		The '''pal.h''' header file provided with the STRIDE Runtime contains all the function prototypes necessary for writing the PAL.

	STRIDE provides fully functional implementations of the PAL for several major platforms. In addition, an empty PAL implementation template is provided to allow an early [[~~Integrating the STRIDE Runtime into a Target~~\|Target build integration]] until the actual one is complete. If you are interested in customizing the PAL for a target platform that is not already provided by S2, you may follow the examples provided in the prebuilt [[:Category:SDKs\|Platform SDK packages]].		STRIDE provides fully functional implementations of the PAL for several major platforms. In addition, an empty PAL implementation template is provided to allow an early [[Runtime_Integration\|Target build integration]] until the actual one is complete. If you are interested in customizing the PAL for a target platform that is not already provided by S2, you may follow the examples provided in the prebuilt [[:Category:SDKs\|Platform SDK packages]].

	For a detailed description of the PAL and its interfaces, see the '''[[Platform Abstraction Layer\|Platform Abstraction Layer]]''' description and the [[Media:s2sPAL.pdf\|STRIDE Platform Abstraction Layer (PAL) Specification]].		For a detailed description of the PAL and its interfaces, see the '''[[Platform Abstraction Layer\|Platform Abstraction Layer]]''' description and the [[Media:s2sPAL.pdf\|STRIDE Platform Abstraction Layer (PAL) Specification]].

Ivailop: /* Overview */

2009-06-17T06:18:17Z

Overview

← Older revision		Revision as of 06:18, 17 June 2009
Line 1:		Line 1:
	== Overview ==		== Overview ==
	The PAL, or Platform Abstraction Layer, enables the STRIDE Runtime to be platform-independent by providing 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.		The PAL, or Platform Abstraction Layer, enables the [[Runtime Reference\|STRIDE Runtime]] to be platform-independent by providing 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, provide the interfaces between your operating system and platform transport mechanism to the STRIDE Runtime. Through the PAL, the STRIDE Runtime becomes independent of any specific platform. The PAL is designed to use standard concepts and services present in almost all operating systems and transport mechanisms. To complete a PAL, you’ll need to be familiar with concepts such as event signaling, scheduling, timers, critical section protection, memory allocation and data transfers.		A small set of functions, written according to the PAL specification, provide the interfaces between your operating system and platform transport mechanism to the STRIDE Runtime. Through the PAL, the STRIDE Runtime becomes independent of any specific platform. The PAL is designed to use standard concepts and services present in almost all operating systems and transport mechanisms. To complete a PAL, you’ll need to be familiar with concepts such as event signaling, scheduling, timers, critical section protection, memory allocation and data transfers.