Morello board setup issue (hangs at: "EFI stub: Exiting boot services and installing virtual address map...")

Hello,

I am trying to setup the Morello board with "busybox" (release 1.4). I followed the following guide:

https://git.morello-project.org/morello/docs/-/blob/morello/release-1.4/user-guide.rst

After plugging-in the bootable USB drive (flashed with busybox.img) and choosing it from "Boot manager", the AP port (n+3) seems to stop at the following line:

"EFI stub: Exiting boot services and installing virtual address map..."

Here's the log of AP port:

Loading driver at 0x000F54C0000 EntryPoint=0x000F6B924ECMiB  100%  49.24KiB/s ]
Loading driver at 0x000F54C0000 EntryPoint=0x000F6B924EC
EFI stub: Booting Linux Kernel...
EFI stub: EFI_RNG_PROTOCOL unavailable, KASLR will be disabled
EFI stub: Using DTB from configuration table
EFI stub: Exiting boot services and installing virtual address map...

At the same time MCC port doesn't hang, and still can be interacted with.

I checked that I select the right device in boot manager by unplugging the USB, retrying and seeing it disappear from the list.

Is it normal that the bootable USB drive appears as the following on my host PC?

sdd      8:48   1  14.7G  0 disk
├─sdd1   8:49   1  29.9M  0 part
└─sdd2   8:50   1     8M  0 part /media/michal/88f608b2-4a41-4796-9669-52535f67a

Is it right that it has 2 partitions and are the sizes correct?

I prepared it by first formatting it to either fat16 and fat32 (did it twice) with a single 15GB partition (and once with unallocated space), and then using commands from the guide:

sudo dd if=<IMAGE> of=/dev/sdb conv=fsync bs=1M
sync

On the Setting up the Morello Hardware Development Platform there are instructions on how to "format the Morello board’s pre-installed SATA SSD", is that necessary for busybox setup? (I didn't do it)

Here's the log from MCC port following the reboot:

Cmd> REBOOT
Rebooting...
Disabling debug USB..

MCC to access SD card request acknowledged.
Clear ULINK JTAG
Board rebooting...  

Powering up system...

MCC to access SD card request acknowledged.
Clear ULINK JTAG

Time :  14:20:26
Date :  13:05:2022  

Switching on ATXPSU...
Switching on main power...

12V Rail Check Pass 

Reading Board File \MB\HBI0364B\io_v010f.txt
TOTAL OSCCLKS: 15   
PMIC RAM configuration (80_1_86G.bin)...

Temperature (deg C) 
Outlet = 29.9 PMIC   = 40.9 SoC = 35.9 IN2  = 32.9 IN1 = 31.9
MidBrd = 41   PCIeSW = 47   MCC = 33.5 FPGA = 39.7 SoC Fan Speed = 9%
ALERT off

Configuring motherboard (rev B, var A)...

Configuring FPGA from file \MB\HBI0364B\io_v010f.bit
Address: 0x007E0000 
FPGA configuration complete.

Config clocks num: 15
OSCCLK0  : 50.000000MHz
OSCCLK1  : 50.000000MHz
OSCCLK2  : 50.000000MHz
OSCCLK3  : 50.000000MHz
OSCCLK4  : 50.000000MHz
OSCCLK5  : 50.000000MHz
OSCCLK6  : 50.000000MHz
OSCCLK7  : 50.000000MHz
OSCCLK8  : 75.000000MHz
OSCCLK9  : 85.000000MHz
OSCCLK10  : 12.288000MHz
OSCCLK11  : 50.000000MHz
OSCCLK12  : 50.000000MHz
OSCCLK13  : 50.000000MHz
OSCCLK14  : 170.000000MHz
OSCCLK setup: PASSED
GTXCLK setup: PASSED

EEPROM config found 
File to compare \MB\HBI0364B\pci_v002.bin \MB\HBI0364B\pci_v002.bin
Writing SCC 0x014 with ACLK 50000000 Hz
Writing SCC 0x00C with 0x00000003
Writing SCC 0x020 with 0x06090805
Writing SCC 0x024 with 0x06060606
Writing SCC 0x028 with 0x00000606
Writing SCC 0x1160 with 0x00000001
Writing SCC 0x1164 with 0x01000000
Writing SCC 0x1168 with 0x00000000
Writing SCC 0x116C with 0x00000000
Writing SCC 0x1180 with 0x00000000
Writing SCC 0x1184 with 0x0000000C
Writing SCC 0x1188 with 0x00000000
Writing SCC 0x118C with 0x00000000
Writing SCC 0x1190 with 0x00000000
Writing SCC 0x1194 with 0x00000000
Writing SCC 0x1198 with 0x00000000
Writing SCC 0x119C with 0x00000000
Reading SCC 0xFF8 with 0x0A364A08
Reading SCC 0xFFC with 0x41050000


QSPI Controller detected id = 0x4000303
Device ID 0x20, 0xBB, 0x19
Setting QSPI dummy clocks...
Dummy clocks already set
Device ID 0x20, 0xBB, 0x19
QSPI Controller detected id = 0x4000303
Device ID 0x20, 0xBB, 0x19
Setting QSPI dummy clocks...
Dummy clocks already set
Device ID 0x20, 0xBB, 0x19
QSPI Controller detected id = 0x4000303
Device ID 0x20, 0xBB, 0x19
Setting QSPI dummy clocks...
Dummy clocks already set
Device ID 0x20, 0xBB, 0x19

Reading images file \MB\HBI0364B\images.txt

PCIe mac address = 0002 F700977E
PCC mac address = 0002 F700977D
LAN9221 was identified successfully.
MAC addrs test: PASSED

SMC MAC address 0002-F700-977F

Identifying DDR 0   

Device Information  
Manufacturer ID = 80 2C
Module Part Number = 9ASF1G72PZ-2G9E1
Module Serial Number = F2 E C0 FE

Identifying DDR 1   

Device Information  
Manufacturer ID = 80 2C
Module Part Number = 9ASF1G72PZ-2G9E1
Module Serial Number = F2 E C0 F7

Setting System LEDs[7:4]
Setting PCIe_nPERST/PCIESW_PERSTN
PCIe control C2C disabled
APUART0 connected to USBPORT_3
SCPUART connected to USBPORT_4
MCPUART connected to USBPORT_5
PL031 Date & Time set = Fri May 13 14:20:45 2022

QSPI test (0x6403FEF8):0xFFFFFFFF
Releasing SOC_nPOR/SOC_nSRST

SPI Write command to PCC: register 3 cmd 0xD003 tx data 0x2
SPI Return data from PCC: register 3 cmd 0x2000 rx data 0x0

USB Serial Number = 500541683023
Cmd>                

I attached all the files from the SD card (as described in the guide, these were copied from "bsp/board-firmware/", with "SOFTWARE" directory overwritten by "output/soc/firmware/").

https://www.mediafire.com/file/k3osfjllzk6iiq3/M1SDP.tar.gz/file

Do you know what could be the reason for this issue?