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

Timestamp:

08/10/09 20:31:36 (15 years ago)

Author:

Cocanlucian

Comment:

Developer/Projects/Open/TraceTool

@@ -21 +21 @@
                           '''--config'''=''path to the configuration file''
 
-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:
+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''. 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:
 
    ./rtems_trace.py 
@@ -196 +196 @@
 = Tutorial =
 
-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.
+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. The BSP used is i386 and the RTEMS version is 4.10.
 
  *  Set up the configuration file as explained [http://www.rtems.org/wiki/index.php/RTEMS_Trace_Tool#Configuration_files here].
  *  Generate the wrapping code:
 
-   ./rtems_trace.py --mode=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. Also, if the
+   ./rtems_trace.py
+
+ *  Compile the wrapping and the application code (copy your application code in the ''cwd/wrappers'' directory).
+
+   ./rtems_trace.py --mode=compile --compiler=i386-rtems4.10-gcc 
+
+ *  Do the linking.
+
+   ./rtems_trace.py --mode=link --compiler=i386-rtems4.10-gcc -build=/home/cocan/Faculta/RTEMS/build-i386-qemu-rtems
+
+ *  Run the final executable in QEMU in order to get the trace file needed for decoding.
+TBD
+ *  Decode the trace file (copy the trace file in ''cwd'').
+
+   ./rtems_trace.py --mode=decode
+
+This is it. All the tracing information it's now saved in the ''cwd/decoded.txt'' file.