Build Integration - Revision history

Ivailop: /* Building the Target with STRIDE Diagnostics */

2015-09-08T19:53:35Z

Building the Target with STRIDE Diagnostics

← Older revision		Revision as of 19:53, 8 September 2015
Line 193:		Line 193:
	# Make appropriate changes to your target build process so that additional source files are included:		# Make appropriate changes to your target build process so that additional source files are included:
	#* <tt>strideIM.c(cpp)</tt> - generated IM code		#* <tt>strideIM.c(cpp)</tt> - generated IM code


	=== Running Diagnostics ===		=== Running Diagnostics ===

Ivailop: /* Running Diagnostics */

2015-09-08T19:29:31Z

Running Diagnostics

← Older revision		Revision as of 19:29, 8 September 2015
Line 203:		Line 203:
	Specify your database and device options as required.		Specify your database and device options as required.

	Upon running, the host console running stride will display summary test results:		Upon running, the host console running stride will display summary test results on the console:
	<pre>		<pre>
	Loading database...		Loading database...
Line 224:		Line 224:
	Disconnecting from device...		Disconnecting from device...
	Saving result file...		Saving result file...
			</pre>

	</~~pre~~>		Also a report '''diagnostics.xml''' is generated (this file is specified via the <tt>--output</tt> command line option). In addition a '''diagnostics.html''' is generated that could be open in a web browser of your choice.

Ivailop at 18:32, 17 July 2015

2015-07-17T18:32:59Z

← Older revision		Revision as of 18:32, 17 July 2015
Line 185:		Line 185:
	These tests are implemented in the files <tt>srdiag.h</tt> and <tt>srdiag.c</tt> included in the distribution Runtime directory. These tests provide a simple starting point, and will provide diagnostic information if the build isn't right.		These tests are implemented in the files <tt>srdiag.h</tt> and <tt>srdiag.c</tt> included in the distribution Runtime directory. These tests provide a simple starting point, and will provide diagnostic information if the build isn't right.
	# Include the STRIDE Runtime in your build as described in [[Runtime Integration]].		# Include the STRIDE Runtime in your build as described in [[Runtime Integration]].
	# Review the compiler target settings (typically in the file <tt>stride.s2compile</tt>) for correctness ~~(additional samples are [[Sample Stride Target Settings\|here]]~~. At a minimum, be sure that:		# Review the compiler target settings (typically in the file <tt>stride.s2compile</tt>) for correctness. At a minimum, be sure that:
	#* compatibility option is specified correctly, and		#* compatibility option is specified correctly, and
	#* the CPU endian-ness is specified correctly		#* the CPU endian-ness is specified correctly

Ivailop: /* Adding STRIDE Build Tools to Your Target Build */

2015-07-17T18:30:48Z

Adding STRIDE Build Tools to Your Target Build

← Older revision		Revision as of 18:30, 17 July 2015
Line 33:		Line 33:

	;<tt>--targ_*</tt>		;<tt>--targ_*</tt>
	: Sets datatype characteristics (size, alignment, etc.). ~~Some examples are shown in [[Sample Stride Target Settings \| Build Target settings examples]]~~		: Sets datatype characteristics (size, alignment, etc.).

	=== Build Tools Integration ===		=== Build Tools Integration ===

Marku at 19:03, 3 July 2015

2015-07-03T19:03:00Z

← Older revision		Revision as of 19:03, 3 July 2015
Line 3:		Line 3:

	== Adding STRIDE Build Tools to Your Target Build ==		== Adding STRIDE Build Tools to Your Target Build ==
	If you haven't already done so, download and install the appropriate [[~~Distribution_Files~~#~~Build_Tools~~\|~~Build Tools~~]] ~~package~~ on your target build machine. The [[Build Tools\|STRIDE Build Tools]] must be run as part of your build process to generate additional artifacts needed to build and run your tests.		If you haven't already done so, download and install the appropriate [[Framework_Setup#Packages \| package]] on your target build machine. The [[Build Tools\|STRIDE Build Tools]] must be run as part of your build process to generate additional artifacts needed to build and run your tests.

	=== Build Artifacts ===		=== Build Artifacts ===
Line 19:		Line 19:
	The collection of .h files that comprise the input to the Build Tools (specifically, the [[S2scompile\|s2scompile]] tool) will change as new test assets are created. It's important that the process of adding new test files to the target build is simple and straightforward. Therefore, a technique that supports this changing input is recommended.		The collection of .h files that comprise the input to the Build Tools (specifically, the [[S2scompile\|s2scompile]] tool) will change as new test assets are created. It's important that the process of adding new test files to the target build is simple and straightforward. Therefore, a technique that supports this changing input is recommended.

	The Makefile provided as part of the [[~~:Category:SDKs~~\|standard Platform SDKs]] uses such a technique: a directory is designated to contain all files to be input to the s2scompile tool.		The Makefile provided as part of the [[Framework_Setup#SDK\|standard Platform SDKs]] uses such a technique: a directory is designated to contain all files to be input to the s2scompile tool.

	===Compiler Settings===		===Compiler Settings===
Line 33:		Line 33:

	;<tt>--targ_*</tt>		;<tt>--targ_*</tt>
	: Sets datatype characteristics (size, alignment, etc.). Some examples are shown in [[Sample Stride Target Settings]]		: Sets datatype characteristics (size, alignment, etc.). Some examples are shown in [[Sample Stride Target Settings \| Build Target settings examples]]

	=== Build Tools Integration ===		=== Build Tools Integration ===
	The Makefile included with any [[~~:Category:SDKs~~\|standard Platform SDK]] can serve as an example of build tools make integration. Another stripped-down Makefile is shown below.		The Makefile included with any [[Framework_Setup#SDK\|standard Platform SDK]] can serve as an example of build tools make integration. Another stripped-down Makefile is shown below.

	'''Note''': If you copy and paste any content from this example into a makefile, be aware that you will probably need to replace leading spaces with tabs for any lines that specify rules (since make utilities typically require tab indentation for rules).		'''Note''': If you copy and paste any content from this example into a makefile, be aware that you will probably need to replace leading spaces with tabs for any lines that specify rules (since make utilities typically require tab indentation for rules).
Line 127:		Line 127:
	* Start the STRIDE IM thread.		* Start the STRIDE IM thread.

	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\|Platform SDKs]] for examples of a startup sequence. Briefly it should be something like:

	<source lang="c">		<source lang="c">

Marku: /* Building the Target with STRIDE Diagnostics */

2014-11-11T19:34:34Z

Building the Target with STRIDE Diagnostics

← Older revision		Revision as of 19:34, 11 November 2014
Line 195:		Line 195:


	[[~~Category:Installation~~]]		=== Running Diagnostics ===
			Start the target app running on the target hardware, then run [[Stride Runner\|stride]] as follows:
			<source lang="bash">
			stride --diagnostics --database=<path>/stride.sidb --device=<device_address> --run="*" --output=diagnostics
			</source>

			Specify your database and device options as required.

			Upon running, the host console running stride will display summary test results:
			<pre>
			Loading database...
			Connecting to device...
			runtime version: 5.x.yy
			Executing diagnostics...
			test unit "Link"
			Loopback ............
			Payload Fragmentation
			Stub-Proxy Deadlock
			Target Characteristics
			> 4 passed, 0 failed, 0 in progress, 0 not in use.
			test unit "Stat"
			> 2 passed, 0 failed, 0 in progress, 0 not in use.
			test unit "Time"
			> 2 passed, 0 failed, 0 in progress, 0 not in use.
			---------------------------------------------------------------------
			Summary: 8 passed, 0 failed, 0 in progress, 0 not in use.

			Disconnecting from device...
			Saving result file...

			</pre>

Ivailop: /* Example GNU Makefile */

2011-07-06T19:32:21Z

Example GNU Makefile

← Older revision		Revision as of 19:32, 6 July 2011
Line 52:		Line 52:
	# Set this to the directory that contains the		# Set this to the directory that contains the
	# STRIDE 'Runtime' files		# STRIDE 'Runtime' files
	RUNTIME_PATH = $(HOME)/SDK/Runtime		RUNTIME_PATH = $(HOME)/stride/SDK/Runtime

	BUILD_ROOT = .		BUILD_ROOT = .
Line 72:		Line 72:
	CFLAGS = $(INC_PATHS) $(DEFINES) --c		CFLAGS = $(INC_PATHS) $(DEFINES) --c

	COMPILER_OPTIONS_FILE = $(HOME)/SDK/Posix/settings/stride.s2compile		COMPILER_OPTIONS_FILE = $(HOME)/stride/SDK/Posix/settings/stride.s2compile

	METAS = $(foreach src, $(SCL_SRCS_H:.h=.h.meta), $(INT_PATH)/$(notdir $(src)))		METAS = $(foreach src, $(SCL_SRCS_H:.h=.h.meta), $(INT_PATH)/$(notdir $(src)))

Ivailop: /* Building the Target with STRIDE Diagnostics */

2011-06-16T18:09:17Z

Building the Target with STRIDE Diagnostics

← Older revision		Revision as of 18:09, 16 June 2011
Line 188:		Line 188:
	#* compatibility option is specified correctly, and		#* compatibility option is specified correctly, and
	#* the CPU endian-ness is specified correctly		#* the CPU endian-ness is specified correctly
	~~#:The STRIDE Diagnostics will detect other incorrect settings.~~
	# Make appropriate changes to your target build process so that the STRIDE build tools run as described.		# Make appropriate changes to your target build process so that the STRIDE build tools run as described.
	# Modify your target source so that the STRIDE IM thread is started (and is shutdown when your program terminates).		# Modify your target source so that the STRIDE IM thread is started (and is shutdown when your program terminates).

Ivailop: /* Building the Target with STRIDE Diagnostics */

2011-06-16T17:52:37Z

Building the Target with STRIDE Diagnostics

Ivailop: /* Building the Target with STRIDE Diagnostics */

2011-06-16T17:49:29Z

Building the Target with STRIDE Diagnostics

← Older revision		Revision as of 17:49, 16 June 2011
Line 183:		Line 183:
	==Building the Target with STRIDE Diagnostics==		==Building the Target with STRIDE Diagnostics==
	For a first-time instrumented target build, we recommend including the built-in diagnostic tests.		For a first-time instrumented target build, we recommend including the built-in diagnostic tests.
	These tests are implemented in the files srdiag.h and srdiag.c included in the distribution Runtime directory. These tests provide a simple starting point, and will provide diagnostic information if the build isn't right.		These tests are implemented in the files ''srdiag.h'' and ''srdiag.c'' included in the distribution Runtime directory. These tests provide a simple starting point, and will provide diagnostic information if the build isn't right.
	# Include the STRIDE Runtime in your build as described in [[Runtime Integration]].		# Include the STRIDE Runtime in your build as described in [[Runtime Integration]].
	# Review the compiler target settings (typically in the file stride.s2compile) for correctness (additional samples are [[Sample Stride Target Settings\|here]]. At a minimum, be sure that:		# Review the compiler target settings (typically in the file stride.s2compile) for correctness (additional samples are [[Sample Stride Target Settings\|here]]. At a minimum, be sure that:

← Older revision		Revision as of 17:52, 16 June 2011
Line 183:		Line 183:
	==Building the Target with STRIDE Diagnostics==		==Building the Target with STRIDE Diagnostics==
	For a first-time instrumented target build, we recommend including the built-in diagnostic tests.		For a first-time instrumented target build, we recommend including the built-in diagnostic tests.
	These tests are implemented in the files ''srdiag.h'' and ''srdiag.c'' included in the distribution Runtime directory. These tests provide a simple starting point, and will provide diagnostic information if the build isn't right.		These tests are implemented in the files <tt>srdiag.h</tt> and <tt>srdiag.c</tt> included in the distribution Runtime directory. These tests provide a simple starting point, and will provide diagnostic information if the build isn't right.
	# Include the STRIDE Runtime in your build as described in [[Runtime Integration]].		# Include the STRIDE Runtime in your build as described in [[Runtime Integration]].
	# Review the compiler target settings (typically in the file stride.s2compile) for correctness (additional samples are [[Sample Stride Target Settings\|here]]. At a minimum, be sure that:		# Review the compiler target settings (typically in the file <tt>stride.s2compile</tt>) for correctness (additional samples are [[Sample Stride Target Settings\|here]]. At a minimum, be sure that:
	#* compatibility option is specified correctly, and		#* compatibility option is specified correctly, and
	#* the CPU endian-ness is specified correctly		#* the CPU endian-ness is specified correctly
Line 191:		Line 191:
	# Make appropriate changes to your target build process so that the STRIDE build tools run as described.		# Make appropriate changes to your target build process so that the STRIDE build tools run as described.
	# Modify your target source so that the STRIDE IM thread is started (and is shutdown when your program terminates).		# Modify your target source so that the STRIDE IM thread is started (and is shutdown when your program terminates).
	# Provide '''srdiag.h''' as an input to the STRIDE build tools. (If using the example Makefile above, you would add the file to the SCL_SRCS_H list.)		# Provide '''<tt>srdiag.h</tt>''' as an input to the STRIDE build tools. (If using the example Makefile above, you would add the file to the <tt>SCL_SRCS_H</tt> list.)
	# Make appropriate changes to your target build process so that additional source files are included:		# Make appropriate changes to your target build process so that additional source files are included:
	#* strideIM.c(cpp) - generated IM code		#* <tt>strideIM.c(cpp)</tt> - generated IM code


	[[Category:Installation]]		[[Category:Installation]]