Nick A

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.

Can you take pictures of your board.. maybe we can figure out which chip your box uses for Ethernet. Also, can you post your boot logs. https://linux-sunxi.org/Ethernet

If you are using v20240725 build... Delete patch/u-boot/u-boot-sunxi/opizero3-1.5GB-trim-from-u-boot-v2024.01.patch It's causing boot issues on my transpeed box.

BRANCH=current 6.6 Use the edge kernel. 6.7 ./compile.sh build BOARD=transpeed-8k618-t BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=bookworm

You can use my build and instructions above to create an armbian image using miniarch’s vontar dts and defconfig. U-boot https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/160-add-vontar-h618-defconfig.patch Kernel https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.10/files/0647-arm64-dts-allwinner-h618-add-vontar-h618-TVbox.patch

Hi Kazekami, It's not so simple. First you would need a working DTS and u-boot defconfig for your box. You can use mine and modify it with your box settings. OrangePi-Zero2 uses the same wifi/bt aw859a chip. You can borrow code off that board to get WIFI to work. https://github.com/orangepi-xunlong/linux-orangepi/blob/orange-pi-6.1-sun50iw9/arch/arm64/boot/dts/allwinner/sun50i-h616-orangepi-zero2.dts https://github.com/warpme/minimyth2/blob/master/script/kernel/linux-6.10/files/0641-arm64-dts-allwinner-h616-OrangePI-Zero23-enable-ths-hdmi-audio.patch Your GPIO might be a different value. You can find the correct settings in your android dts. "reset-gpios = <&pio 6 18 GPIO_ACTIVE_LOW>; /* PG18 */" reg_vcc33_wifi: vcc33-wifi { /* Always on 3.3V regulator for WiFi and BT */ compatible = "regulator-fixed"; regulator-name = "vcc33-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; vin-supply = <&reg_vcc5v>; }; reg_vcc_wifi_io: vcc-wifi-io { /* Always on 1.8V/300mA regulator for WiFi and BT IO */ compatible = "regulator-fixed"; regulator-name = "vcc-wifi-io"; regulator-min-microvolt = <1800000>; regulator-max-microvolt = <1800000>; regulator-always-on; vin-supply = <&reg_vcc33_wifi>; }; wifi_pwrseq: wifi-pwrseq { compatible = "mmc-pwrseq-simple"; clocks = <&rtc 1>; clock-names = "osc32k-out"; reset-gpios = <&pio 6 18 GPIO_ACTIVE_LOW>; /* PG18 */ post-power-on-delay-ms = <200>; }; . . . &mmc1 { vmmc-supply = <&reg_vcc33_wifi>; vqmmc-supply = <&reg_vcc_wifi_io>; mmc-pwrseq = <&wifi_pwrseq>; bus-width = <4>; non-removable; mmc-ddr-1_8v; status = "okay"; }; You would need to create patches for your box. Make your changes to both u-boot and kernel sun50i-h618-transpeed-8k618-t.dts. git clone https://github.com/NickAlilovic/build.git cd build ./compile.sh In the choose board menu click on "Show CSC/WIP/EOS/TVB" option then choose "transpeed-8k618-t". Choose "bleeding edge", "bookworm", server or desktop doesn't matter. Any desktop environment. Any software. (After the kernel patches are applied and kernel starts to build) ctrl C Create patches for u-boot: cd cache/sources/u-boot-worktree/u-boot/v2024.01 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.) git commit --signoff pico arch/arm/dts/sun50i-h618-transpeed-8k618-t.dts git status git add arch/arm/dts/sun50i-h618-transpeed-8k618-t.dts git commit --signoff (Remember the first line patch title and the second line patch description.) git format-patch -1 Create patches for kernel: cd ~/build/cache/sources/kernel-sunxi64-6.7/ 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.) git commit --signoff pico arch/arm64/boot/dts/allwinner/sun50i-h618-transpeed-8k618-t.dts git status git add arch/arm64/boot/dts/allwiner/sun50i-h618-transpeed-8k618-t.dts git commit --signoff (Remember the first line patch title and the second line patch description.) git format-patch -1 Patch directories: u-boot ~/build/patch/u-boot/u-boot-sunxi/ kernel ~/build/patch/kernel/archive/sunxi-6.7/patches.armbian/ Kernel patches config ( mines (-) before the patch name disables the patch) Add your new kernel patch to the bottom of these two files. ~/build/patch/kernel/archive/sunxi-6.7/series.armbian ~/build/patch/kernel/archive/sunxi-6.7/series.conf Armbian board config: # Allwinner H618 quad core 4GB RAM SoC WiFi USB BOARD_NAME="Transpeed 8k618-t" BOARDFAMILY="sun50iw9" BOARD_MAINTAINER="Nick A" BOOTCONFIG="transpeed-8k618-t_defconfig" OVERLAY_PREFIX="sun50i-h616" BOOT_LOGO="desktop" KERNEL_TARGET="current,edge" FORCE_BOOTSCRIPT_UPDATE="yes" function post_family_tweaks__station_m2() { display_alert "$BOARD" "Installing board tweaks" "info" cp -R $SRC/packages/blobs/station/firmware/brcm/* $SDCARD/lib/firmware/brcm return 0 } If you need to add wifi or bluetooth firmware. Add your firmware to /build/packages/blobs/station/firmware and make changes to the bottom copy command. pico ~/build/config/boards/transpeed-8k618-t.wip Firmware for aw859a chip may already be in the armbian build. https://github.com/warpme/minimyth2/blob/master/script/firmware/aw859a-firmware/Makefile

sorry latest armbian 24.8.0 release removed until I find out why HDMI doesn't work without a serial console attached to the uart. Edit: removing patch/u-boot/u-boot-sunxi/opizero3-1.5GB-trim-from-u-boot-v2024.01.patch fixes the problem.

Do you have a log for the Armbian build? If you don't have a serial console you can find it on the sdcard.

What's the name of the box? Try one of these images. (except the secure boot.) https://github.com/NickAlilovic/build/releases/tag/v20240716

I created a patch using my Armbian build. If you want to compile an image yourself you need to copy this patch into the /build/patch/u-boot/u-boot-sunxi folder. Here's an image you can test. https://github.com/NickAlilovic/build/releases/download/v20240716/Armbian-20240716-unofficial_24.5.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_xfce_desktop_Secure_Boot.img.tar.xz configs-Transpeed-8K618-T-Add-Transpeed-Secure-Boot.patch From fc6da5681853bdf61ef403dd47a8bc9e5451a6d7 Mon Sep 17 00:00:00 2001 From: Nick Alilovic <nickalilovic@gmail.com> Date: Tue, 23 Jul 2024 00:45:46 -0400 Subject: [PATCH 1/1] configs: Transpeed-8K618-T: Add Transpeed Secure Boot Add Secure Boot Signed-off-by: Nick Alilovic <nickalilovic@gmail.com> --- configs/transpeed-8k618-t_defconfig | 1 + root_key.pem | 28 ++++++++++++++++++++++++++++ 2 files changed, 29 insertions(+) create mode 100644 root_key.pem diff --git a/configs/transpeed-8k618-t_defconfig b/configs/transpeed-8k618-t_defconfig index ef7559bf68..5e65c2fa72 100644 --- a/configs/transpeed-8k618-t_defconfig +++ b/configs/transpeed-8k618-t_defconfig @@ -29,3 +29,4 @@ CONFIG_AXP313_POWER=y CONFIG_AXP_DCDC3_VOLT=1360 CONFIG_USB_EHCI_HCD=y CONFIG_USB_OHCI_HCD=y +CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y diff --git a/root_key.pem b/root_key.pem new file mode 100644 index 0000000000..892a10ef90 --- /dev/null +++ b/root_key.pem @@ -0,0 +1,28 @@ +-----BEGIN PRIVATE KEY----- +MIIEvgIBADANBgkqhkiG9w0BAQEFAASCBKgwggSkAgEAAoIBAQCWZ7G39E+RCi+9 +B48yiD4GxnfqNzvlXOxAd+GHQuKbgynXZd5pIuNHt3ewhZTHZkdHxuO9liqX9MmU +8OhiG+Skww2LzHPPi/eLeN4vCt/waXkjFrkblkhNzB3c6MejKdiz9sfw8oeOFX1S +teP/MJBoRaj6Hexj5g/oCspU+KFfv0cOBcWuq4vZwPJ6+U44IBi7EGleShGHNhBI +xQEyvNaDLWoDCPGLrjRM0DrIbUpzEntk9KJ0z+3Th8O/FtvlW21atolIVr5F96Pw +EEv3CDUHrY+IvK0z+IwNhnYo99kMPi5djB6vviz4In530JQ+OdPxhi4cQY3Yw9wx +Sm8EFaRRAgMBAAECggEAEaEcZ+k7VU8aGuBStNPa31zui9XHD8KlT4YtuXbJzHwi +kKSYXf7woISdAyQZNQkkREHICn4aRn7zDOHy/yLxWS2ivhbsITDxBlhXxLBT4OBg +ClCcyGLEXVgWTQE8+z9Jrwh3VaL76BfVPXdj/tKwroQxwwV0Yp5CEYsIPc75zVjW +Y2tppJL9XlTfKXTSo7FAxJmjkTC8QGPSHgMglR5FOfZ/D3Nj4KV4LV1gHCkICKUy +c2jklHISy8S6/pvgpWb50TKArEhbN6uAKQBNb74ZsChKJ9h9aof/vjH/8Ab1rwUJ +g91lpkR3mEefTjJTW1JOuoT49Y3lfWmkRVh75GiCsQKBgQDUo3uMcy9VdbbmY9Gt +2JuhbSvwR/dOHZJoXvtlNYVJ+1JvavExBy2u31cYsK/2SH/Upc8AXS6H02dXbnC3 +wjlUFi21Xi7/PCQM8TUz05km3+9qOkDYw53EBBBnCdjawBpDgcUSkoZGU+ltBzcR +sj0nsmI29DjwfYHXhofnlfI52QKBgQC1E2Q0hGfk3YUtfzTjDJCfd3gs6QYGQGeT +49jvnsbYsnz9vsK4Ao2skN8nBhSefDJR8h2X+7tRXEefQB2Hy/+9qoiuoVzPJGWD +IiHjeVJDoEqA2Q483UhZ+OPjUGFDTI7O/j1A1HkEBKswdJpKlGVygdoXYaieUAfz +Sb+dCYf7OQKBgQCWkE/aSnE4vQpOJl4BEABbFFdpYzvcpxnVJ3Qw3O3NTdS4Keww +wBl72o7sX6eo5vsE0oc5hcF90ZY6FWxg4XkAblfdNZxng+ku9NisIuct3KDFAgyK +sDCU7B/FJfbUJfQy2r91gCTtxVripZo7wI6G/kuHB/UNbIE04AB5XfZPOQKBgAGw +K5f9wAY3Nn2lGPYg8Nw7vegVSBQY155eWnBpd4sfpuCqvZ//jhiUxS/U865ClCmF +a1c2ZpmslZJbg6r3cOvwwhN2t6nKuhON5uj7AZRV0zv+Sg6xNXJ5So6c+jspZI9z +eVi4YmRyMrJh8+pMFeIKaeEb7PmE334aKuoo45apAoGBAKNp7ssXgU4Ma7cUr7+L +TKGBNVsMZyM3T2qsXJjFY1f90+lwp7TlNQGVMPOSOHxyINWkuLNgAgetlhavnc0S +0l+SbSaO6SfnHfQWBFPEJfol8V/Xa4rcVP7fGxQn4phYnk14N09xKIQa24Mi2Xa5 +9G0C2VOB8Yz6OWcQZELs0uFp +-----END PRIVATE KEY----- -- 2.34.1

I noticed my transpeed dts booted further without kernel panics. Does the log stop at "[ 1.577046] sun50i-h616-pinctrl 300b000.pinctr" ? I guess the other transpeed dts is the one that came with mainline u-boot? I think the only difference between the two is the Ethernet patch. The first patch adds Ethernet to transpeed dts. Other two edits u-boot source code to support the SOC on chip Ethernet phy called AC300. https://github.com/NickAlilovic/build/tree/main/patch/u-boot/u-boot-sunxi dts-Transpeed-8K618-T-Enable-Ethernet.patch 100-sunsi-add-h616-internal-eth-phy-support.patch 106-Add-int-phy-eth-H313-h616-with-AC300.patch U-boot log should show "apply fix for AC300 ephy bb version bug ..." when these patches are applied. I also noticed your Kernel only show's 2 GiB Dram. I think you are missing a patch to fix this problem. Last time I used MiniArch.. I was able to boot using the Vontar image. I didn't make any changes. Of course you probably need to change miniarch's Vontar u-boot with secure boot option. https://github.com/warpme/miniarch/releases/download/v20240715/MiniArch-20240715-6.10.0-board-h618.vontar_h618-SD-Image.img.xz The mainline u-boot you are using might not be compatible with warpme's build. I think you are missing some of the patches (for example the Ethernet and Dram fixes). The transpeed dts file might not be compatible because the sun50i-h616.dtsi might be different. These are the patches warpme uses for h616 u-boot.. https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/Makefile https://github.com/warpme/minimyth2/tree/master/script/bootloaders/u-boot-h616/files Apply these patches to mainline u-boot and add "CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" to "/2024.01-rc3/configs/vontar_h618_defconfig" Compile u-boot with Vontar dts. The only change to miniarch vontar u-boot should be "CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y".

Changing the verbosity to 7 worked on my box. Maybe your serial /dev/ttyS0 is different. Can't really do much without kernel messages. You can access your /armbi_root/var/log/kern.log from the SD card using your PC.

Try changing the verbosity=1 to 7. Or you can try this to get more debug information. Some DTS would show the dram settings. This one doesn't. Is this your box? https://androidpctv.com/firmware-m98-8k-plus/ This firmware shows the same dram settings as the 8K618-T rick0cm has a transpeed 8K618-T like mine but with a different wifi chip. Not all boxes are the same. The firmware above might be for M98 plus without secure boot. Maybe with different Ram chips. It would be better to extract your boot0 partition and figure out your dram settings. One last thing before you quit. I just want to see the kernel errors you are getting. You could be right about the secure boot being the problem. You can always ask for help at #linux-sunxi IRC https://oftc.irclog.whitequark.org/linux-sunxi/2024-07-19

Something changed when loading the kernel.. It's not showing the output to your serial console. I'm pretty sure it's due to "plymouth.ignore-serial-consoles" in your /armbi_root/boot/boot.cmd if test "${bootlogo}" = "true"; then setenv consoleargs "splash plymouth.ignore-serial-consoles ${consoleargs}" edit /armbi_root/boot/armbianEnv.txt change bootlogo=true to bootlogo=false Kernel panic could be due to incorrect Dram settings. Try extracting your Android boot_a.img, vendor_boot_a and dtbo_a. Instructions at the bottom of this page. You can also use https://github.com/apritzel/sunxi-fw to extract the dram settings. If you can find a firmware update for you box.

There seems to be an issue with 6.6 kernel current build. I would stick with 6.7 kernel edge build for now. Most of the miniarch patches are applied to the 6.7 kernel anyways. I'll create a few binaries and upload them online if anyone needs it. https://github.com/NickAlilovic/build/releases/tag/v20240716

Last I heard about the H713 chip it was still in early development. https://oftc.irclog.whitequark.org/linux-sunxi/2024-03-29

Hey Rick, Try using the ddbr command to backup your emmc . I added a patch to boot off emmc I got from MiniArch. I haven't tried it yet personally. Too busy with work. But someone posted a while back that it works.

I haven''t done this before but I think you need to follow these instructions to compile u-boot with TOC0 support. I'm guessing the deconfig needs "CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y". https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/configs-Transpeed-8K618-T-Add-Transpeed-8K618-T-board-support.patch You probably want to change the makeimage command to option "-A arm64" https://linux-sunxi.org/TOC0#TOC0_images_generation Here's more information on building u-boot https://linux-sunxi.org/U-Boot

Looking at your Android DTS for sdc0. cd-gpios = <0x00000053 0x00000008 0x00000010 0x00000006 0x00000001 0x00000003 0xffffffff>; I'm pretty sure your Linux DTS for mmc0 should be. cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ Not sure why there's so many hex numbers. But looking at Pine64 Android DTS for sdc0. https://github.com/ayufan-pine64/device-pine64-common/blob/master/bootloader/pine64/sun50i-a64-pine64-plus.dts cd-gpios = <0x00000030 0x00000005 0x00000006 0x00000000 0x00000001 0x00000002 0xffffffff>; Linux DTS for mmc0 shows. https://github.com/torvalds/linux/blob/master/arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>; Remember to add these changes to both your u-boot and linux DTS.

I think your problem has to do with boot rom security. Here's some links that might help. https://linux-sunxi.org/TOC0 https://linux-sunxi.org/Jide_Remix_Mini#Tips.2C_Tricks.2C_Caveats

I just got a X98H. It has the same problem. I was able to extract the Android dts. I found the stock firmware for the box. https://chinagadgetsreviews.com/download-android-12-stock-firmware-for-x98h-tv-box-2.html Using Apritzel's sunxi firmware extraction tool. https://github.com/apritzel/sunxi-fw nick@nick-Inspiron-5680:~/sunxi-fw$ ./sunxi-fw info -v X98H-20221020-1143.img @ 0: wty: PhoenixSuite image file header v3.0, 45 images, 1898 MB wty:sys_config.fex : 34908 bytes @ +0x0000b800 wty:board.fex : 1024 bytes @ +0x00014400 wty:config.fex : 53248 bytes @ +0x00014800 wty:split_xxxx.fex : 512 bytes @ +0x00021800 wty:sys_partition.fex : 5601 bytes @ +0x00021c00 wty:sunxi.fex : 71168 bytes @ +0x00023400 wty:boot0_nand.fex : 61440 bytes @ +0x00034c00 wty:boot0_sdcard.fex : 61440 bytes @ +0x00043c00 wty:u-boot.fex : 884736 bytes @ +0x00052c00 wty:u-boot-crash.fex : 37 bytes @ +0x0012ac00 wty:toc1.fex : 8 bytes @ +0x0012b000 wty:toc0.fex : 8 bytes @ +0x0012b400 wty:fes1.fex : 40160 bytes @ +0x0012b800 wty:boot_package.fex : 1261568 bytes @ +0x00135800 wty:usbtool.fex : 154112 bytes @ +0x00269800 wty:usbtool_crash.fex : 621056 bytes @ +0x0028f400 wty:aultools.fex : 166515 bytes @ +0x00327000 wty:aultls32.fex : 152069 bytes @ +0x0034fc00 wty:cardtool.fex : 73728 bytes @ +0x00375000 wty:cardscript.fex : 1899 bytes @ +0x00387000 wty:sunxi_gpt.fex : 8192 bytes @ +0x00387800 wty:sunxi_mbr.fex : 65536 bytes @ +0x00389800 wty:dlinfo.fex : 16384 bytes @ +0x00399800 wty:arisc.fex : 6 bytes @ +0x0039d800 wty:vmlinux.fex : 12619923 bytes @ +0x0039dc00 wty:boot-resource.fex : 7490560 bytes @ +0x00fa7000 wty:Vboot-resource.fex : 4 bytes @ +0x016cbc00 wty:env.fex : 131072 bytes @ +0x016cc000 wty:Venv.fex : 4 bytes @ +0x016ec000 wty:boot.fex : 67108864 bytes @ +0x016ec400 wty:Vboot.fex : 4 bytes @ +0x056ec400 wty:vendor_boot.fex : 33554432 bytes @ +0x056ec800 wty:Vvendor_boot.fex : 4 bytes @ +0x076ec800 wty:super.fex : 1847555340 bytes @ +0x076ecc00 wty:Vsuper.fex : 4 bytes @ +0x758e4400 wty:misc.fex : 16777216 bytes @ +0x758e4800 wty:Vmisc.fex : 4 bytes @ +0x768e4800 wty:vbmeta.fex : 8192 bytes @ +0x768e4c00 wty:Vvbmeta.fex : 4 bytes @ +0x768e6c00 wty:vbmeta_system.fex : 4096 bytes @ +0x768e7000 wty:Vvbmeta_system.fex : 4 bytes @ +0x768e8000 wty:vbmeta_vendor.fex : 4096 bytes @ +0x768e8400 wty:Vvbmeta_vendor.fex : 4 bytes @ +0x768e9400 wty:dtbo.fex : 2097152 bytes @ +0x768e9800 wty:Vdtbo.fex : 4 bytes @ +0x76ae9800 @ 542: boot0: Allwinner boot0 size: 61440 bytes eGON checksum matches: 0xbf64ad3a DRAM parameters: A64 H616 DRAM clock : 0x288 0x288 - DRAM type : 0x3 0x3 - ZQ value : 0x3030303 - - ODT enabled : 0xe0e0e0e 0x1 - DX ODT : - 0x3030303 - DX DRI : - 0xe0e0e0e - CA DRI : - 0x1f12 - PARA1 : 0x1f12 0x30fb - PARA2 : 0x1 0 - MR0 : 0x30fb 0x840 - MR1 : 0 0x4 - MR2 : 0x840 0x8 - MR3 : 0x4 0 - TPR0 : 0x8 0xc0001002 - TPR6 : 0 0x33808080 - TRP10 : 0 0x2f1107 - TRP11 : 0 0xddddcccc - TRP12 : 0xc0001002 0xeddc7665 - TRP13 : 0 0x40 - The Dram settings where the same so I didn't have to edit the U-boot patch. https://github.com/NickAlilovic/build/blob/main/patch/u-boot/u-boot-sunxi/configs-Transpeed-8K618-T-Add-Transpeed-8K618-T-board-support.patch +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 My 8K618-T image won't work because these values were different. MMC errors means your box won't boot past U-boot and load a kernel. So you won't get hdmi output, no sound, no wifi, no bluetooth. This is why it's important to have uart installed. X98H mmc: Android dts cd-gpios = <0x23 0x05 0x06 0x11>; Armbian dts cd-gpios = <&pio 5 6 GPIO_ACTIVE_LOW>; /* PF6 */ 8K618-T mmc: Android dts cd-gpios = <0x23 0x08 0x10 0x11>; Armbian dts cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ U-Boot SPL 2024.01-armbian (May 09 2024 - 19:55:37 -0400) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.10.2(debug):armbian NOTICE: BL31: Built : 19:53:26, May 9 2024 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0a0648, model: Transpeed 8K618-T 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 2024.01-armbian (May 09 2024 - 19:55:37 -0400) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: Transpeed 8K618-T DRAM: 2 GiB Core: 61 devices, 22 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... MMC: no card present ** Bad device specification mmc 0 ** In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: apply fix for AC300 ephy bb version bug ... using AC300 emac1 ephy fixed config ... eth0: ethernet@5030000 starting USB... Bus usb@5101000: sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus 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 Autoboot in 1 seconds, press <Space> to stop MMC: no card present switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... MMC: no card present No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image Device 0: unknown device ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-00-70-41-af-ea ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00000000 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0000000 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/000000 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00000 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0000 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/000 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! A quick and easy way to fix this is to edit the one line in my patch. (Or whatever device dts patch that worked for you) https://github.com/NickAlilovic/build/blob/main/patch/kernel/archive/sunxi-6.7/patches.armbian/arm64-dts-allwinner-h618-add-Transpeed-8K618-T-TV-box.patch +&mmc0 { + vmmc-supply = <&reg_dldo1>; + cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ + bus-width = <4>; + status = "okay"; +}; If you need to add more lines then you would have follow my instructions at the bottom of page 2. (Note: the branch names may of changed "linux-6.7.y" and "v2024.01" for the format-patch command. Use "git branch --show-current" for the new branch name.) You can't just add an Android DTS and hope it works. There's been a lot of changes to the linux kernel since than. You need to port the values to the latest Mainline kernel code. You can find examples here. (Look for DTS in patch file name. 0647-arm64-dts-allwinner-h618-add-vontar-h618-TVbox.patch) https://github.com/torvalds/linux/tree/master/arch/arm64/boot/dts/allwinner https://github.com/warpme/minimyth2/tree/master/script/kernel/linux-6.9/files https://github.com/NickAlilovic/build/tree/main/patch/kernel/archive/sunxi-6.7/patches.armbian

If there's a kernel or u-boot update then your box won't boot. The kernel and u-boot need patches from my repository for it to work on your box. There are no apt packages for this. I guess you need to burn another sdcard and start from scratch.

Do you have a TV with hdmi port? Maybe these links can help. https://forums.raspberrypi.com/viewtopic.php?t=353936&start=50 https://forums.raspberrypi.com/viewtopic.php?t=24679&start=225

well you have something to work with... use the manjaro dtsi and the dts that worked

Have your tried another monitor?