endrift

I did more digging. It seems like the U-boot build is buggy somehow. I managed to work around it and get it to boot by adding this line to the armbianEnv.txt file: skip_board_fixup="1" I don't really know why this works, but it did.

Hi, I'm also having this problem, or a similar one. I grabbed a UART breakout and am getting an exception when trying to boot: Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 32000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 20195814 Bytes = 19.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Loading Ramdisk to 7ac02000, end 7bf449e6 ... OK Loading Device Tree to 000000007ab90000, end 000000007ac01fff ... OK "Synchronous Abort" handler, esr 0x96000004 elr: 000000000106056c lr : 000000000104fee8 (reloc) elr: 000000007dfb756c lr : 000000007dfa6ee8 x0 : 040da13e7bc5efcf x1 : 000000007dfbebc8 x2 : 0000000000000010 x3 : 0000000000000000 x4 : 0000000000000000 x5 : 040da13e7bc5efcf x6 : 000000007bf5ce00 x7 : 0000000000000000 x8 : 0000000000000007 x9 : 0000000000000000 x10: 00000000000001dc x11: 000000007bf4928c x12: 00000000000000b0 x13: 000000007bf49248 x14: 000000007ab90000 x15: 0000000000000020 x16: 000000007bf449e6 x17: 0000000000000000 x18: 000000007bf54db0 x19: 000000007af49040 x20: 000000007df57b20 x21: 000000007dfbebc8 x22: 0000000000001000 x23: 000000007bf5cd50 x24: 000000007dfdc8a0 x25: 0000000001000000 x26: 0000000001000000 x27: 0000000001000000 x28: 0000000000001000 x29: 000000007bf49240 Code: eb02009f 54000061 52800000 14000006 (386468a3) Resetting CPU ... resetting ... Disassembling the code shows that it's trying to load the byte at the address x4 + x5, which is very clearly not valid memory.