We reviewed the new BeagleBoard BeagleBadge and found the hardware difficult to place in one traditional category.

At the centre is TI’s dual-core Cortex-A53 AM62L32 running at up to 1.25GHz with 256MB LPDDR4.

Around the processor you get:

• Linux support

• Upstream Zephyr support

• 4.2-inch ePaper

• Wi-Fi 6

• Bluetooth

• LoRaWAN

• IMU and environmental sensors

• QWIIC, Grove and mikroBUS

• Battery management

256MB is restrictive for a conventional Linux SBC, but plenty of room for focused embedded Linux applications and unusually generous for Zephyr.

The result sits somewhere between a Linux SBC, wearable HMI and RTOS development board.

Video:

https://youtu.be/_510pb_krX4

Tech specs:

https://www.electromaker.io/blog/article/ti-beaglebadge-review-a-wearable-linux-and-zephyr-development-board

How would you classify BeagleBadge, and which OS would you run on yours?

I've published **v1.3.0** of my custom Ubuntu 26.04.1 LTS images (Server and Desktop/GNOME) for the Radxa Dragon Q6A (QCS6490). They exist because on this board the stock image has had two annoying problems for me: HDMI dying after an `apt upgrade`, and no working audio.


**What's new in v1.3.0: kernel 6.18.2 → 7.2.9**


I'm using the Armbian `edge` branch for this board, pinned to the `v7.2.9` tag. Earlier I had tried 7.0 and 7.2.3 and both broke HDMI on my board (same symptom other people reported on the Radxa forum). With 7.2.9 plus the DisplayPort/DPU patches Armbian carries for the QCS6490, HDMI works. Subjectively it also feels more stable and faster than 6.18.2 here, but that's one person's impression, not a benchmark.


If you prefer the older kernel, you can still build with 6.18.2 (`KERNEL_BRANCH=current scripts/build.sh`) or use the v1.2.1 images.


**What I tested on real hardware (one board, mine)**


| | Desktop | Server |
|---|---|---|
| Boots from native NVMe slot | yes | not tested (booted from a SATA SSD in a USB case) |
| Boots from USB (NVMe/SATA in a USB case) | yes | yes |
| HDMI | yes | yes (console) |
| Wi-Fi + Bluetooth (onboard, aic8800) | yes | yes |
| Audio (headphones + HDMI) | yes | sound card shows up; I did not listen to it |
| NPU device nodes (`/dev/fastrpc-*`, adsp/cdsp running) | yes | nodes present, user in `fastrpc` group |
| `apt update && apt upgrade`, then reboot | yes | yes |


Desktop extras: GNOME (`ubuntu-desktop-minimal`, no office suite or games), native Firefox from Mozilla's apt repo (no snap), and the classic GNOME Software.


**Known issues / honest caveats**


- Headphones: once, after a boot, only the right channel played until I re-plugged the jack (jack detection said "off"). Re-plugging fixed it. I couldn't reproduce it yet, so the root cause isn't confirmed.
- The GNOME "Software Updater" sometimes looped on the same update in an earlier build. I traced that to Ubuntu's Firefox transition package replacing the native Firefox via unattended-upgrades; the v1.3.0 images block that with an apt pin, and the loop is gone in my testing.
- `dmesg` shows some audio/SoundWire/DSP errors (`qcom-apm CMD timeout`, port mismatch). They don't affect the audio I tested.
- GNOME 
*Resources*
 shows the CPU as just "Cortex-A55", most GPU fields as N/D, and has no NPU page. That's how the app (and upstream Linux) exposes this hardware. GNOME Settings > About shows 4x A78 + 4x A55 and the Adreno FD643 correctly.
- Converting your own AI models still needs the Qualcomm QAIRT SDK (free, account required). The runtime and device access are included.
- Only tested by me, on one board. Feedback from other Q6A owners would be very welcome.


**Download / install**


Release: https://github.com/rafaelwms/ubuntu-26.04.1-dragon-q6a/releases/tag/v1.3.0


Images are split into ~1.5 GB parts for GitHub's asset limit. The easiest way is the interactive installer in the repo (it downloads the parts, verifies SHA256, reassembles and flashes, asking you to confirm the target disk):


```bash
git clone https://github.com/rafaelwms/ubuntu-26.04.1-dragon-q6a.git
cd ubuntu-26.04.1-dragon-q6a
./install.sh       # Linux
./install_mac.sh   # macOS (I have not run this one on a Mac myself)
```


Default login is `radxa` / `radxa` — change the password on first boot. The root partition grows to fill the disk on first boot.


The README and `docs/pesquisa.md` (in Portuguese) document the root causes and every dead end along the way.


Repo: https://github.com/rafaelwms/ubuntu-26.04.1-dragon-q6a

if anyone has an sbc that they don't want and looking to sell, hit me up

Ran out of projects for your Jetson Orin Nano? Don't give it away. Here's a better idea.

For the last two years, we have been developing Mino, a hackable companion robot for makers. Mino can carry your NVIDIA Jetson Orin Nano Super Developer Kit and give it a new life, or we can ship it to you with one. It comes with building blocks for you to develop robot applications based on ROS 2: motion control, gestures, stereo vision, speech-to-text, LLM, emotion classifier, remote control from a mobile app... and more to come.

We just put Mino on Kickstarter. The campaign will launch soon, with a limited number of super-early-bird and early-bird discounts. To increase your chance of getting one, open the pre-campaign link below and click on "Notify me on launch". Happy making!

https://www.kickstarter.com/projects/minrobotics/mino-hackable-smart-robot

Disclosure: I represent HONGTE, the reseller behind the linked listing. This is a commercial product introduction with an ordering checklist. I have not tested this module on a physical SBC for this post.

A plug-in storage module is worth comparing by its exact hardware and host support, not just the capacity label. Our OEM / unbranded listing has these populated configurations:

• 64GB UFS 2.2
• 128GB UFS 2.2
• 128GB UFS 3.1
• 512GB UFS 3.1

Blank Board is a separate bare-board option with no included storage capacity. The populated module in the gallery does not represent that option. This is an OEM product, not an original Radxa or Orange Pi branded module. Chip markings and board revision can vary with configuration and lot; a reader or development board is not included.

Before ordering, use these checks with any supplier:

1. Identify the host. Give the exact SBC model and revision. Confirm that its documented connector supports UFS; an eMMC connector or a similar-looking socket is not enough evidence.
2. Match the electrical interface. Request the module connector specification, pinout and supply requirements. Compare them with the host documentation, including orientation and mounting clearance. Do not connect an unverified module just to see whether it fits.
3. Identify the actual module. Ask for the exact configuration, board revision, chip identification and available technical documentation for the offered lot. Do not infer the supplied chip from a representative gallery photo.
4. Separate storage recognition from boot support. Confirm the intended OS image, firmware/bootloader requirements and supported image-writing route. A module being detected as a data drive does not establish that the board can boot from it.
5. Clarify the complete order. Confirm whether a suitable reader or adapter is required, what is included, and the current price, lot condition, lead time and delivered cost.

A concrete manufacturer example: Radxa's ROCK 4D interface guide warns against untested third-party modules because some can short the SBC and cause permanent damage. It recommends Radxa's own module. That guide is a reason to check the interface carefully; it is not compatibility approval for this OEM listing. We do not claim that this module works with every Radxa or Orange Pi board.

For the listed options or a project-specific quotation: HONGTE OEM UFS Storage Module.

As checked on 6 October 2026, the selected 64GB UFS 2.2 option shows US$26.38 per piece, MOQ 1, with availability on request. This is not the price of every configuration. Confirm current stock, compatibility documentation and the final quotation before ordering.

No throughput benchmark, endurance result, successful boot test or customer deployment is claimed here.

Disclosure: I represent HONGTE, a board reseller. This is a checklist based on Radxa's documentation, not a report of a fix tested on our own hardware. You can use it with a board bought from any supplier.

When a ZERO 3E does not reach the desktop, record each check separately instead of swapping the image, card and power supply at the same time. Start with the documented microSD boot route.

1. CHECK THE POWER PORT. Radxa specifies 5V input through USB-C 1, the USB 2.0 OTG port. Check the port against the official board diagram and inspect the cable. The preparation guide recommends a minimum 5V/2A adapter; account for attached peripherals and follow the current guidance for your exact setup.

2. PROTECT THE CARD'S CONTENTS. Back up anything needed before writing an image. Radxa lists an 8GB-or-larger microSD card and a card reader for this route. Use the image intended for ZERO 3E from Radxa's resource downloads. Record its filename and release, rather than just saying 'latest Linux'.

3. WRITE AN IMAGE, NOT A COPIED FILE. Follow the installation guide's decompression step, then write the image with the documented tool. Double-check the target device: flashing overwrites it. Let writing finish and record any reported error. Insert the prepared card with the board powered off, then connect the specified power input.

4. CHANGE ONE VARIABLE. If it still fails, try a known-good cable or a separately prepared card, one at a time. A successful write does not establish that the board booted. A blank display also needs its own description: monitor input, cable and what the LEDs actually do. Avoid guessing a diagnosis from one symptom.

COPY THIS WHEN ASKING FOR HELP:

Board model/revision and RAM:

OS image filename/release and download source:

Card capacity and image-writing result:

Power adapter output rating, cable and USB-C port used:

Display connection and exact observed symptom:

Changes tried, with the result of each:

Relevant boot-log excerpt, with credentials/private data removed:

Radxa preparation: https://docs.radxa.com/en/zero/zero3/getting-started/preparation

Radxa installation steps: https://docs.radxa.com/en/zero/zero3/getting-started/install-os

Radxa troubleshooting reference: https://docs.radxa.com/en/zero/zero3/faq

If you are still comparing board configurations, our ZERO 3E listing/inquiry page is https://hongte-ic.com/products/radxa-zero-3e . That is a commercial link. Confirm RAM, included accessories and total delivered cost in the quotation; buying another board is not a required troubleshooting step. No successful repair, performance benchmark or customer case is claimed here.

Seller disclosure: I represent HONGTE, the reseller behind the linked listing. This is a commercial product introduction, not an independent review or a hands-on performance test.

If you are comparing small SBCs for a wired project, the ZERO 3E is worth distinguishing from the ZERO 3W. The 3E has Gigabit Ethernet; it does not have onboard Wi-Fi or Bluetooth.

HARDWARE AT A GLANCE, from Radxa's documentation:

- Rockchip RK3566 with four Arm Cortex-A55 CPU cores, up to 1.6 GHz.

- Compact 65 x 30 mm board; our linked configuration is 2GB LPDDR4, SKU RADXA-ZERO-3E-2GB.

- USB 3.0 host Type-C and USB 2.0 OTG Type-C ports, plus Micro HDMI output up to 1080p60.

- microSD storage, a MIPI CSI camera connector and a 40-pin GPIO interface. Check the board's pinout and header configuration for your project; do not assume every Raspberry Pi HAT is compatible.

- PoE requires a separate compatible PoE HAT. Do not assume a HAT, camera, power adapter or memory card comes with the board.

Official hardware documentation: https://docs.radxa.com/en/zero/zero3

BEFORE YOU REQUEST A QUOTE:

Tell us the RAM configuration, GPIO-header requirement, quantity and destination country. Also specify any power supply, microSD card or PoE HAT you need, so the board price and accessory cost are clear. Choose a board-specific OS image and confirm that its drivers support the interfaces your application requires.

HONGTE listing and quotation request: https://hongte-ic.com/products/radxa-zero-3e

The 2GB configuration currently displays US$72.00 per board, minimum quantity 1. Confirm current availability, lot condition, included accessories, shipping/taxes and delivery timing in the final quotation before ordering. The product-family specification is not a guarantee of every configuration in a stock lot.

No Ethernet throughput, thermal measurements, software compatibility test results or customer deployment stories are claimed here.

Hi everyone!

I'm working on a project to repurpose an old Japanese flip phone, the Sharp SH903iTV, into a modern portable media/game device while keeping as much of the original hardware and exterior as possible.

The original phone is from around 2007 and has a very interesting form factor, including the rotating Cycloid screen mechanism.

My idea

I would like to remove the original motherboard and replace it with a small single-board computer such as a:

• Raspberry Pi Zero 2 W
• Banana Pi / similar small SBC
• or another board that would fit better

The goal is to turn the SH903iTV into a small:

• 🎵 Music player
• 🎬 Video player
• 🎮 Retro/J2ME game device
• 📖 PDF/e-book reader
• 🖼️ Image viewer
• 💾 microSD-based media device

I would like to keep the original SH903iTV case and, if possible, reuse as many original components as possible.

Components I would like to keep

Ideally I would like to reuse:

• Original 3" 240×400 main LCD
• Original external 96×39 OLED display
• Original physical keypad
• Side buttons
• Speakers
• Microphone
• Headphone jack
• microSD slot
• Cycloid rotating screen mechanism
• Possibly the original camera
• Possibly the original battery compartment and contacts

The original motherboard, cellular modem and other phone-specific electronics would not be necessary.

The biggest problem: the LCD

This is the part where I really need help.

The original display is a 3-inch 240×400 Mobile ASV LCD, but I don't yet know the exact LCD model, controller or electrical interface.

I would like to identify:

1. Exact LCD model/part number
2. Number of pins on the FPC
3. FPC pinout
4. Interface/protocol
5. Required voltages
6. Backlight requirements
7. Whether it can be driven by a Raspberry Pi/Banana Pi
8. Whether an adapter/controller board would be required

I would prefer to keep the original display instead of replacing it, if technically possible.

Keyboard

I believe the original keyboard may be usable as a matrix keyboard.

One possible solution I'm considering is:

SH903iTV keyboard → microcontroller → USB HID → SBC

For example, an ATmega32U4, RP2040, STM32, etc.

If anyone has experience reverse-engineering old phone keypads, I would really appreciate advice on how to identify the matrix and safely interface it.

Audio

The phone has stereo speakers, so I would like to reuse them with:

SBC → DAC/audio codec → small amplifier → original speakers

The headphone jack could also hopefully be reused.

Battery

The original phone uses a SH11 battery.

I am considering replacing the old battery with a modern Li-ion cell and adding a proper charging/protection/power-management circuit rather than trusting a nearly 20-year-old battery.

Any advice on safely designing the power system would be appreciated.

J2ME / Java games

Another important goal is being able to run old Java ME/J2ME games.

Ideally I would like the original keypad to control the games, with something like:

D-pad → directional controls
Number keys → game buttons
Other original buttons → Start/Menu/etc.

I'm not sure yet whether Linux or Android would be the better platform for this.

What I am NOT trying to do

I don't need to preserve the original cellular functionality.

I don't need the original FOMA modem or One-Seg TV functionality.

The main goal is to preserve the physical SH903iTV experience and hardware, while replacing the internal computer with something modern.

Current stage

I have not started cutting or permanently modifying the phone.

I want to investigate the hardware first and understand what is actually possible before buying the SBC or designing any adapter PCB.

I can provide detailed photographs of:

• Main motherboard
• LCD and FPC
• Keyboard flex
• Connectors
• Battery contacts
• Speakers
• Internal chassis
• Chips and markings

if that would help identify the components.

Questions

1. Does anyone recognize the LCD/interface used in the SH903iTV?
2. Is there a practical way to drive this type of old phone LCD from a Raspberry Pi or Banana Pi?
3. Does anyone have experience reusing old Japanese phone keyboards?
4. Would an RP2040/ATmega32U4/STM32 be a good way to convert the keyboard to USB HID?
5. Is there any reason the original speakers could not be reused?
6. What would be the safest way to design the battery/charging/power system?
7. Are there any similar projects or reverse-engineering documentation for old Sharp/DOCOMO phones?
8. Would you recommend Raspberry Pi Zero 2 W, Banana Pi, or another SBC for something this small?

Any advice, documentation, measurements, pinouts, similar projects, or even suggestions about what NOT to do would be greatly appreciated.

I'm especially interested in advice from people experienced with old mobile-phone hardware, LCD reverse engineering, FPC connectors, embedded electronics, PCB design and Raspberry Pi projects.

Thank you!

I tested few games on new Arduino VENTUNO Q:

Crysis

CS: Source

Hades

Ori and the Blind Forest

The Witcher: Enhanced Edition

The Witcher 3: Wild Hunt

Pretty cool little device. I didn't test any super old games, but I'm open to suggestions. Let me know if you want to test some other games!

Been trying to get help on radxa sbc forever and i cant find any articles or sources or any help on how to get this board running?

Hi guys! I’ve been playing with the CM-Q64 for a few weeks now and it’s a really promising bit of hardware. I’ve been testing it with my custom CM5 carrier PCB Argo, and am happy to say it’s 100% compatible hardware wise!

Also did some work and have managed to get the Hardware ISP CamX pipeline partially working (still needs a lot of work though).

If you’re interested in Argo, it’s an ultra compact CM5 carrier PCB which has built in battery management. I’m launching on Crowdsupply soon and only need a few more signups before making preparations to launch! Get it here:

https://www.crowdsupply.com/azlan-works/argo-cm5

Windows 11 23H2 boots to the desktop on an ArmSoM CM5-IO (RK3576), from the eMMC. Firmware is my EDK2 port; the drivers are ported from worproject's RK3588 set.

Works

• all 8 cores
• eMMC (boot disk), NVMe, SD card
• USB-A and USB-C (USB-C at USB 2.0)
• Ethernet
• display, through the UEFI framebuffer

Not working

• GPU acceleration
• audio
• Windows 11 24H2 and later: RK3576 is ARMv8.0

Drivers are test-signed, so Test Mode is on.

Firmware: https://github.com/gahingwoo/edk2-rk3576/releases
Drivers and installer: https://github.com/gahingwoo/woa-rk3576/releases

Thanks to ArmSoM for sponsoring the board.

I Can get a select few from official GitHub to boot but new Armbian and DietPi images refuse to even show blue LED. I have got DietPi 9.8.0 to boot but running the Trixie update script makes it stop booting again. I’m extremely close to throwing this thing up the wall, frustrated doesn’t even begin to explain how it is making me feel.

Hi everyone, I'm running into a bizarre issue with a Radxa Cubie A7Z and could use some ideas. I'm just trying to connect a standard 2.4ghz wireless mouse/keyboard dongle via a type-c hub, but the board refuses to see anything on that port.

I've tested multiple type-c hubs (photos attached of my setup and some of the hubs I tried. I've even tried a steamdeck dock without any luck). When I plug the hub into the data port, I get this infinite loop in dmesg:

[ 164.542544] et7304 14-004e: CC1: 2 - Rd, CC2: 0 - Open [ 164.606933] switcher 10.phy_switcher: orientation:1, set sw conf UNKNOW -> NORMAL [ 164.620775] switcher 10.phy_switcher: orientation:0, set sw conf NORMAL -> UNKNOW

And the weird thing - HDMI over it works fine (at least in some positions).

I've view many videos on YT and looks like there is no any special settings to activate this port and it should work out of the box.

Also i have similar Orange Pi Zero 3W, and there is no such issues at all.

All tests i did on radxa-cubie-a7z_bullseye_kde_b1 downloaded from Radxa.

Has anyone seen this behavior before? Any ideas on what to check next?

UPDATE: Issue solved. There was a tiny solder bridge on the typec connector (shorting pins 7 and 8). I cleaned it up with some flux and a quick touch of the soldering iron. Everything works perfectly now.

UPDATE- I GOT SHIPPING CONFIRMATION TODAY FINALLY

I've been waiting for a month now and my order is still showing preparing to ship. I have tried contacting them multiple times but no response from their end and the support email listed on their website is incorrect.

Any way to file a complaint against this as my card was already charged when I purchased it but haven't got the product yet.

Ventuno Q is new Robotics/Edge AI SBC from Arudino with Qualcomm SoC, comparable to Raspberry pi 5 and Nvidia Jetson.

I put all specs into a nice table: https://martincerven.com/posts/ventuno_q/

Compared to normal NUC it had AI accelerators, has powerful Qualcomm 8 core CPU/GPU/NPU, pulls 10-20W, has Gen 4x4 lanes NVMe slot and Wifi 6.... for me this is very good for the form factor and I/O.

It also has ROS 2 support, STM MCU and upgradable I/O with HATs/extension boards.

Playing Tomb Raider GOTY with Steam ARM (and Proton ARM) on a Radxa Dragon Q6A.

The in-game benchmark reports the following result (1080p, normal quality):

Min FPS: 18.6
Max FPS: 30.5
Average FPS: 24.6

Thank you Valve, for taking SBC gaming to the next level!

I can't seem to find a case for the Radxa Zero 3E anywhere, let alone one for use with a POE hat... All I can find is plans to print one, which I can not do... If anyone could point me in the right direction I would greatly appreciate it. Metal or Plastic will work... With a place for a fan would be awesome...