Conversation
5b1679c to
2a2d428
Compare
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>
2a2d428 to
b995c3a
Compare
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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
So should I look for another fix in order to stay on bookworm? Or do you mean to upgrade the layer to trixie?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 ?
This fixes the mtda-rpi4b-ebg which can be used to integrated full swupdate support.
Multiple things were fixed:
Note:It's not recommended to reference isar-cip-core next since it's getting rebased from time to time