Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

IOT2050 does not boot

Created by: Luke_de_Munk at: 6/24/2021 10:34 AM (1 Replies)

Rating (0)

Thanks 1

2 Entries

6/24/2021 10:34 AM	Rate (0)
Luke_de_Munk Posts: 2 Rating: (0)	Hi, I am stuck at boot too. Siemens OS was preloaded, but I wanted to install the example image. While I was copying the .img from an sdcard to eMMc, the IOT2050 was stuck at some point. I turned the IOT2050 off and now it won't boot. With the micro SD inserted, the uart debug says: uuid conflict: 88c13384-a6c4-4c29-93da-0b25e8de2e06 Without micro SD, the following output is given: 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@[1065 1140 1140] ======================= Board: IOT2050-ADVANCED Serial: N4C18963 MLFB: 6ES7647-0BA00-1YA2 UUID: 9987F12D39BB47CEB75034ED0C95896C A5E: A5E452229880AA05 MAC[0]: 8c-f3-19-16-99-c8 MAC[1]: 8c-f3-19-16-99-c9 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.3.0-2)) #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@04FA0000 - probe failed: -123 sdhci@4f80000: 1 Loading Environment from SPI Flash... SF: Detected w25q128 with page size 256 Bytes, 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 no mmc device at slot 0 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 check end ====== switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Failed to iterate over directory extlinux Failed to iterate over directory boot.scr.uimg Failed to iterate over directory boot.scr no mmc device at slot 0 Device 0: unknown device Device 1: unknown device Device 2: unknown device When I want to boot from an USB stick, it won't work. The IOT2050 won't recognize the USB. I tried everything here and I can't come up with something else I can try right now. Can someone help me out? Thanks in advance! ------------------------------------------------------------------------------------------ Split from IOT2050 does not boot anymore.
Luke_de_Munk Posts: 2 Rating: (0)	Last edited by: Jen_Moderator at: 06/24/2021 12:18:39 New subject after splitting
Suggestion To thank Quote Answer

6/25/2021 5:01 PM	Rate (0)
Luke_de_Munk Posts: 2 Rating: (0)	I found out that the USB stick I used was not recognized by the bootloader. The USB works fine, even with the freshly installed Example image.
Luke_de_Munk Posts: 2 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Jen_Moderator

|

Share this page:

Share this page on...

Follow us on