|Release Date||October 2013|
|Website||Cubietruck Product Page|
|SoC||A20 @ 1Ghz|
|DRAM||2GiB DDR3 @ 480MHz (GT8UB512M8EN-BG or H5TQ4G63AFR-PBC)|
|Power||DC 5 V @ 2 A (3A with 2.5" SATA drive) using 4/1.7mm jack, JST XH 2.5mm Battery connector|
|Video||HDMI (Type A - full), VGA|
|Audio||3.5 mm headphone plug, HDMI, S/PDIF|
|Network||WiFi 802.11 b/g/n (Ampak AP6210), 10/100/1000Mbps Ethernet (Realtek RTL8211E)|
|Storage||µSD, SATA 2.0|
|USB||2 USB 2.0 Host, 1 mini-USB2.0 OTG|
Cubietruck is the third generation of the famous Cubieboard, and is the most full-featured board to date.
The board helpfully states "CUBIETRUCK".
There are two revisions of the A20. Since Feb 2014 it is RevB. The Rev state is not printed on the board and is not retrievable from the SoC. There is also no information regarding the differences of these revisions. There is evidence of different behavior and boot problems with older kernel on RevB cubietrucks.
Mostly supported. See Tips, Tricks, Caveats below for more details.
Instruction to make ArchLinux ARM images for Cubietruck.
You can build things for yourself by following our Manual build howto and by choosing from the configurations available below.
Use the Cubietruck build target.
Use the Cubietruck build target.
Use the cubietruck.fex file.
Use the sun7i-a20-cubietruck.dtb device-tree binary.
Tips, Tricks, Caveats
There is a button marked 'FEL' next to the full-size usb ports, which triggers FEL mode.
The Cubietruck is the only board to date that has a properly implemented VGA connector with DDC. Load-detection is also reliable. In future kernel versions (with sunxi-kms), VGA and the attached monitor will be detected properly and will require no intervention.
For now though, you need to edit the FEX file still.
There is one issue with VGA though. Due to bad PCB placement, there is some crosstalk between Wifi and VGA in certain videomodes.
<tomee^> arokux: 432MHz. that's the speed at which my board runs with sunxi bootloader, too. but look here:http://dl.cubieboard.org/software/a20-cubietruck/common/ct-v101_sys_config.fex <tomee^> arokux: I simply do not know why 432MHz if the hardware can do 480... they downclocked it for security purposes in the first batch? <arokux> tomee^: sorry, I have no idea. <tomee^> arokux: I've heard somewhere that someone complained about overheating of the prototype <arokux> tomee^: Turl may know. <Turl> dunno, we should ask benn
See this conversation on memory frequency problems.
There is an AMPAK AP6210 Wifi+BT chip on board with PCB antenna, but it is not clear what exactly is inside:
- Broadcom BCM43362 + BCM20710
- Broadcom BCM4330 / BCM40183 Based Chipset
- Cubietech says it is BCM4329/BCM40181
If your're using the Cubietech's kernel, you can enable the module with
There is a parameter op_mode, which allows you to enable AP mode, for example
modprobe bcmdhd op_mode=2
For the linux-sunxi's 3.4 kernel, you will need a special driver, instructions to integrate and compile the AMPAK AP6210 Wifi and Bluetooth driver with the sunxi-3.4 source code are avalable.
The Lubuntu Desktop images has NetworkManager running. It spawns its own wpa_supplicant, which is respawned once you kill it. This wpa_supplicant will also interfere with yours, if you want to configure WLAN Adapter by yourself. I have removed NetworkManager and was able to successfully configure WiFi.
wpa_supplicant -D nl80211 -B -i wlan0 -c <(wpa_passphrase YOUR_SSID YOUR_PASSWORD)
This is a new or differently wired chip, status UNKNOWN, please test it!
- Here is some info on how to get the bcmdhd compiled with workarounds / ideas how to overcome problems
<tomee^> arokux: CC [M] drivers/net/wireless/bcmdhd/dhd_linux.o drivers/net/wireless/bcmdhd/dhd_linux.c: In function ‘dhd_os_prealloc’: drivers/net/wireless/bcmdhd/dhd_linux.c:5192:2: error: implicit declaration of function ‘wl_android_prealloc’ [-Werror=implicit-function-declaration] <tomee^> arokux: I guess you should ifdef the DHD_OS_PREALLOC option for non-android builds... or I did something wrong <tomee^> arokux: it comes from the bcmdhd driver compilation <tomee^> arokux: when I disabled buffer preallocation for it, it went through <tomee^> arokux: CONFIG_DHD_USE_STATIC_BUF=y broke the compilation. CONFIG_DHD_USE_STATIC_BUF=n made it work. maybe this flag should depend on android or some other build environment
Tha battery backups the power supply. It allows an uninterruptible operation. Depending on the battery capacity several hours of operation are possible.
The battery will be charged during operation. A 3.7 Volt Lithium polymer battery is needed. The JST XH 0.1"/2.5mm connector is near the ethernet port (see frontside board pictures).
For kernel 3.4:
- The battery capacity in mA has to be set in the fex file.
- The current voltage can be read here /sys/class/power_supply/battery/voltage_now
- The current status charging/discharging can be read here /sys/class/power_supply/battery/status
The cubietruck is prepared to power directly a 3.5" HDD with Cubietech's optional 3.5 inch HDD addon package. Unlike other sunxi boards that feature an onboard SATA-power-connector suitable for powering 2.5" disks the Cubie solution is able to feed 3.5 disks that need both 5V/12V from a single 12V power source (using a 5.5/2.1 power barrel). The Addon board contains a step-down converter supplying 5V on 2 USB type A ports (from where you can feed the board using an USB-to-4/1.7mm-cable) and provides 12V on a JST XH 0.1"/2.5mm header. An identical header on the Cubietruck routes the 12V to the SATA connector on the board's edge (see gallery below).
Both 5V and 12V power connectors towards disk also use the JST XH 2.5mm header. Banana Pi/Pro/M1+, Orange Pi, Orange Pi Mini and pcDuino3 Nano use all the same JST header to provide 5V to a SATA disk. But only the pcDuino uses the same polarity, on Bananas/Oranges 5V/GND are inversed! So you could use Cubietech's 3.5 inch HDD addon package with pcDuino3 Nano or use the 2.5" SATA-power kits available for the pcDuino with Cubieboards without modifications. But due to different polarity the different Pis are incompatible and would require cable modifications.
Cubietech Kernel source
There are kernels developed by Cubietech, they are supposed to have all features working.
- Kernel: https://github.com/cubieboard/linux-sunxi
- fex and kernel config: https://github.com/cubieboard/cubie_configs
Reportedly AP mode does not work with the WiFi driver in this kernel.
This kernel is abandoned by Cubietech, but can still have something interesting, such as: https://github.com/cubieboard2/linux-sunxi/tree/sunxi-3.4-ct-dev/drivers/net/ethernet/allwinner/gmac
The cubietruck exposes 2 2.0 mm pitch connectors with lots of expansion possibilities.
|CN8 (Near Ethernet connector)|
|5||PC19 (SPI2-CS0/EINT12)||6||PC21 (SPI2-MOSI/EINT14)|
|7||PC20 (SPI2-CLK/EINT13)||8||PC22 (SPI2-MISO/EINT15)|
|9||PB14 (SPI0-CS0/JTAG_MS0)||10||PB16 (SPI0-MOSI/JTAG_DO0)|
|11||PB15 (SPI0-CLK/JTAG_CK0)||12||PB17 (SPI0-MISO/JTAG_DI0)|
|15||PI20 (FMIN-L/PS2SCLK0/UART7-TX/HSCL)||16||PI14 (PS2SCLK1/EINT26)|
|17||PI21 (FMIN-R/PS2SDA0/UART7-RX/HSDA)||18||PI15 (PS2SDA1/EINT27)|
|19||PI3 (PWM1)||20||PB3 (IR0-TX)|
|21||PB2 (PWM0)||22||PB4 (IR0-RX)|
|CN9 (Near USB Ports)|
|3||PG0 (TS1_CLK/CSI1-PCLK)||4||PG3 (TS1_ERR/CSI1-VSYNC)|
|5||PG2 (TS1_SYNC/CSI1-HSYNC)||6||PG1 (TS1_DVLD/CSI1-MCLK)|
|7||PG4 (TS1_D0/CSI1-D0)||8||PG5 (TS1_D1/CSI1-D1)|
|9||PG6 (TS1_D2/CSI1-D2/UART3-TX)||10||PG7 (TS1_D3/CSI1-D3/UART3-RX)|
|11||PG8 (TS1_D4/CSI1-D4/UART3-RTS)||12||PG9 (TS1_D5/CSI1-D5/UART3-CTS)|
|13||PG10 (TS1_D6/CSI1-D6/UART4-TX)||14||PG11 (TS1_D7/CSI1-D7/UART4-RX)|
Adding a serial port
There is a nice 0.1" connector behind the USB ports, just plug in your UART adapter.
Also known as
The cubieboards are a well known brandname nowadays and there are no rebadgers. The Cubietruck is also known as Cubieboard 3.