Looks like I will soon have yet another distraction - Arduino UNO Q

The 8 in 1 USB C Hub arrived and plugged in it powered up and App Lab found it and said ... for the third time:
1761881311005.png

Then again?
1761881620051.png

WIP for sure ... Seems that was updating the "App Lab" that runs on the Q_CPU under linux.
Plugged in HDMI and linux came up there with keyboard and mouse and ran App Lab there.

Builds and runs the same 'Blink LED with UI. Opened a Chromium page to click the Blink. Opened another page to DuckDuckGo search and a normal looking linux desktop.
 
layers of abstraction
Not really what the casual Arduino user of old might expect for sure! Just a bit more involved than writing windows 2 apps in the 80's.

Plugged Ethernet cable and it swapped out of WiFi mode through the 8 in 1 USA adapter.

> assume a recent rPi 3 or 4 would have better perf than this? Viewing over HDMI::
Moving a smaller Chromium window around pushed all four cores over 50%
Quick clicking on the UNO-Q Pin Toggle Example button took all 4 cores to 65-75+% to have the LED toggle a couple times/second.
RAM was 1.2MB of 1.7MB with the taskMgr thing open and the example push button Chromium open and probably the 'App Lab'
Mouse easily moved faster than the menu drop downs responded to highlight - mouse was moving too fast.
 
Been playing around with the Q for the last couple of days developing an actual app that reads imu data from the MCU and processes it on the MPU through a Madgwick filter. Note think we are working on the 2gb version as saw something thats says 4gb wont be out until december.

Basic experience.
1. Yeah boot time is annoying but not overly so. Definitely not instant on. Compile time not horrific. Not like Teensy. Remember teensy and the Q are different beasts. As for comparing with Pi5 - dont have one but have played with the Pi4. But so far different beasts to me.
2. Applab takes some getting use too but not terrible for edit both python code and Arduino code. Makes it simpler to edit to fix the inteface.
3. Once you get the hang of it not bad to transfer data back and forth between the 2 (mpu and mcu) - did find trying to hook up a teensy to the pi was difficult to data transferred easily.
4. Only working in SBC mode over wifi.

Havent tried video etc just still experiementing.

If you want to read more about the app head over to:

You will also see over there a bunch of questions that @KurtE and I have been asking.
 
This 7:23 summary a few hours old - in a word it is 'Weird' power not up to Pi4 level - they call BRICKS the combined INO and linux Python:

Some test specs/notes he exposes here:
 
Note: I have been playing with it and having some fun and ... So far mostly playing at the Arduino level.
I created an excel document that shows all of the GPIO pins... Still WIP... Not sure if anyone will be interested but here is a PDF of it.
 

Attachments

  • uno_q_pin_info.pdf
    595.6 KB · Views: 21
Back
Top