Hello Sebastian,
On 23.04.2024 19:56, Sebastian Huber wrote:
1. Are all the things need for the release resolved? Tickets reviewed?
It would be nice to have the interrupt get/set priority API in RTEMS 6. The
Cortex-M floating point issue is not yet fixed in the RTEMS master.
Do you have any
Hello Sebastian,
On 08.02.2024 11:09, Sebastian Huber wrote:
Hello Cedric,
On 08.02.24 10:53, Cedric Berger wrote:
Hello,
I've a question: does RTEMS really wants to support FPU operations in
ISRs?
Because if the answer is "no", then I believe that we could simplify
the
Hello,
I've a question: does RTEMS really wants to support FPU operations in ISRs?
Because if the answer is "no", then I believe that we could simplify the
RTEMS code (and for me the mental model of the whole thing) by running
the FPU with both FPCCR.ASPEN and FPCCR.LSPEN = 0.
This mean
Hello,
I've started to investigate bug #4923.
A first problem can be found after applying the following patch to the
paranoia.exe test:
https://devel.rtems.org/attachment/ticket/4923/bug-1-make-paranoia-test-fail.patch
The test fails because of the added sleep(1) at the beginning of Init()
Hello,
On 19.01.2024 08:55, Sebastian Huber wrote:
On 19.01.24 07:58, Sebastian Huber wrote:
This patch fixes bugs #4908 and #4965 which were reported by RTMES
users. The patch is from 19 May 2023 and was blocked due to missing
tests on macOS. I have no macOS system for tests. Would someone
Hello,
On 18.12.2023 07:05, Chris Johns wrote:
On 16/12/2023 2:04 am, Cedric Berger wrote:
Hello Heinz,
On 15.12.2023 10:44, Heinz Junkes wrote:
HI,
I can follow Cedric's reasoning. Even if I was the initiator of this discussion.
I use RTEMS in my lectures/exercises, among other things
Hello Heinz,
On 15.12.2023 10:44, Heinz Junkes wrote:
HI,
I can follow Cedric's reasoning. Even if I was the initiator of this discussion.
I use RTEMS in my lectures/exercises, among other things, and have always been
able to give the students
freedom which laptops with which OS they wanted
Hello,
On 04.12.2023 22:37, Chris Johns wrote:
The issue has been resolved in gmp-6.3.0 for M silicon. I am how looking at:
https://lists.rtems.org/pipermail/users/2023-October/068894.html
and the crash is in a GMP call via MPFR. This is on Intel silicon on Ventura. I
have just run `make
Hello,
On 28.11.2023 05:12, Chris Johns wrote:
-https://libisl.sourceforge.io/isl-0.26.tar.gz
This does not build on my M2 with Sonoma and the latest Xcode. Something about a
missing constructor.
This is so weird, it should make no difference with my system.
Full build log below.
Cedric
Hello,
On 28.11.2023 03:00, Chris Johns wrote:
On 27/11/2023 6:43 pm, Cedric Berger wrote:
Hello,
On 24.11.2023 08:36, Sebastian Huber wrote:
Would updating to ISL 0.26 and MPC 1.3.1 fix this issue also?
I just tried in on my fully up-to-date M1 Pro (macOS Sonoma 14.1.1, Xcode
15.0.1
Hello,
On 24.11.2023 08:36, Sebastian Huber wrote:
Would updating to ISL 0.26 and MPC 1.3.1 fix this issue also?
I just tried in on my fully up-to-date M1 Pro (macOS Sonoma 14.1.1,
Xcode 15.0.1)
Short answer: everything works well without issues (configure, make, check)
I just installed
On 09.08.23 10:51, Sebastian Huber wrote:
We could add some text to the option description:
# Defines the program prefix of tools (compiler, assembler, linker).
# This option may be used to build RTEMS with a vendor tool suite.
# Please note that using tool suites not provided by the RTEMS
Hello
On 04.08.23 07:07, Sebastian Huber wrote:
On 04.08.23 00:43, Chris Johns wrote:
On 3/8/2023 10:17 pm, Sebastian Huber wrote:
Build the arm libdebugger support only for supported ARM architectures.
What ARM archs are not supported?
At least ARMv7-M and everything with Thumb 1.
Is
Hello,
On 26.07.23 22:48, Kinsey Moore wrote:
This adds an option to allow operation of the CPU at its maximum
temperature range of 125F by reducing the CPU clock to 400MHz instead of
the 105F limit imposed by the default 480MHz CPU clock. This tradeoff is
detailed in table 122 in section 7.3.1
On 20.07.23 09:52, Chris Johns wrote:
On 20/7/2023 5:24 pm, Cedric Berger wrote:
On 20.07.23 07:45, chr...@rtems.org wrote:
From: Chris Johns
The kernel open call requires a path so to open a file we need to
set the current directory to the parent vnode. If the open mode is
create the path
On 20.07.23 07:45, chr...@rtems.org wrote:
From: Chris Johns
The kernel open call requires a path so to open a file we need to
set the current directory to the parent vnode. If the open mode is
create the path info vnode is the directory to perform the open
create in. Using the parent node
Hello Kinsley,
Yes, basically:
if you look at page 135 of the reference manual:
https://www.st.com/resource/en/reference_manual/rm0399-stm32h745755-and-stm32h747757-advanced-armbased-32bit-mcus-stmicroelectronics.pdf
SDRAM BANK 1 is at 0xc000 (behaving like device memory, not
executable)
Hello,
On 03.07.23 23:58, Joel Sherrill wrote:
On Mon, Jul 3, 2023 at 11:29 AM Christian Mauderer
wrote:
Hello Cedric,
Am 03.07.23 um 08:47 schrieb Cedric Berger:
> Hello,
>
> Two issues here:
>
> 1) When looking at RTEMS on github, it seems eve
Hello,
Two issues here:
1) When looking at RTEMS on github, it seems everything stopped being
updated on March 23.
2) Then going to https://www.rtems.org, clicking "Git" yield this page:
Trac Error
Page Developer/Git not found
Is there something we can do to help with this
Hello,
I'm looking at the filesystem options for RTEMS (on top of a 4GB eMMC
chip), but I need something that behaves properly in case of a sudden
power loss.
I probably missed something, but:
Regarding RFS, I found this:
https://lists.rtems.org/pipermail/users/2013-December/060969.html
Sorry for a slightly off-topic question here:
[...]
In that case, I'll stick with the BSP management improvements once v4
of this patch set goes in (probably) and skip the generic build.
Is a generic build something that would be worth pursuing for lwIP? It
would come with the core stacks,
Hello,
On 07.07.22 09:35, Duc Doan wrote:
Actually my project is focused on STM32F4, but it is nice that the code
could be extensible to H7. However, I can't think of a good way to use
that code with H7 right now; do you think that the code can be copied
and pasted to H7 BSP? Or is there a
Hello,
On 06.07.22 13:03, Duc Doan wrote:
Hello Cedric,
Thank you for your feedback. I agree with you that there are places that could
be optimized out. Here is a new patch for that.
Yes, this looks good, thanks!
One more detail and one question follows:
static unsigned int
Hello,
Have you tried a tiny bit to optimize this code because at a quick
glance, it sounds like for critical routines, you choose some slow and
complicated ways to do simple things, see a few some example below:
+static uint16_t GPIO_PIN_x[] = {
+GPIO_PIN_0,
+GPIO_PIN_1,
+
On 13.05.22 17:55, Joel Sherrill wrote:
On Fri, May 13, 2022 at 10:42 AM Cedric Berger
wrote:
On 13.05.22 17:25, Joel Sherrill wrote:
> I think you are missing my point. I'm not opposed to the patches
and
> understand the need.
>
> The RTEMS Project t
On 13.05.22 17:25, Joel Sherrill wrote:
I think you are missing my point. I'm not opposed to the patches and
understand the need.
The RTEMS Project tried putting patches in our git repos when the RSB
was new. It did not improve our diligence in getting them upstream or
removing them from
On 13.05.22 16:25, Joel Sherrill wrote:
On Fri, May 13, 2022, 9:08 AM Karel Gardas wrote:
Joel,
I agree that having support upstreamed would be the best option. Due to
upstream lag behind apple hardware development I'm afraid we would miss
RTEMS 6 release if we would wait on upstream here,
Hello,
On 28.04.22 18:15, Joel Sherrill wrote:
[...]
It should be checked to be sure it is up to date and definitely covered
somewhere prominent. It looks like the page we long time folks likely
think is very prominent and accessible isn't anymore. Before Trac, the
top entry page of the Wiki
, at 08:55, Sebastian Huber
wrote:
On 18/04/2022 21:01, Cedric Berger wrote:
Hello,
On 11.04.22 00:37, Chris Johns wrote:
I suspect we will need a later version of expat that has the aarch64 support. I
do not have access access to an M1 Mac so I cannot test this.
Chris
So I tried to compile
of months ago, I was able to build an RTEMS toolchain on
aarch64 Linux with just an expat upgrade. I was not aware that GMP was
needed as well.
Alan
*From: *Cedric Berger <mailto:ced...@precidata.com>
*Sent: *Tuesday, April 19, 2022 11:23 AM
*To: *Jay Zhu <mailto:jing...@usc.edu>; dev
Hello,
On 10.04.22 20:37, Jay Zhu wrote:
Hi,
I am a student new to RTEMS and trying to get my first lines to run. When
following the quick-start guide, I was stuck in Install Tool Suite procedure.
Using this command:
../source-builder/sb-set-builder --prefix=$HOME/quick-start/rtems/6
Hello,
On 11.04.22 00:37, Chris Johns wrote:
I suspect we will need a later version of expat that has the aarch64 support. I
do not have access access to an M1 Mac so I cannot test this.
Chris
So I tried to compile RTEMS 6 for arm on MacOS for both the M1 and Intel
architecture. It was not
Hello Karel,
On 30.01.22 20:41, Karel Gardas wrote:
Hello Sebastian,
I guess you will be in charge of reviewing this patch. Please allow me
to explain motivation behind it plus add some questions.
You know I'd like to update STM32H7 HAL to the latest code provided by
STMicro to be able to use
On 18.06.20 22:47, Joel Sherrill wrote:
Hi
I have an example FACE application I am trying to port to RTEMS. This
is a multi-question email:
First, it fails with EADDRNOTAVAIL on this call:
// Subscribe to multicast group
struct ip_mreq mreq;
rc =
Hello,
I wanted to test the snapshot, but the following link:
https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2005-2/
contains broken references. For example, the Quick Guide:
https://ftp.rtems.org/pub/rtems/releases/5/5.0.0/5.0.0-m2005-2/docs/rtems-docs-5.0.0-m2005-2-user.pdf
35 matches
Mail list logo
