Nick A

@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..

@Ducdanh Nguyen @ccs1664 is correct.. there’s a lot of information on that thread and the x96q threads to get your box running. I have to post the same advice over and over again. The last thread you posted in. I gave instructions to get your dram settings and dts. Have you extracted them? it could be possible that you have secure boot.

@ARx8 can you take a picture of your board so we can figure out if your wifi chip has mainline kernel drivers. You can find the gpio #’s using your dts.0.dts file. The wifi might already be detected but you are missing firmware. If you can post your dmesg.

@Randlin there’s a patch for hard coded 1.5 ram detection in the official armbian build. https://github.com/armbian/build/blob/main/patch/u-boot/v2025-sunxi/0009-sunxi-h616-dram-support-1.5GB-RAM-size.patch

I have some issue trying to build a new image. [🌱] artifact [ armbian-base-files :: armbian-base-files() ] jq: error: syntax error, unexpected '/', expecting $end (Unix shell quoting issues?) at <top-level>, line 1: /home/nick/Desktop/build/.tmp/work-3ba39b3b-774c-4ca7-9727-9091c1861a2f/tmp.UXcUDUX3m2 jq: 1 compile error [🚸] Could not find package filename for 'base-files' in distro repo [ looking for base-files, found_package_filename is ] [🚸] Command failed, retrying in 15s [ apt_find_upstream_package_version_and_download_url base-files ] jq: error: syntax error, unexpected '/', expecting $end (Unix shell quoting issues?) at <top-level>, line 1: /home/nick/Desktop/build/.tmp/work-3ba39b3b-774c-4ca7-9727-9091c1861a2f/tmp.E4L2MRkv6o jq: 1 compile error [🚸] Could not find package filename for 'base-files' in distro repo [ looking for base-files, found_package_filename is ] [🚸] Command failed, retrying in 15s [ apt_find_upstream_package_version_and_download_url base-files ] jq: error: syntax error, unexpected '/', expecting $end (Unix shell quoting issues?) at <top-level>, line 1: /home/nick/Desktop/build/.tmp/work-3ba39b3b-774c-4ca7-9727-9091c1861a2f/tmp.GvFd0v7vHh jq: 1 compile error If you restart the build with the same options it continues where the build left off and compiles fine. [🌱] artifact [ armbian-base-files :: armbian-base-files() ] [🌱] Found upstream base-files package filename [ base-files_12.4+deb12u11_arm64.deb ] [🌱] Found base-files upstream package version [ 12.4+deb12u11 ] [🌱] Getting ORAS manifest [ ORAS manifest from ghcr.io/armbian/os/armbian-base-files-bookworm-arm64:1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa ] [🌱] Artifact is available in remote cache [ ghcr.io/armbian/os/armbian-base-files-bookworm-arm64:1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa - 'armbian-base-files-bookworm-arm64 - 1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa - Armbian armbian-base-files original bookworm version "12.4+deb12u11" framework bash hash "aa17ac95f5df03a9" - type: deb' ] [🌱] Obtaining artifact from remote cache [ ghcr.io/armbian/os/armbian-base-files-bookworm-arm64:1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa into base-files_1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa_arm64.deb ] ✓ Pulled base-files_1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa_arm64.deb 51.6/51.6 kB 100.00% 11ms └─ sha256:0fdb605bead0a6b686964f17e6cd33b487c94c32b01abdff64a72b9ec12590ec ✓ Pulled application/vnd.oci.image.manifest.v1+json 901/901 B 100.00% 222µs └─ sha256:4ab7c71e4c8dd5f07c15499186dab687550c9237898f4e9fa99d72e76e232549 [🔨] Pulled [registry] ghcr.io/armbian/os/armbian-base-files-bookworm-arm64:1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa [🔨] Digest: sha256:4ab7c71e4c8dd5f07c15499186dab687550c9237898f4e9fa99d72e76e232549 [💖] artifact [ obtained from remote cache: armbian-base-files-bookworm-arm64 1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa ] [🌱] Reversioning package [ re-version 'armbian-base-files-bookworm-arm64(deb)::1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa' to '25.05.0-trunk-12.4+deb12u11-bookworm' ] [🔨] removed '/home/nick/Desktop/build/output/packages-hashed/extra/bookworm-utils/base-files_1-bookworm-1armbian1-Baa17-U12.4--deb12u11-R55fa_arm64.deb' log-build-b4214f74-4d03-4030-9e38-7a16d2e86846.log

You can find the dram config options here. https://elixir.bootlin.com/u-boot/v2025.07-rc2/source/arch/arm/mach-sunxi/Kconfig if DRAM_SUN50I_H616 config DRAM_SUNXI_DX_ODT hex "DRAM DX ODT parameter" help DX ODT value from vendor DRAM settings. config DRAM_SUNXI_DX_DRI hex "DRAM DX DRI parameter" help DX DRI value from vendor DRAM settings. config DRAM_SUNXI_CA_DRI hex "DRAM CA DRI parameter" help CA DRI value from vendor DRAM settings. config DRAM_SUNXI_ODT_EN hex "DRAM ODT EN parameter" default 0x1 help ODT EN value from vendor DRAM settings. config DRAM_SUNXI_TPR0 hex "DRAM TPR0 parameter" default 0x0 help TPR0 value from vendor DRAM settings. config DRAM_SUNXI_TPR2 hex "DRAM TPR2 parameter" default 0x0 help TPR2 value from vendor DRAM settings. config DRAM_SUNXI_TPR6 hex "DRAM TPR6 parameter" default 0x3300c080 help TPR6 value from vendor DRAM settings. config DRAM_SUNXI_TPR10 hex "DRAM TPR10 parameter" help TPR10 value from vendor DRAM settings. It tells which features should be configured, like write leveling, read calibration, etc. config DRAM_SUNXI_TPR11 hex "DRAM TPR11 parameter" default 0x0 help TPR11 value from vendor DRAM settings. config DRAM_SUNXI_TPR12 hex "DRAM TPR12 parameter" default 0x0 help TPR12 value from vendor DRAM settings.

Have you tried running sunxi-fw with the boot image you used to extract the dts? The boot image you posted is a U-Boot FIT image. It doesn't have the dram information we are looking for. I believe mmcblk0boot0 is the correct boot image but the one you uploaded didn't work with sunxi-fw. Also, I found this in your dts. Maybe these settings will work. To make sure these settings are correct I prefer to get the dram settings using the sunxi-fw tool. dram { compatible = "allwinner,dram"; clocks = <0xda>; clock-names = "pll_ddr"; dram_clk = <0x288>; dram_type = <0x07>; dram_zq = <0x3f3fdd>; dram_odt_en = <0x9988eeee>; dram_para1 = <0x30fa>; dram_para2 = <0x1000>; dram_mr0 = <0x00>; dram_mr1 = <0xc3>; dram_mr2 = <0x06>; dram_mr3 = <0x01>; dram_tpr0 = <0x00>; dram_tpr1 = <0x00>; dram_tpr2 = <0x00>; dram_tpr3 = <0x00>; dram_tpr4 = <0x00>; dram_tpr5 = <0x00>; dram_tpr6 = <0x2fc08080>; dram_tpr7 = <0x00>; dram_tpr8 = <0x00>; dram_tpr9 = <0x00>; dram_tpr10 = <0x402f3379>; dram_tpr11 = <0xd100b0f>; dram_tpr12 = <0x11131113>; dram_tpr13 = <0x80060>; linux,phandle = <0x183>; phandle = <0x183>; device_type = "dram"; dram_dx_odt = <0x6060606>; dram_dx_dri = <0xd0d0d0d>; dram_ca_dri = <0x1919>; dram_mr4 = <0x00>; dram_mr5 = <0x00>; dram_mr6 = <0x00>; dram_mr11 = <0x00>; dram_mr12 = <0x00>; dram_mr13 = <0x00>; dram_mr14 = <0x00>; dram_mr16 = <0x00>; dram_mr17 = <0x00>; dram_mr22 = <0x00>; }; The dram clock is in hex you'll need to convert this value to decimal. https://www.rapidtables.com/convert/number/hex-to-decimal.html

Actually in that post it was about downloading the boot_a partition. Then extracting the dts.. you can skip the dts extraction part for now. We need your boot_a partition. also that’s not the android dts you posted. It has some info but not all of it.

This post should help extracting your boot.img from android. That’s if your box is already rooted.

AXP1530 is the same as AXP313a. Take a look at the link I posted above. You could use this tool to extract your dram settings from an android update or boot0.bin. https://github.com/apritzel/sunxi-fw sunxi-fw info -v boot0.bin

H313/H616/H618 are pretty much the same SOC. It’s the AXP power management IC that’s different. Also RAM and WIFi chips are usually different. https://linux-sunxi.org/AXP_PMICs

Your tv stick probably has secure boot enabled. You can compile a secure boot image using these steps.

Try the Transpeed, vontar, x98h orTanix-acp313 images. There might be few other boxes that use axp313 chip in the list.

Can you tell me the axp### numbers on the chip? I can’t see it in your pictures. Try these images.. maybe you’ll find one that boots https://github.com/NickAlilovic/build/releases/tag/20250306