[PATCH] Fix build issues on Debian 10

--- trace/wscript | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/trace/wscript b/trace/wscript index 7335c8f..187ee82 100644 --- a/trace/wscript +++ b/trace/wscript @@ -33,8 +33,15 @@ def options(opt): def configure(conf): conf.load('compiler_c')

Re: New Build System Ready for Integration

On 04/12/2019 09:58, Sebastian Huber wrote: On 04/12/2019 09:51, Chris Johns wrote: Is there anything else open which prevents us from merging in the new build system? I am about to head to Huntsville to see Joel and I would like to discuss this with him. He is out of town at the moment so

Re: [PATCH 6/7] bsps: Remove uses of BSP_GET_WORK_AREA_DEBUG

On 17/12/2019 00:34, Chris Johns wrote: On 16 Dec 2019, at 11:42 pm, Sebastian Huber wrote: The code covered by BSP_GET_WORK_AREA_DEBUG was basically dead code since there was no normal way to activate it (e.g. via a BSP configuration option). BSP developers should use a debugger instead.

Re: [PATCH 6/7] bsps: Remove uses of BSP_GET_WORK_AREA_DEBUG

> On 16 Dec 2019, at 11:42 pm, Sebastian Huber > wrote: > > The code covered by BSP_GET_WORK_AREA_DEBUG was basically dead code > since there was no normal way to activate it (e.g. via a BSP > configuration option). BSP developers should use a debugger instead. You will need to establish a

Re: Requirement Document generator tool

On Mon, Dec 16, 2019 at 7:29 AM Jose Valdez wrote: > Hello Chris, > > Thank you for your reply. > > Please find below my answers. > > José > > -Original Message- > From: Chris Johns [mailto:chr...@rtems.org] > Sent: sexta-feira, 13 de dezembro de 2019 19:09 > To: Jose Valdez;

Re: Problem running RTEMS on raspberrypi3

What about using U-boot? I just tried running my own bare metal example using u-boot and it works fine. The 3rd stage bootloader start the u-boot and I was able to interact with it through serial. and then I used fatload mmc 0 0x8000 kernel.img ; go 0x8000 to load and run the img. I tried the same

Re: Problem running RTEMS on raspberrypi3

But I am not able to boot using the 3 stage bootloader. Can someone try booting any examples on raspi3 or other newer models? If it's work's please post the instructions. The steps that I followed are: 1. arm-rtems5-objcopy -Obinary hello.exe kernel.img 2. copied the kernel image to sd card and

[PATCH 21/21] score: Simplify _Thread_Initialize()

Allocate new thread queue heads during objects information extend. This removes an error case and the last dependency on the workspace in _Thread_Initialize(). Update #3835. --- cpukit/Makefile.am | 1 + cpukit/include/rtems/score/thread.h| 10 +++-

[PATCH 17/21] score: Add _Freechain_Is_empty()

Update #3835. --- cpukit/include/rtems/score/freechain.h | 12 testsuites/sptests/spfreechain01/init.c | 3 ++- 2 files changed, 14 insertions(+), 1 deletion(-) diff --git a/cpukit/include/rtems/score/freechain.h b/cpukit/include/rtems/score/freechain.h index

[PATCH 12/21] score: Add _Objects_Free_objects_block()

This is a preparation to allow a customization of the objects information extend. Update #3835. --- cpukit/include/rtems/score/objectimpl.h| 11 cpukit/score/src/objectshrinkinformation.c | 92 +- 2 files changed, 64 insertions(+), 39 deletions(-) diff --git

[PATCH 15/21] score: Inline _Objects_Namespace_remove_u32()

This function is simple enough to be inlined. Update #3835. --- cpukit/include/rtems/score/objectimpl.h | 38 ++-- cpukit/score/src/objectnamespaceremove.c | 9 2 files changed, 21 insertions(+), 26 deletions(-) diff --git

[PATCH 19/21] score: Add _Freechain_Extend()

Update #3835. --- cpukit/include/rtems/score/freechain.h | 18 ++ cpukit/score/src/freechain.c | 33 + 2 files changed, 43 insertions(+), 8 deletions(-) diff --git a/cpukit/include/rtems/score/freechain.h

[PATCH 20/21] score: Add _Objects_Activate_unlimited()

Update #3835. --- cpukit/include/rtems/score/objectimpl.h| 24 cpukit/score/src/objectallocateunlimited.c | 13 + 2 files changed, 25 insertions(+), 12 deletions(-) diff --git a/cpukit/include/rtems/score/objectimpl.h

Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3

That is usually the way I run RTEMS on the Raspberry Pi (1 and 2). I have not run RTEMS on the Pi in a while, but the last time I did, I had to revert to an earlier version of the raspberry pi firmware/bootloader. I had to use this release of the firmware:

[PATCH 13/21] score: Split up objects allocation

Split up the different objects allocation methods into separate functions. This helps to avoid a dependency on the workspace in case no objects or a static set of objects is configured. Change license to BSD-2-Clause according to file histories. Update #3053. Update #3835. ---

[PATCH 16/21] score: _Objects_Extend_information()

Return block index in _Objects_Extend_information(). This allows to customize the objects information extend. Update #3835. --- cpukit/include/rtems/score/objectimpl.h| 5 - cpukit/score/src/objectextendinformation.c | 21 ++--- 2 files changed, 10 insertions(+), 16

[PATCH 07/21] score: Split stack allocator configuration

This allows the linker garbage collection to perform its work. Update #3835. --- cpukit/Makefile.am | 1 + cpukit/include/rtems/confdefs.h| 63 +++--- cpukit/include/rtems/config.h | 63 --

[PATCH 18/21] score: Add _Freechain_Pop()

Update #3835. --- cpukit/include/rtems/score/freechain.h | 12 testsuites/sptests/spfreechain01/init.c | 4 2 files changed, 16 insertions(+) diff --git a/cpukit/include/rtems/score/freechain.h b/cpukit/include/rtems/score/freechain.h index bbae0b65bb..e656f64f8e 100644 ---

[PATCH 01/21] score: Remove superfluous FP types/defines

Update #3835. --- cpukit/score/cpu/arm/include/rtems/score/cpu.h | 6 - cpukit/score/cpu/bfin/include/rtems/score/cpu.h| 185 + .../score/cpu/epiphany/include/rtems/score/cpu.h | 106 +--- cpukit/score/cpu/lm32/include/rtems/score/cpu.h| 92 +-

[PATCH 14/21] score: Split up objects free

Split up the different objects free methods into separate functions. This helps to avoid a dependency on the workspace in case no objects or a static set of objects is configured. Update #3835. --- cpukit/Makefile.am | 2 + cpukit/include/rtems/score/objectdata.h | 51

[PATCH 11/21] score: Statically allocate idle/MPCI stacks

Place idle and MPCI stacks into extra linker sections. This can be optionally used by applications to control the placement of the stacks. Update #3835. --- cpukit/include/rtems/confdefs.h | 39 +++- cpukit/include/rtems/score/mpci.h| 7 +++

[PATCH 08/21] score: Add Thread_Configuration

Add the Thread_Configuration structure to reduce the parameter count of _Thread_Initialize(). This makes it easier to add more parameters in the future. It simplifies the code generation since most architectures do not have that many registers available for function parameters. Update #3835.

[PATCH 10/21] score: Move thread stack allocation

Move thread stack allocation to caller side of _Thread_Initialize(). Update #3835. --- cpukit/include/rtems/score/thread.h | 2 -- cpukit/include/rtems/score/threadimpl.h | 9 -- cpukit/posix/src/pthreadcreate.c| 20 + cpukit/rtems/src/taskcreate.c | 16

[PATCH 06/21] score: Simplify TLS area allocation

Use the stack area to allocate the TLS area. Update #3835. --- cpukit/Makefile.am | 2 + cpukit/include/rtems/confdefs.h | 3 +- cpukit/include/rtems/config.h | 8 +--- cpukit/include/rtems/score/stack.h | 11 -

[PATCH 03/21] score: Simplify thread stack free

Update #3835. --- cpukit/include/rtems/score/stackimpl.h | 9 + cpukit/include/rtems/score/thread.h | 9 + cpukit/include/rtems/score/threadimpl.h | 11 --- cpukit/score/src/threadinitialize.c | 27 +-- cpukit/score/src/threadrestart.c

[PATCH 04/21] score: Remove _Stack_Ensure_minimum() call

This call is superfluous since _Thread_Initialize() will do this also. Update #3835. --- cpukit/score/src/threadcreateidle.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/cpukit/score/src/threadcreateidle.c b/cpukit/score/src/threadcreateidle.c index

[PATCH 02/21] score: Simplify thread stack allocation

Remove superfluous Thread_Control::Start::stack member. Update #3835. --- cpukit/include/rtems/score/stackimpl.h | 10 ++ cpukit/include/rtems/score/thread.h | 2 -- cpukit/include/rtems/score/threadimpl.h | 17 - cpukit/score/src/threadinitialize.c | 29

[PATCH 05/21] score: Simplify FP context allocation

Use the stack area to allocate the FP context. This considerably simplifies the application configuration since the task count no longer influences the configured work space size. With this change the stack space size is overestimated since an FP context for each thread is accounted. Memory

[PATCH 00/21] Support statically allocated threads

This change set makes it possible to statically allocate threads. This means the thread control block is provided by a statically allocated thread information and the thread stack is provided by the user. Currently, no API function exists for this. Adding this API is a follow up change set.

[PATCH 09/21] score: Add _Stack_Extend_size()

Update #3835. --- cpukit/include/rtems/score/stackimpl.h | 27 +++ cpukit/score/src/threadinitialize.c| 13 +++-- 2 files changed, 30 insertions(+), 10 deletions(-) diff --git a/cpukit/include/rtems/score/stackimpl.h b/cpukit/include/rtems/score/stackimpl.h

Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3

I'm not that sure that the right UART is used. The driver in the raspberry BSP doesn't care for the configuration file. So it most likely always uses the same UART regardless what the bootloader tells. The dtoverlay=disable-bt in the config file just adds a devicetree overlay. We currently

Re: Problem running RTEMS on raspberrypi3

I think I have guided you to a wrong path here. I mentioned U-Boot because it is often used on a lot of evaluation boards. In the raspberry case it seems that the stage 3 loader is something different. But everything should work with that stage 3 loader. I don't think that U-Boot is necessary. On

Re: Problem running RTEMS on raspberrypi3

On 16/12/2019 12:43, Niteesh wrote: > On Mon, Dec 16, 2019 at 2:36 AM Christian Mauderer > wrote: > > > > On 15/12/2019 21:29, Niteesh wrote: > > > > > > On Mon, Dec 16, 2019 at 12:53 AM Christian Mauderer > mailto:l...@c-mauderer.de> > >

Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3

If possible can you write down the exact steps of how you loaded the image? I tried running it on my RPi3 by placing the rtems kernel.img in my SD card but it didn't work. On Mon, Dec 16, 2019 at 7:33 PM Cudmore, Alan P. (GSFC-5820) < alan.p.cudm...@nasa.gov> wrote: > That’s good to know. I

Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3

That’s good to know. I would like to try the Raspberry Pi Zero W and make sure it works like the Pi Zero without the wireless. From: Niteesh Date: Monday, December 16, 2019 at 8:54 AM To: Alan Cudmore Cc: Christian Mauderer , "rtems-de...@rtems.org" Subject: Re: [EXTERNAL] Re: Problem

Re: Query related to PRU drivers of BeagleBone Black

Thank you for the clarification. On Mon, Dec 16, 2019 at 6:31 PM Nils Hölscher wrote: > Hi, > > > On Sun, 15 Dec 2019 at 15:45, Christian Mauderer > wrote: > >> Hello Utkarsh Rai, >> >> I haven't followed the project tightly. So I can't tell much regarding 2 >> and 3. I added Nils (who did the

Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3

I looked at the source code for UART. RTEMS uses the PL011 which is by default connected to the bluetooth module, but this can be changed by adding disable-bt command to the config.txt this will configure PL011 as the primary uart. So I don't think anything has to be changed. On Mon, Dec 16, 2019

RE: Requirement Document generator tool

Hello Chris, Thank you for your reply. Please find below my answers. José -Original Message- From: Chris Johns [mailto:chr...@rtems.org] Sent: sexta-feira, 13 de dezembro de 2019 19:09 To: Jose Valdez; devel@rtems.org Subject: Re: Requirement Document generator tool On 14/12/19 3:09

Re: [EXTERNAL] Re: Problem running RTEMS on raspberrypi3

Has the RPI3 UART/Console been addressed in RTEMS? My understanding is that the RPI 1, Zero (without wireless) and 2 all share the same UART/Console driver. But the Raspberry Pi 3 and Zero W use that UART to talk to the Bluetooth module. The “mini” UART is then used for the console. So, at a

Re: Query related to PRU drivers of BeagleBone Black

Hi, On Sun, 15 Dec 2019 at 15:45, Christian Mauderer wrote: > Hello Utkarsh Rai, > > I haven't followed the project tightly. So I can't tell much regarding 2 > and 3. I added Nils (who did the GSoC 2019 project) to CC so maybe he > can give you some more details. > > Regarding 1: In RTEMS we

Re: Problem running RTEMS on raspberrypi3

I got uboot running on my raspi3. But I can't figure out to load and run a custom kernel. Can you explain the steps or point me to some reference. On Mon, Dec 16, 2019 at 5:13 PM Niteesh wrote: > On Mon, Dec 16, 2019 at 2:36 AM Christian Mauderer > wrote: > >> >> >> On 15/12/2019 21:29, Niteesh

[PATCH 6/7] bsps: Remove uses of BSP_GET_WORK_AREA_DEBUG

The code covered by BSP_GET_WORK_AREA_DEBUG was basically dead code since there was no normal way to activate it (e.g. via a BSP configuration option). BSP developers should use a debugger instead. If this output via printk() turns out to be still wanted by users, it can be added as an

[PATCH 7/7] bsps: Rework work area initialization

The work area initialization was done by the BSP through bsp_work_area_initialize(). This approach predated the system initialization through the system initialization linker set. The workspace and C program heap were unconditionally initialized. The aim is to support RTEMS application

[PATCH 0/7] Rework work area initialization

This change set reworks the work area initialization carried out by the BSPs to initialize the workspace and C program heap only on demand, e.g. in case these components are used by the application. Currenlty, the workspace is always used, however, this may change in a follow up change set.

[PATCH 1/7] score: Add Memory Handler

Update #3838. --- cpukit/Makefile.am | 1 + cpukit/headers.am | 1 + cpukit/include/rtems/score/memory.h | 331 cpukit/score/src/memoryallocate.c | 67 4 files changed, 400 insertions(+) create mode 100644

[PATCH 5/7] stackchk: Add RTEMS_SYSINIT_ISR_STACK

Use a dedicated system initialization step for the stack checker interrupt stack support. Update #3838. --- cpukit/include/rtems/sysinit.h | 1 + cpukit/libmisc/stackchk/check.c | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/cpukit/include/rtems/sysinit.h

[PATCH 4/7] bsps: Add RTEMS_SYSINIT_BSP_EARLY

Add new BSP system initialization step for work to be performed before the work areas are initialized. Update #3838. --- bsps/powerpc/beatnik/start/bspstart.c | 19 --- bsps/powerpc/motorola_powerpc/start/bspstart.c | 19 ---

[PATCH 3/7] bsps: Add RamEnd to linker command files

Update #3838. --- bsps/arm/shared/start/linkcmds.base | 1 + bsps/bfin/TLL6527M/start/linkcmds| 1 + bsps/bfin/bf537Stamp/start/linkcmds | 1 + bsps/bfin/eZKit533/start/linkcmds| 1 + bsps/epiphany/epiphany_sim/start/linkcmds| 1 +

[PATCH 2/7] score: Add _Memory_Dirty()

Update #3838. --- cpukit/Makefile.am | 1 + cpukit/include/rtems/score/memory.h | 11 - cpukit/score/src/memorydirty.c | 48 + 3 files changed, 59 insertions(+), 1 deletion(-) create mode 100644 cpukit/score/src/memorydirty.c

Re: Problem running RTEMS on raspberrypi3

On Mon, Dec 16, 2019 at 2:36 AM Christian Mauderer wrote: > > > On 15/12/2019 21:29, Niteesh wrote: > > > > > > On Mon, Dec 16, 2019 at 12:53 AM Christian Mauderer > > wrote: > > > > On 15/12/2019 19:46, Niteesh wrote: > > > > > > > > > On Sun, Dec 15,