RTEMS Release Snapshot: 5.0.0-m2004 (02 Apr 2020)

[Alan Cudmore]

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 <chrisj at rtems.org> 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 <chrisj at rtems.org> 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 user at rtems.org or devel at 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 build at rtems.org.
> >>
> >> This is a development release and may have errors and be unstable.
> >>
> >> Thanks
> >> Chris
> >> _______________________________________________
> >> devel mailing list
> >> devel at rtems.org
> >> http://lists.rtems.org/mailman/listinfo/devel