6/28/2023 5:49 PM | |
Joined: 10/18/2021 Last visit: 10/9/2024 Posts: 1 Rating: (0) |
I would like to update from V1.1.1 to 1.3.1 on iot2050 advanced fs:01. Using V1.1.1 I have performed the firmware update to (Version 1.3, 04/2023) as described in the guide. I have cleared the eMMC beforehand and boot order chosen was as suggested with mmc0 first. But with both V1.1.1 or V1.3.1 on the SD card I now get a red stat led on boot attempts and device is not accessible on the network. So it seems I have already bricked a few iot2050 advanced fs:01 this way with the firmware update... I should mention that using the Displayport cable to DVI on a monitor never worked on any of those devices unfortunately so I don't really see whats going on. (but same cable does work on an ET200sp OpenController) Any suggestions what could be useful next steps? Document "IOT2050 Setting Up with Example Image Version 1.2.1, 03/2023" does mention to connect via UART on X14 but does not give specifics on the pinout of X14. Anyone can help? What would be ways to diagnose whats going on using the UART? Another question is what Debian version V1.3.1 is based on? Would that be Debian "Bookworm"? (Just trying to understand if rescuing the bricked IOT2050s would be worth it at all. ------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 06/29/2023 08:14:58New subject after splitting |
|
7/5/2023 8:55 AM | |
Joined: 4/28/2015 Last visit: 11/5/2024 Posts: 3345 Rating: (379)
|
Hi, what commands did you use to update the firmware? With the UART cable you can see what it going on and where the boot is stuck. The pinout of the UART pin can be found in the manual. Best regards! |
Not working for IOT2050 support anymore from March 1st, 2024. |
|
Follow us on