Nick A

Hi @lynya5 Can you test the server images and let me know which version works for you. Edit: Never mind.. I had time so I compiled ubuntu xfce for all 4 x96q versions. Remember you have a custom kernel. You need to block kernel updates with the armbian config tool.

@Silv3r_18 Change the armbianEnv.txt log level to 7 on your sdcard. Try to boot again.

Maybe this is the problem? https://discourse.ubuntu.com/t/mount-root-proc-cannot-mount-proc-read-only-with-lxd-5-21-2-22f93f4-from-snap/47533/1

AXP806 is the same as AXP305. https://linux-sunxi.org/AXP_PMICs Try the X96Q DDR3 image above. I see you already have your serial adaptor installed. Can you post your boot logs here?

Do you have a pictures of your board? Can you find the version of your AXP CHIP? If it's AXP305 then this might work. https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-ddr3_bookworm_edge_6.12.11_server.img.xz If not try these https://github.com/NickAlilovic/build/releases/tag/20250306

If anyone wants to test my Armbian unofficial build using the latest Armbian 25.05.0 build, Kernel 6.12.11 and miniarch patches. I compiled all 4 versions of X96Q. If you need secure boot or desktop build let know. This is a work in progress so I might be updating the build often. Images: https://github.com/NickAlilovic/build/releases/tag/20250306 Sources: git clone https://github.com/NickAlilovic/build.git --branch v20250329 Remember you have a custom kernel. You need to block kernel updates with the armbian config tool.

If anyone wants to test my Armbian unofficial build using the latest Armbian 25.05.0 build, Kernel 6.12.11 and miniarch patches. I compiled all 4 versions of X96Q. If you need secure boot or desktop build let know. This is a work in progress so I might be updating the build often. Images: https://github.com/NickAlilovic/build/releases/tag/20250306 Sources: git clone https://github.com/NickAlilovic/build.git --branch v20250306

Hi fefpi H313 is the same as H616. You need to test images with H616 and AXP305. Here are some boards with source code that might work. Sorry you'll have to wait until the new images are released. There's a DRAM bug in the latest images. v13.9.1 U-Boot SPL 2025.01 (Feb 06 2025 - 15:11:12 +0100) DRAM: x96q ddr3 (axp313a version will not work) MiniMyth2-armv8-master-xxxxxxx-board-h313.x96_q-SD-Image.img.xz https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/151-add-x96-q-ddr3-defconfig.patch tanix-tx6s (axp313a version will not work) MiniMyth2-armv8-master-xxxxxxxxx-board-h616.tanix_tx6s-SD-Image.img.xz https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/152-add-tanix-tx6s-defconfig.patch

Hey Mark, Good job on the LED Display. When I have time I'll give Jean-Francois alternative module a try. I haven't played with the remote yet. Here's a post from the H618 thread that might help you.

I'm busy with another build but If anyone wants to send a PR? I don't think sicxnull would mind. A lot of the source comes from Warpme's Minimyth2 patches. https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/150-add-x96-q-lpddr3-defconfig.patch https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/151-add-x96-q-ddr3-defconfig.patch https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/159-add-x96-q-lpddr3-v1.3-defconfig.patch https://github.com/warpme/minimyth2/blob/master/script/bootloaders/u-boot-h616/files/163-add-x96-q-ddr3-v5.1-defconfig.patch Sicxnull already sent a PR for "X96Q-TVBOX-LPDDR3" branch back in august. https://github.com/armbian/build/pull/7101 Clone the Official Armbian build then add Sicxnull/Warpme changes. Send a PR.

Try building an image using sicXnull's branch. git clone https://github.com/sicXnull/armbian-build.git --branch X96Q-5.1-DDR3 --single-branch Patch directory is. patch/u-boot/u-boot-sunxi/board_x96q-v5-1 He also has a branch called "X96Q-TVBOX-LPDDR3"

Did press & hold the reset button (in the AV port) before you apply power? Try using another SDcard.

Do you see UART messages booting Android? If not then maybe it’s a problem with the UART connections. Are your RX and TX connections swapped? Use BelenaEtcher to write your images.

I think this patch will apply cleanly if you put it in the "patch/u-boot/u-boot-sunxi/board_x96q" folder. No need to add "CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y" the patch already does this for you. The "configs" folder is located in the u-boot source directory. You can find it in the armbian build "cache/sources" folder. You won't see the cache folder until you start a build. The armbian build scripts will use git to clone the u-boot sources into "cache/sources" folder. This is why the armbian build system has a patch directory. It uses these patches to overwrite source files located in your cache folder. If you wanted to create your own patch you would go into the cache and edit the sources then use git commands to create the patch. I would normally stop the build with "Ctrl c" after u-boot is downloaded and all the armbian u-boot patches are applied. Then create my u-boot patch. Patch ordering is important. You want your patch to be last. Your patch title will start with numbers or it will be in alphabetical order. The Armbian "kernel/archive/sunxi-6.x" patch directory is a little different. It uses "series.conf" and "series.armbian" to control the patch order. Plus you can ignore patches using "-" in front of the patch listed inside the two series files. Why do you need secure boot? I don't think Lancoly had secure boot issues. You should only use this secure boot patch if you don't see anything coming from your uart debug messages. If you tried the miniarch latest release v20250206 and it doesn't boot. It might be due to the dram issues I posted above. You will still see debug messages so it's important to have a USB to TTL Serial adaptor attached to your UART.

I'm pretty sure the problem is your dram detection. H313/H616?H618 has problems with dram size detection on some boards . Jernej released new patches that might fix your boot issues. https://github.com/jernejsk/u-boot/commits/a523/ https://github.com/warpme/minimyth2/commit/962ac7da6cb84d0e41826c5555cb101b70a53a8d I tried these patches on my board and it didn't work. U-Boot SPL 2025.01 (Feb 06 2025 - 15:11:12 +0100) DRAM: I also tried the latest Miniarch vontar image and it doesn't work either. Same output as above. Vontar images use to work on my box before. MiniArch-20240715-6.12.12-board-h618.vontar_h618-SD-Image.img.xz Update: There was an issue with these patches. https://oftc.irclog.whitequark.org/linux-sunxi/2025-03-03#34058621; https://github.com/warpme/minimyth2/issues/66 I tested this new fix and my transpeed tv box now boots. https://gist.github.com/warpme/0b225bfda42c7c1802b74f507c6a8bb4 @Cesar93600 I posted an updated image. https://github.com/NickAlilovic/build/releases/download/20250130/Armbian-unofficial_25.02.0-trunk_Q1_bookworm_edge_6.12.11_xfce_desktop.img.xz

@Cesar93600 Here's my custom Armbian build based on 6.12 kernel and warpme patches. This is my source code. https://github.com/NickAlilovic/build/archive/refs/tags/20250130.tar.gz I renamed the image to Q1. It was transpeed after the compile was complete. https://github.com/NickAlilovic/build/releases/download/20250130/Armbian-unofficial_25.02.0-trunk_Q1_bookworm_edge_6.12.11_xfce_desktop.img.xz This is the secure boot patch I used. diff --git a/root_key.pem b/root_key.pem new file mode 100644 index 0000000000..cfffdbf247 --- /dev/null +++ b/root_key.pem @@ -0,0 +1,28 @@ +-----BEGIN PRIVATE KEY----- +MIIEvQIBADANBgkqhkiG9w0BAQEFAASCBKcwggSjAgEAAoIBAQC4N+7DvqP4cmLP +1u9L8dQ1fVtzXxwzt6Qrn0JEMyHtQm2ZSwxOrAjyPKt9UTfEz3G5K7v7wBLzxS+n +KQWtrcwiFfAPrFK5wyEQU/z/ltfUBg4NCagvgngb38AGwdgAPZ9+Wl3cueB6XxpJ +etVlLUQtiaqGb92CyUDqZsbrNaBOOcxUxNEkAtxOHzriDC9PKRi780ntXWjp+R5Z +loDQ0SyxjnhGBPNAhEAkEHXCLhTg82JHm4tNEVi/esXfMwQRm6x/eb/p55zd/ULU +RXdxxS0j7/DPhRpync6mYJzLl7bDRrNA9DnyyC2kgWWkJ9F/QNMl3HqHTgClehTZ +MfO1tCM5AgMBAAECggEAAn6CJsCRUSFWHq6wF8OYupeBK/U6/ojDRmRP59TlyYsB +oi28fIwH/ev1ASne1L+txZ8k85qYp/uUVGjaynrng8roN8OpiZKGo14qMArf6x9S +eb2hjPfmX++vAT6jcOpkrOmDAFnf+IGDbytWPGTTxGoD5upf2PjYHnqPZQyrHY// +yAIpYtS9zjRx44iVN8olwwXXTDVe7yigAkrYvu0f4AUUv4azv68eYWXUXDN1YaWE +gtwjSOCnhuwHTJTyz6Vi40ju32zxq7rTbe09NV7LcU6CmJBy8GDv2KsNfwk+OwsI +gvz31jZ1jwyLZEGAxL/ibA0ldSAsjG3Akgw8jqG1cQKBgQDunDFVljn2uWVoBwip +QJveKIGNgVnJ6YF630JGMP4X20rkh7/9lyBJQUixlc6Z3qUcCfyKi8EJkPMLs1u+ +QSmmKnsInqp8ZkCPG0g4FZNgHkC+fIfmgO+gVNxyh+MXZNsvVVH6NtpRIfLSXeCl +aTWv4d8rIU5Tl9hDY2UhGQ7CaQKBgQDFpPEeS5hdIaqnZaJ50/V/gzrkENAFWZuP +zYqhS4RcD6dogAByjQvvNByIn5avrPz6N75qsZl5VY0TtaYe6hHehDOwKHM7CFZe +FSjSTdgi7b5jL11///9W5Eztn7L1ckZo93j2ZYLl9+PuXGAY4SRcYYOQjBBmOwmj +Qpryy2+gUQKBgCY4uuZc1BgjhoztY4PJJ66kimwiZkGjt+v4y2L3AhzMMej9ndF/ +XdqeLIjV2Gxpb8VYDC4dSOTBZU1gg7esNIG7mE2/LMwUjQ7fbegd/KeO8QwSYqqX +yMrEDTQDdGsQ6tNgNWuBUeNhLsZn505X1hPAeMEt6qAVWL0itNZibyzRAoGBALD6 +8wKa1LPImuTM6MHI4FOvckOZHn078UXC2zl1wu8hAVpdDImG7cHj2w0oQqnK8Lkq +w3MM145D4lFc3oVeOmQT46kBf7XD0Hrs3aH8HOeiFlMArewZk07+njhGQdzx2ETU +HVgeLCm7YTonM9HzgTjMBSChm2m/wfCUiuWQ78MRAoGAWAElZCjb8Dxp9z8KJ0JX +Z3d2yueOgxf3J6X+7XMW7Yv9uFOvYNI/BNT3Ii3P+u6SJpKXuQgBoDT/2FP/f8m6 +U1dMu7PHcBi3MA1IvGi6NSC+cVcIy0yYi2vYsW6lkOsDwr+HrDQWte3HjiXcIy+g +f9CFoVb4L1ILI/SBaZSV8LQ= +-----END PRIVATE KEY----- -- 2.34.1 My modified defconfig with your dram settings plus CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y for secure boot. diff --git a/configs/transpeed-8k618-t_defconfig b/configs/transpeed-8k618-t_defconfig new file mode 100644 index 0000000000..020d3974af --- /dev/null +++ b/configs/transpeed-8k618-t_defconfig @@ -0,0 +1,27 @@ +CONFIG_ARM=y +CONFIG_ARCH_SUNXI=y +CONFIG_DEFAULT_DEVICE_TREE="sun50i-h618-transpeed-8k618-t" +CONFIG_SPL=y +CONFIG_SUNXI_DRAM_H616_LPDDR3=y +CONFIG_DRAM_CLK=600 +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x06060606 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0d0d0d0d +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x00000d0d +CONFIG_DRAM_SUN50I_H616_ODT_EN=0x00000001 +CONFIG_DRAM_SUN50I_H616_TPR0=0x0 +CONFIG_DRAM_SUN50I_H616_TPR2=0x00000000 +CONFIG_DRAM_SUN50I_H616_TPR10=0x002f3359 +CONFIG_DRAM_SUN50I_H616_TPR11=0xaa889967 +CONFIG_DRAM_SUN50I_H616_TPR12=0xeeee8979 +CONFIG_MACH_SUN50I_H616=y +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_SYS_I2C_LEGACY=y +CONFIG_SYS_I2C_MVTWSI=y +CONFIG_SYS_I2C_SLAVE=0x7f +CONFIG_SYS_I2C_SPEED=400000 +CONFIG_SUPPORT_EMMC_BOOT=y +CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y +CONFIG_AXP313_POWER=y +CONFIG_AXP_DCDC3_VOLT=1360 +CONFIG_USB_EHCI_HCD=y +CONFIG_USB_OHCI_HCD=y

I'll make an image with your dram settings. What I find odd is your android boot log says you have DRAM: 1.5 GiB.

Your android has a AXP1530 PMIC also known as AXP313a. You are trying to boot an image with AXP305 PMIC. https://linux-sunxi.org/AXP_PMICs See if this image boots. This has a AXP1530 PMIC and secure boot. https://github.com/NickAlilovic/build/releases/download/v20240726/Armbian-20240726-unofficial_24.8.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_xfce_desktop_SECURE_BOOT.img.tar.xz

You should install a USB to TTL Serial adaptor to your UART. Your UART is clearly marked RX TX and GND on your board. I use gtkterm. "sudo gtkterm -p /dev/ttyUSB0 -s 115200". You'll see u-boot and kernel boot messages. This way you're not in the dark guessing why these images don't boot. After you post your boot logs I can help you figure out why it doesn't boot.

Here’s the patch you need to compile a secure boot image

Sorry @JamesCL, Werner is correct. I thought 8 would display all kernel messages. Not sure if we can pass ignore_loglevel. Try loglevel 7. The source I got the information from was wrong. https://stackoverflow.com/questions/16390004/change-default-console-loglevel-during-boot-up/16390389#16390389

Change the armbianEnv.txt log level to 8 in your sdcard. That should give you a more verbose kernel startup.

These are the instructions MMorales posted in the H618 thread. If your LED display is on then the module is already installed. This was done when you ran the commands "make modules_install" and "modprobe openvfd". I don't see "make clean". You only use that command if you plan on editing the sources and need to compile a new driver. cp openvfd.dts /boot/dtb/allwinner/overlay/ armbian-add-overlay /boot/dtb/allwinner/overlay/openvfd.dts reboot ln -sf /boot/System.map-$(uname -r) /lib/modules/$(uname -r)/build/System.map cd cd /linux_openvfd/driver make -j 4 depmod -a make modules_install modprobe openvfd cd .. chmod +x OpenVFDService cp OpenVFDService /usr/sbin/ cp openvfd.service /etc/systemd/system/openvfd.service #apt install python3-psutil systemctl enable openvfd.service systemctl start openvfd.service Type this command to list the modules already installed and running on your system. lsmod If you don't see openvfd in the list. Run modprobe without the .ko modprobe openvfd Check the directory /sys/class/leds/openvfd/ see if it exits. ls /sys/class/leds/openvfd/ You can skip these lines. We are more interested in the LED Icons. insmod openvfd.ko ./OpenVFDService & (run OpenVFDService Daemon to show time) ./OpenVFDService -t & (run OpenVFDService Daemon in test mode) I haven't looked at the openvfd driver sources much. I guess it's not the job of the driver to check the status of your network, usb etc... I believe the openvfd.service script sets the icons on or off manually using these commands. This is why you don't see any changes after you update your dts. The python script you sent me is based on xbmc/kodi scripts. I don't understand it too much. But I found this in the script. self._vfdon = '/sys/class/leds/openvfd/led_on' self._vfdoff = '/sys/class/leds/openvfd/led_off' The openvfd driver sets the on/off state manually using command for example alarm icon. echo alarm > /sys/class/leds/openvfd/led_on In this function fd650_set_icon(const char *name, unsigned char state) - name is the string we passed to the function (in this example it's "alarm") and the code inside compares name using the strncmp(name,"alarm",5) function. (name = "alarm" and 5 stands for the length of the string). The strncmp returns 0 if the string compare is correct. - dtb->led_dots[LED_DOT1_ALARM] is set in your dts. led_dots[] is an array of numbers. LED_DOT1_ALARM is the first position in the array. Alarm in the array is normally set to 0 but some displays are different. So we can change that value in the dts. - This code turns the LED Icon on or off. "dev->status_led_mask = state ? (dev->status_led_mask | dtb->led_dots[LED_DOT1_ALARM]) : (dev->status_led_mask & ~dtb->led_dots[LED_DOT1_ALARM]);" if (strncmp(name,"alarm",5) == 0) { dev->status_led_mask = state ? (dev->status_led_mask | dtb->led_dots[LED_DOT1_ALARM]) : (dev->status_led_mask & ~dtb->led_dots[LED_DOT1_ALARM]); } else if (strncmp(name,"usb",3) == 0) { dev->status_led_mask = state ? (dev->status_led_mask | dtb->led_dots[LED_DOT1_USB]) : (dev->status_led_mask & ~dtb->led_dots[LED_DOT1_USB]); } else if (strncmp(name,"play",4) == 0) { dev->status_led_mask = state ? (dev->status_led_mask | dtb->led_dots[LED_DOT1_PLAY]) : (dev->status_led_mask & ~dtb->led_dots[LED_DOT1_PLAY]); } else if (strncmp(name,"pause",5) == 0) { dev->status_led_mask = state ? (dev->status_led_mask | dtb->led_dots[LED_DOT1_PAUSE]) : (dev->status_led_mask & ~dtb->led_dots[LED_DOT1_PAUSE]); } else if (strncmp(name,"colon",5) == 0) { dev->status_led_mask = state ? (dev->status_led_mask | dtb->led_dots[LED_DOT1_SEC]) : (dev->status_led_mask & ~dtb->led_dots[LED_DOT1_SEC]); } else if (strncmp(name,"eth",3) == 0) { dev->status_led_mask = state ? (dev->status_led_mask | dtb->led_dots[LED_DOT1_ETH]) : (dev->status_led_mask & ~dtb->led_dots[LED_DOT1_ETH]); } else if (strncmp(name,"wifi",4) == 0) { dev->status_led_mask = state ? (dev->status_led_mask | dtb->led_dots[LED_DOT1_WIFI]) : (dev->status_led_mask & ~dtb->led_dots[LED_DOT1_WIFI]); } break; I don't think we need to make any changes to the driver. We need to figure out the correct number for each icon and test it by manually setting the icon on or off. Then we need to figure out a way to make our own service script to set these icons on or off depending on their state.

Hi Mark It looks like that python script might be using these commands. Try these commands maybe they'll work for you. https://github.com/arthur-liberman/linux_openvfd/blob/9264588ba27a964a1e56346202901dd17f9e133d/led_control.txt