Hello Leif,
Thanks a lot for your detailed response.
Leif Lindholm wrote (ao):
On Sun, Dec 01, 2013 at 12:54:49PM +0100, Sander wrote:
It seems that imgbuild.sh destroys the GPT, resulting in kernel not found.
The issue is unfortunately somewhat more fundamental than that; the Samsung Arndale boot PLD contains code that reads whatever is at offset 512 from the start of SD card as its BL2 image.
This means that it is not possible* to use GPT partitioning with the original Samsung Arndale board.
*: Well, it is possible - if you install UEFI into the eMMC device, and change the dip switches to boot from that by default, then the microSD slot can have whatever partitioning you want. But you cannot load UEFI from microSD and have GPT partitioning on the same device.
Makes sense. The SD will be used to hold the UEFI images. Can a USB stick then be used to hold the uImage and board.dtb? If so, is it possible to 'hardcode' the paths to the stick to make the boot proceed unattended? (given the fact that there is no keyboard response atm).
- FDT: VenHw(3A02E7FE-0649-4FB4-BE4F-A862CA1872A9)/HD(2,MBR,0x00000000,0x2000,0x1A000)/board.dtb - LoaderType: Linux kernel with Local FDT
Global FDT Config - VenHw(3A02E7FE-0649-4FB4-BE4F-A862CA1872A9)/HD(2,MBR,0x00000000,0x2000,0x1A000)/board.dtb
[a] Boot Manager [b] Shell [c] Reboot [d] Shutdown Start:
There is no response on keypresses here. There should be?
Yes. Something in UEFI probably gets quite unhappy when trying to access filesystems in the above situation.
Can I make myself useful, and help to debug this? Shell access will probably give the capability to answer the above question regarding boot from USB myself :-)
This EFI boot is new for me, so please let me know if I do something wrong. Also, please let me know if this is the wrong list for this kind of questions.
This is definitely the correct list.
Thanks! I've subscribed :-)
Sander