Off-Target Environment - Revision history

Marku: Redirected page to STRIDE Off-Target Environment

2011-06-09T18:15:08Z

Redirected page to STRIDE Off-Target Environment

← Older revision		Revision as of 18:15, 9 June 2011
Line 1:		Line 1:
	~~== Overview ==~~		#REDIRECT [[STRIDE Off-Target Environment]]
	~~[[image:STRIDE_Desktop.jpg\|right\|The Off-Target configuration puts both host and target code on the desktop]]~~
	Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a '''host-only''' ''Off-Target Configuration'' that emulates your target system. All of the supplied [[Samples \| samples]] run identically under either the Off-Target environment or your actual target. In addition, any test code you write will also run in either environment. This enables the user to create their own '''sandbox''' for training and Off-Target unit testing.

	~~The Off-Target Environment utilizes the [[Desktop_Installation~~#~~SDK\|Framework's "SDK"]] that can be built and executed on the host system. The~~ [[STRIDE Runner]] application executes on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.

	~~== Prerequisites ==~~
	To simplify training, we recommend using a single Windows or Linux (x86) computer for both the target and host systems. Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment~~'' are directly transferable to a production environment.~~

	~~Please complete and verify the following prerequisites:~~
	~~# [[Desktop Installation \| Desktop Installation]]~~
	# Host system development '''toolchain''' installation. For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free [http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used (download [http://www.microsoft.com/express/download/#webInstall here]). For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all Linux distros) is required.
	~~# Build a [[Off-Target_Test_App \| TestApp]] and successfully execute [[Off-Target_Test_App#Diagnostics \| built-in diagnostics]].~~

	~~[[Category:Installation~~]]

Marku: /* Prerequisites */

2011-01-04T23:06:20Z

Prerequisites

← Older revision		Revision as of 23:06, 4 January 2011
Line 11:		Line 11:
	# [[Desktop Installation \| Desktop Installation]]		# [[Desktop Installation \| Desktop Installation]]
	# Host system development '''toolchain''' installation. For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free [http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used (download [http://www.microsoft.com/express/download/#webInstall here]). For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all Linux distros) is required.		# Host system development '''toolchain''' installation. For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free [http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used (download [http://www.microsoft.com/express/download/#webInstall here]). For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all Linux distros) is required.
	# Build a [[Off-Target_Test_App \| TestApp]] and ~~successful~~ execute [[Off-Target_Test_App#Diagnostics \| built-in diagnostics]].		# Build a [[Off-Target_Test_App \| TestApp]] and successfully execute [[Off-Target_Test_App#Diagnostics \| built-in diagnostics]].

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

Ivailop: /* Prerequisites */

2010-11-01T17:23:14Z

Prerequisites

← Older revision		Revision as of 17:23, 1 November 2010
Line 10:		Line 10:
	Please complete and verify the following prerequisites:		Please complete and verify the following prerequisites:
	# [[Desktop Installation \| Desktop Installation]]		# [[Desktop Installation \| Desktop Installation]]
	# Host system development '''toolchain''' installation. For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free [http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used~~. Download~~ [http://www.microsoft.com/express/download/#webInstall here]. For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all Linux distros) is required.		# Host system development '''toolchain''' installation. For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free [http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used (download [http://www.microsoft.com/express/download/#webInstall here]). For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all Linux distros) is required.
	# Build a [[Off-Target_Test_App \| TestApp]] and successful execute [[Off-Target_Test_App#Diagnostics \| built-in diagnostics]].		# Build a [[Off-Target_Test_App \| TestApp]] and successful execute [[Off-Target_Test_App#Diagnostics \| built-in diagnostics]].

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

Marku: /* Evaluation Steps */

2010-08-23T15:55:51Z

Evaluation Steps

← Older revision		Revision as of 15:55, 23 August 2010
Line 5:		Line 5:
	The Off-Target Environment utilizes the [[Desktop_Installation#SDK\|Framework's "SDK"]] that can be built and executed on the host system. The [[STRIDE Runner]] application executes on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.		The Off-Target Environment utilizes the [[Desktop_Installation#SDK\|Framework's "SDK"]] that can be built and executed on the host system. The [[STRIDE Runner]] application executes on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.

	== ~~Evaluation Steps~~ ==		== Prerequisites ==
	To simplify ~~the evaluation~~, we recommend using a single Windows or Linux (x86) computer for both the target and host systems. Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment'' are directly transferable to a production environment.		To simplify training, we recommend using a single Windows or Linux (x86) computer for both the target and host systems. Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment'' are directly transferable to a production environment.

	~~The recommended evaluation steps are as follows:~~
	~~# Review the [[STRIDE Overview]]~~
	~~# Install required [[Desktop Installation \| desktop Framework package]]~~
	~~# Configure [[Test_Space_Setup\|STRIDE Test Space]] for publishing results~~
	~~# [[Off-Target_Test_App\|Build the basic TestApp]] with built-in S2 diagnostic tests~~
	~~# [[Running and Publishing the TestIntro Sample\|Build and test the TestApp with ''Unit Tests'' examples]].~~
	~~# [[Running and Publishing the Expectations Sample\|Build and test the TestApp with the ''Behavior (Expectations) Tests'' examples]], publishing results to Test Space~~
	~~# Explore other [[Samples]]~~

			Please complete and verify the following prerequisites:
			# [[Desktop Installation \| Desktop Installation]]
			# Host system development '''toolchain''' installation. For Windows Microsoft Visual Studio 2005 or later is required. If you don't already have Visual Studio, the free [http://en.wikipedia.org/wiki/Microsoft_Visual_Studio_Express Visual C++ Express] can be used. Download [http://www.microsoft.com/express/download/#webInstall here]. For Linux the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all Linux distros) is required.
			# Build a [[Off-Target_Test_App \| TestApp]] and successful execute [[Off-Target_Test_App#Diagnostics \| built-in diagnostics]].

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

Marku: /* Overview */

2010-08-23T15:21:58Z

Overview

← Older revision		Revision as of 15:21, 23 August 2010
Line 1:		Line 1:
	== Overview ==		== Overview ==
	[[image:STRIDE_Desktop.jpg\|right\|The Off-Target configuration puts both host and target code on the desktop]]		[[image:STRIDE_Desktop.jpg\|right\|The Off-Target configuration puts both host and target code on the desktop]]
	Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a host-only ''Off-Target Configuration'' that emulates your target system ~~for purposes of evaluation and training~~. All of the supplied samples ~~and test code~~ run identically under either the Off-Target environment or your actual target. In addition, any test code you write will also run in either environment. This enables the user to create their own '''sandbox''' for ~~evaluation,~~ training, and unit testing.		Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a '''host-only''' ''Off-Target Configuration'' that emulates your target system. All of the supplied [[Samples \| samples]] run identically under either the Off-Target environment or your actual target. In addition, any test code you write will also run in either environment. This enables the user to create their own '''sandbox''' for training and Off-Target unit testing.

	The Off-~~target~~ utilizes the [[Desktop_Installation#SDK\|Framework's "SDK"]] that can be built and executed on the host system. The ~~test runner~~ application ~~runs~~ on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.		The Off-Target Environment utilizes the [[Desktop_Installation#SDK\|Framework's "SDK"]] that can be built and executed on the host system. The [[STRIDE Runner]] application executes on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.

	== Evaluation Steps ==		== Evaluation Steps ==

Marku: /* Evaluation Steps */

2010-06-02T16:29:56Z

Evaluation Steps

← Older revision		Revision as of 16:29, 2 June 2010
Line 6:		Line 6:

	== Evaluation Steps ==		== Evaluation Steps ==
	To simplify the evaluation, we recommend using a single Windows or Linux (x86) computer for both the target and host systems. Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ~~sandbox evaluation and training~~ are directly transferable to a production environment.		To simplify the evaluation, we recommend using a single Windows or Linux (x86) computer for both the target and host systems. Host and target code will run in separate processes and communicate via TCP/IP, thus simulating an embedded target with host computer configuration. All code and techniques used in the ''Off-Target Environment'' are directly transferable to a production environment.

	The recommended evaluation steps are as follows:		The recommended evaluation steps are as follows:
	# Review the [[STRIDE Overview]]		# Review the [[STRIDE Overview]]
	# Install required [[Desktop Installation \| Framework]]		# Install required [[Desktop Installation \| desktop Framework package]]
	# Configure [[Test_Space_Setup\|STRIDE Test Space]] for publishing results		# Configure [[Test_Space_Setup\|STRIDE Test Space]] for publishing results
	# [[Off-Target_Test_App\|Build the basic TestApp]] with built-in S2 diagnostic tests		# [[Off-Target_Test_App\|Build the basic TestApp]] with built-in S2 diagnostic tests
	# [[Running and Publishing the ~~Expectations~~ Sample\|Build and test the TestApp with ~~the Expectations sample~~]]~~, publishing results to Test Space~~		# [[Running and Publishing the TestIntro Sample\|Build and test the TestApp with ''Unit Tests'' examples]].
	# ~~If you are interested in learning about tests in native C/C++, you can also~~ [[Running and Publishing the ~~TestIntro~~ Sample\|~~build~~ and test the TestApp with the ~~TestIntro sample~~]].		# [[Running and Publishing the Expectations Sample\|Build and test the TestApp with the ''Behavior (Expectations) Tests'' examples]], publishing results to Test Space
	# Explore other [[Samples~~\|sample tests~~]]		# Explore other [[Samples]]


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

Ivailop at 21:57, 17 May 2010

2010-05-17T21:57:13Z

← Older revision		Revision as of 21:57, 17 May 2010
Line 18:		Line 18:


	[[Category:~~The Sandbox~~]]		[[Category:Installation]]

Ivailop: /* Overview */

2010-05-17T21:49:39Z

Overview

← Older revision		Revision as of 21:49, 17 May 2010
Line 3:		Line 3:
	Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a host-only ''Off-Target Configuration'' that emulates your target system for purposes of evaluation and training. All of the supplied samples and test code run identically under either the Off-Target environment or your actual target. In addition, any test code you write will also run in either environment. This enables the user to create their own '''sandbox''' for evaluation, training, and unit testing.		Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a host-only ''Off-Target Configuration'' that emulates your target system for purposes of evaluation and training. All of the supplied samples and test code run identically under either the Off-Target environment or your actual target. In addition, any test code you write will also run in either environment. This enables the user to create their own '''sandbox''' for evaluation, training, and unit testing.

	The Off-target utilizes the Framework's "SDK" that can be built and executed on the host system. The test runner application runs on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.		The Off-target utilizes the [[Desktop_Installation#SDK\|Framework's "SDK"]] that can be built and executed on the host system. The test runner application runs on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.

	== Evaluation Steps ==		== Evaluation Steps ==

Ivailop: /* Overview */

2010-05-17T21:48:05Z

Overview

← Older revision		Revision as of 21:48, 17 May 2010
Line 1:		Line 1:
	== Overview ==		== Overview ==
	[[image:~~STRIDE_Sandbox_Configuration~~.jpg\|right\|The ~~sandbox~~ configuration puts both host and target code on the ~~host PC~~]]		[[image:STRIDE_Desktop.jpg\|right\|The Off-Target configuration puts both host and target code on the desktop]]
	Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a host-only ''~~sandbox~~'' that emulates your target system for purposes of evaluation and training. All of the supplied samples and test code run identically under either the ~~sandbox~~ environment or your actual target. In addition, any test code you write will also run in either environment.		Two of the largest barriers to embedded developer productivity are long build/test cycles and scarce target hardware. Fortunately, STRIDE's cross-platform capabilities make it possible to run STRIDE in a host-only ''Off-Target Configuration'' that emulates your target system for purposes of evaluation and training. All of the supplied samples and test code run identically under either the Off-Target environment or your actual target. In addition, any test code you write will also run in either environment. This enables the user to create their own '''sandbox''' for evaluation, training, and unit testing.

	The ~~sandbox~~ utilizes a "~~target~~" ~~application~~ that is built and ~~runs~~ on the host system. The test runner application runs on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for rapid build/~~run cycles~~.		The Off-target utilizes the Framework's "SDK" that can be built and executed on the host system. The test runner application runs on the same system and communicates with the "target" process over a TCP/IP connection. This set up frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.

	== Evaluation Steps ==		== Evaluation Steps ==

Ivailop: /* Evaluation Steps */

2010-05-16T01:37:28Z

Evaluation Steps

← Older revision		Revision as of 01:37, 16 May 2010
Line 11:		Line 11:
	# Review the [[STRIDE Overview]]		# Review the [[STRIDE Overview]]
	# Install required [[Desktop Installation \| Framework]]		# Install required [[Desktop Installation \| Framework]]
	# Configure [[STRIDE Test Space]] for publishing results		# Configure [[Test_Space_Setup\|STRIDE Test Space]] for publishing results
	# [[ Off-Target_Test_App\|Build the basic TestApp]] with built-in S2 diagnostic tests		# [[Off-Target_Test_App\|Build the basic TestApp]] with built-in S2 diagnostic tests
	# [[Running and Publishing the Expectations Sample\|Build and test the TestApp with the Expectations sample]], publishing results to Test Space		# [[Running and Publishing the Expectations Sample\|Build and test the TestApp with the Expectations sample]], publishing results to Test Space
	# If you are interested in learning about tests in native C/C++, you can also [[Running and Publishing the TestIntro Sample\|build and test the TestApp with the TestIntro sample]].		# If you are interested in learning about tests in native C/C++, you can also [[Running and Publishing the TestIntro Sample\|build and test the TestApp with the TestIntro sample]].

← Older revision		Revision as of 01:37, 16 May 2010
Line 11:		Line 11:
	# Review the [[STRIDE Overview]]		# Review the [[STRIDE Overview]]
	# Install required [[Desktop Installation \| Framework]]		# Install required [[Desktop Installation \| Framework]]
	# Configure [[STRIDE Test Space]] for publishing results		# Configure [[Test_Space_Setup\|STRIDE Test Space]] for publishing results
	# [[ Off-Target_Test_App\|Build the basic TestApp]] with built-in S2 diagnostic tests		# [[Off-Target_Test_App\|Build the basic TestApp]] with built-in S2 diagnostic tests
	# [[Running and Publishing the Expectations Sample\|Build and test the TestApp with the Expectations sample]], publishing results to Test Space		# [[Running and Publishing the Expectations Sample\|Build and test the TestApp with the Expectations sample]], publishing results to Test Space
	# If you are interested in learning about tests in native C/C++, you can also [[Running and Publishing the TestIntro Sample\|build and test the TestApp with the TestIntro sample]].		# If you are interested in learning about tests in native C/C++, you can also [[Running and Publishing the TestIntro Sample\|build and test the TestApp with the TestIntro sample]].