[PATCH] RTEMS: Add Cortex-R52 multilib

gcc/ * config/arm/t-rtems: Add "-mthumb -mcpu=cortex-r52 -mfloat-abi=hard" multilib. --- gcc/config/arm/t-rtems | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/gcc/config/arm/t-rtems b/gcc/config/arm/t-rtems index 94a2eb7dd0b..b2fcf572bca 100644 --- a/gcc/

RE: CAN user space API for RTEMS

Great. I did some search regarding RTEMS and CAN beforehand, but only found quite old discussions. I blame the naming of the bus for that 😉. @Pavel Pisa You have lots of experience with different CAN setups. In your Email from March you also discussed many different APIs.

[PATCH v3] samples/unlimited: Prevent compile error

For architectures with relatively large minimum stack sizes, this test breaks during compilation due to a static check. The init task stack size should not need to be set for this test. --- testsuites/samples/unlimited/system.h | 1 - 1 file changed, 1 deletion(-) diff --git a/testsuites/samples/

[PATCH v3] zynq-uart: Fix set_attributes implementation

The zynq-uart set_attributes implementation was configured to always return false which causes spconsole01 to fail. This restores the disabled implementation which sets the baud rate registers appropriately and allows spconsole01 to pass. This also expands the set_attributes functionality to allow

Re: [PATCH v3] samples/unlimited: Prevent compile error

On 03/12/2020 16:24, Kinsey Moore wrote: For architectures with relatively large minimum stack sizes, this test breaks during compilation due to a static check. The init task stack size should not need to be set for this test. Ok. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 8217

Re: [PATCH v3] zynq-uart: Fix set_attributes implementation

On 03/12/2020 16:25, Kinsey Moore wrote: The zynq-uart set_attributes implementation was configured to always return false which causes spconsole01 to fail. This restores the disabled implementation which sets the baud rate registers appropriately and allows spconsole01 to pass. This also expand

Re: [PATCH] RTEMS: Add Cortex-R52 multilib

seems fine to me, send to gcc On Thu, Dec 3, 2020 at 1:39 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > gcc/ > > * config/arm/t-rtems: Add "-mthumb -mcpu=cortex-r52 > -mfloat-abi=hard" multilib. > --- > gcc/config/arm/t-rtems | 5 +++-- > 1 file changed, 3 ins

[PATCH v2 1/1] tester: Add yaml format to the supported report formats

From: Cláudio Maia --- tester/rt/test.py | 115 +- 1 file changed, 113 insertions(+), 2 deletions(-) diff --git a/tester/rt/test.py b/tester/rt/test.py index 9b157e9..e0cfdff 100644 --- a/tester/rt/test.py +++ b/tester/rt/test.py @@ -339,9 +339,120 @@

[PATCH v2 0/1] Add yaml format to the supported report formats

From: Cláudio Maia Two output formats were supported by RTEMS Tester: json and junit. This patch adds yaml to the list of supported formats. The information being stored in the ouput file is the same as the one being stored for the other formats, with the addition of adding a few more execution

Re: [PATCH v3] zynq-uart: Fix set_attributes implementation

On Thu, Dec 3, 2020 at 8:32 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 03/12/2020 16:25, Kinsey Moore wrote: > > > The zynq-uart set_attributes implementation was configured to always > > return false which causes spconsole01 to fail. This restores the > > disabled implem

Re: [PATCH v3] zynq-uart: Fix set_attributes implementation

On Thu, Dec 3, 2020 at 8:25 AM Kinsey Moore wrote: > The zynq-uart set_attributes implementation was configured to always > return false which causes spconsole01 to fail. This restores the > disabled implementation which sets the baud rate registers > appropriately and allows spconsole01 to pass.

Re: [PATCH 1/1] Add yaml format to the supported report formats

On 02/12/20 20:41, Chris Johns wrote: > On 3/12/20 3:05 am, cl...@isep.ipp.pt wrote: >> From: Cláudio Maia > Thanks. Does this work on python2? I had to do a small change in v2 due to the unicode string returned by path.basename() which was not being handled correctly by PyYAML. After that chan

Re: Report on failing tests with thread stack protection and their resolution.

On Wed, Dec 2, 2020 at 5:53 PM Utkarsh Rai wrote: > Hello, > As discussed in this > thread, > I have compiled a list of the tests that deal with inter stack > communication and fail with the thread stack protection option. Most o

RE: [PATCH v3] zynq-uart: Fix set_attributes implementation

From: Gedare Bloom Sent: Thursday, December 3, 2020 10:43 To: Sebastian Huber Cc: Kinsey Moore ; devel@rtems.org Subject: Re: [PATCH v3] zynq-uart: Fix set_attributes implementation On Thu, Dec 3, 2020 at 8:32 AM Sebastian Huber mailto:sebastian.hu...@embedded-brains.de>> wrote: On 03/12/202

Re: [PATCH v3] zynq-uart: Fix set_attributes implementation

On Thu, Dec 3, 2020 at 9:46 AM Gedare Bloom wrote: > > > On Thu, Dec 3, 2020 at 8:25 AM Kinsey Moore > wrote: > >> The zynq-uart set_attributes implementation was configured to always >> return false which causes spconsole01 to fail. This restores the >> disabled implementation which sets the ba

RE: [PATCH v3] zynq-uart: Fix set_attributes implementation

From: Gedare Bloom Sent: Thursday, December 3, 2020 12:51 To: Kinsey Moore Cc: devel@rtems.org Subject: Re: [PATCH v3] zynq-uart: Fix set_attributes implementation On Thu, Dec 3, 2020 at 9:46 AM Gedare Bloom mailto:ged...@rtems.org>> wrote: On Thu, Dec 3, 2020 at 8:25 AM Kinsey Moore mailto:k

[PATCH v4] zynq-uart: Fix set_attributes implementation

The zynq-uart set_attributes implementation was configured to always return false which causes spconsole01 to fail. This restores the disabled implementation which sets the baud rate registers appropriately and allows spconsole01 to pass. This also expands the set_attributes functionality to allow

Re: [PATCH v4] zynq-uart: Fix set_attributes implementation

looks good to me On Thu, Dec 3, 2020 at 12:10 PM Kinsey Moore wrote: > The zynq-uart set_attributes implementation was configured to always > return false which causes spconsole01 to fail. This restores the > disabled implementation which sets the baud rate registers > appropriately and allows s

[PATCH v1] spec: Move zynq-uart into its own object

Currently, zynq-uart code is always built and has some requirements for BSPs that use it. Instead of making all BSPs satisfy that requirement or working around it by setting defaults, this moves the zynq-uart code into its own spec build object so it can be included if needed. --- bsps/include/dev

Building llvm/clang for RTEMS

Hello, I am thinking about building an LLVM toolchain for RISC-V and AArch64 from RSB. I am looking for some suggestions or references if someone has worked on clang/llvm support for RTEMS. Best regards, Vijay ___ devel mailing list devel@rtems.org ht

Re: [PATCH v3] zynq-uart: Fix set_attributes implementation

On 4/12/20 3:42 am, Gedare Bloom wrote: > On Thu, Dec 3, 2020 at 8:32 AM Sebastian Huber > > > wrote: > On 03/12/2020 16:25, Kinsey Moore wrote: > > The zynq-uart set_attributes implementation was configured to always > > return false which ca

Re: Building llvm/clang for RTEMS

On Thu, Dec 3, 2020 at 4:19 PM Vijay Kumar Banerjee wrote: > Hello, > > I am thinking about building an LLVM toolchain for RISC-V and AArch64 > from RSB. I am looking for some suggestions or references if someone has > worked on clang/llvm support for RTEMS. > There is an RSB bset for clang-llv

Re: [PATCH v1] spec: Move zynq-uart into its own object

On 03/12/2020 20:47, Kinsey Moore wrote: Currently, zynq-uart code is always built and has some requirements for BSPs that use it. Instead of making all BSPs satisfy that requirement or working around it by setting defaults, this moves the zynq-uart code into its own spec build object so it can

Which threads execute _Thread_Handler ?

Hi, When I am trying to debug tm24 running on the Strong APA scheduler code, I can see that the thread which comes after the call to _CPU_Context_switch, resumes execution from the same code (next line in the _Thread_Do_dispatch function after _CPU_Context_switch), whereas when the same code is ru