linking error in rtems_record_server.c but bsp is configured with --disable-networking

2021-04-30 Thread Juan Solano
Hi all, I am learning my way around RTEMS, developing a BSP for Xilinx Zynq, using RTEMS 5. I configure with --disable-networking but I have a linking error when building the BSP, a networking function in librtemscpu.a is compiled in, should this be happening? There are missing references to s

[PATCH 1/2] covoar: Store only the file name in ExecutableInfo

2021-04-30 Thread Alex White
This changes the ExecutableInfo class to only store the executable file's name rather than an entire instance of rld::files::object. This allows the rld::files::object to be cleaned up in the ExecutableInfo constructor. Updates #4383 --- tester/covoar/ExecutableInfo.cc | 12 +--- tester/c

[PATCH 2/2] covoar: Store address-to-line info outside of DWARF

2021-04-30 Thread Alex White
This adds the AddressToLineMapper class and supporting classes to assume responsibility of tracking address-to-line information. This allows the DWARF library to properly cleanup all of its resources and leads to significant memory savings. Closes #4383 --- rtemstoolkit/rld-dwarf.cpp |

[PATCH 0/2] covoar: Dispose of file info in ExecutableInfo

2021-04-30 Thread Alex White
This patch set includes two patches that significantly lower the memory usage of covoar. For a full coverage run of the leon3 BSP on my machine, the peak memory usage falls from 9.6 GB down to 1.4 GB. The cleanup of the ELF and DWARF info had previously been moved from the ExecutableInfo class's c

RFS and 2038

2021-04-30 Thread Joel Sherrill
Hi Ryan has been working to add support for the new (not obsolete) nanosecond granularity variants of utime. In changing the utime_h file system handler to utimens_h and propagating the changes, Ryan tripped across this. rtems/rfs/rtems-rfs-inode.h:typedef uint32_t rtems_rfs_time; Our first incl

Re: [PATCH] rtems-examples: Add CoreMark Benchmark

2021-04-30 Thread Hesham Almatary
Hello Damien, Glad to know you have an interest in it. Yes, we needed to add Make support for it, I just didn't get to work on that yet. Do you need to exclusively use Make and not waf though? On Fri, 30 Apr 2021 at 16:50, BAILLIEZ Damien wrote: > > Hi all, > > > > I’ve seen in the Archives that

[PATCH] spmisc01: Test RTEMS_NOINIT

2021-04-30 Thread Sebastian Huber
Close #3866. --- testsuites/sptests/spmisc01/init.c | 5 + 1 file changed, 5 insertions(+) diff --git a/testsuites/sptests/spmisc01/init.c b/testsuites/sptests/spmisc01/init.c index e64fa4e480..6fbc0eeff8 100644 --- a/testsuites/sptests/spmisc01/init.c +++ b/testsuites/sptests/spmisc01/init.

[PATCH] score: Add _Thread_Dispatch_direct_no_return()

2021-04-30 Thread Sebastian Huber
The __builtin_unreachable() cannot be used with current GCC versions to tell the compiler that a function does not return to the caller, see: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99151 Add a no return variant of _Thread_Dispatch_direct() to avoid generation of dead code. --- cpukit/inclu

Re: [PATCH] rtems-examples: Add CoreMark Benchmark

2021-04-30 Thread BAILLIEZ Damien
Hi all, I've seen in the Archives that the discussion about adding the CoreMark Benchmark ended a few weeks ago on the subject of Make support, which greatly interests me. Does someone involved with this know if there has been any progress ? Regards, Damien __

[PATCH 1/2] basedefs: Add RTEMS_NOINIT

2021-04-30 Thread Sebastian Huber
Update #3866. --- cpukit/include/rtems/score/basedefs.h | 42 +-- 1 file changed, 26 insertions(+), 16 deletions(-) diff --git a/cpukit/include/rtems/score/basedefs.h b/cpukit/include/rtems/score/basedefs.h index 71dc18216e..33fb272291 100644 --- a/cpukit/include/rtems/sc

[PATCH 2/2] bsps: Support RTEMS_NOINIT in linkcmds

2021-04-30 Thread Sebastian Huber
Close #3866. --- bsps/arm/include/bsp/arm-cp15-start.h| 6 +- bsps/arm/include/bsp/linker-symbols.h| 4 bsps/arm/shared/start/linkcmds.base | 7 +++ bsps/bfin/TLL6527M/start/linkcmds| 4 bsps/bfin/bf537Stamp/start/linkcmds

Re: [PATCH] riscv/start: Startup sequence update.

2021-04-30 Thread Sebastian Huber
On 30/04/2021 15:32, Hesham Almatary wrote: The noinit attributes is a bit broken in GCC: I guess we can go for a separate custom section then? Or we can just assign it a magic value so that it doesn’t go into BSS. I propose to add something like this: +/* Generated from spec:/rtems/bas

Re: [PATCH] riscv/start: Startup sequence update.

2021-04-30 Thread Hesham Almatary
On Fri, 30 Apr 2021 at 14:22, Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 29/04/2021 20:53, Sebastian Huber wrote: > > > On 29/04/2021 20:18, Hesham Almatary wrote: > > > I would place the device tree in a noinit section. > > >>> That is probably a better solution.

Re: [PATCH] riscv/start: Startup sequence update.

2021-04-30 Thread somesh deshmukh
Hi Sebastian, For testing, I had manually added the device tree blob address into the a1 register. On Fri, Apr 30, 2021 at 6:52 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 29/04/2021 20:53, Sebastian Huber wrote: > > > On 29/04/2021 20:18, Hesham Almatary wrote: > > > >>

Re: [PATCH] riscv/start: Startup sequence update.

2021-04-30 Thread Sebastian Huber
On 29/04/2021 20:53, Sebastian Huber wrote: On 29/04/2021 20:18, Hesham Almatary wrote: I would place the device tree in a noinit section. That is probably a better solution. It should also be documented in this start.S file what are the assumptions about parameters coming from the bootload

Re: RTEMS source builder: can't find RTEMS include files but then can?

2021-04-30 Thread dufault
> On Apr 30, 2021, at 05:03 , dufa...@hda.com wrote: > > Can I override what to use as "cmake" in RSB to specify "cmake3"? > >> On Apr 30, 2021, at 04:41 , Peter Dufault wrote: >> >> I verified my environment is squeaky-clean with a simple path and no >> environment variables set that affect

Re: [PATCH] riscv/console: Updated the console-config.c file

2021-04-30 Thread Hesham Almatary
On Fri, 30 Apr 2021 at 04:44, somesh deshmukh wrote: > > > On Thu, Apr 29, 2021 at 10:59 PM Hesham Almatary < > hesham.almat...@cl.cam.ac.uk> wrote: > >> On Wed, 28 Apr 2021 at 15:23, Somesh Deshmukh >> wrote: >> > >> > - Parsing the sub-node should be available generic not specific to >> Freedo

[PATCH] riscv/console: console-config.c update

2021-04-30 Thread Somesh Deshmukh
- Parsing the sub-node should be available generic not specific to Freedom Arty310 board. If we remove the Freedom Arty macro now, it will lose backward compatibility.The proposed change will retain the backward compatibility and also adds the necessary fix for parsing sub-node. - Restored n

Re: RTEMS source builder: can't find RTEMS include files but then can?

2021-04-30 Thread dufault
I lied. I had /usr/local/bin in my path to pick up "cmake3" instead of the system "cmake". I thought I repeated the test with PATH set to just /usr/bin and /usr/sbin, but I hadn't. Can I override what to use as "cmake" in RSB to specify "cmake3"? > On Apr 30, 2021, at 04:41 , Peter Dufault w

RTEMS source builder: can't find RTEMS include files but then can?

2021-04-30 Thread Peter Dufault
I updated to the latest "Simple Open EtherCAT Master" (SOEM) git and the build failed because gcc couldn't find . This is weird because: - is where it shoud be; - "gcc" had already compiled a source file that included just before it failed to find . To debug I turned off the "-j" (just becau

Re: Issues with rtems_waf on Windows 10 with gccdeps module

2021-04-30 Thread Robin Müller
The "dirty solution" actually only works if the drive is named C, and maybe the backslashes should not be there in the first place. Maybe you already have dealt with this issue? Kind Regards Robin On Fri, 30 Apr 2021 at 10:36, Robin Müller wrote: > Issue can be reproduced by doing the quickstar

Re: Issues with rtems_waf on Windows 10 with gccdeps module

2021-04-30 Thread Robin Müller
Issue can be reproduced by doing the quickstart application build on Windows 10. The issue are backslashes in the absolute paths of the dependency paths which were not stripped from dependency paths on Windows, causing waf to not recognize them as valid absolute paths. More specifically, I printed