S32G274ARDB2 Yocto built and pre built image does not boot

[asifrizwan]

Linux BSP 28.0
Machine: S32G274ARDB2 

I tired both pre build and by building the Yocto as per the " Linux BSP 28.0 User Manual for S32G274A". Unfortunately I am not able to understand the issue.

Always get following error: Bad Linux ARM64 Image magic!

Terminal Output:

Hit any key to stop autoboot: 0
run loadimage
run loadfdt
run mmcargs
${boot_mtd} ${loadaddr} - ${fdt_addr}
Bad Linux ARM64 Image magic!


Build Result:

NOTE: Tasks Summary: Attempted 2321 tasks of which 1 didn't need to be rerun and all succeeded.

Summary: There were 31 WARNING messages shown.

Kindly let me know what am I missing?

Regards,

[bpe]

The error you observed generally means you are trying to boot a binary that
does not appear as a valid kernel image. It is not clear why exactly this happens in
your case. The root cause may be a wrong image used to prepare your boot
media or a failure to correctly follow the image writing instructions, or the
boot card/memory being corrupt. BSP 28.0 pre-built images are known to boot
smoothly on RDB2. Note, however, that it is not the most recent Linux BSP for
your board. Suggestions:

1. Consider moving to the most recent Automotive BSP. Follow this link to obtain
it.

2. Follow the image programming instructions from the BSP User Manual strictly.

3. Make sure the binary you are trying to program is valid for your boot
media/memory type.

[asifrizwan]

Thanks for your input.

>> 1. Consider moving to the most recent Automotive BSP. Follow this link to obtain it.

 Linux BSP 29.0.0 is able to boot but unfortunately it crashed at the end:


[ 2.044164] 000: x0 : 0000000040000005
[ 2.048061] 000:
[ 2.050013] 000: Call trace:
[ 2.052937] 000: do_undefinstr+0x2e4/0x310
[ 2.057190] 000: el1_undef+0x10/0x84
[ 2.060913] 000: spi_mem_driver_register_with_owner+0x0/0x40
[ 2.066763] 000: do_one_initcall+0x50/0x1a8
[ 2.071105] 000: kernel_init_freeable+0x134/0x1d0
[ 2.075981] 000: kernel_init+0x10/0xf8
[ 2.079884] 000: ret_from_fork+0x10/0x24
[ 2.083967] 000: Code: f9401bf7 17ffff7d a9025bf5 f9001bf7 (d4210000)
[ 2.090625] 000: Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 2.098857] 000: SMP: stopping secondary CPUs
[ 2.103289] 000: Kernel Offset: disabled
[ 2.107275] 000: CPU features: 0x0002,2000200c
[ 2.111793] 000: Memory Limit: none
[ 2.115338] 000: ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---


Please share the link of  Linux BSP 27.0.0, I would really appreciate it.

Regards,

[bpe]

Your board fails to boot proven working binary images. Playing with BSP versions
is not a solution in your case. If you followed all suggestions given earlier
in this thread, and the problem is still there, a more appropriate course of
actions is:

1. Verify your board switch settings against the defaults specified in
   Section 3.1 of S32G-VNP-RDB2 User Guide.
2. Use another SD card.
3. Try replacing the power supply.
4. If nothing helps, the board is likely to be damaged. Study this article for other possible actions.

Best Regards,
Platon