odroid-c2 integration - understand rpi 3b boot

asked 2018-08-06 20:39:50 -0500

Hello! I'm looking at attempting to help/join the community of developers that are integrating arm devices into the next release of fedora. I'd like to help get the Odroid C2 and Odroid XU4 devices working out of the box or with very little effort. My current focus/attempts have been on the C2; I'd like to emulate something similar to the raspberry pi 2/3 using EFI and grub2 to boot the kernel. I'm currently stuck trying to boot the standard 3.16 LTS odroid kernel using the EFI grub loader; I've built the kernel under Fedora 28 arch64 in a chroot on the odroid c2 device (under ubuntu). The kernel, initramfs and device tree, built fine. I've set them in what I believe were the proper locations and referenced the grub config to them although I couldn't get past the attempting to boot kernel screen after grub.

Is there a contact that I could reach out to that may be able to shed some light on what I may try? Or a wiki page somewhere that I may be missing which can offer me another angle of attack? I believe it should be something that indicates how the u-boot > EFI loader > grub EFI setup looks and possible ways to investigate non booting kernels?

This is how far I make it when booting from grubaarch64.efi; booting the current 4.17.11-200.aarch64 kernel

EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...

When booting the 3.16LTS version i just get

EFI stub: Booting Linux Kernel...

Im running "U-Boot 2018.03-R002-00003-ga2c996d154 (Jul 08 2018 - 20:54:28 -0400) odroid-c2" and I've configured it to be with the binary blob 'bl1.bin.hardkernel' from hardkernel.

Cheers,

Forward

edit retag flag offensive close merge delete