Re: arm/tms570ls3137_hdk_with_loader build failures

[Sebastian Huber]

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.

--
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: [PATCH 4/6] build: Add support to make bootloader images

[Chris Johns]

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.

> 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"?

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

Re: Multiple PowerPC BSPs Fail to BUIld

[Chris Johns]

On 10/3/2024 8:40 am, Joel Sherrill wrote:
> Hi
> 
> 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?

There has been some PowerPC interrupt changes recently.

I do not have access to a mvme2700 to test these changes and awhen I can is not
known at this point in time. My concern is the interconnected relationship these
BSPs have makes them fragile. The last release that had working interrupts on
the mvme2700 was 4.10 and 5 did not work until I updated the release branch. We
had broken interrupts for years. I would like to avoid this if possible.

Chris

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

does anyone tried "Zynq on Qemu with a USB"

[ashish ashish]

I am trying to use zynq on qemu and plugging usb device or unplugging
device doesn't show any log message  and libbsd testsuite media01 is used
and using command
```
sudo qemu-system-arm -serial null -serial mon:stdio -nographic \
-M
xilinx-zynq-a9 -m 256M \
  -device
usb-host,hostbus=3,hostport=3 \
-kernel
build/arm-rtems6-xilinx_zynq_a9_qemu-default/media01.exe```
i am new to this project and anyone got working zynq on qemu with a usb.
just help!
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel