Fix odroidc1 #1932
Fix odroidc1 #1932
Conversation
remove EOS enable current and dev config meson-current: update config meson-dev: update config Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
without uImage the board will not boot take the already used hack (?) from general-kernel-odroidn2-current.patch since KERNEL_IMAGE_TYPE does not work as expected Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
with default loading locations in u-boot the uImage can be too large and will be partly overwritten with the loaded dtb leading to boot failues due to wrong checksum Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
|
Doesn't want to boot for me. First it was corrupted kernel image, then corrupted ramdisk, changed SD cards, environment ... huh? |
|
I used
Maybe there is some issue there ? and then I select the full image dev Kernel and odroidc1 in the menu for example bootlog of one of such image is at notice: Ubuntu 20.x , 5.6.8 and loglevel 7 there indicating that the patches are working (environment is taken from a changed loglevel 3-> logleve 7 boot.ini) - uImage size is below "critical" ~8MB because memory locations |
|
cleaned docker and did a new build again (full image, dev Kernel, buster) and this is booting on my end too |
|
Images made via our automated build are working - a problem with my build host. It seems that we can also enable HDMI once? Perhaps its coming with 5.7-> I would rather leave this config as .CSC until we don't have HDMI. Non working HDMI is a bummer for average Joe which questions we try to avoid this way. |
One can choose what to build, while build targets are defined elsewhere
Cause of changes in boot.ini we don't need to worry about size. After few tests, no problems sighted. Tested running Docker.
|
Added few improvements, tested few times. |
|
!build |
|
How stable is this build for you? I am getting filesystem / sd card errors after some time ... |
|
As reported in #1960 my Odroid C1 cannot boot with the current images. I am burning the images using the latest version of balena Etcher. Any thoughts? |
|
I tried a boot with the bionic-server as of 16.05.2020, that worked. Bionic-server Buster-server: |
There are days of suffering hidden behind ;) Yes. Its under control now and it will hopefully stay this way. One day also HDMI will be added. There are some experimental builds in the wild, but not really time to proceed on that right now. This board is old and we have very ... very little time. |
|
Thank you very much :)! This made the board useable for me, so I am a happy camper |
Currently odroid-c1 is broken and marked EOS
each patch should have a sufficient description
and is signed off
I separated some functional changes if those are not wanted
Creating a bootable image makes testing the ongoing changes for S805 easier
This patch series:
Issue for example reported: https://forum.armbian.com/topic/12260-odroidc1-ubuntu-images-from-master-do-not-boot/
I tested several minimal images with 5.4.x and 5.6.x Kernels and all of boot to userspace*
i didnt test Desktop because currently I only have a "bad" micro-sdxc [1] that currently limits test capability, using a usb rootfs with these changes seems to work tho (but that doubles flashing/testing time)
[1] https://wiki.odroid.com/odroid-c1/troubleshooting/microsd_selection