[Bug]: Arduino UNO Q: I'm unable to boot Ubuntu and Debian images

[fedecarg]

What happened?

Flashing Armbian images for Arduino UNO Q using Armbian Imager v1.3.3 does not produce a bootable system on my board. After flashing, the board does not appear to boot successfully and I do not get video output through USB-C DisplayPort Alt Mode using my HDMI adapter or hub.

I tested the following images:

❌ Armbian Debian 13 Trixie Minimal CLI, flashed with Armbian Imager v1.3.3
❌ Armbian Ubuntu 26.04 Resolute GNOME, flashed with Armbian Imager v1.3.3

https://armbian.com/boards/arduino-uno-q

I also tested flashing with Arduino Flasher CLI v0.5.1, but the same Armbian images did not boot successfully.

As a control test, Arduino's official Debian 13 Trixie Desktop image works correctly when flashed using both tools:

✅ Arduino Debian 13 Trixie Desktop, flashed with Armbian Imager v1.3.3
✅ Arduino Debian 13 Trixie Desktop, flashed with Arduino Flasher CLI v0.5.1

Hardware:

Arduino UNO Q
Variant: 4 GB RAM, 32 GB eMMC
Power: USB-C 5V / 3A
Display setup: USB-C hub or USB-C to HDMI adapter
Monitor resolution tested: 1920x1080
Host OS used for flashing: MacBook Air M1
Armbian Imager version: 1.3.3
Arduino Flasher CLI version: 0.5.1

Expected result:

The Armbian image should boot on the Arduino UNO Q and provide either visible video output through USB-C DisplayPort Alt Mode, network access, serial console output, or another clear indication that the system has started.

Actual result:

• After flashing the Armbian images, the board does not appear to boot successfully. I do not get video output through my USB-C hub or HDMI adapter, and I cannot confirm that the OS is running.
• adb does not list any devices because the OS never starts.
• The Arduino UNO Q LEDs indicate that these images are not bootable.

Control result:

Flashing Arduino's official Debian image works as expected on the same board, using the same power supply, cable, hub, display, and flashing tools.

How to reproduce?

1. Install

• Armbian Debian 13 Trixie Minimal CLI, flashed with Armbian Imager v1.3.3
• Armbian Ubuntu 26.04 Resolute GNOME, flashed with Armbian Imager v1.3.3

2. Arduino's LED matrix is stuck on the startup logo and not booting, it indicates a bootloader error
3. adb devices doesn't list andy connected devices

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

MacBook Air M1 Version 14.7.4

Are you building on Windows WSL2?

• Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[SuperKali]

Please, attach the Arduino on your PC via usb-c and install adb, with adb check if the device is listed with adb devices.

[igorpecovnik]

@fedecarg

Please forum for support.

[fedecarg]

@SuperKali The images are not booting. adb does not list any devices because the OS never starts. The Arduino UNO Q LEDs indicate that these images are not bootable.

[fedecarg]

Compiling the image and flashing it using arduino-flasher-cli didn't work either:

$ ./compile.sh BOARD=arduino-uno-q RELEASE=trixie BUILD_DESKTOP=yes BUILD_MINIMAL=no KERNEL_CONFIGURE=no
$ ./arduino-flasher-cli flash Armbian-unofficial_26.05.0-trunk_Arduino-uno-q_trixie_edge_7.0.0_minimal.tar 
...truncated...
11 patches applied                                                              
partition 0 is now bootable

The board has been successfully flashed. You can now power-cycle the board (unplug and re-plug). Remember to remove the jumper.

• Unplugged USB-C.
• Removed jumper.
• Re-plugged and waited 1 minute.
• adb devices && adb shell: no devices/emulators found

[fedecarg]

@igorpecovnik I'm happy to use the forum for support, but I think there may be a real issue here. I'm testing on the Arduino UNO Q with the latest available tools and packages, and the images are not booting. adb does not list any devices because the OS never starts. The board LEDs also indicate that these images are not bootable. (PS. Ljubljana is such a beautiful place, I used to live in Zagreb)

[EvilOlaf]

There may be a real issue here, however not related to the framework, building Armbian to say. This is obviously about booting or flashing. Former shall be reported in forums, latter (if related to Armbian imager) in its own repository.

[igorpecovnik]

there may be a real issue here

Absolutely, you may be right - there could still be a problem, even though we were unable to reproduce it on our side. I personally tested this board, and Superkali tested it again; in both cases the system booted normally.

We already invested significant time into first porting and now investigation and testing, and unfortunately we are not able to continue deeper debugging within the scope of free community support https://docs.armbian.com/User-Guide_Board-Support-Rules/#community-maintained

Our support team is combination of volonteers and people we support and is super tiny. They need to avoid spending excessive engineering time on such targets (CSC - run it if it works but don't expect any support) in order to keep the project and themselves sustainable. We only have few boards which we got on Embedded World fair as a giveaway - they are all the same and for proper support you need to have different variants and revisions - and there is no cooperation whatsoever with Arduino. This means we have to pay for the time we need from this and that is gone for years in advance.

This place here is off topic, so I am moving issue to the place where it can stay. We don't want that people open hardware related bugs in build framework issue tracker. I hope you do understand.

[SuperKali]

These are the tests we ran last night after you opened this issue:

After flashing, disconnect the device, remove the jumper, and restart it.

adb shell -> connects directly to the terminal

In any case, without useful information, logs extracted from the serial port won’t be of much help to us. Furthermore, as Igor mentioned above, these boards were given to us at the Embedded World event—they’re the same model—so they might be slightly different from ours, but I have serious doubts about that. Without the serial port, it’s difficult to debug.
Support for this board is community-based, so it can work one day and have issues the next. There is no dedicated support.

[fedecarg]

Thanks for your time and support guys. I'll keep investigating and will try to get useful logs from the serial port if I can.

[govindsi]

I am also able to reproduce the issue and below are the boot logs.

Image: Armbian_community_26.2.0-trunk.904_Arduino-uno-q_resolute_edge_7.0.0_gnome_desktop.tar.xz
Flasher: Armbian.Imager_1.3.4_amd64.AppImage

The logs show a synchronous abort in U-Boot (ESR 0x96000005) due to an invalid memory access at address 0xd4000000.
This likely results from incorrect memory mapping or boot script configuration.
There is also an indication of DTB mismatch and missing armbianEnv.txt, which suggests a boot configuration issue rather than a confirmed memory overwrite.

Logs:
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.XF.4.1.2-00018-KAMORTALAZ-1
S - IMAGE_VARIANT_STRING=AgattiPkgLAA
S - OEM_IMAGE_VERSION_STRING=crm-ubuntu154
S - Boot Interface: USB
S - Secure Boot: Off
S - Boot Config @ 0x01b46070 = 0x00000041
S - JTAG ID @ 0x01b46130 = 0x001c80e1
S - OEM ID @ 0x01b46138 = 0x00000000
S - Serial Number @ 0x01b46134 = 0x5c1a0bac
S - OEM Config Row 0 @ 0x01b441b8 = 0x0000000000000000
S - OEM Config Row 1 @ 0x01b441c0 = 0x0000000000000000
S - Feature Config Row 0 @ 0x01b441d0 = 0x0050200016418000
S - Feature Config Row 1 @ 0x01b441d8 = 0x0012008017830000
S - Core 0 Frequency, 1305 MHz
S - PBL Patch Ver: 1
S - PBL freq: 600 MHZ
D - 5505 - pbl_apps_init_timestamp
D - 3444094 - bootable_media_detect_timestamp
D - 170469597 - bl_elf_metadata_loading_timestamp
D - 692 - bl_hash_seg_auth_timestamp
D - 93093 - bl_elf_loadable_segment_loading_timestamp
D - 4260 - bl_elf_segs_hash_verify_timestamp
D - 17406 - bl_sec_hash_seg_auth_timestamp
D - 859 - bl_sec_segs_hash_verify_timestamp
D - 31 - pbl_populate_shared_data_and_exit_timestamp
S - 174035537 - PBL, End
B - 174052159 - SBL1, Start (MPM timestamp = 173938358)
B - 174165545 - SBL1 BUILD @ 22:39:35 on Jul 25 2023
D - 629 - sbl1_hw_init
D - 7 - boot_flash_init
B - 174177818 - Using boot chain :: Primary
D - 2882 - sbl1_update_partition_ids
D - 1085 - sbl1_xblconfig_init
D - 4 - sbl1_feature_config_init
D - 3 - boot_config_data_table_default_init
D - 19 - sbl1_ddr_set_default_params
B - 174199856 - Using default CDT
D - 3916 - boot_config_data_table_init
B - 174206828 - CDT Version:3,Platform ID:34,Major ID:1,Minor ID:0,Subtype:0
D - 9491 - sbl1_hw_platform_pre_ddr
D - 2702 - pmic DevPrg init
D - 3654 - sbl1_hw_pre_ddr_init
D - 3 - boot_dload_handle_forced_dload_timeout
D - 80 - sbl1_ddr_set_params
B - 174235457 - DSF version = 20.0, DSF RPM version = 11.0
B - 174235574 - Manufacturer ID = 255, Device Type = 7
B - 174240791 - Rank 0 size = 2048 MB, Rank 1 size = 0 MB
B - 174245665 - Max Frequency = 1804 MHz
B - 174250802 - Row Hammer Check : DRAM supports unlimited MAC Value : MR24[OP2:0 = 0] & MR24[OP3 = 1] for CH0 & CS0
D - 27810 - sbl1_ddr_init
D - 74 - sbl1_do_ddr_training
B - 174267504 - DevProg DDR Entry
B - 174273098 - usb: init start
B - 174273823 - usb: HIGH , 0x900e
B - 174276684 - usb: timer_start , 0x4c4b40
B - 174279799 - usb: ENUM success
B - 174288725 - usb: host sends ZLP

Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.XF.4.1.2-00023-KAMORTALAZ-5
S - IMAGE_VARIANT_STRING=AgattiPkgLAA
S - OEM_IMAGE_VERSION_STRING=hu-snanaval-hyd
S - Boot Interface: eMMC
S - Secure Boot: Off
S - Boot Config @ 0x01b46070 = 0x00000041
S - JTAG ID @ 0x01b46130 = 0x001c80e1
S - OEM ID @ 0x01b46138 = 0x00000000
S - Serial Number @ 0x01b46134 = 0x5c1a0bac
S - OEM Config Row 0 @ 0x01b441b8 = 0x0000000000000000
S - OEM Config Row 1 @ 0x01b441c0 = 0x0000000000000000
S - Feature Config Row 0 @ 0x01b441d0 = 0x0050200016418000
S - Feature Config Row 1 @ 0x01b441d8 = 0x0012008017830000
S - Core 0 Frequency, 1305 MHz
S - PBL Patch Ver: 1
S - PBL freq: 600 MHZ
D - 5512 - pbl_apps_init_timestamp
D - 190825 - bootable_media_detect_timestamp
D - 3573 - bl_elf_metadata_loading_timestamp
D - 695 - bl_hash_seg_auth_timestamp
D - 16028 - bl_elf_loadable_segment_loading_timestamp
D - 4057 - bl_elf_segs_hash_verify_timestamp
D - 17417 - bl_sec_hash_seg_auth_timestamp
D - 859 - bl_sec_segs_hash_verify_timestamp
D - 32 - pbl_populate_shared_data_and_exit_timestamp
S - 238998 - PBL, End
B - 256192 - SBL1, Start (MPM timestamp = 261019)
B - 369846 - SBL1 BUILD @ 18:02:00 on Jun 19 2025
B - 375176 - usb: hs_phy_nondrive_start
B - 379553 - usb: hs_phy_nondrive_finish
D - 8527 - sbl1_hw_init
D - 13 - boot_flash_init
B - 414640 - Using boot chain :: Primary
D - 25072 - sbl1_update_partition_ids
D - 947 - Auth Metadata
D - 7166 - sbl1_xblconfig_init
D - 388 - sbl1_feature_config_init
D - 3 - boot_config_data_table_default_init
D - 17 - sbl1_ddr_set_default_params
D - 4134 - boot_config_data_table_init
B - 441456 - CDT Version:3,Platform ID:32,Major ID:1,Minor ID:0,Subtype:1
D - 9483 - sbl1_hw_platform_pre_ddr
D - 5078 - devcfg init
B - 519303 - PM: PSI: b0x00_v0x14
B - 522845 - PM: Device Init # SPMI Transn: 4094
B - 526004 - PM: Driver Init # SPMI Transn: 233
B - 527515 - PM: Imola charging = 0x0
B - 532015 - PM: CHG Init # SPMI Transn: 4331
D - 78407 - pmic XBL init
D - 10398 - vsense_railway_cpr init
D - 98435 - sbl1_hw_pre_ddr_init
D - 2 - boot_dload_handle_forced_dload_timeout
D - 2931 - sbl1_load_ddr_training_data
D - 4969 - sbl1_ddr_set_params
B - 569412 - DSF version = 20.0, DSF RPM version = 11.0
B - 569452 - Manufacturer ID = 255, Device Type = 7
B - 574670 - Rank 0 size = 2048 MB, Rank 1 size = 0 MB
B - 579545 - Max Frequency = 1804 MHz
B - 584682 - Row Hammer Check : DRAM supports unlimited MAC Value : MR24[OP2:0 = 0] & MR24[OP3 = 1] for CH0 & CS0
D - 27913 - sbl1_ddr_init
B - 598594 - do_ddr_training, Start
B - 604922 - Bootup frequency set to 1804800
D - 3675 - do_ddr_training, Delta
D - 10627 - sbl1_do_ddr_training
D - 2 - sbl1_hand_control_to_devprog_ddr_or_ddi
B - 616019 - Pimem init cmd, entry
D - 9922 - Pimem init cmd, exit
D - 15608 - sbl1_post_ddr_init
D - 270 - sbl1_hw_init_secondary
B - 639810 - APDP Image Loaded, Start
D - 1048 - APDP Image Loaded, Delta - (0 Bytes)
D - 3 - boot_dload_dump_security_regions
D - 13 - boot_dload_check
D - 2 - boot_cache_set_memory_barrier
D - 1 - boot_smem_debug_init
D - 294 - boot_smem_init
D - 3 - boot_smem_alloc_for_minidump
D - 45 - boot_smem_store_pon_status
D - 11 - sbl1_hw_platform_smem
D - 113 - boot_clock_init_rpm
D - 2 - boot_vsense_copy_to_smem
D - 1 - boot_share_flash_data
D - 7 - boot_populate_ram_partition_table
D - 7 - boot_populate_ddr_details_shared_table
D - 4 - sbl1_tlmm_init
D - 2 - sbl1_efs_handle_cookies
D - 1 - boot_apt_test
B - 706264 - OEM_MISC Image Loaded, Start
D - 768 - Auth Metadata
D - 238 - Segments hash check
D - 7241 - OEM_MISC Image Loaded, Delta - (7816 Bytes)
B - 719154 - QTI_MISC Image Loaded, Start
D - 2880 - QTI_MISC Image Loaded, Delta - (0 Bytes)
B - 728090 - PM: PM Total Mem Allocated: 1249
D - 5043 - sbl1_pm_aop_pre_init_wrapper
B - 735524 - RPM Image Loaded, Start
D - 873 - Auth Metadata
D - 1340 - Segments hash check
D - 16254 - RPM Image Loaded, Delta - (220604 Bytes)
B - 755008 - QSEE Dev Config Image Loaded, Start
D - 937 - Auth Metadata
D - 441 - Segments hash check
D - 13786 - QSEE Dev Config Image Loaded, Delta - (40096 Bytes)
B - 777567 - QSEE Image Loaded, Start
D - 17959 - Auth Metadata
D - 17079 - Segments hash check
D - 98275 - QSEE Image Loaded, Delta - (3416070 Bytes)
D - 46 - sbl1_hw_play_vibr
B - 886637 - SEC Image Loaded, Start
D - 696 - SEC Image Loaded, Delta - (0 Bytes)
B - 890908 - QHEE Image Loaded, Start
D - 850 - Auth Metadata
D - 2148 - Segments hash check
D - 15511 - QHEE Image Loaded, Delta - (374176 Bytes)
B - 911986 - STI Image Loaded, Start
D - 2786 - STI Image Loaded, Delta - (0 Bytes)
B - 918349 - ABL Image Loaded, Start
D - 777 - Auth Metadata
D - 724 - Segments hash check
D - 12467 - ABL Image Loaded, Delta - (146024 Bytes)
B - 934710 - APPSBL Image Loaded, Start
D - 965 - Auth Metadata
D - 8814 - Segments hash check
D - 28495 - APPSBL Image Loaded, Delta - (2228224 Bytes)
D - 5 - sbl1_appsbl_arch_determination
B - 972418 - SBL1, End
D - 719801 - SBL1, Delta
S - Flash Throughput, 58000 KB/s (6466710 Bytes, 109727 us)
S - DDR Frequency, 1804 MHz

UEFI Start [ 1161]

• 0x05FC01000 [ 1167] Sec.efi
  ASLR : ON
  DEP : ON (RTB)
  Timer Delta : +5 mS
  RAM Entry 0 : Base 0x0000000040000000 Size 0x000000003EB00000
  RAM Entry 1 : Base 0x0000000080000000 Size 0x0000000040000000
  UART Buffer size set to 0x8000
  Init 3 aux cores of 3
  Init CPU core 1
  Init CPU core 2
  Init CPU core 3

Scheduler up on Core 1
UEFI Ver : 5.0.250619.BOOT.XF.4.1.2-00023-KAMORTALAZ-5
Build Info : 64b Jun 19 2025 18:02:47
Boot Device : eMMC
PROD Mode : TRUE
Retail : TRUE
Scheduler up on Core 2
Scheduler up on Core 3
First FV Decompress time 22 ms
Second FV Decompress time 0 ms (Decompress Thread)
Module cannot re-initialize DAL module environment
Embedded Images Supported and Commonlibs loaded
HW Wdog Setting from PCD : Disabled
PM0: 55,
DisplayDxe: SW renderer mode enabled!
DisplayDxe: Resolution 640x480 (1 intf)
UsbConfigPortsQueryConnectionChange: UFP and Type-C
UsbConfigPortsQueryConnectionChange: usbport->connectstate: ATT
MinidumpTADxe: Minidump TA loading not enabled.
WaitParallelThreads InIt [ 1380]

---

Platform Init [ 1380] BDS
Var Store : WARNING, not persistent
UEFI Ver : 5.0.250619.BOOT.XF.4.1.2-00023-KAMORTALAZ-5
Platform : IOT
Chip Name : QRB_AGATTI
Chip Ver : 1.0
Chip Serial Number : 0x5C1A0BAC

UEFI Total : 238 ms
POST Time [ 1399] OS Loader
Loader Build Info: May 26 2025 15:58:24
VB: Non-secure device: Security State: (0xF3F)
VB: RWDeviceState: Succeed using devinfo!
GetActiveSlot: First boot: set default slot _a
Total DDR Size: 0x000000007EB00000
KeyPress:0, BootReason:0
Fastboot=0, Recovery:0
GetVmData: making ScmCall to get HypInfo
GetVmData: No Vm data present! Status = (0x3)
VM Hyp calls not present
Find misc_boot Partiton.
misc_boot cookie = 00, Boot Slot is _a
Active Slot _a is bootable, retry count 6
Booting from slot (_a)
Booting Into Mission Mode
Loading Image Start : 1627 ms
Loading Image Done : 1628 ms
Total Image Read size : 4096 Bytes
Loading Image Start : 1628 ms
Loading Image Done : 1631 ms
Total Image Read size : 585728 Bytes
No dtbo partition is found, Skip dtbo
VB: verification skipped for debug builds
GetVmData: making ScmCall to get HypInfo
GetVmData: No Vm data present! Status = (0x3)
No Ffbm cookie found, ignore: Not Found
Memory Base Address: 0x40000000
Decompressing kernel image start: 1633 ms
Decompressing kernel image done: 1647 ms
BootLinux: failed to get dtbo image
DTB offset is incorrect, kernel image does not have appended DTB
No verity command line found
Failed to get LEVerityCmdLine: Not Found
Error getting off mode charging info: Unsupported
Cmdline: root=/dev/notreal androidboot.bootdevice=4744000.sdhci androidboot.serialno=24f95a3 androidboot.baseband=apq

RAM Partitions
Add Base: 0x0000000040000000 Available Length: 0x000000003EB00000
Add Base: 0x0000000080000000 Available Length: 0x0000000040000000
ERROR: Could not get splash memory region node
kaslr-Seed is added to chosen node

Shutting Down UEFI Boot Services: 1653 ms
Start EBS [ 1653]
BDS: LogFs sync skipped, Unsupported
App Log Flush : 145 ms
Exit EBS [ 1811] UEFI End

U-Boot 2026.01-rc3_armbian-2026.01-rc3-S8008-P1a39-H710f-V0e90-Bd0d2-R448a (May 13 2026 - 05:06:39 +0000)

Model: Arduino SA,Imola
DRAM: 2 GiB
Core: 105 devices, 31 uclasses, devicetree: board
WDT: Started watchdog@f017000 with servicing every 1000ms (30s timeout)
MMC: mmc@4744000: 0
Loading Environment from nowhere... OK
In: serial,button-kbd
Out: serial,vidconsole
Err: serial,vidconsole
Model: Arduino SA,Imola
** Read outside partition 2
Net: No ethernet found.
GENI-SE: GENI SE wrapper not found

scanning bus for devices...
starting USB...
No USB controllers found
scanning usb for storage devices... 0 Storage Device(s) found
Hit key to stop autoboot in 1s
3230 bytes read in 20 ms (157.2 KiB/s)

Executing script at 8a800000

Boot script loaded from mmc 0:43
** Reading file would overwrite reserved memory **
Failed to load 'armbianEnv.txt'
"Synchronous Abort" handler, esr 0x96000005, far 0xd4000000
elr: 00000000000abd28 lr : 00000000000a9460 (reloc)
elr: 00000000bfe92d28 lr : 00000000bfe90460
x0 : 00000000afe14b00 x1 : 00000000d4000000
x2 : 0000000000000c9e x3 : 0000000000000000
x4 : 0000000000000c9e x5 : 00000000bfeefa38
x6 : 0000000000000078 x7 : 00000000bfef01a8
x8 : 0000000000009af0 x9 : fffffffffffffff0
x10: 00000000afdebd30 x11: 00000000000f0966
x12: 0000000000000000 x13: 0000000000000004
x14: 00000000bfefca7f x15: 000000013fefca7c
x16: 00000000bfe0b724 x17: 0000000000000000
x18: 00000000afdc7c70 x19: 0000000000000c9e
x20: 0000000000000000 x21: 00000000afe14b00
x22: 0000000000000000 x23: 00000000bfef61b0
x24: 00000000afdb9690 x25: 0000000000000001
x26: 000000000000000a x27: 0000000000000000
x28: 00000000d4000000 x29: 00000000afdb9690

Code: d2800003 eb03005f 540001e1 d65f03c0 (f8636824)
Resetting CPU ...

resetting ...