Aleqssandro Farias Posted May 19 Posted May 19 (edited) Hi @Nick A, good afternoon! Yes, I tested them — I tried all three ISOs you shared. I'm sending you the UART logs from two of them: the one you specifically asked me to test and the MiniArch one. The one you asked me to try throws a DRAM error, while the MiniArch image actually boots — maybe because it’s configured for eMCP. log_miniarch.txt log_armbian_unofficial.txt Edited May 19 by Aleqssandro Farias 0 Quote
Nick A Posted May 20 Posted May 20 @Aleqssandro Farias your miniarch image says it’s using Tanix TX6s (axp313). Try the armbian version. https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_Tanix-tx6s-axp313_bookworm_edge_6.12.11.img.xz 0 Quote
Aleqssandro Farias Posted May 20 Posted May 20 Hi @Nick A, This ISO you sent has the same UART log error as the previous one. Here's the log: " U-Boot SPL 2025.01-armbian-2025.01-S6d41-P7151-H8869-V98f7-Bb703-R448a-dirty (Apr 02 2025 - 21:19:05 -0400) DRAM: testing 32-bit width, rank = 2 read calibration failed! testing 32-bit width, rank = 1 read calibration failed! testing 16-bit width, rank = 2 read calibration failed! testing 16-bit width, rank = 1 read calibration failed! This DRAM setup is currently not supported. resetting ... " Right now, the only image that boots properly is the MiniArch one. 0 Quote
Aleqssandro Farias Posted May 20 Posted May 20 (edited) Good afternoon @Nick A I managed to make some progress with the ISO you envy. I extracted the DTB used in MiniArch (which worked on the IK316 TV box) and replaced the DTB in its ISO. However, I noticed that the same error persisted. So, I decided to change the bootloader using the following commands: Extracted the working bootloader: $ dd if=MiniArch-20240715-6.14.0-board-h616.tanix_tx6s_axp313-SD-Image.img of=u-boot-sunxi-with-spl.bin bs=1024 skip=8 count=1016 So I injected it into the ISO that you envied me: $ dd if=u-boot-sunxi-with-spl.bin of=Armbian-unofficial_25.05.0-trunk_Tanix-tx6s-axp313_bookworm_edge_6.12.11.img bs=1024 seek=8 conv=notrunc After that, I got a new log and the TV Box booted, but I believe Armbian didn't start properly — it seems to take me to the U-Boot console. Here's the full log: " U-Boot SPL 2025.01 (24 de março de 2025 - 21:02:39 +0100) DRAM: 1024 MiB Tentando inicializar a partir do MMC1 AVISO: BL31: v2.10.0 (depuração):v14.0.0-98-gde86a8ab6 AVISO: BL31: Compilado: 01:02:27, 19 de março de 2025 AVISO: BL31: SoC Allwinner H61 detectado (1823) AVISO: BL31: DTB U-Boot encontrado em 0x4a0b0f80, modelo: Tanix TX6s (axp313) INFO: Driver ARM GICv2 inicializado INFO: Configurando o driver SPC INFO: PMIC: Sondando AXP305 sem RSB ERRO: RSB: tempo de execução definido endereço: 0x10003 INFO: Não foi possível inicializar RSB: -65539 INFO: BL31: Configuração da plataforma concluída INFO: BL31: Inicializando serviços de tempo de execução INFO: BL31: cortex_a53: Solução alternativa da CPU para a errata 855873 foi aplicada INFO: BL31: cortex_a53: solução alternativa da CPU para a errata 1530924 foi aplicada INFO: PSCI: Suspender não está disponível INFO: BL31: Preparando para saída EL3 para o mundo normal INFO: Endereço do ponto de entrada = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Árvore de dispositivos alterados. U-Boot 2025.01 (24 de março de 2025 - 21:02:39 +0100) Tecnologia Allwinner CPU: Allwinner H616 (SUN50I) Modelo: Tanix TX6s (axp313) DRAM: 1 GiB Núcleo: 58 dispositivos, 20 uclasses, devicetree: separado WDT: Não iniciando watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4021000: 3, mmc@4022000: 1 Carregando ambiente do FAT... Não é possível usar mmc 0:1... Entrada: serial@5000000 Saída: serial@5000000 Erro: serial@5000000 Nenhum dispositivo USB encontrado Rede: Não foi possível obter PHY para ethernet@5030000: endereço 16 Nenhuma ethernet encontrada. iniciando USB... Nenhum driver USB encontrado Pressione qualquer tecla para parar a inicialização automática: 0 alternativa para partições #0, OK mmc0 é o dispositivo atual Verificando mmc 0:1... Encontrado /boot/extlinux/extlinux.conf Recuperando arquivo: /boot/extlinux/extlinux.conf 1: MiniArch Recuperando arquivo: /boot/Image Recuperando arquivo: /boot/initrd.img append: root=/dev/mmcblk0p1 rootwait console=ttyS0,115200 panic=10 Recuperando arquivo: /boot/dtbs/allwinner/sun50i-h616-tanix-tx6s-axp313. dtb Movendo imagem de 0x40080000 para 0x40200000, end=0x420b0000 ## Blob da árvore de dispositivos achatada em 4fa00000 Inicializando usando o blob fdt em 0x4fa00000 FDT de trabalho definido como 4fa00000 Carregando Ramdisk para 49853000, fim 49fffc5e ... OK Carregando Árvore de Dispositivos para 0000000049848000, fim 00000000498524af ... OK FDT de trabalho definido como 49848000 Iniciando o kernel... :: Executando o gancho inicial [udev] Iniciando o systemd-udevd versão 253-1-arch :: Executando o gancho [udev] :: Disparando uevents... :: Executando o gancho [mapa de teclas] :: Carregando o mapa de teclas...kbd_mode: KDSKBMODE: ioctl inadequado para o dispositivo completo. :: montando '/dev/mmcblk0p1' na raiz real : executando o gancho de limpeza [udev] ERRO: Dispositivo raiz montado com sucesso, mas /sbin/init não existe. Saindo do controle, você está por conta própria. Boa sorte. sh: não é possível acessar tty; controle de tarefas desativado [rootfs]# " It looks like the root device was mounted correctly, but it couldn't find /sbin/init, so the system couldn't continue booting. Let me know if you have any suggestions or if you want me to try something else. Edited May 20 by Aleqssandro Farias 0 Quote
Nick A Posted May 20 Posted May 20 (edited) @Aleqssandro Farias which miniarch image are you using? Because I’m using miniarch patches so the dts should be the same. Edited May 20 by Nick A 0 Quote
Aleqssandro Farias Posted May 20 Posted May 20 @Nick A I’m using the MiniArch image that was shared here on the forum. From it, I extracted the DTBs, Image, and other boot files, and replaced them in the Armbian image. I also took the bootloader from the MiniArch image and replaced the one in Armbian. With that, I managed to boot into Armbian, but unfortunately, no network adapters were detected. 0 Quote
Alexandre Nery Posted July 11 Posted July 11 Hello, would you be able to share the ISO you used along with the modified DTBs? @Aleqssandro Farias 0 Quote
Jeeva Kandasamy Posted October 24 Posted October 24 Hi @Nick A thanks for the build details. It is working perfectly in my hardware: IK316Q-EMCP_V4.1 (IK3166-H, AXP313A, TYDOGH221664RA [1GB+8GB]) Current image: https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_server.img.xz However when I do apt upgrade I get the following error, Err:7 https://mirror.albony.in/armbian bookworm Release Redirection from https to 'http://mirror.hyd.albony.in/armbian/dists/bookworm/Release' is forbidden [IP: 82.180.145.196 443] I am using this device as headless server for IoT with internet, So I would like to keep updated kernel and packages all the time. Can you please guide me how to achieve this? 0 Quote
Nick A Posted October 24 Posted October 24 (edited) @Jeeva Kandasamy I would freeze your kernel updates using armbian-config. I’m using a custom kernel so it will break your system. I made google search and found this. https://github.com/MichaIng/DietPi/issues/4600 Edited October 25 by Nick A 0 Quote
Jeeva Kandasamy Posted October 25 Posted October 25 Thanks @Nick A for the details and link shared ! If I understand correctly, I can build kernel only locally and freeze kernel update. other packages can be downloaded from public repository Is that correct? 0 Quote
Jeeva Kandasamy Posted October 27 Posted October 27 (edited) Hi @Nick A I tried build your fork repository and facing the following error, Can you please help me to fix this error? Source code: https://github.com/NickAlilovic/build/ $ git remote -v origin git@github.com:NickAlilovic/build.git (fetch) origin git@github.com:NickAlilovic/build.git (push) $ git branch main * v20250306 Build command: ./compile.sh build BOARD=x96q-lpddr3-v1-3 BRANCH=edge BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=yes RELEASE=trixie Error: [🐳|🌱] git: Fetch from remote completed, rev-parsing... [ 'debootstrap-debian-devel' 'master' 'FETCH_HEAD' ] [🐳|🌱] Debootstrap version [ '1.0.142' for /armbian/cache/sources/debootstrap-debian-devel/debootstrap ] [🐳|🌱] Installing base system with 5 packages [ Stage 1/2 ] [🐳|🔨] I: Retrieving InRelease [🐳|🔨] I: Checking Release signature [🐳|🔨] E: Release signed by unknown key (key id 762F67A0B2C39DE4) [🐳|🔨] The specified keyring /usr/share/keyrings/debian-archive-keyring.gpg may be incorrect or out of date. [🐳|🔨] You can find the latest Debian release key at https://ftp-master.debian.org/keys.html [🐳|💥] error! [ Debootstrap first stage failed /armbian/cache/sources/debootstrap-debian-devel/debootstrap trixie yes ] [🐳|💥] Cleaning up [ please wait for cleanups to finish ] Edited October 27 by Jeeva Kandasamy 0 Quote
Nick A Posted October 27 Posted October 27 @Jeeva Kandasamy I haven't had that error before. Maybe your host is out of date. Have you tried "sudo apt update && sudo apt upgrade"? 0 Quote
Jeeva Kandasamy Posted October 28 Posted October 28 Thanks for the details @Nick A I tried with fedora/docker Can you please share the OS details, originally build OS and "./compile" options for https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-ddr3-v5-1_bookworm_edge_6.12.11_server.img.xz 0 Quote
Nick A Posted October 28 Posted October 28 (edited) @Jeeva Kandasamy it’s on this page. Build Host Requirements. https://github.com/armbian/build Edited November 27 by Nick A Updated the link to official Armbian build. 1 Quote
Nick A Posted November 27 Posted November 27 (edited) @Jeeva Kandasamy I noticed the same problem with my older builds. Should be fixed now. You'll need to install Docker. Also, if you see the build-root errors. Run the same compile options again and it continue where you left off. Edited November 27 by Nick A 0 Quote
Jeeva Kandasamy Posted November 27 Posted November 27 (edited) Thanks a lot @Nick A I will give a try now. I see few more device support added on your fork https://github.com/NickAlilovic/build Can I get the change log only for IK316/H616 with LPDDR RAM support? I would like to sync those changes with the most recent upstream source code. Edited November 27 by Jeeva Kandasamy 0 Quote
Nick A Posted November 27 Posted November 27 @Jeeva Kandasamy depends on which branch you are looking at? V20250306 hasn’t changed much. https://github.com/NickAlilovic/build/commits/v20250306/ 2 Quote
PH Ph Posted December 15 Posted December 15 Hi @Nick A, I have an identical motherboard as shown on page 1. Ik316-emcp_v1.0 2021.06.01 I can boot from the SD card, but it doesn't detect the internal memory. The Wi-Fi isn't working either, but that's already explained in the topic. How can I tell if the EMCP is damaged? Or if it's not being identified correctly? I have a CH431A available if needed. I believe it's possible to access UART via CH431. Previous reports suggest that the internal memory worked on this model, but I'm not certain of that. However, I must inform you that I was unable to install the supposed ROM on this model using PhoenixTool or PhoenixCard, This could indicate a failure in the emcp in the storage block. Thank you in advance for your support. boot.log 0 Quote
Nick A Posted December 15 Posted December 15 @PH Ph You need to find the correct GPIO# for your emmc. Extract the boot.bin from your original Android to get the device tree (DTS). Follow the steps in this link. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-187672 0 Quote
PH Ph Posted Thursday at 03:17 AM Posted Thursday at 03:17 AM (edited) Hi @Nick A, As I said above, I can't install the ROM on this board. on phoenixSuit or usbpro Failure due to timeout. I believe the memory block is damaged. But the RAM is still working. To confirm that the ROM works, I used PhoenixCard in startup mode, and it booted from the SD card normally. But when I use product mode to install the ROM from the SD card, the screen goes black, the installation bar doesn't appear, and it stays that way. I really believe it only damaged the internal memory. Okay, about that, next question: When I use stock Android 10, even with 1GB of RAM, I can play 1080p videos (youtube using chrome v143) on this box, but using Armbian it's very difficult to get 480p-720p, not to mention the overall image quality; it's as if there's no graphics acceleration. On Android (aida64) says it's a Mali-G31. Is there any way to confirm this? Config on armbian is Xfce removed install I3wm Update chromium Zram update to 1gb Using sdcard class10 u3 Edited Thursday at 03:30 AM by PH Ph 0 Quote
Nick A Posted Thursday at 06:17 AM Posted Thursday at 06:17 AM @PH Ph there is graphics acceleration but not on chromium. If you can still boot android then you can extract your dts. Not sure what's wrong with PhoenixCard. I rarely use it. That's mostly for Android images. 0 Quote
PH Ph Posted 2 hours ago Posted 2 hours ago (edited) Hi @Nick A, I think I'm doing something wrong, but here goes. cat /proc/partitions major minor #blocks name 1 0 8192 ram0 1 1 8192 ram1 1 2 8192 ram2 1 3 8192 ram3 1 4 8192 ram4 1 5 8192 ram5 1 6 8192 ram6 1 7 8192 ram7 1 8 8192 ram8 1 9 8192 ram9 1 10 8192 ram10 1 11 8192 ram11 1 12 8192 ram12 1 13 8192 ram13 1 14 8192 ram14 1 15 8192 ram15 254 0 745120 zram0 179 0 31166976 mmcblk0 179 1 32768 mmcblk0p1 179 2 16384 mmcblk0p2 179 3 32768 mmcblk0p3 179 4 2097152 mmcblk0p4 179 5 16384 mmcblk0p5 179 6 32768 mmcblk0p6 179 7 911360 mmcblk0p7 179 8 16384 mmcblk0p8 179 9 16384 mmcblk0p9 179 10 16384 mmcblk0p10 179 11 16384 mmcblk0p11 179 12 16384 mmcblk0p12 179 13 512 mmcblk0p13 179 14 15872 mmcblk0p14 179 15 16384 mmcblk0p15 259 0 16384 mmcblk0p16 259 1 27858432 mmcblk0p17 253 0 1241204 dm-0 253 1 146376 dm-1 253 2 113948 dm-2 ls -al /dev/block/platform/soc/sdc0/by-name/ total 0 drwxr-xr-x 2 root root 380 1969-12-31 21:00 . drwxr-xr-x 3 root root 420 1969-12-31 21:00 .. lrwxrwxrwx 1 root root 21 1969-12-31 21:00 Reserve0 -> /dev/block/mmcblk0p16 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 UDISK -> /dev/block/mmcblk0p17 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 boot -> /dev/block/mmcblk0p3 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 bootloader -> /dev/block/mmcblk0p1 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 cache -> /dev/block/mmcblk0p7 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 empty -> /dev/block/mmcblk0p14 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 env -> /dev/block/mmcblk0p2 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 frp -> /dev/block/mmcblk0p13 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 media_data -> /dev/block/mmcblk0p15 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 metadata -> /dev/block/mmcblk0p11 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 misc -> /dev/block/mmcblk0p5 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 private -> /dev/block/mmcblk0p12 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 recovery -> /dev/block/mmcblk0p6 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 super -> /dev/block/mmcblk0p4 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 vbmeta -> /dev/block/mmcblk0p8 lrwxrwxrwx 1 root root 20 1969-12-31 21:00 vbmeta_system -> /dev/block/mmcblk0p9 lrwxrwxrwx 1 root root 21 1969-12-31 21:00 vbmeta_vendor -> /dev/block/mmcblk0p10 I couldn't open vendor.img boot.img i do.However, I couldn't find the dts file, only fstab, initd, and a few other empty folders. I posted the images below on 4shared. boot = boot.img vbmeta_vendor = vendor.img boot.img (32.0MB) Image type: Boot image Header version: 2 Command line arguments: selinux=1 androidboot.selinux=permissive androidboot.dtbo_idx=0,1,2 buildvariant=userdebug files avp folder s-gsi.avbpubkeyq-gsi.avbpubkeyr-gsi.avbpubkey fstab.sun50iw9p1 initrd.gz If you can check, I would appreciate it; I await further instructions. !off I tried mounting the partitions by inserting the burned SD card into the PC, but it's not possible to mount them. Except for a few... The SD card made by Phoenixcard is quite interesting. Could it be that the scheme on the SD card is not the same as when installed in the internal memory? The Udisk partition, for example. It's like shared memory, expanding all remaining space on both the memory card and the datauser partition. Similar to using a formatted SD card as internal memory on cell phones with that option. Edited 1 hour ago by PH Ph 0 Quote
Nick A Posted 1 hour ago Posted 1 hour ago @PH Ph bootloader -> /dev/block/mmcblk0p1 Maybe this is the boot.bin we are looking for? Try extracting it with Android_boot_image_editor. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.