...
The importing process consists of two stages: 1) Generating the Build Data File (.bdf) and 2) importing this file in C++test.
Generating a .bdf
...
from an EW
...
Project
- For runtime testing, increase "Stack/Heap" in EW project options to at least 2048(800h)/ 1280(500h) respectively to allow for testing overheads. For EW430 projects that use the 430X core and medium or large data model, the values should be at least 4096(1000h) for stack and 2048(800h)/4096(1000h) for the heaps.
- Start console.
- Set the compiler toolchain on PATH (as for C++test; 'cspybat' on PATH & EW_DIR envar aren't needed).
- Set the C++test install directory on PATH.
- CD to the project's directory.
- Run the following command:
| Code Block | ||
|---|---|---|
| ||
cpptesttrace --cpptesttraceProjectName=<prj_name> --cpptesttraceResponseFileOption=-f --cpptesttraceOutputFile=<prj_dir>\<prj_name>. |
...
bdf iarbuild <prj_name>.ewp -build <EW_project_config_name> |
Use an EW project configuration name (e.g., Debug, Release, DebugRunFromFlash, etc.) for the -build argument.
Specify the absolute path to the the --cpptesttraceOutputFile option option. This is because several .bdf files are likely to spread through working directories spawned by by iarbuild toolchain toolchain commands.
You may need to place quotation marks around the options containing spaces/braces.
In most circumstances, you should name your C++test project after the .ewp file name when using the the --cpptesttraceProjectName=<prj_name> option option.
By default, the trace feature is configured to capture each toolchain executable name recognized by C++test through built-in compiler configurations. If the process' command-lines aren't scanned, specify the compiler and linker executable names by adding a a --cpptesttraceTraceCommand option option to the the cpptesttrace command command.
EW430 Example:
--cpptesttraceTraceCommand=icc430\.exe$|xlink\.exe$
STM8 Example:
--cpptesttraceTraceCommand=iccstm8\.exe$|ilinkstm8\.exe$
The The cpptesttrace command command always appends its output file, so you should remove the previous .bdf file before re-scanning the project.
You may also use use -log all after the -build flag flag to show detailed build progress information. The The -log all option option is an an iarbuild option option.
Import a BDF
...
into C++test
- Start console (or reuse this for BDF generation).
- Set environment for the appropriate toolchain as described in the documentation (executables on PATH, EW_DIR envar).
- Start C++test.
- Follow steps of importing the BDF file described in documentation (see Importing project using Build Data File with the GUI wizard).
- Confirm project settings correctness in Properties> Parasoft> C++test> Build Settings.
...