6/26/2021 8:35 AM | |
Posts: 20 Rating: (0) |
Dear All, I have been facing issues when booting from the eMMC. Try 1 - created the example iot2050 image using the procedure outlined on the meta-iot2050 git repo - wrote this image to a USB stick using Win32DiskImager (?) - connected the UART debug pins to the usb serial port of my windows laptop - powered the IoT box up - when the STATUS LED started blinking orange I pressed the USER button for about 5 seconds and could see some messages indicating that the image is being written to the eMMC (the USER led was blinking fast (green) during the installation as expected) - Once the installation was done the device rebooted itself and tried to boot from the eMMC but fails with some GUID/GPT partition error messages. - the system eventually falls back to the USB and boot itself properly. Can someone please suggest what could be wrong in what I did, any help is much appreciated. The debug log is attached. Try 2: - mount the usb stick with the image on a linux machine and copy the image to the /home directory - load the IoT box with the USB again and copy the image from /home to mmc1 using the following command I see some errors towards the end of this command (again GPT errors) root@iot:~# dd if=/home/iot2050-image-example-iot2050-debian-iot2050.wic.img of=/dev/mmcblk1 bs=100M conv=fsync status=progress 2236886016 bytes (2.2 GB, 2.1 GiB) copied, 288 s, 7.8 MB/s 21+1 records in 21+1 records out 2236886016 bytes (2.2 GB, 2.1 GiB) copied, 291.811 s, 7.7 MB/s [ 494.547255] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 494.555577] GPT:4368917 != 31080447 [ 494.559083] GPT:Alternate GPT header not at the end of the disk. [ 494.565108] GPT:4368917 != 31080447 [ 494.568607] GPT: Use GNU Parted to correct GPT errors. [ 494.573803] mmcblk1: p1 Attachmentmmc_boot_issue.txt (378 Downloads) |
Last edited by: kapilbhudhia at: 06/26/2021 08:36:43Last edited by: kapilbhudhia at: 06/26/2021 18:30:14 |
|
6/27/2021 4:01 PM | |
Joined: 4/28/2015 Last visit: 4/21/2024 Posts: 578 Rating: (43) |
Thanks for reporting. Seems method 1 still has issues. Could you retry with the image produced here (will be available in an hour or so from now) and report back? |
6/28/2021 11:19 AM | |
Posts: 20 Rating: (0) |
ok sure, I will give this a shot and let you know the results. |
7/5/2021 2:47 PM | |
Joined: 4/28/2015 Last visit: 4/21/2024 Posts: 578 Rating: (43) |
Could you share the complete serial log, from the installation, across the reboot into the system installed on eMMC? This is what I got with the rt example image from CI:
After that, the system booted happily into the eMMC (no unplugging of the stick needed, eMMC is preferred when available). |
7/5/2021 3:57 PM | |
Posts: 20 Rating: (0) |
About not booting from eMMC directly I had used the sdcard at mmc0 - the boot configuration is such that on my box it prefers mmc0 over mmc1. I will try with the usb this time. [snip]
Attachmentbooting.txt (319 Downloads) |
Last edited by: kapilbhudhia at: 07/05/2021 17:03:30Last edited by: Jen_Moderator at: 07/06/2021 06:35:01Added information as txt. file. |
|
7/5/2021 5:52 PM | |
Posts: 20 Rating: (0) |
Another attempt: I formatted eMMC using mkfs.ext4 /dev/mmc1blk1 (in contrast to how you suggested above).Created a fresh sd card from the CI image and then booted from it - wrote the image to eMMC using the standard procedure), this time the system rebooted from the eMMC, faced the same GPT errors like before (the very beginning), I dont know what is going on - could there be a problem with the image I have built - but then the same image works fine from usb and mmc0. [snip]
Attachmentbooting2.txt (385 Downloads) |
Last edited by: Jen_Moderator at: 07/06/2021 06:37:15Added information as txt. file. |
|
7/6/2021 7:32 AM | |
Joined: 4/28/2015 Last visit: 4/21/2024 Posts: 578 Rating: (43) |
Like I wrote: I also need to log of the installation from the external medium to eMMC, as I also shared (as snippet). You provided that with your very first report as well. |
Follow us on