Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

IOT2050 does not boot anymore

Created by: marvinle at: 11/20/2020 7:24 PM (7 Replies)

Rating (0)

Thanks 0

8 Entries

11/20/2020 7:24 PM	Rate (0)
marvinle Posts: 4 Rating: (0)	Hello everyone! My IOT2050 does not boot anymore, the STAT LED is constantly red. I used the operating instruction manual and at first everything worked perfectly, I could connect to the IOT via Ethernet. When I wanted to reset the IOT and therefore flashed the micro-SD card again, the issue occured. Since then I tried flashing the micro-SD multiple times and also used different cards, nothing changed. When I connect an FTDI-cable, it appears that the IOT is stuck in the booting process. I use the IOT2050_Example_Image_V1.0.2 as OS and work on a Windows PC. I only have little experience with linux and there is no valuable data on the IOT, so a loss of data would not be a problem. Could you please help me? Best Regards! This is what the boot loader shows: ▒SIMATIC IOT2050 SE-Boot Version: D01.00.00.09-0-g9827cee9-0x0000 BuildDate: 20200317 SYSFW ABI: 2.9 [version: 19] [19.12.1-v2019.12a (Terrific Lla] AVS@[1100 1180 1180] ======================= Board: IOT2050-ADVANCED Serial: M8BF5406 MLFB: 6ES7647-0BA00-1YA2 UUID: B18A68CD12BC47308680FB5AD9537BCA A5E: A5E452229880AA04 MAC[0]: e0-dc-a0-d7-97-10 MAC[1]: e0-dc-a0-d7-97-11 Initlialzing DDR ...done. SKU: SE Loading PK... ok PK count: 00 PK version: 00 SV: 00-00 Security ID 0x5125e53f-0x842e215d Security policy: soft Loading image... Loading image... Loading image... Loading image... NOTICE: BL31: v2.1(release):v2.1-421-g996d37930-dirty NOTICE: BL31: Built : 20:04:56, Mar 18 2020 I/TC: I/TC: OP-TEE version: 3.6.0-16-ge260ea8d-dev (gcc version 8.3.0 (Debian 8) #1 Wed Mar 18 20:08:49 UTC 2020 aarch64 I/TC: Initialized U-Boot SPL 2019.01-V01.00.00.2-0-g8e86139 (Mar 18 2020 - 20:04:56 +0000) Trying to boot from SPI Using 'conf-iot2050-advanced' configuration ## Verifying Hash Integrity ... sha256,rsa4096:custMpk+ OK ## Checking hash(es) for Image u-boot ... sha256+ OK ## Checking hash(es) for Image iot2050-advanced.dtb ... sha256+ OK U-Boot 2019.01-V01.00.00.2-0-g8e86139 (Mar 18 2020 - 20:04:56 +0000) Model: Siemens IOT2050 Advanced Base Board DRAM: 2 GiB MMC: sdhci@4f80000: 1, sdhci@04FA0000: 0 Loading Environment from SPI Flash... SF: Detected w25q128 with page sizetes, erase size 64 KiB, total 16 MiB OK In: serial Out: serial Err: serial Net: eth0: pruss0_eth Hit any key to stop autoboot: 0 ====== uuid conflict check begin ====== switch to partitions #0, OK mmc1(part 0) is current device switch to partitions #0, OK mmc0 is current device resetting USB... USB0: Register 2001040 NbrPorts 2 Starting the controller USB XHCI 1.10 USB1: Register 2001040 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 3 USB Device(s) found scanning bus 1 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 uuid conflict: 88c13384-a6c4-4c29-93da-0b25e8de2e06 ====== uuid conflict check end ======
marvinle Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

11/23/2020 9:34 AM	Rate (0)
jan-k Silver Member Joined: 4/28/2015 Last visit: 1/7/2026 Posts: 578 Rating: (43)	Remove the SD-card and let the eMMC boot up once. Normally, it will regenerate its partition UUIDs on first boot and, thus, resolve this duplication.

Suggestion To thank Quote Answer

11/23/2020 11:44 AM	Rate (0)
marvinle Posts: 4 Rating: (0)	Thank you for your answer! Unfortunately, after reinserting the SD-card (formatted and reflashed), the problem remains the same. Is there anything else I can do?
marvinle Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

11/23/2020 12:16 PM	Rate (0)
bergmanu Platinum Member Joined: 4/28/2015 Last visit: 4/24/2025 Posts: 3345 Rating: (382)	Hi, do you have something flashed on your eMMc? If not then the regeneration of the UUIDs does not take place, because it is not booting from anything. Best regards!
	Not working for IOT2050 support anymore from March 1st, 2024. I really enjoyed the time supporting you! :)
Suggestion To thank Quote Answer

11/23/2020 1:17 PM	Rate (0)
marvinle Posts: 4 Rating: (0)	Hi! No I don't. Is it possible to flash something onto the eMMc while the IOT is not booted, maybe via FTDI?
marvinle Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

11/23/2020 1:51 PM	Rate (0)
bergmanu Platinum Member Joined: 4/28/2015 Last visit: 4/24/2025 Posts: 3345 Rating: (382)	Hi, ah, you can also try to write the Example Image to an USB flash drive instead of using an SD card and boot from this one. Please remove the SD card while trying this. I hope the procedure jan-k described works with this as well. If booting from USB does also not work, we may have a problem.. Best regards!
	Last edited by: bergmanu at: 11/23/2020 13:54:45 Not working for IOT2050 support anymore from March 1st, 2024. I really enjoyed the time supporting you! :)
Suggestion To thank Quote Answer

11/24/2020 6:52 AM	Rate (0)
jan-k Silver Member Joined: 4/28/2015 Last visit: 1/7/2026 Posts: 578 Rating: (43)	If the eMMC should be actually blank, it would be extremely weird that a partition UUID conflict exists - between what? I suppose you only have one device? Then it might be simplest to build your own image from meta-iot2050. That will inherently get a new UUID, thus can't be in conflict with anything on the device anymore.

Suggestion To thank Quote Answer

12/10/2020 6:24 PM	Rate (0)
marvinle Posts: 4 Rating: (0)	Thank you guys for your effort! I tried booting via USB as described - the same result happened again. I sent the IOT back to Siemens, in order to repair or replace it, as I didn't think I could get it to work anymore. I hope my next try will deliver better results. Anyway, I appreciate this forum and thank you for your fast answers! Best regards!
marvinle Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on