summaryrefslogtreecommitdiffstats
path: root/getting-started/machines/intel.md
diff options
context:
space:
mode:
Diffstat (limited to 'getting-started/machines/intel.md')
-rw-r--r--getting-started/machines/intel.md59
1 files changed, 38 insertions, 21 deletions
diff --git a/getting-started/machines/intel.md b/getting-started/machines/intel.md
index c2e8f0a..0c420d5 100644
--- a/getting-started/machines/intel.md
+++ b/getting-started/machines/intel.md
@@ -1,37 +1,43 @@
# Running AGL on Intel Minnowboard (and most Intel 64 bits HW)
## Scope
+
This documentation is aiming at people who want to run Automotive Grade
Linux (AGL) on an Intel Hardware (HW).
While the reference HW used by AGL project is the Open Source Minnowboard.
This documentation [MinnowBoard wiki](https://minnowboard.org/)
-can be used to enable most of 64 bits Intel Architecture (IA) using UEFI as boot loader.<br>
+can be used to enable most of 64 bits Intel Architecture (IA) using UEFI as boot loader.
In addition to the MinnowBoard, support for the the [Joule Developer Kit](https://software.intel.com/en-us/iot/hardware/joule/dev-kit) has been added.
-You need to run the 64 bits version of the UEFI boot.
+You need to run the 64 bits version of the UEFI boot.
Minnowbaord Max and Turbo has well as the Joule are both 64 bits capable.
-**Note** :
- * This page is more focused on please willing to create bespoke AGL image and BSP.
-If you are more interested by Apps creation, please visit [ Developing Apps for AGL](https://wiki.automotivelinux.org/agl-distro/developer_resources_intel_apps)
+**Note**:
+
+* This page is more focused on please willing to create bespoke AGL image and BSP.
+
+If you are more interested by Apps creation, please visit [ Developing Apps for AGL](<https://wiki.automotivelinux.org/agl-distro/developer>_resources_intel_apps)
UEFI has evolved a lot recently and you likely want to check that your HW firmware is up-to-date, this is mandatory for the Minnowboard and the Joule.
-[`https://firmware.intel.com/projects/minnowboard-max`](https://firmware.intel.com/projects/minnowboard-max)<br>
+[`https://firmware.intel.com/projects/minnowboard-max`](https://firmware.intel.com/projects/minnowboard-max)
[`https://software.intel.com/en-us/flashing-the-bios-on-joule`](https://software.intel.com/en-us/flashing-the-bios-on-joule)
## Where to find an AGL bootable image
-### Building an AGL image from scratch using Yocto.
+### Building an AGL image from scratch using Yocto
+
+**Note**:
+
+* An alternative method for building an image is to use the AGL SDK delivered in a Docker container.
-**Note:**:
- * An alternative method for building an image is to use the AGL SDK delivered in a Docker container.
There is currently no SDK dedicated to IA but the SDK provided for the Porter Board can build an IA image without changes (just aglsetup.sh needs to call for Intel).
see chapter 2 of [Porter QuickStart](http://iot.bzh/download/public/2016/sdk/AGL-Kickstart-on-Renesas-Porter-board.pdf "wikilink").
#### Download AGL source code
+
Downloading the AGL sources from the various Git repositories is automated with the repo
-tools [ to RepoDocumentation](https://source.android.com/source/using-repo.html "wikilink")
+tools [to RepoDocumentation](https://source.android.com/source/using-repo.html "wikilink")
To install the repo tool.
@@ -48,12 +54,14 @@ To install the repo tool.
cd AGL-3.0.x;
repo init -b chinook -m default.xml -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo
```
+
#### Configuring for master (DD)
```bash
cd AGL-master;
repo init -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo;
```
+
Once that you repo is initialised either with the stable or WIP, you need to sync the repo to fetch the various git trees.
#### Downloading the configured AGL source code
@@ -63,6 +71,7 @@ Once that you repo is initialised either with the stable or WIP, you need to syn
```
#### Building the AGL distro
+
You are now ready to initialise your Yocto build.
When running the command:
@@ -76,7 +85,8 @@ You will notice the Intel entries
intel-corei7-64
joule
```
-Simply select that entry to replace porter in the -m option.<br>
+
+Simply select that entry to replace porter in the -m option.
**Note:** agl-netboot option is required to create the right initramfs even if you do not boot from a network
```bash
@@ -85,6 +95,7 @@ Simply select that entry to replace porter in the -m option.<br>
-b build \
agl-devel agl-demo agl-appfw-smack agl-netboot
```
+
**Note:** use the option "-m joule" when building for a Joule developer Kit target.
Start the build **This can take several hours depending of your CPU and
@@ -93,13 +104,14 @@ internet connection and will required several GB on /tmp as well as on your buil
```bash
bitbake agl-demo-platform
```
-** Your newly baked disk image (.hddimg) will be located at **:
+
+**Your newly baked disk image (.hddimg) will be located at**:
`tmp/deploy/images/intel-corei7-64/`
##### Alternative: Download a *ready made* image from AGL web site
The Continuous Integration (CI) process from AGL creates and publish daily and stable builds.
-Pointers to both can be found in [ AGL supported HW](https://wiki.automotivelinux.org/agl-distro) (see Reference BSP/Intel).
+Pointers to both can be found in [AGL supported HW](https://wiki.automotivelinux.org/agl-distro) (see Reference BSP/Intel).
Once you have validated your process you can start to play/work with the snapshot pointer.
@@ -107,11 +119,11 @@ Note that snapshot build may not work.
Follow the directory:
-` intel-corei7-64/deploy/images/intel-corei7-64/`
+`intel-corei7-64/deploy/images/intel-corei7-64/`
and download the file:
-` agl-demo-platform-intel-corei7-64.hddimg`
+`agl-demo-platform-intel-corei7-64.hddimg`
## Create a bootable media
@@ -119,7 +131,7 @@ Depending your target HW you will use an USB stick, an SD card or a HDD/SDD.
The creation process remains the same independently of the selected support.
It does require to have access to a Linux machine with sudo or root password.
-### Insert you removable media in the corresponding interface.
+### Insert you removable media in the corresponding interface
### Check the device name where the media can be accessed with the command
@@ -128,17 +140,19 @@ It does require to have access to a Linux machine with sudo or root password.
# Note that you want the name of the raw device not of a partition on the media
#(eg. /dev/sdc or /dev/mmcblk0)
```
+
### Download the script mkefi-agl.sh
+
This script is present in the directory meta-agl/scripts from blowfish 2.0.4, alternatively you can download it from the following Git repo:
[https://github.com/dominig/mkefi-agl.sh](https://github.com/dominig/mkefi-agl.sh)
-
### check the available option
```bash
sh mkefi-agl.sh -v;
```
+
### create your media with the command ajusted to your configuration
```bash
@@ -158,11 +172,14 @@ This script is present in the directory meta-agl/scripts from blowfish 2.0.4, al
1. Let AGL boot
-**Note:**:
- * Depending on the speed of the removable media, the first boot may not complete, in that case simply reboot the device.
-This is quite common with USB2 sticks.
+**Note:**:
+
+* Depending on the speed of the removable media, the first boot may not complete, in that case simply reboot the device.
+
+This is quite common with USB2 sticks.
+
By default the serial console is configured and activated at the rate of 115200 bps.
## How to create your 1st AGL application
-[ Developing Apps for AGL](https://wiki.automotivelinux.org/agl-distro/developer_resources_intel_apps)
+[Developing Apps for AGL](https://wiki.automotivelinux.org/agl-distro/developer_resources_intel_apps)