| Message ID | 20220916114330.18443-1-Shivanand.Kunijadar@toshiba-tsip.com (mailing list archive) |
|---|---|
| State | Handled Elsewhere |
| Headers | show |
| Series | [isar-cip-core,v2] README.swupdate.md: Add steps to verify SWUpdate on BBB | expand |
Hi Jan, Could you please check the below revised patch and let me know your feedback. Thanks & Regards Shivanand K -----Original Message----- From: Shivanand.Kunijadar@toshiba-tsip.com <Shivanand.Kunijadar@toshiba-tsip.com> Sent: Friday, September 16, 2022 5:14 PM To: cip-dev@lists.cip-project.org; jan.kiszka@siemens.com Cc: kunijadar shivanand(ＴＳＩＰ TMIEC ODG Porting) <Shivanand.Kunijadar@toshiba-tsip.com>; dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ) <kazuhiro3.hayashi@toshiba.co.jp> Subject: [isar-cip-core v2] README.swupdate.md: Add steps to verify SWUpdate on BBB From: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com> Most of the steps are similar for both qemu-amd64 and BBB targets. Add reference link wherever required instead of repeating steps. Signed-off-by: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com> --- doc/README.swupdate.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md index 1b242a2..9be3498 100644 --- a/doc/README.swupdate.md +++ b/doc/README.swupdate.md @@ -32,6 +32,8 @@ Copy `cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost: ``` +## SWUpdate verification + Check which partition is booted, e.g. with lsblk: ``` root@demo:~# lsblk @@ -215,3 +217,26 @@ user variables: ``` + +# Building and testing the CIP Core image for BBB + +Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files. +- Replace qemu-amd64.yml kas file with BBB board specific file i.e +bbb.yml +- .swu file will be generated in the following folder +build/tmp/deploy/images/bbb/ + +Flash the BeagleBone Black image into SDcard ``` host$ dd +if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \ + of=/dev/<medium-device> bs=1M status=progress ``` + +After flashing the BBB image into SD card, mount the SD card on host PC and copy .swu file directly to root partition like below. + +``` +host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu +/<mnt>/home/root/ ``` + +Connect a serial port cable between host PC and BBB. +Insert SD card to BBB, hold S2 button while applying power supply to BBB. + +For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification). -- 2.20.1
On 16.09.22 13:43, Shivanand.Kunijadar@toshiba-tsip.com wrote: > From: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com> > > Most of the steps are similar for both qemu-amd64 and BBB targets. > Add reference link wherever required instead of repeating steps. > > Signed-off-by: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com> > --- > doc/README.swupdate.md | 25 +++++++++++++++++++++++++ > 1 file changed, 25 insertions(+) > > diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md > index 1b242a2..9be3498 100644 > --- a/doc/README.swupdate.md > +++ b/doc/README.swupdate.md > @@ -32,6 +32,8 @@ Copy `cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in > host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost: > ``` > > +## SWUpdate verification > + > Check which partition is booted, e.g. with lsblk: > ``` > root@demo:~# lsblk > @@ -215,3 +217,26 @@ user variables: > > > ``` > + > +# Building and testing the CIP Core image for BBB > + > +Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files. > +- Replace qemu-amd64.yml kas file with BBB board specific file i.e bbb.yml > +- .swu file will be generated in the following folder build/tmp/deploy/images/bbb/ > + > +Flash the BeagleBone Black image into SDcard > +``` > +host$ dd if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \ > + of=/dev/<medium-device> bs=1M status=progress > +``` > + > +After flashing the BBB image into SD card, mount the SD card on host PC and copy .swu file directly to root partition like below. This is missing a step: Build a different image configuration, e.g. switching to the RT kernel. Otherwise, you are now suggesting to flash the same SWU on the disk as you write as full image, and we know that this is broken (plus we have no error detection for that yet). Jan > + > +``` > +host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu /<mnt>/home/root/ > +``` > + > +Connect a serial port cable between host PC and BBB. > +Insert SD card to BBB, hold S2 button while applying power supply to BBB. > + > +For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification).
Hi Jan, > This is missing a step: Build a different image configuration, e.g. > switching to the RT kernel. Otherwise, you are now suggesting to flash the same SWU on the disk as you write as > full image, and we know that this is broken (plus we have no error detection for that yet). I have mentioned a reference section "building-and-testing-the-cip-core-image" in the readme for BBB, which means we have to create two images (Non-RT and RT) as per the section. I will clearly mention in BBB section to create two images. Thanks & Regards Shivanand K -----Original Message----- From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Jan Kiszka Sent: Tuesday, September 20, 2022 3:46 PM To: kunijadar shivanand(ＴＳＩＰ TMIEC ODG Porting) <Shivanand.Kunijadar@toshiba-tsip.com>; cip-dev@lists.cip-project.org Cc: dinesh kumar(ＴＳＩＰ TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ) <kazuhiro3.hayashi@toshiba.co.jp> Subject: Re: [cip-dev] [isar-cip-core v2] README.swupdate.md: Add steps to verify SWUpdate on BBB On 16.09.22 13:43, Shivanand.Kunijadar@toshiba-tsip.com wrote: > From: Shivanand Kunijadar <Shivanand.Kunijadar@toshiba-tsip.com> > > Most of the steps are similar for both qemu-amd64 and BBB targets. > Add reference link wherever required instead of repeating steps. > > Signed-off-by: Shivanand Kunijadar > <Shivanand.Kunijadar@toshiba-tsip.com> > --- > doc/README.swupdate.md | 25 +++++++++++++++++++++++++ > 1 file changed, 25 insertions(+) > > diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md index > 1b242a2..9be3498 100644 > --- a/doc/README.swupdate.md > +++ b/doc/README.swupdate.md > @@ -32,6 +32,8 @@ Copy > `cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost: > ``` > > +## SWUpdate verification > + > Check which partition is booted, e.g. with lsblk: > ``` > root@demo:~# lsblk > @@ -215,3 +217,26 @@ user variables: > > > ``` > + > +# Building and testing the CIP Core image for BBB > + > +Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files. > +- Replace qemu-amd64.yml kas file with BBB board specific file i.e > +bbb.yml > +- .swu file will be generated in the following folder > +build/tmp/deploy/images/bbb/ > + > +Flash the BeagleBone Black image into SDcard ``` host$ dd > +if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \ > + of=/dev/<medium-device> bs=1M status=progress ``` > + > +After flashing the BBB image into SD card, mount the SD card on host PC and copy .swu file directly to root partition like below. This is missing a step: Build a different image configuration, e.g. switching to the RT kernel. Otherwise, you are now suggesting to flash the same SWU on the disk as you write as full image, and we know that this is broken (plus we have no error detection for that yet). Jan > + > +``` > +host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu > +/<mnt>/home/root/ ``` > + > +Connect a serial port cable between host PC and BBB. > +Insert SD card to BBB, hold S2 button while applying power supply to BBB. > + > +For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification). -- Siemens AG, Technology Competence Center Embedded Linux
diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md index 1b242a2..9be3498 100644 --- a/doc/README.swupdate.md +++ b/doc/README.swupdate.md @@ -32,6 +32,8 @@ Copy `cip-core-image-cip-core-bullseye-qemu-amd64.swu` file from `tmp` folder in host$ scp -P 22222 /tmp/cip-core-image-cip-core-bullseye-qemu-amd64.swu root@localhost: ``` +## SWUpdate verification + Check which partition is booted, e.g. with lsblk: ``` root@demo:~# lsblk @@ -215,3 +217,26 @@ user variables: ``` + +# Building and testing the CIP Core image for BBB + +Follow the steps mentioned in the section [Building and testing the CIP Core image](README.swupdate.md#building-and-testing-the-cip-core-image) for creating images and .swu files. +- Replace qemu-amd64.yml kas file with BBB board specific file i.e bbb.yml +- .swu file will be generated in the following folder build/tmp/deploy/images/bbb/ + +Flash the BeagleBone Black image into SDcard +``` +host$ dd if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-bullseye-bbb.wic \ + of=/dev/<medium-device> bs=1M status=progress +``` + +After flashing the BBB image into SD card, mount the SD card on host PC and copy .swu file directly to root partition like below. + +``` +host$ sudo cp tmp/cip-core-image-cip-core-bullseye-bbb.swu /<mnt>/home/root/ +``` + +Connect a serial port cable between host PC and BBB. +Insert SD card to BBB, hold S2 button while applying power supply to BBB. + +For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification).