Difference between revisions of "STRIDE Off-Target Environment"

From STRIDE Wiki
Jump to: navigation, search
(Created page with '== Off-Target Environment == right|300px| The Off-Target configuration puts both host and target code on the desktop Two of the largest barriers t…')
 
(Host Compiler)
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Off-Target Environment ==
+
= Configuration =  
[[image:STRIDE_Desktop.jpg|right|300px| The Off-Target configuration puts both host and target code on the desktop]]
+
[[image:STRIDE_Desktop.jpg|right|400px| 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_Overview | 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.  
+
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.  
  
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.
+
In order to conduct '''training''' or build and execute our [[Samples_Overview | Samples]], we leverage this environment (i.e. 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. This enables the user to create their own ''sandbox'' for training and Off-Target unit testing.  
  
In order to conduct training or build and execute our [[Samples_Overview | Samples]],  we leverage 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 Off-Target Environment utilizes the [[Desktop_Installation#SDK|Framework's "SDK"]] that can be built and executed on the host system. When using the SDK Makefile a simulated target ''native application'' is generated, which we call a '''Test Application (TestApp)'''.  
  
Please refer to the following [[Off-Target_Environment_Setup | Off-Target Environment Setup]] instructions.
+
The [[STRIDE Runner]] application executes on the same system and communicates with the '''TestApp''' process over a TCP/IP connection. This setup frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.
 +
 
 +
= Host Compiler =
 +
The off-target environment requires a [[Installation_Overview#Desktop_Installation | STRIDE Desktop Installation]], and the appropriate host '''compiler''':
 +
* For Windows, Microsoft Visual Studio 2008 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]). <i>In case you have [http://www.cygwin.com Cygwin] installed, the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] could be used as an alternative.</i>
 +
* For Linux and FreeBSD, the [http://en.wikipedia.org/wiki/GNU_Compiler_Collection GNU Compiler Collection] (included by default in almost all distros) is required.
 +
 
 +
For instructions on building an off-target '''TestApp''' refer to the following [[Building an Off-Target Test App | article]].
 +
 
 +
 
 +
[[Category:Installation]]

Latest revision as of 17:21, 25 September 2013

Configuration

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.

In order to conduct training or build and execute our Samples, we leverage this environment (i.e. 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. This enables the user to create their own sandbox for training and Off-Target unit testing.

The Off-Target Environment utilizes the Framework's "SDK" that can be built and executed on the host system. When using the SDK Makefile a simulated target native application is generated, which we call a Test Application (TestApp).

The STRIDE Runner application executes on the same system and communicates with the TestApp process over a TCP/IP connection. This setup frees you from external hardware dependencies and provides for a rapid "edit/build/test" cycle.

Host Compiler

The off-target environment requires a STRIDE Desktop Installation, and the appropriate host compiler:

For instructions on building an off-target TestApp refer to the following article.