Changes between Version 52 and Version 53 of Developer/Projects/Open/TraceTool


Ignore:
Timestamp:
Aug 10, 2009, 8:31:36 PM (10 years ago)
Author:
Cocanlucian
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Projects/Open/TraceTool

    v52 v53  
    2121                          '''--config'''=''path to the configuration file''
    2222
    23 Using this mode the user will generate the wrapping code, which is a set of files corresponding to the functions that he specified in the configuration file. If the --mode option it's not specified then the default mode chosen by the tool will be ''generate''. So if the user wants to generate and save the wrapping code in a directory named ''wrappers'' from the current working directory (cwd) which is the default path, then he can simply do this:
     23Using this mode the user will generate the wrapping code, which is a set of files corresponding to the functions that he specified in the configuration file. If the --mode option it's not specified then the default mode chosen by the tool will be ''generate''. If the -c (--config) option it's not specified, then the tool will always look for the default configuration file ''rtems-trace.cfg'' from your current working directory. So if the user wants to generate and save the wrapping code in a directory named ''wrappers'' from the current working directory (cwd) which is the default path, then he can simply do this:
    2424
    2525   ./rtems_trace.py
     
    196196= Tutorial =
    197197
    198 The following section will try to illustrate how to properly use the RTEMS trace tool in order to get the decoded file containing the information needed.
     198The following section will try to illustrate how to properly use the RTEMS trace tool in order to get the decoded file containing the information needed. The BSP used is i386 and the RTEMS version is 4.10.
    199199
    200200 *  Set up the configuration file as explained [http://www.rtems.org/wiki/index.php/RTEMS_Trace_Tool#Configuration_files here].
    201201 *  Generate the wrapping code:
    202202
    203    ./rtems_trace.py --mode=generate
    204 
    205 If the -c (--config) option it's not specified, then the tool will always look for the default configuration file '''rtems-trace.cfg''' from your current working directory. Also, if the
     203   ./rtems_trace.py
     204
     205 *  Compile the wrapping and the application code (copy your application code in the ''cwd/wrappers'' directory).
     206
     207   ./rtems_trace.py --mode=compile --compiler=i386-rtems4.10-gcc
     208
     209 *  Do the linking.
     210
     211   ./rtems_trace.py --mode=link --compiler=i386-rtems4.10-gcc -build=/home/cocan/Faculta/RTEMS/build-i386-qemu-rtems
     212
     213 *  Run the final executable in QEMU in order to get the trace file needed for decoding.
     214TBD
     215 *  Decode the trace file (copy the trace file in ''cwd'').
     216
     217   ./rtems_trace.py --mode=decode
     218
     219This is it. All the tracing information it's now saved in the ''cwd/decoded.txt'' file.