On 15 June 2015 at 15:52, Haojian Zhuang haojian.zhuang@linaro.org wrote: [...]
Hi all,
I implemented the multiple boot entries in this driver. https://github.com/hzhuang1/edk2/blob/bootentry/HisiPkg/HiKeyPkg/Drivers/HiK...
This driver create multiple boot entries successfully. At here, you'll get the "fastboot" and "debian on emmc" entries. It's based on whether "BootNext" is created. If "BootNext" variable is created by the driver, BDS won't create default boot entry by PCD values.
At last, the whole scenarios are in below.
- After flushing the initial images in factory. System would try to
load debian from eMMC directly if pin 5-6 isn't connected in J15 on HiKey board. Or system would try to run fastboot directly if pin 5-6 is connected in J15.
- User select whether boot debian or android. Or boot from emmc or sd.
(Use additional oem command in fastboot protocol.) $fastboot oem bootorder {index number} 0 -- fastboot 1 -- debian on emmc 2 -- debian on sd 3 -- android on emmc 4 -- android on sd 5 -- openembed on emmc 6 -- openembed on sd
When the boot order is specified, UEFI will always try the selected boot order.
- User select whether uart0 or uart2 is the serial console.
$fastboot oem serialconsole {console string} console string could be either "uart0" or "uart2". It'll only change the serial console of linux kernel. And it won't change the serial console in ATF or UEFI. By default, uart0 is the default serial console of linux kernel.
Do you have any opinion on these scenarios? If not, I'll continue on enabling these scenarios. Since we don't have serial port on hikey board, we have to create these scenarios to make it work.
Hello Haojian,
I am a bit lost here: how do these changes have anything to do with the original problem that started this thread? You were asking about how to load the FDT and initrd when booting in true UEFI mode (PcdDefaultBootType == 0) How did you address that issue?