Hello Chris,
Thanks to you and the RTEMS developers for creating this release!
I am testing your release packages. So far I have tried the following:
1. Built tools for SPARC, ARM, and i386 on an Ubuntu 18.04 LTS host.
2. Built the BSP for Beaglebone Black and the corresponding LibBSD
3. Built the
, 2020 12:38 PMTo: users@rtems.orgCc: Alan CudmoreSubject: Fwd: JTAG error with arm-rtems-gdb -- Forwarded message -De: Mario Palomares <palomares.mari...@gmail.com>Date: dom., 17 may. 2020 a las 18:33Subject: Re: JTAG error with arm-rtems-gdbTo: Alan Cudmore <alan.cudm...@
Hello Mario,Did you try bringing up the complete bare metal environment in the Bare Metal Raspberry Pi 3b JTAG blog entry?I would verify that that environment with the bare metal Aarch64 examples work before trying to get the 32 bit RTEMS binaries to work.It seems like these should work on the Pi2
That should work. I am currently using the shell on various LEON3 boards
using rcc-1.3-rc6.
My RTEMS config has this note:
/* POSIX Keys are needed for the Shell */
#define CONFIGURE_MAXIMUM_POSIX_KEYS 32
#define CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS64
( my values are p
Nice!
How does the 6LoWPAN device interface to the BeagleBone? SPI, UART?
Do you have any plans to integrate any IOT libraries such as MQTT?
Alan
On Thu, Jan 31, 2019 at 6:22 AM Pierre FICHEUX
wrote:
> Hi all,
>
> Here is a link to a screenshot of the 1rst version of "RTEMS / IoT"
> (RTEMS + 6L
Is the POSIX API preferred for RTEMS applications moving forward?
Thanks,
Alan
On Wed, Oct 17, 2018 at 5:20 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 15/10/2018 14:23, Thawra Kadeed wrote:
> >
> > Thanks a lot Sebastian for referring me to the git master.
> >
> > Actua
I have not used Cexp in a while. I am working on integrating support for
the RTEMS dynamic loader (RTL) in the OSAL and cFE, but it may take a while
for that to be integrated into the open source OSAL release.
For your immediate problem, would it be possible to try removing the #error
macro line?
RTEMS should work on the Raspberry Pi Zero, but I have not tried RTEMS on
the Raspberry Pi Zero W. The "W" model has wifi and bluetooth, and like the
Raspberry Pi 3, the bluetooth is connected to the UART which is used by the
RTEMS console. I believe we need to write a new console driver for the Pi
Paul,
I don't think the gethostid function is used in the cFS, so you could just
#undef the OS_INCLUDE_NETWORK in the osconfig.h file. This would remove the
gethostid call and allow it to compile.
I'm working on a LEON3 RTEMS 4.11 build. I have it running on several
boards, TSIM, and a QEMU target
