Message ID | 20220909132535.3671-1-Shivanand.Kunijadar@toshiba-tsip.com (mailing list archive) |
---|---|
State | Handled Elsewhere |
Headers | show |
Series | [isar-cip-core] README.swupdate.md: Add steps to verify SWUpdate on BBB | expand |
On 09.09.22 15:25, 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 | 52 ++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 52 insertions(+) > > diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md > index 1b242a2..72690d6 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,53 @@ 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 > +``` > + > +Prepare the hardware connections > + > +- Connect a serial port cable between host PC and BBB > +- Connect an Ethernet cable between host PC and BBB > + > +Insert SD card to BBB, hold S2 button while applying power suppy to BBB. typo: supply > +Once the system is up, execute below command to configure static IP address to BBB > + > +``` > +root@demo:~# cat <<EOF >> /etc/network/interfaces > +auto eth0 > +iface eth0 inet static > + address 192.168.2.2 > + netmask 255.255.255.0 > + network 192.168.2.0 > + broadcast 192.168.2.255 > +EOF > +root@demo:~# /etc/init.d/networking restart > +``` > + > +In host PC, configure below settings for Ethernet IPv4. > + > +- IP address: 192.168.2.1 > +- Subnet mask: 255.255.255.0 > + > +Execute below command to confirm 192.168.2.1 is accessible from BBB. > +``` > +root@demo:~# ping 192.168.2.1 > +``` > + > +Copy .swu file from `tmp` folder to BBB from host PC using below command. > + > +``` > +host$ scp tmp/cip-core-image-cip-core-bullseye-bbb.swu root@192.168.2.2:/root/ > +``` > + > +For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification). How I tested (in the absence of a test network at that time): - mount the flashed SD-card on the host - cp the DIFFERENT swu into <mnt>/root/ - boot the target and run swupdate -i /root/<image>.swu I think that is simpler if there is no common network with dhcp in reach. Jan
Hello Jan, Thank you for the suggestion. I think the approach you mentioned is more developer friendly compared to mine. however, I would like keep both, let user select the preferable option. Is it ok? 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: Friday, September 9, 2022 11:11 PM To: kunijadar shivanand(TSIP TMIEC ODG Porting) <Shivanand.Kunijadar@toshiba-tsip.com>; cip-dev@lists.cip-project.org Cc: dinesh kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 □SWC◯ACT) <kazuhiro3.hayashi@toshiba.co.jp> Subject: Re: [cip-dev] [isar-cip-core] README.swupdate.md: Add steps to verify SWUpdate on BBB On 09.09.22 15:25, 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 | 52 > ++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 52 insertions(+) > > diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md index > 1b242a2..72690d6 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,53 @@ 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 ``` > + > +Prepare the hardware connections > + > +- Connect a serial port cable between host PC and BBB > +- Connect an Ethernet cable between host PC and BBB > + > +Insert SD card to BBB, hold S2 button while applying power suppy to BBB. typo: supply > +Once the system is up, execute below command to configure static IP > +address to BBB > + > +``` > +root@demo:~# cat <<EOF >> /etc/network/interfaces auto eth0 iface > +eth0 inet static > + address 192.168.2.2 > + netmask 255.255.255.0 > + network 192.168.2.0 > + broadcast 192.168.2.255 > +EOF > +root@demo:~# /etc/init.d/networking restart ``` > + > +In host PC, configure below settings for Ethernet IPv4. > + > +- IP address: 192.168.2.1 > +- Subnet mask: 255.255.255.0 > + > +Execute below command to confirm 192.168.2.1 is accessible from BBB. > +``` > +root@demo:~# ping 192.168.2.1 > +``` > + > +Copy .swu file from `tmp` folder to BBB from host PC using below command. > + > +``` > +host$ scp tmp/cip-core-image-cip-core-bullseye-bbb.swu > +root@192.168.2.2:/root/ ``` > + > +For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification). How I tested (in the absence of a test network at that time): - mount the flashed SD-card on the host - cp the DIFFERENT swu into <mnt>/root/ - boot the target and run swupdate -i /root/<image>.swu I think that is simpler if there is no common network with dhcp in reach. Jan -- Siemens AG, Technology Competence Center Embedded Linux
Hello Shiva-san, > > Hello Jan, > > Thank you for the suggestion. I think the approach you mentioned is more developer friendly compared to mine. > however, I would like keep both, let user select the preferable option. Is it ok? I think the document should be shorter & simpler and focus on SWUpdate testing. If the network settings step is just for "scp", it's better to replace it by another simple way. Best regards, Kazu > > 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: Friday, September 9, 2022 11:11 PM > To: kunijadar shivanand(TSIP TMIEC ODG Porting) <Shivanand.Kunijadar@toshiba-tsip.com>; > cip-dev@lists.cip-project.org > Cc: dinesh kumar(TSIP TMIEC ODG Porting) <dinesh.kumar@toshiba-tsip.com>; hayashi kazuhiro(林 和宏 □SW > C◯ACT) <kazuhiro3.hayashi@toshiba.co.jp> > Subject: Re: [cip-dev] [isar-cip-core] README.swupdate.md: Add steps to verify SWUpdate on BBB > > On 09.09.22 15:25, 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 | 52 > > ++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 52 insertions(+) > > > > diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md index > > 1b242a2..72690d6 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,53 @@ 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 ``` > > + > > +Prepare the hardware connections > > + > > +- Connect a serial port cable between host PC and BBB > > +- Connect an Ethernet cable between host PC and BBB > > + > > +Insert SD card to BBB, hold S2 button while applying power suppy to BBB. > > typo: supply > > > +Once the system is up, execute below command to configure static IP > > +address to BBB > > + > > +``` > > +root@demo:~# cat <<EOF >> /etc/network/interfaces auto eth0 iface > > +eth0 inet static > > + address 192.168.2.2 > > + netmask 255.255.255.0 > > + network 192.168.2.0 > > + broadcast 192.168.2.255 > > +EOF > > +root@demo:~# /etc/init.d/networking restart ``` > > + > > +In host PC, configure below settings for Ethernet IPv4. > > + > > +- IP address: 192.168.2.1 > > +- Subnet mask: 255.255.255.0 > > + > > +Execute below command to confirm 192.168.2.1 is accessible from BBB. > > +``` > > +root@demo:~# ping 192.168.2.1 > > +``` > > + > > +Copy .swu file from `tmp` folder to BBB from host PC using below command. > > + > > +``` > > +host$ scp tmp/cip-core-image-cip-core-bullseye-bbb.swu > > +root@192.168.2.2:/root/ ``` > > + > > +For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate > Verification](README.swupdate.md#swupdate-verification). > > How I tested (in the absence of a test network at that time): > - mount the flashed SD-card on the host > - cp the DIFFERENT swu into <mnt>/root/ > - boot the target and run swupdate -i /root/<image>.swu > > I think that is simpler if there is no common network with dhcp in reach. > > Jan > > -- > Siemens AG, Technology > Competence Center Embedded Linux
diff --git a/doc/README.swupdate.md b/doc/README.swupdate.md index 1b242a2..72690d6 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,53 @@ 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 +``` + +Prepare the hardware connections + +- Connect a serial port cable between host PC and BBB +- Connect an Ethernet cable between host PC and BBB + +Insert SD card to BBB, hold S2 button while applying power suppy to BBB. +Once the system is up, execute below command to configure static IP address to BBB + +``` +root@demo:~# cat <<EOF >> /etc/network/interfaces +auto eth0 +iface eth0 inet static + address 192.168.2.2 + netmask 255.255.255.0 + network 192.168.2.0 + broadcast 192.168.2.255 +EOF +root@demo:~# /etc/init.d/networking restart +``` + +In host PC, configure below settings for Ethernet IPv4. + +- IP address: 192.168.2.1 +- Subnet mask: 255.255.255.0 + +Execute below command to confirm 192.168.2.1 is accessible from BBB. +``` +root@demo:~# ping 192.168.2.1 +``` + +Copy .swu file from `tmp` folder to BBB from host PC using below command. + +``` +host$ scp tmp/cip-core-image-cip-core-bullseye-bbb.swu root@192.168.2.2:/root/ +``` + +For verifying swupdate on BBB use the same steps as mentioned in above [SWUpdate Verification](README.swupdate.md#swupdate-verification).