On Mon, Oct 7, 2024, at 20:23, Linus Walleij wrote: > On Mon, Oct 7, 2024 at 6:35 PM Karl Chan <exxxxkc@xxxxxxxxxxxxxxx> wrote: > > Starting kernel ... > > undefined instruction > pc : [<41208004>] lr : [<4a921f8f>] > reloc pc : [<41208004>] lr : [<4a921f8f>] > sp : 4a822838 ip : 00000001 fp : 00000000 > r10: 4a83b914 r9 : 4a822ea0 r8 : 00000000 > r7 : 00000000 r6 : 41208000 r5 : 4a97d848 r4 : 00000000 > r3 : 644d5241 r2 : 4a0ae000 r1 : 08040001 r0 : 00000000 > Flags: nzCV IRQs off FIQs off Mode SVC_32 > Resetting CPU ... > > resetting ... > > So perhaps someone knows how we can get around this. > > It seems to me the U-Boot is in 32bit mode and tries to just > execute an Aarch64 binary and that doesn't work. > > What we need is a 32bit mode preamble that can switch > the machine to Aarch64 and continue. I found this older patch for u-boot about a similar problem on sunxi machines: https://patchwork.ozlabs.org/project/uboot/patch/1480902750-839-12-git-send-email-andre.przywara@xxxxxxx/#1528602 Karl, do you have the u-boot sources for this board? I found a source tarball for kernel (both in 32-bit and 64-bit mode) and userland on this machines at https://support.linksys.com/kb/article/316-en/ but the u-boot sources in there don't seem to match the binary (they are only used to build the u-boot tools, but not the actual loader). Is this the same base you are working from, or do you have something else beyond that? Arnd
