Hi, i got the 2gb Arduino UNO Q back in October. I haven't had a problem with it until today, my UNO Q was working fine today until i flashed it. After I flashed it whenever i would connect it to a USB-C to C cord it would start booting then reset continuously, but on a USB A to C cord it would just loop the bootloader animation. Power is going through the pins but my pc wont recognize it with USB. My pc does recognize the Bluetooth but it wont connect. i suspect that the problem was because of my mac. when i tried flashing it i didn't have the jumper on but allowing apples popup allowed the uno q to bypass the EDL restrictions, i tried reflashing the board multiple times but i think the problem has something to do with a lower level program inside the arduino. what can i do to fix this? thank you.
Hi @yousifmussa. Did the flashing process complete successfully the last time you attempted it?
yes the flashing process completed successfully in both the first time and the later attempts
After connecting power, the Arduino UNO Q displays an animation on the LED matrix. At the end of the animation, the board is recognized by the PC.
In your case, the animation never ends, and the board is not recognized. Under these conditions, updating the board is not possible, as EDL mode requires a functional USB connection.
My UNO Q worked for about two months, but then it suddenly stopped showing the animation and was no longer recognized. The board now appears to be out of order.
That sounds like the flash might’ve messed up the bootloader or put it in a weird state. I’ve had something similar where forcing it back into recovery/EDL mode with the jumper properly set and then reflashing fixed it, but it took a couple tries. You might also want to try a different machine (like Windows) just to rule out the Mac doing something odd during the flash.
UPDATE:
I got my hands on a USB to TTL adapter, and i found the exact issue of my UNO Q board:
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 = 0x5ca29d5c
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 - 5511 - pbl_apps_init_timestamp
D - 106193 - bootable_media_detect_timestamp
D - 3648 - bl_elf_metadata_loading_timestamp
D - 701 - bl_hash_seg_auth_timestamp
D - 16123 - bl_elf_loadable_segment_loading_timestamp
D - 4056 - bl_elf_segs_hash_verify_timestamp
D - 17425 - bl_sec_hash_seg_auth_timestamp
D - 862 - bl_sec_segs_hash_verify_timestamp
D - 32 - pbl_populate_shared_data_and_exit_timestamp
S - 154551 - PBL, End
B - 171737 - SBL1, Start (MPM timestamp = 171257)
B - 285390 - SBL1 BUILD @ 18:02:00 on Jun 19 2025
B - 290720 - usb: hs_phy_nondrive_start
B - 295087 - usb: hs_phy_nondrive_finish
D - 8528 - sbl1_hw_init
D - 12 - boot_flash_init
B - 330189 - Using boot chain :: Primary
D - 25074 - sbl1_update_partition_ids
D - 957 - Auth Metadata
D - 7483 - 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 - 4136 - boot_config_data_table_init
B - 357322 - CDT Version:3,Platform ID:32,Major ID:1,Minor ID:0,Subtype:1
D - 9483 - sbl1_hw_platform_pre_ddr
D - 4982 - devcfg init
B - 381283 - PM: Device Init # SPMI Transn: 10
B - 381319 - Mem dump cmd, entry
D - 8 - Mem dump cmd, exit
B - 388981 - Error code 22000080 at sbl1_hw.c Line 573
B - 392120 - ^^^^- Printing Call Stack -^^^^
B - 397252 - func_addr : 0C22FBCC
B - 401513 - func_addr : 0C23B434
B - 405085 - func_addr : 0C23B6F0
B - 408655 - func_addr : 0C23BC3C
B - 412227 - func_addr : 0C22F4E0
B - 415798 - func_addr : 0C2259A8
B - 419370 - ^^^^^- Done Printing -^^^^
this section of code keeps repeating due to a 22000080 error code, can anyone help me fix this error?
The UART (0, 1) port on the MCU side appears to be functional. What about the USB-C connection? It must also be in working condition for the UNO Q board to function.
the USB connection is working and power is going through the board, i think the problem is the code of the bootloader itself. the error code shows a problem with sbl1 which i believe stands for S??? bootloader 1. this also could be what's impacting the C to C power negotiation.
When you connect the UNO Q board to the PC using the USB-C connector, does the LED matrix display the startup animation and end with a heart symbol? After that, please open the Device Manager and check whether the board is recognized under the COM ports. These events indicate that the UNO Q board is functional.
the issue with my board is that it does start up the animation with the Arduino logo but it loops continuously it cannot get to the heartbeat animation. the power is going through all the pins but because it cannot finish the animation due to the error code it cannot transmit or receive any data.
That means that the USB-C connection is not working; the board is non-functional. How long ago did you purchase the board? My board survived only for two months.
when it was on preorder before october is when i bought it
Thank you so much for your help
Why did you buy the board - to learn 32-bit MCU, 64-bit MPU, Linux OS, Zephyr RTOS, C++, Python, HTML, networking, signal processing, image processing, video processing, audio processing, etc.?
i bought it for a project that would utilize both the Linux and sketch functionalities of the board
sorry for your troubles..
curious, in your original post you mention different operations depending upon which cable you used usb-c to usb-c and usb-a to usb-c..
which cable did you use when you captured the boot log??
is the log different when using the other cable??
what happens in the logs if you use a sturdy 5vdc usb-c power adapter like 3amps??
good luck.. ~q
Hi, I had the same problem too. I found 2 problems / solutions:
- If the boot animation is stuck, it may not like the cable. Yes, this does actually occur. I thought there was something wrong with my first Arduino Uno Q and it turned out that the Uno Q sometimes is picky with a cable. If one cable keeps isn't making the board boot, I try another cable and it works.
- If the boot animation is stuck, it didn't boot correctly. Like Windows, if the computer fails booting twice Windows will see what's wrong. This doesn't apply to Debian 13 (Trixie). Failed boots often lead to a BusyBox terminal, a blinking cursor, or a kernel panic, which remain until you fix the issue.
Hope this helps!