<div dir="ltr"><div>I got the test to run but there were tons of errors. I haven't touched any of the source or really dived into it. <br></div><div><br></div><div>RTEMS Testing - Tester, 5.0.not_released<br> Command Line: /home/zakonrockets/development/rtems/5/bin/rtems-test --rtems-tools=/home/zakonrockets/development/rtems/5 --rtems-bsp=pc-qemu /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites --rtems-prefix=/home/zakonrockets/development/rtems/5<br> Host: Linux zakonrockets-Inspiron-15-7000-Gaming 5.3.0-64-generic #58-Ubuntu SMP Fri Jul 10 19:33:51 UTC 2020 x86_64<br> Python: 3.7.5 (default, Apr 19 2020, 20:18:17) [GCC 9.2.1 20191008]<br>Host: Linux-5.3.0-64-generic-x86_64-with-Ubuntu-19.10-eoan (Linux zakonrockets-Inspiron-15-7000-Gaming 5.3.0-64-generic #58-Ubuntu SMP Fri Jul 10 19:33:51 UTC 2020 x86_64 x86_64)<br>[ 3/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: cdtest.exe<br>[ 6/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: hello.exe<br>[ 4/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: cxx_iostream.exe<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/hello.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/hello.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cxx_iostream.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cdtest.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cxx_iostream.exe: exit-code:2<br>warning: switched to dry run due to errors<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cdtest.exe: exit-code:2<br>warning: switched to dry run due to errors<br>warning: switched to dry run due to errors<br>[ 2/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:3 W:0 | i386/pc686: capture.exe<br>[ 8/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:3 W:0 | i386/pc686: minimum.exe<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/capture.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/capture.exe: exit-code:2<br>warning: switched to dry run due to errors<br>[ 7/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: loopback.exe<br>[ 1/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: base_sp.exe<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/minimum.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/minimum.exe: exit-code:2<br>warning: switched to dry run due to errors<br>[ 5/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: fileio.exe<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/loopback.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/loopback.exe: exit-code:2<br>warning: switched to dry run due to errors<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/base_sp.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/base_sp.exe: exit-code:2<br>warning: switched to dry run due to errors<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/fileio.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/fileio.exe: exit-code:2<br>warning: switched to dry run due to errors<br>[ 1/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: base_sp.exe<br>Result: invalid Time: 0:00:00.017795 base_sp.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/base_sp.exe<br>[ 2/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:3 W:0 | i386/pc686: capture.exe<br>Result: invalid Time: 0:00:00.014453 capture.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/capture.exe<br>[ 3/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: cdtest.exe<br>Result: invalid Time: 0:00:00.054058 cdtest.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cdtest.exe<br>[ 4/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: cxx_iostream.exe<br>Result: invalid Time: 0:00:00.026283 cxx_iostream.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cxx_iostream.exe<br>[ 5/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: fileio.exe<br>Result: invalid Time: 0:00:00.010072 fileio.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/fileio.exe<br>[ 6/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: hello.exe<br>Result: invalid Time: 0:00:00.035287 hello.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/hello.exe<br>[ 7/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: loopback.exe<br>Result: invalid Time: 0:00:00.029105 loopback.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/loopback.exe<br>[ 8/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:3 W:0 | i386/pc686: minimum.exe<br>[10/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 | i386/pc686: paranoia.exe<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/paranoia.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/paranoia.exe: exit-code:2<br>warning: switched to dry run due to errors<br>[13/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:8 W:0 | i386/pc686: unlimited.exe<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/unlimited.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/unlimited.exe: exit-code:2<br>warning: switched to dry run due to errors<br>[11/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:9 W:0 | i386/pc686: pppd.exe<br>[12/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:9 W:0 | i386/pc686: ticker.exe<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/pppd.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/pppd.exe: exit-code:2<br>warning: switched to dry run due to errors<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/ticker.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/ticker.exe: exit-code:2<br>warning: switched to dry run due to errors<br>[ 9/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:11 W:0 | i386/pc686: nsecs.exe<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/nsecs.exe: exit-code:2<br>error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/nsecs.exe: exit-code:2<br>warning: switched to dry run due to errors<br>[ 9/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:11 W:0 | i386/pc686: nsecs.exe<br>Result: invalid Time: 0:00:00.004524 nsecs.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/nsecs.exe<br>[10/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 | i386/pc686: paranoia.exe<br>Result: invalid Time: 0:00:00.006776 paranoia.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/paranoia.exe<br>[11/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:9 W:0 | i386/pc686: pppd.exe<br>Result: invalid Time: 0:00:00.018013 pppd.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/pppd.exe<br>[12/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:9 W:0 | i386/pc686: ticker.exe<br>Result: invalid Time: 0:00:00.008560 ticker.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/ticker.exe<br>[13/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:8 W:0 | i386/pc686: unlimited.exe<br>Result: invalid Time: 0:00:00.006357 unlimited.exe<br>=> run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/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: 12<br>Wrong Version: 0<br>Wrong Build: 0<br>Wrong Tools: 0<br>-----------------<br>Total: 13<br>Invalid:<br> cdtest.exe<br> hello.exe<br> cxx_iostream.exe<br> capture.exe<br> loopback.exe<br> base_sp.exe<br> fileio.exe<br> paranoia.exe<br> unlimited.exe<br> pppd.exe<br> ticker.exe<br> nsecs.exe<br>Average test time: 0:00:00.060904<br>Testing time : 0:00:00.791756</div><div><br></div><div>regards <br></div><div>zack<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Il giorno lun 10 ago 2020 alle ore 21:51 Vijay Kumar Banerjee <<a href="mailto:vijay@rtems.org">vijay@rtems.org</a>> ha scritto:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Aug 11, 2020 at 7:14 AM Zacchaeus Liang <<a href="mailto:zliang111@gmail.com" target="_blank">zliang111@gmail.com</a>> wrote:<br>
><br>
> Do i add it as an argument and what is the argument name (didn't reply all sorry?<br>
><br>
You don't need a separate option just add the location with the<br>
command line you're using. Something like this:<br>
<br>
rtems-test \<br>
--rtems-tools=$HOME/development/rtems/5 \<br>
--rtems-bsp=lpc-qemu \<br>
$HOME/development/rtems/kernel/pc386/i386-rtems5/c/pc386/testsuites/samples<br>
<br>
> Thanks<br>
> zack<br>
><br>
> Il giorno lun 10 ago 2020 alle ore 21:31 Vijay Kumar Banerjee <<a href="mailto:vijay@rtems.org" target="_blank">vijay@rtems.org</a>> ha scritto:<br>
>><br>
>> On Tue, Aug 11, 2020 at 6:57 AM Zacchaeus Liang <<a href="mailto:zliang111@gmail.com" target="_blank">zliang111@gmail.com</a>> wrote:<br>
>> ><br>
>> > It says that there is not supplied executable<br>
>> Looks like you're in the right direction.<br>
>><br>
>> Add the location to the samples directory to the command line and<br>
>> it'll work. The location will be in the bsp build location.<br>
>> something like pc-386/i386-rtems5/c/pc386/testsuites/samples<br>
>><br>
>><br>
>> Best regards,<br>
>> Vijay<br>
>> > zack<br>
>> ><br>
>> > Il giorno lun 10 ago 2020 alle ore 21:10 Vijay Kumar Banerjee <<a href="mailto:vijay@rtems.org" target="_blank">vijay@rtems.org</a>> ha scritto:<br>
>> >><br>
>> >> Hi Zack,<br>
>> >><br>
>> >> I have posted a comment below...<br>
>> >><br>
>> >> On Tue, Aug 11, 2020 at 5:54 AM Zacchaeus Liang <<a href="mailto:zliang111@gmail.com" target="_blank">zliang111@gmail.com</a>> wrote:<br>
>> >> ><br>
>> >> > I tried to add the prefix and i had the prefix with this<br>
>> >> > rtems-test --rtems-bsp=i386-rtems5 --rtems-tools=$HOME/development/rtems/5 --rtems-prefix=$HOME/development/rtems/5<br>
>> >> > i get the same error. Was the prefix correct based on the instructions?<br>
>> >> ><br>
>> >> > Thanks<br>
>> >> > zack<br>
>> >> ><br>
>> >> > Il giorno lun 10 ago 2020 alle ore 00:31 Niteesh G. S. <<a href="mailto:niteesh.gs@gmail.com" target="_blank">niteesh.gs@gmail.com</a>> ha scritto:<br>
>> >> >><br>
>> >> >> Hello,<br>
>> >> >><br>
>> >> >>><br>
>> >> >>> Hello,<br>
>> >> >>><br>
>> >> >>> I'm Zack and I'm currently finishing up my university degree in comp sci.<br>
>> >> >>> I'm really interested in aviation and aerospace systems. I want to get into<br>
>> >> >>> rtems to learn more about rtos and contribute to rtems !<br>
>> >> >>><br>
>> >> >>> Currently I'm trying to build rtems and test and bsp. Hoping to then<br>
>> >> >>> contribute. I followed one of you GSOC student's tutorials and tried to go<br>
>> >> >>> ahead. I'm trying to build the test the bsp right now.<br>
>> >> >>> here is his blog post<br>
>> >> >>> <a href="https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902" rel="noreferrer" target="_blank">https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902</a><br>
>> >> >>> I tried to run the bsp testing like this and it says the ini file is not<br>
>> >> >>> found. Is this the right bsp argument? After this i'm going to try to<br>
>> >> >>> build an application and would like to know the right path to install it.<br>
>> >> >>> Any tips on looking for easy things to learn to patch? Thanks in advance i<br>
>> >> >>> know it's a handful for questions!<br>
>> >> >>><br>
>> >> >>><br>
>> >> >>><br>
>> >> >>> zakonrockets@zakonrockets-Inspiron-15-7000-Gaming:~/development/rtems/kernels-5/pcp-386$<br>
>> >> >>> rtems-test --rtems-bsp=i386-rtems5<br>
>> >> >>> --rtems-tools=$HOME/development/rtems/5<br>
>> >> >>> RTEMS Testing - Tester, 5.0.not_released<br>
>> >> >>> Command Line: /home/zakonrockets/development/rtems/5/bin/rtems-test<br>
>> >> >>> --rtems-bsp=i386-rtems5<br>
>> >><br>
>> >> --rtems-bsp option should have the bsp and not the architecture.<br>
>> >> Please try --rtems-bsp=pc-qemu<br>
</blockquote></div>