Hi Daniel, I've done some experiments as well [1]. Could you try prefixing the "kas build" command with "gosu builder"? Something like this: gosu builder kas build --target core-image-minimal

Hi Michael, [snip] I tried but I got this weird behavior: https://gitlab.com/cip-project/cip-core/deby/-/jobs/228110647 $ export USER_ID=30000 $ /bin/bash /kas/docker-entrypoint $ whoami root $ cat

Oh, good. I understand the desire to limit the support burden. But I hope that there is a plan to support a newer kernel version eventually, if necessary. Ben. -- Ben Hutchings, Software

Hello, Actually, the iwg20m board does work with the upstream Kernel as well as v4.19.y-cip, e.g. [1]. I think it's just that Renesas doesn't intend to support the board with anything other than

[...] "-Wl,-z,relro" is a gcc option which should result in passing "-z relro" to the linker. Perhaps a Makefile is invoking $(LD) with $(LDFLAGS), where it should be invoking $(CC) instead? In any

[...] This really shouldn't be allowed to happen. All the patches applied to 4.4-cip to support this board were already upstream, so this must be a regression. If this board is used as a basis for

Alright, the token exchange was successful this morning and gitlab-cloud-ci runner should be visible to all child projects now. However, we ran into an issue [1] when executing Daniel's CI

Ah, now I read the reasoning properly - got it, unfortunate, but makes sense. We can add that patch to isar-cip-core until we update to a version that contains it -> follow-up patch. Jan

Hi, You could just use the mkimage that comes from your u-boot source to be certain. I do something similar [1] since the upstream debian u-boot-tools do not support creating signed fit images. [1]

Continuing with this conversation on the public list, it seems that the job on gitlab-cloud-ci failed: https://gitlab.com/cip-project/cip-core/deby/-/jobs/226291592 --- Error summary --- ERROR:

ext4load seems to be available on the u-boot command line. After loading boot.scr, don't we need the "source" command to work? "source" does not seem to be configured in the pre-installed

This patch adds support for the iwg20m board to isar-cip-core. - Kernel version notes This board is only supported by the 4.4 kernel. For that reason, the preferred version is set to 4.4 and the

Hi Jan, Here is the patch again with kernel set to 4.4 by default [next] iwg20m: add support for this board Thanks, Daniel P.S.: sorry for not using some prefix the last time.

Hi Daniel, sure, no problem! I suggest moving my instance of the gitlab-ci runner to the project-level. Then it should be visible to all sub-projects (which includes your project). For this however,

As you are cross-posting, the subject should probably also contain some tag like "[isar-cip-core]", to clarify the target project. In fact, that would even help on cip-dev as we now have quite a few

Hello Michael, I have added an initial, very simple, gitlab-ci yaml script for building CIP tiny profile (Deby for BBB). https://gitlab.com/cip-project/cip-core/deby/blob/master/.gitlab-ci.yml I

Sorry, i forgot to fill the subject line for the --compose option.

This patch adds support for the iwg20m board to isar-cip-core. - Kernel version notes This board is only supported by the 4.4 kernel. The document doc/README_iwg20m.md already explains that. -

Hi Jan, This patch adds support for the iwg20m board on ISAR CIP Core. [PATCH] iwg20m: add support for this board For now, it uses the u-boot shipped with the board. We could improve that in the