Integration with VectorCAST® - Code Coverage


The embedded tools company
Integration Environment for Trace-based Code Coverage
Integration Environment for RAM-based Code Coverage


Picture
  Highlights
Trace-based Code Coverage

Based on TRACE32 code coverage export file
Based on TRACE32 real-time code coverage without instrumentation
Based on instruction trace capability of chip under test
Open for all off-chip trace interfaces supported by TRACE32
TRACE32 Trace Streaming allows long-term coverage
Immediate switch to debug on a test fault

RAM-based Code Coverage

Based on TRACE32 RAM save output file
VectorCAST Harness collects coverage data and writes them to Coverage RAM
No off-chip trace port required
Immediate switch to debug on a test fault
Open for all processor architectures supported by TRACE32
Open for all compilers supported by TRACE32
 
  Introduction
The TRACE32® VectorCAST integration allows performing code coverage in the VectorCAST look-and-feel for both: chips with or without instruction trace capability.


Link Support
Technical Support
[www.vectorcast.com]  VectorCAST Code Coverage

TRACE32 Trace-based Code Coverage




TOP

Integration Environment for Trace-based Code Coverage


    If the chip under test has an off-chip trace interface that provides instruction trace visibility, TRACE32 records this information and takes it as base for its code coverage. The advantage of an off-chip trace interface is real-time code coverage without instrumentation of the target application. The recording volume for a test run is several TBytes of trace information if TRACE32 Trace Streaming is used or 4 GByte otherwise.



    The TRACE32 code coverage results can be exported to a file and then be imported into the VectorCAST tool chain for further analysis.


TOP

Integration Environment for RAM-based Code Coverage


    The VectorCAST Harness test agent collects the coverage data, if the chip under test does not provide an off-chip trace interface. The Harness is using a Coverage RAM allocated on the target for this purpose. The size of the Coverage RAM determines the recording volume for a test run. After each test run the contents of the Coverage RAM can be saved to a file by TRACE32 and then loaded into the VectorCAST tool chain for further analysis.





Copyright © 2016 Lauterbach GmbH, Altlaufstr.40, D-85635 Höhenkirchen-Siegertsbrunn, Germany  Impressum
The information presented is intended to give overview information only.
Changes and technical enhancements or modifications can be made without notice. Report Errors
Last generated/modified: 17-Mar-2016