Rodrigo Campos

Hi @Nick A, I really need your help to understand the way to change the 171-add-x98h-defconfig.patch. Firstly, I extracted the DRAM parameters, but there are 15 of them: DRAM parameters, DRAM parameters 1, ... DRAM parameters E. Some of them have distinct parameters. The first of then (DRAM parameters) have the very identical parameters as yours, only differ in the same parameters, that isn't in patch file like TPR13, but I don't know if it matters. So I tried using the DRAM parameters 1, which is the most different, with clock 600 instead of 648 and almost all parameters different, but it works the same way with the same 2GB of RAM. I think this is strange, because with so many differences, I expected the image would not work. Do you have any tips for giving me? My extracted parameters: ./sunxi-fw info -v ./image4.img @ 0: wty: PhoenixSuite image file header v3.0, 45 images, 1859 MB wty:sys_config.fex : 34908 bytes @ +0x000000b800 wty:board.fex : 1024 bytes @ +0x0000014400 wty:config.fex : 53248 bytes @ +0x0000014800 wty:split_xxxx.fex : 512 bytes @ +0x0000021800 wty:sys_partition.fex : 5601 bytes @ +0x0000021c00 wty:sunxi.fex : 71680 bytes @ +0x0000023400 wty:boot0_nand.fex : 61440 bytes @ +0x0000034c00 wty:boot0_sdcard.fex : 61440 bytes @ +0x0000043c00 wty:u-boot.fex : 917504 bytes @ +0x0000052c00 wty:u-boot-crash.fex : 37 bytes @ +0x0000132c00 wty:toc1.fex : 8 bytes @ +0x0000133000 wty:toc0.fex : 8 bytes @ +0x0000133400 wty:fes1.fex : 40160 bytes @ +0x0000133800 wty:boot_package.fex : 1294336 bytes @ +0x000013d800 wty:usbtool.fex : 154624 bytes @ +0x0000279800 wty:usbtool_crash.fex : 621056 bytes @ +0x000029f400 wty:aultools.fex : 166515 bytes @ +0x0000337000 wty:aultls32.fex : 152069 bytes @ +0x000035fc00 wty:cardtool.fex : 73728 bytes @ +0x0000385000 wty:cardscript.fex : 1899 bytes @ +0x0000397000 wty:sunxi_gpt.fex : 8192 bytes @ +0x0000397800 wty:sunxi_mbr.fex : 65536 bytes @ +0x0000399800 wty:dlinfo.fex : 16384 bytes @ +0x00003a9800 wty:arisc.fex : 6 bytes @ +0x00003ad800 wty:vmlinux.fex : 12444168 bytes @ +0x00003adc00 wty:boot-resource.fex : 7490560 bytes @ +0x0000f8c000 wty:Vboot-resource.fex : 4 bytes @ +0x00016b0c00 wty:env.fex : 131072 bytes @ +0x00016b1000 wty:Venv.fex : 4 bytes @ +0x00016d1000 wty:boot.fex : 67108864 bytes @ +0x00016d1400 wty:Vboot.fex : 4 bytes @ +0x00056d1400 wty:vendor_boot.fex : 33554432 bytes @ +0x00056d1800 wty:Vvendor_boot.fex : 4 bytes @ +0x00076d1800 wty:super.fex : 1806382676 bytes @ +0x00076d1c00 wty:Vsuper.fex : 4 bytes @ +0x0073185400 wty:misc.fex : 16777216 bytes @ +0x0073185800 wty:Vmisc.fex : 4 bytes @ +0x0074185800 wty:vbmeta.fex : 8192 bytes @ +0x0074185c00 wty:Vvbmeta.fex : 4 bytes @ +0x0074187c00 wty:vbmeta_system.fex : 4096 bytes @ +0x0074188000 wty:Vvbmeta_system.fex : 4 bytes @ +0x0074189000 wty:vbmeta_vendor.fex : 4096 bytes @ +0x0074189400 wty:Vvbmeta_vendor.fex : 4 bytes @ +0x007418a400 wty:dtbo.fex : 2097152 bytes @ +0x007418a800 wty:Vdtbo.fex : 4 bytes @ +0x007438a800 @ 542: boot0: Allwinner boot0 size: 61440 bytes eGON checksum matches: 0x505a301a DRAM parameters: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1f12 0x1f12 PARA0 : - - 0x1 PARA1 : 0x1f12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0001002 0 TPR2 : 0 0 0xc0001002 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f1107 0x2f1107 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0001002 0xeddc7665 0xeddc7665 TPR13 : 0 0x40 0x40 DRAM parameters 1: A64 H616 A133 DRAM clock : 600 600 600 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c1a 0x1c1a PARA0 : - - 0x1 PARA1 : 0x1c1a 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc000130a 0 TPR2 : 0 0 0xc000130a TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc000130a 0xeddc6554 0xeddc6554 TPR13 : 0 0x40 0x40 DRAM parameters 2: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 3: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 4: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 5: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 6: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 7: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 8: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters 9: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters A: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters B: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters C: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters D: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40 DRAM parameters E: A64 H616 A133 DRAM clock : 648 648 648 DRAM type : 0x3 0x3 0x3 ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 0x3030303 DX DRI : - 0xe0e0e0e 0xe0e0e0e CA DRI : - 0x1c12 0x1c12 PARA0 : - - 0x1 PARA1 : 0x1c12 0x30fb 0x30fb PARA2 : 0x1 0 0 MR0 : 0x30fb 0x840 0x840 MR1 : 0 0x4 0x4 MR2 : 0x840 0x8 0x8 MR3 : 0x4 0 0 TPR0 : 0x8 0xc0000a05 0 TPR2 : 0 0 0xc0000a05 TPR6 : 0 0x33808080 0x33808080 TPR10 : 0 0x2f0006 0x2f0006 TPR11 : 0 0xddddcccc 0xddddcccc TPR12 : 0xc0000a05 0xeddc7564 0xeddc7564 TPR13 : 0 0x40 0x40

Sorry last message, need more test.

Ok, I think I got it. Tomorrow I will give a try, thanks. Mi box is the Transpeed M98 Plus by the way.

Ok, maybe I made a mistake before. I tried with an no secure-boot .img file and it give a long list of DRAM params and I put it in the file below. But I don't know What I can do with it... I will appreciate your help. Thanks. DRAM_Transpeed_M98txt

Thanks again @Nick A, I already did it, the file I got, cant understood well, and there are very low information about dram, just 3 params dram {phandle = <0x7a>;}; vcc-dram = <0x04>; dram = "/dram"; dtb.0.dts

Yes, maybe. There are a way to make a similar patch for kernel instread of u-boot? In Android, the boot logo show some parameters like DRAM_VCC, DRAM_CLK, Chip id, Param1, param2 and tpr113 , it helps? Tanks for your time. [626]HELLO! SBOOT is starting! [629]sboot commit : 4b34f2890a [632]set pll start [634]periph0 has been enabled [637]set pll end [641]unknow PMU [642]unknow PMU [646]PMU: AXP1530 [650]dram return write ok [653]board init ok [655]enable_jtag [656]DRAM BOOT DRIVE INFO: V0.651 [660]the chip id is 0x2000 [662]chip id check OK [684]DRAM_VCC set to 1500 mv [687]DRAM CLK =648 MHZ [689]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [697]Actual DRAM SIZE =4096 M [700]DRAM SIZE =4096 MBytes, para1 = 310b, para2 = 10000000, dram_tpr13 = 6041 [709]DRAM simple test OK. [711]rtc standby flag is 0x0, super standby flag is 0x0 [717]dram size =4096 [719]Use rtc to store dram tuning para [723][mmc]: mmc driver ver 2021-10-12 13:56 [727][mmc]: b mmc 2 bias 4 [735][mmc]: Wrong media type 0x0, but host sdc2, try mmc first [741][mmc]: ***Try MMC card 2*** [770][mmc]: RMCA OK! [773][mmc]: MMC 5.1 [775][mmc]: HSSDR52/SDR25 8 bit [778][mmc]: 50000000 Hz [780][mmc]: 119280 MB [782][mmc]: ***SD/MMC 2 init OK!!!*** [858]read toc1 from emmc 32800 sector [862]OLD version: 0.0 [864]NEW version: 0.0 [870]don't have rotpk, skip check [941]load rotpk hash [1204]load vbmeta_a-key hash [1207]load vbmeta_a hash [1214]load vbmeta_b-key hash [1217]load vbmeta_b hash [1220]monitor entry=0x48000000 [1223]uboot entry=0x4a000000 [1226]optee entry=0x48600000 [1229]opensbi entry=0x0 [1231]no need rotpk flag [1234]tunning data addr:0x4a0003e8 [1239]run out of boot0 NOTICE: BL3-1: v1.0(debug):54937d5 NOTICE: BL3-1: Built : 17:44:59, 2021-12-13 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V2.0 NOTICE: secure os exist MESSAGE: [0x0] TEE-CORE: OP-TEE version: 5c40397e #1 Tue Feb 2 07:45:37 UTC 2021 arm NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 U-Boot 2018.07-gb99798b4 (Apr 04 2023 - 13:23:26 +0000) Allwinner Technology [01.302]CPU: Allwinner Family [01.305]Model: sun50iw9 I2C: ready [01.313]DRAM: 4 GiB [01.322]Relocation Offset is: 70ecd000 [01.358]secure enable bit: 1 [01.360]smc_tee_inform_fdt failed with: ffffffff [01.365]pmu_axp152_probe pmic_bus_read fail [01.369]PMU: AXP1530 FDT ERROR:fdt_get_regulator_name:get property handle twi-supply error:FDT_ERR_INTERNAL [01.383]CPU=1416 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz

Yes, you already teach me how to make a patch to use secure boot and it works fine. Anyway, the ram patch didn't work. I build a new image now and it still shows only 2GB instead of 4GB. Maybe I miss a step to apply this patch?. The strange thing is that u-boot shows 4GB, than kernel shows 2GB in boot log. Even with a half of memory it works very well.

Hi @Nick A, sorry my late answer. I can't directly use your image, because my box is that boot-secure. I need to compile it every time I want to update, so my last build have about 4 months, but I think that time it just have a "new patch for dram" unless have a other new dram patch. Anyway, I'll try to build it again to try. If you have any additional tip to this, I'll appreciate. Thanks again for all your efforts.

@Alfi ciio, did you try to change the PRETTY_NAME on os-release file? It should be "Debian GNU/Linux 12 (bookworm)" to install HA Supervisor

Thanks @firepower, I have an Transpeed M98 with the same SP6330-X wifi-bluetooth chip and had the same problem as you had described. Now I just replace my original BCM4330B1.hcd by yours and now the Bluetooth worked like a charm. Now The only problem I still need to found a fix is my Ram memory that I just could use the half of 4GB that the box have.

Hi @Nick A. Sorry the late feedback, but I'm still test some things... Yes, I finally could boot Armbian with this image successfully. Almost everything worked fine Just Bluetooth and the memory size still bad. Desktop started OK; HDMI - image and sound - OK (Not in u-boot); Ethernet - OK; WIFI didn't work in beginning, because my chip is the sp6330, but I could make it to work following this tip: https://forum.armbian.com/topic/16696-armbian-for-tanix-tx3-amlogic-s905x3-with-sp6330-wifibluetooth-module/?do=findComment&comment=117066; Bluetooth still don't work. I see somewhere in this topic a tip about it, I'll look for it then; The box just recognize 2GB instead 4GB (In u-boot shows 4GB, but in system for some reason, just recognize 2GB); I could successfully install this image in internal EMMC with armbian-install and it works fine without the uSD inserted; Obs.: I cant update/upgrade the system, because it make the system stop working, so I freezed kernel upgrades and now I can update and upgrade without break the system. Thank for yours tips and efforts to help us.

Thanks again @Nick A. There are no kern.log file in /var/log, even in mini Arch that starts the kernel. Anyway, I will put here 3 files with consoles. A mini Arch with original transpeed dtb (UART_miniArch_transpeeddtb.txt), a mini Arch with yours armbian transpeed dtb (UART_miniArch_Nicks_transpeeddtb.txt) and an android logo of a functional rom(UART_Android_customROM.txt) (I changed the original one for this, because the original is an Android TV and this is a pure Android with root). UART_miniArch_transpeeddtb.txt UART_miniArch_Nicks_transpeeddtb.txt UART_Android_customROM.txt

Hi @Nick A. Thaks for new answer. I tried changing the verbosity=1 to 7, but the same problem. tried extraargs=debug initcall_debug as the link you posted, but none change, still stops in "Starting kernel ..." Yes. This is exactly the same as mine. my wifi chip is the SP6330. My board is exactly the same as @afiftyp posted in page 3 of this topic, but theirs is not with secure boot activated. As I understood, he could use Armbian with your image without modifications. Because of it I think that my problem is the demon of sunx secure boot. Any way, I'm very thank for the effort of all of you in help me.

Thanks for your reply @Nick A, but my bootlogo is already false. My armbianEnv.txt contents is the above: verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun50i-h616 rootdev=UUID=6de22aaf-f6c2-4ed0-9715-b931c3d7602d rootfstype=ext4 fdtfile=/allwinner/sun50i-h618-transpeed-8k618-t.dtb I extracted my android dts, but don't know what to do with it. I think there are a problem in boot armbian and boot secure, because some other with same M98 plus like mine told that theirs worked with your image untouched. Anyway I will attach my extracted dts file that is very similar than the one you posted here in page 5. Unfortunately I thik that I will have to give up to put Armbian in my Transpeed M98 plus. dtb.0.dts

Hi @kil, Thanks for your new information, but I just tried all dtb files in dtb folder, but with no sucess. Even with the new compilation that Nick posted in last massage. What I see was that with armbian, with any dtb file, it stops in "Starting kernel ..." and with miniarch the kernel ran, but stop with kernel panic. I tried with orangepi armbian with the transpeed dtb with same result than Nick's image. BTW, for any dont know, to change the dtb file that will be used you need to change the armbianEnv.txt and write in the end of the file a "fdtfile=" and the path for fdt filelike "fdtfile=/allwinner/sun50i-h618-transpeed-8k618-t.dtb" above is my uart with armbian: U-Boot 2024.07-rc5 (Jul 16 2024 - 11:41:56 -0300) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: Transpeed 8K618-T DRAM: 2 GiB Core: 59 devices, 21 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: No ethernet found. starting USB... Bus usb@5101000: USB EHCI 1.00 Bus usb@5101400: USB OHCI 1.0 Bus usb@5200000: USB EHCI 1.00 Bus usb@5200400: USB OHCI 1.0 scanning bus usb@5101000 for devices... 1 USB Device(s) found scanning bus usb@5101400 for devices... 1 USB Device(s) found scanning bus usb@5200000 for devices... 1 USB Device(s) found scanning bus usb@5200400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3259 bytes read in 2 ms (1.6 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 209 bytes read in 2 ms (101.6 KiB/s) 35515 bytes read in 7 ms (4.8 MiB/s) Working FDT set to 4fa00000 4203 bytes read in 6 ms (683.6 KiB/s) Applying kernel provided DT fixup script (sun50i-h616-fixup.scr) ## Executing script at 45000000 18349552 bytes read in 765 ms (22.9 MiB/s) 23572488 bytes read in 982 ms (22.9 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=41910000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 18349488 Bytes = 17.5 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 48e80000, end 49fffdb0 ... OK Loading Device Tree to 0000000048e0e000, end 0000000048e7ffff ... OK Working FDT set to 48e0e000 Starting kernel ...

Hi @Nick A, thanks for your answer. The @kil already give me the path in private massage (He tell me that for any reason his messages in here were not working). The step I skip was "At uboot build step "make menuconfig" I changed one option inside "ARM architecture" from "SPL Image Type (eGON (normal))" to "SPL Image Type (TOC0 (secure))"" that I think is the same as change the .config file and change CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y as you say. Now the u-boot is starting and give the wart logo. So I used your last image with this u-boot, but it stopped in "Starting kernel" I tried other images, some stopped in Kernel Panic others with some other errors, but none of them booted all the system. I still don't have HDMI image, but I see in your past messages that I have to put some patches in u-boot. I still don't know how to do it, but I'm still reading and trying. BTW I tried the miniArch that I had kernel panic or other error that I don't remember exactly. Best regards

Hi @kil, I have a Transpeed M98 with the same problem as yours T95H, this secure boot option, but different than you, I can't understood what to do in the links informed by Nick A. It's my fault, because I have a limitate knowledge in English. Can you help me with the exact steps you made to put the image to work in the SD card? Thanks in advance.

Thanks kajen for your reply. I read this Russian forum and tried boot with the firmware posted there burned with Phoenixcard without sucess. The Phoenix Usb and Phoenix suit didn't recognize my box, because none driver I tried work in my notebook. Tomorrow I'll try another computer or maybe with Linux. Anyway, I'm afraid of brick my box with it...

Thanks for fast reply. I already tried it. My box didn't boot over SD. I tried either boot with an Android burned in PhoenixCard_v4.2.7 and nothing happens. Maybe I got a box with some blocked firmware. The mine is An Android TV. I enabled developer options without problem and turned on the USB debugging. I could pull the dts files over adb as you teach, but cant boot over sd card or pen-drive. The SD is working and I could see it in Android and The Android could write its default folders in it. There are any way to change its boot order. Please, see my serial log attached With Armbian SD inserted and Without it I didn't see any important difference. SerialLog-SD_Armbian.txt SerialLog_AndroidWO SD.txt

Hi guys, first of all I want to thanks for Nike efforts and care with all people. I Bought a Transpeed M98 plus and need your help. usually don't ask questions in topics, because almost always just have the answer in already posted in past messengers, but I read all the topic and tried everything relative to my box, but cant boot over SD Card ou USB stick. If I power on my box pressing the bottom behind the P2 jack, The led is just red and no image in screen, In Uart there are none this way. If I boot no pressing the bottom, the Uart shows the logo, but doesn't appear the box try to boot from SD, it starts directly from internal memory. I had same problem in a RK322x box and solved it installing a new loader in it, but I see no similar thing for the Transpeed M98 Plus. I miss anything? You or other could help me with ant tips? P.S. I'm Brazilian, and my English is not so good, sorry any mistake.

Hello guys, first of all, I'd like to thank @jock for your very powerful work, very patient with all us newbies and thanks too @fabiobassa for your always fast answer. I have the R29 box that didn't run HDMI neither WI-FI, so I tested the new multiboot and the new minimal firmware and as the most people, it works flawlessly boting in pendrive, I could install in internal EMMC and everything is OK. So, to go ahead I tried to install the XFCE desktop environment in armbian-config, but wen I did it, the HDMI stopped working. The system still works behind the screen with my pi-hole server, but without Image in HDMI. I just see and it still in led7 option. There are anything I could do to try? Could a desmeg of my board help? Or is necessary both, before and after desktop installation to help? Any test could I do to help you guys to improve this firmware?