Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A3700 customer board: execution of ipxe based efi image results in ERROR and hang #24

Open
rustyscottweber opened this issue Oct 21, 2021 · 1 comment

Comments

@rustyscottweber
Copy link

Espressobin based board. Attempt to boot an EFI image based on IPXE so that a different image can be chain loaded.

Marvell>> dhcp
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
*** Unhandled DHCP Option in OFFER/ACK: 119
*** Unhandled DHCP Option in OFFER/ACK: 119
DHCP client bound to address 10.10.10.199 (1026 ms)
Using neta@30000 device
TFTP from server 10.10.20.2; our IP address is 10.10.10.199; sending through gateway 10.10.10.1
Filename 'UEFIBoot-arm64.efi'.
Load address: 0x5000000
Loading: ###############
	 1.4 MiB/s
done
Bytes transferred = 212480 (33e00 hex)
Marvell>> boot 
  boot bootd bootefi bootelf booti bootm bootp bootvx
Marvell>> boot
  boot bootd bootefi bootelf booti bootm bootp bootvx
Marvell>> printenv
baudrate=115200
bootcmd=mmc dev 0; ext4load mmc 0:1 0x5000000 boot/Image; ext4load mmc 0:1 0x4f00000 boot/armada.dtb;  setenv bootargs ttyMV0,115200 earlycon=ar3700_uart,0xd0012000 root=/dev/mmcblk0p2 rw rootwait; booti 0x5000000 - 0x4f00000; bootdelay=2
bootdelay=2
bootfile=UEFIBoot-arm64.efi
bootmmc=mmc dev 0; ext4load mmc 0:1 $kernel_addr $image_name;ext4load mmc 0:1 $fdt_addr $fdt_name;setenv bootargs $console root=/dev/mmcblk0p1 rw rootwait; booti $kernel_addr - $fdt_addr
console=console=ttyMV0,115200 earlycon=ar3700_uart,0xd0012000
dnsip=10.10.10.1
eth1addr=00:51:82:11:22:01
eth2addr=00:51:82:11:22:02
eth3addr=00:51:82:11:22:03
ethact=neta@30000
ethaddr=F0:AD:4E:0C:CB:2C
ethprime=eth0
fdt_addr=0x4f00000
fdt_high=0xffffffffffffffff
fdt_name=boot/armada.dtb
fdtcontroladdr=3f716298
fileaddr=5000000
filesize=33e00
gatewayip=10.10.10.1
get_images=tftpboot $kernel_addr $image_name; tftpboot $fdt_addr $fdt_name; run get_ramfs
get_ramfs=if test "${ramfs_name}" != "-"; then setenv ramfs_addr 0x8000000; tftpboot $ramfs_addr $ramfs_name; else setenv ramfs_addr -;fi
hostname=marvell
image_name=boot/Image
initrd_addr=0xa00000
initrd_size=0x2000000
ipaddr=10.10.10.199
kernel_addr=0x5000000
loadaddr=0x5000000
netdev=eth0
netmask=255.255.255.0
ramfs_addr=0x8000000
ramfs_name=-
root=root=/dev/nfs rw
rootpath=/srv/nfs/
serverip=10.10.20.2
set_bootargs=setenv bootargs $console $root ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:none nfsroot=$serverip:$rootpath $extra_params
stderr=serial@12000
stdin=serial@12000
stdout=serial@12000

Environment size: 1639/65532 bytes
Marvell>> bootefi ${kernel_addr} ${fdt_addr}
## Starting EFI application at 05000000 ...
Scanning disk [email protected]...
Card did not respond to voltage select!
mmc_init: -95, time 50
Found 1 disks
## Application terminated, r = 9
ERROR : memory not allocated

I've validated and checked that the .efi image can be booted by other classes of arm64 based machines.

@erdoukki
Copy link

erdoukki commented Aug 4, 2024

https://www.cybermind.fr/en/Cyber/EspressoBin-GlobalScaleTechnologies-UEFI-BOOT/

May be these notes can be helpfull...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants