<div dir="ltr"><div dir="ltr"><br></div><div>How is this dealt with in sp01 and samples/ticker in the main tree?</div><div><br></div><div>I suppose we need a patch for the rtems-examples repository.</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 9, 2020 at 8:34 AM Alan Cudmore <<a href="mailto:alan.cudmore@gmail.com">alan.cudmore@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">Hi Sebastian,<br>
Thank you for reproducing this. I added the floating point attribute<br>
to my demo tasks and it works as expected.<br>
I was just about to try Chris' suggestion of using GDB when I saw this message.<br>
<br>
I encountered the same problem building the examples with waf.<br>
<br>
Regards,<br>
Alan<br>
<br>
On Thu, Apr 9, 2020 at 7:51 AM Sebastian Huber<br>
<<a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a>> wrote:<br>
><br>
> Hello Alan,<br>
><br>
> On 08/04/2020 17:48, Alan Cudmore wrote:<br>
> > Regarding the LEON3: I am noticing something with the release that I<br>
> > don't understand yet.<br>
> ><br>
> > I am able to build and run a number of ARM BSPs including raspberrypi,<br>
> > raspberrypi2, beagleboneblack, and xlinx_zynq_a9_qemu<br>
> > When I build my application for the leon3, most of it appears to work,<br>
> > but I have a task demo that crashes when I try to print a variable<br>
> > that is on the task stack. ( task ID, similar to what ticker does )<br>
> > I went back and ran a number of the testsuite programs on both my<br>
> > patched QEMU and sparc-rtems5-sis with no problems.<br>
> > I then cloned the latest rtems-examples git repository and built the<br>
> > ticker examples using the (obsolete) Makefile. When built this way,<br>
> > the ticker program crashes as well on both QEMU and SIS.<br>
> ><br>
> > I'm trying to narrow down the differences by comparing the flags used<br>
> > to build the testsuite in the build tree vs. my applications and the<br>
> > rtems-examples repository.<br>
> ><br>
> > Should I try building the examples with waf?<br>
><br>
> I was able to reproduce this issue. It seems to be a problem with the<br>
> use of the FPU in a non-FP task:<br>
><br>
> Program received signal SIGTERM, Terminated.<br>
> syscall () at<br>
> /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/syscall.S:44<br>
> 44 ta 0 ! syscall 1, halt with<br>
> %g1,%g2,%g3 info<br>
> (gdb) bt<br>
> #0 syscall () at<br>
> /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/syscall.S:44<br>
> #1 0x4000f888 in _User_extensions_Fatal_visitor (executing=0x0,<br>
> arg=0x26, callouts=0x40020ca8 <_User_extensions_List+4>) at<br>
> /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/userextiterate.c:131<br>
> #2 0x4001cdc4 in _CPU_Fatal_halt (source=10, source@entry=0, error=0,<br>
> error@entry=38) at<br>
> /home/EB/sebastian_h/src/rtems/c/src/lib/libbsp/sparc/leon3/../../../../../../bsps/sparc/leon3/start/bsp_fatal_halt.c:33<br>
> #3 0x4000fb68 in _Terminate<br>
> (the_source=the_source@entry=INTERNAL_ERROR_CORE, the_error=38,<br>
> the_error@entry=0) at<br>
> /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/interr.c:44<br>
> #4 0x4000fb7c in _Internal_error (core_error=0,<br>
> core_error@entry=INTERNAL_ERROR_ILLEGAL_USE_OF_FLOATING_POINT_UNIT) at<br>
> /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/interr.c:52<br>
> #5 0x40001664 in bsp_spurious_handler (trap=260, isf=0x40028518) at<br>
> /home/EB/sebastian_h/src/rtems/c/src/lib/libbsp/sparc/leon3/../../../../../../bsps/sparc/leon3/start/spurious.c:124<br>
> #6 0x40012390 in pil_fixed () at<br>
> /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/cpu_asm.S:592<br>
><br>
> It would be good to add support for the RTEMS Tester to the examples.<br>
><br>
> I was not able to build the examples with waf:<br>
><br>
> Waf: Entering directory<br>
> `/home/EB/sebastian_h/src/rtems-examples/build/sparc-rtems5-leon3'<br>
> [ 1/14] Compiling hello/hello_world_c/test.c<br>
> [ 2/14] Compiling hello/posix_hello_world/test.c<br>
> [ 3/14] Compiling hello/both_hello/test.c<br>
> [ 4/14] Compiling hello/both_hello/test.c<br>
> [ 5/14] Compiling hello/both_hello/test.c<br>
> [ 6/14] Linking<br>
> build/sparc-rtems5-leon3/hello/posix_hello_world/posix_hello.exe<br>
> [ 7/14] Linking build/sparc-rtems5-leon3/hello/hello_world_c/hello.exe<br>
> [ 8/14] Compiling build/sparc-rtems5-leon3/hello/both_hello/test.c.2.o<br>
> [ 9/14] Compiling build/sparc-rtems5-leon3/hello/both_hello/test.c.1.o<br>
> [10/14] Linking build/sparc-rtems5-leon3/hello/both_hello/both_hello.exe<br>
> [11/14] Compiling gdb/overwrite/rtems_init.c<br>
> [12/14] Compiling gdb/overwrite/overwrite.c<br>
> [13/14] Compiling filesystem/fat_ramdisk/rootfs/shell-init<br>
> [14/14] Linking build/sparc-rtems5-leon3/gdb/overwrite/overwrite.exe<br>
> [15/15] Compiling<br>
> build/sparc-rtems5-leon3/filesystem/fat_ramdisk/rootfs/shell-init<br>
> [16/16] Compiling<br>
> build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root.tar<br>
> [17/29] Compiling<br>
> build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root-tar.c<br>
> [18/29] Compiling filesystem/fat_ramdisk/init.c<br>
> [19/29] Compiling<br>
> build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root-tar.c<br>
> [20/29] Compiling filesystem/fat_ramdisk/init.c<br>
> [21/29] Compiling classic_api/classic_signal/test.c<br>
> [22/29] Compiling classic_api/triple_period/tasks.c<br>
> Waf: Leaving directory<br>
> `/home/EB/sebastian_h/src/rtems-examples/build/sparc-rtems5-leon3'<br>
> Build failed<br>
> Traceback (most recent call last):<br>
> File<br>
> "/home/EB/sebastian_h/src/rtems-examples/.waf-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py",<br>
> line 190, in process<br>
> self.post_run()<br>
> File "/home/EB/sebastian_h/src/rtems-examples/rtems_waf/gccdeps.py",<br>
> line 144, in post_run<br>
> raise ValueError('could not find %r for %r' % (x, self))<br>
> ValueError: could not find ['filesystem', 'fat_ramdisk',<br>
> 'fs-root-tar.h'] for<br>
> {task 140228625202304: c init.c -> init.c.6.o}<br>
><br>
> Traceback (most recent call last):<br>
> File<br>
> "/home/EB/sebastian_h/src/rtems-examples/.waf-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py",<br>
> line 190, in process<br>
> self.post_run()<br>
> File "/home/EB/sebastian_h/src/rtems-examples/rtems_waf/gccdeps.py",<br>
> line 144, in post_run<br>
> raise ValueError('could not find %r for %r' % (x, self))<br>
> ValueError: could not find ['filesystem', 'fat_ramdisk',<br>
> 'fs-root-tar.h'] for<br>
> {task 140228625202904: c init.c -> init.c.5.o}<br>
><br>
> This used to work some days ago. Maybe commit<br>
> 341747b0a03ffce9082ed84a94905cd9a3ea32fc cased this issue?<br>
><br>
><br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div></div></div>