Deployment Environment

From Apertis
Jump to: navigation, search
Apertis SDK image running in a VM

You can try out Apertis in a virtual machine or on real hardware. Release and daily build images are available for testing. Apertis development is fasted paced, so we recommend that you use the daily build images whenever possible.


Apertis on virtual machines

The recommended virtual machine platform for the i386 and AMD64 Apertis system images is VirtualBox. Please see the Apertis VirtualBox setup instructions.

In particular, please note that the AMD64 system images require EFI, which must be specifically configured during virtual machine creation in current versions of VirtualBox.

Apertis on reference hardware

Base Minnowboard setup with a Lilliput screen

The recommended Intel (64 bit) reference hardware is the Minnowboard Max with some optional extras. Please see its setup guide for first-time setup.

The recommended ARM (32 bit) hardware is the i.MX6 Sabrelite, also with some optional extras. Note that ARM images are not publicly available.

Working with target images

Target images deliberately don't have development/debugging tools installed. To get a basic set (somewhere between the official target and development images) you can log in on the serial console or use the xterm, and run:

sudo apertis-dev -b -g -3

Add --help to see more options.

Please note that a machine where this has been done is not a "pure" target image; if a bug was reported for target images, please confirm the fix on a target image without these development tools.

Using SSH

Accessing the device via SSH is generally more convenient than using a serial console or xterm. To do so, add the following to your ~/.ssh/config file

Match host apertis*
    User user
    IdentityFile ~/.ssh/apertis.ssh
    IdentitiesOnly yes
    StrictHostKeyChecking no
    UserKnownHostsFile /dev/null

Generate a new key which you will use for connecting to all Apertis target images:

ssh-keygen -t rsa -N "" -f ~/.ssh/apertis.ssh

Then, for each new target image installation you have, set up the key, replacing $hostname with the board’s hostname:

ssh-copy-id -i ~/.ssh/ user@$hostname

You should then be able to SSH in using:

ssh $hostname
Personal tools