Can HUDIY work on other Linux SBC?
Can HUDIY work on other Linux SBC?
Just curious if HUDIY can run on other Linux SBC with higher performance?
Re: Can HUDIY work on other Linux SBC?
It should be doable if the Linux on that SBC uses standard kernel mechanisms (such as DRM, V4L2, NM). Which SBC do you have in mind exactly?
Hudiy Team
Re: Can HUDIY work on other Linux SBC?
I'm thinking something like Jetson Orin and Lattepanda Sigma that have stronger compute system. LattePanda Sigma that runs Ubuntu and has build in Arduino Leonardo MCU for various control.
https://www.electromaker.io/blog/articl ... AM%20specs.
https://www.electromaker.io/blog/articl ... AM%20specs.
-
RockyHarder22
- Posts: 2
- Joined: Mon Sep 15, 2025 1:43 am
Re: Can HUDIY work on other Linux SBC?
I've been playing around with the Radxa Zero3W3E. The minimal Armbian Debian 12 image works well on that board with a desktop added. The main issue I'm running into is hudiy wants a specific version of libboost (and the config file is different). I did get slash screen to display, but have to play with getting labwc on 12.
Re: Can HUDIY work on other Linux SBC?
Orange Pi 5 and above. Very cool offering and I'm going to test it out after I get mine working with custom teensy controller board.
Re: Can HUDIY work on other Linux SBC?
Anyone wanting to try it on x86 might want to try installing the Raspberry PI Desktop image: https://www.raspberrypi.com/software/operating-systems/
It's older Debian 11, but can be updated to Debian 12. Might provide a similar environment to on an actual raspberry pi.
It's older Debian 11, but can be updated to Debian 12. Might provide a similar environment to on an actual raspberry pi.
-
RockyHarder22
- Posts: 2
- Joined: Mon Sep 15, 2025 1:43 am
Re: Can HUDIY work on other Linux SBC?
Popping back in with a small update -- I started messing around with this in earnest around May, but got sidetracked, so I'm currently trying to retrace my steps and take notes, but I did successfully get HUDIY running on a Radxa zero3W, building onto the Armbian vendor kernel cli image with help from GPT.
The image uses a wayland/labwc environment instead of a full desktop to minimize resource usage.
It loads, uses RTLSDR (I have the v4 version which is no longer being produced fyi), and Android Auto connects via wireless and USB and plays smoothly. I believe there's some difference in how the gpio works on this board, but I haven't gotten around to that yet.
It is using hardware acceleration, and with active cooling the board never really gets above 50c. It uses around 1/2GB of RAM.
The board I used to do this was a 4GB version. Unfortunately I took terrible notes getting this set up and then walked away for a bit, so my current mission is to recreate this image from scratch and test my findings. I have this board on 4GB, 2GB, and 1GB variations, and given the RAM usage seen, I would speculate it should work on all three.
My known caveats at this point would be - - the board has a USB 3.0 port, but it seems like images that are not the official radxa ones lack this support. I'm trying to figure that out as well, but most of what I'm using isn't or doesn't need 3.0 speeds. That said, both the radxa official and Armbian images can be run with boot on SD and root on a separate device like an SSD, so that would be a benefit to it working properly.
Radxa's official images seem fine when they work, but they can be a pita to get setup. And updating the system outside of their rsetup program can break things. Some of the things going on with their boards are tied specifically to the pre-created users the images come with, so there's also that. All that being said, once I get it going on Armbian, I am going to give an attempt at setting it up on the official image, which uses a kde desktop.
The other caveat is, unfortunately, availability- with the RAM shortage and everything going on, these boards have become very difficult to find. Arace has occasionally had moments where they have 1 or 2GB in stock at a more reasonable-for-the-time price. Currently Amazon has some in stock, but they want like $80. I bought the 1 GB version that I have from Arace a couple months ago for $30, probably 40 with shipping.
The final caveat might be camera connection - obviously a USB camera would be fine, but getting a pi 1 or 2 camera working on this board is trying with the radxa official image and a nightmare to do on the Armbian image (those are the only two supported cameras, although radxa has their own version of the pi2 camera and I believe a 4k camera). Id managed to get it working when the board first came out, long before hudiy, but I'd have to dust off my druthers to try and tackle that again.
I also have a dragon q6a that i haven't even opened yet. To some degree that might be overkill for this, but I guess we'll see.
The image uses a wayland/labwc environment instead of a full desktop to minimize resource usage.
It loads, uses RTLSDR (I have the v4 version which is no longer being produced fyi), and Android Auto connects via wireless and USB and plays smoothly. I believe there's some difference in how the gpio works on this board, but I haven't gotten around to that yet.
It is using hardware acceleration, and with active cooling the board never really gets above 50c. It uses around 1/2GB of RAM.
The board I used to do this was a 4GB version. Unfortunately I took terrible notes getting this set up and then walked away for a bit, so my current mission is to recreate this image from scratch and test my findings. I have this board on 4GB, 2GB, and 1GB variations, and given the RAM usage seen, I would speculate it should work on all three.
My known caveats at this point would be - - the board has a USB 3.0 port, but it seems like images that are not the official radxa ones lack this support. I'm trying to figure that out as well, but most of what I'm using isn't or doesn't need 3.0 speeds. That said, both the radxa official and Armbian images can be run with boot on SD and root on a separate device like an SSD, so that would be a benefit to it working properly.
Radxa's official images seem fine when they work, but they can be a pita to get setup. And updating the system outside of their rsetup program can break things. Some of the things going on with their boards are tied specifically to the pre-created users the images come with, so there's also that. All that being said, once I get it going on Armbian, I am going to give an attempt at setting it up on the official image, which uses a kde desktop.
The other caveat is, unfortunately, availability- with the RAM shortage and everything going on, these boards have become very difficult to find. Arace has occasionally had moments where they have 1 or 2GB in stock at a more reasonable-for-the-time price. Currently Amazon has some in stock, but they want like $80. I bought the 1 GB version that I have from Arace a couple months ago for $30, probably 40 with shipping.
The final caveat might be camera connection - obviously a USB camera would be fine, but getting a pi 1 or 2 camera working on this board is trying with the radxa official image and a nightmare to do on the Armbian image (those are the only two supported cameras, although radxa has their own version of the pi2 camera and I believe a 4k camera). Id managed to get it working when the board first came out, long before hudiy, but I'd have to dust off my druthers to try and tackle that again.
I also have a dragon q6a that i haven't even opened yet. To some degree that might be overkill for this, but I guess we'll see.