Changes between Version 43 and Version 44 of Developer/Projects/Open/TraceTool


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

Legend:

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

    v43 v44  
    1515
    1616  Usage: ./rtems_trace.py '''-m''' ''generate''
     17                          '''-c''' ''path to the configuration file''
    1718                          '''-g''' ''path to where the wrapping code should be saved''
    1819         ./rtems_trace.py '''--mode'''=''generate''
    1920                          '''--genpath'''=''path to where the wrapping code should be saved''
     21                          '''--config'''=''path to the configuration file''
    2022
    2123Using 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:
     
    3638                           '''--lib'''=''path to where the RTEMS libraries were installed''
    3739
    38 Using this mode the user can compile all the .c files from a directory (usually the .c files from the wrapping code directory) and save the resulted files (.o files) in the directory specified by the -o option. If the -g and -o options are not specified then the rtems_trace tool will look in the ''wrappers'' directory located in cwd and save the .o files in a directory named ''objects'' also from cwd. Also, if the -l option it's not specified than the tool will choose this path by default: ''/opt/rtems-4.10/i386-rtems4.10/pc386/lib/''.
     40Using this mode the user can compile all the .c files from a directory (usually the .c files from the wrapping code directory) and save the resulted files (.o files) in the directory specified by the -o option. If the -g and -o options are not specified then the rtems_trace tool will look in the ''wrappers'' directory located in cwd and save the .o files in a directory named ''objects'' also from cwd. Also, if the -l option it's not specified than the tool will choose this path by default: ''/opt/rtems-4.10/i386-rtems4.10/pc386/lib/''. <BR>
    3941Example:
    4042
     
    5860                           '''--lib'''=''path to where the RTEMS libraries were installed''
    5961
    60 In this mode, the RTEMS trace tool will link all the object files from the specified directory (or from the default one if no directory is specified using the -o or --objpath option) if the --trace-o option it's not used. The user can specify only a subset of object files to be included in the final executable using the --trace-o option. The final executable file is placed into the same directory where the object files are found, under the ''wrapper.exe'' name.
     62In this mode, the RTEMS trace tool will link all the object files from the specified directory (or from the default one if no directory is specified using the -o or --objpath option) if the --trace-o option it's not used. The user can specify only a subset of object files to be included in the final executable using the --trace-o option. The final executable file is placed into the same directory where the object files are found, under the ''wrapper.exe'' name. <BR>
     63Example:
     64
     65   ./rtems_trace.py --mode=link --compiler=i386-rtems4.10-gcc -build=/home/cocan/Faculta/RTEMS/build-i386-qemu-rtems
     66
     67will link all the object files from ''cwd/objects'', generating the final executable file ''cwd/objects/wrapper.exe''
    6168= Decode mode =
    6269
     70
     71   Usage: ./rtems_trace.py '''-m''' ''decode''
     72                           '''-t''' ''path to the trace file''
     73                           '''-d''' ''where to save the final decoded data''
     74          ./rtems_trace.py '''--mode'''=''decode''
     75                           '''--trace-file'''=''path to the trace file''
     76                           '''--dec-file'''=''where to save the final decoded data''
     77
     78In this mode, the RTEMS trace tool will read the input file, specified using the -t or --trace-file option and decode it, generating the final decoded data in the file specified by the -d or --dec-file option.                           
    6379= Configuration files =
    6480