Nick A

You can clone the original armbian build (git clone https://github.com/armbian/build.git), sicXnull build (git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch) or my build (git clone https://github.com/NickAlilovic/build.git --branch v20240918) SicXnull has the latest fixes for X96Q LPDDR3. If you want to use the 6.10 kernel with hdmi support I can modify the X96Q config on my build to include both current and edge kernels. git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-TVBOX-LPDDR3 --single-branch cd armbian-build ./compile.sh In the choose board menu click on "Show CSC/WIP/EOS/TVB" option then choose "x96q". Choose "current", "bookworm", server or desktop doesn't matter. Any desktop environment. Any software. (After the u-boot patches are applied and u-boot starts to build) ctrl C Create patches for u-boot: cd cache/sources/u-boot-worktree/u-boot/v2024.01 sudo git add . (For the first line patch title you can put "test" and the second line patch description put "test". Doesn't matter right now.) sudo git commit --signoff sudo pico configs/x96q_lpddr3_defconfig Add this line to your defconfig. CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y sudo openssl genrsa -out root_key.pem sudo git status sudo git add configs/x96q_lpddr3_defconfig sudo git add root_key.pem sudo git commit --signoff (Remember the first line patch title and the second line patch description.) sudo git format-patch v2024.01 Copy the patch to this armbian build directory. ~/build/patch/u-boot/u-boot-sunxi/ ./compile.sh Your new image should be in output/images directory.

Allwinner h618 (and maybe h626/h313) has an issue reading emmc during boot. The code is noway perfect. The read and write speeds go back to normal when the kernel is loaded. I guess we can add code to prevent other SOC’s from loading the code if not needed.

Can post your nand chip... maybe we can figure out the problem.

Do you have any info on what the problem might be?

Have you tried Miniarch's EMMC patch? https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/107-sunxi_mmc-dec-f_max-to-12MHz-to-get-emmc-reliable.patch

I edited the broadcom kernel drivers. /drivers/net/wireless/broadcom/brcm80211/include/brcm_hw_ids.h #define BRCM_CC_43342_CHIP_ID 43342 /drivers/net/wireless/broadcom/brcm80211/brcmfmac/sdio.c BRCMF_FW_DEF(43342, "brcmfmac43342-sdio"); BRCMF_FW_ENTRY(BRCM_CC_43342_CHIP_ID, 0xFFFFFFFF, 43342), I made a patch for you. Copy the patch to build/patch/kernel/archive/sunxi-6.9/patches.armbian directory. Edit build/patch/kernel/archive/sunxi-6.9/series.armbian and build/patch/kernel/archive/sunxi-6.9/series.conf to include the new patch. Then copy firmware files below to your sdcard. drivers-net-wireless-brcmfmac-add-43342-firmware.patch 43342_firmware.tar.gz

Can you open your box and take a picture of the wifi chip?

You need to edit these patches or create your own. Then add them to the armbian build. u-boot: https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/163-add-x96-q-ddr3-v5.1-defconfig.patch Linux Kernel: https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.10/files/0651-arm64-dts-allwinner-h313-add-x96q-v5.1-TVbox.patch

For Allwinner boxes you need to add this line to your u-boot defconfig. CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y To generate a TOC0 image from a binary, you will need an RSA key (pair) file. As most secure-boot enabled devices do not burn the VENDOR_ID eFUSE, you can use any RSA key, so just generate one, for instance with the openssl tool (would only need to be done once): openssl genrsa -out root_key.pem Your root_key.pem needs to be in the u-boot root directory.

Download these two firmware files and copy to /lib/firmware/brcm directory on your sdcard. https://github.com/LibreELEC/brcmfmac_sdio-firmware brcmfmac4334-sdio.bin brcmfmac4334-sdio.txt

https://github.com/warpme/minimyth2 close to to the bottom of the page. Allwinner H6 OrangePi-3 LTS not works (aw859a) Allwinner H616 OrangePi-Zero2 works (aw859a@SDIO) Allwinner H618 OrangePi-Zero3 works (uwe5622a@SDIO) I guess uwe5622 and aw859a are the same. OrangePi 3 LTS does not use SDIO. I'm pretty sure T95Z Plus does.

My transpeed image should boot on all the boxes you listed. X98H PRO: you need to edit the transpeed dts and change the gpio for mmc0. Android DTS. cd-gpios = <0x00000023 0x00000005 0x00000006 0x00000011>; Armbian/Linux DTS cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>; /* PF6 */ This shows a picture of the x96. I have the non-pro version of the X98H and I'm pretty sure it's a AIC8800 chip. http://nskhuman.ru/allwinner/x98hpro.php?np=3 you might have a hard time getting the AIC8800 driver for wifi to work. I haven't spent a lot of time on it. https://github.com/radxa-pkg/aic8800/tree/3.0%2Bgit20240327.3561b08f-2 I'm working on the 6.10 kernel right now. I'm going to release a custom dts for X98H when I'm done.

I see two different dram settings in your dtb. Not sure which is the correct one. Lets try the first one. You can edit the values in my u-boot defconfig patch. git clone https://github.com/NickAlilovic/build.git --branch v20240909 --single-branch cd build/patch/u-boot/u-boot-sunxi pico configs-Transpeed-8K618-T-Add-Transpeed-8K618-T-board-support.patch dram_para1 { device_type = "dram_para1"; dram_clk = <0x288>; dram_type = <0x03>; dram_dx_odt = <0x3030303>; dram_dx_dri = <0xe0e0e0e>; dram_ca_dri = <0x1c1c>; dram_odt_en = <0x01>; dram_para1 = <0x30fb>; dram_para2 = <0x00>; dram_mr0 = <0x840>; dram_mr1 = <0x04>; dram_mr2 = <0x08>; dram_mr3 = <0x00>; 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>; dram_tpr0 = <0xc0001305>; dram_tpr1 = <0x00>; dram_tpr2 = <0x00>; dram_tpr3 = <0x00>; dram_tpr6 = <0x33808080>; dram_tpr10 = <0x2f0006>; dram_tpr11 = <0xffffdddd>; dram_tpr12 = <0xfedf7657>; dram_tpr13 = <0x40>; }; dram { compatible = "allwinner,dram"; clocks = <0xd9>; clock-names = "pll_ddr"; dram_clk = <0x2b8>; dram_type = <0x08>; dram_zq = <0x3f3fdd>; dram_odt_en = <0xffffeeee>; dram_para1 = <0x30fa>; dram_para2 = <0x00>; dram_mr0 = <0x00>; dram_mr1 = <0x34>; dram_mr2 = <0x1b>; dram_mr3 = <0x33>; dram_tpr0 = <0x00>; dram_tpr1 = <0x00>; dram_tpr2 = <0x00>; dram_tpr3 = <0x00>; dram_tpr4 = <0x00>; dram_tpr5 = <0x00>; dram_tpr6 = <0x39808080>; dram_tpr7 = <0x00>; dram_tpr8 = <0x00>; dram_tpr9 = <0x00>; dram_tpr10 = <0x402f6663>; dram_tpr11 = <0x31313031>; dram_tpr12 = <0xd0d0c0e>; dram_tpr13 = <0x60>; linux,phandle = <0x17d>; phandle = <0x17d>; device_type = "dram"; dram_dx_odt = <0xc0c0c0c>; dram_dx_dri = <0xe0e0e0e>; dram_ca_dri = <0xe0b>; dram_mr4 = <0x03>; dram_mr5 = <0x00>; dram_mr6 = <0x00>; dram_mr11 = <0x04>; dram_mr12 = <0x72>; dram_mr13 = <0x00>; dram_mr14 = <0x09>; dram_mr16 = <0x00>; dram_mr17 = <0x00>; dram_mr22 = <0x24>; }; dram_clk = <0x288>; 288 hex = 648 https://www.rapidtables.com/convert/number/hex-to-decimal.html?x=288 It should be 8 or 4 digits. I added a 0 to the beginning of DX_ODT and DX_DRI. dram_dx_odt = <0x3030303>; CONFIG_DRAM_SUN50I_H616_DX_ODT=0x03030303 Change my defconfig to these values. +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x0c0c0c0c +CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x0e0b +CONFIG_DRAM_SUN50I_H616_TPR0=0xc0001305 +CONFIG_DRAM_SUN50I_H616_TPR10=0x2f0006 +CONFIG_DRAM_SUN50I_H616_TPR11=0xffffdddd +CONFIG_DRAM_SUN50I_H616_TPR12=0xfedf7657 Now you compile a new image. You will find the image in output/images. cd ../../../ ./compile.sh build BOARD=transpeed-8k618-t BRANCH=edge BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED=browsers DESKTOP_ENVIRONMENT=xfce DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base KERNEL_CONFIGURE=no RELEASE=bookworm cd output/images If your box is really LPDDR4. Then change these lines. +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x03030303 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x1f12 +CONFIG_DRAM_SUN50I_H616_TPR0=0xc0001002 +CONFIG_DRAM_SUN50I_H616_TPR10=0x2f1107 +CONFIG_DRAM_SUN50I_H616_TPR11=0xddddcccc +CONFIG_DRAM_SUN50I_H616_TPR12=0xeddc7665 +CONFIG_MACH_SUN50I_H616=y +CONFIG_SUNXI_DRAM_H616_DDR3_1333=y +CONFIG_DRAM_CLK=648 To +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x07070707 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x0e0e +CONFIG_DRAM_SUN50I_H616_ODT_EN=0xffffeeee +CONFIG_DRAM_SUN50I_H616_TPR6=0x402f6663 +CONFIG_DRAM_SUN50I_H616_TPR10=0x402f6663 +CONFIG_DRAM_SUN50I_H616_TPR11=0x31313031 +CONFIG_DRAM_SUN50I_H616_TPR12=0x0d0d0c0e +CONFIG_MACH_SUN50I_H616=y +CONFIG_SUNXI_DRAM_H616_LPDDR4=y +CONFIG_DRAM_CLK=696 Because you are adding another line of code @@ -0,0 +1,27 @@ should be @@ -0,0 +1,28 @@. Or you can follow these steps to create your own patch.

Had some time to update armbian and the linux kernel. If anyone wants to test my latest Armbian 24.11.0 with 6.9.12 kernel here are the links. https://github.com/NickAlilovic/build/releases/tag/v20240909 https://github.com/NickAlilovic/build/tree/v20240909

Your welcome Kazekami. If you have a working box. Make a board config. Post your board config, u-boot defconfig, u-boot dts and linux kernel dts. I can make a patch for you and add it to my build. It will help others with the same box as yours. https://github.com/NickAlilovic/build/blob/main/config/boards/transpeed-8k618-t.wip

H313/H616 is very similar to H618. If you read the H618 thread you might find some useful information.

Hi L Jumadi You need the correct defconfig for your u-boot. You can use sunxi-fw to extract your DRAM setup. https://github.com/apritzel/sunxi-fw You can use an android update firmware or your extracted boot0. Also, you can run a statically linked sunxi-fw on the boot block device from Android, like "sunxi-fw info -v /dev/block/mmcblk1", to dump the DRAM parameters (if you have root there) for example Orangepie zero 3 has lpddr4. CONFIG_DRAM_SUN50I_H616_DX_ODT=0x07070707 CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0e0e0e0e CONFIG_DRAM_SUN50I_H616_CA_DRI=0x0e0e CONFIG_DRAM_SUN50I_H616_ODT_EN=0xaaaaeeee CONFIG_DRAM_SUN50I_H616_TPR6=0x44000000 CONFIG_DRAM_SUN50I_H616_TPR10=0x402f6663 CONFIG_DRAM_SUN50I_H616_TPR11=0x24242624 CONFIG_DRAM_SUN50I_H616_TPR12=0x0f0f100f CONFIG_MACH_SUN50I_H616=y CONFIG_SUNXI_DRAM_H616_LPDDR4=y CONFIG_DRAM_CLK=792 You can get more information on your box by extracting your android dts. Sometimes you can find the dram settings in your dts.

Hi sicxnull I was looking at your DTS.. why is ehci0 and ohci0 disabled? &ehci0 { + status = "disabled"; +&ohci0 { + status = "disabled"; +}; For your internel emmc you probably have to set the correct gpio. Check your original android DTS see if it's setting PF6 or another gpio PI16. cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>; /* PF6 */ cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ Also, if you install to emmc you might need this u-boot patch to boot armbian. Not sure if the H313/H616 has the same emmc boot problems as H618. https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/107-sunxi_mmc-dec-f_max-to-12MHz-to-get-emmc-reliable.patch

Hi Hayat, I think you still need the brcmfmac4334-sdio.txt in the brcm folder. Right now it's called "brcmfmac4334-sdio.rockchip,rk3318-box.txt". The rockchip does the opposite and renames the .txt file instead of the .bin file. If you can post your boot log we can figure it out. You might have a different WIFI chip. For MMC it could be something simple or it could be your dts. There are differences in the Transpeed and Vontar dts settings. On the Transpeed box I have to set cd-gpios to PI16. +&mmc0 { + vmmc-supply = <&reg_dldo1>; + cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ + bus-width = <4>; + status = "okay"; +}; On the Vontar box this is set to broken-cd. You just need to change that one line in my u-boot and kernel .dts patches. +&mmc0 { + vmmc-supply = <&reg_dldo1>; + broken-cd; + bus-width = <4>; + status = "okay"; +}; git clone https://github.com/NickAlilovic/build.git edit these two files. ~/build/patch/kernel/archive/sunxi-6.7/patches.armbian/dts-allwinner-h618-add-Transpeed-8K618-T-TV-box.patch ~/build/patch/u-boot/u-boot-sunxi/dts-Transpeed-8K618-T-Add-Transpeed-8K618-T-board-support.patch ./compile.sh Not sure if you can still extract your original android dts. Your android dts can help figure out your gpio settings.

Hi Hayat, If you can boot Miniarch then you can boot Armbian. You just need to port over the vontar.dts and defconfig for u-boot and kernel from Miniarch to my Armbian build. I posted the steps in the previous page. I don't have a vontar box so I can't help you with testing. Plus I'm too busy with work right now. https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/160-add-vontar-h618-defconfig.patch https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.10/files/0647-arm64-dts-allwinner-h618-add-vontar-h618-TVbox.patch https://github.com/NickAlilovic/build

Hi kazekami, Try adding this to your .dts &ehci2 { status = "okay"; }; &ohci2 { status = "okay"; };

Hi Johan, Try the firmware from https://github.com/LibreELEC/brcmfmac_sdio-firmware brcmfmac4334-sdio.txt brcmfmac4334-sdio.bin Rename brcmfmac4334-sdio.bin to brcmfmac4334-sdio.transpeed,8k618-t.bin or create a link. copy the files into your /lib/firmware/brcm/ directory.

Hi Loong I would use the Ethernet code from Sipeed Longan 3H... this board uses a similar chip RTL8211F-CG. https://github.com/sipeed/LonganPi-3H-SDK/blob/main/linux/0001-arm64-dts-allwinner-h616-Add-Sipeed-Longan-SoM-3H-an.patch

I remember Jernej was working on better Ram detection. But I don't know if this will fix the kernel Ram detection. Maybe your Ram settings in your u-boot defconfig has something to do with it. You would have to extract your boot0 to get the correct Ram settings. I haven't found the fix for this issue yet. https://github.com/jernejsk/u-boot/commits/dram-fixes/ For Bluetooth, I would need to see the bluetooth errors in the boot log. Maybe your missing the bluetooth firmware, GPIO in the dts is the wrong number or for some reason Bluetooth on my transpeed box only works when I have bluetooth enabled in Android.

hv16.dts looks like the android dts. Can I have your armbian linux dts you are using right now? H618 soc suports two Ethernet devices.. emac0 uses external Ethernet chip. (Usually 1000/100Mbit ethernet) emac1 uses the internal PHY built in Ehternet inside H618 soc. (100Mbit ethernet) Orangepie zero2. (External Ethernet chip) aliases { mmc0 = &mmc0; mmc2 = &mmc2; ethernet0 = &emac0; ethernet1 = &wlan; serial0 = &uart0; }; &emac0 { allwinner,rx-delay-ps = <3100>; allwinner,tx-delay-ps = <700>; phy-mode = "rgmii"; phy-supply = <&reg_dcdce>; }; Transpeed and Vontar box. (H618 Ethernet inside H618 soc.) aliases { mmc0 = &mmc0; mmc2 = &mmc2; ethernet0 = &emac1; ethernet1 = &wlan; serial0 = &uart0; }; &emac1 { pinctrl-names = "default"; pinctrl-0 = <&rmii_pins>; phy-mode = "rmii"; phy-handle = <&rmii_phy>; phy-supply = <&reg_aldo1>; allwinner,rx-delay-ps = <3100>; allwinner,tx-delay-ps = <700>; status = "okay"; }; &mdio1 { rmii_phy: ethernet-phy@0 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0>; }; }; You might have to compile your kernel with RTL8211f support. Not sure if the option is already selected. Remember both u-boot and kernel dts needs these changes.