Uboot says bad image magic - mainline kernel
10-13-2024, 01:17 PM
In an attempt to troubleshoot failing to get generic alpine linux to run on PA64-2G-LTS, I've tried to reduce the problem to the smallest steps that are legible to me.
When booting the kernel, I get "Bad ARM64 Image Magic" I can't figure out what this means, and why it is happening. Sources I have searched seem to be board specific, and found nothing on this board. I've arrived at a point where I cannot find a way to reason further about it, so thus I am reaching out.
I am currently loading the kernel and dtb manually at the uboot prompt:
setenv bootargs loglevel=7 earlyprintk
fatload mmc 0:1 0x42000000 boot/vmlinux
fatload mmc 0:1 0x4a000000 boot/u-boot.dtb
booti 0x42000000 - 0x4a000000
My current configuration is:
- linux 5.14 from mainline (git:7d2a07b769330c34b4deabeed939325c77a7ec2f)
- u-boot v2024.10 from https://source.denx.de/u-boot/u-boot (git:f919c3a889f0ec7d63a48b5d0ed064386b0980bd)
- dtb from the u-boot build
- bl31.bin from PLAT=sun50i_a64 https://git.trustedfirmware.org/TF-A/tru...ware-a.git lts-v2.10.6 (git:f2aebf361050d69176d60016170291efa9e08a68)
- scp.bin from https://github.com/crust-firmware/crust 0.6 (git:ffe9f1ac9c675e6e67db9084bd19fbdeffd8e162)
- u-boot-sunxi-with-spl.bin written to offset 8k
- tried sd and emmc vfat single partition (whole disk) with
* boot/vmlinux
* boot/u-boot.dtb
Files:
- uboot defconfig: https://g33k.holbrook.no/c36cab0e6a15127...7b25f71bdd
- uboot environment (saved from soc): https://g33k.holbrook.no/1c4d93e6510eb49...2329468b73
- linux defconfig: https://g33k.holbrook.no/5bde4487e333f5a...19beb3382f
When booting the kernel, I get "Bad ARM64 Image Magic" I can't figure out what this means, and why it is happening. Sources I have searched seem to be board specific, and found nothing on this board. I've arrived at a point where I cannot find a way to reason further about it, so thus I am reaching out.
I am currently loading the kernel and dtb manually at the uboot prompt:
setenv bootargs loglevel=7 earlyprintk
fatload mmc 0:1 0x42000000 boot/vmlinux
fatload mmc 0:1 0x4a000000 boot/u-boot.dtb
booti 0x42000000 - 0x4a000000
My current configuration is:
- linux 5.14 from mainline (git:7d2a07b769330c34b4deabeed939325c77a7ec2f)
- u-boot v2024.10 from https://source.denx.de/u-boot/u-boot (git:f919c3a889f0ec7d63a48b5d0ed064386b0980bd)
- dtb from the u-boot build
- bl31.bin from PLAT=sun50i_a64 https://git.trustedfirmware.org/TF-A/tru...ware-a.git lts-v2.10.6 (git:f2aebf361050d69176d60016170291efa9e08a68)
- scp.bin from https://github.com/crust-firmware/crust 0.6 (git:ffe9f1ac9c675e6e67db9084bd19fbdeffd8e162)
- u-boot-sunxi-with-spl.bin written to offset 8k
- tried sd and emmc vfat single partition (whole disk) with
* boot/vmlinux
* boot/u-boot.dtb
Files:
- uboot defconfig: https://g33k.holbrook.no/c36cab0e6a15127...7b25f71bdd
- uboot environment (saved from soc): https://g33k.holbrook.no/1c4d93e6510eb49...2329468b73
- linux defconfig: https://g33k.holbrook.no/5bde4487e333f5a...19beb3382f