Hello Cláudio,
On 26/02/2020 11:13, Cláudio Maia wrote:
Hello,
This email describes several possible issues related to RTEMS Tester and its
documentation.
1- On the documentation page of RTEMS Tester
(https://docs.rtems.org/branches/master/user/tools/tester.html) it is stated that one can
use "sparc-rtems5-run" to execute/test programs compiled for SPARC
architectures.
However, this command does not exist in the bin folder of the toolchain, and I
believe that is not being built when building the toolchain executables (at
least with the configurations that I am using).
Is this command not being used any more?
2- Consequently, when executing the Tester with the following options (as
suggested in Section 11.5.3):
$ rtems-test --log=log_erc32_run --rtems-bsp=erc32-run --rtems-tools=$RTEMS/5
./build/sparc-rtems5/c/erc32/testsuites/samples
I get the following error message for each of the tests (example for
base_sp.exe):
error: run.cfg:70: execute failed:
/opt/working-dir/rtems/5/bin/sparc-rtems5-run
./build/sparc-rtems5/c/erc32/testsuites/samples/base_sp.exe: exit-code:2
However, if I modify the bsp from "erc32-run" to "erc32-sis", as follows:
$ rtems-test --log=log_erc32_run --rtems-bsp=erc32-sis --rtems-tools=$RTEMS/5
./build/sparc-rtems5/c/erc32/testsuites/samples
all tests execute with success, as it is using the SIS simulator.
if you find issues like this, please fix it in the documentation sources
https://git.rtems.org/rtems-docs/
and send a patch:
https://docs.rtems.org/branches/master/user/support/contrib.html
This is an indicator that "--rtems-bsp=erc32-run" is using "sparc-rtems5-run"
which is not being built (as explained in 1).
3- Oddly enough, when I execute the RTEMS Tester with "--rtems-bsp=erc32-run" as an
option and using the "samples" folder as input, the minimum.exe passes the test without
any error message.
However, when executing the test alone, as follows:
$ rtems-test --log=log_erc32_run --rtems-bsp=erc32-run --rtems-tools=$RTEMS/5
./build/sparc-rtems5/c/erc32/testsuites/samples/minimum.exe
the log shows the same error message (as below) but the test is marked as
passed.
error: run.cfg:70: execute failed:
/opt/working-dir/rtems/5/bin/sparc-rtems5-run
./build/sparc-rtems5/c/erc32/testsuites/samples/minimum.exe: exit-code:2
The minium.exe test intentionally produces no output. I guess the
sparc-rtems5-run is somewhat broken.
4- The documentation mentions GDB in Section 11.5.3 "Select the erc32 BSP and use GDB."
but no GDB instance is instantiated by default when running the tester and no GDB option appears in
the help of "rtems-tester --help" command. Am I missing something here?
Originally, the SIS was integrated in the GDB as a built-in simulator.
Jiri Gaisler moved it to a stand-a-lone project. This needs
documentation changes throughout. You can help to fix this.
5- Now concerning ARM architectures, is there any equivalent procedure to cross-test
executables for ARM architectures, as there is at the moment for SPARC (with SIS)? What
is the purpose of "arm-rtems5-run"?
You can use the Qemu based BSPs on ARM for test runs, e.g.
xilinx_zynq_a9_qemu and realview_pbx_a9_qemu. Not all tests run well on
Qemu due to simulator timing restrictions.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
