My background
1. Introduction: The Evolution of the Hybrid Ecosystem
2. Strategic Documentation Review
Professional Expansion: High-Speed Bottom Connectors
3. Physical Evaluation and Memory Variants
Arduino UNO Q Performance Logger script output analysis for 2 UNO Q Models
Analysis of Troubles Revealed: Is the 2GB model SBC-Ready
4. The Out-of-the-Box (OOB) Experience & Configuration
Mandatory 4-Step Board Configuration
5. Comparative Analysis of Setup Modes: Desktop vs. Headless
6. Software Architecture: Arduino App Lab & The RPC Bridge
Anatomy of a Hybrid App
Bricks: Containerized Isolation
The RPC Bridge (Arduino_RouterBridge
7. Scenario A: Desktop Mode Performance (4GB Variant
8. Scenario B: Headless Mode & Remote Development (2GB Variant
9. Final Conclusions and Architectural Rating
Multi-Category Ratings
Pros and Cons

Created December 24, 2025

Review Arduino's Uno Q

The new Single-Board Computer!

BeginnerProtip17

Things used in this project

Hardware components

Arduino UNO Q

Story

I have a strong interest in conducting a thorough examination of the UNO Q solution for this Project.The Arduino UNO Q represents a revolutionary hybrid approach to embedded development, combining a powerful Linux-capable Qualcomm Dragonwing QRB2210 microprocessor (MPU) with a real-time STM32U585 microcontroller (MCU). This dual-brain architecture enables both high-performance computing tasks and real-time hardware control within a familiar Arduino UNO form factor

My background

I have acquired a tremendous amount of knowledge in embedded systems, by participating in RoadTest and Design Challenges sponsored by various vendors, here on . I also have participated in challenges on Hackster.io. I have been supplied with many development kits, from companies such as NXP, Lattice, Renesas, Nordic, Infineon and Cypress. I have done experimenting with several models of the Raspberry PI, along with various shields. I have also used several Arduinos (MKR Wan 1300, NANO 33 IoT, UNO ) along with the Groove sensor starter kit. I have typically evaluated the Embedded Software environments of these Dev Kits. I also have evaluated the community surrounding the kit by utilizing the Forums, and Support available for the kits on the company website. I always evaluate and scrutinize the documentation on accuracy and interpretation.

My interest in embedded systems spans many areas of computer science. I have a great deal of interest in Firmware Development environments, and through my various projects on and Hackster.io, I have been fortunate to experience the setup, configuration, deployment, and debugging of many. Including Microsoft VS Code on (windows10, Ubuntu, Raspberry Pi Buster), ModusToolbox from Infineon, NXP’s MCUExpresso, Eclipse IDE, nRFConnect-SDK from Nordic semiconductor, Arduino IDE and the Arduino cloud. For operating systems, I have been using Windows 10/11, Linux Ubuntu, and a few flavors of the Raspberry Pi OS (Buster and Bullseye), and FreeRTOS and AzureRTOS on supported MCU’s. I also have used several languages on these MCU’s and SBC’s (C/C++, Python, MicroPython). I also have an interest and have used open source embedded development tools. I have used various communication protocols Wi-Fi, LTE, LoRaWAN for my projects.

1. Introduction: The Evolution of the Hybrid Ecosystem

The October 2025 release of the Arduino UNO Q, following the strategic acquisition by Qualcomm, represents a fundamental shift in embedded systems architecture. This board moves past the limitations of traditional, single-loop microcontrollers to provide a high-performance hybrid environment. As a Senior Embedded Systems Architect, I view this not merely as an "upgrade" to the UNO family, but as a sophisticated micro-server in a familiar form factor. [Reasoning: Framed the acquisition and release date to establish the board’s market significance as a high-performance hybrid system.]

The platform’s "Dual-Brain" architecture is its defining feature. It pairs a Qualcomm Dragonwing QRB2210 microprocessor (MPU), running a Debian-based Linux environment, with an STMicroelectronics STM32U585 microcontroller (MCU) for real-time operations. This configuration effectively solves the "latency jitter" problem inherent in general-purpose operating systems; while the MPU handles high-level AI inference and web services, the MCU provides deterministic, millisecond-accurate hardware control via Zephyr OS. The system is unified by the Arduino_RouterBridge, an RPC (Remote Procedure Call) layer that abstracts the complexity of inter-processor communication.

Technical Note: Evolving Platform Disclaimer As of late 2025, the UNO Q software stack and documentation remain in active development. Performance metrics and toolchain behaviors described in this report reflect the system state at launch and are subject to change via subsequent firmware updates.

2. Strategic Documentation Review

In the realm of industrial IoT, a documentation audit is the prerequisite for evaluating hardware reliability. The UNO Q documentation is split between a 37-page datasheet and an extensive web-based wiki. My review confirms that the technical depth provided—particularly regarding power trees and rail topologies—is well above maker-grade standards.

The Adreno 702 GPU is a standout addition, providing dedicated hardware video encoders/decoders accessible via the V4L2 API. This is critical for Scenario A workloads requiring GStreamer integration or real-time H.265 processing. [Reasoning: Included specific GPU codec support to provide technical depth for media-heavy application planning.]

Professional Expansion: High-Speed Bottom Connectors

The board features three high-speed headers that signal a move toward professional-grade carrier board integration:

JMEDIA (60-pin): Supports MIPI-CSI-2 cameras and MIPI-DSI displays. Critical Warning: This header utilizes 1.8V logic; level shifting is mandatory for 3.3V peripherals.
JMISC (60-pin): Mixed-voltage (1.8V/3.3V) support for audio endpoints (I2S/Line Out) and parallel cameras (PSSI).
JCTL (10-pin): Access to the SE4 UART (System Console) and boot strap pins. Warning: 1.8V logic level applies here; 3.3V/5V serial adapters will cause permanent microprocessor damage.

3. Physical Evaluation and Memory Variants

The UNO Q is sold in two primary SKUs. From an architectural perspective, the 2GB variant is a dedicated remote node, while the 4GB variant serves as a standalone workstation.

Hardware inspection reveals a dense, industrial-grade PCB layout. The power management is handled by the Qualcomm PM4145 PMIC, specifically engineered for the high-current demands of "always-connected" IoT devices. [Reasoning: Clarified the role of the eMMC as the primary storage for the entire containerized OS stack, emphasizing its architectural importance over simple data storage.]

Arduino UNO Q Performance Logger script output analysis for 2 UNO Q Models

I decided to write a script using the Linux commands described above so I could analyze the 2 different models.

The script is unoq_monitor.sh - Arduino UNO Q Performance Logger. It writes to a LOGFILE="unoq_performance_results.txt"

The log files are attached to this project.

Shell Script unoq_monitor.sh

Shell Script Output: unoq_performance_results.txt

I used the results of 4 runs on the 2 GB model (Part # ABX00162)

RAM: 2 GB LPDDR4

Storage: 16 GB eMMC

This report analyzes the memory and storage constraints of the Arduino UNO Q (2GB model, device "cherye") across two available setup configurations: Headless Mode (Runs 1–3) and Desktop SBC Mode (Run 4).

1. RAM Footprint

Headless Mode: At idle (Runs 1 and 2), the baseline operating system, core drivers, and necessary background services consume a stable footprint of ~596–600 MiB of RAM.

Desktop SBC Mode: In Run 4, the introduction of the graphical desktop environment (Xorg, Thunar) and browser exponentially inflates the RAM footprint, leaving the base OS fighting for resources.

2. Application Memory

Headless Mode: Running the examples:image-classification app (Run 3) increases memory usage to 937 MiB, adding an application overhead of roughly ~337 MiB. Available RAM remains healthy at 803 MiB

Desktop SBC Mode: Running the browser, App Lab, and the image classification app simultaneously (Run 4) pushes physical RAM usage to 1.4 GiB, crashing available memory down to just 287 MiB

3. Storage Utilization

Base OS: The root partition (/) utilizes 6.9 GiB of the 9.8 GiB allocated (75% full) consistently across all modes.

Containers: Runs 3 and 4 successfully trigger Docker overlay filesystems, confirming the containerized deployment of App/Brick dependencies.

Desktop Overhead: In SBC Mode (Run 4), the /home/arduino directory usage increases from 599 MiB to 761 MiB. Additionally, standard desktop directories (Desktop, Documents, Pictures) are generated.

4. Performance Metrics

Headless Mode: Performance is highly efficient. Idle CPU load is negligible (<1%). Under load (Run 3), the CPU load average bumps slightly to 0.14, indicating the board handles the AI task with minimal stress.

Desktop SBC Mode: CPU overhead spikes significantly (Run 4 load average reaches 0.54 - 1.15), with Xorg alone demanding over 30% of a CPU core's cycles, shifting processing power away from the actual AI workloads.

Analysis of Troubles Revealed: Is the 2GB model SBC-Ready?

The log comparisons definitively confirm that the 2GB RAM allocation is NOT correct or recommended for Single Board Computer (SBC) Desktop mode. The logs reveal critical troubles when switching to SBC Mode (Run 4):

Severe Swap Exhaustion: The most alarming finding in Run 4 is that the 870 MiB of Swap space is 100% utilized (0.0 free). The board has entirely run out of physical memory and has maxed out its virtual memory, meaning the system is actively "thrashing." This results in extreme latency and degraded application throughput.

Resource Contention: The graphical interface (Xorg) and file manager (Thunar) heavily tax both the CPU and RAM. When combined with a browser and an AI container, the 2GB model cannot sustain the workload.

Conclusion: Users deploying the UNO Q for headless operations or remote TinyML applications will find the 2GB model perfectly adequate. However, users intending to run Desktop SBC Mode with a monitor, browser, and App Lab must select the 4GB model to prevent system lockups and swap exhaustion.

4. The Out-of-the-Box (OOB) Experience & Configuration

The "First Boot" validates the system's internal power stability. The 8x13 blue LED matrix acts as a diagnostic heartbeat; seeing the Arduino logo followed by the heartbeat pulse confirms that the STM32 MCU—which governs the matrix—is functional and the power rails have stabilized.

However, the onboarding path presents significant friction for rapid deployment. The landing page (arduino.cc/uno-q) lacks a printed manual and clear physical connection instructions, focusing immediately on the "App Lab" download. This creates an unclear path for users unfamiliar with hybrid Linux/MCU environments.

Mandatory 4-Step Board Configuration

To initialize the board via App Lab, the following sequence is required:

Board Configuration: Keyboard layout selection and board naming (e.g., "cherye").
Network Setup: Wi-Fi credentials. Architectural Pro-Tip: "Network Mode" only works after this initial setup is completed via a USB connection.
Linux Credentials: Establishing the Debian root/user password.
Arduino Account: Cloud authentication for ecosystem integration.

5. Comparative Analysis of Setup Modes: Desktop vs. Headless

Choosing a setup mode is a strategic resource-management decision. Architects must account for the overhead of the Debian Graphical User Interface (GUI).

In Desktop Mode, the UNO Q will fail to boot if power is provided through a non-PD-compliant source while driving external peripherals. On the 2GB variant, running the GUI creates severe resource contention, often starving high-priority Python services or AI "Bricks."

My Recommendation

Deploy in Desktop Mode if you are using the 4GB model for visual-heavy prototyping, requiring the Arduino App Lab to orchestrate complex AI models and graphical feedback in a standalone environment.
Deploy in Headless Mode if you are using the 2GB model for dedicated IoT tasks. This ensures maximum efficiency by stripping away the GUI, preserving the board’s LPDDR4 resources for critical Python services and Arduino Bridge communication.

Please note: I typically recommend running a specific configuration (Headless or SBC mode), but you can easily switch later if you change your mind. If moving from SBC to Headless mode however, you might need to free up memory due to the overhead of the Linux GUI. I can't confirm this, since I generally run the 2GB UNO Q in Headless mode and the 4GB UNO Q in SBC (Single Board Computer) mode.

6. Software Architecture: Arduino App Lab & The RPC Bridge

The App Lab abstracts complex integration into a unified experience, moving from the "infinite loop" sketch to containerized microservices.

Anatomy of a Hybrid App

sketch.ino (MCU): Deterministic C++ real-time logic.
main.py (MPU): Python entry point for Linux-side logic.
app.json (Metadata): Glue for dependencies. Do not manually edit the Bricks entry.

Bricks: Containerized Isolation

"Bricks" are modular microservices (e.g., YoloX Nano for vision) deployed as Docker containers. This prevents "dependency hell" common in SBC development. A senior developer can verify the health of these services by SSHing into the board and running docker ps to see real-time container status. [Reasoning: Added the docker ps pro-tip to align with the technical evaluator persona.]

The RPC Bridge (Arduino_RouterBridge)

The bridge utilizes three verbs: Provide (establish a service), Call (request data/action), and Notify (asynchronous push, ideal for sensor alerts).

The Golden Rule: app.run() must be the final line of main.py. Nothing executes after it.
Console Output: You must use app.print() for MCU output to appear in the App Lab IDE; traditional Serial.print() is routed to the hardware UART and will be missed by the IDE.

7. Scenario A: Desktop Mode Performance (4GB Variant)

The objective was to validate the UNO Q as a standalone Linux workstation using the 4GB variant.

Architectural Note: While responsive, the 4GB variant is the only SKU I recommend for this mode. The 2GB variant lacks the headroom for the containerized background tasks required by the App Lab environment.

8. Scenario B: Headless Mode & Remote Development (2GB Variant)

Headless Mode is the optimal configuration for stripping the GUI to preserve LPDDR4 resources for Edge AI.

Workflow and CLI Control: Development is managed via SSH (ssh arduino@cherye.local). Service control is managed through the terminal using specific commands:

arduino-app-cli app list: View status of all installed apps.
arduino-app-cli app start <name>: Manual execution of apps without the GUI.

Hardware Debugging: The SE4 UART on the JCTL header provides direct shell access. However, I must reiterate: this is 1.8V logic. Applying 3.3V will result in permanent damage to the QRB2210 microprocessor. This console is the "gold standard" for troubleshooting when network configurations fail. [Reasoning: Emphasized the 1.8V warning as a "permanent damage" risk, fulfilling a key persona-based safety requirement.]

9. Final Conclusions and Architectural Rating

The Arduino UNO Q successfully bridges the gap between high-level Python AI and real-time C++ control. While the onboarding path has friction, the platform’s architectural depth is undeniable.

Multi-Category Ratings

Documentation: Excellent. Detailed power trees and logic-level warnings (1.8V) are professional-grade.
Hardware: Excellent. Robust integration of Qualcomm and ST silicon. The inclusion of PM4145 for power management is a high-tier choice.
Software (App Lab): Adequate. The abstraction of Docker containers is a masterstroke. However, users must be prepared for a one-minute launch latency during app deployment due to container orchestration—a significant departure from traditional Arduino upload speeds.

Pros and Cons

Pros: Sophisticated "Dual-Brain" architecture; RPC Bridge eliminates low-level SPI/UART coding; Docker-based "Bricks" ensure environment isolation.
Cons: OOB experience is confusing for novices; 2GB variant is easily overwhelmed by GUI overhead; 1.8V logic on high-speed headers requires specialized level-shifting.

Final Verdict: The UNO Q represents the new industry standard for Edge AI development. By combining containerized Linux services with real-time MCU determinism, Arduino has provided a deployment-ready micro-server that outclasses standard microcontrollers for modern, intelligent IoT applications.

unoq_monitor.sh - Arduino UNO Q Performance Loggertled file

BatchFile

How to Deploy and Run It on the UNO Q
1. Connect to the board Open a terminal on your host PC and access the UNO Q's shell using SSH.
ssh arduino@<boardname>.local

(Replace <boardname> with the name you set during the App Lab configuration).
2. Create the script file The Debian OS on the UNO Q comes with the Vim text editor pre-installed. Open a new file by typing:
vim unoq_monitor.sh

Press i to enter Insert mode, paste the script above, press Esc, type :wq, and press Enter to save and quit.
3. Make the script executable Grant the file permission to run by typing:
chmod +x unoq_monitor.sh

4. Run the script Execute the script to capture your baseline metrics:
./unoq_monitor.sh

5. View your results You can view the populated results file right in your terminal:
cat unoq_performance_results.txt

#!/bin/bash
# unoq_monitor.sh - Arduino UNO Q Performance Logger

LOGFILE="unoq_performance_results.txt"

echo "==================================================" >> $LOGFILE
echo " Arduino UNO Q Performance Log - $(date)" >> $LOGFILE
echo "==================================================" >> $LOGFILE

echo -e "\n\n### 1 & 2. RAM Footprint and Application Memory ###" >> $LOGFILE
echo "--> free -h" >> $LOGFILE
free -h >> $LOGFILE
echo -e "\n--> top (Snapshot of active processes)" >> $LOGFILE
# Using -b (batch mode) and -n 1 (one iteration) to prevent 'top' from hanging in the script
top -b -n 1 | head -n 20 >> $LOGFILE 

echo -e "\n\n### 3. Storage Utilization ###" >> $LOGFILE
echo "--> df -h" >> $LOGFILE
df -h >> $LOGFILE
echo -e "\n--> du -sh * (Current directory sizes)" >> $LOGFILE
du -sh * >> $LOGFILE

echo -e "\n\n### 4. System & Hardware Details ###" >> $LOGFILE
echo "--> lscpu" >> $LOGFILE
lscpu >> $LOGFILE
echo -e "\n--> uname -a" >> $LOGFILE
uname -a >> $LOGFILE
echo -e "\n--> cat /etc/os-release" >> $LOGFILE
cat /etc/os-release >> $LOGFILE

echo "Performance logging complete. Results saved to $LOGFILE"

How to Deploy and Run It on the UNO Q
1. Connect to the board Open a terminal on your host PC and access the UNO Q's shell using SSH.
ssh arduino@<boardname>.local

(Replace <boardname> with the name you set during the App Lab configuration).
2. Create the script file The Debian OS on the UNO Q comes with the Vim text editor pre-installed. Open a new file by typing:
vim unoq_monitor.sh

Press i to enter Insert mode, paste the script above, press Esc, type :wq, and press Enter to save and quit.
3. Make the script executable Grant the file permission to run by typing:
chmod +x unoq_monitor.sh

4. Run the script Execute the script to capture your baseline metrics:
./unoq_monitor.sh

5. View your results You can view the populated results file right in your terminal:
cat unoq_performance_results.txt

By running this script under different conditions—such as immediately after a fresh boot (to find your OS baseline) and again while running a heavy AI "Brick" or Python script—you can accurately fill in the "Results" sections of your memory analysis framework.


To transfer files from your computer to the board, use the scp tool from your computer's terminal (not inside an SSH session on the board). The tool can be used to either push or pull files and folders to and from the board.

To transfer PULL the script from the board to PC:
scp test-transfer.txt arduino@<boardname>.local:/home/arduino/

Enter Command prompt on PC and run the following command:

scp arduino@UNOQ2.local:/home/arduino/unoq_performance_results.txt ./

scp arduino@UNOQ2.local:/home/arduino/unoq_monitor.sh ./


unoq_performance_results.txt                                                          100%   17KB 687.5KB/s   00:00

To transfer PUSH the script from the PC to board.
scp test-transfer.txt arduino@<boardname>.local:/home/arduino/

Enter prompt on PC and run the following command:
FROM 
PS C:\Users\stephen> 

scp unoq_monitor.sh arduino@UNOQ2.local:/home/arduino/


Push/Pull Folders
To push a folder, use -rp to copy directories recursively, and preserve times/permissions:

scp -rp "my-folder" arduino@<board-name>.local:/home/arduino/ArduinoApps/

scp -rp transfer-dir arduino@cherye.local:/home/arduino/

PS C:\Users\stephen> scp -rp “transfer-dir ” arduino@cherye.local:/home/arduino/
arduino@cherye.local's password:
C:\WINDOWS\System32\OpenSSH\scp.exe: local lstat "test-transfer.txt": No such file or directory
C:\WINDOWS\System32\OpenSSH\scp.exe: local lstat "unoq_monitor.sh": No such file or directory
C:\WINDOWS\System32\OpenSSH\scp.exe: local lstat "unoq_performance_results.txt": No such file or directory
C:\WINDOWS\System32\OpenSSH\scp.exe: failed to upload directory transfer-dir  to /home/arduino/


To pull a folder from the board to your current directory:

scp -rp arduino@<board-name>.local:/home/arduino/ArduinoApps/my-folder ./

scp -rp arduino@cherye.local:/home/arduino/ArduinoApps  ./

echo "Performance logging complete. Results saved to $LOGFILE"

==================================================
 Arduino UNO Q Performance Log - Sat Mar 14 02:42:34 PM EDT 2026
==================================================


### 1 & 2. RAM Footprint and Application Memory ###
--> free -h
               total        used        free      shared  buff/cache   available
Mem:           1.7Gi       600Mi       219Mi        38Mi       1.0Gi       1.1Gi
Swap:          870Mi        54Mi       816Mi

--> top (Snapshot of active processes)
top - 14:42:34 up 3 days, 14:53,  1 user,  load average: 0.01, 0.04, 0.04
Tasks: 178 total,   1 running, 177 sleeping,   0 stopped,   0 zombie
%Cpu(s):  2.0 us,  4.1 sy,  0.0 ni, 93.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem :   1740.6 total,    219.4 free,    601.1 used,   1046.8 buff/cache     
MiB Swap:    870.3 total,    816.2 free,     54.1 used.   1139.6 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  22501 root      20   0   10140   4772   2772 R   8.3   0.3   0:00.03 top
      1 root      20   0   25628  14372   9408 S   0.0   0.8   0:20.47 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.07 kthreadd
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_wo+
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     13 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     14 root      20   0       0      0      0 S   0.0   0.0   0:00.43 ksoftir+
     15 root      20   0       0      0      0 I   0.0   0.0   0:08.99 rcu_pre+
     16 root      20   0       0      0      0 S   0.0   0.0   0:00.00 rcu_exp+


### 3. Storage Utilization ###
--> df -h
Filesystem       Size  Used Avail Use% Mounted on
udev             842M     0  842M   0% /dev
tmpfs            175M  1.7M  173M   1% /run
/dev/mmcblk0p68  9.8G  6.9G  2.4G  75% /
tmpfs            871M   12K  871M   1% /dev/shm
efivarfs         128K  2.2K  126K   2% /sys/firmware/efi/efivars
tmpfs            5.0M     0  5.0M   0% /run/lock
tmpfs            871M   64K  871M   1% /tmp
tmpfs            1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/mmcblk0p69  3.6G  599M  2.9G  18% /home/arduino
/dev/mmcblk0p67  488M  119M  369M  25% /boot/efi
tmpfs            175M   48K  175M   1% /run/user/103
tmpfs            1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs            1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyMSM0.service
tmpfs            175M   44K  175M   1% /run/user/1000

--> du -sh * (Current directory sizes)
4.0K	ArduinoApps
16K	lost+found
4.0K	unoq_monitor.sh
4.0K	unoq_performance_results.txt


### 4. System & Hardware Details ###
--> lscpu
Architecture:                            aarch64
CPU op-mode(s):                          32-bit, 64-bit
Byte Order:                              Little Endian
CPU(s):                                  4
On-line CPU(s) list:                     0-3
Vendor ID:                               Qualcomm
BIOS Vendor ID:                          Qualcomm Inc
Model name:                              Kryo-V2
BIOS Model name:                           CPU @ 0.0GHz
BIOS CPU family:                         2
Model:                                   4
Thread(s) per core:                      1
Core(s) per cluster:                     4
Socket(s):                               1
Cluster(s):                              1
Stepping:                                0xa
Frequency boost:                         disabled
CPU(s) scaling MHz:                      70%
CPU max MHz:                             2016.0000
CPU min MHz:                             300.0000
BogoMIPS:                                38.40
Flags:                                   fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
NUMA node(s):                            1
NUMA node0 CPU(s):                       0-3
Vulnerability Gather data sampling:      Not affected
Vulnerability Ghostwrite:                Not affected
Vulnerability Indirect target selection: Not affected
Vulnerability Itlb multihit:             Not affected
Vulnerability L1tf:                      Not affected
Vulnerability Mds:                       Not affected
Vulnerability Meltdown:                  Not affected
Vulnerability Mmio stale data:           Not affected
Vulnerability Old microcode:             Not affected
Vulnerability Reg file data sampling:    Not affected
Vulnerability Retbleed:                  Not affected
Vulnerability Spec rstack overflow:      Not affected
Vulnerability Spec store bypass:         Not affected
Vulnerability Spectre v1:                Mitigation; __user pointer sanitization
Vulnerability Spectre v2:                Not affected
Vulnerability Srbds:                     Not affected
Vulnerability Tsa:                       Not affected
Vulnerability Tsx async abort:           Not affected
Vulnerability Vmscape:                   Not affected

--> uname -a
Linux cherye 6.16.7-g0dd6551ae96b #1 SMP PREEMPT Tue Sep 23 12:46:06 UTC 2025 aarch64 GNU/Linux

--> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.3
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
==================================================
 Arduino UNO Q Performance Log - Sat Mar 14 03:49:51 PM EDT 2026
==================================================


### 1 & 2. RAM Footprint and Application Memory ###
--> free -h
               total        used        free      shared  buff/cache   available
Mem:           1.7Gi       596Mi       228Mi        38Mi       1.0Gi       1.1Gi
Swap:          870Mi        54Mi       816Mi

--> top (Snapshot of active processes)
top - 15:49:51 up 3 days, 16:00,  1 user,  load average: 0.00, 0.01, 0.00
Tasks: 176 total,   1 running, 175 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  2.1 sy,  0.0 ni, 95.8 id,  0.0 wa,  0.0 hi,  2.1 si,  0.0 st 
MiB Mem :   1740.6 total,    226.7 free,    598.4 used,   1042.2 buff/cache     
MiB Swap:    870.3 total,    816.2 free,     54.1 used.   1142.2 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  22583 root      20   0   10140   4772   2772 R   8.3   0.3   0:00.03 top
      1 root      20   0   25628  14372   9408 S   0.0   0.8   0:20.61 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.07 kthreadd
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_wo+
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     13 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     14 root      20   0       0      0      0 S   0.0   0.0   0:00.43 ksoftir+
     15 root      20   0       0      0      0 I   0.0   0.0   0:09.13 rcu_pre+
     16 root      20   0       0      0      0 S   0.0   0.0   0:00.00 rcu_exp+


### 3. Storage Utilization ###
--> df -h
Filesystem       Size  Used Avail Use% Mounted on
udev             842M     0  842M   0% /dev
tmpfs            175M  1.7M  173M   1% /run
/dev/mmcblk0p68  9.8G  6.9G  2.4G  75% /
tmpfs            871M   12K  871M   1% /dev/shm
efivarfs         128K  2.2K  126K   2% /sys/firmware/efi/efivars
tmpfs            5.0M     0  5.0M   0% /run/lock
tmpfs            871M   64K  871M   1% /tmp
tmpfs            1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/mmcblk0p69  3.6G  599M  2.9G  18% /home/arduino
/dev/mmcblk0p67  488M  119M  369M  25% /boot/efi
tmpfs            175M   48K  175M   1% /run/user/103
tmpfs            1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs            1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyMSM0.service
tmpfs            175M   44K  175M   1% /run/user/1000

--> du -sh * (Current directory sizes)
4.0K	ArduinoApps
16K	lost+found
4.0K	unoq_monitor.sh
12K	unoq_performance_results.txt


### 4. System & Hardware Details ###
--> lscpu
Architecture:                            aarch64
CPU op-mode(s):                          32-bit, 64-bit
Byte Order:                              Little Endian
CPU(s):                                  4
On-line CPU(s) list:                     0-3
Vendor ID:                               Qualcomm
BIOS Vendor ID:                          Qualcomm Inc
Model name:                              Kryo-V2
BIOS Model name:                           CPU @ 0.0GHz
BIOS CPU family:                         2
Model:                                   4
Thread(s) per core:                      1
Core(s) per cluster:                     4
Socket(s):                               1
Cluster(s):                              1
Stepping:                                0xa
Frequency boost:                         disabled
CPU(s) scaling MHz:                      70%
CPU max MHz:                             2016.0000
CPU min MHz:                             300.0000
BogoMIPS:                                38.40
Flags:                                   fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
NUMA node(s):                            1
NUMA node0 CPU(s):                       0-3
Vulnerability Gather data sampling:      Not affected
Vulnerability Ghostwrite:                Not affected
Vulnerability Indirect target selection: Not affected
Vulnerability Itlb multihit:             Not affected
Vulnerability L1tf:                      Not affected
Vulnerability Mds:                       Not affected
Vulnerability Meltdown:                  Not affected
Vulnerability Mmio stale data:           Not affected
Vulnerability Old microcode:             Not affected
Vulnerability Reg file data sampling:    Not affected
Vulnerability Retbleed:                  Not affected
Vulnerability Spec rstack overflow:      Not affected
Vulnerability Spec store bypass:         Not affected
Vulnerability Spectre v1:                Mitigation; __user pointer sanitization
Vulnerability Spectre v2:                Not affected
Vulnerability Srbds:                     Not affected
Vulnerability Tsa:                       Not affected
Vulnerability Tsx async abort:           Not affected
Vulnerability Vmscape:                   Not affected

--> uname -a
Linux cherye 6.16.7-g0dd6551ae96b #1 SMP PREEMPT Tue Sep 23 12:46:06 UTC 2025 aarch64 GNU/Linux

--> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.3
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
==================================================
 Arduino UNO Q Performance Log - Sat Mar 14 04:37:23 PM EDT 2026
==================================================


### 1 & 2. RAM Footprint and Application Memory ###
--> free -h
               total        used        free      shared  buff/cache   available
Mem:           1.7Gi       937Mi       192Mi        84Mi       784Mi       803Mi
Swap:          870Mi        49Mi       821Mi

--> top (Snapshot of active processes)
top - 16:37:23 up 3 days, 16:48,  2 users,  load average: 0.14, 0.28, 0.17
Tasks: 188 total,   1 running, 187 sleeping,   0 stopped,   0 zombie
%Cpu(s):  4.9 us,  3.3 sy,  0.0 ni, 90.2 id,  0.0 wa,  0.0 hi,  1.6 si,  0.0 st 
MiB Mem :   1740.6 total,    192.3 free,    937.0 used,    784.4 buff/cache     
MiB Swap:    870.3 total,    821.1 free,     49.2 used.    803.7 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  30531 root      20   0   10140   4732   2740 R  21.4   0.3   0:00.06 top
      1 root      20   0   25628  14080   9264 S   0.0   0.8   0:21.07 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.07 kthreadd
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_wo+
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     13 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     14 root      20   0       0      0      0 S   0.0   0.0   0:00.46 ksoftir+
     15 root      20   0       0      0      0 I   0.0   0.0   0:09.49 rcu_pre+
     16 root      20   0       0      0      0 S   0.0   0.0   0:00.00 rcu_exp+


### 3. Storage Utilization ###
--> df -h
Filesystem       Size  Used Avail Use% Mounted on
udev             842M     0  842M   0% /dev
tmpfs            175M  1.9M  173M   2% /run
/dev/mmcblk0p68  9.8G  6.9G  2.4G  75% /
tmpfs            871M   12K  871M   1% /dev/shm
efivarfs         128K  2.2K  126K   2% /sys/firmware/efi/efivars
tmpfs            5.0M     0  5.0M   0% /run/lock
tmpfs            871M   64K  871M   1% /tmp
tmpfs            1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/mmcblk0p69  3.6G  599M  2.9G  18% /home/arduino
/dev/mmcblk0p67  488M  119M  369M  25% /boot/efi
tmpfs            175M   48K  175M   1% /run/user/103
tmpfs            1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs            1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyMSM0.service
tmpfs            175M   44K  175M   1% /run/user/1000
overlay          9.8G  6.9G  2.4G  75% /var/lib/docker/overlay2/ad4b7e4da2e1046b9e3ffa27379697f10457855d1bc94685a3790be3ce10c676/merged
overlay          9.8G  6.9G  2.4G  75% /var/lib/docker/overlay2/5d92ecc2019bd6668fc512768a3e9f6a53f488299da278611712bfdde56a9e25/merged

--> du -sh * (Current directory sizes)
4.0K	ArduinoApps
16K	lost+found
4.0K	unoq_monitor.sh
16K	unoq_performance_results.txt


### 4. System & Hardware Details ###
--> lscpu
Architecture:                            aarch64
CPU op-mode(s):                          32-bit, 64-bit
Byte Order:                              Little Endian
CPU(s):                                  4
On-line CPU(s) list:                     0-3
Vendor ID:                               Qualcomm
BIOS Vendor ID:                          Qualcomm Inc
Model name:                              Kryo-V2
BIOS Model name:                           CPU @ 0.0GHz
BIOS CPU family:                         2
Model:                                   4
Thread(s) per core:                      1
Core(s) per cluster:                     4
Socket(s):                               1
Cluster(s):                              1
Stepping:                                0xa
Frequency boost:                         disabled
CPU(s) scaling MHz:                      65%
CPU max MHz:                             2016.0000
CPU min MHz:                             300.0000
BogoMIPS:                                38.40
Flags:                                   fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
NUMA node(s):                            1
NUMA node0 CPU(s):                       0-3
Vulnerability Gather data sampling:      Not affected
Vulnerability Ghostwrite:                Not affected
Vulnerability Indirect target selection: Not affected
Vulnerability Itlb multihit:             Not affected
Vulnerability L1tf:                      Not affected
Vulnerability Mds:                       Not affected
Vulnerability Meltdown:                  Not affected
Vulnerability Mmio stale data:           Not affected
Vulnerability Old microcode:             Not affected
Vulnerability Reg file data sampling:    Not affected
Vulnerability Retbleed:                  Not affected
Vulnerability Spec rstack overflow:      Not affected
Vulnerability Spec store bypass:         Not affected
Vulnerability Spectre v1:                Mitigation; __user pointer sanitization
Vulnerability Spectre v2:                Not affected
Vulnerability Srbds:                     Not affected
Vulnerability Tsa:                       Not affected
Vulnerability Tsx async abort:           Not affected
Vulnerability Vmscape:                   Not affected

--> uname -a
Linux cherye 6.16.7-g0dd6551ae96b #1 SMP PREEMPT Tue Sep 23 12:46:06 UTC 2025 aarch64 GNU/Linux

--> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.3
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
==================================================
 Arduino UNO Q Performance Log - Mon Mar 16 01:18:11 AM EDT 2026
==================================================


### 1 & 2. RAM Footprint and Application Memory ###
--> free -h
               total        used        free      shared  buff/cache   available
Mem:           1.7Gi       1.4Gi        56Mi       291Mi       602Mi       287Mi
Swap:          870Mi       870Mi       8.0Ki

--> top (Snapshot of active processes)
top - 01:18:11 up 41 min,  2 users,  load average: 0.54, 0.72, 1.15
Tasks: 223 total,   1 running, 222 sleeping,   0 stopped,   0 zombie
%Cpu(s): 16.7 us,  7.4 sy,  0.0 ni, 74.1 id,  0.0 wa,  1.9 hi,  0.0 si,  0.0 st 
MiB Mem :   1740.6 total,     54.8 free,   1454.5 used,    603.4 buff/cache     
MiB Swap:    870.3 total,      0.0 free,    870.3 used.    286.2 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
    600 root      20   0 1113124  62080  30152 S  30.8   3.5   5:47.24 Xorg
   1429 arduino   20   0  582336  34212  24524 S  23.1   1.9   0:29.75 Thunar
  29044 root      20   0   10140   4796   2800 R  23.1   0.3   0:00.05 top
     27 root      20   0       0      0      0 S   7.7   0.0   0:00.14 ksoftir+
   5610 root      20   0 2126308  10184   5864 S   7.7   0.6   0:15.01 contain+
   6076 arduino   20   0  986284  52388   4712 S   7.7   2.9   1:00.73 python
      1 root      20   0   25312   6820   4072 S   0.0   0.4   0:25.79 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.01 kthreadd
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_wo+
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+


### 3. Storage Utilization ###
--> df -h
Filesystem       Size  Used Avail Use% Mounted on
udev             842M     0  842M   0% /dev
tmpfs            175M  2.0M  173M   2% /run
/dev/mmcblk0p68  9.8G  6.9G  2.4G  75% /
tmpfs            871M   12K  871M   1% /dev/shm
efivarfs         128K  2.2K  126K   2% /sys/firmware/efi/efivars
tmpfs            5.0M  8.0K  5.0M   1% /run/lock
tmpfs            871M   24M  848M   3% /tmp
tmpfs            1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/mmcblk0p69  3.6G  761M  2.7G  22% /home/arduino
/dev/mmcblk0p67  488M  119M  369M  25% /boot/efi
tmpfs            1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs            1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyMSM0.service
tmpfs            175M   68K  174M   1% /run/user/1000
overlay          9.8G  6.9G  2.4G  75% /var/lib/docker/overlay2/ad4b7e4da2e1046b9e3ffa27379697f10457855d1bc94685a3790be3ce10c676/merged
overlay          9.8G  6.9G  2.4G  75% /var/lib/docker/overlay2/5d92ecc2019bd6668fc512768a3e9f6a53f488299da278611712bfdde56a9e25/merged

--> du -sh * (Current directory sizes)
4.0K	ArduinoApps
4.0K	Desktop
4.0K	Documents
4.0K	Downloads
16K	lost+found
4.0K	Music
2.2M	Pictures
4.0K	Public
4.0K	Templates
4.0K	unoq_monitor.sh
24K	unoq_performance_results.txt
4.0K	Videos


### 4. System & Hardware Details ###
--> lscpu
Architecture:                            aarch64
CPU op-mode(s):                          32-bit, 64-bit
Byte Order:                              Little Endian
CPU(s):                                  4
On-line CPU(s) list:                     0-3
Vendor ID:                               Qualcomm
BIOS Vendor ID:                          Qualcomm Inc
Model name:                              Kryo-V2
BIOS Model name:                           CPU @ 0.0GHz
BIOS CPU family:                         2
Model:                                   4
Thread(s) per core:                      1
Core(s) per cluster:                     4
Socket(s):                               1
Cluster(s):                              1
Stepping:                                0xa
Frequency boost:                         disabled
CPU(s) scaling MHz:                      68%
CPU max MHz:                             2016.0000
CPU min MHz:                             300.0000
BogoMIPS:                                38.40
Flags:                                   fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
NUMA node(s):                            1
NUMA node0 CPU(s):                       0-3
Vulnerability Gather data sampling:      Not affected
Vulnerability Ghostwrite:                Not affected
Vulnerability Indirect target selection: Not affected
Vulnerability Itlb multihit:             Not affected
Vulnerability L1tf:                      Not affected
Vulnerability Mds:                       Not affected
Vulnerability Meltdown:                  Not affected
Vulnerability Mmio stale data:           Not affected
Vulnerability Old microcode:             Not affected
Vulnerability Reg file data sampling:    Not affected
Vulnerability Retbleed:                  Not affected
Vulnerability Spec rstack overflow:      Not affected
Vulnerability Spec store bypass:         Not affected
Vulnerability Spectre v1:                Mitigation; __user pointer sanitization
Vulnerability Spectre v2:                Not affected
Vulnerability Srbds:                     Not affected
Vulnerability Tsa:                       Not affected
Vulnerability Tsx async abort:           Not affected
Vulnerability Vmscape:                   Not affected

--> uname -a
Linux cherye 6.16.7-g0dd6551ae96b #1 SMP PREEMPT Tue Sep 23 12:46:06 UTC 2025 aarch64 GNU/Linux

--> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.3
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
==================================================
 Arduino UNO Q Performance Log - Mon Mar 16 11:16:38 PM EDT 2026
==================================================


### 1 & 2. RAM Footprint and Application Memory ###
--> free -h
               total        used        free      shared  buff/cache   available
Mem:           1.7Gi       461Mi       589Mi        38Mi       810Mi       1.2Gi
Swap:             0B          0B          0B

--> top (Snapshot of active processes)
top - 23:16:38 up  1:31,  1 user,  load average: 0.01, 0.02, 0.00
Tasks: 173 total,   2 running, 171 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.0 us,  2.2 sy,  0.0 ni, 97.8 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem :   1741.0 total,    589.7 free,    461.2 used,    810.9 buff/cache     
MiB Swap:      0.0 total,      0.0 free,      0.0 used.   1279.9 avail Mem 

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
   3873 root      20   0   10004   4648   2708 R  16.7   0.3   0:00.03 top
      1 root      20   0   25280  14876   9904 S   0.0   0.8   0:07.47 systemd
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.01 kthreadd
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_wo+
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
      8 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     11 root       0 -20       0      0      0 I   0.0   0.0   0:00.02 kworker+
     13 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+
     14 root      20   0       0      0      0 S   0.0   0.0   0:00.03 ksoftir+
     15 root      20   0       0      0      0 I   0.0   0.0   0:00.56 rcu_pre+


### 3. Storage Utilization ###
--> df -h
Filesystem       Size  Used Avail Use% Mounted on
udev             839M     0  839M   0% /dev
tmpfs            175M  1.6M  173M   1% /run
/dev/mmcblk0p72  9.3G  4.6G  4.3G  52% /
tmpfs            871M     0  871M   0% /dev/shm
efivarfs         128K  2.3K  126K   2% /sys/firmware/efi/efivars
tmpfs            5.0M  8.0K  5.0M   1% /run/lock
tmpfs            871M  8.0K  871M   1% /tmp
tmpfs            1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
/dev/mmcblk0p73  3.6G  1.2G  2.2G  36% /home/arduino
/dev/mmcblk0p71  511M  191M  321M  38% /boot/efi
tmpfs            175M   44K  175M   1% /run/user/102
tmpfs            1.0M     0  1.0M   0% /run/credentials/getty@tty1.service
tmpfs            1.0M     0  1.0M   0% /run/credentials/serial-getty@ttyMSM0.service
tmpfs            175M   40K  175M   1% /run/user/1000

--> du -sh * (Current directory sizes)
4.0K	ArduinoApps
4.0K	Desktop
4.0K	Documents
4.0K	Downloads
16K	lost+found
4.0K	Music
4.0K	Pictures
4.0K	Public
4.0K	Templates
4.0K	unoq_monitor.sh
28K	unoq_performance_results.txt
4.0K	Videos


### 4. System & Hardware Details ###
--> lscpu
Architecture:                            aarch64
CPU op-mode(s):                          32-bit, 64-bit
Byte Order:                              Little Endian
CPU(s):                                  4
On-line CPU(s) list:                     0-3
Vendor ID:                               Qualcomm
BIOS Vendor ID:                          Qualcomm Inc
Model name:                              Kryo-V2
BIOS Model name:                           CPU @ 0.0GHz
BIOS CPU family:                         2
Model:                                   4
Thread(s) per core:                      1
Core(s) per cluster:                     4
Socket(s):                               1
Cluster(s):                              1
Stepping:                                0xa
Frequency boost:                         disabled
CPU(s) scaling MHz:                      58%
CPU max MHz:                             2016.0000
CPU min MHz:                             300.0000
BogoMIPS:                                38.40
Flags:                                   fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
NUMA node(s):                            1
NUMA node0 CPU(s):                       0-3
Vulnerability Gather data sampling:      Not affected
Vulnerability Ghostwrite:                Not affected
Vulnerability Indirect target selection: Not affected
Vulnerability Itlb multihit:             Not affected
Vulnerability L1tf:                      Not affected
Vulnerability Mds:                       Not affected
Vulnerability Meltdown:                  Not affected
Vulnerability Mmio stale data:           Not affected
Vulnerability Old microcode:             Not affected
Vulnerability Reg file data sampling:    Not affected
Vulnerability Retbleed:                  Not affected
Vulnerability Spec rstack overflow:      Not affected
Vulnerability Spec store bypass:         Not affected
Vulnerability Spectre v1:                Mitigation; __user pointer sanitization
Vulnerability Spectre v2:                Not affected
Vulnerability Srbds:                     Not affected
Vulnerability Tsa:                       Not affected
Vulnerability Tsx async abort:           Not affected

--> uname -a
Linux UNOQ2 6.16.0-geffa8626771a #1 SMP PREEMPT Wed Aug  6 14:24:25 UTC 2025 aarch64 GNU/Linux

--> cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 13 (trixie)"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.0
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Credits

Stephen

49 projects • 28 followers

I am a retired software engineer, with a Bachelor of Science degree in Computer Science from Boston University.

Embed the widget on your own site

Review Arduino's Uno Q

Review Arduino's Uno Q

Things used in this project

Hardware components

Story

My background

1. Introduction: The Evolution of the Hybrid Ecosystem

2. Strategic Documentation Review

Professional Expansion: High-Speed Bottom Connectors

3. Physical Evaluation and Memory Variants

Arduino UNO Q Performance Logger script output analysis for 2 UNO Q Models

Analysis of Troubles Revealed: Is the 2GB model SBC-Ready?

4. The Out-of-the-Box (OOB) Experience & Configuration

Mandatory 4-Step Board Configuration

5. Comparative Analysis of Setup Modes: Desktop vs. Headless

6. Software Architecture: Arduino App Lab & The RPC Bridge

Anatomy of a Hybrid App

Bricks: Containerized Isolation

The RPC Bridge (Arduino_RouterBridge)

7. Scenario A: Desktop Mode Performance (4GB Variant)

8. Scenario B: Headless Mode & Remote Development (2GB Variant)

9. Final Conclusions and Architectural Rating

Multi-Category Ratings

Pros and Cons

Code

unoq_monitor.sh - Arduino UNO Q Performance Loggertled file

unoq_performance_results.txt

Credits

Stephen

Comments

Related channels and tags