This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

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:

Fullscreen
1
2
3
4
5
6
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...
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

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:

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
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
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

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?

0