Compiling from master doesn't generate bootable Khadas Vim2 images / kernels

    I just compiled a fresh image from master for the Khadas Vim2 box which is running on a year old version. At the moment it doesn't generate a bootable image (no special settings, just running the PROJECT=Amlogic ARCH=aarch64 DEVICE=AMLGX UBOOT_SYSTEM="khadas-vim2" make image I was using before; screen remains black, white LED on, no USB input). I checked with the running version by just replacing the system and kernel with the freshly compiled one, same result (moving the stuff back, produces a working system again). Other recent images boot, like the latest oowow and Armbian (November last year). I think I tried a new build in last August and already failed with the same result (but didn't have time to investigate, but simply switched back to the working image). Any ideas what I do wrong here?

    This boot fail is known issue

    Post

    RE: Official LE13 Test Images for Amlogic (Kodi-22)

    It looks like CONFIG_KASAN=y snuck into a kernel defconfig and this increases the KERNEL size to a point where standard vendor u-boot configurations (as used with Android STBs) will fail to load the kernel and fault. This is nothing to do with RAM size.

    I have a large list of changes to work on and current progress is rather slow, so I will update images at some point soon, but to avoid breaking promises I'm not going to give a timeline on when.
    chewitt
    April 9, 2026 at 10:44 AM

    Please wait to fix, or disable CONFIG_KASAN on your kernel config and build image.