Re: [PATCH rtems-source-builder 1/2] Update to gdb 13.1 for rtems 6

2023-02-22 Thread Frank Kühndel 

Hello Joel,

On 2/21/23 16:25, Joel Sherrill wrote:

Subject:
[PATCH rtems-source-builder 1/2] Update to gdb 13.1 for rtems 6
From:
Joel Sherrill 
Date:
2/21/23, 16:25

To:
devel@rtems.org


---
  rtems/config/6/rtems-default.bset |  2 +-
  rtems/config/tools/rtems-gdb-13.1.cfg | 16 
  2 files changed, 17 insertions(+), 1 deletion(-)
  create mode 100644 rtems/config/tools/rtems-gdb-13.1.cfg

diff --git a/rtems/config/6/rtems-default.bset 
b/rtems/config/6/rtems-default.bset
index a0601aa..a76efe6 100644
--- a/rtems/config/6/rtems-default.bset
+++ b/rtems/config/6/rtems-default.bset
@@ -12,7 +12,7 @@
  %defineifnot with_rtems_dtc  devel/dtc-1.6.1-1
  %defineifnot with_rtems_expatdevel/expat-2.4.8-1
  %defineifnot with_rtems_gmp  devel/gmp-6.2.1
-%defineifnot with_rtems_gdb  tools/rtems-gdb-12.1
+%defineifnot with_rtems_gdb  tools/rtems-gdb-13.1
  %defineifnot with_rtems_binutils tools/rtems-binutils-2.38
  %defineifnot with_rtems_gcc  tools/rtems-gcc-12-newlib-head
  %defineifnot with_rtems_toolstools/rtems-tools-6
diff --git a/rtems/config/tools/rtems-gdb-13.1.cfg 
b/rtems/config/tools/rtems-gdb-13.1.cfg
new file mode 100644
index 000..4a6a1c7
--- /dev/null
+++ b/rtems/config/tools/rtems-gdb-13.1.cfg
@@ -0,0 +1,16 @@
+#
+# GDB 12.1


Is 12.1 correct? It looks like a copy-paste error.

Greetings
Frank


+#
+
+%include %{_configdir}/checks.cfg
+%include %{_configdir}/base.cfg
+
+%define gdb_version 13.1
+%define gdb_src_ext xz
+%hash sha512 gdb-%{gdb_version}.tar.xz \
+   
5lBU/7wDV+7tSxfh7cXvRapzyd3zsSEGUePYWVduJ8HSeyZoAP4mMo7aWIV0VczYYy9AAM/F9j+QhUCWKQGHyg==
+
+#%patch add gdb 
--rsb-file=gdb-readline8.2.patchhttps://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=1add37b567a7dee39d99f37b37802034c3fce9c4
+#%hash sha512 gdb-readline8.2.patch 
E/nGalfBBfn0rl/pi1SGIuKD11x0qREZBp3ajaFbl/nGMZUIm31M/1z0FsG76K7IjvE5pPsl2JqESt+LBN9lZA==
+
+%include %{_configdir}/gdb-common-1.cfg
-- 2.24.4 ___ devel mailing 
list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel




--
embedded brains GmbH
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email: frank.kuehn...@embedded-brains.de
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11
fax:+49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0

2023-02-22 Thread Hesham Almatary 
On Tue, 21 Feb 2023 at 14:30,  wrote:
>
> Hello everyone,
>
> I tried to build a riscv BSP with the information from Hesham. Thanks again.
> It now compiles the files, but produces a lot of warnings and fails to link 
> in the end.
>
> The warnings are of this type
> ../../../cpukit/score/cpu/riscv/riscv-exception-handler.S:48:10: warning: 
> unknown option, expected 'push', 'pop', 'rvc', 'norvc', 'relax' or 'norelax'
>.option arch, +zicsr
>^
Does this happen if you use the latest LLVM?

> And in the end the linker cannot find the " _RISCV_Exception_handler", so I 
> guess the warning prevents those symbols from being built. My best guess is 
> that it is related to this llvm issue: https://reviews.llvm.org/D141666 which 
> is actively worked on as of this month and we probably have to wait for this 
> to become part of llvm.
>
Are you sure the right linker is used (lld?) I remember I had to add a
custom patch for RTEMS to be able to use the right linker and options.
https://github.com/CTSRD-CHERI/clang/blob/master/lib/Driver/ToolChains/RTEMS.cpp

> Out of curiosity, I tried the same with the Zedboard BSP. There, linking 
> passed and I got to this point for base_sp.exe:
> *** BEGIN OF TEST OH ***
> *** TEST VERSION: 6.0.0.c0fad60c59bf14b9d1a4eb3d76f872e2cf43e7b8
> *** TEST STATE: (null)
> *** TEST BUILD:
> *** TEST TOOLS: Clang 11.1.0 (https://git.rtems.org/rtems-source-builder 
> 64df106288cf6c4289a9c78850a82bfb2b41caa2)
> Creating and starting an application task
>
> *** FATAL ***
> fatal source: 0 (INTERNAL_ERROR_CORE)
> fatal code: 31 (INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT)
> RTEMS version: 6.0.0.c0fad60c59bf14b9d1a4eb3d76f872e2cf43e7b8
> RTEMS tools: Clang 11.1.0 (https://git.rtems.org/rtems-source-builder 
> 64df106288cf6c4289a9c78850a82bfb2b41caa2)
> executing thread is NULL
>
> So, let's say it's something. Now at least I have a system to debug. I will 
> also have a look how to make the process more accessible. At the moment 
> things are just crowbarred into the build system to make it work.
>
> Coming back to the patch: If there are no objections I would like to push the 
> commit for llvm11.
> Chances are that further updates are to come as I progress.
>
> Best regards,
>
> Jan
>
> > -Original Message-
> > From: Hesham Almatary 
> > Sent: Mittwoch, 15. Februar 2023 11:17
> > To: Sommer, Jan 
> > Cc: j...@rtems.org; devel@rtems.org
> > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0
> >
> > On Wed, 15 Feb 2023 at 09:22,  wrote:
> > >
> > >
> > >
> > > > -Original Message-
> > > > From: Hesham Almatary 
> > > > Sent: Montag, 13. Februar 2023 16:19
> > > > To: Sommer, Jan 
> > > > Cc: j...@rtems.org; devel@rtems.org
> > > > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0
> > > >
> > > > On Mon, 13 Feb 2023 at 12:12,  wrote:
> > > > >
> > > > > > -Original Message-
> > > > > > From: Joel Sherrill 
> > > > > > Sent: Freitag, 10. Februar 2023 15:21
> > > > > > To: Sommer, Jan 
> > > > > > Cc: devel@rtems.org
> > > > > > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Feb 10, 2023 at 3:16 AM Jan Sommer  > > > > >  > wrote:
> > > > > >
> > > > > >
> > > > > >   Hello,
> > > > > >
> > > > > >   I couldn't get the rtems-llvm buildset to work.
> > > > > >   As it was building llvm8 which is not that modern, I just 
> > > > > > tried to
> > build
> > > > > >   a more recent version with the scripts.
> > > > > >   It works with llvm11. Are there any objections to updating?
> > > > > >
> > > > > >
> > > > > >
> > > > > > Nope. Please feel free to add this.
> > > > > >
> > > > > >
> > > > > >   And should we keep the rtems-llvm-8.cfg or should I remove
> > > > > > this with
> > > > > >   this patch?
> > > > > >
> > > > > >
> > > > > >
> > > > > >  My main concern is if the architectures that built with llvm 8
> > > > > > still build with llvm 11. I think that's only SPARC and RISC-V.
> > > > > > Are there
> > > > others?
> > > > > >
> > > > Why not the latest LLVM (especially to pick up the latest RISC-V
> > > > fixes/support). I am not sure how mature the RISC-V support is in
> > > > LLVM 8, if it was supported at all.
> > > >
> > >
> > > Yes, that is also my goal. I got llvm11 building with only small changes 
> > > to the
> > buildset and wanted to go from there.
> > > In the meantime I also managed to build llvm up to 14 locally. Once I have
> > all the bits and pieces working to some degree I will probably consolidate 
> > to a
> > more recent version.
> > >
> > Seems like a good plan.
> >
> > > > > > I guess that points to me not knowing the list of architectures
> > > > > > that are expected to work. I wonder where we would keep this
> > information.
> > > > > > Any thoughts?
> > > > > >
> > > > >
> > > > > Thanks for the information.
> > > > > I tried to build those to check if they still work

RE: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0

2023-02-22 Thread Jan.Sommer 



> -Original Message-
> From: Hesham Almatary 
> Sent: Mittwoch, 22. Februar 2023 14:34
> To: Sommer, Jan 
> Cc: j...@rtems.org; devel@rtems.org
> Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0
> 
> On Tue, 21 Feb 2023 at 14:30,  wrote:
> >
> > Hello everyone,
> >
> > I tried to build a riscv BSP with the information from Hesham. Thanks again.
> > It now compiles the files, but produces a lot of warnings and fails to link 
> > in
> the end.
> >
> > The warnings are of this type
> > ../../../cpukit/score/cpu/riscv/riscv-exception-handler.S:48:10: warning:
> unknown option, expected 'push', 'pop', 'rvc', 'norvc', 'relax' or 'norelax'
> >.option arch, +zicsr
> >^
> Does this happen if you use the latest LLVM?
> 

The latest I tried so far was llvm14 and there it happened. Do you know if this 
might be solved in more recent versions?
llvm14 was the latest I could build with the shipped compilers of my 
workstation.

> > And in the end the linker cannot find the " _RISCV_Exception_handler", so
> I guess the warning prevents those symbols from being built. My best guess
> is that it is related to this llvm issue: https://reviews.llvm.org/D141666 
> which
> is actively worked on as of this month and we probably have to wait for this
> to become part of llvm.
> >
> Are you sure the right linker is used (lld?) I remember I had to add a custom
> patch for RTEMS to be able to use the right linker and options.
> https://github.com/CTSRD-
> CHERI/clang/blob/master/lib/Driver/ToolChains/RTEMS.cpp
> 

So far I used the linker of the rtems6-gcc toolchain.

> > Out of curiosity, I tried the same with the Zedboard BSP. There, linking
> passed and I got to this point for base_sp.exe:
> > *** BEGIN OF TEST OH ***
> > *** TEST VERSION: 6.0.0.c0fad60c59bf14b9d1a4eb3d76f872e2cf43e7b8
> > *** TEST STATE: (null)
> > *** TEST BUILD:
> > *** TEST TOOLS: Clang 11.1.0
> > (https://git.rtems.org/rtems-source-builder
> > 64df106288cf6c4289a9c78850a82bfb2b41caa2)
> > Creating and starting an application task
> >
> > *** FATAL ***
> > fatal source: 0 (INTERNAL_ERROR_CORE)
> > fatal code: 31
> (INTERNAL_ERROR_BAD_THREAD_DISPATCH_ENVIRONMENT)
> > RTEMS version: 6.0.0.c0fad60c59bf14b9d1a4eb3d76f872e2cf43e7b8
> > RTEMS tools: Clang 11.1.0 (https://git.rtems.org/rtems-source-builder
> > 64df106288cf6c4289a9c78850a82bfb2b41caa2)
> > executing thread is NULL
> >
> > So, let's say it's something. Now at least I have a system to debug. I will 
> > also
> have a look how to make the process more accessible. At the moment things
> are just crowbarred into the build system to make it work.
> >
> > Coming back to the patch: If there are no objections I would like to push
> the commit for llvm11.
> > Chances are that further updates are to come as I progress.
> >
> > Best regards,
> >
> > Jan
> >
> > > -Original Message-
> > > From: Hesham Almatary 
> > > Sent: Mittwoch, 15. Februar 2023 11:17
> > > To: Sommer, Jan 
> > > Cc: j...@rtems.org; devel@rtems.org
> > > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0
> > >
> > > On Wed, 15 Feb 2023 at 09:22,  wrote:
> > > >
> > > >
> > > >
> > > > > -Original Message-
> > > > > From: Hesham Almatary 
> > > > > Sent: Montag, 13. Februar 2023 16:19
> > > > > To: Sommer, Jan 
> > > > > Cc: j...@rtems.org; devel@rtems.org
> > > > > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version 11.1.0
> > > > >
> > > > > On Mon, 13 Feb 2023 at 12:12,  wrote:
> > > > > >
> > > > > > > -Original Message-
> > > > > > > From: Joel Sherrill 
> > > > > > > Sent: Freitag, 10. Februar 2023 15:21
> > > > > > > To: Sommer, Jan 
> > > > > > > Cc: devel@rtems.org
> > > > > > > Subject: Re: [PATCH v1 0/1] Update rtems-llvm to version
> > > > > > > 11.1.0
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Feb 10, 2023 at 3:16 AM Jan Sommer
> > > > > > > mailto:jan.som...@dlr.de> > wrote:
> > > > > > >
> > > > > > >
> > > > > > >   Hello,
> > > > > > >
> > > > > > >   I couldn't get the rtems-llvm buildset to work.
> > > > > > >   As it was building llvm8 which is not that modern, I
> > > > > > > just tried to
> > > build
> > > > > > >   a more recent version with the scripts.
> > > > > > >   It works with llvm11. Are there any objections to updating?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Nope. Please feel free to add this.
> > > > > > >
> > > > > > >
> > > > > > >   And should we keep the rtems-llvm-8.cfg or should I
> > > > > > > remove this with
> > > > > > >   this patch?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >  My main concern is if the architectures that built with
> > > > > > > llvm 8 still build with llvm 11. I think that's only SPARC and 
> > > > > > > RISC-V.
> > > > > > > Are there
> > > > > others?
> > > > > > >
> > > > > Why not the latest LLVM (especially to pick up the latest RISC-V
> > > > > fixes/support). I am not sure how mature the RISC-V support is
> > >

[PATCH] riscv: Update RISC-V BSPs

2023-02-22 Thread Hesham Almatary 
* Only use BSPs supported by GCC's multilibs. This removes rv32imafdc
* Remove BSPs with medany name in them (See #4775).
RV64 BSPs are now all medany by default.
---
 config/rtems-bsps-riscv.ini | 5 ++---
 config/rtems-bsps-tiers.ini | 5 ++---
 2 files changed, 4 insertions(+), 6 deletions(-)

diff --git a/config/rtems-bsps-riscv.ini b/config/rtems-bsps-riscv.ini
index 804245e..af037ec 100644
--- a/config/rtems-bsps-riscv.ini
+++ b/config/rtems-bsps-riscv.ini
@@ -23,7 +23,6 @@
 [riscv]
 bsps = frdme310arty,
griscv, grv32i, grv32im, grv32imac, grv32imafdc,
-   rv32iac, rv32i, rv32imac, rv32imafc, rv32imafdc, rv32imafd, rv32im,
-   rv64imac, rv64imac_medany, rv64imafdc, rv64imafd, rv64imafdc_medany,
-   rv64imafd_medany
+   rv32iac, rv32i, rv32imac, rv32imafc, rv32imafd, rv32im,
+   rv64imac, rv64imafdc, rv64imafd
 exclude-smp = rv32i, rv32im
diff --git a/config/rtems-bsps-tiers.ini b/config/rtems-bsps-tiers.ini
index 9b52429..c8b4ad5 100644
--- a/config/rtems-bsps-tiers.ini
+++ b/config/rtems-bsps-tiers.ini
@@ -124,9 +124,8 @@ bsps_powerpc = beatnik,
 virtex, virtex4, virtex5
 bsps_riscv = griscv, grv32i, grv32im, grv32imac, grv32imafdc,
 frdme310arty,
-rv32i, rv32iac, rv32im, rv32imac, rv32imafc, rv32imafd, rv32imafdc,
-rv64imac, rv64imac_medany, rv64imafd, rv64imafd_medany,
-rv64imafdc, rv64imafdc_medany
+rv32i, rv32iac, rv32im, rv32imac, rv32imafc, rv32imafd,
+rv64imac, rv64imafd, rv64imafdc
 bsps_sh = gensh1, gensh2, gensh4, simsh1, simsh2, simsh2e, simsh4
 bsps_sparc = at697f, gr712rc, ut699, ut700, gr740
 bsps_sparc64 = niagara, usiii
-- 
2.25.1

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-source-builder 1/2] Update to gdb 13.1 for rtems 6

2023-02-22 Thread Joel Sherrill 
Is it ok to push if I fix the comment?

--joel

On Wed, Feb 22, 2023 at 3:29 AM Frank Kühndel <
frank.kuehn...@embedded-brains.de> wrote:

> Hello Joel,
>
> On 2/21/23 16:25, Joel Sherrill wrote:
> > Subject:
> > [PATCH rtems-source-builder 1/2] Update to gdb 13.1 for rtems 6
> > From:
> > Joel Sherrill 
> > Date:
> > 2/21/23, 16:25
> >
> > To:
> > devel@rtems.org
> >
> >
> > ---
> >   rtems/config/6/rtems-default.bset |  2 +-
> >   rtems/config/tools/rtems-gdb-13.1.cfg | 16 
> >   2 files changed, 17 insertions(+), 1 deletion(-)
> >   create mode 100644 rtems/config/tools/rtems-gdb-13.1.cfg
> >
> > diff --git a/rtems/config/6/rtems-default.bset
> b/rtems/config/6/rtems-default.bset
> > index a0601aa..a76efe6 100644
> > --- a/rtems/config/6/rtems-default.bset
> > +++ b/rtems/config/6/rtems-default.bset
> > @@ -12,7 +12,7 @@
> >   %defineifnot with_rtems_dtc  devel/dtc-1.6.1-1
> >   %defineifnot with_rtems_expatdevel/expat-2.4.8-1
> >   %defineifnot with_rtems_gmp  devel/gmp-6.2.1
> > -%defineifnot with_rtems_gdb  tools/rtems-gdb-12.1
> > +%defineifnot with_rtems_gdb  tools/rtems-gdb-13.1
> >   %defineifnot with_rtems_binutils tools/rtems-binutils-2.38
> >   %defineifnot with_rtems_gcc  tools/rtems-gcc-12-newlib-head
> >   %defineifnot with_rtems_toolstools/rtems-tools-6
> > diff --git a/rtems/config/tools/rtems-gdb-13.1.cfg
> b/rtems/config/tools/rtems-gdb-13.1.cfg
> > new file mode 100644
> > index 000..4a6a1c7
> > --- /dev/null
> > +++ b/rtems/config/tools/rtems-gdb-13.1.cfg
> > @@ -0,0 +1,16 @@
> > +#
> > +# GDB 12.1
>
> Is 12.1 correct? It looks like a copy-paste error.
>
> Greetings
> Frank
>
> > +#
> > +
> > +%include %{_configdir}/checks.cfg
> > +%include %{_configdir}/base.cfg
> > +
> > +%define gdb_version 13.1
> > +%define gdb_src_ext xz
> > +%hash sha512 gdb-%{gdb_version}.tar.xz \
> > +
>  
> 5lBU/7wDV+7tSxfh7cXvRapzyd3zsSEGUePYWVduJ8HSeyZoAP4mMo7aWIV0VczYYy9AAM/F9j+QhUCWKQGHyg==
> > +
> > +#%patch add gdb --rsb-file=gdb-readline8.2.patchhttps://
> sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=1add37b567a7dee39d99f37b37802034c3fce9c4
> > +#%hash sha512 gdb-readline8.2.patch
> E/nGalfBBfn0rl/pi1SGIuKD11x0qREZBp3ajaFbl/nGMZUIm31M/1z0FsG76K7IjvE5pPsl2JqESt+LBN9lZA==
> > +
> > +%include %{_configdir}/gdb-common-1.cfg
> > -- 2.24.4 ___ devel mailing
> > list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
> >
>
> --
> embedded brains GmbH
> Herr Frank KÜHNDEL
> Dornierstr. 4
> 82178 Puchheim
> Germany
> email: frank.kuehn...@embedded-brains.de
> phone:  +49-89-18 94 741 - 23
> mobile: +49-176-15 22 06 - 11
> fax:+49-89-18 94 741 - 08
>
> Registergericht: Amtsgericht München
> Registernummer: HRB 157899
> Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
> Unsere Datenschutzerklärung finden Sie hier:
> https://embedded-brains.de/datenschutzerklaerung/
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] riscv: Update RISC-V BSPs

2023-02-22 Thread Joel Sherrill 
This is OK.

Be sure to follow up with a patch to bump the rtems-tools hash in the RSB.

--joel

On Wed, Feb 22, 2023 at 9:14 AM Hesham Almatary 
wrote:

> * Only use BSPs supported by GCC's multilibs. This removes rv32imafdc
> * Remove BSPs with medany name in them (See #4775).
> RV64 BSPs are now all medany by default.
> ---
>  config/rtems-bsps-riscv.ini | 5 ++---
>  config/rtems-bsps-tiers.ini | 5 ++---
>  2 files changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/config/rtems-bsps-riscv.ini b/config/rtems-bsps-riscv.ini
> index 804245e..af037ec 100644
> --- a/config/rtems-bsps-riscv.ini
> +++ b/config/rtems-bsps-riscv.ini
> @@ -23,7 +23,6 @@
>  [riscv]
>  bsps = frdme310arty,
> griscv, grv32i, grv32im, grv32imac, grv32imafdc,
> -   rv32iac, rv32i, rv32imac, rv32imafc, rv32imafdc, rv32imafd, rv32im,
> -   rv64imac, rv64imac_medany, rv64imafdc, rv64imafd,
> rv64imafdc_medany,
> -   rv64imafd_medany
> +   rv32iac, rv32i, rv32imac, rv32imafc, rv32imafd, rv32im,
> +   rv64imac, rv64imafdc, rv64imafd
>  exclude-smp = rv32i, rv32im
> diff --git a/config/rtems-bsps-tiers.ini b/config/rtems-bsps-tiers.ini
> index 9b52429..c8b4ad5 100644
> --- a/config/rtems-bsps-tiers.ini
> +++ b/config/rtems-bsps-tiers.ini
> @@ -124,9 +124,8 @@ bsps_powerpc = beatnik,
>  virtex, virtex4, virtex5
>  bsps_riscv = griscv, grv32i, grv32im, grv32imac, grv32imafdc,
>  frdme310arty,
> -rv32i, rv32iac, rv32im, rv32imac, rv32imafc, rv32imafd, rv32imafdc,
> -rv64imac, rv64imac_medany, rv64imafd, rv64imafd_medany,
> -rv64imafdc, rv64imafdc_medany
> +rv32i, rv32iac, rv32im, rv32imac, rv32imafc, rv32imafd,
> +rv64imac, rv64imafd, rv64imafdc
>  bsps_sh = gensh1, gensh2, gensh4, simsh1, simsh2, simsh2e, simsh4
>  bsps_sparc = at697f, gr712rc, ut699, ut700, gr740
>  bsps_sparc64 = niagara, usiii
> --
> 2.25.1
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Many failures on RISC-V BSPs

2023-02-22 Thread Joel Sherrill 
Hi

This may be mechanical but
https://lists.rtems.org/pipermail/build/2023-February/date.html shows
recent RTEMS test runs with a lot of RISC-V BSP failures. Scanning them, it
seems as though there are 100s of test failures when SMP is enabled. Here
is one example:

https://lists.rtems.org/pipermail/build/2023-February/042279.html

Any ideas?

--joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH rtems-source-builder 1/2] Update to gdb 13.1 for rtems 6

2023-02-22 Thread Frank Kühndel 

On 2/22/23 16:26, Joel Sherrill wrote:

Is it ok to push if I fix the comment?


I confess I have not tried your patch. I noted you have commented out 
the gdb-readline8.2.patch. Beside that no surprises and from my side you 
can go ahead.


Greetings
Frank



--joel

On Wed, Feb 22, 2023 at 3:29 AM Frank Kühndel <
frank.kuehn...@embedded-brains.de> wrote:


Hello Joel,

On 2/21/23 16:25, Joel Sherrill wrote:

Subject:
[PATCH rtems-source-builder 1/2] Update to gdb 13.1 for rtems 6
From:
Joel Sherrill
Date:
2/21/23, 16:25

To:
devel@rtems.org


---
   rtems/config/6/rtems-default.bset |  2 +-
   rtems/config/tools/rtems-gdb-13.1.cfg | 16 
   2 files changed, 17 insertions(+), 1 deletion(-)
   create mode 100644 rtems/config/tools/rtems-gdb-13.1.cfg

diff --git a/rtems/config/6/rtems-default.bset

b/rtems/config/6/rtems-default.bset

index a0601aa..a76efe6 100644
--- a/rtems/config/6/rtems-default.bset
+++ b/rtems/config/6/rtems-default.bset
@@ -12,7 +12,7 @@
   %defineifnot with_rtems_dtc  devel/dtc-1.6.1-1
   %defineifnot with_rtems_expatdevel/expat-2.4.8-1
   %defineifnot with_rtems_gmp  devel/gmp-6.2.1
-%defineifnot with_rtems_gdb  tools/rtems-gdb-12.1
+%defineifnot with_rtems_gdb  tools/rtems-gdb-13.1
   %defineifnot with_rtems_binutils tools/rtems-binutils-2.38
   %defineifnot with_rtems_gcc  tools/rtems-gcc-12-newlib-head
   %defineifnot with_rtems_toolstools/rtems-tools-6
diff --git a/rtems/config/tools/rtems-gdb-13.1.cfg

b/rtems/config/tools/rtems-gdb-13.1.cfg

new file mode 100644
index 000..4a6a1c7
--- /dev/null
+++ b/rtems/config/tools/rtems-gdb-13.1.cfg
@@ -0,0 +1,16 @@
+#
+# GDB 12.1

Is 12.1 correct? It looks like a copy-paste error.

Greetings
Frank


+#
+
+%include %{_configdir}/checks.cfg
+%include %{_configdir}/base.cfg
+
+%define gdb_version 13.1
+%define gdb_src_ext xz
+%hash sha512 gdb-%{gdb_version}.tar.xz \
+

  
5lBU/7wDV+7tSxfh7cXvRapzyd3zsSEGUePYWVduJ8HSeyZoAP4mMo7aWIV0VczYYy9AAM/F9j+QhUCWKQGHyg==

+
+#%patch add gdb --rsb-file=gdb-readline8.2.patchhttps://

sourceware.org/git/?p=binutils-gdb.git;a=commitdiff_plain;h=1add37b567a7dee39d99f37b37802034c3fce9c4

+#%hash sha512 gdb-readline8.2.patch

E/nGalfBBfn0rl/pi1SGIuKD11x0qREZBp3ajaFbl/nGMZUIm31M/1z0FsG76K7IjvE5pPsl2JqESt+LBN9lZA==

+
+%include %{_configdir}/gdb-common-1.cfg
-- 2.24.4 ___ devel mailing
listde...@rtems.org  http://lists.rtems.org/mailman/listinfo/devel


--
embedded brains GmbH
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email:frank.kuehn...@embedded-brains.de
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11
fax:+49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel




--
embedded brains GmbH
Herr Frank KÜHNDEL
Dornierstr. 4
82178 Puchheim
Germany
email: frank.kuehn...@embedded-brains.de
phone:  +49-89-18 94 741 - 23
mobile: +49-176-15 22 06 - 11
fax:+49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

RFC #4666 TFTP: Implement block and window size options

2023-02-22 Thread Joel Sherrill 
Hi Sebastian,

This ticket has a number of commits logged against it. What remains or can
it be closed?

https://devel.rtems.org/ticket/4666

If it can't be closed, an update on what needs to be done should be added
and maybe the milestone bumped.

Thanks.

--joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: [PATCH] riscv: Update RISC-V BSPs

2023-02-22 Thread Sebastian Huber 

On 22.02.23 16:14, Hesham Almatary wrote:

* Remove BSPs with medany name in them (See #4775).
RV64 BSPs are now all medany by default.


Do we still need the non-medany 64-bit multilibs in GCC? I plan to 
adjust the multilib selection a bit and also add multilibs for 
non-compact 32-bit variants.


--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

RTEMS Open Class (virtual) April 24-28, 2023

2023-02-22 Thread Joel Sherrill 
Hi

There will be an RTEMS Open Class held virtually the week of April 24-28
Times each day will be based on the US Central time zone (Chicago).
Adjustments
may be considered to accommodate the participants.

April 24  - Kick Start and Getting Started
April 25-28 - Open Class

Details and registration forms at http://rtems.com/trainingschedule.

If you have questions at all about the class, feel free to email me
directly.

Thanks.

--Joel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Jetson Nano BSP

2023-02-22 Thread Prakhar Agrawal 
Hello,

Does the current RTEMS version support the Jetson nano board, if not, do
you think It will be a good project for gsoc2023? something like porting
RTEMS to Jetson nano or jetson AGX orin maybe?

Looking forward to your response.

Best Regards
Prakhar
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Ticket #4272 BSP executable conversion project

2023-02-22 Thread Prakhar Agrawal 
Hello,

My name is Prakhar Agrawal and I am interested in contributing to RTEMS as
a gsoc this year.

While going through the list of open projects, the BSP executable
conversion project caught my interest.

I have completed the hello world task for gsoc and now looking to start
contributing to the projects. Can you please guide me in the right
direction with the correct resources and a list of tasks, which I can
follow to learn more about the above project and also start contributing to
the same?

Looking forward to the responses.

Best Regards
Prakhar
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: Jetson Nano BSP

2023-02-22 Thread Joel Sherrill 
On Wed, Feb 22, 2023, 9:26 PM Prakhar Agrawal 
wrote:

> Hello,
>
> Does the current RTEMS version support the Jetson nano board, if not, do
> you think It will be a good project for gsoc2023? something like porting
> RTEMS to Jetson nano or jetson AGX orin maybe?
>

I'm torn whether this is a good project or not. It is quite ambitious but
it appears that a fair amount of the boards horsepower is tied to binary
blobs which likely won't work with RTEMS.

One challenge is that much of the support will be GPL licensed which is
unacceptable for RTEMS.

That said, it may be feasible since freebsd appears to support it now. I
have no idea what devices work under freebsd. But if you can boot freebsd
on it and see what works, that would be great information.

https://cgit.freebsd.org/src/commit/?id=e903478919602c90fdc202a8628b89eb7c3bc104

The other side of this is how useful this will be either for RTEMS users.
What would a hobbyist use it for? A production team?

Is the board too old to be worth the effort for the limited audience?

Honestly I'd rather see a new BSP for a decent RISC-V board.



> Looking forward to your response.
>

I'm also curious to hear what others think.

--joel

>
> Best Regards
> Prakhar
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel