Off-Target Environment: Difference between revisions
No edit summary |
No edit summary |
||
| 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_Sandbox_Configuration.jpg|right|The sandbox configuration puts both host and target code on the host PC]] | ||
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 | 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. | ||
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 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. | ||
== 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 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 sandbox evaluation and training 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 packages | # Install required packages | ||
# Activate your STRIDE license | # Activate your STRIDE license | ||
| Line 17: | Line 15: | ||
# Build and test the basic TargetApp with built-in S2 diagnostic tests, publishing results to TestSpace | # Build and test the basic TargetApp with built-in S2 diagnostic tests, publishing results to TestSpace | ||
# Build and test the TargetApp with the TestIntro sample, publishing results to TestSpace | # Build and test the TargetApp with the TestIntro sample, publishing results to TestSpace | ||
# Explore other sample tests | # Explore other sample tests | ||
| Line 30: | Line 27: | ||
* Build Tools | * Build Tools | ||
== Related Links == | == Related Links == | ||
| Line 49: | Line 38: | ||
== Notes == | == Notes == | ||
<references/> | <references/> | ||
[[Category: | [[Category:Sandbox & Training]] | ||
Revision as of 17:11, 4 September 2009
Overview
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.
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.
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.
The recommended evaluation steps are as follows:
- Review the STRIDE Overview
- Install required packages
- Activate your STRIDE license
- Configure STRIDE Test Space for publishing results
- Build and test the basic TargetApp with built-in S2 diagnostic tests, publishing results to TestSpace
- Build and test the TargetApp with the TestIntro sample, publishing results to TestSpace
- Explore other sample tests
Installing Packages
The following packages must be installed on the computer you will use for your sandbox environment. (Use Windows or Linux packages as appropriate).
See Package Installation for instructions.
- STRIDE SDK
- Host Tools
- Samples
- Build Tools