Re: [rtems-release commit] Do not use tar Jxf for uncompressed archives

On 17/02/2022 20:15, Chris Johns wrote: On 17/2/22 4:45 pm, Sebastian Huber wrote: Hello Chris, On 17/02/2022 04:11, Chris Johns wrote: I would like to approve all commits to this repo. Why have you made this change? I tried to run the scripts on my Linux machine and this fixed one of the is

Problem compiling leon3 and gr712rc with Tests and SMP enabled.

Hi, I've been trying to manually build BSP using waf on RTEMS 6. I'm working off HEAD of the RTEMS master branch. However, on gr712rc, whenever I try to have both SMP and tests enabled I get compile errors, which I can't really understand. When I try building with only either option, it works in b

Re: Problem compiling leon3 and gr712rc with Tests and SMP enabled.

On 18/02/2022 12:02, Jerzy Jaskuc wrote: Am I doing something wrong or missing some new steps with it? Any help would be appreciated! This is probably a bug in the dependency tracking of the build system. Try to delete the build directory before the waf configure. -- embedded brains GmbH Her

Re: Problem compiling leon3 and gr712rc with Tests and SMP enabled.

Thanks Sebastian! It seems like it was dependency tracking. All is working now after deleting the build directory. Thanks and all the best, Jerzy On Fri, 18 Feb 2022 at 11:20, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 18/02/2022 12:02, Jerzy Jaskuc wrote: > > Am I doing

NTP client recommendation for RTEMS?

Hello, I would like to add an NTP client support for RTEMS. The ntp_adjtime() implementation is already available as a patch. For testing purposes I ported the NTP daemon from FreeBSD to libbsd. This basically works fine. I am not sure about the maintenance status of this code (https://www.nt

Re: NTP client recommendation for RTEMS?

On Fri, Feb 18, 2022, 7:22 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > I would like to add an NTP client support for RTEMS. The ntp_adjtime() > implementation is already available as a patch. For testing purposes I > ported the NTP daemon from FreeBSD to libbsd. Th

Re: NTP client recommendation for RTEMS?

On 18/02/2022 14:43, Joel Sherrill wrote: On Fri, Feb 18, 2022, 7:22 AM Sebastian Huber > wrote: Hello, I would like to add an NTP client support for RTEMS. The ntp_adjtime() implementation is already available as a patch. For testing purp

Re: [PATCH v1 3/5] cpukit/microblaze: Add interrupt hooks

On 2/17/2022 20:31, Chris Johns wrote: On 18/2/22 8:58 am, Kinsey Moore wrote: On 2/17/2022 15:31, Chris Johns wrote: On 18/2/22 7:12 am, Kinsey Moore wrote: On 2/17/2022 13:53, Chris Johns wrote: Who is setting breaks points in interrupts? Where I encountered issues was setting breaks in

Re: NTP client recommendation for RTEMS?

On Fri, Feb 18, 2022 at 7:46 AM Sebastian Huber wrote: > > On 18/02/2022 14:43, Joel Sherrill wrote: > > On Fri, Feb 18, 2022, 7:22 AM Sebastian Huber > > > > wrote: > > > > Hello, > > > > I would like to add an NTP client support for RTEMS. The

[PATCH] config: CONFIGURE_DISABLE_NEWLIB_REENTRANCY

Do not initialize Thread_Control::libc_reent if CONFIGURE_DISABLE_NEWLIB_REENTRANCY is defined. This helps to catch errors with a NULL pointer exception rather than a corruption of the thread control block. --- cpukit/include/rtems/confdefs/threads.h | 17 + 1 file changed, 9 inse

config, _IO_Initialize_all_drivers

I'm still trying to get the booting and registering and initialising of the i2c devices on the MVME3100 to work properly. In confdefs/iodrivers.h the driver address table is built up and then _IO_Initialize_all_drivers() is called without registering the individual devices first. If I now ente

Re: config, _IO_Initialize_all_drivers

On Fri, Feb 18, 2022 at 10:18 AM Heinz Junkes wrote: > > I'm still trying to get the booting and registering and initialising of the > i2c devices on the MVME3100 to work properly. > > In confdefs/iodrivers.h the driver address table is built up and then > _IO_Initialize_all_drivers() is called w

[PATCH v2 0/6] Add MicroBlaze libdebugger support

Differences from v1: * Patch 1/6: Commit message reworded * Patch 4/6: Added for independent exception control * Patch 6/6: Reworked to use illegal opcode instead of architecture-defined software break instruction ___ devel mailing list dev

[PATCH v2 1/6] cpukit/libdebugger: Avoid missed swbreak removal

It is possible to remove software breaks without actually restoring the original instruction to memory. When this happens, the original instruction is lost. This ensures that the original instruction is restored when a software break is removed. --- cpukit/libdebugger/rtems-debugger-target.c | 16

[PATCH v2 2/6] cpukit/libdebugger: Add pure swbreak capability

Add a capability that allows for implementations that operate purely using software breaks. Due to this implementation method, software breaks must not be restored until just before returning control to the thread itself and will be handled by the implementation through thread switch and interrupt

[PATCH v2 3/6] cpukit/microblaze: Add interrupt hooks

Add hooks for manipulating system state before and after interrupts are run. These hooks serve primarily to allow the MicroBlaze libdebugger backend to prevent software breaks from occurring in interrupt context. --- cpukit/score/cpu/microblaze/cpu.c | 42 +++ cpukit/sc

[PATCH v2 4/6] microblaze: Decouple exceptions from interrupts

Exception handling should be enabled at all times during execution to ensure that exceptions are not ignored which would cause further problems. This separates use of the exception enable bit from use of the interrupt enable bit in the machine status register so that they can be manipulated indepen

[PATCH v2 5/6] cpukit/microblaze: Create interrupt flag

The MicroBlaze Machine Status Register (MSR) does not have a flag that designates the current execution status of the interrupt handler other than the Interrupt Enable (IE) bit which may be unset for other reasons. This makes use of R13 to signal the current interrupt nesting encompassing the entir

[PATCH v2 6/6] cpukit/libdebugger: Add MicroBlaze support

Add MicroBlaze support for libdebugger. This uses only software break type instructions to provide self-hosted GDB debugging support for applications since internal control of debug hardware is not possible. Also of note, this implementation for MicroBlaze would typically use the brki instruction

Re: config, _IO_Initialize_all_drivers

> On 18. Feb 2022, at 17:47, Joel Sherrill wrote: > > > "Normally" the driver initialization entry registers names. Unfortunately, I cannot confirm that. I don't see any registrations (rtems_io_register_driver()) of the drivers. Only rtems_io_initialize() major 0 - > (in my case) 39 is cal

Re: [PATCH v1 3/5] cpukit/microblaze: Add interrupt hooks

On Fri, Feb 18, 2022 at 6:50 AM Kinsey Moore wrote: > > > On 2/17/2022 20:31, Chris Johns wrote: > > On 18/2/22 8:58 am, Kinsey Moore wrote: > >> On 2/17/2022 15:31, Chris Johns wrote: > >>> On 18/2/22 7:12 am, Kinsey Moore wrote: > On 2/17/2022 13:53, Chris Johns wrote: > > Who is settin

Re: [PATCH v1 3/5] cpukit/microblaze: Add interrupt hooks

On 2/18/2022 14:37, Gedare Bloom wrote: On Fri, Feb 18, 2022 at 6:50 AM Kinsey Moore wrote: On 2/17/2022 20:31, Chris Johns wrote: On 18/2/22 8:58 am, Kinsey Moore wrote: On 2/17/2022 15:31, Chris Johns wrote: On 18/2/22 7:12 am, Kinsey Moore wrote: On 2/17/2022 13:53, Chris Johns wrote: W

Re: [PATCH] added malloc usable size and test

On Thu, Feb 17, 2022 at 8:14 PM zack leung wrote: > > --- > cpukit/include/rtems/libcsupport.h| 5 ++- > cpukit/libcsupport/src/mallocusablesize.c | 47 +++ > spec/build/cpukit/librtemscpu.yml | 1 + > testsuites/libtests/malloctest/init.c | 13 +++ >