Hi Mohammed, > Should I be using the instructions outlined inhttps://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-demo to run a basic update of the CIP image on a BBB from hawkBit? Can the

Hello, Should I be using the instructions outlined in https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-demo to run a basic update of the CIP image on a BBB from hawkBit? Can the update

Hi, Mohammed-san, No worries. Meeting minutes will be produced at every meeting. So, you can check them out to see what is going on afterwards. FYI, last meeting minutes are the

Suzuki, M. Kudo: Thank you for getting back to me. I'll order the BBB, and start navigating the codebase until it arrives. I will try my best to make the meetings on Thursday, but it may be difficult

I understood now, i will rebase the patches with master branch and i will resend the patches for review, sorry for the confusion Currently we don't have such configuration changes, but most probably

Hi Mohammed, Thank you very much for your offer! I’m Akihiro Suzuki, a chair of SW Updates WG. Currently, we are using BeagleBone Black (BBB) for developing our initial software update

Hi, Mohammed-san, Thanks very much for watching the talk, and welcome to cip-dev! Regarding SW Update WG, the followings are the their wiki pages.

Hi all, just a note after watching https://sched.co/c46p, https://github.com/nexB/vulnerablecode: Still early, but might be worth looking at if we can benefit from it for vulnerability

Hello! I joined the mailing list from the recommendation on the IRC channel (after viewing the CIP talk at ELC). I'd like to work on the following issue:

... You are trying to sneak in more than a README ;) Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

From: Quirin Gylstorff <quirin.gylstorff@...> Use the Debian snakeoil keys to have a demo case available without the OVMF setup. Copy the used keys from the build to the deploy directory to

From: Quirin Gylstorff <quirin.gylstorff@...> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> --- doc/README.secureboot.md | 188 +++++++++++++++++++++++++++++++++++++++

From: Quirin Gylstorff <quirin.gylstorff@...> A unified kernel image contains the os-release, kernel, kernel commandline, initramfs and efi-stub in one binary. This binary can be boot by

From: Quirin Gylstorff <quirin.gylstorff@...> Adapt the initramfs generation to set for example the root device in the initramfs Signed-off-by: Quirin Gylstorff

From: Quirin Gylstorff <quirin.gylstorff@...> As the usage of a unified kernel image freeze the kernel commmandline during build time the rootfs selection for swupdate can no longer be done

From: Quirin Gylstorff <quirin.gylstorff@...> This patchset adds secureboot with efibootguard to cip-core. The image build signs the efibootguard bootloader (bootx64.efi) and generates a

From: Quirin Gylstorff <quirin.gylstorff@...> Add a fat configuration to access FAT Partitions on the qemu-amd64 target. Signed-off-by: Quirin Gylstorff <quirin.gylstorff@...> ---

From: Quirin Gylstorff <quirin.gylstorff@...> Create a swu file for swupdate to update devices in the field. This is done in the same step as the complete image build to avoid diverging

From: Quirin Gylstorff <quirin.gylstorff@...> Add swupdate for A/B software updates. Currently the Round Robin handler in lua supports efibootguard as bootloader. The u-boot implementation is