Differences between revisions 28 and 32 (spanning 4 versions)
Revision 28 as of 2016-02-06 23:28:06
Size: 3600
Editor: ?ThomasBechtold
Comment: Add blog post link for Debian Stretch setup notes
Revision 32 as of 2018-01-17 09:33:07
Size: 4530
Editor: PaulWise
Comment: fit the correct naming scheme
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from ArmHardFloatPort/CuBox-i
Line 6: Line 7:
The [[http://cubox-i.com|CuBox-i]] devices are a series of small-footprint, always-on computers based on the Free``Scale i.MX6 chipset. The [[https://www.solid-run.com/freescale-imx6-family/cubox-i/|CuBox-i]] devices are a series of small-footprint, always-on computers based on the Free``Scale i.MX6 chipset.
Line 31: Line 32:
== Desktop Environments ==

On Buster Gnome on Wayland works out of the box. It is important to boot the kernel with the cma=... parameter set, e.g. cma=256M.

See also [[https://wiki.debian.org/InstallingDebianOn/Wandboard#cma|cma entry for the Wandboard]]

I added the cma=... parameter by

{{{
rd@xbian:/etc/flash-kernel/bootscript$ diff -u bootscr.cubox-i~ bootscr.cubox-i
--- bootscr.cubox-i~ 2017-07-25 06:58:47.000000000 +0200
+++ bootscr.cubox-i 2018-01-13 17:26:46.983026580 +0100
@@ -29,6 +29,7 @@
fi
 
setenv bootargs @@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} @@LINUX_KERNEL_CMDLINE@@
+@@UBOOT_ENV_EXTRA@@
 
if test -z "${prefix}" ; then
  setenv image_locations '/boot/ /'
rd@xbian:/etc/flash-kernel/bootscript$

# echo 'setenv bootargs ${bootargs} cma=256M' | tee /etc/flash-kernel/ubootenv.d/cma && flash-kernel


}}}
Line 37: Line 65:
 * Igor Pečovnik provides an adapted Wheezy and Jessie [[http://www.igorpecovnik.com/2014/08/19/cubox-i-hummingboard-debian-sd-image/|image]]  * Armbian by Igor Pečovnik is a Debian-derived [[http://www.armbian.com/hummingboard/|distribution]]

CuBox-i support in Debian

This page exists to collate information about the status of support in Debian for the CuBox-i family of devices by SolidRun (CuBox-i1, CuBox-i2, CuBox-i2Ultra, CuBox-i4Pro).

General information

The CuBox-i devices are a series of small-footprint, always-on computers based on the FreeScale i.MX6 chipset.

Bootloader support

The CuBox-i uses U-Boot as a bootloader. As of 2014-03-09, upstream provides a git tree based on U-Boot 2013.10. A port of upstream U-Boot support to 2014.01 (the version in jessie/sid) is available here and was included in the Debian package u-boot 2014.04-1 (see: 741127).

The CuBox-i U-Boot uses SPL (allowing the same U-Boot image to be used across multiple models), and should be installed to the SD card using the layout described here. Note that this version of U-Boot will also support reading the second-stage bootloader from a FAT filesystem on the first partition of the device; however, since U-Boot also reads its environment from an offset of 384K on the SD card, there is 342K of reserved space at the front of the disk which will be otherwise unused. It is therefore recommended to install U-Boot to the embedded space at the front of the disk, and not to set up a dedicated boot partition on the SD card.

Kernel support

The CuBox-i should have basic support with the armmp linux kernel (3.16+) in Debian Jessie, including serial console, usb, ethernet, mmc, HDMI, eSATA and ir receiver. To enable additional features, you may need to explore one of the following options:

  • Install a kernel from jessie-backports, stretch, sid or experimental.
  • Apply the enablement patches to your linux source.

  • Build a kernel from the SolidRun 3.10 stable kernel branch.

  • Use a pre-built binary kernel image from SolidRun, available here. (Note: these kernels are based on a Linux 3.0 Android BSP.)

Installing Debian

Starting from Debian 8.0, the cubox-i and hummingboard are supported through the official debian installer. Be prepared to attach a serial console to your cubox-i/hummingboard, because the installer does not output messages on the HDMI interface.

In the default configuration after rebooting from the installer the serial console is not(!) enabled. To enable execute

 echo 'T0:23:respawn:/sbin/getty -L ttymxc0 115200 vt100' >> /etc/inittab

Desktop Environments

On Buster Gnome on Wayland works out of the box. It is important to boot the kernel with the cma=... parameter set, e.g. cma=256M.

See also cma entry for the Wandboard

I added the cma=... parameter by

rd@xbian:/etc/flash-kernel/bootscript$ diff -u bootscr.cubox-i~ bootscr.cubox-i 
--- bootscr.cubox-i~    2017-07-25 06:58:47.000000000 +0200 
+++ bootscr.cubox-i     2018-01-13 17:26:46.983026580 +0100 
@@ -29,6 +29,7 @@ 
fi 
 
setenv bootargs @@LINUX_KERNEL_CMDLINE_DEFAULTS@@ ${bootargs} @@LINUX_KERNEL_CMDLINE@@ 
+@@UBOOT_ENV_EXTRA@@ 
 
if test -z "${prefix}" ; then 
  setenv image_locations '/boot/ /' 
rd@xbian:/etc/flash-kernel/bootscript$

# echo 'setenv bootargs ${bootargs} cma=256M' | tee /etc/flash-kernel/ubootenv.d/cma  && flash-kernel

Further info