Open main menu

DAVE Developer's Wiki β

Changes

Axel Embedded Linux Kit (XELK)

11,351 bytes added, 16:18, 31 August 2022
no edit summary
{{AppliesToAxelEsatta}}
{{InfoBoxBottom}}
 
{{ObsoleteWikiPage|link=DESK-MX6-L}}
==Introduction==
{{ImportantMessage|text='''Customers are strongly recommended to register their kits'''. Registration grants access to reserved material such as source code and additional documentation.
 
To register the kit, please send an email to [mailto:support-axel@dave.eu support-axel@dave.eu], [[Development_Kits_Identification_Codes|providing the kit P/N and S/N]].}}
[[File:Axel-on-evb-02.png|500px]]
|-
| style="text-align: center;" | [[File:Axel-01.png|60px]]
|Axel Ultra SOM (or Axel Lite SOM) <br>CPU: Freescale i.MX6<br>SDRAM: 2 GB DDR3<br>NOR: bootable SPI flash 32 MB<br>NAND: 1GB
|Please refer to [[Hardware Manual (AxelUltra) | Axel Ultra Hardware Manual]]
|-
| style="text-align: center;" | [[File:AxelLite-SOM.jpg|80px]]
|Axel Lite SOM<br>CPU: Freescale i.MX6<br>SDRAM: 2 GB DDR3<br>NOR: bootable SPI flash 32 MB<br>NAND: 1GB
|Please refer to [[Hardware Manual (AxelLite) | Axel Lite Hardware Manual]]
|-
| style="text-align: center;" | [[File:Axelevb-lite-01.png|60px]]
{| class="wikitable"
!
! colspan="811" | XELK version
|-
|Release number
|2.3.1
|3.0.1
|3.5.0
|4.0.0
|4.1.1
|-
|Release type
|Maintenance
|Major
|Maintenance
|Major
|Maintenance
|-
|Status
|Released
|Released
|Released
|Released
|Released
|October 2016
|November 2017
|April 2019
|August 2019
|August 2020
|-
|'''Release notes'''
|[[#XELK 2.3.1 | Ver 2.3.1]]
|[[#XELK 3.0.1 | Ver 3.0.1]]
|[[#XELK 3.5.0 | Ver 3.5.0]]
|[[#XELK 4.0.0 | Ver 4.0.0]]
| [[Axel Embedded Linux Kit (XELK)#XELK 4.1.1|Ver 4.1.1]]
|-
|SOM PCB version
|Axel Ultra: CS030713B<br>Axel Lite: CS335013A
|Axel Ultra: CS030713B<br>Axel Lite: CS335013A<br>Axel Lite: CS335013C
|Axel Lite: CS335013A<br>Axel Lite: CS335013C
|Axel Lite: CS335013A<br>Axel Lite: CS335013C
|Axel Lite: CS335013A<br>Axel Lite: CS335013C
|Axel Lite: CS335013A<br>Axel Lite: CS335013C
|--
|{{pageoldid|AxelEVB-Lite|2970}}<br>[[AxelEVB-Lite|AxelEVB-Lite rev.A]]<br>[[:Category:Dacu | Dacu]]<br>[[:Category:SBC-AXEL | SBCX]]
|{{pageoldid|AxelEVB-Lite|2970}}<br>[[AxelEVB-Lite|AxelEVB-Lite rev.A]]<br>[[:Category:Dacu | Dacu]]<br>[[:Category:SBC-AXEL | SBCX]]
|{{pageoldid|AxelEVB-Lite|2970}}<br>[[AxelEVB-Lite|AxelEVB-Lite rev.A]]<br>[[:Category:Dacu | Dacu]]<br>[[:Category:SBC-AXEL | SBCX]]
|{{pageoldid|AxelEVB-Lite|2970}}<br>[[AxelEVB-Lite|AxelEVB-Lite rev.A]]<br>[[:Category:Dacu | Dacu]]<br>[[:Category:SBC-AXEL | SBCX]]
|{{pageoldid|AxelEVB-Lite|2970}}<br>[[AxelEVB-Lite|AxelEVB-Lite rev.A]]<br>[[:Category:Dacu | Dacu]]<br>[[:Category:SBC-AXEL | SBCX]]
|-
|MVM (distro version)
|Ubuntu 12.04
|Ubuntu 12.04
|Ubuntu 12.04
|Ubuntu 12.04
|Ubuntu 12.04
|Ubuntu 12.04
|Ubuntu 12.04
|Ubuntu 14.04
|Ubuntu 14.04
|Ubuntu 14.04
|Ubuntu 14.04
|-
|U-Boot version
|2013.04-xelk-2.3.1
|2016.03-xelk-3.0.2
|2016.03-xelk-3.5.0
|2017.03-xelk-4.0.0
|2017.03-xelk-4.0.0
|-
|Linux version
|3.10.17-xelk-2.3.1
|4.1.15-xelk-3.0.0
|4.1.15-xelk-3.0.0
|4.9.11-xelk-4.0.0
|4.9.11-xelk-4.1.1
|-
|Drivers
| valign="top" | SPI NOR Flash (boot)<br>UART debug (2-wire)<br>USB Host<br>USB OTG<br>SD/MMC1<br>CAN<br>Touch screen controller<br>EMAC<br>SATA<br>HDMI<br>LVDS0<br>NAND<br>RTC<br>I2C<br>SPI<br>Video Input (MIPI)<br>PCIe<br>[[ConfigID_and_UniqueID | ConfigID]]<br>Splash screen (U-Boot) [1]
| valign="top" | SPI NOR Flash (boot)<br>UART debug (2-wire)<br>USB Host<br>USB OTG<br>SD/MMC1<br>CAN<br>Touch screen controller<br>EMAC<br>SATA<br>HDMI<br>LVDS0<br>NAND<br>RTC<br>I2C<br>SPI<br>Video Input (MIPI)<br>PCIe<br>[[ConfigID_and_UniqueID | ConfigID]]<br>Splash screen (U-Boot) [1]
| valign="top" | SPI NOR Flash (boot)<br>UART debug (2-wire)<br>USB Host<br>USB OTG<br>SD/MMC1<br>CAN<br>Touch screen controller<br>EMAC<br>SATA<br>HDMI<br>LVDS0<br>NAND<br>RTC<br>I2C<br>SPI<br>Video Input (MIPI)<br>PCIe<br>[[ConfigID_and_UniqueID | ConfigID]]<br>Splash screen (U-Boot) [1]<br>SPL boot[2]
| valign="top" | SPI NOR Flash (boot)<br>UART debug (2-wire)<br>USB Host<br>USB OTG<br>SD/MMC1<br>CAN<br>Touch screen controller<br>EMAC<br>SATA<br>HDMI<br>LVDS0<br>NAND<br>RTC<br>I2C<br>SPI<br>Video Input (MIPI)<br>PCIe<br>[[ConfigID_and_UniqueID | ConfigID]]<br>Splash screen (U-Boot) [1]<br>SPL boot[2]
| valign="top" | SPI NOR Flash (boot)<br>UART debug (2-wire)<br>USB Host<br>USB OTG<br>SD/MMC1<br>CAN<br>Touch screen controller<br>EMAC<br>SATA<br>HDMI<br>LVDS0<br>NAND<br>RTC<br>I2C<br>SPI<br>Video Input (MIPI)<br>PCIe<br>[[ConfigID_and_UniqueID | ConfigID]]<br>Splash screen (U-Boot) [1]<br>SPL boot[2]
|-
|NXP/Freescale BSP version
|L3.10.17-1.0.3
|L4.1.15-2.0.0
|L4.1.15-2.0.0
|L4.9.11_1.0.0
|L4.9.11_1.0.0
|-
|Graphic libraries
|Qt 5.3.2
|Qt 5.6.2
|Qt 5.6.2
|Qt 5.9.8
|Qt 5.9.8
|-
|Build System
|Yocto Dora (1.5)
|Yocto Krogoth (2.1)
|Yocto Krogoth (2.1)
|Yocto Morty (2.2)
|Yocto Morty (2.2)
|-
|Android
|Kitkat 4.4.2
|Marshmallow 6.0.1
|Marshmallow 6.0.1
|
|
|}
[1] Splashscreen on LVDS0
 
[2] U-Boot SPL version
====Downloadable binary images====
*bootscript: <code>boot.scr</code>
U-boot file <code>u-boot.imx</code> must be stored into first raw sector of the SD card using <code>dd</code> command}}  {{ImportantMessage|text=Since '''XELK-3.5.0''' U-boot performs 2-stage bootloader providing two files: SPL and u-boot.img.
Both two files must be stored into SD card using <code>dd</code> command}}
{| class="wikitable"
|-
|-
| Device tree (DualLite processor) || [[mirror:axel/xelk-3.0.1/xelk-3.0.0_imx6dl-xelk-l.dtb|imx6dl-xelk-l.dtb]] || [[mirror:axel/xelk-3.0.1/xelk-3.0.0_imx6dl-sbcx-cb0012.dtb|imx6dl-sbcx-cb0012.dtb]] || [[mirror:axel/xelk-3.0.1/xelk-3.0.0_imx6dl-sbcx-cb0013.dtb|imx6dl-sbcx-cb0013.dtb]]
|}
 
{| class="wikitable"
|-
! Image !! colspan="3" |XELK version 3.5.0 (QUAD/DUAL LITE)
|-
| Platform || colspan="2" style="text-align: center" |XELK / SBCX
|-
| U-Boot SPL || colspan="1" style="text-align: center" |[[mirror:axel/xelk-3.5.0/xelk-3.5.0_mx6qdlaxel_spi_SPL|SPL (boot from NOR)]] || colspan="1" style="text-align: center" |[[mirror:axel/xelk-3.5.0/xelk-3.5.0_mx6qdlaxel_nand_SPL|SPL (boot from NAND)]]
|-
| U-Boot img || colspan="1" style="text-align: center" |[[mirror:axel/xelk-3.5.0/xelk-3.5.0_mx6qdlaxel_spi_u-boot.img| img (boot from NOR)]] || colspan="1" style="text-align: center" |[[mirror:axel/xelk-3.5.0/xelk-3.5.0_mx6qdlaxel_nand_u-boot.img|img (boot from NAND)]]
|}
 
{| class="wikitable"
|-
! Image !! colspan="5" |XELK version 4.1.1
|-
| Platform || XELK rev.A || SBCX rev.B || SBCX rev.B
|-
| Carrier Board [[ConfigID_and_UniqueID | ConfigID]]|| 0001 || 0012 || 0013
|-
| LCD panel || colspan="5" style="text-align: center" | Ampire 800 x 480 7" LVDS 262K colors (RGB666)<br>(AM-800480STMQW-TA1 or AM-800480SETMQW-TA1H)
|-
| Touchscreen || colspan="1" | resistive || colspan="1" | resistive || colspan="1" style="text-align: center" | capacitive
|-
| bootscript || colspan="1" style="text-align: center" |[[mirror:axel/xelk-4.1.1/boot.scr|boot.scr]] || colspan="4" style="text-align: center" |[[mirror:axel/xelk-4.1.1/boot.scr|boot.scr]]
|-
| U-Boot SPL || colspan="1" style="text-align: center" |[[mirror:axel/xelk-4.0.0/xelk-4.0.0_mx6qdlaxel_spi_SPL|SPL (Quad - boot from NOR)]] || colspan="4" style="text-align: center" |[[mirror:axel/xelk-4.0.0/xelk-4.0.0_mx6qdlaxel_nand_SPL|SPL (DualLite - boot from NAND)]]
|-
| U-Boot || colspan="1" style="text-align: center" |[[mirror:axel/xelk-4.0.0/xelk-4.0.0_mx6qdlaxel_spi_u-boot.img|img (Quad - boot from NOR)]] || colspan="4" style="text-align: center" |[[mirror:axel/xelk-4.0.0/xelk-4.0.0_mx6qdlaxel_nand_u-boot.img|img (DualLite - boot from NAND)]]
|-
| Linux kernel || colspan="5" style="text-align: center" |[[mirror:axel/xelk-4.1.1/xelk-4.1.1_uImage|uImage]]
|-
| Device tree (Quad processor) || [[mirror:axel/xelk-4.1.1/xelk-4.1.1_imx6q-xelk-l-2.0.0.dtb|imx6q-xelk-l-2.0.0.dtb]] || [[mirror:axel/xelk-4.1.1/xelk-4.1.1_imx6q-sbcx-cb0012.dtb|imx6q-sbcx-cb0012.dtb]] || [[mirror:axel/xelk-4.1.1/xelk-4.1.1_imx6q-sbcx-cb0013.dtb|imx6q-sbcx-cb0013.dtb]]
|-
| Device tree (DualLite processor) || [[mirror:axel/xelk-4.1.1/xelk-4.1.1_imx6dl-xelk-l.dtb|imx6dl-xelk-l.dtb]] || [[mirror:axel/xelk-4.1.1/xelk-4.1.1_imx6dl-sbcx-cb0012.dtb|imx6dl-sbcx-cb0012.dtb]] || [[mirror:axel/xelk-4.1.1/xelk-4.1.1_imx6dl-sbcx-cb0013.dtb|imx6dl-sbcx-cb0013.dtb]]
|}
* VirtualBox virtual machine (.OVA archive)
* Based on Lubuntu 1214.04 LTS (64-bit version)
* Pre-installed VirtualBox Guest Additions
* LXDE desktop environment
* Boot disk with the distro and pre-configured basic Linux services:
** TFTP: with base directory <code>/srv/tftp/</code>** NFS: configured through the <code>/etc/exports </code> file
* Secondary disk containing source code and tools:
** Bootloader (u-boot) source tree cloned from DAVE Embedded Systems public git repository
==== Updating git repositories ====
 In XELK, the following source trees are clones of the correspondent '''DAVE Embedded Systems''' public git repositories: {| class="wikitable"
|-
!| Component
!GIT Remote
!XELK Installation Directory
|-
|LinuxU-Boot|<code>git@git.dave.eu:dave/axel/linuxu-2.6boot-imx.git|</home/dvdk/xelk/linux-2.6-imxcode>
|-
|U-BootLinux kernel|<code>git@git.dave.eu:dave/axel/ulinux-boot2.6-imx.git|/home/dvdk</xelk/u-boot-imxcode>
|-
|Yocto BSP
|<code>git@git.dave.eu:dave/axel/axel-bsp.git|</home/dvdk/xelk/axel-bsp|-code>
|}
For more information about the access to these repositories, please refer to [[Building_the_Yocto_BSP_(XELK)|this link]].
 
Access to DAVE Embedded Systems' git repositories is granted to development kit's owners only. Please refer to [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|this page]] for detailed instructions on how to get access.
 
==== Synchronizing the repository ====
 
The components listed in the table above can be kept in sync and up to date with DAVE Embedded Systems' repositories.
 
Once the git account has been enabled, the developer can:
*clone the repository with the <code>git clone <git_remote_repository></code> command
*synchronize a source tree entering the repository directory and launching the <code>git fetch origin</code> command.
 
Please note that git fetch doesn't merge the commits on the current branch. To do that, the developer should run the <code>git merge</code> command or replace the ''fetch-merge'' process with a single <code>git pull</code> command. Please note that the recommended method is the ''fetch-merge'' process. For further information on Git, please refer to the official Git Documentation (http://git-scm.com
 
== Release types ==
XELK release type can be:* '''Major''', when substantial changes are applied to the BSP (eg: major kernel version upgrades) or to the development kit (eg: new features, build system updates, ..). This usually means that these components can be kept in sync and up to date with a new DVDK is created for the XELK release* '''DAVE Embedded SystemsMaintenance''' , when minor updates and bug fixes are introduced. This usually means that the DVDK remains the same provided with the previous major version, and only an update of the source tree repositories(and the tftp binaries) is required As an example, XELK 2.2.0 is a maintenance release, so it provides the DVDK released with the 2.0.0 major release; customers can easily upgrade to the 2.2.0 release by updating the software components as described in [[Axel_Embedded_Linux_Kit_(XELK)#XELK_Updates|XELK Updates]].
==== RSA key generation ==Release notes ==
Please follow {{ImportantMessage|text=After the procedure reported below to generate XELK DVDK installation, please check for updates of the RSA ssh key:source tree repositories provided with the kit, as described in [[Axel_Embedded_Linux_Kit_(XELK)#XELK_Updates | XELK Updates]].}}
* select your username (ad es=== XELK 4. username@myhost1.com)* start the DVDK and login into the virtual machine* start a shell session* enter the .ssh subdirectory into your home directory: <code>cd ~/.ssh/</code>* launch the following command: <br><pre>ssh-keygen -t rsa -C "username@myhost.com" -f username@myhost.com</pre>* this command creates the files <code>~/.ssh/username@myhost.com</code> ('''private key''') and <code>~/.ssh/username@myhost.com.pub</code> ('''public key''')* edit your <code>~/.ssh/config</code> adding the following lines:1 ===
<pre>Host git.dave.eu User git Hostname git.dave.eu PreferredAuthentications publickey IdentityFile ~/.ssh/username@myhost.com</pre>Release notes:
Please send the public key file to one of the following email * Added kernel support addresses (depending on which for AxelLite SOM is included in your kit version)with iMX6Q @1.2GHz and NOR SPI ISSI model
* [mailto:support-axel@dave.eu support-axel@dave.eu]
with the request for the creation of a new public git account associated to your username=== XELK 4. The support team will enable the account and send you a confirmation as soon as possible1.0 ===
==== Synchronizing the repository ====Release notes:
When the account is enabled* Updated Yocto targets recipes: added X11, you can synchronize a source tree entering the repository directory and launching the <code>git fetch</code> commandbrowser, like in the following example:Qt5 Wayland root file system images
<pre class="workstation-terminal">dvdk@dvdk-vm:~$ cd /home/dvdk/xelk/linux-2== XELK 4.6-imx/dvdk@dvdk-vm:/home/dvdk/xelk/linux-20.6-imx$ git fetch origin</pre>0 ===
Please note that <code>git fetch</code> doesn{{ImportantMessage|text=New MVM must be installed for using XELK-4.0.0. The VM is available for download on DAVE't merge the commits on the current branchs XELK Reserved Area for registered users. To do that, you should run }}
<pre class="workstation-terminal">git merge origin/axel</pre>Release notes:
or replace the ''fetch-merge'' process with a single <code>git pull</code> command* Major change to NXP BSP 4. Please note that the recommended method is the ''fetch-merge'' process9. For further information on Git, please refer to [http://git11* Updated u-scm.com/documentation Git Documentation].boot and kernel versions* Updated Yocto version* Updated Qt version
== Release types == Known Limitations ====
The following table reports the known limitations of this XELK release type can be:* '''Major''', when substantial changes are applied to the BSP (eg: major kernel version upgrades) or to the development kit (eg: new features, build system updates, ..). This usually means that a new DVDK is created for the XELK release* '''Maintenance''', when minor updates and bug fixes are introduced. This usually means that the DVDK remains the same provided with the previous major version, and only an update of the source tree repositories (and the tftp binaries) is required
As an example, XELK 2.2.0 {| class="wikitable" |-!Issue!Description|-|NAND Samsung|NAND Model K9F4G08U0D not detected in u-boot|-|Linux kernel <code>xconfig</code>|<code>make xconfig</code> does not work|-|Wayland not supported|Yocto QT5 images with Wayland backend is a maintenance release, so it provides the DVDK released with the 2.0.0 major release; customers can easily upgrade to the 2.2.0 release by updating the software components as described in [[Axel_Embedded_Linux_Kit_(XELK)#XELK_Updatesnot yet supported|-|XELK Updates]].}
== Release notes = XELK 3.5.0 ===
{{ImportantMessage|text=After NXP iMX6 silicon revision 1.4 limited the XELK DVDK installation, please check for updates of u-boot binary size (due to bug fix in bootrom code). This required the source tree repositories provided with the kit, as described in [[Axel_Embedded_Linux_Kit_switch to u-boot <b>SPL</b> version (XELKfirst and second stage)#XELK_Updates | XELK Updates]].}}
=== XELK 3.0.1 ===Release notes:
* Release date: 17/11/2017* Status: released* NXP Linux BSP: L4.1.15Major change to u-2.0.0boot SPL version* Supported carrier boards: AxelEVBUpdated u-Lite on Dacu, SBCXboot version
==== Notes =XELK 3.0.1 ===
{{ImportantMessage|text=New MVM must be installed for using XELK-3.0.1. The VM is available for download on DAVE's XELK Reserved Area for registered users.}}
 
Release notes:
* Major change to NXP BSP 4.1.15
* Updated Qt version
=== XELK 2.3.1 older releases ===
* Release date: 18/10/2016* Status: released* Freescale Linux BSP: L3.10.17-1.0.3* Supported carrier boards: SBCXFor XELK older ''unsupported'' releases information, please click on Expand here below (on the right)
<div class="mw-collapsible mw-collapsed"> === Notes = XELK 2.3.1 ====
{{ImportantMessage|text=It's highly recommended to read the [[ConfigID and UniqueID]] page.}}
 
Release notes:
* Added support for other ConfigID splash screen on u-boot
* Bug fixes and minor changes
==== XELK 2.2.0 === * Release date: 03/02/2016* Status: released* Freescale Linux BSP: L3.10.17-1.0.3* Supported carrier boards: AxelEVB-Lite on Dacu, SBCX ==== Notes ====
{{ImportantMessage|text=It's highly recommended to read the [[ConfigID and UniqueID]] page.}}
* Bug fixes and minor changes
===== Known Limitations =====
The following table reports the known limitations of this XELK release:
|}
==== XELK 2.1.0 === * Release date: 04/05/2015* Status: released* Freescale Linux BSP: L3.10.17-1.0.0* Supported carrier boards: AxelEVB-Lite on Dacu ==== Notes ====
{{ImportantMessage|text=It's highly recommended to read the [[ConfigID and UniqueID]] page.}}
* Bug fixes and minor changes
===== Known Limitations =====
The following table reports the known limitations of this XELK release:
|}
==== XELK 2.0.0 === * Release date: 26/11/2014* Status: released* Freescale Linux BSP: L3.10.17-1.0.0* Supported carrier boards: AxelEVB-Lite on Dacu ==== Notes ====
* Added support for Yocto 1.5
* Bug fixes and minor changes
===== Known Limitations =====
The following table reports the known limitations of this XELK release:
|}
==== XELK 1.2.0 === * Release date: 20/05/2014* Status: released* Freescale Linux BSP: L3.0.35-4.1.0* Supported carrier boards: AxelEVB-Lite on Dacu ==== Notes ====
* Added support for Axel Lite SOM
* Bug fixes and minor changes
===== Known Limitations =====
The following table reports the known limitations of this XELK release:
|}
==== XELK 1.1.0 === * Release date: January, 29th 2014* Status: released* Freescale Linux BSP: L3.0.35-4.1.0* Supported carrier boards: AxelEVB-Lite on Dacu ==== Notes ====
* Minor update that adds support for more peripherals: nand, rtc, i2c, spi
* The system can boot from SD
===== Known Limitations =====
The following table reports the known limitations of this XELK release:
|}
==== XELK 1.0.0 === * Release date: November, 4th 2013* Status: released* Freescale Linux BSP: L3.0.35-4.1.0* Supported carrier boards: AxelEVB-Lite on Dacu ==== Notes ====
* First official release
===== Known Limitations =====
The following table reports the known limitations of this XELK release:
|-
|}
 
</div>
 
== Quick start guide ==
This chapter describes how to quickly start working with the XELK kit. The following paragraphs will guide you through the setup and installation procedures.
 
===Kit registration===
{{ImportantMessage|text='''Customers are strongly recommended to register their kits'''. Registration grants access to reserved material such as source code and additional documentation.}}
 
To register the kit, please send an email to [mailto:support-axel@dave.eu support-axel@dave.eu], [[Development_Kits_Identification_Codes|providing the kit P/N and S/N]].
 
If you also wish to access git repositories containing source code, please follow the procedure described [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|here]].
 
===Target setup and first boot===
This section describes how to quick start the AxelEVB board delivered along with XELK kit (see also the following image). The hardware setup is the same for AxelUltra and AxelLite SOMs.
 
The picture below shows the AxelLite SOM inserted into the AxelEVB: please note the first HW release of {{oldid|3287|AxelEVB-Lite}}
[[File:AxelLite-AxelEVB.jpg|thumb|center|600px|Axel Lite SOM / (first) AxelEVB setup]]
 
The picture below shows the AxelUltra SOM inserted into the AxelEVB: please note the new HW release of [[AxelEVB-Lite]]
[[File:AxelUltra-AxelEVB.jpg|thumb|center|600px|Axel Ultra SOM / (latest) AxelEVB setup]]
 
The microSD provided with the XELK can be used to boot the system, since it contains a bootable partition (<code>mmcblk0p1</code>) and a root file system partition (<code>mmcblk0p2</code>).
#Insert the MicroSD card provided with the development kit into the microSD slot
#Connect the 12V power supply to the JP2 socket on the DACU board
#(optional) To access the serial console:
#*Connect a serial cable, using a null-modem cable (https://en.wikipedia.org/wiki/Null_modem) ''not provided'', between
#** the J251 connector on the DACU board and PC COM port - for the latest AxelEVB-Lite HW version (see picture above)
#** the J28 connector on the AxelEVB-Lite and PC COM port - for the first AxelEVB-Lite HW version (see picture above)
#*Start your favorite terminal software on hist side; communication parameters are:
#**Baud rate: 115200 Bps
#**Data bits: 8
#**Stop bits: 1
#**Parity: none
#(optional) To connect the system to Ethernet LAN, please plug cable on connector J6 connector of the AXELEVB-Lite
 
By default, the system is configured to boot automatically from the microSD card when powered up.
 
===Binary images on SD card===
 
{{ImportantMessage|text=The XELK bootable microSD card delivered along with the kit is set up to do a full bootstrap sequence. For more details, please refer to [[Working_with_the_Yocto_build_system#bootscript|this section]].}}
 
Once you got the new binaries compiled from your modified sources, they have to be installed on first SD partition preserving the original file names used into <i>boot.scr</i> u-boot bootscript.
 
Otherwise, you may create a new '''boot.scr''' file using different file names. Here below there is an example on how to create a boot.scr file for booting from SD card:
 
The '''bootscript.txt''' is the text version of the <i>boot.scr</i> file:
 
<pre>
echo 'bootscript generated with command "mkimage -A ARM -T script -C none -n XELK -d bootscript.txt boot.scr"'
 
setenv fdtfile imx6q-xelk-l.dtb
setenv bootfile uImage
 
setenv mmc_loadk 'fatload mmc ${mmcdev}:1 ${loadaddr} ${bootfile}'
setenv mmc_loadfdt 'fatload mmc ${mmcdev}:1 ${fdtaddr} ${fdtfile}'
setenv mmcboot 'run mmc_loadk mmc_loadfdt mmcargs addip addcons addmisc adddisp0; bootm ${loadaddr} - ${fdtaddr}'
 
echo Booting AxelLite-XELK via mmcboot
 
run mmcboot
 
echo mmcboot FAILURE
</pre>
 
and compile it using:
 
<pre>
mkimage -A ARM -T script -C none -n XELK -d bootscript.txt boot.scr
</pre>
 
Then copy the kernel, dtb and boot.scr into the SD card first partion (the FAT one) and boot XELK with the new images.
 
===Host setup===
As stated previously, XELK host tools are based on a [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine]]. As indicated [[Axel_Embedded_Linux_Kit_(XELK)#XELK_microSD_Layout|here]], microSD card delivered along with XELK includes basic version of MVM that is the default option.
 
Please follows the README file on the SD card to extract the ''*.ova'' archive and to install the MVM.
 
It is also worth remembering that access to git repositories is required to download target source code. To enable it, please refer to [[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|this page]].
 
{{ImportantMessage|text=The MVM provides the tools required to build [[Building_U-Boot_(XELK)|U-boot]] and [[Building_Linux_kernel_(XELK)|Linux kernel]]. It does not include the tools required to run Yocto build system instead.}}
 
XELK MVM can be downloaded [https://cloud.dave.eu/ws-reserved-area-xelk/XELK-3.0.1 here]. For accessing <b><i>XELK Reserved area</i></b> please contact our [mailto:sales@dave.eu sales department]
 
===Target configuration for the development stage (<code>net_nfs</code>)===
 
{{ImportantMessage|text=The default XELK Virtual Machine network configuration is using NAT: this allows to accessing external network (i.e. Internet) using the host computer's networking connection.
For software development using <code>net_nfs</code> with tftp/nfs protocols, please configure your VM network interface in ''Bridge mode'' (see below)}}
 
During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:
*retrieve binary images (i.e. Linux kernel) via TFTP protocol
*mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted [[Deploying_Embedded_Linux_Systems#The_development_environment|here]]. An example of ''Bridge mode'' configuration for DIVELK can be found [[Booting_from_NFS_(XELK) | here]]
In DAVE Embedded Systems development kits, this configuration is generally denoted as <code>net_nfs</code>. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up. They are detailed [[Booting_Linux_Kernel#Configuration_net_nfs|here]].
 
For more details about TFTP and NFS servers on host side, please refer to this [[Setting_up_tftp_and_nfs|page]].
 
===Target configuration for standalone boot===
Please refer to [[Standalone_boot_(XELK)|this page]].
==Related Documents ==
8,186
edits