Error during execution of testsuites on host OS, for ARM Architecture.
Vaibhav Gupta
vaibhavgupta40 at gmail.com
Wed Apr 24 18:03:29 UTC 2019
Hello,
I even tried to run rtems-test for the testsuites/samples for ARM
Architecture,
$ rtems-test --rtems-bsp=xilinx_zynq_a9_qemu
--rtems-tools=$HOME/development/rtems/5
~/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples
RTEMS Testing - Tester, 5.0.not_released
Command Line: /home/varodek/development/rtems/5/bin/rtems-test
--rtems-bsp=xilinx_zynq_a9_qemu
--rtems-tools=/home/varodek/development/rtems/5
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples
Python: 3.7.3 (default, Mar 26 2019, 21:43:19) [GCC 8.2.1 20181127]
Host: Linux-5.0.5-arch1-1-ARCH-x86_64-with-arch (Linux varodek
5.0.5-arch1-1-ARCH #1 SMP PREEMPT Wed Mar 27 17:53:10 UTC 2019 x86_64 )
[ 1/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 |
arm/xilinx_zynq_a9_qemu: base_sp.exe
[ 4/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 |
arm/xilinx_zynq_a9_qemu: cxx_iostream.exe
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/base_sp.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/base_sp.exe:
exit-code:2
warning: switched to dry run due to errors
[ 3/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:1 W:0 |
arm/xilinx_zynq_a9_qemu: cdtest.exe
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/cxx_iostream.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/cxx_iostream.exe:
exit-code:2
warning: switched to dry run due to errors
[ 2/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:2 W:0 |
arm/xilinx_zynq_a9_qemu: capture.exe
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/cdtest.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/cdtest.exe:
exit-code:2
warning: switched to dry run due to errors
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/capture.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/capture.exe:
exit-code:2
warning: switched to dry run due to errors
[ 1/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 |
arm/xilinx_zynq_a9_qemu: base_sp.exe
Result: invalid Time: 0:00:00.027521 base_sp.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/base_sp.exe
[ 2/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:2 W:0 |
arm/xilinx_zynq_a9_qemu: capture.exe
Result: invalid Time: 0:00:00.005902 capture.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/capture.exe
[ 3/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:1 W:0 |
arm/xilinx_zynq_a9_qemu: cdtest.exe
Result: invalid Time: 0:00:00.021361 cdtest.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/cdtest.exe
[ 4/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 |
arm/xilinx_zynq_a9_qemu: cxx_iostream.exe
Result: invalid Time: 0:00:00.027792 cxx_iostream.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/cxx_iostream.exe
[ 5/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 |
arm/xilinx_zynq_a9_qemu: fileio.exe
[ 7/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 |
arm/xilinx_zynq_a9_qemu: minimum.exe
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/fileio.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/fileio.exe:
exit-code:2
warning: switched to dry run due to errors
[ 6/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:5 W:0 |
arm/xilinx_zynq_a9_qemu: hello.exe
[ 8/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:5 W:0 |
arm/xilinx_zynq_a9_qemu: nsecs.exe
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/minimum.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/minimum.exe:
exit-code:2
warning: switched to dry run due to errors
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe:
exit-code:2
warning: switched to dry run due to errors
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/nsecs.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/nsecs.exe:
exit-code:2
warning: switched to dry run due to errors
[ 5/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 |
arm/xilinx_zynq_a9_qemu: fileio.exe
Result: invalid Time: 0:00:00.041632 fileio.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/fileio.exe
[ 6/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:5 W:0 |
arm/xilinx_zynq_a9_qemu: hello.exe
Result: invalid Time: 0:00:00.017531 hello.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe
[ 7/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 |
arm/xilinx_zynq_a9_qemu: minimum.exe
[ 8/11] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:5 W:0 |
arm/xilinx_zynq_a9_qemu: nsecs.exe
Result: invalid Time: 0:00:00.010854 nsecs.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/nsecs.exe
[ 9/11] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 |
arm/xilinx_zynq_a9_qemu: paranoia.exe
[11/11] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 |
arm/xilinx_zynq_a9_qemu: unlimited.exe
[10/11] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 |
arm/xilinx_zynq_a9_qemu: ticker.exe
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/paranoia.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/paranoia.exe:
exit-code:2
warning: switched to dry run due to errors
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/unlimited.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/unlimited.exe:
exit-code:2
warning: switched to dry run due to errors
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/ticker.exe:
exit-code:2
error: qemu.cfg:84: execute failed: qemu-system-arm -no-reboot -serial null
-serial mon:stdio -nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/ticker.exe:
exit-code:2
warning: switched to dry run due to errors
[ 9/11] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 |
arm/xilinx_zynq_a9_qemu: paranoia.exe
Result: invalid Time: 0:00:00.036784 paranoia.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/paranoia.exe
[10/11] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 |
arm/xilinx_zynq_a9_qemu: ticker.exe
Result: invalid Time: 0:00:00.009978 ticker.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/ticker.exe
[11/11] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 |
arm/xilinx_zynq_a9_qemu: unlimited.exe
Result: invalid Time: 0:00:00.017402 unlimited.exe
=> run: qemu-system-arm -no-reboot -serial null -serial mon:stdio
-nographic -net none -M xilinx-zynq-a9 -m 256M -kernel
/home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/unlimited.exe
Passed: 1
Failed: 0
User Input: 0
Expected Fail: 0
Indeterminate: 0
Benchmark: 0
Timeout: 0
Invalid: 10
Wrong Version: 0
Wrong Build: 0
Wrong Tools: 0
-----------------
Total: 11
Invalid:
base_sp.exe
cxx_iostream.exe
cdtest.exe
capture.exe
fileio.exe
hello.exe
nsecs.exe
paranoia.exe
unlimited.exe
ticker.exe
Average test time: 0:00:00.095631
Testing time : 0:00:01.051941
.
.
Why the executables are not able to execute?
.
Thank you
Vaibhav Gupta
On Wed, Apr 24, 2019 at 1:26 PM Vaibhav Gupta <vaibhavgupta40 at gmail.com>
wrote:
> Hello,
> .
> I have successfully build RTEMS for SPARC erc32, and have run the
> testsuites, before.
> This time I have build RTEMS for ARM xilinx_zynq_a9_qemu
> But when I try to run the hello world example, it gives me following error:
> .
> $ arm-rtems5-gdb
> ~/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe
>
> GNU gdb (GDB) 8.2.1
> Copyright (C) 2018 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "--host=x86_64-linux-gnu --target=arm-rtems5".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from
> /home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe...done.
> (gdb) tar sim
> Connected to the simulator.
> (gdb) load
> Loading section .start, size 0xad0 lma 0x0
> Loading section .text, size 0x1a5f8 lma 0xb00
> Loading section .init, size 0xc lma 0x1b0f8
> Loading section .fini, size 0xc lma 0x1b104
> Loading section .rodata, size 0x1694 lma 0x1b110
> Loading section .ARM.exidx, size 0x8 lma 0x1c7a4
> Loading section .eh_frame, size 0x4 lma 0x1c7ac
> Loading section .init_array, size 0x4 lma 0x1c7b0
> Loading section .fini_array, size 0x4 lma 0x1c7b4
> Loading section .rtemsroset, size 0x38 lma 0x1c7b8
> Loading section .data, size 0x66c lma 0x101000
> Start address 0x40
> Transfer rate: 946528 bits in <1 sec.
> (gdb) r
> Starting program:
> /home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe
>
> Unknown machine type '19'; please update sim_create_inferior.
> [Inferior 1 (process 42000) exited with code 060]
> .
> .
> I am not able to analyze the problem, why is it showing Unknown machine
> type? The test runs were successful for SPARC.
> .
> Thank You
> Vaibhav Gupta
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190424/58a9acdb/attachment-0001.html>
More information about the devel
mailing list