I will do it by either today or tomorrow.
On Fri, 20 Dec, 2019, 12:03 PM Sebastian Huber, <
sebastian.hu...@embedded-brains.de> wrote:
> On 19/12/2019 15:28, Niteesh wrote:
> > As far as I know, 0x8000 is a fixed address where the bootloader jumps
> > to after loading the application assuming th
On 19/12/2019 15:28, Niteesh wrote:
As farĀ as I know, 0x8000 is a fixed address where the bootloader jumps
to after loading the application assuming the CPU is in 32bit mode. For
64bit mode, it jumps to 0x8.
Would you mind testing this patch:
https://lists.rtems.org/pipermail/devel/2019-D
The RTEMS entry point must be at 0x8000.
Update #3774.
---
bsps/arm/raspberrypi/start/linkcmds.in | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/bsps/arm/raspberrypi/start/linkcmds.in
b/bsps/arm/raspberrypi/start/linkcmds.in
index d99b4fe23e..fde75877e7 100644
On 19/12/2019 15:20, Joel Sherrill wrote:
What native GNAT version do you use to build the RTEMS GNAT?
I use the same major versions, e.g. GCC 7 (sparc) or 9 (riscv).
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax
Given a cursory review, this looks OK.
What native GNAT version do you use to build the RTEMS GNAT?
--joel
On Wed, Dec 18, 2019 at 9:26 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Update #3845.
> ---
> cpukit/include/rtems/confdefs.h | 80
> ++-
On 19/12/2019 14:24, Christian Mauderer wrote:
Hello,
triggered by the discussion regarding RTEMS on raspberrypi 3 I did some
tests. I haven't been able to start a RTEMS on my Pi 1 if I tried a
version after commit c5fd79cd4704a4270ba0114a1009ab8556f997c9 from
29.07.2019. Right before it everyth
On 16/12/2019 02:29, chr...@rtems.org wrote:
From: Chris Johns
- This patch is based on the patch attached to #3552 submitted
by jameszxj.
Closes #3552
I tested and pushed the patch. It looks good now:
ENTER:Exit SPACE:Refresh S:Scroll A:All <>:Order +/-:Lines
Uptime: 7hr10m18.4177
On 19/12/2019 14:27, Sebastian Huber wrote:
> On 19/12/2019 14:24, Christian Mauderer wrote:
>> Hello,
>>
>> triggered by the discussion regarding RTEMS on raspberrypi 3 I did some
>> tests. I haven't been able to start a RTEMS on my Pi 1 if I tried a
>> version after commit c5fd79cd4704a4270ba0114
As far as I know, 0x8000 is a fixed address where the bootloader jumps to
after loading the application assuming the CPU is in 32bit mode. For 64bit
mode, it jumps to 0x8.
On Thu, Dec 19, 2019 at 6:58 PM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> On 19/12/2019 14:24, Chri
Hello,
triggered by the discussion regarding RTEMS on raspberrypi 3 I did some
tests. I haven't been able to start a RTEMS on my Pi 1 if I tried a
version after commit c5fd79cd4704a4270ba0114a1009ab8556f997c9 from
29.07.2019. Right before it everything works as expected.
The commit changes the me
Use CONFIGURE_MAXIMUM_PROCESSORS to configure the EDF SMP scheduler
context. This avoids hard to debug configuration errors resulting in
memory corruptions.
Close #3815.
---
cpukit/include/rtems/confdefs.h | 3 +--
cpukit/include/rtems/scheduler.h | 10 +++---
testsuites/
Close #3841.
---
c-user/object_services.rst | 28
1 file changed, 28 insertions(+)
diff --git a/c-user/object_services.rst b/c-user/object_services.rst
index 544ff02..860ce8c 100644
--- a/c-user/object_services.rst
+++ b/c-user/object_services.rst
@@ -49,6 +49,8 @@ th
12 matches
Mail list logo