Nick A

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.

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.