Nick A

@Sergioclr Try this one next. 159-add-x96-q-lpddr3-v1.3-defconfig.patch

@Sergioclr can you find a AXP chip on your board? It’s safer to boot images with the same AXP chip. I haven’t bricked any of my boxes. Don’t use armbian-config’s write to emmc until you have a stable image.

@Sergioclryou are only adding one line of code.. so whatever it is just add one. 162 would be 163.

@qq20739111 I'll add it soon. 6.18 might take awhile.

@HenricoLegal https://forum.armbian.com/topic/57960-sv6256p-wifi-now-working-on-linux-6x-armbian-tested/

@Sergioclr you can also try a newer branch https://github.com/NickAlilovic/build/tree/v20251014 https://github.com/NickAlilovic/build/tree/v20251014?tab=readme-ov-file#build-host-requirements

@Sergioclr Requirements for self hosted x86_64 / aarch64 machine at least 2GB of memory and ~35GB of disk space for VM, container or bare metal installation Armbian / Ubuntu Jammy 22.04.x for native building or any Docker capable Linux for containerised Windows 10/11 with WSL2 subsystem running Ubuntu Jammy 22.04.x Superuser rights (configured sudo or root access). Make sure your system is up-to-date! Outdated Docker binaries, for example, can cause trouble.

@Sergioclr the H313, H616, H618, and IK316 are essentially the same SoC family. To successfully boot an image, you must match the correct AXP chip (the Power Management IC) and the specific DRAM version used on your board. Essentially, any thread discussing the H616/H618 (excluding older H3/H5/H6 chips) will contain relevant information for these SoCs. PMIC Information: http://linux-sunxi.org/AXP_PMICs DRAM Types: 3: DDR3 4: DDR4 7: LPDDR3 8: LPDDR4 You can try flashing various boot images until one successfully initializes your hardware. (If your box is secure-boot enabled, you will need to add the secure-boot modifications posted above.) https://github.com/NickAlilovic/build/releases/tag/20250306 Alternatively, for a more precise approach: Extract your Device Tree (DTS). Identify the specific AXP chip located on your board. Connect a USB-to-UART TTL device to the RX, TX, and GND pins on your board to monitor the boot sequence. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-232411 https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/4/#findComment-187672 https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/page/23/#findComment-218660 https://linux-sunxi.org/UART Decompile your Device Tree Blob (DTB😞 dtc -I dtb -O dts -o source.dts source.dtb For a visual reference of a board using these specific chips, check out this hardware breakdown. http://nskhuman.ru/allwinner/krugh618.php?np=3

@Ducdanh Nguyen probably a real H313 SOC. You know this! You were on the other thread.

@HenricoLegal can you find the wifi chip on your board?

@mrdeathjr Mainline Linux support for the A733 is still in its early stages. I currently have a Armbian build using a collection of patches sourced from the kernel mailing lists. However, I’m getting a lot of errors and haven't managed to boot to a login prompt. https://oftc.catirclogs.org/linux-sunxi/2026-03-23 13:07 <indy> hi all, is there any a733 upstreaming effort? 13:29 <apritzel> indy: effort is underway: pinctrl is WIP (patches have been on the list), and the clock patches have recently been posted 13:30 <apritzel> RTC and AXP are on the list as well, that would conclude the basic necessities to get a DT merged that wouldn't break in the future 15:25 <indy> apritzel_, is it targeted for 7.0? 15:29 <apritzel> indy: no, that's way too late, v7.0 is due to be released in like three weeks already. It's even too late now for v7.1. 15:30 <apritzel> and it's the usual bottleneck: reviews ... I hope I find some time soon to look at the clock patches With @alexc hard work porting the v1.4.8 BSP driver to kernel 6.18, I was able to create a working Armbian build for the Radxa A7Z. https://github.com/NickAlilovic/build/tree/Radxa-mainline-WIP

@thanh_tan This looks like an AI-generated adaptation of my Radxa Cubie A7Z Armbian build. The Orange Pi 4 Pro uses the same Allwinner A733, so the family config is shared, but Radxa's BSP isn't directly compatible with the Orange Pi 4 Pro without board-specific modifications. Looking at the repo, it's very early stage — The write_uboot_platform() function is just a stub that does nothing, and it's relying on whatever bootloader is already on the SD card. I wouldn't expect it to actually boot on real hardware in its current state.

@Octavio Cuatrochio I just noticed your link in the first post. The board in the link is a FAKE Allwinner H313. If your board does not have a small AXP### chip then it's not an Allwinner H313.

@alexc Thanks for all your hard work! I’ve put together an Armbian build using your kernel—you can check it out here: https://github.com/NickAlilovic/build/tree/Radxa-mainline-WIP

@Mohammad Adel AW869A and AIC8800 are the same WiFI chips. You should have WiFi working.

@Mohammad Adel I need to know the physical WiFi and Ethernet chip model number on your board. If you can take a high resolution picture or just tell me the model number. https://openwrt.org/toh/xunlong/orange_pi_zero_3 is the closest model. But you need to edit the device tree. (dts) and u-boot defconfig.

@Mohammad Adel can you find the wifi chip on the board? Also Ethernet.

@Thur_Wander you don’t need 3.3v. Normally there’s a ground. You’ll need to find a ground. Maybe the outer surface of the usb port. Remember, the RX and TX have to be crossed. X

@Mohammad Adel There are differences like Ethernet and maybe WiFi. Lets see if the X98H boots first.

@Mohammad Adel Here are the steps to make a secure boot image. In your case you want to modify the X98H defconfig. git clone https://github.com/NickAlilovic/build.git --branch v20250306 cd build pico patch/u-boot/u-boot-h616/171-add-x98h-defconfig.patch You need to add this line to the bottom. "+CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" and change "@@ -0,0 +1,31 @@" to @@ -0,0 +1,32 @@. From 25669b44bab8ffdc4d07e140226c6385a9d13950 Mon Sep 17 00:00:00 2001 From: Nick Alilovic <nickalilovic@gmail.com> Date: Tue, 11 Mar 2025 22:09:15 -0400 Subject: [PATCH] add x98h defconfig add x98h defconfig --- configs/x98h_defconfig | 31 +++ .../src/arm64/allwinner/sun50i-h618-x98h.dts | 223 ++++++++++++++++++ 2 files changed, 254 insertions(+) create mode 100644 configs/x98h_defconfig create mode 100644 dts/upstream/src/arm64/allwinner/sun50i-h618-x98h.dts diff --git a/configs/x98h_defconfig b/configs/x98h_defconfig new file mode 100644 index 0000000000..b87498cd10 --- /dev/null +++ b/configs/x98h_defconfig @@ -0,0 +1,32 @@ +CONFIG_ARM=y +CONFIG_ARCH_SUNXI=y +CONFIG_DEFAULT_DEVICE_TREE="allwinner/sun50i-h618-x98h" +CONFIG_SPL=y +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 +CONFIG_MMC_SUNXI_SLOT_EXTRA=2 +CONFIG_R_I2C_ENABLE=y +# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set +CONFIG_SPL_I2C=y +CONFIG_SPL_I2C_SUPPORT=y +CONFIG_SPL_SYS_I2C_LEGACY=y +CONFIG_SYS_I2C_MVTWSI=y +CONFIG_SYS_I2C_SLAVE=0x7f +CONFIG_SYS_I2C_SPEED=400000 +CONFIG_PHY_REALTEK=y +CONFIG_SUN8I_EMAC=y +CONFIG_I2C3_ENABLE=y +CONFIG_SUPPORT_EMMC_BOOT=y +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 Then create the secure boot patch. pico patch/u-boot/u-boot-h616/secure-boot.patch 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 ./compile.sh choose "Do not change kernel configuration" choose "Show CSC/WIP/EOS/TVB" choose "I understand and agree" choose "X98H" choose "edge" rest is up to you. Your image should be in output/images directory.

@boggy have you tried another SD card? You have a lot of mmc errors. which miniarch image booted for you? Maybe we can use the mmc settings from that image.

@boggy do you have a boot log from armbian?

@boggy Try my Transpeed 8K618T image. It includes the most critical DTS settings for this hardware. All your Dram settings in the dts have dram_type = <0x03> or DDR3. dram_para1 { device_type = "dram_para1"; dram_clk = <0x258>; dram_type = <0x03>; cd-gpios = <&pio 8 16 GPIO_ACTIVE_LOW>; /* PI16 */ sdmmc@04020000 { compatible = "allwinner,sunxi-mmc-v4p1x"; device_type = "sdc0"; . . . cd-gpios = <0x53 0x08 0x10 0x06 0x01 0x03 0xffffffff>; can you find the wifi chip on your board?

@José Manuel Márquez Luque try these images https://github.com/NickAlilovic/build/releases/tag/20250306