Skip to content
Snippets Groups Projects
Commit e10c3e44 authored by Martyn Welch's avatar Martyn Welch
Browse files

Tidy up reference hardware information 


Information about the reference hardware and supported platforms is a bit
jumbled and out of date. Split out the listing of reference hardware by
architecture to avoid having one massive long page. Shift out development
related details.

Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
parent 697d52ad
No related branches found
No related tags found
1 merge request!35Next bunch of website updates
Hide whitespace changes
Inline Side-by-side
Showing
with 246 additions and 235 deletions
content/_index.md
+ 0
− 1
View file @ e10c3e44
......@@ -68,7 +68,6 @@ Apertis provides a number of pre-built images for Intel (64-bit) and ARM (32-bit
* [Download the current images]( {{< ref "/images.md" >}} )
* [Source code](https://gitlab.apertis.org)
* [Mailing lists](https://lists.apertis.org/)
* [Set up your development environment]( {{< ref "/deployment_environment.md" >}} )
* [Development guidelines]( {{< ref "/guidelines/_index.md" >}} )
* [Concept designs]( {{< ref "concepts" >}} )
* [Supported APIs](https://developer.apertis.org/latest/apis.html)
......
content/deployment_environment.md deleted 100644 → 0
+ 0
− 80
View file @ 697d52ad
+++
date = "2016-11-30"
weight = 100
title = "Deployment Environment"
aliases = [
"/old-wiki/Deployment_Environment"
]
+++
![300px|thumb|Apertis SDK image running in a
VM](/images/vm-sdk.png) You can try out Apertis in a virtual
machine or on real hardware.
[Release](https://images.apertis.org/release/) and [daily
build](https://images.apertis.org/daily/15.12/latest/) 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
<div style="clear: both;">
</div>
## Apertis on reference hardware
![300px|thumb|Base Minnowboard setup with a Lilliput
screen](/images/hardware-intel.jpg) The recommended Intel (64
bit) [reference hardware]( {{< ref "/reference_hardware/_index.md" >}} ) is the
Minnowboard Max with [some optional
extras]( {{< ref "/reference_hardware/_index.md" >}} ). Please see its [setup
guide]( {{< ref "/reference_hardware/minnowboard_setup.md" >}} ) for first-time
setup.
The recommended ARM (32 bit) hardware is the i.MX6 Sabrelite, also with
[some optional extras]( {{< ref "/reference_hardware/_index.md" >}} ). 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/apertis.ssh.pub user@$hostname`
You should then be able to SSH in using:
`ssh $hostname`
content/guidelines/howtodevelopondevices.md
+ 49
− 20
View file @ e10c3e44
......@@ -32,17 +32,17 @@ rootfs managed by OSTree.
Apertis device images come with some restriction out-of-the-box when
trying to develop directly on them:
- only the `target` APT repository is enabled by default, while most
of the useful development tools are in the \`development\`
repository
- the rootfs is mounted read-only
- some utilities are kept to a older, less featureful versions since
the newer ones switched to GPLv3
To easily overcome these issues, Apertis images ship the `apertis-dev`
tool:
<code>
- only the `target` APT repository is enabled by default, while most of the
useful development tools are in the \`development\` repository
- the rootfs is mounted read-only
- some utilities are kept to a older, less featureful versions since the newer
ones switched to GPLv3
- target images deliberately don't have development/debugging tools installed
To easily overcome these issues, Apertis images ship the `apertis-dev` tool. To
get a basic set of development tools (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 --help
usage: sudo apertis-dev [OPTIONS]
......@@ -56,24 +56,53 @@ tool:
--disable-debug: disable debug logging from applications
For developer use only: do not do this in production.
</code>
For instance, to install `gdbserver`, run: <code>
For instance, to install `gdbserver`, run:
$ sudo apertis-dev
$ sudo apt install gdbserver
</code>
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/apertis.ssh.pub user@$hostname
You should then be able to SSH in using:
$ ssh $hostname
# Building software
The recommended environment to build platform packages and application
bundles is the Apertis [SDK]( {{< ref "/sdk.md" >}} ).
The recommended environment to build platform packages and application bundles
is the Apertis [SDK]( {{< ref "/sdk.md" >}} ).
However, it is also possible to build software on the devices directly
with the preparation steps below: <code>
However, it is also possible to build software on the devices directly with the
preparation steps below:
$ sudo apertis-dev --build --gpl3
$ sudo apt install apertis-dev-tools
</code>
content/guides/virtualbox.md
+ 2
− 0
View file @ e10c3e44
......@@ -16,6 +16,8 @@ The recommended virtual machine platform for the AMD64 Apertis system images is
[Apertis SDK]( {{< ref "sdk.md" >}} ) to be run in a virtual machine, though
other image types can also be used.
![300px|thumb|Apertis SDK image running in a VM](/images/vm-sdk.png)
# VirtualBox Setup
......
content/reference_hardware/_index.md
+ 13
− 60
View file @ e10c3e44
......@@ -5,71 +5,24 @@ weight = 100
title = "Reference Hardware"
aliases = [
"/old-wiki/Deployment_Environment",
"/old-wiki/Reference_Hardware"
]
+++
If you currently don't have access to any of the below supported hardware, the
`amd64` images can be run on a
[virtual machine]( {{< ref "/guides/virtualbox.md" >}} ).
## Intel (64 bit) reference hardware
| Reference | Hardware | Comments |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Intel reference device | MinnowBoard Turbot Dual-Core (E3826) | [Setup guide]( {{< ref "/reference_hardware/minnowboard_setup.md" >}} ) The system does not come with a power-supply, be sure to order one seperately |
| Alternative Intel reference device | MinnowBoard Turbot Quad-Core (E3845) | **Untested** |
| MicroSD card | 16GB or larger microSD card | Speed class C10/U1 or better recommended |
| Optional: Multitouch screen | [Lilliput FA1014-NP/C/T](http://www.lilliputdirect.com/lilliput-fa1014-10-inch-capacitive-touchscreen-monitor) | Only needed for developers of multitouch applications or working with the multitouch stack. Other developers can just use a HDMI monitor. Monitor does not ship with a stand - needs to be bought seperately Monitor also functions as audio output. |
| Optional: Bluetooth dongle | [Bluetooth PTS Radio Module](http://www.gvinedesigns.com/shopping/bluetooth/product_detail.cfm?pid=141) | Only needed for Bluetooth testing and development. |
| Optional: Reference phone \#1 | iPhone 6 | Only needed for Bluetooth testing and development. |
| Optional: Reference phone \#2 | Samsung Galaxy J7 (2016) | Only needed for Bluetooth testing and development. |
| Optional: Reference router | [D-link N300 router](http://www.dlink.com/us/en/home-solutions/connect/routers/dir-615-wireless-n-300-router) | Only needed for ConnMan testing and development. |
| Optional: Reference 3G modem | [Huawei E3372 3G modem](http://consumer.huawei.com/en/mobile-broadband/dongles/tech-specs/e3372.htm) | Only needed for 3G connectivity testing and development. |
| Optional: SDK Multi-touch device | [Apple Magic Trackpad](http://store.apple.com/us/product/MC380LL/A/magic-trackpad) | Only needed for multi-touch development. |
| Optional: Reference Webcam | [Logitech HD Pro Webcam C910](http://www.logitech.com/en-in/product/6816) | Only needed for development related with camera features. |
| Optional: Alternative Bluetooth dongle | [Asus USB-BT211 Mini Bluetooth Dongle](http://www.amazon.co.uk/gp/product/B0033CA2XM) | Only needed for development related to BlueTooth. |
| Optional: Wireless dongle | [Asus USB-N10 - 150Mbps Wireless Lan USB Adapter](http://www.amazon.co.uk/gp/product/B002VGQQAE) | Only needed for development related to Wireless. |
## ARM (32 bit) reference hardware
Apertis currently supports a selection of reference hardware designs. These
span the Intel 64-bit, ARM 64-bit and ARM 32-bit architectures:
| Reference | Hardware | Comments |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| ARM reference device | i.MX6 Sabrelite | [Setup guide]( {{< ref "/reference_hardware/imx6q_sabrelite_setup.md" >}} ) |
| Power source | [The 5V+ power source unit](http://www.digikey.com/product-search/en?WT.z_header=search_go&lang=en&site=us&keywords=993-1019-ND&x=14&y=17) that should come with the i.MX6 Sabrelite | |
| SD card | Full-sized SD card (or microSD in full-size adapter), 16GB or larger | Speed class C10/U1 or better recommended |
| Recommended: 100 Mbit network switch or hub | Use a network connection that *does not* support gigabit | Workaround for [reliability issues with this particular hardware when using gigabit](https://community.nxp.com/thread/381119) |
| Recommended: LVDS panel touchscreen | [HannStar HSD100PXN1-A00-C11](https://www.mouser.com/ProductDetail/Boundary-Devices/NIT6X_101HANNSTAR/?qs=%2Fha2pyFaduhICqiA62NC348xLf7lkR37nWVKEUqzpogToe6HSSy1X%2FAMJ8uCmShD) | |
| Recommended: LVDS panel cable | [Cable for LVDS panel](http://boundarydevices.com/products/lvds-cable-for-freescale-10-1-hannstar/) | |
| Recommended: USB to serial adapter | [USB\<-\>serial adapter cable](http://www.amazon.com/TRENDnet-RS-232-Serial-Converter-TU-S9/dp/B0007T27H8/ref=sr_1_1?s=electronics&ie=UTF8&qid=1396528293&sr=1-1&keywords=usb+to+serial+adapter) | To look at the console |
| Recommended: USB keyboard | USB keyboard | |
| Optional: Attached camera | [OV5640-based 5MP MIPI attached camera module](http://boundarydevices.com/products/nit6x_5mp_mipi/) | |
| | | |
- [Intel 64-bit reference hardware]( {{< ref "/reference_hardware/amd64.md" >}} )
- [ARM 32-bit reference hardware]( {{< ref "/reference_hardware/arm32.md" >}} )
- [ARM 64-bit reference hardware]( {{< ref "/reference_hardware/arm64.md" >}} )
- [Optional extra reference hardware]( {{< ref "/reference_hardware/extras.md" >}} )
![SabreLite and touchscreen](/images/hardware-arm.jpg)
Sabrelite and touchscreen
![Sabrelite and back of touchscreen](/images/hardware-arm-back.jpg)
Sabrelite and back of touchscreen
Various prebuilt [images]( {{< ref "images.md" >}} ) are available for testing.
Apertis development is fasted paced, so we recommend that you use the daily
build images whenever possible.
## ARM (64 bit) reference hardware
Starting with the 17.03 release ARM64 images are available. With the
17.03 release only the minimal (headless) image is supported, full
(graphical) bring-up is expected to be done later in 2017. While the
images in principle support various 64 bit ARM boards, Renesas
Generation 3 SoCs are the main target.
The recommend reference boards for these images are the R-Car Starter
Kit boards, however the Salvator-x boards are also support. For more
information about Renesas R-Car starter kit please see the [Renesas
product
page](https://www.renesas.com/en-us/solutions/automotive/adas/solution-kits/r-car-starter-kit.html).
If you currently don't have access to any of the supported hardware, the
`amd64` images can be run on a
[virtual machine]( {{< ref "/guides/virtualbox.md" >}} ).
| Reference | Hardware | Comments |
| ---------------------------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| ARM64 reference device | [Renesas R-Car M3 Starter Kit Pro (M3SK/m3ulcb)](http://elinux.org/R-Car/Boards/M3SK) | [Setup guide]( {{< ref "/reference_hardware/rcar-gen3_setup.md" >}} ) |
| Alternative ARM64 reference device | [Renesas R-Car H3 Starter Kit Premier (H3SK/h3ulcb)](http://elinux.org/R-Car/Boards/H3SK) | [Setup guide]( {{< ref "/reference_hardware/rcar-gen3_setup.md" >}} ) **Untested** |
| | | |
| Alternative ARM64 reference device | [Renesas R-Car H3 Salvator-X (r8a7795-salvator-x)](http://elinux.org/R-Car/Boards/Salvator-X) | [Setup guide]( {{< ref "/reference_hardware/rcar-gen3_setup.md" >}} ) |
| Alternative ARM64 reference device | [Renesas R-Car M3-W Salvator-X (r8a7796-salvator-x)](http://elinux.org/R-Car/Boards/Salvator-X) | [Setup guide]( {{< ref "/reference_hardware/rcar-gen3_setup.md" >}} ) **Untested** |
| | | |
content/reference_hardware/amd64.md 0 → 100644
+ 25
− 0
View file @ e10c3e44
+++
date = "2020-06-10"
weight = 100
title = "Intel 64-bit Reference Hardware"
+++
The recommended Intel 64-bit
[reference hardware]( {{< ref "/reference_hardware/_index.md" >}} )
is the Minnowboard Max. Please see its
[setup guide]( {{< ref "/reference_hardware/minnowboard_setup.md" >}} )
for first-time setup.
The following [optional extras]( {{< ref "/reference_hardware/extras.md" >}} )
may be of interest.
If you currently don't have access to any supported hardware, the `amd64`
images can be run on a
[virtual machine]( {{< ref "/guides/virtualbox.md" >}} ).
| Reference | Hardware | Comments |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Intel reference device | MinnowBoard Turbot Dual-Core (E3826) | [Setup guide]( {{< ref "/reference_hardware/minnowboard_setup.md" >}} ) The system does not come with a power-supply, be sure to order one seperately |
| Alternative Intel reference device | MinnowBoard Turbot Quad-Core (E3845) | **Untested** |
| MicroSD card | 16GB or larger microSD card | Speed class C10/U1 or better recommended |
| Optional: Multitouch screen | [Lilliput FA1014-NP/C/T](http://www.lilliputdirect.com/lilliput-fa1014-10-inch-capacitive-touchscreen-monitor) | Only needed for developers of multitouch applications or working with the multitouch stack. Other developers can just use a HDMI monitor. Monitor does not ship with a stand - needs to be bought seperately Monitor also functions as audio output. |
content/reference_hardware/arm32.md 0 → 100644
+ 30
− 0
View file @ e10c3e44
+++
date = "2020-06-10"
weight = 100
title = "ARM 32-bit Reference Hardware"
+++
The recommended ARM 32-bit hardware is the i.MX6 Sabrelite.
Please see its
[setup guide]( {{< ref "/reference_hardware/imx6q_sabrelite_setup.md" >}} )
for first-time setup.
The following [optional extras]( {{< ref "/reference_hardware/extras.md" >}} )
may be of interest.
If you currently don't have access to any supported hardware, the `amd64`
images can be run on a
[virtual machine]( {{< ref "/guides/virtualbox.md" >}} ).
| Reference | Hardware | Comments |
| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| ARM reference device | i.MX6 Sabrelite | [Setup guide]( {{< ref "/reference_hardware/imx6q_sabrelite_setup.md" >}} ) |
| Power source | [The 5V+ power source unit](http://www.digikey.com/product-search/en?WT.z_header=search_go&lang=en&site=us&keywords=993-1019-ND&x=14&y=17) that should come with the i.MX6 Sabrelite | |
| SD card | Full-sized SD card (or microSD in full-size adapter), 16GB or larger | Speed class C10/U1 or better recommended |
| Recommended: 100 Mbit network switch or hub | Use a network connection that *does not* support gigabit | Workaround for [reliability issues with this particular hardware when using gigabit](https://community.nxp.com/thread/381119) |
| Recommended: LVDS panel touchscreen | [HannStar HSD100PXN1-A00-C11](https://www.mouser.com/ProductDetail/Boundary-Devices/NIT6X_101HANNSTAR/?qs=%2Fha2pyFaduhICqiA62NC348xLf7lkR37nWVKEUqzpogToe6HSSy1X%2FAMJ8uCmShD) | |
| Recommended: LVDS panel cable | [Cable for LVDS panel](http://boundarydevices.com/products/lvds-cable-for-freescale-10-1-hannstar/) | |
| Recommended: USB to serial adapter | [USB\<-\>serial adapter cable](http://www.amazon.com/TRENDnet-RS-232-Serial-Converter-TU-S9/dp/B0007T27H8/ref=sr_1_1?s=electronics&ie=UTF8&qid=1396528293&sr=1-1&keywords=usb+to+serial+adapter) | To look at the console |
| Recommended: USB keyboard | USB keyboard | |
| Optional: Attached camera | [OV5640-based 5MP MIPI attached camera module](http://boundarydevices.com/products/nit6x_5mp_mipi/) | |
| | | |
content/reference_hardware/arm64.md 0 → 100644
+ 31
− 0
View file @ e10c3e44
+++
date = "2020-06-10"
weight = 100
title = "ARM 64-bit Reference Hardware"
+++
Starting with the 17.03 release, ARM64 images have been made available. While
the images in principle support various 64 bit ARM boards, Renesas Generation 3
SoCs are the main target.
The recommend reference boards for these images are the R-Car Starter Kit
boards, however the Salvator-x boards are also supported. For more information
about Renesas R-Car starter kit please see the
[Renesas product page](https://www.renesas.com/en-us/solutions/automotive/adas/solution-kits/r-car-starter-kit.html).
The following [optional extras]( {{< ref "/reference_hardware/extras.md" >}} )
may be of interest.
If you currently don't have access to any of the below supported hardware, the
`amd64` images can be run on a
[virtual machine]( {{< ref "/guides/virtualbox.md" >}} ).
| Reference | Hardware | Comments |
| ---------------------------------- | ----------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| ARM64 reference device | [Renesas R-Car M3 Starter Kit Pro (M3SK/m3ulcb)](http://elinux.org/R-Car/Boards/M3SK) | [Setup guide]( {{< ref "/reference_hardware/rcar-gen3_setup.md" >}} ) |
| Alternative ARM64 reference device | [Renesas R-Car H3 Starter Kit Premier (H3SK/h3ulcb)](http://elinux.org/R-Car/Boards/H3SK) | [Setup guide]( {{< ref "/reference_hardware/rcar-gen3_setup.md" >}} ) **Untested** |
| | | |
| Alternative ARM64 reference device | [Renesas R-Car H3 Salvator-X (r8a7795-salvator-x)](http://elinux.org/R-Car/Boards/Salvator-X) | [Setup guide]( {{< ref "/reference_hardware/rcar-gen3_setup.md" >}} ) |
| Alternative ARM64 reference device | [Renesas R-Car M3-W Salvator-X (r8a7796-salvator-x)](http://elinux.org/R-Car/Boards/Salvator-X) | [Setup guide]( {{< ref "/reference_hardware/rcar-gen3_setup.md" >}} ) **Untested** |
| | | |
content/reference_hardware/extras.md 0 → 100644
+ 22
− 0
View file @ e10c3e44
+++
date = "2020-06-10"
weight = 100
title = "Optional Extra Reference Hardware"
+++
The following optional extras are those used for testing in combination with
the reference hardware platforms.
| Reference | Hardware | Comments |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Bluetooth dongle | [Bluetooth PTS Radio Module](http://www.gvinedesigns.com/shopping/bluetooth/product_detail.cfm?pid=141) | Only needed for Bluetooth testing and development. |
| Reference phone \#1 | iPhone 6 | Only needed for Bluetooth testing and development. |
| Reference phone \#2 | Samsung Galaxy J7 (2016) | Only needed for Bluetooth testing and development. |
| Reference router | [D-link N300 router](http://www.dlink.com/us/en/home-solutions/connect/routers/dir-615-wireless-n-300-router) | Only needed for ConnMan testing and development. |
| Reference 3G modem | [Huawei E3372 3G modem](http://consumer.huawei.com/en/mobile-broadband/dongles/tech-specs/e3372.htm) | Only needed for 3G connectivity testing and development. |
| SDK Multi-touch device | [Apple Magic Trackpad](http://store.apple.com/us/product/MC380LL/A/magic-trackpad) | Only needed for multi-touch development. |
| Reference Webcam | [Logitech HD Pro Webcam C910](http://www.logitech.com/en-in/product/6816) | Only needed for development related with camera features. |
| Alternative Bluetooth dongle | [Asus USB-BT211 Mini Bluetooth Dongle](http://www.amazon.co.uk/gp/product/B0033CA2XM) | Only needed for development related to BlueTooth. |
| Wireless dongle | [Asus USB-N10 - 150Mbps Wireless Lan USB Adapter](http://www.amazon.co.uk/gp/product/B002VGQQAE) | Only needed for development related to Wireless. |
content/reference_hardware/imx6q_sabrelite_setup.md
+ 74
− 74
View file @ e10c3e44
......@@ -2,26 +2,27 @@
date = "2019-11-08"
weight = 100
title = "i.MX6Q Sabrelite Setup"
title = "i.MX6Q SABRE Lite Setup"
aliases = [
"/old-wiki/Reference_Hardware/imx6q_sabrelite_setup"
]
+++
This is the setup recommended for developers using the Sabrelite
directly. See
[Reference_Hardware/imx6q_sabrelite_setup_lava]( {{< ref "/reference_hardware/imx6q_sabrelite_setup_lava.md" >}} )
![SabreLite and touchscreen](/images/hardware-arm.jpg)
This is the setup recommended for developers using the Sabrelite directly. See
[SABRE Lite LAVA setup]( {{< ref "/reference_hardware/imx6q_sabrelite_setup_lava.md" >}} )
for setting up devices for use in LAVA.
# Required items
You should have at least:
- 1 SABRE Lite board
- 1 Power adaptor
- 1 USB to serial cable (RS232 line voltages)
- 1 SD card, with adapter if MicroSD card used (at least 8GB)
- 1 SABRE Lite board
- 1 Power adaptor
- 1 USB to serial cable (RS232 line voltages)
- 1 SD card, with adapter if MicroSD card used (at least 8GB)
# SABRE Lite board setup
......@@ -30,17 +31,16 @@ expects to be flashed into the NOR Flash on SPI. This is preferred over
storing U-Boot on the SD card as it allows a common Apertis image to be
programmed onto the SD card.
- Download and program the SABRE Lite installer (called
`uboot-`<version>`-installer-mx6qsabrelite.img.gz` to the SD card.
Images can be found under the `installer` directory of the relevant
release on the [Apertis image download](https://images.apertis.org/)
site.
- Insert the SD card into the full SD card slot on the rear of the
board, labelled `SD3` **not** the MicroSD card slot on the front
labelled `SD4/BOOT`.
- Attach the serial breakout cable to the SABRE Lite and connect the
DB9 connector labelled \`CONSOLE\` to the USB to serial cable.
- Ensure the SW1 switches are in the following positions:
- Download and program the SABRE Lite installer (called
`uboot-<version>-installer-mx6qsabrelite.img.gz` to the SD card. Images can
be found under the `installer` directory of the relevant release on the
[Apertis image download](https://images.apertis.org/) site.
- Insert the SD card into the full SD card slot on the rear of the board,
labelled `SD3` **not** the MicroSD card slot on the front labelled
`SD4/BOOT`.
- Attach the serial breakout cable to the SABRE Lite and connect the DB9
connector labelled `CONSOLE` to the USB to serial cable.
- Ensure the `SW1` switches are in the following positions:
| | | |
| ------ | -------- | -------------------------------------------------------------------- |
......@@ -48,9 +48,9 @@ programmed onto the SD card.
| SW1.1 | 0 | |
| SW1.2 | 0 | |
- Power up the SABRE Lite.
- Once the SABRE Lite has finished programming, the following message
will be displayed:
- Power up the SABRE Lite.
- Once the SABRE Lite has finished programming, the following message will be
displayed:
<!-- end list -->
......@@ -60,25 +60,24 @@ programmed onto the SD card.
| Please remove the SD Card and power cycle the board to continue |
+-----------------------------------------------------------------+
- Remove the SD card and power off the board.
- Download and program the required arm64 Apertis image from the
[Apertis image download](https://images.apertis.org/) site onto the
SD card.
- Insert the SD card into the into the full SD card slot on the rear
of the board, labelled `SD3` **not** the MicroSD card slot on the
front labelled `SD4/BOOT`.
- Power up the SABRE Lite.
- Remove the SD card and power off the board.
- Download and program the required arm64 Apertis image from the
[Apertis image download](https://images.apertis.org/) site onto the SD card.
- Insert the SD card into the into the full SD card slot on the rear of the
board, labelled `SD3` **not** the MicroSD card slot on the front labelled
`SD4/BOOT`.
- Power up the SABRE Lite.
# Flash the SABRE Lite NOR if SD card not booting
If the SD card procedure above is not working, it may be that the NOR
Flash is not in the required state. We can recover from this situation
by booting via USB-OTG.
If the SD card procedure above is not working, it may be that the NOR Flash is
not in the required state. We can recover from this situation by booting via
USB-OTG.
In addition to the items outlined in the "Required items" section you
will need a USB to microUSB cable.
In addition to the items outlined in the "Required items" section you will need
a USB to microUSB cable.
- Download and build the imx loader:
- Download and build the imx loader:
<!-- end list -->
......@@ -87,10 +86,9 @@ will need a USB to microUSB cable.
$ cd imx_usb_loader
$ make
- Ensure the SABRE Lite is powered down.
- Attach the microUSB cable to the `USB OTG` port and the other to
your host.
- Ensure the SW1 switches are in the following positions:
- Ensure the SABRE Lite is powered down.
- Attach the microUSB cable to the `USB OTG` port and the other to your host.
- Ensure the `SW1` switches are in the following positions:
| | | |
| ------ | -------- | -------------------------------------------------------------------- |
......@@ -98,35 +96,36 @@ will need a USB to microUSB cable.
| SW1.1 | 0 | |
| SW1.2 | 1 | |
- Download and program the SABRE Lite installer (called
`uboot-`<version>`-installer-mx6qsabrelite.img.gz` to the SD card.
Images can be found under the `installer` directory of the relevant
release on the [Apertis image download](https://images.apertis.org/)
site.
- Mount the `data` partition on the SD card and retrieve the
`u-boot.imx` file from `deb-binaries/usr/lib/u-boot/mx6qsabrelite/`
and copy to the folder where the imx loader was cloned.
- Unmount the SD card and insert the SD card into the full SD card
slot on the rear of the board, labelled `SD3` **not** the MicroSD
card slot on the front labelled `SD4/BOOT`.
- Power up the board.
- The following USB device should show as being attached to your host:
- Download and program the SABRE Lite installer (called
`uboot-`<version>`-installer-mx6qsabrelite.img.gz` to the SD card. Images
can be found under the `installer` directory of the relevant release on the
[Apertis image download](https://images.apertis.org/) site.
- Mount the `data` partition on the SD card and retrieve the `u-boot.imx` file
from `deb-binaries/usr/lib/u-boot/mx6qsabrelite/` and copy to the folder
where the imx loader was cloned.
- Unmount the SD card and insert the SD card into the full SD card slot on the
rear of the board, labelled `SD3` **not** the MicroSD card slot on the front
labelled `SD4/BOOT`.
- Power up the board.
- The following USB device should show as being attached to your host:
<!-- end list -->
$ lsusb -d15a2:0054
Bus 002 Device 048: ID 15a2:0054 Freescale Semiconductor, Inc. i.MX 6Dual/6Quad SystemOnChip in RecoveryMode
$ From the location where imx loader was cloned and built, run the
following command:
- From the location where imx loader was cloned and built, run the following
command:
<!-- end list -->
$ sudo imx_usb ./u-boot.imx
- Board should boot U-Boot and program the flash using the image on
the SD card.
- This step is needed **ONLY** in case if you see the U-Boot prompt
\`=\>\` -- usually it happens if you flash different U-Boot version.
You have to reset default environment and start the boot process:
- Board should boot U-Boot and program the flash using the image on the SD
card.
- This step is needed **ONLY** in case if you see the U-Boot prompt `=>`,
usually it happens if you flash different U-Boot version. You have to reset
default environment and start the boot process:
<!-- end list -->
......@@ -134,8 +133,8 @@ following command:
saveenv
run bootcmd
- Once the SABRE Lite has finished programming, the following message
will be displayed:
- Once the SABRE Lite has finished programming, the following message
will be displayed:
<!-- end list -->
......@@ -145,9 +144,9 @@ following command:
| Please remove the SD Card and power cycle the board to continue |
+-----------------------------------------------------------------+
- Remove the SD card and power down the board.
- Ensure the SW1 switches are returned to the following positions to
allow normal booting:
- Remove the SD card and power down the board.
- Ensure the `SW1` switches are returned to the following positions to allow
normal booting:
| | | |
| ------ | -------- | -------------------------------------------------------------------- |
......@@ -155,19 +154,20 @@ following command:
| SW1.1 | 0 | |
| SW1.2 | 0 | |
# Known issues
## Gigabit networks
The i.MX6 internal bus is too slow for full speed 1Gbps traffic, to
avoid congestion and dropped frames the [kernel tells the hardware to
send "pause"
frames](http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/140114.html)
The i.MX6 internal bus is too slow for full speed 1Gbps traffic, to avoid
congestion and dropped frames the
[kernel tells the hardware to send "pause" frames](http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/140114.html)
if switches say that they support them to slow down the flow.
Unfortunately some switches say that they support pause frames but get
badly confused by them, causing severe packet loss.
Unfortunately some switches say that they support pause frames but get badly
confused by them, causing severe packet loss.
The best workaround is to buy an inexpensive 100Mbps switch and
interpose it between the device and the affected 1000Mbps switch to
force the i.MX6 connection to a slower but safe speed.
The best workaround is to buy an inexpensive 100Mbps switch and interpose it
between the device and the affected 1000Mbps switch to force the i.MX6
connection to a slower but safe speed.
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
Apertis Website Terms of Use Privacy Policy