7/6/2021 6:30 PM | |
Joined: 4/28/2015 Last visit: 6/28/2024 Posts: 578 Rating: (43) |
There is a suspicious discrepancy between the number of sectors I've written ("install-on-emmc.sh[176]: Writing 4368884 sectors to eMMC /dev/mmcblk1...") and those you transfererd ("install-on-emmc.sh[183]: Writing 4368592 sectors to eMMC /dev/mmcblk1..."). Were you using the RT images from https://github.com/siemens/meta-iot2050/actions/runs/976344173#artifacts again, as you've done before (which is why I also did that)? The error you see is the same as without my patch ("partx: specified range <1:0> does not make sense"), and that prevents creating a unique UUID for the clone on the eMMC, causing all kinds of problems later on. The root cause may also be that not everything was written consistently. No idea yet what could cause that, though. |
7/8/2021 7:26 PM | |
Joined: 4/28/2015 Last visit: 6/28/2024 Posts: 578 Rating: (43) |
I would rather say download that RT image from https://github.com/siemens/meta-iot2050/suites/3096527972/artifacts/70763534, then we are on the exact same page. |
7/9/2021 7:20 PM | |
Posts: 20 Rating: (0) |
Is this because of some existing content on the eMMC, is there a way to like completely wipe it clean? |
7/12/2021 3:24 PM | |
Joined: 4/28/2015 Last visit: 6/28/2024 Posts: 578 Rating: (43) |
I've just pushed another try to resolve the issue to https://github.com/siemens/meta-iot2050/commits/jan/fix-emmc-install. It assumes that we see a race between partx triggering a rescan of the partitions and /dev/mmcblk1p1 actually popping up. It tries to plug that by waiting for udevd to finish as well as polling for the device node to show up. |
7/12/2021 3:29 PM | |
Posts: 20 Rating: (0) |
Cool, I will pull your changes, build the OS and then try installing it, will let you know what happens. |
Follow us on