Archive for the ODROID-C1 Category

It has just occured to me …

Posted in Parallel Talk, Erlang, ConCurrency, ODROID-C1, Chapel, Parallella on May 19, 2017 by asteriondaedalus

… what a coincidence.

The Parallella and the Odroid-C1 PCB are same size (almost).  Is that Feng Shui, synchronicity or serendipity?

Pity the post holes don’t line up.

Tax return is in

Posted in Chapel, ODROID is wonderful, ODROID-C1, ODROID-XU4, Parallel Talk on April 30, 2017 by asteriondaedalus

Well late really, last two years after tax department started writing letters.

Serve them right as I got a quite hefty lump sum out of it.

So, after agonising over what to do about GPU based system, I decided I am only dabbling so I opted to simply get an ODROID-XU4 so that I can at least run OpenCL under Python.

Mind you, after toying with Chapel on my quad-core Odriod C1, I will be interested in the Octa-Core Xu4.  I did splurge and get an 32GB eMMC 5.0 with Linux.

I went this way as even now the Jetson TK1 is available (as its now obsolete) in Australia, I am rather more interested now in Chapel.   Not to mention that Chapel appears to be a better approach than Cuda.  That is the appeal, you can take your Chapel code and just change the underlying engine.

So, my cluster will be one ODROID-XU4 and four ODROID-C1.  So, 24 cores all up (not taking the general purpose GPU on the XU4 into account).

Oh, and the 18 cores the Parallella adds.  You do know there is an Erlang for the Parralella don’t you?

I am in parallel programming heaven.

The thing that makes it all possible is the 9 port POE switch and a gaggle of active POE splitters (48V down to 5V) – you don’t need n-power packs on your wall.

Don’t forget TTY+ (MPutty) or some other multiple session tool.

Built into the guts of an old game PC case my mate gave me, so the wife will never know.

If I need more grunt a NVDIA card maybe later, in an 8-core PC, maybe.

However, PhD submission draft this weekend so dabbling is all that I will have time for.

Install node-red Odroid C1

Posted in Linux, ODROID-C1, The downside of Opensource on December 27, 2016 by asteriondaedalus

Again with the raft of various authors with their own twists.

So far so good on odrobian vanilla with:

Install npm with:

sudo apt-get install npm

Install node-red with:

sudo npm install -g node-red

However, a couple of fails and various warnings ensued so stay tuned for the debug.


Go figure, again with the 1,000,000 authors story.

So far we had to fiddle.

Installing npm installs nodejs of a version that node-red is not happy with so won’t install.

I ended up installing nvm to pull latest node.js onto machine.  I then had to use apt-get remove to rip out nodejs/npm installed previously to leave latest node.js along with it’s npm.



Unfortunately I didn’t write the steps down as I was having to slash on the fly to try and work out what was going wrong, why two node were being installed etc.

Having problems with node-red-node-google calendar out??? Same setup works on PC.  The callback provided by node is to localhost.  The odrobian version provides a callback based upon which you have to resolve to the odroid’s ip in /etc/hosts.  The problem, a DNS error is raised at the last step of the “authorise with google” for the API.  The prompt appears, but when you select allow the DNS address error is raised.

ODROID-C1 dropping internet

Posted in Linux, ODROID-C1, The downside of Opensource on December 26, 2016 by asteriondaedalus

I found I was having problems with the ODROID-C1, which I am building up as the node-red, mqtt, Phoenix server for home automation, was loosing internet connection a time after boot.

I am building the machine on top of odrobian vanilla – I am using Debian based Linux on all my boxes by preference – which does leave me out in the cold with some software yes.

The cli command told me the ethernet on board was working so I suspected a problem with IP allocation.  A reboot would fix the problem after all.

I poked around the odrobian docs.

Go figure the installed /etc/network/interfaces file read:

auto lo
iface lo inet loopback

The starting example in the docs read:

auto eth0
iface eth0 inet dhcp

Interwebbything, again, has no useful help in as far as there are 1,000,000 plus pages on iface setup so who knows who actually understands what they are telling people and how many are just gash copies of material from the first place people found it?

So what I ended up doing is the following:

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp

The reason being one oft copied recommendation is always have the loopback.

I tried the eth0 without the auto in front but ping failed to find the real-world.   You would know if it failed as the ping returns immediately.   If it takes any time it’s because it got out into the real-world and is looking for the target.

The auto  command is telling the etho (and lo for that matter) to start on boot.  Without it you would need to do a manual start from the command line.

So, there appears a problem in the supporting manual for odrobian as it assumes what might be in the /etc/network/interfaces file and is simply wrong.

I checked it out by starting a ping to and then jumped on my bike and went for a half hour spin THEN a medium length walk with the dogs (b4 it rains again).

When I came back, we were still on the Interwebbything.

Looks like that they have just copied material from somewhere without tuning it for the actual distro.