flipthedream

Thanks for your help, but no luck yet. One very important item I noticed is that using the Armbian compile.sh does not create a zImage file and creates uImage instead. The image that works uses zImage, which I believe is the compressed kernel? How do I make it boot with uImage that is produced by the Armbian compile.sh process?

Hello, I am new here and stuck trying to build and boot my own image successfully. I have a T95 S1 box that boots into Linux fine from one of the Yandisk images I have downloaded from a link here. I attempted to build one of the experimental set-top box configurations, updated the uEnv.ini to match the file on the image that works (meson-gxl-s905x-khadas-vim.dtb), but the image I create does not boot. I am trying to identify what is different between the two and have noticed the following differences: - I compared the working and non-working dtb files and they are not the same size, so I assume there are updates? - I also noticed when I build an image myself I only end up with one ext4 partition instead of the vfat BOOT + ext4 ROOT partition like the working card. Does the vfat BOOT partition make a difference? - If the meson-gxl-s905x-khadas-vim.dtb file works from the downloaded image shouldn't the meson-gxl-s905x-khadas-vim.dtb file from my build work also? Or should I try all the other dtb files until one works?