diff options
author | Chris Johns <chrisj@rtems.org> | 2019-02-28 08:36:39 +1100 |
---|---|---|
committer | Chris Johns <chrisj@rtems.org> | 2019-03-01 09:52:59 +1100 |
commit | d5b631fa3bcd822815c7f875432b15e8b9875395 (patch) | |
tree | 153c5012fad2b329b10d11fbd248828fa8ef9928 /user/tracing | |
parent | Add commands and output to the README. (diff) | |
download | rtems-docs-d5b631fa3bcd822815c7f875432b15e8b9875395.tar.bz2 |
User: Change output block to type none.
Diffstat (limited to 'user/tracing')
-rw-r--r-- | user/tracing/captureengine.rst | 4 | ||||
-rw-r--r-- | user/tracing/examples.rst | 10 | ||||
-rw-r--r-- | user/tracing/tracelinker.rst | 6 |
3 files changed, 10 insertions, 10 deletions
diff --git a/user/tracing/captureengine.rst b/user/tracing/captureengine.rst index d04b8a4..a8bca53 100644 --- a/user/tracing/captureengine.rst +++ b/user/tracing/captureengine.rst @@ -19,7 +19,7 @@ file: `sparc-rtems5/c/erc32/testsuites/samples`. In order to access the capture testcase perform the following set of operations inside the RTEMS build directory. -.. code-block:: shell +.. code-block:: none $ cd /sparc-rtems5/c/erc32/testsuites/samples $ sparc-rtems5-run ./capture.exe @@ -98,7 +98,7 @@ traces the context switches between these tasks. ``cwceil`` and ``cwfloor`` are set to a narrow range of task priorities to avoid creating noise from a large number of context switches between tasks we are not interested in. -.. code-block:: shell +.. code-block:: none *** BEGIN OF TEST CAPTURE ENGINE *** *** TEST VERSION: 5.0.0.de9b7d712bf5da6593386fd4fbca0d5f8b8431d8 diff --git a/user/tracing/examples.rst b/user/tracing/examples.rst index c44daff..d0bef0b 100644 --- a/user/tracing/examples.rst +++ b/user/tracing/examples.rst @@ -46,7 +46,7 @@ has been stored) run the following commands to generate traces: BSP is configured with the following command - -.. code-block:: shell +.. code-block:: none ../rtems/configure --target=sparc-rtems5 --prefix=/development/rtems/5 \ --enable-networking --enable-tests --enable-rtemsbsp=erc32 --enable-cxx @@ -58,7 +58,7 @@ following commands according to your installation. Also confirm the path of the fileio's executable and object files in the last line of the command according to your installation. -.. code-block:: shell +.. code-block:: none sparc-rtems5-gcc -Bsparc-rtems5/erc32/lib/ \ -specs bsp_specs -qrtems -mcpu=cypress -O2 -g -ffunction-sections \ @@ -72,7 +72,7 @@ the application. The link command follows the escape sequence "--". "-C" option denotes the name of the user configuration file and "-W" specifies the name of the wrapper c file. -.. code-block:: shell +.. code-block:: none rtems-tld -C fileio-trace.ini -W fileio-wrapper -- -Bsparc-rtems5/erc32/lib/ \ -specs bsp_specs -qrtems -mcpu=cypress -O2 -g -ffunction-sections \ @@ -88,13 +88,13 @@ display the contents of the trace buffer and save the buffer to disk in the form of binary files. Use `rtrace -l` to list the availalble options for commands with `rtrace`. -.. code-block:: shell +.. code-block:: none sparc-rtems5-run sparc-rtems5/c/erc32/testsuites/samples/fileio.exe The output from the above commands will be as follows: -.. code-block:: shell +.. code-block:: none *** BEGIN OF TEST FILE I/O *** *** TEST VERSION: 5.0.0.de9b7d712bf5da6593386fd4fbca0d5f8b8431d8 diff --git a/user/tracing/tracelinker.rst b/user/tracing/tracelinker.rst index b1e60fd..d32e52b 100644 --- a/user/tracing/tracelinker.rst +++ b/user/tracing/tracelinker.rst @@ -25,7 +25,7 @@ options it needs and the second part is a standard linker command line you would use to link an RTEMS application. The current command line for trace linker consists of: -.. code-block:: shell +.. code-block:: none $ rtems-tld -h rtems-trace-ld [options] objects @@ -482,12 +482,12 @@ commands in the topmost build directory to build the tools project: First we configure using: -.. code-block:: shell +.. code-block:: none $./waf configure --prefix=$HOME/development/rtems/5 Then we build and install using: -.. code-block:: shell +.. code-block:: none $./waf build install |