Hi Geoff, Guodong,
On Sat, Jan 23, 2016 at 08:15:42AM +0800, Guodong Xu wrote:
On 23 January 2016 at 01:48, Geoff Levand geoff@infradead.org wrote:
On Fri, 2016-01-22 at 10:12 +0800, Guodong Xu wrote: So, now, let's take one step back: which version of ATF/UEFI are you
using on HiKey? as of now, we recommends official released UEFI,
downloadable here: https://builds.96boards.org/releases/hikey/linaro/binaries/15.11/
(please use ptable-linux-4g.img if your board comes with 4GB eMMC).
uefi_path="${builds_root}/ builds.96boards.org/releases/hikey/linaro/binaries/15.11" debian_path="${builds_root}/ builds.96boards.org/releases/hikey/linaro/debian/15.11"
boot_image="${debian_path}/boot-fat.uefi.img"
sudo fastboot flash ptable "${uefi_path}/ptable-linux-4g.img" sudo fastboot flash fastboot "${uefi_path}/fip.bin" sudo fastboot flash nvme "${uefi_path}/nvme.img" sudo fastboot flash boot ${boot_image}
For 15.11 release (with v3.18 kernel), these steps are correct. I confirm.
But Geoff, I am not clear what's the purpose you post these. It looks off the topic to me.
Can you now boot your v4.4 vanilla image on HiKey or you want clarity other things?
Remind one thing which just several days before I encountered. Now Hikey has moved Image and dtb files into rootfs but not in boot_image anymore. So if only burn boot_image, then definitely cannot boot up successfully.
If you want to boot your own images, you can manually add grub boot entry like below [1]:
menuentry 'Custom Kernel' { search.fs_label rootfs root search.fs_label boot esp linux ($esp)/Image console=tty0 console=ttyAMA3,115200 root=/dev/disk/by-partlabel/system rootwait rw efi=noruntime initrd ($esp)/initrd.img devicetree ($esp)/hi6220-hikey.dtb }
Not sure if this is your case, hope this info will be helpful.
[1] https://github.com/96boards/documentation/wiki/HiKeyUEFI
Thanks, Leo Yan