Mathijs wrote:I narrowed it down to the CONFIG_ANDROID option. Whenever that one is enabled, I get the colour screen. It's in Device Drivers -> Staging -> Android. Its suboptions don't matter.
Do you know what actually produces the colour screen?
Question: are you try to start a "standard" file system, e.g. Debian, rather than an Android one? If so what sort?
The colour screen is because the firmware was not able to load the kernel. I don't know the specifics, except that the boot process is kind of unusual (firmware gets loaded into GPU, then the CPU gets started later on).
Not sure if I understand your second question right. Do you mean ext4? I extracted the rootfs zip from the link to an ext4 partition. Make sure this is in cmdline.txt on your boot partition:
Code: Select all
root=/dev/mmcblk0p2 rootfstype=ext4 rootwait init=init
If your android partition is not the second partition on your sd card, then you need to alter the root=mmcblk0p2 of course. init=init makes sure the kernel finds the right init file, which is in the root of your android partition.
I haven't tried making my own Android root filesystem, because some changes are needed. Usually it generates a boot.img, system.img, userdata.img, etc. but we'd rather have it all on one to make things easier. This file
contains a device tree that apparently generates a root filesystem for a device (the Mini6410) that looks rather similar regarding the SoC.