Skip to content

Comments

Fix: mtda-rpi4b-ebg target#564

Merged
chombourger merged 2 commits intosiemens:nextfrom
bniedermayr:bump-isar
Feb 2, 2026
Merged

Fix: mtda-rpi4b-ebg target#564
chombourger merged 2 commits intosiemens:nextfrom
bniedermayr:bump-isar

Conversation

@bniedermayr
Copy link

@bniedermayr bniedermayr commented Jan 21, 2026

This fixes the mtda-rpi4b-ebg which can be used to integrated full swupdate support.

Multiple things were fixed:

  • Update isar and isar-cip core to to their current master. Fixes the reference to stale commits (isar-cip-core next).
    Note:It's not recommended to reference isar-cip-core next since it's getting rebased from time to time
  • Switch to debian-trixie: The reason for this was to update u-boot (u-boot-rpi) which contains important fixes for booting on the rpi4b platform.

@github-actions github-actions bot requested a review from chombourger January 21, 2026 19:54
@bniedermayr bniedermayr changed the base branch from master to next January 21, 2026 19:56
@bniedermayr bniedermayr marked this pull request as draft January 21, 2026 19:57
Bump isar and isar-cip-core to current master.
Using "next" for the isar-cip-core is dangerous since the branch
is getting rebased occasionally.

Signed-off-by: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
@bniedermayr bniedermayr marked this pull request as ready for review January 21, 2026 20:02
@bniedermayr bniedermayr changed the title Update isar and isar-cip-core Fix: Update isar and isar-cip-core Jan 22, 2026
@bniedermayr bniedermayr marked this pull request as draft January 26, 2026 12:23
@bniedermayr bniedermayr changed the title Fix: Update isar and isar-cip-core Fix: mtda-rpi4b-ebg target Jan 27, 2026
This fixes booting the image for the rpi4b-ebg target. The used u-boot
verion on debian-bookworm (2023.01+dfsg-2+deb12u2) refuses to boot on
rpi4 platforms:

```
Found EFI removable media binary efi/boot/bootaa64.efi
** Reading file would overwrite reserved memory **
Failed to load 'efi/boot/bootaa64.efi'
```

Important fixes have been added to u-boot 2023.04 regarding the lmb
implementation which fixes the above error.

The easiest fix is to just upgrade to debian trixie.

Signed-off-by: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
includes:
- kas/common/base.yml
- kas/debian/bookworm-base.yml
- kas/debian/trixie-base.yml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense, but we should keep the whole MTDA layer on a single default distribution, as the protocol between mtda-cli and the server is incompatible between bookworm and trixie (i.e. a bookworm client cannot access a trixie server and vice versa). #524

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So should I look for another fix in order to stay on bookworm? Or do you mean to upgrade the layer to trixie?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The solution itself is fine, but I'm not sure if we should apply this fix just to the rpi4 target. In the end, that means if you build for rpi4 it will be trixie based, otherwise it will be bookworm based. Let's ask @chombourger for guidance.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

given what mtda remains under heavy development, it probably makes sense to get everything on trixie and remove support for bookworm. it may be difficult to support both Debian N and N-1. Would you agree @fmoessbauer and @bniedermayr ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree.

@chombourger chombourger marked this pull request as ready for review February 2, 2026 18:56
@chombourger chombourger merged commit 2696d7e into siemens:next Feb 2, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants