Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
How is this dealt with in sp01 and samples/ticker in the main tree? I suppose we need a patch for the rtems-examples repository. On Thu, Apr 9, 2020 at 8:34 AM Alan Cudmore wrote: > Hi Sebastian, > Thank you for reproducing this. I added the floating point attribute > to my demo tasks and it works as expected. > I was just about to try Chris' suggestion of using GDB when I saw this > message. > > I encountered the same problem building the examples with waf. > > Regards, > Alan > > On Thu, Apr 9, 2020 at 7:51 AM Sebastian Huber > wrote: > > > > Hello Alan, > > > > On 08/04/2020 17:48, Alan Cudmore wrote: > > > Regarding the LEON3: I am noticing something with the release that I > > > don't understand yet. > > > > > > I am able to build and run a number of ARM BSPs including raspberrypi, > > > raspberrypi2, beagleboneblack, and xlinx_zynq_a9_qemu > > > When I build my application for the leon3, most of it appears to work, > > > but I have a task demo that crashes when I try to print a variable > > > that is on the task stack. ( task ID, similar to what ticker does ) > > > I went back and ran a number of the testsuite programs on both my > > > patched QEMU and sparc-rtems5-sis with no problems. > > > I then cloned the latest rtems-examples git repository and built the > > > ticker examples using the (obsolete) Makefile. When built this way, > > > the ticker program crashes as well on both QEMU and SIS. > > > > > > I'm trying to narrow down the differences by comparing the flags used > > > to build the testsuite in the build tree vs. my applications and the > > > rtems-examples repository. > > > > > > Should I try building the examples with waf? > > > > I was able to reproduce this issue. It seems to be a problem with the > > use of the FPU in a non-FP task: > > > > Program received signal SIGTERM, Terminated. > > syscall () at > > > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/syscall.S:44 > > 44 ta 0 ! syscall 1, halt with > > %g1,%g2,%g3 info > > (gdb) bt > > #0 syscall () at > > > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/syscall.S:44 > > #1 0x4000f888 in _User_extensions_Fatal_visitor (executing=0x0, > > arg=0x26, callouts=0x40020ca8 <_User_extensions_List+4>) at > > > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/userextiterate.c:131 > > #2 0x4001cdc4 in _CPU_Fatal_halt (source=10, source@entry=0, error=0, > > error@entry=38) at > > > /home/EB/sebastian_h/src/rtems/c/src/lib/libbsp/sparc/leon3/../../../../../../bsps/sparc/leon3/start/bsp_fatal_halt.c:33 > > #3 0x4000fb68 in _Terminate > > (the_source=the_source@entry=INTERNAL_ERROR_CORE, the_error=38, > > the_error@entry=0) at > > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/interr.c:44 > > #4 0x4000fb7c in _Internal_error (core_error=0, > > core_error@entry=INTERNAL_ERROR_ILLEGAL_USE_OF_FLOATING_POINT_UNIT) at > > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/interr.c:52 > > #5 0x40001664 in bsp_spurious_handler (trap=260, isf=0x40028518) at > > > /home/EB/sebastian_h/src/rtems/c/src/lib/libbsp/sparc/leon3/../../../../../../bsps/sparc/leon3/start/spurious.c:124 > > #6 0x40012390 in pil_fixed () at > > > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/cpu_asm.S:592 > > > > It would be good to add support for the RTEMS Tester to the examples. > > > > I was not able to build the examples with waf: > > > > Waf: Entering directory > > `/home/EB/sebastian_h/src/rtems-examples/build/sparc-rtems5-leon3' > > [ 1/14] Compiling hello/hello_world_c/test.c > > [ 2/14] Compiling hello/posix_hello_world/test.c > > [ 3/14] Compiling hello/both_hello/test.c > > [ 4/14] Compiling hello/both_hello/test.c > > [ 5/14] Compiling hello/both_hello/test.c > > [ 6/14] Linking > > build/sparc-rtems5-leon3/hello/posix_hello_world/posix_hello.exe > > [ 7/14] Linking build/sparc-rtems5-leon3/hello/hello_world_c/hello.exe > > [ 8/14] Compiling build/sparc-rtems5-leon3/hello/both_hello/test.c.2.o > > [ 9/14] Compiling build/sparc-rtems5-leon3/hello/both_hello/test.c.1.o > > [10/14] Linking build/sparc-rtems5-leon3/hello/both_hello/both_hello.exe > > [11/14] Compiling gdb/overwrite/rtems_init.c > > [12/14] Compiling gdb/overwrite/overwrite.c > > [13/14] Compiling filesystem/fat_ramdisk/rootfs/shell-init > > [14/14] Linking build/sparc-rtems5-leon3/gdb/overwrite/overwrite.exe > > [15/15] Compiling > > build/sparc-rtems5-leon3/filesystem/fat_ramdisk/rootfs/shell-init > > [16/16] Compiling > > build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root.tar > > [17/29] Compiling > > build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root-tar.c > > [18/29] Compiling filesystem/fat_ramdisk/init.c > > [19/29] Compiling > > build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root-tar.c > > [20/29] Compiling filesystem/fat_ramdisk/init.c > > [21/29] Compiling classic_api/classic_signal/test.c > > [22/29] Compiling classic_api/triple_period/tas
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
Hi Sebastian, Thank you for reproducing this. I added the floating point attribute to my demo tasks and it works as expected. I was just about to try Chris' suggestion of using GDB when I saw this message. I encountered the same problem building the examples with waf. Regards, Alan On Thu, Apr 9, 2020 at 7:51 AM Sebastian Huber wrote: > > Hello Alan, > > On 08/04/2020 17:48, Alan Cudmore wrote: > > Regarding the LEON3: I am noticing something with the release that I > > don't understand yet. > > > > I am able to build and run a number of ARM BSPs including raspberrypi, > > raspberrypi2, beagleboneblack, and xlinx_zynq_a9_qemu > > When I build my application for the leon3, most of it appears to work, > > but I have a task demo that crashes when I try to print a variable > > that is on the task stack. ( task ID, similar to what ticker does ) > > I went back and ran a number of the testsuite programs on both my > > patched QEMU and sparc-rtems5-sis with no problems. > > I then cloned the latest rtems-examples git repository and built the > > ticker examples using the (obsolete) Makefile. When built this way, > > the ticker program crashes as well on both QEMU and SIS. > > > > I'm trying to narrow down the differences by comparing the flags used > > to build the testsuite in the build tree vs. my applications and the > > rtems-examples repository. > > > > Should I try building the examples with waf? > > I was able to reproduce this issue. It seems to be a problem with the > use of the FPU in a non-FP task: > > Program received signal SIGTERM, Terminated. > syscall () at > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/syscall.S:44 > 44 ta 0 ! syscall 1, halt with > %g1,%g2,%g3 info > (gdb) bt > #0 syscall () at > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/syscall.S:44 > #1 0x4000f888 in _User_extensions_Fatal_visitor (executing=0x0, > arg=0x26, callouts=0x40020ca8 <_User_extensions_List+4>) at > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/userextiterate.c:131 > #2 0x4001cdc4 in _CPU_Fatal_halt (source=10, source@entry=0, error=0, > error@entry=38) at > /home/EB/sebastian_h/src/rtems/c/src/lib/libbsp/sparc/leon3/../../../../../../bsps/sparc/leon3/start/bsp_fatal_halt.c:33 > #3 0x4000fb68 in _Terminate > (the_source=the_source@entry=INTERNAL_ERROR_CORE, the_error=38, > the_error@entry=0) at > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/interr.c:44 > #4 0x4000fb7c in _Internal_error (core_error=0, > core_error@entry=INTERNAL_ERROR_ILLEGAL_USE_OF_FLOATING_POINT_UNIT) at > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/interr.c:52 > #5 0x40001664 in bsp_spurious_handler (trap=260, isf=0x40028518) at > /home/EB/sebastian_h/src/rtems/c/src/lib/libbsp/sparc/leon3/../../../../../../bsps/sparc/leon3/start/spurious.c:124 > #6 0x40012390 in pil_fixed () at > /home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/cpu_asm.S:592 > > It would be good to add support for the RTEMS Tester to the examples. > > I was not able to build the examples with waf: > > Waf: Entering directory > `/home/EB/sebastian_h/src/rtems-examples/build/sparc-rtems5-leon3' > [ 1/14] Compiling hello/hello_world_c/test.c > [ 2/14] Compiling hello/posix_hello_world/test.c > [ 3/14] Compiling hello/both_hello/test.c > [ 4/14] Compiling hello/both_hello/test.c > [ 5/14] Compiling hello/both_hello/test.c > [ 6/14] Linking > build/sparc-rtems5-leon3/hello/posix_hello_world/posix_hello.exe > [ 7/14] Linking build/sparc-rtems5-leon3/hello/hello_world_c/hello.exe > [ 8/14] Compiling build/sparc-rtems5-leon3/hello/both_hello/test.c.2.o > [ 9/14] Compiling build/sparc-rtems5-leon3/hello/both_hello/test.c.1.o > [10/14] Linking build/sparc-rtems5-leon3/hello/both_hello/both_hello.exe > [11/14] Compiling gdb/overwrite/rtems_init.c > [12/14] Compiling gdb/overwrite/overwrite.c > [13/14] Compiling filesystem/fat_ramdisk/rootfs/shell-init > [14/14] Linking build/sparc-rtems5-leon3/gdb/overwrite/overwrite.exe > [15/15] Compiling > build/sparc-rtems5-leon3/filesystem/fat_ramdisk/rootfs/shell-init > [16/16] Compiling > build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root.tar > [17/29] Compiling > build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root-tar.c > [18/29] Compiling filesystem/fat_ramdisk/init.c > [19/29] Compiling > build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root-tar.c > [20/29] Compiling filesystem/fat_ramdisk/init.c > [21/29] Compiling classic_api/classic_signal/test.c > [22/29] Compiling classic_api/triple_period/tasks.c > Waf: Leaving directory > `/home/EB/sebastian_h/src/rtems-examples/build/sparc-rtems5-leon3' > Build failed > Traceback (most recent call last): >File > "/home/EB/sebastian_h/src/rtems-examples/.waf-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py", > line 190, in process > self.post_run() >File "/home/EB/sebastian_h/src/rtems-examples/rtems_waf/gccdeps.py", > lin
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
Hello Alan,
On 08/04/2020 17:48, Alan Cudmore wrote:
Regarding the LEON3: I am noticing something with the release that I
don't understand yet.
I am able to build and run a number of ARM BSPs including raspberrypi,
raspberrypi2, beagleboneblack, and xlinx_zynq_a9_qemu
When I build my application for the leon3, most of it appears to work,
but I have a task demo that crashes when I try to print a variable
that is on the task stack. ( task ID, similar to what ticker does )
I went back and ran a number of the testsuite programs on both my
patched QEMU and sparc-rtems5-sis with no problems.
I then cloned the latest rtems-examples git repository and built the
ticker examples using the (obsolete) Makefile. When built this way,
the ticker program crashes as well on both QEMU and SIS.
I'm trying to narrow down the differences by comparing the flags used
to build the testsuite in the build tree vs. my applications and the
rtems-examples repository.
Should I try building the examples with waf?
I was able to reproduce this issue. It seems to be a problem with the
use of the FPU in a non-FP task:
Program received signal SIGTERM, Terminated.
syscall () at
/home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/syscall.S:44
44 ta 0 ! syscall 1, halt with
%g1,%g2,%g3 info
(gdb) bt
#0 syscall () at
/home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/syscall.S:44
#1 0x4000f888 in _User_extensions_Fatal_visitor (executing=0x0,
arg=0x26, callouts=0x40020ca8 <_User_extensions_List+4>) at
/home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/userextiterate.c:131
#2 0x4001cdc4 in _CPU_Fatal_halt (source=10, source@entry=0, error=0,
error@entry=38) at
/home/EB/sebastian_h/src/rtems/c/src/lib/libbsp/sparc/leon3/../../../../../../bsps/sparc/leon3/start/bsp_fatal_halt.c:33
#3 0x4000fb68 in _Terminate
(the_source=the_source@entry=INTERNAL_ERROR_CORE, the_error=38,
the_error@entry=0) at
/home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/interr.c:44
#4 0x4000fb7c in _Internal_error (core_error=0,
core_error@entry=INTERNAL_ERROR_ILLEGAL_USE_OF_FLOATING_POINT_UNIT) at
/home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/src/interr.c:52
#5 0x40001664 in bsp_spurious_handler (trap=260, isf=0x40028518) at
/home/EB/sebastian_h/src/rtems/c/src/lib/libbsp/sparc/leon3/../../../../../../bsps/sparc/leon3/start/spurious.c:124
#6 0x40012390 in pil_fixed () at
/home/EB/sebastian_h/src/rtems/c/src/../../cpukit/score/cpu/sparc/cpu_asm.S:592
It would be good to add support for the RTEMS Tester to the examples.
I was not able to build the examples with waf:
Waf: Entering directory
`/home/EB/sebastian_h/src/rtems-examples/build/sparc-rtems5-leon3'
[ 1/14] Compiling hello/hello_world_c/test.c
[ 2/14] Compiling hello/posix_hello_world/test.c
[ 3/14] Compiling hello/both_hello/test.c
[ 4/14] Compiling hello/both_hello/test.c
[ 5/14] Compiling hello/both_hello/test.c
[ 6/14] Linking
build/sparc-rtems5-leon3/hello/posix_hello_world/posix_hello.exe
[ 7/14] Linking build/sparc-rtems5-leon3/hello/hello_world_c/hello.exe
[ 8/14] Compiling build/sparc-rtems5-leon3/hello/both_hello/test.c.2.o
[ 9/14] Compiling build/sparc-rtems5-leon3/hello/both_hello/test.c.1.o
[10/14] Linking build/sparc-rtems5-leon3/hello/both_hello/both_hello.exe
[11/14] Compiling gdb/overwrite/rtems_init.c
[12/14] Compiling gdb/overwrite/overwrite.c
[13/14] Compiling filesystem/fat_ramdisk/rootfs/shell-init
[14/14] Linking build/sparc-rtems5-leon3/gdb/overwrite/overwrite.exe
[15/15] Compiling
build/sparc-rtems5-leon3/filesystem/fat_ramdisk/rootfs/shell-init
[16/16] Compiling
build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root.tar
[17/29] Compiling
build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root-tar.c
[18/29] Compiling filesystem/fat_ramdisk/init.c
[19/29] Compiling
build/sparc-rtems5-leon3/filesystem/fat_ramdisk/fs-root-tar.c
[20/29] Compiling filesystem/fat_ramdisk/init.c
[21/29] Compiling classic_api/classic_signal/test.c
[22/29] Compiling classic_api/triple_period/tasks.c
Waf: Leaving directory
`/home/EB/sebastian_h/src/rtems-examples/build/sparc-rtems5-leon3'
Build failed
Traceback (most recent call last):
File
"/home/EB/sebastian_h/src/rtems-examples/.waf-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py",
line 190, in process
self.post_run()
File "/home/EB/sebastian_h/src/rtems-examples/rtems_waf/gccdeps.py",
line 144, in post_run
raise ValueError('could not find %r for %r' % (x, self))
ValueError: could not find ['filesystem', 'fat_ramdisk',
'fs-root-tar.h'] for
{task 140228625202304: c init.c -> init.c.6.o}
Traceback (most recent call last):
File
"/home/EB/sebastian_h/src/rtems-examples/.waf-2.0.19-1f3c580272b15a03d2566843c5fe872a/waflib/Task.py",
line 190, in process
self.post_run()
File "/home/EB/sebastian_h/src/rtems-examples/rtems_waf/gccdeps.py",
line 144, in post_run
raise ValueError('could
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
On 2020-04-09 01:48, Alan Cudmore wrote: I definitely plan on creating a readme for the repository to help anyone that is interested. Thanks. Regarding the LEON3: I am noticing something with the release that I don't understand yet. I am able to build and run a number of ARM BSPs including raspberrypi, raspberrypi2, beagleboneblack, and xlinx_zynq_a9_qemu When I build my application for the leon3, most of it appears to work, but I have a task demo that crashes when I try to print a variable that is on the task stack. ( task ID, similar to what ticker does ) I went back and ran a number of the testsuite programs on both my patched QEMU and sparc-rtems5-sis with no problems. I then cloned the latest rtems-examples git repository and built the ticker examples using the (obsolete) Makefile. When built this way, the ticker program crashes as well on both QEMU and SIS. Can you see a faulting address? Can you attach a debugger to see what happens? QEMU and SIS can attach gdb. With the SIS use the `target remote :` command where `` is the port the SIS is listening on. Then `load` and `run` should work. I'm trying to narrow down the differences by comparing the flags used to build the testsuite in the build tree vs. my applications and the rtems-examples repository. Should I try building the examples with waf? Sure, but I am not a LEON or SPARC user so I am not sure what is happening here. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
Hi Chris, I definitely plan on creating a readme for the repository to help anyone that is interested. Regarding the LEON3: I am noticing something with the release that I don't understand yet. I am able to build and run a number of ARM BSPs including raspberrypi, raspberrypi2, beagleboneblack, and xlinx_zynq_a9_qemu When I build my application for the leon3, most of it appears to work, but I have a task demo that crashes when I try to print a variable that is on the task stack. ( task ID, similar to what ticker does ) I went back and ran a number of the testsuite programs on both my patched QEMU and sparc-rtems5-sis with no problems. I then cloned the latest rtems-examples git repository and built the ticker examples using the (obsolete) Makefile. When built this way, the ticker program crashes as well on both QEMU and SIS. I'm trying to narrow down the differences by comparing the flags used to build the testsuite in the build tree vs. my applications and the rtems-examples repository. Should I try building the examples with waf? Thanks, Alan On Tue, Apr 7, 2020 at 2:35 AM Chris Johns wrote: > > Hi Alan, > > This is awesome. I welcome deployment stories and support for them. I > wonder if we need a way to assist capturing this for our users. > > You may need to add something to the site's README to provide beginner > steps. > > Chris > > On 2020-04-07 11:44, Alan Cudmore wrote: > > Chris, > > I tested this release on the Raspberry Pi (Zero), Raspberry Pi 2, > > Beaglebone Black with LibBSD, xilinx_zynq_a9_qemu, and partially on > > the leon3. ( samples all work on Leon3 QEMU, but I'm still configuring > > my application ) > > > > To help generate tools and BSPs for releases like this, I created a > > series of Dockerfiles to generate a base system, Add tools, then build > > BSPs. I was learning docker, and I thought generating release > > candidate images might be a good exercise :) > > > > Here are the Dockerfiles in case anyone is interested: > > https://github.com/alanc98/rtems-release-docker > > > > To use these, create the "rtems5-m2004-base" image first, then for the > > ARM tools, the "rtems5-m2004-arm-tools" image. Finally, you can create > > an image like "rtems5-m2004-arm-bbb" to build the RTEMS BSP and > > rtems-libbsd for the Beaglebone Black. > > > > The resulting Docker image will allow you to build RTEMS applications > > that are shared through the "/host" directory in the container. > > > > With these, I hope to be able to crank out a series of builds for the > > targets I'm interested in for future releases. > > > > I'm also working on integration of my RTEMS Kernel Image (RKI) with > > rtems-libbsd. I have it working on the Beaglebone black and the > > zynq_a9_qemu target. That is a work in progress here: > > https://github.com/alanc98/rki2 > > All of the above targets work except for the leon3 right now. ( > > Raspberry Pi targets are not libbsd) > > > > Alan > > > > On Thu, Apr 2, 2020 at 6:13 AM wrote: > >> > >> RTEMS Release Build - 5.0.0-m2004 > >> > >> RTEMS 5 Release snapshot m2004 is avaliable for testing. > >> It can be found at: > >> > >> https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2004 > >> > >> Please test and report any issues to the u...@rtems.org or devel@rtems.org > >> mailing lists or please raise a ticket. > >> > >> If you are part of the RTEMS testing program please build on your preferred > >> host posting build and BSP test results to bu...@rtems.org. > >> > >> This is a development release and may have errors and be unstable. > >> > >> Thanks > >> Chris > >> ___ > >> devel mailing list > >> devel@rtems.org > >> http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
Hi Alan, This is awesome. I welcome deployment stories and support for them. I wonder if we need a way to assist capturing this for our users. You may need to add something to the site's README to provide beginner steps. Chris On 2020-04-07 11:44, Alan Cudmore wrote: Chris, I tested this release on the Raspberry Pi (Zero), Raspberry Pi 2, Beaglebone Black with LibBSD, xilinx_zynq_a9_qemu, and partially on the leon3. ( samples all work on Leon3 QEMU, but I'm still configuring my application ) To help generate tools and BSPs for releases like this, I created a series of Dockerfiles to generate a base system, Add tools, then build BSPs. I was learning docker, and I thought generating release candidate images might be a good exercise :) Here are the Dockerfiles in case anyone is interested: https://github.com/alanc98/rtems-release-docker To use these, create the "rtems5-m2004-base" image first, then for the ARM tools, the "rtems5-m2004-arm-tools" image. Finally, you can create an image like "rtems5-m2004-arm-bbb" to build the RTEMS BSP and rtems-libbsd for the Beaglebone Black. The resulting Docker image will allow you to build RTEMS applications that are shared through the "/host" directory in the container. With these, I hope to be able to crank out a series of builds for the targets I'm interested in for future releases. I'm also working on integration of my RTEMS Kernel Image (RKI) with rtems-libbsd. I have it working on the Beaglebone black and the zynq_a9_qemu target. That is a work in progress here: https://github.com/alanc98/rki2 All of the above targets work except for the leon3 right now. ( Raspberry Pi targets are not libbsd) Alan On Thu, Apr 2, 2020 at 6:13 AM wrote: RTEMS Release Build - 5.0.0-m2004 RTEMS 5 Release snapshot m2004 is avaliable for testing. It can be found at: https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2004 Please test and report any issues to the u...@rtems.org or devel@rtems.org mailing lists or please raise a ticket. If you are part of the RTEMS testing program please build on your preferred host posting build and BSP test results to bu...@rtems.org. This is a development release and may have errors and be unstable. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
Chris, I tested this release on the Raspberry Pi (Zero), Raspberry Pi 2, Beaglebone Black with LibBSD, xilinx_zynq_a9_qemu, and partially on the leon3. ( samples all work on Leon3 QEMU, but I'm still configuring my application ) To help generate tools and BSPs for releases like this, I created a series of Dockerfiles to generate a base system, Add tools, then build BSPs. I was learning docker, and I thought generating release candidate images might be a good exercise :) Here are the Dockerfiles in case anyone is interested: https://github.com/alanc98/rtems-release-docker To use these, create the "rtems5-m2004-base" image first, then for the ARM tools, the "rtems5-m2004-arm-tools" image. Finally, you can create an image like "rtems5-m2004-arm-bbb" to build the RTEMS BSP and rtems-libbsd for the Beaglebone Black. The resulting Docker image will allow you to build RTEMS applications that are shared through the "/host" directory in the container. With these, I hope to be able to crank out a series of builds for the targets I'm interested in for future releases. I'm also working on integration of my RTEMS Kernel Image (RKI) with rtems-libbsd. I have it working on the Beaglebone black and the zynq_a9_qemu target. That is a work in progress here: https://github.com/alanc98/rki2 All of the above targets work except for the leon3 right now. ( Raspberry Pi targets are not libbsd) Alan On Thu, Apr 2, 2020 at 6:13 AM wrote: > > RTEMS Release Build - 5.0.0-m2004 > > RTEMS 5 Release snapshot m2004 is avaliable for testing. > It can be found at: > > https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2004 > > Please test and report any issues to the u...@rtems.org or devel@rtems.org > mailing lists or please raise a ticket. > > If you are part of the RTEMS testing program please build on your preferred > host posting build and BSP test results to bu...@rtems.org. > > This is a development release and may have errors and be unstable. > > Thanks > Chris > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
On 2020-04-03 01:19, Gedare Bloom wrote: On Thu, Apr 2, 2020 at 4:17 AM Sebastian Huber wrote: Hello, in the readme file: cd mkdir -p development/rtems wget https://ftp.rtems.org/pub/rtems/releases/sources/rtems-source-builder-5.0.0-m2004.tar.xz tar jxf rtems-source-builder-5.0.0-m2004.tar.xz And this j should be capital J? It has been OK on FreeBSD (I think) but using J should not hurt. cd rtems-source-builder-5.0.0-m2004/rtems there is probably a cd development/rtems missing after the mkdir. Pushed both changes. Thank you for the review and feedback. Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
On Thu, Apr 2, 2020 at 4:17 AM Sebastian Huber wrote: > > Hello, > > in the readme file: > > cd > mkdir -p development/rtems > wget > https://ftp.rtems.org/pub/rtems/releases/sources/rtems-source-builder-5.0.0-m2004.tar.xz > tar jxf rtems-source-builder-5.0.0-m2004.tar.xz And this j should be capital J? > cd rtems-source-builder-5.0.0-m2004/rtems > > there is probably a > > cd development/rtems > > missing after the mkdir. > > ___ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
Re: RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
Hello, in the readme file: cd mkdir -p development/rtems wget https://ftp.rtems.org/pub/rtems/releases/sources/rtems-source-builder-5.0.0-m2004.tar.xz tar jxf rtems-source-builder-5.0.0-m2004.tar.xz cd rtems-source-builder-5.0.0-m2004/rtems there is probably a cd development/rtems missing after the mkdir. ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)
RTEMS Release Build - 5.0.0-m2004 RTEMS 5 Release snapshot m2004 is avaliable for testing. It can be found at: https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2004 Please test and report any issues to the u...@rtems.org or devel@rtems.org mailing lists or please raise a ticket. If you are part of the RTEMS testing program please build on your preferred host posting build and BSP test results to bu...@rtems.org. This is a development release and may have errors and be unstable. Thanks Chris ___ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
