All Activity

Found the method. A program called anylinuxfs will mount the EXT4 sd card on a Mac. However, even on the Trunk 100, I don't see armbianEnv.txt in /boot. Where do I find it?

You could use the Cubie for it. The trunk.100 works you said, so you have a working Linux computer, can be operated via serial cable console.

I usually just re-plug the sdcard back into my laptop, the fs mounts automatically for me. Using Linux though, no clue about MacOS.

I didn't know it was possible to edit a file within a boot image... I'm using MacOS, how would I do that?

Fair enough. "WRITE the image" would probably be clearer. The image file is from the repository, I'm using Balena to WRITE the image (rather than MAKE) to the SD card. I'm sure you knew what I meant, but I agree that clarity is important. BTW - Where would I find the changelogs for these trunks?

Please set verbosity to 7 in armbianenv.txt to get a clue about what happens after "starting kernel..." data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw== Interesting. While this isn't an actual issue since the correct dt was loaded nevertheless it seems like BOOT FDT FILE Is set wrong

moved to tvboxes

---- Opened the serial port /dev/tty.PL2303G-USBtoUART8430 ---- U-Boot SPL 2026.01-rc4_armbian-2026.01-rc4-S0e0a-Peafc-H5aa4-Vd0f6-B4d1d-R448a (Dec 29 2025 - 03:26:30 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.12.0(debug):armbian NOTICE: BL31: Built : 03:26:10, Dec 29 2025 NOTICE: BL31: Detected Allwinner A523 SoC (1890) NOTICE: BL31: Found U-Boot DTB at 0xa0ab9f8, model: Radxa Cubie A5E INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: Maximum SPI INTID supported: 287 INFO: Configuring SPC Controller INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a55: CPU workaround for erratum 1530923 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 ns16550_serial serial@2500000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2026.01-rc4_armbian-2026.01-rc4-S0e0a-Peafc-H5aa4-Vd0f6-B4d1d-R448a (Dec 29 2025 - 03:26:30 +0000) Allwinner Technology CPU: Allwinner A523 (SUN55I) Model: Radxa Cubie A5E DRAM: 2 GiB sunxi_set_gate: (CLK#35) unhandled Core: 77 devices, 22 uclasses, devicetree: separate WDT: Not starting watchdog@2050000 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: serial@2500000 Out: serial@2500000 Err: serial@2500000 Net: eth0: ethernet@4500000 starting USB... sun4i_usb_phy phy@4100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 Bus usb@4101000: 1 USB Device(s) found Bus usb@4101400: 1 USB Device(s) found Bus usb@4200000: 1 USB Device(s) found Bus usb@4200400: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4641 bytes read in 3 ms (1.5 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 190 bytes read in 2 ms (92.8 KiB/s) The file sun55i-a527-radxa-a5e.dtb was not found in the path /dtb/allwinner Load fdt: /dtb/allwinner/sun55i-a527-cubie-a5e.dtb 33947 bytes read in 6 ms (5.4 MiB/s) Working FDT set to 4fa00000 Failed to load '/dtb/overlay/sun55i-a527-fixup.scr' 15452067 bytes read in 642 ms (23 MiB/s) 31721984 bytes read in 1315 ms (23 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42130000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15452003 Bytes = 14.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 49143000, end 49fff763 ... OK Loading Device Tree to 00000000490d2000, end 0000000049142fff ... OK Working FDT set to 490d2000 Starting kernel ... Never goes any further. It doesn't get an IP so I can't SSH into it. The "heatbeat" LED does keep flashing, though... Comparing a the trunk 100 which DOES go on to the login prompt and finishes normally: ---- Opened the serial port /dev/tty.PL2303G-USBtoUART8430 ---- U-Boot SPL 2026.01-rc4_armbian-2026.01-rc4-Sd24f-P0000-He0b4-V52aa-Bbf55-R448a (Dec 19 2025 - 03:11:57 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.12.0(debug):armbian NOTICE: BL31: Built : 03:11:45, Dec 19 2025 NOTICE: BL31: Detected Allwinner A523 SoC (1890) NOTICE: BL31: Found U-Boot DTB at 0xa0ab9f8, model: Radxa Cubie A5E INFO: GICv3 without legacy support detected. INFO: ARM GICv3 driver initialized in EL3 INFO: Maximum SPI INTID supported: 287 INFO: Configuring SPC Controller INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a55: CPU workaround for erratum 1530923 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 ns16550_serial serial@2500000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2026.01-rc4_armbian-2026.01-rc4-Sd24f-P0000-He0b4-V52aa-Bbf55-R448a (Dec 19 2025 - 03:11:57 +0000) Allwinner Technology CPU: Allwinner A523 (SUN55I) Model: Radxa Cubie A5E DRAM: 2 GiB sunxi_set_gate: (CLK#35) unhandled Core: 77 devices, 22 uclasses, devicetree: separate WDT: Not starting watchdog@2050000 MMC: mmc@4020000: 0 Loading Environment from FAT... Unable to read "uboot.env" from mmc0:1... In: serial@2500000 Out: serial@2500000 Err: serial@2500000 Net: eth0: ethernet@4500000 starting USB... sun4i_usb_phy phy@4100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 Bus usb@4101000: 1 USB Device(s) found Bus usb@4101400: 1 USB Device(s) found Bus usb@4200000: 1 USB Device(s) found Bus usb@4200400: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot.scr 4641 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 190 bytes read in 1 ms (185.5 KiB/s) The file sun55i-a527-radxa-a5e.dtb was not found in the path /dtb/allwinner Load fdt: /dtb/allwinner/sun55i-a527-cubie-a5e.dtb 17944 bytes read in 4 ms (4.3 MiB/s) Working FDT set to 4fa00000 Failed to load '/dtb/overlay/sun55i-a527-fixup.scr' 14716909 bytes read in 834 ms (16.8 MiB/s) 31918592 bytes read in 1323 ms (23 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42150000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14716845 Bytes = 14 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 491f7000, end 49ffffad ... OK Loading Device Tree to 000000004918a000, end 00000000491f6fff ... OK Working FDT set to 4918a000 Starting kernel ... Very little is different, except that the ftd is about twice the size...

Post the UART log.

Hello. I recently got a vontar-dq08 working with armbian. I used someone's build for a x88pro, so I replaced the dtb with the one that came on my board. After editing the ArmbianEnv.txt and resetting, it did not boot. Idk if it's a typo on my end or the tree not working, but to make it boot I would just have to change ArmbianEnv.txt, but taking the sdcard out and plugging it in my computer I can't find the file in /boot How can I revert the ArmbianEnv.txt when my machine doesn't boot?

Succes, I lowlevel formatted my SD cart. Now i can install the CLI I think there was something not right The next thing to try is install a desktop image. And fix the overscan issue and then install to the emmc internal memory My internal menory is Sandisk SDINADF4-16G so i am hopefull. But when i brick the system, is it stil possible to boot from a SD card or must i try to flash a version of android first using a USB A to USB a cabble? Sorry I am not allowed to upload Image?

For you, 'make an image' means downloading a file from Armbian website and write it to an SD-card. For me, 'make an image' means using the Armbian build environment https://github.com/armbian/build to create an image yourself locally on your computer. This is what 'make an image' is. Already 2 people including myself showed that GPT is corrupted in the image file on the Armbian website. You can assume that the bootloader when run on the board itself also detects that, so it won't boot/proceed. So something goes wrong in the Armbian build infrastructure. However, that is what I assume. So up to you confirm by showing the logs of the bootloader. You need serial console cable for that, so you can copy and paste for sharing that log here on the forum. Other option, a step further ahead, is to make an image yourself. You need a Linux computer/environment for it. It also shows very detailed logs, share that.

https://paste.armbian.com/etukovewas

For once as stated don't use Balena. use Armbian imager or usbimager For the other write the image anyway as it is, try to boot and grab serial logs if there is an actual issue or not.

Huh? How can you create logs when you can't make an image?

No logs - no issue.

Trunk 151 has the same problem.

@Werner OK, since I have a few Duos (v1.0 and v1.1) I tried same Jammy with 6.1.63 kernel SD in each and let idle. The 1.1 with copper heatsink runs about 40C, the 1.1 with same aluminum heat sink runs around 45C. The v1.0 runs around 50C. So weird. I'll try latest build, but stress-ng causing thermal shutdowns worries me. I used to run decent loads on these little boards. Good thing is thermal shutdown works or it would burn up the board.

How can I force it to boot from SD though?

As a followup: hardware crypto is damn slow on the Ky / SpacemIt platform, at least for default LUKS block encryption with AES. This probably also affects the Banana Pi F3 image. With default sector-size of 512 byte, HW-AES is 5 times slower than SW-AES, while cryptsetup benchmark reports 5 times faster. Main reason: block size. With sector-size of 4096 LUKS is reasonable fast. Also there is leftover debug (cannot be switched off) and a small bugs in the driver that triggers SW crypto fallback after HW crypto succeeds. Patches: https://github.com/sven-ola/armbian-build/tree/orangepi-rv2/patch/kernel/ky-current Best // Sven-Ola

I do not use chatgpt Most of them are rubbish anwers

Here is ukrainian forum with Android for this box: https://legione.name/upload/?dir=Smart-TV-Box/Q1/ Any chance to find linux for the same box? Android tv box q1 v3.0 Allwinner H313 If someone will find working version, please share

I dumped all your text in ChatGPT and got enough answers; maybe do the same

What are the possible commands you can use I there a possibility to enable wifi on first boot Or set the monitor resolution Or other settings you can make

Hello! It seems that there is some issue with the user files FTP server. The multitool image should be acessessible from: https://users.armbian.com/jock/web/rk322x/multitool/ But it is present in: https://users.armbian.com/users.armbian.com/jock/web/rk322x/multitool/