September 21, 2019, 10:05:17 pm


Have you visited the Allwinner Chipset wiki? -

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - castalla

General Discussion / IBOX - a Cubieboard A20 variant
April 25, 2014, 07:13:18 pm
ITEAD have just released a new mini-PC based on the Cubieboard A20 -

Could we start a new dedicated thread for this device?   Or, maybe just use this new topic as a starting point?

A20 users only!

If you are interested, could you please PM me expressing your interest?
General Discussion / Debian server image?
January 19, 2014, 12:06:02 pm
I've lost track of the various changes and images for the CB over the last months

Can someone recommend a stable precompiled Debian-based image for the A10.   Preferably a server version.

Here's an interesting project:

Simply write the image and you're ready to go!
Accessories / Cubieboard case - review
April 30, 2013, 08:33:03 am
I just received the 'official' case today. 

It's very well made.  The board is a very tight fit - be careful how you push the board into the casing!

The OTG power plug enclosure is too small for many plugs to fit if they have a molded case - I was fortunately able to strip back the cable's plastic molding enough using a very sharp modelling knife.

There are no plastic or rubber pads provided to stop the box sliding on slippy surfaces.

Score: 7/10
I'm trying to buy a case from the online shop.

It's impossible!

There's no shipping charge included in the payment!

Cubieboard v1 OS (A10 Based) / Fedora 18 & Bluetooth
March 27, 2013, 06:25:33 pm
Does anyone know how to get bluetooth pairing to work with Fedora 18?
This image is ready for use with the 1024mb Cubie:

Ssh enabled:  root & fedora
You can set up your Cubieboard as a Squeezebox server and player - just follow the threads here:

Logitech Media Server:

Squeezelite Player:

You may have to install a few extras - especially cifs-utils, patch

General Discussion / Cubieboard vs. Raspi
February 17, 2013, 09:07:34 pm
The Cubie is promoted (mainly by the usual bunch of 'reviewers' (who seem only able to reprint commercial blurb rather than actually reviw anything in real life) as an alternative to the Raspi.   

What is the actual experience of an ordinary end-user?

1.  The Cubie costs marginally more.

2.  The Cubie is much more difficult to set-up and use for a 'novice' user.  A new user is faced with navigating the hideously awful Cubieboard group on Google Groups in order to discover any useful nformation.   Essentially, the posts by Martin Wild and Romanrm are the only useful material for the beginner - findng their contributions would tax anyone.

2. The choice of viable out-of-the-box distros is severely limited.  A novice is left swimming in a sea of references to the A10 series of  boards, wondering how these actually run on the Cubie most do, but why should it be so obscure?

3.  In contrast to the Raspi, where thee are utilities such as rpi-update and the ability to edit a config.txt file to fine-tune an installation, the Cubie leaves the user in the Wonderland of Linux ....

4.  Whereas the Raspi has 100s of different projects and applications, the Cubie is almost devoid of any development except some applications which are so esoteric that they are of minimal interest to anybody other than the developer themselves.  XBMC is a case in point - there are three specific images available for the Raspi - there's only one implementation of XBMC for the Cubie which seems sub-optimal in performance.

5. The Cubie has Android - enough said.

6.  The Cubie is definitely less robust than the Raspi - the standard simple case gives some protection but really is only an interim solution for a proper case.  The black motherboard looks 'cool', but that's not really the point, is it?

7. Community support for the Cubie is good but often assumes too much technical knowledge on behalf of the questioning user.   Support from Cubie itself is pathetic - they seem content to sell the boards but fail dismally to actually provide any viable support.  My experience has been without the contributions of only 2 users (named above) then I would have either returned the device or simply thrown it in the bin as unusable!

Overall, the Cubie is an interesting project, but little more than that.  In my limited experience it has little to offer over a B series Raspi for the average user.  Reviewers' claims that it is a Raspi 'killer' are simply reviewers' hype. 

Before I get shot down in flames, there's little point in replying that the Cubie is a development board ... development for what?   I've yet to see anything in development that compares with the myriad of developments being carried out by Raspi users.  I can't see this changing significantly in the future.

So, in score terms ... the Cubie gets a 3, the Rspi an 8.

Essentially, I'll use the Cubie as a backup device for my 2 Raspis.  A third standby Raspi would probably have been a better purchase.
I've been messing with one of my Raspi setups today - changing a lot of settings is very easy because it uses a config.txt file which is accessible via an editor (even on a Windows PC).

Is there any real reason why the Cubie can't have a similar setup config file?

I can't get mp3 files to play using the Debian image (provided by Romanrm).

I installed alsa & libmad - thought that would be sufficient.


edit: own advice, install libmpg123-0

Following my success in installing bluetooth (!) ... I've run into an irritating connection problem.

Rather than post all the gory details, can I just ask if there's anybody here who is a bluetooth expert, or guru, who might be able to advise?

Essentially, it's an auto reconnect issue with a bt headset/speaker.
Here's the lsusb output for RasPi:

BT dongle is seen and activated as hci0

root@squeezeplug:~# lsusb
Bus 001 Device 002: ID 0424:9512 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Here's the lsusb for Cubieboard:

BT dongle is listed but not available or activated

pi@raspberrypi ~ $ hciconfig

pi@raspberrypi ~ $ lsusb
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

So, where do I start?

Both the Pi and Cubie are running Raspian.

Here you go - for Windows users

1.  Download the Berryboot installer -

2.  Write image from zip using WindDiskImager -

3.  You can install using a remote connection or connect the Cubie to a screen (plus keyboard & mouse)

     a. Remote:  edit the uEnv.txt on the SD card - add vncinstall to the end of the last line

     b. Install VNC Viewer for Windows -

4.  Put SD card in Cubie - fire up.   Wait a minute or so - now discover the IP address of the Cubie
     (I use Netscan which shows devices on your network)

5.  Run VNC - add the new IP address - you will see the Berryboot screen - complete the install routine.

6.  When Berryboot is finished - reboot the Cubie

7.  The reboot should bring up the distro you installed - I chose Raspian (as a Pi user)

8.  You can SSH login to Raspian using user 'pi' and password 'raspberry' 

9.  At the command prompt you can run sudo raspi-config to set up some basic features - not all
     the items may be applicable. 

10. Experiment.

I just read on the Pi forum that max (the author of Berryboot) has added ChameleonOS to the OS list.

This looks like an interesting OS -

Is this available on the Cubie Berryboot?
Beginners / Bootable OS images - from the Wiki
January 31, 2013, 08:31:45 pm
So, there is now a list of bootable images (

It states:  'These should work on any Allwinner A10 based device, despite the author targetting some particular device (like the Cubieboard or the MK802). At most, to make the image compatible with your device, you will need to add the u-boot and script.bin from your particular hwpack.'

First beginner's request follows   ;D

Can somebody explain step-by-step how to add the Cubie hwpack files to another image?

(Let's assume I've got a Live version of Mint running)

Note: I've read,26.msg83.html#msg83 but I'm confused by the references to IPL and SPL and how these relate to u-boot and script.bin (mentioned in the Wiki).
Projects / PiCoPlayer for Cubie - a project proposal
January 29, 2013, 10:26:12 am
The fine people over at the Squeezebox forum are developing a new standalone player for the Squeezebox ecosystem (   Their work is an extension of Triode's brilliant Squeezelite player.  Their current version is aimed at the Raspberry Pi.

I'd like to propose a similar effort for the Cubie - implementing PiCoPlayer using Microcore linux.  I believe most of the heavy lifting has already been done by users spb and Gerrelt.

So, anyone here willing to add to their efforts?

I see the process as:

1. Implementing Microcore linux (or TinyCore) - see

2. Integrating the PicoPlayer code

Hope there are others out there who can contribute their technical skills & ideas to this project.

General Discussion / Where to buy in Europe ...
January 29, 2013, 07:00:58 am