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


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

Legend:

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

    v42 v43  
    2525
    2626 
    27    Usage: ./rtems_trace.py -m compile
    28                            -i name of the compiler
    29                            -g path to the wrapping code
    30                            -o path to where the compiled wrapping code should be saved
    31                            -l path to where the RTEMS libraries were installed
    32           ./rtems_trace.py --mode=compile
    33                            --compiler=name of the compiler 
    34                            --genpath=path to the wrapping code
    35                            --objpath=path to where the compiled wrapping code should be saved
    36                            --lib=path to where the RTEMS libraries were installed
     27   Usage: ./rtems_trace.py '''-m''' ''compile''
     28                           '''-i''' ''name of the compiler''
     29                           '''-g''' ''path to the wrapping code''
     30                           '''-o''' ''path to where the compiled wrapping code should be saved''
     31                           '''-l''' ''path to where the RTEMS libraries were installed''
     32          ./rtems_trace.py '''--mode'''=''compile''
     33                           '''--compiler'''=''name of the compiler''
     34                           '''--genpath'''=''path to the wrapping code''
     35                           '''--objpath'''=''path to where the compiled wrapping code should be saved''
     36                           '''--lib'''=''path to where the RTEMS libraries were installed''
    3737
    3838Using 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/''.
     
    4747   Usage: ./rtems_trace.py '''-m''' ''link''
    4848                           '''-i''' ''name of the compiler''
    49                            -b RTEMS build path
    50                            -o path to the compiled code (.o files)
    51                            -  list of comma separated object files that should be included in the final executable
    52                            -l path to where the RTEMS libraries were installed
    53           ./rtems_trace.py --mode=link
    54                            --compiler=name of the compiler   
    55                            --build=RTEMS build path
    56                            --objpath=path to the compiled code(.o files)
    57                            --trace-o=list of comma separated object files that should be included in the final executable
    58                            --lib path to where the RTEMS libraries were installed
     49                           '''-b''' ''RTEMS build path''
     50                           '''-o''' ''path to the compiled code (.o files)''
     51                           '''-'''  ''list of comma separated object files that should be included in the final executable''
     52                           '''-l''' ''path to where the RTEMS libraries were installed''
     53          ./rtems_trace.py '''--mode'''=''link''
     54                           '''--compiler'''=''name of the compiler''
     55                           '''--build'''=''RTEMS build path''
     56                           '''--objpath'''=''path to the compiled code(.o files)''
     57                           '''--trace-o'''=''list of comma separated object files that should be included in the final executable''
     58                           '''--lib'''=''path to where the RTEMS libraries were installed''
    5959
    6060In 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.
     
    180180= How to use it =
    181181
     182The 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.
    182183
    183184 *  Set up the configuration file as explained here.