; -------------------------------------------------------------------------------- ; @Title: TRACE32 Custom Trace - README ; @Description: - ; @Author: jboch ; @Copyright: (C) 1989-2014 Lauterbach GmbH, licensed for use with TRACE32(R) only ; -------------------------------------------------------------------------------- ; $Id: readme.txt 7025 2014-04-28 15:42:01Z kjmal $ ********************************************* * Table of contents * ********************************************* - List of files - Introduction - ToDo ********************************************* * Introduction * ********************************************* The intention of this demo project is to familiarize you with the use of T32's CustomTrace feature and to help you creating your own custom trace applications. Thereby the term 'application' refers to a dynamically linked library, which decodes high-level instrumentation messages not known to T32. For a general description of the CustomTrace feature please refer to 'customtrace_dll.pfd'! In this example we will focus on only one feature of the CustomTrace, namely to decode high-level instrumentation messages and feed them back to T32. In particular we will deal with STPv1 messages that are utilized to provide a basic program and date tracing mechanism: On entering certain functions, the functions's address as well as a variable's address and value are written to the instrumentation port. These information then are exported to T32 by the library and also printed to an AREA window in raw format. !!!Important!!! The example at hand has been created for use with Texas Instruments' System Trace Module. Users of different instrumentation traces (like ITM or STM by ARM) need to adapt some of the provided files (see 'Optional' items in section 'ToDo')! ********************************************* * List of files * ********************************************* - customtrace_dll.pfd Manual that helps you to create your own libraries - demo.c Source code to be compiled for your target architecture - readme.txt This file - setup_ct.cmm Script file which sets up T32 for the customtrace example - customtrace_linux_gcc/makelinux Makefile to compile the customtrace example for linux machines using the GNU C Compiler - customtrace_linux_gcc/pipeproto.c Source file required for compilation - customtrace_linux_gcc/pipeproto.h Header file required for compilation - customtrace_linux_gcc/pproto.c Source file of the customtrace example - customtrace_linux_gcc/pproto.so.1 Compiled example library - customtrace_linux_gcc/makefile Makefile to compile the customtrace example for Win32 machines using Microsoft's Visual C Compiler. - customtrace_win32_vcc/pipeproto.c Source file required for compilation - customtrace_win32_vcc/pipeproto.h Header file required for compilation - customtrace_win32_vcc/pproto.c Source file of the customtrace example - customtrace_win32_vcc/pproto.def Definition file required for compilation - customtrace_win32_vcc/pproto.dll Compiled example library ********************************************* * ToDo * ********************************************* Optional: - Configure file 'setup_ct.cmm' for use with STM via TPIU, if necessary. - Check that 'STM_BASE' and 'STP_TRACE_xx' are defined correctly in file 'demo.c'. - Recompile library 'pproto' if the compiled librarys do not match your host OS. Mandatory: - Compile demo.c for your target architecture - Copy the content of this folder to your project's working path - Add 'do setup_ct.cmm' in your startup script where appropriate