Hi all.
Ok, some steps about booting OpoenBSD on the C5:
As mentioned, I have a compiled u-boot for the board. I also verify that it
works properly
and it looks ok.
I also have a copy of the dtb, I've loaded it into u-boot and it can print it
correctly, so I see
it as ok.
I got the various memory addresses to boot the EFI bootloader and the related
fdt as,
of course, you can esily find those from the boot.scr script (no distro_bootcmd
and no
"run findfdt" here, so I needed to go and hunt for the addresses around:
setenv fdt_addr_r ${dtb_mem_addr}
setenv kernel_addr_r ${loadaddr_kernel}
dtb_mem_addr and loadaddr_kernel are, of course, already set when u-boot starts.
Following the small magic in the arm64 installation instructions page, trying
to boot
the EFI bootloader results in this:
"Synchronous Abort" handler, esr 0x9600004f
Fault address:0xdf58ad08
elr: 00000000000d3a38 lr : 00000000000d3a20 (reloc)
elr: 00000000df65ca38 lr : 00000000df65ca20
x0 : 00000000d61ee000 x1 : 0000000000000000
x2 : 0000000000004000 x3 : 00000000d757fbe0
x4 : 00000000000d61ee x5 : 0000000000000040
x6 : 00000000d61ee000 x7 : 0000000000000007
x8 : 0000000000000006 x9 : 0000000000000000
x10: 0000000000003aec x11: 00000000d71fed04
x12: 0101010101010101 x13: 0000000000000028
x14: ffffffffffffffff x15: 0000000000000002
x16: 00000000df6380bc x17: 0000005800000004
x18: 00000000d71ff570 x19: 00000000df58ad00
x20: 00000000df70f000 x21: 0000000000000000
x22: 00000000d76959c0 x23: 0000000000000003
x24: 00000000df743864 x25: 00000000df704000
x26: 0000000015cf81b5 x27: 0000000000000000
x28: 00000000d76959f0 x29: 00000000d71fefd0
Call trace:
[<00000000df65ca38>] efi_var_mem_init+0x48/0xe0
[<00000000df65d2ac>] efi_init_variables+0x8/0x28
[<00000000df65bed0>] efi_init_obj_list+0x40/0x1e0
[<00000000df59eb68>] do_bootefi+0x50/0x1dc
[<00000000df5db598>] cmd_process+0x184/0x214
[<00000000df5cf7fc>] run_list_real+0x6e8/0x730
[<00000000df5cf9c0>] parse_stream_outer+0x17c/0x698
[<00000000df5cf0e0>] parse_string_outer+0xdc/0x110
[<00000000df5cf6ac>] run_list_real+0x598/0x730
[<00000000df5cf9c0>] parse_stream_outer+0x17c/0x698
[<00000000df5cff20>] parse_file_outer+0x44/0x6c
[<00000000df5da9b8>] cli_loop+0x8/0x10
[<00000000df5cdfb0>] main_loop+0x60/0x70
[<00000000df5d1ee0>] run_main_loop+0x10/0x18
[<00000000df5d21e4>] board_init_r+0x54/0x9c
"efi_var_mem_init" is, literally, a function nthat tries to initialize some
data structures
(it doesn't even take any argument).
Now I'm a bit lost here, due to my lack of experience in the matter. Should I
give up?
Any additional resource I can follow to further try to debug the issue?
-- absc
