Off-Target Environment

Overview

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 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:

1. Review the STRIDE Overview
2. Install required Framework
3. Configure STRIDE Test Space for publishing results
4. Build the basic TargetApp with built-in S2 diagnostic tests
5. Build and test the TargetApp with the Expectations sample, publishing results to Test Space
6. If you are interested in learning about tests in native C/C++, you can also build and test the TargetApp with the TestIntro sample.
7. Explore other sample tests