Enea Linux is available as both pre-built binary images and source code. Both serve a specific purpose and each have their advantages. However, using the pre-built binary images allows for getting up and running faster. Please refer to the sections below for details on how to get Enea Linux as pre-built binary images or source code.

Enea Linux pre-built binaries are available for download on portal.enea.com. Log in using the credentials provided by Enea for your user account. Using the menu, browse to the Linux section where you will now have access to the Files and Online Documentation sections. The Files section lists each Enea Linux distribution, one for each version and profile, as a separate download package. Clicking on the name of the distribution will open a new page, which presents further details about the content of the release and a list of downloadable archives, one for each hardware target included in the release. Each archive provides the following content: images directory – this directory includes the binary image files needed to boot the target with Enea Linux. This includes the kernel, the root file system, device tree, etc. sdk directory – this directory includes the installer for the SDK. deb directory – this directory contains all the packages included in the distribution in deb format, which can be installed using the package manager. For faster downloads, each archive is mirrored in several places, geographically. Choose the archive in the region closest to you. The Documentation section lists all the documents delivered with the release: Enea Linux User’s Guide - intended for Enea Linux platform developers, who want to configure and build customized Linux kernel images for embedded system targets, using the Yocto configuration and build system. Enea Linux Open Source Report - contains the open source and license information pertaining to packages provided with this release of Enea Linux. Enea Linux Release Info - provides information about the current released distribution for a selected set of targets, along with installation requirements and procedures.

Enea Linux sources are available for cloning from a set of Git repositories on git.enea.com. Since Enea Linux requires multiple repositories, Google Repo tool is used in order to manage configurations and make the cloning step simpler. The Google Repo tool uses files, known as manifests, which store a list of tuples (repository URL, version). The Repo tool is then used to traverse the list of tuples in the manifest file and clone the specified versions of each repository. See Google Code Archive for git-repo, for more info.

In order to get access to git.enea.com, a ssh key is required for Git authentication. If you don't already have such a key, follow the steps below to generate one: Generate the ssh key pair: $ ssh-keygen -t rsa When asked for a password, just press Enter. This will create two files in the .ssh directory in your home directory. id_rsa id_rsa.pub Copy the public key into an authorized_keys file: $ cat id_rsa.pub >> authorized_keys Once these steps are done and you have a valid ssh key pair, send the public key, id_rsa.pub, via email to mailto:git_support@list.enea.se in order to get access to git.enea.com.

To use the Repo tool to download the sources for Enea Linux, do the following: Make sure that the repo tool is installed. If not, do the following: Below is include of ID "eltf-getting-repo-install-command" from eltf_params_updated.xml Define the MACHINE to the following target listed here:Below is the "machine_list" programlisting in machine_list_generated.xml created by the make system by extracting from the manifest Then use the repo command below: Once the source code is downloaded, the current directory will contain a README file with instructions on how to build the distro and boot the raspberry pi machine. For ease of use, these instructions are also copied into this document, see . It is not necessary to explicitly clone the manifest repository since that is done automatically by the repo tool. To see the current manifest, use the following command: $ repo manifest The UG should be updated with instructions on how to add customizations. That section should also contain more info about the manifest: the manifest templates, using a branch instead of the tag EL6, etc. When this is done a reference from here should be added.