Hey Siemens,


Below is a copy from my Git Issue: https://github.com/siemens/meta-iot2050/issues/624
Feel free to answer via my git issue or here, whatever you prefer.

Would appreciate the help :)

----- 

I hope that you will be able to help me as I believe I am rather close, but do not know what the problem might be. I am using the below device:

Board: IOT2050-ADVANCED
SIMATIC IOT2050 SE-Boot Version: V01.04.01-0-g629b172b-0x0000
BuildDate: 20240103
SYSFW ABI: 3.1 [version: 21] [21.9.1--v2021.09a (Terrific Lla]

I am trying to build an swupdate image that I want to setup on the emmc of the IOT2050 device. I followed the instructions within this repo and used .kas to build with the following commands. I only added my own opt to remove unwanted software from the eventual image.

My Setup for building the image:

I have added one .yaml file here kas/opt/docker.yml with the name of the project containing the following:

header:
  version: 14

local_conf_header:
  minimal: |
    IOT2050_NODE_RED_SUPPORT = "0"
    IMAGE_INSTALL:remove = "tcf-agent"
    IOT2050_DEBIAN_DEBUG_PACKAGES:remove = "mosquitto mosquitto-clients"

I then run the following command:  ./kas-container build kas-iot2050-swupdate.yml:./kas/opt/dgam-pr.yml

The image builds and I get the expected .wic image. I boot from SD card OS into Linux and inset a USB stick into the IOT2050, mount it and use dd to copy the .WIC file to the EMMC. I remove the USB and powercycle/reset the device so it reboots.

I then see the following happening via my UART connection:

SIMATIC IOT2050 SE-Boot Version: V01.04.01-0-g629b172b-0x0000

BuildDate: 20240103

SYSFW ABI: 3.1 [version: 21] [21.9.1--v2021.09a (Terrific Lla]

=======================

Board: IOT2050-ADVANCED

Serial: <OBFUSCATED>

MLFB: 6ES7647-0BA00-1YA2

UUID: 2053************E7C0

A5E: A5E452229880AB08

MAC[0]: 8c-f3-19-5f-xx-xx

MAC[1]: 8c-f3-19-5f-xx-xx

DDR: 2048MB

SKU: SE

Loading PK... ok

PK count: 00

PK version: 00

SV: 00-00

Security ID: 0x********-0x********

Security policy: none

No options found, skip.

Validating FIT... 

Loading image atf... 

Loading image tee... 

Loading image spl... 

Loading image fdt-0... 

NOTICE:  BL31: lts-v2.8.10(release):
NOTICE:  BL31: Built : 01:00:00, Jan  1 1970
I/TC: 
I/TC: OP-TEE version: 4.0.0 (gcc version 12.2.0 (Debian 12.2.0-14)) #1 Thu Jan  1 01:00:00 UTC 1970 aarch64
I/TC: Primary CPU initializing
I/TC: SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.1--v2021.09a (Terrific Lla')
I/TC: Secure Board Configuration Software: Rev 0
I/TC: Secure Boot Keys: Count 2, Rev 1
I/TC: Activated SA2UL device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2023.10-V01.05.01-0-g605c620 (Jan 01 1970 - 01:00:00 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.9.1--v2021.09a (Terrific Lla')
Trying to boot from SPI


U-Boot 2023.10-V01.05.01-0-g605c620 (Jan 01 1970 - 01:00:00 +0000)

Model: SIMATIC IOT2050 Advanced
DRAM:  2 GiB
Core:  176 devices, 32 uclasses, devicetree: separate
WDT:   Not starting watchdog@40610000
MMC:   mmc@4f80000: 1, mmc@4fa0000: 0
Loading Environment from SPIFlash... SF: Detected w25q128 with page size 256 Bytes, erase size 64 KiB, total 16 MiB
OK
In:    serial@2810000
Out:   serial@2810000
Err:   serial@2810000
Net:   No ethernet found.
Hit SPACE to stop autoboot in 2 seconds...
WDT:   Started watchdog@40610000 without servicing  (0s timeout)
Watchdog started, timeout 60000 ms
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
�7�[r�[999;999H�[6n�8MMC: no card present
BootOrder not defined
EFI boot manager: Cannot load any image
Found EFI removable media binary efi/boot/bootaa64.efi
54088 bytes read in 37 ms (1.4 MiB/s)
Booting /efi\boot\bootaa64.efi

�[2J�[1;1H�[0;36;40mEFI Boot Guard v0.19

�[0;37;40m�[0;37;40mBoot medium: VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Path(131,29,0x01000000831D0800)/Path(131,29,0x0000000084013000)

�[0;37;40m�[0;37;40mFound 3 handles for file IO



�[0;37;40m�[0;37;40mVolume 0: �[0;37;40m�[0;37;40m(On boot medium) �[0;37;40m�[0;37;40mVenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Path(131,29,0x01000000831D0800)/Path(131,29,0x0000000084013000)/HD(1,MBR,0xD82C07CE), LABEL=, CLABEL=(null)

�[0;37;40m�[0;37;40mVolume 1: �[0;37;40m�[0;37;40m(On boot medium) �[0;37;40m�[0;37;40mVenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Path(131,29,0x01000000831D0800)/Path(131,29,0x0000000084013000)/HD(2,MBR,0xD82C07CE), LABEL=, CLABEL=BOOT0

�[0;37;40m�[0;37;40mVolume 2: �[0;37;40m�[0;37;40m(On boot medium) �[0;37;40m�[0;37;40mVenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Path(131,29,0x01000000831D0800)/Path(131,29,0x0000000084013000)/HD(3,MBR,0xD82C07CE), LABEL=, CLABEL=BOOT1

�[0;37;40m�[0;37;40mLoading configuration...

�[0;37;40m�[0;37;40mConfig file found on volume 1.

�[0;37;40m�[0;37;40mConfig file found on volume 2.

�[0;37;40m�[0;37;40mBooting with environments from boot medium only.

�[0;37;40m�[0;37;40m2 config partitions detected.

�[0;37;40m�[0;37;40mConfig Revision: 2:

�[0;37;40m�[0;37;40m ustate: 0

�[0;37;40m�[0;37;40m kernel: C:BOOT0:linux.efi

�[0;37;40m�[0;37;40m args: 

�[0;37;40m�[0;37;40m timeout: 0 seconds

�[0;37;40m�[0;37;40mFull path for kernel is: VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/VenHw(E61D73B9-A384-4ACC-AEAB-82E828F3628B)/Path(131,29,0x01000000831D0800)/Path(131,29,0x0000000084013000)/HD(2,MBR,0xD82C07CE)/linux.efi

�[0;37;40m�[1;31;40mERROR: �[0;37;40m�[0;37;40mCannot set bootloader interface variables (Not Found).

�[0;37;40m## Application failed, r = 14
EFI LOAD FAILED: continuing...
Scanning mmc 1:2...
BootOrder not defined
EFI boot manager: Cannot load any image
Scanning mmc 1:3...
BootOrder not defined
EFI boot manager: Cannot load any image
MMC: no card present
starting USB...
Bus usb@10000: Register 2001040 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@10000: Register 2001040 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@10000 for devices... 3 USB Device(s) found
scanning bus usb@10000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device

Device 1: unknown device

Device 2: unknown device
IOT2050>

Most important parts:

�Cannot set bootloader interface variables (Not Found).
## Application failed, r = 14

On the IOT2050 via UBOOT CLI the partition looks fine:

1. part list mmc 1:

Partition Map for MMC device 1 -- Partition Type: EFI

Part Start LBA End LBA Name
Attributes
Type GUID
Partition GUID
1 0x00000800 0x000087ff "efi"
attrs: 0x0000000000000004
type: c12a7328-f81f-11d2-ba4b-00a0c93ec93b
guid: c19e7e9f-bacf-49a6-b43d-2fc18d2a8d03
2 0x00008800 0x000287ff "BOOT0"
attrs: 0x0000000000000000
type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
guid: e8567692-2dfa-459a-be15-f6e5ddcc8f49
3 0x00028800 0x000487ff "BOOT1"
attrs: 0x0000000000000000
type: ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
guid: 94b2174d-c792-4e8e-8a34-b506e2927937
4 0x00048800 0x008487ff "primary"
attrs: 0x0000000000000000
type: 0fc63daf-8483-4772-8e79-3d69d8477de4
guid: fedcba98-7654-3210-cafe-5e0710000001
5 0x00848800 0x010487ff "primary"
attrs: 0x0000000000000000
type: 0fc63daf-8483-4772-8e79-3d69d8477de4
guid: fedcba98-7654-3210-cafe-5e0710000002
6 0x01048800 0x011954cb "var"
attrs: 0x0000000000000000
type: 0fc63daf-8483-4772-8e79-3d69d8477de4
guid: 109ad769-43cf-468a-a729-333dc1b3221b
7 0x01195800 0x012e24cb "home"
attrs: 0x0000000000000000
type: 0fc63daf-8483-4772-8e79-3d69d8477de4
guid: 590ee186-ce56-4f36-9b11-182866569159

I can even Boot into the OS if I tell the bootloader what to load manually:

1. load mmc 0:2 ${kernel_addr_r} linux.efi
2. bootefi ${kernel_addr_r}{fdtcontroladdr}
3. OS Boots and I get to the part to change the default password

If I inspect the image on my machine where I build the swupdate image by doing the following:|

1. sudo losetup -fP ./build/tmp/deploy/images/iot2050/iot2050-image-swu-example-iot2050-debian-iot2050.wic
2. sudo mkdir /mnt/myimage
3. lsblk:
   NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
   loop0 7:0 0 9.4G 0 loop
   ├─loop0p1 259:0 0 16M 0 part /mnt/myimage
   ├─loop0p2 259:1 0 64M 0 part
   ├─loop0p3 259:2 0 64M 0 part
   ├─loop0p4 259:3 0 4G 0 part
   ├─loop0p5 259:4 0 4G 0 part
   ├─loop0p6 259:5 0 665.6M 0 part
   └─loop0p7 259:6 0 665.6M 0 part
4. sudo mount /dev/loop0p1 /mnt/yourimage

• ls -lh /mnt/myimage/EFI/BOOT/bootaa64.efi shows bootaa64.efi: -rwxr-xr-x. 1 root root 53K Jan  1  2098 /mnt/myimage/EFI/BOOT/bootaa64.efi

1. sudo mount /dev/loop0p2 /mnt/yourimage

• ls -lh /mnt/myimage/ reveils:
• -rwxr-xr-x. 1 root root 130K Jan 1 2098 BGENV.DAT
  -rwxr-xr-x. 1 root root 10 Jan 1 2098 EFILABEL
  -rwxr-xr-x. 1 root root 28M Jan 1 2098 linux.efi

1. Same as for /dev/loop0p3 as for /dev/loop0p2 (as expected, those are the A/B partitions to swap from with .swu binaries

I cannot find a solution or find something in the documentation that might be able to help me in this case.

I would appreciate it if you would be able to help me or even setup contact with me. I am doing this for an organization that wants to use your IOT2050 devices and I am currently doing an MVP trying to see if we can use the swupdate option which we find very interesting as it allows us to update the OS safely in the field remotely via .swu file.

Thanks in advance!