-
Notifications
You must be signed in to change notification settings - Fork 16
U-boot loader hangs with a solid blue light #8
Comments
We still need some fine tuning. The boot loader expects the
|
Ok, thanks :) |
If you are only interested in running plain Docker on the C2 you may check my automated setup. |
I have the same issue. @umiddelb I could not make much sense of the automated setup, how can I use those scripts to get docker on C2? Are those intended to be executed on a odrobian distro? Which one should I run first? Thanks |
In the meantime we have ordered some C2 to have a faster feedback loop making this work. |
To use these scripts you need to have you C2 up and running with ubuntu / debian / whatever. If you run
Now you have your plain Debian boot media for your C2. |
I tried to follow those steps @umiddelb but I think I missed something that maybe between the lines there. I started with a fresh odroibian install, I've cloned the repo and ran the I'm sure I did not followed the instructions, seems that I missed some steps that should seem trivial to a more experienced user like yourself. Anything missing here? Thanks |
hm, you shouldn't try to overwrite the media you've booted from (mkfs refuses to create filesystems on partitions currently in use). You can attach an USB card reader to your C2 or build the rootfs on uSD while having booted from eMMC (and vice versa). In case you have booted from eMMC (/dev/mmcblk0), you can initialize/erase your uSD(/dev/mmcblk1) prior to execute
|
Maybe this is more of an issue with the build.sh script since U-boot should boot from a single ext4 partition. Just curious if anyone has actually run the script, loaded the image on SD and tried to boot it without making any modifications to boot.ini. I am starting to look in to this closer since I have tried the release image (does not boot) along with making a fresh image from the source per the instructions, same result When running the tests, the results are as follows: SD card image Root filesystem |
Of course u-boot is able to load the kernel image, etc. from an ext4 partition, but the I've talked to @DieterReuter and we agreed on re-introducing a small vfat partition where the boot.ini is to be stored, the kernel image, dtb, etc. will remain on the ext4 partition. |
Thanks. When will the build.sh script be adjusted to include the vfat partition for storing boot.ini so the generated image for C2 can be booted without having to manually address? |
ping @StefanScherer ? btw. there are no Aarch64 Debian packages on https://packagecloud.io/Hypriot/Schatzkiste at this time. |
Since the C2 image is not functional without manual intervention, the best option recommended would be go for another distro and just use the other scripts to layer on docker and so forth? |
@DarkBlaez It's our second shot of a SD card image for C2 and we still do not have C2 boards in our labs. Will be shipped next week. I also agree that we should add a vfat partition, it is also needed for the @umiddelb And yes we also have to prepare a docker deb for aarch64. |
@StefanScherer so if we end up with a leading FAT partition anyway, that would be interesting. The C2's SD card "slot" is badly accessible so I was thinking about putting the image on USB and just having the early boot stuff on SD. Please keep us posted with your experiences once you got the toys ;-) |
You only need the leading FAT partition if you stick to the cfgload/boot.ini mechanism (HK's u-boot version for the C2 is unable to read the boot.ini file from ext2/ext4 filesystems) . If you use the u-boot environment directly (instead of boot.ini) you can omit this partition. |
Like the Ubuntu Partition table as in http://odroid.com/dokuwiki/doku.php?id=en:c2_partition_table ? |
Like the proposed table, but only for the boot.ini file. |
@umiddelb Thanks for #8 (comment) now as we have some devices I understand :-) Changing the boot.ini to ext4 for now as a small next step. |
The U-boot loader hangs with a solid blue light, image created with:
flash -n minion9 https://github.com/hypriot/image-builder-odroid-c2/releases/download/v0.0.4/sd-card-odroid-c2-v0.0.4.img.zip
The text was updated successfully, but these errors were encountered: