(→Wrapping uboot as "kernel": new section) |
|||
| Line 3: | Line 3: | ||
I have mostly questions and only a few answers. | I have mostly questions and only a few answers. | ||
Fedora 25 includes the dtb for this model: rk3288-veyron-speedy.dtb | * Fedora 25 includes the dtb for this model: rk3288-veyron-speedy.dtb | ||
* As best I can tell from my research, the boot system on this chrome book is called "Depthcharge". | |||
If I wrap uImage or vmlinuz-4.. with | If I wrap uImage or vmlinuz-4.. with | ||
| Line 16: | Line 17: | ||
Holding down the power button resets the chromebook after a boot attempt hangs. | Holding down the power button resets the chromebook after a boot attempt hangs. | ||
Apparently, it reads the kernel packed by vbutil_kernel --pack, verifies the signature, and transfers control to the kernel. The bootloader doesn't seem to be used - it seems to be all zero on the factory boot partitions. I don't know what the fedora kernel is missing - there is no output at all. | |||
== Wrapping uboot as "kernel" == | == Wrapping uboot as "kernel" == | ||
This page mentions wrapping uboot as a kernel so that the chrome book will boot like a raspberry pi. Where does one get uboot to wrap? | This page mentions wrapping uboot as a kernel so that the chrome book will boot like a raspberry pi. Where does one get uboot to wrap? | ||
Revision as of 02:27, 28 February 2017
ASUS C201PA ARM Chromebook
I have mostly questions and only a few answers.
- Fedora 25 includes the dtb for this model: rk3288-veyron-speedy.dtb
- As best I can tell from my research, the boot system on this chrome book is called "Depthcharge".
If I wrap uImage or vmlinuz-4.. with
vbutil_kernel --pack fedora.blob --keyblock fedora.keyblock --signprivate fedora.vbprivk \ --version 4 --vmlinuz vmlinuz-4.8.6* --config kcmdline --bootloader=dummy.boot --arch arm
then Booting in developer mode with Ctrl-U gets a blank screen and hangs - with just zero in part 1 and 2, it says it can't find a kernel. So the firmware is loading the image.
How does initrd get loaded? Doesn't uImage already incorporate the itb (compiled from its) and include all the platforms in the dtb-* directory?
Holding down the power button resets the chromebook after a boot attempt hangs.
Apparently, it reads the kernel packed by vbutil_kernel --pack, verifies the signature, and transfers control to the kernel. The bootloader doesn't seem to be used - it seems to be all zero on the factory boot partitions. I don't know what the fedora kernel is missing - there is no output at all.
Wrapping uboot as "kernel"
This page mentions wrapping uboot as a kernel so that the chrome book will boot like a raspberry pi. Where does one get uboot to wrap?