date:20240311

Re: rtems-6.1-rc2 on Mac OSX Sonoma 14.4 (Apple M2) failed -> fixed

2024-03-11 Thread Chris Johns

[ Sorry, my email does not show your message ]

Hi Heinz,

I see you are using brew on your M machine which is fine. As an alternative I
have documented using python.org:

 https://docs.rtems.org/branches/master/user/hosts/macos.html#python

and a virtual environment.

Chris

On 12/3/2024 2:09 pm, Heinz Junkes wrote:
> 
> ___
> 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: Multiple PowerPC BSPs Fail to BUIld

2024-03-11 Thread Chris Johns

On 11/3/2024 6:04 pm, Sebastian Huber wrote:
> sorry for breaking the build. I fixed it. The problem is that 
> header file depends on the BSP-provided define BSP_SHARED_HANDLER_SUPPORT. So,
> the include order matters.

Thank you for quickly sorting this out.

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

Re: rtems-6.1-rc2 on Mac OSX Sonoma 14.4 (Apple M2) failed -> fixed

2024-03-11 Thread Heinz Junkes

Hi
After updating Xcode and OSX to Sonoma 14.4 the Python libs 'disappeared’ ?
Upgrade/update python on homebrew and brew link python3 fixed it.
Heinz

> On 11. Mar 2024, at 16:27, Heinz Junkes  wrote:
>
> Hi,
>
> I am trying to install rc2 on sonoma 14.4 (Apple M2) and unfortunately get
>
> error: config error: gdb-common-1.cfg:146: "gdb: python: library file not 
> found: libpython3.11.*, please install”
>
> It looks like the error described in ticket #4631.
>
> Heinz
>
>
> (base) junkes@Zarquon rtems % ../source-builder/sb-set-builder 
> --prefix=/Volumes/Epics/6_1_RC2/6.1-rc2 6/rtems-powerpc
> RTEMS Source Builder - Set Builder, 6.1-rc2
> Build Set: 6/rtems-powerpc
> Build Set: tools/rtems-default-tools.bset
> config: devel/dtc-1.6.1-1.cfg
> package: dtc-1.6.1-arm64-apple-darwin23.4.0-1
> building: dtc-1.6.1-arm64-apple-darwin23.4.0-1
> sizes: dtc-1.6.1-arm64-apple-darwin23.4.0-1: 3.057MB (installed: 704.209KB)
> cleaning: dtc-1.6.1-arm64-apple-darwin23.4.0-1
> reporting: devel/dtc-1.6.1-1.cfg -> dtc-1.6.1-arm64-apple-darwin23.4.0-1.txt
> reporting: devel/dtc-1.6.1-1.cfg -> dtc-1.6.1-arm64-apple-darwin23.4.0-1.xml
> config: devel/expat-2.5.0-1.cfg
> package: expat-2.5.0-arm64-apple-darwin23.4.0-1
> download: 
> https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/expat-2.5.0.tar.gz
>  -> sources/expat-2.5.0.tar.gz
> downloading: sources/expat-2.5.0.tar.gz - 702.4kB of 702.4kB (100%)  
> building: expat-2.5.0-arm64-apple-darwin23.4.0-1
> sizes: expat-2.5.0-arm64-apple-darwin23.4.0-1: 7.704MB (installed: 905.753KB)
> cleaning: expat-2.5.0-arm64-apple-darwin23.4.0-1
> reporting: devel/expat-2.5.0-1.cfg -> 
> expat-2.5.0-arm64-apple-darwin23.4.0-1.txt
> reporting: devel/expat-2.5.0-1.cfg -> 
> expat-2.5.0-arm64-apple-darwin23.4.0-1.xml
> config: devel/gmp-6.3.0.cfg
> package: gmp-6.3.0-arm64-apple-darwin23.4.0-1
> download: 
> https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/gmp-6.3.0.tar.bz2
>  -> sources/gmp-6.3.0.tar.bz2
> downloading: sources/gmp-6.3.0.tar.bz2 - 2.5MB of 2.5MB (100%)building: 
> gmp-6.3.0-arm64-apple-darwin23.4.0-1
> sizes: gmp-6.3.0-arm64-apple-darwin23.4.0-1: 22.973MB (installed: 1.402MB)
> cleaning: gmp-6.3.0-arm64-apple-darwin23.4.0-1
> reporting: devel/gmp-6.3.0.cfg -> gmp-6.3.0-arm64-apple-darwin23.4.0-1.txt
> reporting: devel/gmp-6.3.0.cfg -> gmp-6.3.0-arm64-apple-darwin23.4.0-1.xml
> Build Set: textproc/gsed-internal.bset
> config: textproc/gsed.cfg
> package: gsed-4.9-arm64-apple-darwin23.4.0-1
> download: 
> https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/sed-4.9.tar.gz 
> -> sources/sed-4.9.tar.gz
> downloading: sources/sed-4.9.tar.gz - 2.2MB of 2.2MB (100%)building: 
> gsed-4.9-arm64-apple-darwin23.4.0-1
> sizes: gsed-4.9-arm64-apple-darwin23.4.0-1: 19.157MB (installed: 0.000B)
> cleaning: gsed-4.9-arm64-apple-darwin23.4.0-1
> cleaning: gsed-4.9-arm64-apple-darwin23.4.0-1
> Build Set: Time 0:00:37.403237
> Build Set: print/texinfo-internal.bset
> config: print/texinfo.cfg
> package: texinfo-7.0.3-arm64-apple-darwin23.4.0-1
> download: 
> https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/texinfo-7.0.3.tar.gz
>  -> sources/texinfo-7.0.3.tar.gz
> download: 
> https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/texinfo-7.0.3.tar.gz:
>  error: HTTP Error 404: Not Found
> download: https://ftp.gnu.org/gnu/texinfo/texinfo-7.0.3.tar.gz -> 
> sources/texinfo-7.0.3.tar.gz
> downloading: sources/texinfo-7.0.3.tar.gz - 10.3MB of 10.3MB (100%)   
> building: texinfo-7.0.3-arm64-apple-darwin23.4.0-1
> sizes: texinfo-7.0.3-arm64-apple-darwin23.4.0-1: 88.975MB (installed: 0.000B)
> cleaning: texinfo-7.0.3-arm64-apple-darwin23.4.0-1
> cleaning: texinfo-7.0.3-arm64-apple-darwin23.4.0-1
> Build Set: Time 0:00:39.965456
> config: tools/rtems-gdb-13.2.cfg
> error: config error: gdb-common-1.cfg:146: "gdb: python: library file not 
> found: libpython3.11.*, please install"
> Build FAILED
> Build Set: Time 0:02:10.561549
> error: config error: gdb-common-1.cfg:146: "gdb: python: library file not 
> found: libpython3.11.*, please install"
> Build Set: Time 0:02:10.563376
> Build FAILED
>
> --
> Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
> Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
> Faradayweg 4-6| VC: https://zoom.fhi.berlin/junkes
> D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
> --
>
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel




smime.p7s
Description: S/MIME cryptographic signature
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

rtems-6.1-rc2 on Mac OSX Sonoma 14.4 (Apple M2) failed

2024-03-11 Thread Heinz Junkes

Hi,

I am trying to install rc2 on sonoma 14.4 (Apple M2) and unfortunately get

error: config error: gdb-common-1.cfg:146: "gdb: python: library file not 
found: libpython3.11.*, please install”

It looks like the error described in ticket #4631.

Heinz


(base) junkes@Zarquon rtems % ../source-builder/sb-set-builder 
--prefix=/Volumes/Epics/6_1_RC2/6.1-rc2 6/rtems-powerpc
RTEMS Source Builder - Set Builder, 6.1-rc2
Build Set: 6/rtems-powerpc
Build Set: tools/rtems-default-tools.bset
config: devel/dtc-1.6.1-1.cfg
package: dtc-1.6.1-arm64-apple-darwin23.4.0-1
building: dtc-1.6.1-arm64-apple-darwin23.4.0-1
sizes: dtc-1.6.1-arm64-apple-darwin23.4.0-1: 3.057MB (installed: 704.209KB)
cleaning: dtc-1.6.1-arm64-apple-darwin23.4.0-1
reporting: devel/dtc-1.6.1-1.cfg -> dtc-1.6.1-arm64-apple-darwin23.4.0-1.txt
reporting: devel/dtc-1.6.1-1.cfg -> dtc-1.6.1-arm64-apple-darwin23.4.0-1.xml
config: devel/expat-2.5.0-1.cfg
package: expat-2.5.0-arm64-apple-darwin23.4.0-1
download: 
https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/expat-2.5.0.tar.gz
 -> sources/expat-2.5.0.tar.gz
downloading: sources/expat-2.5.0.tar.gz - 702.4kB of 702.4kB (100%)  building: 
expat-2.5.0-arm64-apple-darwin23.4.0-1
sizes: expat-2.5.0-arm64-apple-darwin23.4.0-1: 7.704MB (installed: 905.753KB)
cleaning: expat-2.5.0-arm64-apple-darwin23.4.0-1
reporting: devel/expat-2.5.0-1.cfg -> expat-2.5.0-arm64-apple-darwin23.4.0-1.txt
reporting: devel/expat-2.5.0-1.cfg -> expat-2.5.0-arm64-apple-darwin23.4.0-1.xml
config: devel/gmp-6.3.0.cfg
package: gmp-6.3.0-arm64-apple-darwin23.4.0-1
download: 
https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/gmp-6.3.0.tar.bz2 
-> sources/gmp-6.3.0.tar.bz2
downloading: sources/gmp-6.3.0.tar.bz2 - 2.5MB of 2.5MB (100%)building: 
gmp-6.3.0-arm64-apple-darwin23.4.0-1
sizes: gmp-6.3.0-arm64-apple-darwin23.4.0-1: 22.973MB (installed: 1.402MB)
cleaning: gmp-6.3.0-arm64-apple-darwin23.4.0-1
reporting: devel/gmp-6.3.0.cfg -> gmp-6.3.0-arm64-apple-darwin23.4.0-1.txt
reporting: devel/gmp-6.3.0.cfg -> gmp-6.3.0-arm64-apple-darwin23.4.0-1.xml
Build Set: textproc/gsed-internal.bset
config: textproc/gsed.cfg
package: gsed-4.9-arm64-apple-darwin23.4.0-1
download: 
https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/sed-4.9.tar.gz -> 
sources/sed-4.9.tar.gz
downloading: sources/sed-4.9.tar.gz - 2.2MB of 2.2MB (100%)building: 
gsed-4.9-arm64-apple-darwin23.4.0-1
sizes: gsed-4.9-arm64-apple-darwin23.4.0-1: 19.157MB (installed: 0.000B)
cleaning: gsed-4.9-arm64-apple-darwin23.4.0-1
cleaning: gsed-4.9-arm64-apple-darwin23.4.0-1
Build Set: Time 0:00:37.403237
Build Set: print/texinfo-internal.bset
config: print/texinfo.cfg
package: texinfo-7.0.3-arm64-apple-darwin23.4.0-1
download: 
https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/texinfo-7.0.3.tar.gz
 -> sources/texinfo-7.0.3.tar.gz
download: 
https://ftp.rtems.org/pub/rtems/releases/6/rc/6.1-rc2/sources/texinfo-7.0.3.tar.gz:
 error: HTTP Error 404: Not Found
download: https://ftp.gnu.org/gnu/texinfo/texinfo-7.0.3.tar.gz -> 
sources/texinfo-7.0.3.tar.gz
downloading: sources/texinfo-7.0.3.tar.gz - 10.3MB of 10.3MB (100%)   building: 
texinfo-7.0.3-arm64-apple-darwin23.4.0-1
sizes: texinfo-7.0.3-arm64-apple-darwin23.4.0-1: 88.975MB (installed: 0.000B)
cleaning: texinfo-7.0.3-arm64-apple-darwin23.4.0-1
cleaning: texinfo-7.0.3-arm64-apple-darwin23.4.0-1
Build Set: Time 0:00:39.965456
config: tools/rtems-gdb-13.2.cfg
error: config error: gdb-common-1.cfg:146: "gdb: python: library file not 
found: libpython3.11.*, please install"
Build FAILED
Build Set: Time 0:02:10.561549
error: config error: gdb-common-1.cfg:146: "gdb: python: library file not 
found: libpython3.11.*, please install"
Build Set: Time 0:02:10.563376
Build FAILED

--
Fritz-Haber-Institut| Phone: (+49 30) 8413-4270
Heinz Junkes | Fax (G3+G4):   (+49 30) 8413-5900
Faradayweg 4-6| VC: https://zoom.fhi.berlin/junkes
D - 14195 Berlin| E-Mail:jun...@fhi-berlin.mpg.de
--



smime.p7s
Description: S/MIME cryptographic signature
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: arm/tms570ls3137_hdk_with_loader build failures

2024-03-11 Thread Joel Sherrill

On Mon, Mar 11, 2024 at 12:14 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> On 09.03.24 22:39, Joel Sherrill wrote:
> > Hi
> >
> > The build sweep using rtems-bsp-builder reports that 8 build
> > configurations of arm/tms570ls3137_hdk_with_loader fail. See the
> > following for more details.
> >
> > https://lists.rtems.org/pipermail/build/2024-March/051698.html
> > 
> >
> > The first reported configuration is:
> >
> > 1 debug arm/tms570ls3137_hdk_with_loader configure:
> >configure: /home/tester/rtems-cron-6/rtems/waf configure\
> >--prefix=/home/tester/rtems-cron-6/tools/6/bsps
> --top=/home/tester\
> >/rtems-cron-6/rtems --rtems-config=config-arm-\
> >tms570ls3137_hdk_with_loader-debug.ini
> >
> > It would be appreciated if someone could look into that and fix it.
>
> This should be fixed by:
>
> commit 9fdaa4e7c7577710405dab0da828ff9d0710a2d0
> Author: Sebastian Huber 
> Date:   Sat Jan 20 21:55:47 2024 +0100
>
>  config: Update BSPs
>
>  Update #4982.
>

Thanks. The RSB is still referencing an RTEMS tool hash from August. I will
fix that and the newlib hash once the fdset limit is pushed.

It would be nice to have a way to check that ./rtems-bsps and the
rtems-bsp-builder sets of BSPs match.

Thanks.

--joel

>
> --
> embedded brains GmbH & Co. KG
> 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

[PATCH rtems-tools] rtems-score-thread.ini: Remove _Thread_Close so trace examples link

2024-03-11 Thread Joel Sherrill

_Thread_Close no longer exists. There are multiple exapmles which
show tracing in rtems-examples which fail to link due to this.
---
 linkers/rtems-score-thread.ini | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/linkers/rtems-score-thread.ini b/linkers/rtems-score-thread.ini
index 974bcfd..a759f72 100644
--- a/linkers/rtems-score-thread.ini
+++ b/linkers/rtems-score-thread.ini
@@ -5,7 +5,7 @@
 trace = _Thread_Handler_initialization, _Thread_Create_idle, 
_Thread_Start_multitasking
 trace = _Stack_Allocate, _Stack_Free, _Thread_Start
 trace = _Thread_Yield, _Thread_Set_life_protection
-trace = _Thread_Kill_zombies, _Thread_Close
+trace = _Thread_Kill_zombies
 trace = _Thread_Clear_state, _Thread_Set_state, _Thread_Load_environment
 trace = _Thread_Handler
 trace = _Thread_Get
@@ -19,7 +19,7 @@ trace = _Stack_Allocate, _Thread_Start
 trace = _Thread_Restart, _Thread_Handler
 
 [rtems-score-thread-destroy]
-trace = _Thread_Kill_zombies, _Thread_Close
+trace = _Thread_Kill_zombies
 
 [rtems-score-thread-activity]
 trace = _Thread_Yield, _Thread_Set_life_protection
@@ -38,7 +38,6 @@ _Thread_Start = Status_Control, Thread_Control*, const 
Thread_Entry_information*
 _Thread_Yield = void, Thread_Control*
 _Thread_Set_life_protection = Thread_Life_state, Thread_Life_state
 _Thread_Kill_zombies = void, void
-_Thread_Close = void, Thread_Control*, Thread_Control*, Thread_Close_context*
 _Thread_Clear_state = States_Control, Thread_Control*, States_Control
 _Thread_Set_state = States_Control, Thread_Control*, States_Control
 _Thread_Load_environment = void, Thread_Control*
-- 
2.24.4

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

Re: Assistance Needed: Locating arm-rtems5-gdb implementation in source code

2024-03-11 Thread Kinsey Moore

On Mon, Mar 11, 2024 at 6:18 AM Xin Zheng  wrote:

> Hello everyone,
>
>
>
> I’m currently working with RTEMS for ARM architecture and I’m facing
> challenges locating the implementation details for arm-rtems5-gdb in the
> RTEMS source code. Despite my efforts, I have been unable to pinpoint the
> exact location.
>
>
>
> Could you kindly guide me to the specific location within the source code
> where I can find the arm-rtems5-gdb implementation? Any additional
> information or pointers would be greatly appreciated.
>

Hi,
arm-rtems5-gdb would be built with the 5/rtems-arm recipe in RSB. That
overall recipe is located at
rtems-source-builder/rtems/config/5/rtems-arm.bset, but it looks like it
has been removed in recent versions (since 40af487dfc26). You can check out
the RSB 5 branch with "git checkout 5" get access to the current versions
of the 5/rtems-arm recipe.

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

Re: [PATCH] aarch64/zynqmp: Fix UART base addresses and IRQ

2024-03-11 Thread Kinsey Moore

Looks good to me. The overall effect of this is no functional change.
Thanks for the cleanup!

Kinsey

On Mon, Mar 11, 2024 at 8:25 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:

> The base addresses and IRQ numbers for UART 0 and 1 were interchanged.
> Fix this and set BSP_CONSOLE_MINOR to 0 for this BSP family.
> ---
>  bsps/aarch64/xilinx-zynqmp/console/console.c | 4 ++--
>  bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h | 4 ++--
>  spec/build/bsps/optconminor.yml  | 1 +
>  3 files changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/bsps/aarch64/xilinx-zynqmp/console/console.c
> b/bsps/aarch64/xilinx-zynqmp/console/console.c
> index 0b62893e67..9ce0b1da63 100644
> --- a/bsps/aarch64/xilinx-zynqmp/console/console.c
> +++ b/bsps/aarch64/xilinx-zynqmp/console/console.c
> @@ -187,11 +187,11 @@ RTEMS_SYSINIT_ITEM(
>  static zynq_uart_context zynqmp_uart_instances[2] = {
>{
>  .base = RTEMS_TERMIOS_DEVICE_CONTEXT_INITIALIZER( "Zynq UART 0" ),
> -.regs = (volatile struct zynq_uart *) 0xff01,
> +.regs = (volatile struct zynq_uart *) 0xff00,
>  .irq = ZYNQMP_IRQ_UART_0
>}, {
>  .base = RTEMS_TERMIOS_DEVICE_CONTEXT_INITIALIZER( "Zynq UART 1" ),
> -.regs = (volatile struct zynq_uart *) 0xff00,
> +.regs = (volatile struct zynq_uart *) 0xff01,
>  .irq = ZYNQMP_IRQ_UART_1
>}
>  };
> diff --git a/bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h
> b/bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h
> index 2cbe99f863..024fd0d89a 100644
> --- a/bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h
> +++ b/bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h
> @@ -56,8 +56,8 @@ extern "C" {
>  #define ZYNQMP_IRQ_QSPI 47
>  #define ZYNQMP_IRQ_I2C_0 49
>  #define ZYNQMP_IRQ_I2C_1 50
> -#define ZYNQMP_IRQ_UART_0 54
> -#define ZYNQMP_IRQ_UART_1 53
> +#define ZYNQMP_IRQ_UART_0 53
> +#define ZYNQMP_IRQ_UART_1 54
>  #define ZYNQMP_IRQ_ETHERNET_0 89
>  #define ZYNQMP_IRQ_ETHERNET_1 91
>  #define ZYNQMP_IRQ_ETHERNET_2 93
> diff --git a/spec/build/bsps/optconminor.yml
> b/spec/build/bsps/optconminor.yml
> index 514b3fa032..3f17f05fe7 100644
> --- a/spec/build/bsps/optconminor.yml
> +++ b/spec/build/bsps/optconminor.yml
> @@ -7,6 +7,7 @@ copyrights:
>  - Copyright (C) 2020 embedded brains GmbH & Co. KG
>  default:
>  - enabled-by:
> +  - aarch64/bsps/xilinx-zynqmp
>- arm/xilinx_zynq_microzed
>value: 0
>  - enabled-by: true
> --
> 2.35.3
>
> ___
> 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

[PATCH] aarch64/zynqmp: Fix UART base addresses and IRQ

2024-03-11 Thread Sebastian Huber

The base addresses and IRQ numbers for UART 0 and 1 were interchanged.
Fix this and set BSP_CONSOLE_MINOR to 0 for this BSP family.
---
 bsps/aarch64/xilinx-zynqmp/console/console.c | 4 ++--
 bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h | 4 ++--
 spec/build/bsps/optconminor.yml  | 1 +
 3 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/bsps/aarch64/xilinx-zynqmp/console/console.c 
b/bsps/aarch64/xilinx-zynqmp/console/console.c
index 0b62893e67..9ce0b1da63 100644
--- a/bsps/aarch64/xilinx-zynqmp/console/console.c
+++ b/bsps/aarch64/xilinx-zynqmp/console/console.c
@@ -187,11 +187,11 @@ RTEMS_SYSINIT_ITEM(
 static zynq_uart_context zynqmp_uart_instances[2] = {
   {
 .base = RTEMS_TERMIOS_DEVICE_CONTEXT_INITIALIZER( "Zynq UART 0" ),
-.regs = (volatile struct zynq_uart *) 0xff01,
+.regs = (volatile struct zynq_uart *) 0xff00,
 .irq = ZYNQMP_IRQ_UART_0
   }, {
 .base = RTEMS_TERMIOS_DEVICE_CONTEXT_INITIALIZER( "Zynq UART 1" ),
-.regs = (volatile struct zynq_uart *) 0xff00,
+.regs = (volatile struct zynq_uart *) 0xff01,
 .irq = ZYNQMP_IRQ_UART_1
   }
 };
diff --git a/bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h 
b/bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h
index 2cbe99f863..024fd0d89a 100644
--- a/bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h
+++ b/bsps/aarch64/xilinx-zynqmp/include/bsp/irq.h
@@ -56,8 +56,8 @@ extern "C" {
 #define ZYNQMP_IRQ_QSPI 47
 #define ZYNQMP_IRQ_I2C_0 49
 #define ZYNQMP_IRQ_I2C_1 50
-#define ZYNQMP_IRQ_UART_0 54
-#define ZYNQMP_IRQ_UART_1 53
+#define ZYNQMP_IRQ_UART_0 53
+#define ZYNQMP_IRQ_UART_1 54
 #define ZYNQMP_IRQ_ETHERNET_0 89
 #define ZYNQMP_IRQ_ETHERNET_1 91
 #define ZYNQMP_IRQ_ETHERNET_2 93
diff --git a/spec/build/bsps/optconminor.yml b/spec/build/bsps/optconminor.yml
index 514b3fa032..3f17f05fe7 100644
--- a/spec/build/bsps/optconminor.yml
+++ b/spec/build/bsps/optconminor.yml
@@ -7,6 +7,7 @@ copyrights:
 - Copyright (C) 2020 embedded brains GmbH & Co. KG
 default:
 - enabled-by:
+  - aarch64/bsps/xilinx-zynqmp
   - arm/xilinx_zynq_microzed
   value: 0
 - enabled-by: true
-- 
2.35.3

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

Assistance Needed: Locating arm-rtems5-gdb implementation in source code

2024-03-11 Thread Xin Zheng

Hello everyone,

I'm currently working with RTEMS for ARM architecture and I'm facing challenges 
locating the implementation details for arm-rtems5-gdb in the RTEMS source 
code. Despite my efforts, I have been unable to pinpoint the exact location.

Could you kindly guide me to the specific location within the source code where 
I can find the arm-rtems5-gdb implementation? Any additional information or 
pointers would be greatly appreciated.

Thank you.

Xin

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

Re: [PATCH 4/6] build: Add support to make bootloader images

2024-03-11 Thread Sebastian Huber




On 11.03.24 00:40, Chris Johns wrote:

On 7/3/2024 5:27 pm, Sebastian Huber wrote:

On 07.03.24 02:09, Chris Johns wrote:

On 6/3/2024 8:33 am, Gedare Bloom wrote:

If script generation needs to be done, it should be implemented in
Python with input from the yml spec item as necessary to fill out a
templated script with variables to customize for the BSP, and with
appropriate injection of comments etc to allow traceability backward
to the original source data and source program that generated the
script.

We cannot import the YML data in external code without coping it as it all
resides in the wscript file. I would prefer seeing the YML python support moved
into `spec` as modules with unitests that can be imported. This would allow us
to add eco-system tools to support, manage and use the YML data.

The module to work with specification items is here:

https://github.com/RTEMS/rtems-central/blob/master/rtemsspec/items.py

This stuff has tests, code formatting, static analysis, and even a CI script.

This does not help rtens.git ans that is the scope of this patch set.


Yes, but you talked about "We cannot import the YML data in external 
code without coping it...". I assumed this referred to the RTEMS Tools.



Independent of this, working with the build specification items would be the
wrong approach. You need the input of a configured BSP.

I do not understand what this means. What is the "input of a configured BSP"?


Lets assume you have a BSP which has its RAM origin at A or B depending 
on the BSP configuration options. If you have a BSP installed configured 
to use A, then the bootloader image probably needs to be created using 
A. If it is configured to use B, it needs to use B.


--
embedded brains GmbH & Co. KG
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-6.1-rc2 on Mac OSX Ventura 13.6.1 (Intel Core i5)

2024-03-11 Thread Heinz Junkes

Hi,

I tried to build rc2 on OS-X (Ventura Intel) for powerpc and I get the 
following error:

RTEMS Tools Project - Source Builder Error Report
 Build: error: building 
powerpc-rtems6-gcc-13.2.0-newlib-3cacedb-x86_64-apple-darwin22.6.0-1
 Command Line: ../source-builder/sb-set-builder 
--prefix=/Volumes/RTEMS_DEV/RTEMS6_RC2/6.1-rc2 6/rtems-powerpc
 Python: 3.9.12 (main, Apr  5 2022, 01:53:17) [Clang 12.0.0 ]
 RSB: not a valid repo
 Darwin h.rz-berlin.mpg.de 22.6.0 Darwin Kernel Version 22.6.0: Wed Oct  4 
21:25:26 PDT 2023; root:xnu-8796.141.3.701.17~4/RELEASE_X86_64 x86_64
Tail of the build log:
Adding multilib support to Makefile in ../../../../../../gcc-13.2.0/libgcc
with_multisubdir=me6500/m64/vrsave
make[2]: Entering directory 
`/Volumes/RTEMS_DEV/RTEMS6_RC2/rtems-source-builder-6.1-rc2/rtems/build/powerpc-rtems6-gcc-13.2.0-newlib-3cacedb-x86_64-apple-darwin22.6.0-1/build/powerpc-rtems6/libgcc'
# If this is the top-level multilib, build all the other
ln -s ../../../gcc-13.2.0/libgcc/enable-execute-stack-empty.c 
enable-execute-stack.c
ln -s ../../../gcc-13.2.0/libgcc/unwind-generic.h unwind.h
ln -s ../../../gcc-13.2.0/libgcc/config/no-unwind.h md-unwind-support.h
ln -s ../../../gcc-13.2.0/libgcc/config/rs6000/sfp-machine.h sfp-machine.h
# multilibs.
...
/Volumes/RTEMS_DEV/RTEMS6_RC2/rtems-source-builder-6.1-rc2/rtems/build/powerpc-rtems6-gcc-13.2.0-newlib-3cacedb-x86_64-apple-darwin22.6.0-1/build/./gcc/xgcc
 
-B/Volumes/RTEMS_DEV/RTEMS6_RC2/rtems-source-builder-6.1-rc2/rtems/build/powerpc-rtems6-gcc-13.2.0-newlib-3cacedb-x86_64-apple-darwin22.6.0-1/build/./gcc/
 -nostdinc 
-B/Volumes/RTEMS_DEV/RTEMS6_RC2/rtems-source-builder-6.1-rc2/rtems/build/powerpc-rtems6-gcc-13.2.0-newlib-3cacedb-x86_64-apple-darwin22.6.0-1/build/powerpc-rtems6/newlib/
 -isystem 
/Volumes/RTEMS_DEV/RTEMS6_RC2/rtems-source-builder-6.1-rc2/rtems/build/powerpc-rtems6-gcc-13.2.0-newlib-3cacedb-x86_64-apple-darwin22.6.0-1/build/powerpc-rtems6/newlib/targ-include
 -isystem 
/Volumes/RTEMS_DEV/RTEMS6_RC2/rtems-source-builder-6.1-rc2/rtems/build/powerpc-rtems6-gcc-13.2.0-newlib-3cacedb-x86_64-apple-darwin22.6.0-1/gcc-13.2.0/newlib/libc/include
 -B/Volumes/RTEMS_DEV/RTEMS6_RC2/6.1-rc2/powerpc-rtems6/bin/ 
-B/Volumes/RTEMS_DEV/RTEMS6_RC2/6.1-rc2/powerpc-rtems6/lib/ -isystem 
/Volumes/RTEMS_DEV/RTEMS6_RC2/6.1-rc2/powerpc-rtems6/include -isystem 
/Volumes/RTEMS_DEV/RTEMS6_RC2/6.1-rc2/powerpc-rtems6/sys-include-g -O2 -O2 
-I../../../gcc-13.2.0/libgcc/../newlib/libc/sys/rtems/include -g -O2 -DIN_GCC  
-DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wno-narrowing -Wwrite-strings 
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  
-isystem ./include   -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector 
-Dinhibit_libc  -I. -I. -I../.././gcc -I../../../gcc-13.2.0/libgcc 
-I../../../gcc-13.2.0/libgcc/. -I../../../gcc-13.2.0/libgcc/../gcc 
-I../../../gcc-13.2.0/libgcc/../include  -DHAVE_CC_TLS   -o _gcov_merge_add.o 
-MT _gcov_merge_add.o -MD -MP -MF _gcov_merge_add.dep -DL_gcov_merge_add -c 
../../../gcc-13.2.0/libgcc/libgcov-merge.c
../../../gcc-13.2.0/libgcc/emutls.c: In function '__emutls_get_address':
../../../gcc-13.2.0/libgcc/emutls.c:172:13: warning: implicit declaration of 
function 'calloc' [-Wimplicit-function-declaration]
  172 |   arr = calloc (size + 1, sizeof (void *));
  | ^~
../../../gcc-13.2.0/libgcc/emutls.c:32:1: note: include '' or provide 
a declaration of 'calloc'
   31 | #include "gthr.h"
  +++ |+#include 
   32 |
../../../gcc-13.2.0/libgcc/emutls.c:172:13: warning: incompatible implicit 
declaration of built-in function 'calloc' [-Wbuiltin-declaration-mismatch]
  172 |   arr = calloc (size + 1, sizeof (void *));
  | ^~
../../../gcc-13.2.0/libgcc/emutls.c:172:13: note: include '' or 
provide a declaration of 'calloc'
../../../gcc-13.2.0/libgcc/emutls.c:184:13: warning: implicit declaration of 
function 'realloc' [-Wimplicit-function-declaration]
  184 |   arr = realloc (arr, (size + 1) * sizeof (void *));
  | ^~~
../../../gcc-13.2.0/libgcc/emutls.c:184:13: note: include '' or 
provide a declaration of 'realloc'
../../../gcc-13.2.0/libgcc/emutls.c:184:13: warning: incompatible implicit 
declaration of built-in function 'realloc' [-Wbuiltin-declaration-mismatch]
../../../gcc-13.2.0/libgcc/emutls.c:184:13: note: include '' or 
provide a declaration of ‘realloc'

…

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

Re: Multiple PowerPC BSPs Fail to BUIld

2024-03-11 Thread Sebastian Huber


Hello Joel,

On 09.03.24 22:40, Joel Sherrill wrote:
In looking at the build sweep log, I see what looks like 
motorola_powerpc and beatnik all have a common build failure that 
results in 53 configurations failing per


https://lists.rtems.org/pipermail/build/2024-March/051698.html 



This is one but there are a lot.

debug powerpc/mvme2307 build:
       configure: /home/tester/rtems-cron-6/rtems/waf configure\
       --prefix=/home/tester/rtems-cron-6/tools/6/bsps --top=/home/tester\
       /rtems-cron-6/rtems --rtems-config=config-powerpc-mvme2307-debug.ini
      error: home/tester/bsps/powerpc/include/bsp/irq_supp.h:87:65: error:
             'rtems_irq_connect_data' {aka 'struct
             __rtems_irq_connect_data__'} has no member named
             'next_handler'

Anyone care to fix that?


sorry for breaking the build. I fixed it. The problem is that 
 header file depends on the BSP-provided define 
BSP_SHARED_HANDLER_SUPPORT. So, the include order matters.


Some powerpc BSPs have linker errors in the tests:

Waf: Leaving directory `/tmp/sh/b-rtems/powerpc/gwlcfm'
Build failed
 -> task in 'testsuites/fstests/fsjffs2empty01.exe' failed with exit 
status 1 (run with -v to display more information)
 -> task in 'testsuites/fstests/jffs2nand_fsrdwr.exe' failed with exit 
status 1 (run with -v to display more information)
 -> task in 'testsuites/fstests/jffs2nand_fserror.exe' failed with exit 
status 1 (run with -v to display more information)
 -> task in 'testsuites/fstests/jffs2nand_fslink.exe' failed with exit 
status 1 (run with -v to display more information)
 -> task in 'testsuites/fstests/jffs2nand_fsscandir01.exe' failed with 
exit status 1 (run with -v to display more information)
 -> task in 'testsuites/fstests/jffs2nand_fssymlink.exe' failed with 
exit status 1 (run with -v to display more information)
 -> task in 'testsuites/fstests/jffs2nand_fspermission.exe' failed with 
exit status 1 (run with -v to display more information)
 -> task in 'testsuites/fstests/jffs2nand_fspatheval.exe' failed with 
exit status 1 (run with -v to display more information)
 -> task in 'testsuites/fstests/jffs2nand_fstime.exe' failed with exit 
status 1 (run with -v to display more information)


--
embedded brains GmbH & Co. KG
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

Re: rtems-6.1-rc2 on Mac OSX Sonoma 14.4 (Apple M2) failed -> fixed

Re: Multiple PowerPC BSPs Fail to BUIld

Re: rtems-6.1-rc2 on Mac OSX Sonoma 14.4 (Apple M2) failed -> fixed

rtems-6.1-rc2 on Mac OSX Sonoma 14.4 (Apple M2) failed

Re: arm/tms570ls3137_hdk_with_loader build failures

[PATCH rtems-tools] rtems-score-thread.ini: Remove _Thread_Close so trace examples link

Re: Assistance Needed: Locating arm-rtems5-gdb implementation in source code

Re: [PATCH] aarch64/zynqmp: Fix UART base addresses and IRQ

[PATCH] aarch64/zynqmp: Fix UART base addresses and IRQ

Assistance Needed: Locating arm-rtems5-gdb implementation in source code

Re: [PATCH 4/6] build: Add support to make bootloader images

rtems-6.1-rc2 on Mac OSX Ventura 13.6.1 (Intel Core i5)

Re: Multiple PowerPC BSPs Fail to BUIld

13 matches

Site Navigation

Mail list logo

Footer information