FlightAware Discussions

So what OS do you use for your ARM development board

This thread will likely have a number of thoughts… cartridge or cassette, IOS, Windows, Android etc LOL

What OS are you using for your ADS B experience and briefly why. Myself, I currently have an XU4 loaded with their standard Ubuntu Mate. Has been working flawlessly. Handles any ADS B scripts I have chose to use and it is their recommended OS, fully supported. I am about to set up a N2 with a eMMc board and it will be used only for another ADS B unit. I also tend to stick with a recommended and supported version of any sort of OS I have used, possibly not choosing an non official version but works exactly the same. As developers, which OS is easy for you to develop from.

I appreciate for starters it is ARM64 which can create some issues I believe with things you want to do, but as usual on this great reference site, our colleagues have already supplied scripts to cover that OS speed mismatch with programs that are 32. But I am interested in the why for instance, you might want to use Debian Stretch or Buster (the developers sure thought up some interesting names for their creations …) , Ambian or Ubuntu…

Why have so many different versions have come about??? Don’t get too involved in your response, just the basics. :slight_smile:

A desk full of various Raspberry Pis running Raspbian, because that’s the hardware/software combination we target releases at.

As you mention, there’s a ton of different hardware & OS versions out there; directly supporting every combination isn’t practical and if you have to pick one, the Pi family arguably has the best software support & hardware longevity.

Providing source code and targeting Debian-alikes means that it’s possible to build for a lot of other targets without too much pain, too.

They’re all characters from Toy Story.

1 Like

Same reason as so many versions below:

landrover lexus mazda mercedes pegu tesla vw toyota infiniti hyundai honda GM fiat images download


I used Odroid Ubuntu Bionic on the N2 for a while. It had stubborn issues with DNS service (it hung regularly). Then I switched to Stretch and that has been working fine. As said, the building on stretch arm64 was straightforward.

With Stretch, I did have to correct the log-rotation setting (in case you have a desire to look at logs); posted here.

UAT on Pi running only dump978-fa. Works like a charm.

I had big, big plans to have UAT and 1090 on the N2. Alas, dump978 takes up too much attention from the CPU to usefully combine with 1090 in my case. YMMV. :neutral_face:

1 Like

I have two systems, one is a stock piaware image running on a raspberry pi with a ProStick plus, this is my reference system.
My main, also the experimental, system is an Odroid XU4 with Ubuntu Mate 18.04 and an airspy mini at 20MHz sampling rate.
I needed the Odroid to be able to handle the airspy at 20MHz as it was too much for a pi at the time.

1 Like

On my Pi3 I am using Raspbian Stretch from here: https://www.raspberrypi.org/downloads/
I didn’t upgrade to Buster because… I am lazy, I wait for others to fix all the transition issues first.

On my Orange Pi One I am using the Armbian - Debian Stretch - from here:

On my RPi2 I am using Raspbian Buster Lite

On my OPiPC I was using Armbian Stretch, and from yesterday have switched to Armbiam Buster

On my Windows PC through VM, I am using
(1) Debian10 x64
(2) Ubuntu 18.1 x64

1 Like