Randlin

I tried this patch https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3/blob/main/patches/1.5GB_OPZ3_fix.patch , ported to your u-boot (hardcoded 1.5gb), same result. Will try warpme or that sicxnull build, still wondering if I am on a red herring, I'll keep poking around and testing stuff. I'll post as I find things that work/don't work, hopefully this will help someone else too. And no worries, I'm sure your busy. You've helped a lot and helped me get a foundation. Thank you 💯 Log for notes:

Okay that detects 1.5gb at spl, but then detects 2gb at uboot, just like the first patch I tried. Maybe something to do with me currently using the U-Boot DTB from X96-q, a 2gb device? I did try a different config for a different tv box as well (transpeed), but that had the same result. U-Boot SPL 2025.01-armbian-2025.01-S6d41-P37d4-H8869-V004f-Bb703-R448a-dirty (Aug 13 2025 - 17:14:56 +0000) DRAM base address is defined as 0x40000000 DRAM has 15 b/raw, 10 b/col, 4 B/width, 2 #rank and 8 #bank DRAM top address must be less than 0x80000000 DRAM top address must be less than 0x60000000 DRAM: 1536 MiB Trying to boot from MMC1 NOTICE: BL31: v2.10.14(debug):armbian NOTICE: BL31: Built : 15:34:29, Aug 13 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0b2520, model: hechuang,x96-q LPDDR3 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.01-armbian-2025.01-S6d41-P37d4-H8869-V004f-Bb703-R448a-dirty (Aug 13 2025 - 17:14:56 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: hechuang,x96-q LPDDR3 DRAM: 2 GiB (effective 0 Bytes)

So I copied the patches from Minimyth2 to your Armbian and it built, however it is now detecting 2gb ram lol.... Will try to see if I can find a way to hardcode 1.5gb

I've been doing some research/reading and I see that this was a problem before with a somewhat similar box with 1.5gb ram: I will try copying the patches over, thank you for all your help so far!

Do any of those images use secureboot uboot (toc0) that you know of?

Unfortunately that patch has not made a significant difference in how far it boots. It does detects 1.5gb in startup now but then detect 2gb later once uboot dts loads and then halts as usual:

Hmm, in Android boot log I saw references to 1.5g ram, maybe this? https://github.com/johang/sd-card-images/issues/150 The spot in question: [536]Actual DRAM SIZE =1536 M [538]DRAM SIZE =1536 MBytes, para1 = 30fa, para2 = 6001000, dram_tpr13 = 26061 Android boot log in easier to read format:

Sorry for the delay, was busy the last week. I applied the ram settings and did a couple of builds with different ones. Nothing has worked any better so far. Should I try more of the ram configs? does not work, uboot bootloops: dram 7 in dts I extracted using dts-compiler (there are other dram definitions in there as well) +CONFIG_DRAM_CLK=648 +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x3030303 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0xe0e0e0e +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x1f12 +CONFIG_DRAM_SUN50I_H616_ODT_EN=0x01 +CONFIG_DRAM_SUN50I_H616_TPR0=0xc0001002 +CONFIG_DRAM_SUN50I_H616_TPR6=0x33808080 +CONFIG_DRAM_SUN50I_H616_TPR10=0x2f1107 +CONFIG_DRAM_SUN50I_H616_TPR11=0xddddcccc +CONFIG_DRAM_SUN50I_H616_TPR12=0xeddc7665 works the same as before, still gets stuck at same place (from binwalk dts): +CONFIG_DRAM_CLK=648 +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x06060606 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0d0d0d0d +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x1919 +CONFIG_DRAM_SUN50I_H616_ODT_EN=0x9988eeee +CONFIG_DRAM_SUN50I_H616_TPR0=0x00 +CONFIG_DRAM_SUN50I_H616_TPR6=0x2fc08080 +CONFIG_DRAM_SUN50I_H616_TPR10=0x402f3379 +CONFIG_DRAM_SUN50I_H616_TPR11=0xd100b0f +CONFIG_DRAM_SUN50I_H616_TPR12=0x11131113 +CONFIG_DRAM_SUN50I_H616_TPR13=0x80000000 Is it possible this error may be an issue? INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 And the uboot serial log from the working one:

Ok, just used adb pull /proc/device-tree and used dtc and got this dts. This should be a complete dts. dts.txt

Yeah with the full dump it is essentially the same as boot.img. Manual testing it is.

Hmm, I tried running it on both mmcblk0boot* and got no output. I'll try running it on the full dump with -a to see if anything comes up. I'll try adding it to the config and go from there, see if it works. I'm not familiar with memory config and a lot of this stuff, but I am trying to learn all kinds of low level stuff and welcome the challenge!

And just the dts dtb.0.dts.txt

Ok, that extractor worked. I uploaded it as a zip here: https://uploadnow.io/f/9VvPT91

direct link to boot: https://archive.org/download/G96_Firmware_Dump/Dumped Partitions/boot

Hmm, I used a different boot.img extractor before to try to get dts, but that spectacularly failed ( https://github.com/anestisb/android-unpackbootimg ). I do have a dump of each of the partitions from root, but there was no boot_a boot_b, just boot (not an a/b system). I'll try that extractor, hopefully that will be better. everthing is here: https://archive.org/download/G96_Firmware_Dump/Dumped Partitions/ list of partitions dumped: (there are 17 listed in the emmc, but 18 in android for some reason, probably one is a duplicate) Reserve boot bootloader cache empty env frp media_data metadata misc mmcblk0boot0 mmcblk0boot1 private recovery super vbmeta vbmeta_system vbmeta_vendor