Off-Target Environment: Difference between revisions

From STRIDE Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 15: Line 15:


# Build the STRIDE runtime library
# Build the STRIDE runtime library
# Build and connect to the target app with only the runtime
# Build and test the target app with S2 diagnostic tests
# Build and test the target app with S2 diagnostic tests
# Build and test the target app with the TestIntro sample
# Build and test the target app with the TestIntro sample
# Explore other sample tests


==Building the STRIDE Runtime Library==
==Building the STRIDE Runtime Library==
Line 39: Line 39:


== Building the TargetApp ==
== Building the TargetApp ==
This step builds the first version of an instrumented target application. This application links with the STRIDE runtime library and adds the S2 diagnostic tests.
This step builds the first version of an instrumented target application. This application links with the STRIDE runtime library and includes the S2 diagnostic tests.


This step requires an installation of the STRIDE build tools. If not installed, please see [[Package_Installation#Build_Tools|Package Installation]] for more information.
This step requires an installation of the STRIDE build tools. If not installed, please see [[Package_Installation#Build_Tools|Package Installation]] for more information.
Line 61: Line 61:
[[SDK Target Application Details]]
[[SDK Target Application Details]]


=== Verifying Host to Target Connectivity ===
=== Running the S2 Diagnostic Tests ===
In this step, we will use the stride executable to verify connectivity between host and target.
In this step, we will use the stride executable to run the S2 diagnostic tests.


This step requires an installation of the STRIDE host tools. If not installed, please see [[Package_Installation#Host_Tools|Package Installation]] for more information.
This step requires an installation of the STRIDE host tools. If not installed, please see [[Package_Installation#Host_Tools|Package Installation]] for more information.
Line 78: Line 78:
</li>
</li>
<li>From a console window, invoke stride as follows, to verify connectivity with the target app:
<li>From a console window, invoke stride as follows, to verify connectivity with the target app:
<pre>stride --diagnostic --device TCP:localhost:8000</pre></li>
<pre>stride --diagnostic --database ~/stride/SDK/Linux/out/TestApp.sidb --device TCP:localhost:8000</pre></li>
<li>View the output on  
<li>View the output on the
</li>
</li>
</ol>
</ol>

Revision as of 15:47, 4 June 2009

Overview

The STRIDE SDK is provided to be used primarily as an off-target evaluation or development sandbox. This allows you to use STRIDE in a small, controlled environment without needing to make changes to your target build. In addition, the SDK Makefile can serve as an example of the steps needed to add STRIDE instrumentation to your target build.

Each SDK package has identical functionality, but targets a specific operating system. The SDK contains the following items:

  • STRIDE runtime source
  • PAL source for interface with the Target OS
  • Makefile to build STRIDE runtime library, test and sample applications
  • Compiler setting file for target processor

Evaluation Steps

To simplify the evalution, we recommend using a single Windows or Linux 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 transferrable to a production environment.

The recommended evaluation steps are as follows:

  1. Build the STRIDE runtime library
  2. Build and test the target app with S2 diagnostic tests
  3. Build and test the target app with the TestIntro sample
  4. Explore other sample tests

Building the STRIDE Runtime Library

Note: all Makefiles must be run with gnu make. For SDKs targeting OS's where this is not the standard make utility, an executable is supplied in the SDK's bin directory.

Linux

The Makefile assumes a gnu toolchain. (Other toolchains can be used; see the comments in the Makefile.)

  1. cd to ~/stride/SDK/Linux/src
  2. Build the library 
    make library
  3. The file ~/stride/SDK/Linux/out/lib/libstride.a will be produced

Windows

The Makefile assumes a Visual Studio toolchain. (Other toolchains can be used; see the comments in the Makefile.)

  1. If using Microsoft Visual Studio, open a Visual Studio command prompt to ensure that the compiler and linker are on your PATH.[1]
  2. cd to stride\SDK\Windows\src
  3. build the library using the supplied gnu make. (You will get Makefile errors if you use the default make.) 
    ..\bin\make library
  4. The file stride\SDK\Windows\out\lib\stride.lib will be produced

Building the TargetApp

This step builds the first version of an instrumented target application. This application links with the STRIDE runtime library and includes the S2 diagnostic tests.

This step requires an installation of the STRIDE build tools. If not installed, please see Package Installation for more information.

Linux

  1. cd to ~/stride/SDK/Linux/src
  2. Build the test app 
    make testapp
  3. The file ~/stride/SDK/Linux/out/bin/TestApp will be produced
  4. Note also that the STRIDE database file ~/stride/SDK/Linux/out/TestApp.sidb is also produced

Windows

  1. If using Microsoft Visual Studio, open a Visual Studio command prompt to ensure that the compiler and linker are on your PATH.
  2. cd to stride\SDK\Windows\src
  3. build the test app using the supplied gnu make. (You will get Makefile errors if you use the default make.) 
    ..\bin\make testapp
  4. The file stride\SDK\Windows\out\bin\TestApp.exe will be produced
  5. Note also that the STRIDE database file stride\SDK\Linux\out\TestApp.sidb is also produced

SDK Target Application Details

Running the S2 Diagnostic Tests

In this step, we will use the stride executable to run the S2 diagnostic tests.

This step requires an installation of the STRIDE host tools. If not installed, please see Package Installation for more information.

  1. Invoke the TestApp.
    • Windows: TestApp.exe will open and run in a new console window
    • Linux: In order to see TestApp's output, we recommend that you manually open a new console and invoke TestApp from there
  2. Note TestApp's output upon startup. Under Linux, the following is shown 
    [tim@s2centos01 bin]$ ./TestApp
 starting up...
 "_srThread" thread started.
 "stride" thread started.
 Listening on TCP port 8000
  3. From a console window, invoke stride as follows, to verify connectivity with the target app: 
    stride --diagnostic --database ~/stride/SDK/Linux/out/TestApp.sidb --device TCP:localhost:8000
  4. View the output on the

Adding Diagnostic Tests

Adding Sample Tests

Makefile Targets

all
Builds the library target
library
Builds STRIDE runtime, producing stride.lib
clean
Deletes intermediate and target files
testapp
Builds an instrumented test application, TestApp.exe, using sources found in the sample_src directory
database
im
daemon

Instrumenting Multiple Processes

Notes

  1. ↑ You can get a VS command prompt via the Start menu. Choose: Start -> All Programs -> Microsoft Visual Studio 200X -> Visual Studio Tools -> Visual Studio 200X Command Prompt
Retrieved from "https://www.stridewiki.com/index.php?title=Off-Target_Environment&oldid=9873"