ThreadX docsThreadX docs
ThreadX
ThreadX Modules
NetX Duo
FileX
GUIX
USBX
TraceX
LevelX
ThreadX
ThreadX Modules
NetX Duo
FileX
GUIX
USBX
TraceX
LevelX
  • Tracex Documentation

    • Understand TraceX
    • TraceX documentation
    • Chapter 1 - Introduction to TraceX
    • Chapter 2 - Installation and use of TraceX
    • Chapter 3 - Description of TraceX
    • Chapter 4 - TraceX performance analysis
    • Chapter 5 - Generating trace buffers
    • Chapter 6 - ThreadX trace events
    • Chapter 7 - FileX trace events
    • Chapter 8 - NetX Duo trace events
    • Chapter 9 - USBX trace events
    • Chapter 10 - Customer user events
    • Chapter 11 - Format of event trace buffer
    • Appendix A - Sample tx_port.h
    • Appendix B - The tx_trace.h file
    • Appendix C - DOS command-line utilities
    • Appendix D - Dumping and trace buffer
    • TraceX user guide

Chapter 1 - Introduction to TraceX

TraceX is a Eclipse Foundation system analysis tool that displays system event information gathered by ThreadX running on an embedded target. The user is responsible for transferring the trace buffer stored in RAM in the embedded target to a binary file on the host computer. The user can then open this file with TraceX and graphically analyze the target events, diagnosing system problems and tuning a working application to improve performance and resource management.

TraceX Requirements

TraceX requires Windows XP (or above). The system should have a minimum of 192 MB of RAM, 2 GB of available hard-disk space, and a minimum display of 1024x768 with 256 colors. In addition, the application must be running on ThreadX V5.0 or later.

TraceX also requires the .NET framework be installed, which the TraceX installer does automatically.

TraceX Constraints

TraceX has the following constraints:

  • TraceX files are limited to a maximum of 32,768 events (roughly 1 MB ).
  • The time-stamp source must have reasonable resolution. If the resolution is too low, the events will overlap. If the resolution is too high, there is potential for long gaps between events.
  • TraceX cannot accurately measure intervals between events greater than the timer period.
Prev
TraceX documentation
Next
Chapter 2 - Installation and use of TraceX