Nick A

@mdidis do non secure boot images show any output. The one posted is an android boot output.

@dale there’s a new patch to fix boards without external 32k clock. I haven’t tested it yet. https://github.com/warpme/minimyth2/commit/728a14a73924e349fe88fb4def7e5f50a79aed5c

@mdidisDid you compile with the secure boot patch? Because it sounds like that’s your issue. If secure boot is not enabled you won’t get any output from your serial interface. post your dts. I’ll tell you the correct gpio for wifi and emmc.

@Ducdanh Nguyen hard to tell. I don’t see any markings for uart. It’s not going to be easy to debug your board.

@Randlin have you tried adding secure boot to @sicxnull build. If that doesn’t work you’ll need to play with the dram code. I don’t have time or a 1.5g board. https://github.com/sicXnull/armbian-build/tree/X96Q-TVBOX-LPDDR3

@RandlinTry removing 110,111,113 patches in my uboot. Then add https://github.com/armbian/build/blob/main/patch/u-boot/v2025-sunxi/0009-sunxi-h616-dram-support-1.5GB-RAM-size.patch

“This DRAM setup is currently not supported. resetting “ You need to extract your boot0 and use sunxi-fw to read your dram settings. sunxi-fw info -v boot0.bin Go back one page.

https://github.com/NickAlilovic/build/releases/ [01.296]secure enable bit: 1 I see this in your android log so I believe you have to enable secure boot. If the images don’t boot. These are the steps to enable secure boot for tanix_tx6s_axp313. (Link below) [01.303]PMU: AXP1530 You have a axp313a so transpeed, x98h and tanix might work for you. [359]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) Transpeed, x98h and tanix use ddr3 If emmc or wifi do not work. You can use your android dts to find the gpio numbers. You might also need to take a picture of your wifi chip.

@mdidis try the transpeed or x98h image. You might need to enable secure boot.

@jdie both of those are android logs

Orange pi zero 3 with 1.5g had the same problem too.. I think they used the 1.5g hardcoded patch to fix it. You might have to remove the newer ram size detection patch. I haven’t updated warpme patches in awhile so I’m hoping this bug has been fixed.

Oh sorry I forgot… you can add the secure boot patch but compiling minimyth2 might take awhile. or you can copy over minimyth2 latest uboot patches. https://github.com/warpme/minimyth2/tree/master/script/bootloaders/u-boot-aw/files these patches are for uboot version 2025.04. So you need to change the version number here. https://github.com/NickAlilovic/build/blob/v20250306/config/sources/families/include/sunxi64_common.inc declare -g BOOTBRANCH="${BOOTBRANCH:-"tag:v2025.01"}"

You can find secure boot in that link. Also, we are having issues with 1.5g boards. You can read the latest posts in that thread.

@Randlin Have you tried the latest minimyth2 images? https://github.com/warpme/minimyth2/releases/tag/v14.3.0 maybe you can revert to the old ram size detection. https://github.com/warpme/minimyth2/commit/962ac7da6cb84d0e41826c5555cb101b70a53a8d

Start reading here..