Runtime Integration - Revision history

Marku: /* Including the STRIDE Runtime */

2015-07-07T16:28:18Z

Including the STRIDE Runtime

← Older revision		Revision as of 16:28, 7 July 2015
Line 33:		Line 33:

	== Including the STRIDE Runtime ==		== Including the STRIDE Runtime ==
	The [[~~Runtime_Reference\|~~STRIDE Runtime]] is distributed in source form. The source files are included with each [[Framework_Setup#SDK\|SDK]] under "Runtime" directory. Files in that directories should be included in your target build.		The [[STRIDE Runtime]] is distributed in source form. The source files are included with each [[Framework_Setup#SDK\|SDK]] under "Runtime" directory. Files in that directories should be included in your target build.

	If you are using an S2-supplied SDK, additional required sources can be found in the SDK's <tt>src</tt> directory:		If you are using an S2-supplied SDK, additional required sources can be found in the SDK's <tt>src</tt> directory:

Marku: /* Overview */

2015-07-07T16:27:45Z

Overview

← Older revision		Revision as of 16:27, 7 July 2015
Line 7:		Line 7:
	* Incorporate the STRIDE Build Tools in your make process as a pre-compilation step		* Incorporate the STRIDE Build Tools in your make process as a pre-compilation step

	Here we incorporate the [[~~Runtime_Reference\|~~STRIDE Runtime]] in your target application build without tests. In the second and last step, we add the STRIDE [[Build Tools]] to the mix and hook up the test-running harnessing.		Here we incorporate the [[STRIDE Runtime]] in your target application build without tests. In the second and last step, we add the STRIDE [[Build Tools]] to the mix and hook up the test-running harnessing.

	After building the target with the STRIDE Runtime in place, we will run stride from a remote host computer to verify connectivity and runtime operation.		After building the target with the STRIDE Runtime in place, we will run stride from a remote host computer to verify connectivity and runtime operation.

Marku at 19:27, 11 November 2014

2014-11-11T19:27:56Z

← Older revision		Revision as of 19:27, 11 November 2014
Line 25:		Line 25:
	The [[Platform_Abstraction_Layer\|Platform Abstraction Layer (PAL)]] provides the glue between the STRIDE Runtime and services offered by your OS. It is the only piece of the runtime that is customized between operating systems.		The [[Platform_Abstraction_Layer\|Platform Abstraction Layer (PAL)]] provides the glue between the STRIDE Runtime and services offered by your OS. It is the only piece of the runtime that is customized between operating systems.

	Fully tested PALs are provided for Posix and Windows, included as <tt>palcfg.h</tt>, <tt>palIO.c</tt> and <tt>palOS.c</tt> in their respective [[~~:Category:SDKs~~\|~~SDKs~~]]~~. Other PALs are also available or under development. Please [http://www.s2technologies.com/contact.html contact S2] for availability~~.		Fully tested PALs are provided for Posix and Windows, included as <tt>palcfg.h</tt>, <tt>palIO.c</tt> and <tt>palOS.c</tt> in their respective [[Framework_Setup#SDK\|SDK]].

	== Configuring PAL I/O parameters ==		== Configuring PAL I/O parameters ==
Line 33:		Line 33:

	== Including the STRIDE Runtime ==		== Including the STRIDE Runtime ==
	The [[Runtime_Reference\|STRIDE Runtime]] is distributed in source form. The source files are included with each [[~~:Category:SDKs~~ \| ~~standard~~ SDK]] under "Runtime" directory. Files in that directories should be included in your target build.		The [[Runtime_Reference\|STRIDE Runtime]] is distributed in source form. The source files are included with each [[Framework_Setup#SDK\|SDK]] under "Runtime" directory. Files in that directories should be included in your target build.

	If you are using an S2-supplied SDK, additional required sources can be found in the SDK's <tt>src</tt> directory:		If you are using an S2-supplied SDK, additional required sources can be found in the SDK's <tt>src</tt> directory:
Line 80:		Line 80:
	Your target source must be edited to include code that initializes and uninitializes the runtime. The code is typically added to your <tt>main()</tt> function, but the only requirement is that the initialization takes place before the host computer connects and the uninitialization occurs before the process terminates.		Your target source must be edited to include code that initializes and uninitializes the runtime. The code is typically added to your <tt>main()</tt> function, but the only requirement is that the initialization takes place before the host computer connects and the uninitialization occurs before the process terminates.

	Please refer to the standard pre-packaged [[~~:Category:SDKs~~\|~~Platform SDKs~~]] for examples of a startup sequence. Briefly it should be something like:		Please refer to the standard pre-packaged [[Framework_Setup#SDK\|SDK]] for examples of a startup sequence. Briefly it should be something like:

	<source lang="c">		<source lang="c">
Line 178:		Line 178:
	==Testing the Runtime Integration==		==Testing the Runtime Integration==
	Once the instrumented target is successfully built, start the target application. On a separate host computer, connected to the target via TCP/IP (or serial port if so configured), run '''[[STRIDE_Runner\|stride]]''' as follows (substitute the <tt>--device</tt> option argument as needed):		Once the instrumented target is successfully built, start the target application. On a separate host computer, connected to the target via TCP/IP (or serial port if so configured), run '''[[STRIDE_Runner\|stride]]''' as follows (substitute the <tt>--device</tt> option argument as needed):
	~~<ref>If '''stride''' is not already installed, see [[Desktop Installation]].</ref>~~
	<source lang="bash">		<source lang="bash">
	stride --diagnostics --device=<device_address>		stride --diagnostics --device=<device_address>
Line 192:		Line 192:
	Disconnecting from device...		Disconnecting from device...
	</pre>		</pre>

	~~== Notes ==~~
	~~<references/>~~

	~~[[Category:Installation]]~~

Ivailop: /* C/C++ Feature Support */

2014-09-11T22:14:19Z

C/C++ Feature Support

← Older revision		Revision as of 22:14, 11 September 2014
Line 52:		Line 52:

	=== C/C++ Feature Support ===		=== C/C++ Feature Support ===
	By default the C source in the Runtime was written with the presumption that the target C compiler and C Runtime (CRT) library supports '''wchar_t''', '''long long''', '''long double''', ~~and~~ '''safe snprintf'''		By default the C source in the Runtime was written with the presumption that the target C compiler and C Runtime (CRT) library supports '''wchar_t''', '''long long''', '''long double''', '''safe snprintf''', and '''variadic macros'''

	By default the C++ source in the Runtime was written with the presumption that the target C++ compiler can handle '''namespaces'''.		By default the C++ source in the Runtime was written with the presumption that the target C++ compiler can handle '''namespaces''' and '''exceptions'''.

	If desired the user can specify different configuration by using '''-D''' compiler options:		If desired the user can specify different configuration by using '''-D''' compiler options:
Line 62:		Line 62:
	-DsrCRT_HAS_LONG_DBL=<0\|1>		-DsrCRT_HAS_LONG_DBL=<0\|1>
	-DsrCRT_HAS_SNPRINTF=<0\|1>		-DsrCRT_HAS_SNPRINTF=<0\|1>
			-DsrCRT_HAS_VA_ARGS=<0\|1>
	-DsrCPP_HAS_NAMESPACE=<0\|1>		-DsrCPP_HAS_NAMESPACE=<0\|1>
			-DsrCPP_HAS_EXCEPTION=<0\|1>

	where 0=disabled and 1=enabled.		where 0=disabled and 1=enabled.

Ivailop: /* Testing the Runtime Integration */

2014-06-05T20:14:52Z

Testing the Runtime Integration

← Older revision		Revision as of 20:14, 5 June 2014
Line 187:		Line 187:
	<pre>		<pre>
	Connecting to device...		Connecting to device...
	runtime version: 4.3.xx		runtime version: 5.x.yy
	Disconnecting from device...		Disconnecting from device...
	</pre>		</pre>

Ivailop: /* Including the STRIDE Runtime Sources */

2014-06-05T20:14:06Z

Including the STRIDE Runtime Sources

← Older revision		Revision as of 20:14, 5 June 2014
Line 32:		Line 32:
	Otherwise, refer to <tt>palcfg.h</tt> that comes with your PAL for a list of configuration parameters.		Otherwise, refer to <tt>palcfg.h</tt> that comes with your PAL for a list of configuration parameters.

	== Including the STRIDE Runtime ~~Sources~~ ==		== Including the STRIDE Runtime ==
	The [[Runtime_Reference\|STRIDE Runtime]] ~~sources are~~ distributed in source form. The source files are ~~available as a stand-alone package and are also~~ included with each ~~flavor of~~ [[:Category:SDKs\|SDK ~~package~~]].		The [[Runtime_Reference\|STRIDE Runtime]] is distributed in source form. The source files are included with each [[:Category:SDKs \| standard SDK]] under "Runtime" directory. Files in that directories should be included in your target build.

	~~The runtime sources are supplied in three directories:~~
	~~;Runtime~~
	~~: [[Runtime Reference\|STRIDE Runtime]]~~

	Files in ~~each of these~~ directories should be included in your target build.

	If you are using an S2-supplied SDK, additional required sources can be found in the SDK's <tt>src</tt> directory:		If you are using an S2-supplied SDK, additional required sources can be found in the SDK's <tt>src</tt> directory:
Line 48:		Line 42:
	** <tt>palOS.c</tt>		** <tt>palOS.c</tt>

	* Convenience functions (these wrap low-level ~~STRIDE runtime~~ calls)		* Convenience functions (these wrap low-level PAL/Runtime calls)
	** <tt>stride.c</tt>		** <tt>stride.c</tt>
	** <tt>stride.h</tt>		** <tt>stride.h</tt>

Ivailop: /* Including the STRIDE Runtime Sources */

2014-06-05T20:01:54Z

Including the STRIDE Runtime Sources

← Older revision		Revision as of 20:01, 5 June 2014
Line 38:		Line 38:
	;Runtime		;Runtime
	: [[Runtime Reference\|STRIDE Runtime]]		: [[Runtime Reference\|STRIDE Runtime]]
	~~;SLAP~~
	~~: [[SLAP\|Simplified Link-layer Application Protocol]]~~

	Files in each of these directories should be included in your target build.		Files in each of these directories should be included in your target build.

Ivailop: /* Including the STRIDE Runtime Sources */

2013-09-24T21:31:46Z

Including the STRIDE Runtime Sources

← Older revision		Revision as of 21:31, 24 September 2013
Line 36:		Line 36:

	The runtime sources are supplied in three directories:		The runtime sources are supplied in three directories:
	~~;GRS~~
	~~: [[GRS\|Generic RTOS Services]]~~
	;Runtime		;Runtime
	: [[Runtime Reference\|STRIDE Runtime]]		: [[Runtime Reference\|STRIDE Runtime]]

Ivailop: /* Testing the Runtime Integration */

2011-06-09T18:18:09Z

Testing the Runtime Integration

← Older revision		Revision as of 18:18, 9 June 2011
Line 197:		Line 197:
	<pre>		<pre>
	Connecting to device...		Connecting to device...
	runtime version: 4.2.xx		runtime version: 4.3.xx
	Disconnecting from device...		Disconnecting from device...
	</pre>		</pre>

Ivailop: /* Securing a PAL */

2011-06-09T17:01:21Z

Securing a PAL

← Older revision		Revision as of 17:01, 9 June 2011
Line 25:		Line 25:
	The [[Platform_Abstraction_Layer\|Platform Abstraction Layer (PAL)]] provides the glue between the STRIDE Runtime and services offered by your OS. It is the only piece of the runtime that is customized between operating systems.		The [[Platform_Abstraction_Layer\|Platform Abstraction Layer (PAL)]] provides the glue between the STRIDE Runtime and services offered by your OS. It is the only piece of the runtime that is customized between operating systems.

	Fully tested PALs are provided for ~~Linux~~ and Windows, included as <tt>palcfg.h</tt>, <tt>palIO.c</tt> and <tt>palOS.c</tt> in their respective [[:Category:SDKs\|SDKs]]. Other PALs are also available or under development. Please [http://www.s2technologies.com/contact.html contact S2] for availability.		Fully tested PALs are provided for Posix and Windows, included as <tt>palcfg.h</tt>, <tt>palIO.c</tt> and <tt>palOS.c</tt> in their respective [[:Category:SDKs\|SDKs]]. Other PALs are also available or under development. Please [http://www.s2technologies.com/contact.html contact S2] for availability.

	== Configuring PAL I/O parameters ==		== Configuring PAL I/O parameters ==