<div dir="ltr"><div dir="ltr"><div>Hello,</div><div>I even tried to run rtems-test for the testsuites/samples for ARM Architecture,</div><div><br></div><div><span style="font-family:monospace,monospace">$ 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</span></div><div><span style="font-family:monospace,monospace">RTEMS Testing - Tester, 5.0.not_released<br> 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<br> Python: 3.7.3 (default, Mar 26 2019, 21:43:19) [GCC 8.2.1 20181127]<br>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 )<br>[ 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<br>[ 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<br>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<br>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<br>warning: switched to dry run due to errors<br>[ 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<br>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<br>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<br>warning: switched to dry run due to errors<br>[ 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<br>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<br>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<br>warning: switched to dry run due to errors<br>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<br>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<br>warning: switched to dry run due to errors<br>[ 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<br>Result: invalid Time: 0:00:00.027521 base_sp.exe<br>=> 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<br>[ 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<br>Result: invalid Time: 0:00:00.005902 capture.exe<br>=> 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<br>[ 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<br>Result: invalid Time: 0:00:00.021361 cdtest.exe<br>=> 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<br>[ 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<br>Result: invalid Time: 0:00:00.027792 cxx_iostream.exe<br>=> 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<br>[ 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<br>[ 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<br>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<br>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<br>warning: switched to dry run due to errors<br>[ 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<br>[ 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<br>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<br>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<br>warning: switched to dry run due to errors<br>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<br>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<br>warning: switched to dry run due to errors<br>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<br>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<br>warning: switched to dry run due to errors<br>[ 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<br>Result: invalid Time: 0:00:00.041632 fileio.exe<br>=> 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<br>[ 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<br>Result: invalid Time: 0:00:00.017531 hello.exe<br>=> 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<br>[ 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<br>[ 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<br>Result: invalid Time: 0:00:00.010854 nsecs.exe<br>=> 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<br>[ 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<br>[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<br>[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<br>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<br>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<br>warning: switched to dry run due to errors<br>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<br>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<br>warning: switched to dry run due to errors<br>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<br>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<br>warning: switched to dry run due to errors<br>[ 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<br>Result: invalid Time: 0:00:00.036784 paranoia.exe<br>=> 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<br>[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<br>Result: invalid Time: 0:00:00.009978 ticker.exe<br>=> 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<br>[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<br>Result: invalid Time: 0:00:00.017402 unlimited.exe<br>=> 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<br><br>Passed: 1<br>Failed: 0<br>User Input: 0<br>Expected Fail: 0<br>Indeterminate: 0<br>Benchmark: 0<br>Timeout: 0<br>Invalid: 10<br>Wrong Version: 0<br>Wrong Build: 0<br>Wrong Tools: 0<br>-----------------<br>Total: 11<br>Invalid:<br> base_sp.exe<br> cxx_iostream.exe<br> cdtest.exe<br> capture.exe<br> fileio.exe<br> hello.exe<br> nsecs.exe<br> paranoia.exe<br> unlimited.exe<br> ticker.exe<br>Average test time: 0:00:00.095631<br>Testing time : 0:00:01.051941</span><br>.</div><div>.</div><div>Why the executables are not able to execute?</div><div>.</div><div>Thank you</div><div>Vaibhav Gupta<br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 24, 2019 at 1:26 PM Vaibhav Gupta <<a href="mailto:vaibhavgupta40@gmail.com" target="_blank">vaibhavgupta40@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Hello,</div><div>.<br></div><div>I have successfully build RTEMS for SPARC erc32, and have run the testsuites, before.</div><div>This time I have build RTEMS for ARM xilinx_zynq_a9_qemu</div><div>But when I try to run the hello world example, it gives me following error:</div><div>.</div><div><span style="font-family:monospace,monospace">$ arm-rtems5-gdb ~/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe<br></span></div><div><span style="font-family:monospace,monospace"><br></span></div><div><span style="font-family:monospace,monospace">GNU gdb (GDB) 8.2.1<br>Copyright (C) 2018 Free Software Foundation, Inc.<br>License GPLv3+: GNU GPL version 3 or later <<a href="http://gnu.org/licenses/gpl.html" target="_blank">http://gnu.org/licenses/gpl.html</a>><br>This is free software: you are free to change and redistribute it.<br>There is NO WARRANTY, to the extent permitted by law.<br>Type "show copying" and "show warranty" for details.<br>This GDB was configured as "--host=x86_64-linux-gnu --target=arm-rtems5".<br>Type "show configuration" for configuration details.<br>For bug reporting instructions, please see:<br><<a href="http://www.gnu.org/software/gdb/bugs/" target="_blank">http://www.gnu.org/software/gdb/bugs/</a>>.<br>Find the GDB manual and other documentation resources online at:<br> <<a href="http://www.gnu.org/software/gdb/documentation/" target="_blank">http://www.gnu.org/software/gdb/documentation/</a>>.<br><br>For help, type "help".<br>Type "apropos word" to search for commands related to "word"...<br>Reading symbols from /home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe...done.<br>(gdb) tar sim<br>Connected to the simulator.<br>(gdb) load<br>Loading section .start, size 0xad0 lma 0x0<br>Loading section .text, size 0x1a5f8 lma 0xb00<br>Loading section .init, size 0xc lma 0x1b0f8<br>Loading section .fini, size 0xc lma 0x1b104<br>Loading section .rodata, size 0x1694 lma 0x1b110<br>Loading section .ARM.exidx, size 0x8 lma 0x1c7a4<br>Loading section .eh_frame, size 0x4 lma 0x1c7ac<br>Loading section .init_array, size 0x4 lma 0x1c7b0<br>Loading section .fini_array, size 0x4 lma 0x1c7b4<br>Loading section .rtemsroset, size 0x38 lma 0x1c7b8<br>Loading section .data, size 0x66c lma 0x101000<br>Start address 0x40<br>Transfer rate: 946528 bits in <1 sec.<br>(gdb) r<br>Starting program: /home/varodek/development/rtems/kernel/xilinx_zynq_a9_qemu/arm-rtems5/c/xilinx_zynq_a9_qemu/testsuites/samples/hello.exe <br>Unknown machine type '19'; please update sim_create_inferior.<br>[Inferior 1 (process 42000) exited with code 060]</span><br>.</div><div>.</div><div>I am not able to analyze the problem, why is it showing Unknown machine type? The test runs were successful for SPARC.</div><div>.</div><div>Thank You <br></div><div>Vaibhav Gupta<br></div></div></div></div></div>
</blockquote></div>