Re: Debugging efiboot

[Brook Milligan <brook%nmsu.edu@localhost>]

> On Jun 25, 2022, at 11:12 AM, Brook Milligan <brook%nmsu.edu@localhost> wrote:
> 
> What is the best way to debug this?  I’m open to all suggestions.

I’ve been looking into this further.  Here is a reference on arm data exceptions:

	https://developer.arm.com/documentation/ka002692/latest

Here is part of the output produced by efiboot:

9137236+2443104+1407136 [455399+757776+576954]=0xe217f4
data abort
pc : [<9ff5797a>]   lr : [<9ff579b1>]
reloc pc : [<8080097a>]   lr : [<808009b1>]
sp : 9df35a4c  ip : 00000000 fp : 00000000
r10: 9ff57000  r9 : 9df36eb8 r8 : 00019040
r7 : 9ff57c00  r6 : 9ff57bb4 r5 : 000000ad  r4 : 0001ac00
r3 : 00000000  r2 : 00000050 r1 : 9ff57bb0  r0 : abb1aaad
Flags: NzCv  IRQs off  FIQs on  Mode SVC_32
Code: ea83428a d1f52010 f856bdf0 40685b04 (f854b2c5) 
UEFI image [0x9cf03000:0x9cf2b79f] '/\efi\boot\bootarm.efi'
Resetting CPU …

If I interpret this correctly, lr is the link register and the illegal memory location is 8 bytes below that, i.e., 0x808009A9 (=2155874729).

Is this information helpful?  How can I figure out where that is in the source code?

Cheers,
Brook