Changes

← Older edit

Axel Embedded Linux Kit (XELK)

26,151 bytes added, 16:18, 31 August 2022

no edit summary

==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]]

!Notes

|-

|style="text-align: center;" | [[File:Axel-01.png|60px]]|Axel Ultra SOM CPU: Freescale i.MX6 SDRAM: 2 GB DDR3 NOR: bootable SPI flash 32 MB NAND: 1GB

|Please refer to [[Hardware Manual (AxelUltra) | Axel Ultra Hardware Manual]]

|-

|AxelEVB-Lite Carrier board

|Please refer to [[AxelEVB-Lite | AxelEVB-Lite]] page

|-

|style="text-align: center;" | [[File:Dacu-top-view.png|80px]]

|Dacu Carrier board

|Please refer to [[Dacu | Dacu]] page

|-

|style="text-align: center;" | [[File:Display.jpg|60px]]

|Ampire AM-800480STMQW 7” 800x480 LCD display LVDS interface

|Please refer to [[XELK Quick Start Guide]]

|-

|style="text-align: center;" | [[File:Alimentatore.jpg|40px]]

|AC/DC Single Output Wall Mount adapter Output: +12V – 2.0 A

|Please refer to [[XELK Quick Start Guide]]

|-

|style="text-align: center;" | [[File:Cavetto-seriale2.jpg|50px]]

|DB9 Male Serial port adapter

|Please refer to [[XELK Quick Start Guide]]

|-

|style="text-align: center;" | [[File:ProdSDC-MBLY-thumb.png|50px]]

|MicroSDHC card with SD adapter and USB adapter

|Please refer to [[XELK Quick Start Guide]]

== XELK software components ==

'''DAVE Embedded Systems''' adds to the latest Linux BSP from NXP/Freescale the customization required to support the Axel platform. For this reason most of the documentation provided by NXP/Freescale remains valid for the XELK development kit. However, some customization is required, in particular at bootloader and linux kernel levels.

The following table reports the XELK releases information.

{| class="wikitable"

!

!colspan="311" | XELK version

|-

|Release number

|1.0.0

|1.1.0

|1.2.0

|2.0.0

|2.1.0

|2.2.0

|2.3.1

|3.0.1

|3.5.0

|4.0.0

|4.1.1

|-

|Release type

|Major

|Maintenance

|Major

|Maintenance

|Major

|Maintenance

|Major

|Maintenance

|-

|Status

|Released

|-

|Release date

|November, 4th 2013

|January 2014

|-

|'''Release notes'''

|[[~~Axel_Embedded_Linux_Kit_(~~#XELK 1.0.0 | Ver 1.0.0]]|[[#XELK 1.1.0 | Ver 1.1.0]]|[[#XELK 1.2.0 | Ver 1.2.0]]|[[#XELK)2.0.0 | Ver 2.0.0]]|[[#XELK 2.1.0| Ver 2.1.0]]|[[#XELK 2.2.0 | Ver 2.2.0 ]]|[[#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

|--

|Supported carrier boards

|[{{fullurl:AxelEVB-Lite|oldid=2970}} AxelEVB-Lite] [[:Category:Dacu | Dacu]]|{{pageoldid|AxelEVB-Lite|2970}} [[:Category:Dacu | Dacu]]|{{pageoldid|AxelEVB-Lite|2970}} [[:Category:Dacu | Dacu]]|{{pageoldid|AxelEVB-Lite|2970}} [[:Category:Dacu | Dacu]]|{{pageoldid|AxelEVB-Lite|2970}} [[AxelEVB-Lite|AxelEVB-Lite rev.A]] [[:Category:Dacu | Dacu]]|{{pageoldid|AxelEVB-Lite|2970}} [[AxelEVB-Lite|AxelEVB-Lite rev.A]] [[:Category:Dacu | Dacu]] [[:Category:SBC-AXEL | SBCX]]|{{pageoldid|AxelEVB-Lite|2970}} [[AxelEVB-Lite|AxelEVB-Lite rev.A]] [[:Category:Dacu | Dacu]] [[:Category:SBC-AXEL | SBCX]]|{{pageoldid|AxelEVB-Lite|2970}} [[AxelEVB-Lite|AxelEVB-Lite rev.A]] [[:Category:Dacu | Dacu]] [[:Category:SBC-AXEL | SBCX]]|{{pageoldid|AxelEVB-Lite|2970}} [[AxelEVB-Lite|AxelEVB-Literev.A]] [[:Category:Dacu | Dacu]] [[:Category:SBC-AXEL | SBCX]]|{{pageoldid|AxelEVB-Lite|2970}} [[AxelEVB-Lite|AxelEVB-Lite rev.A]] [[:Category:Dacu | Dacu]] [[:Category:SBC-AXEL | SBCX]]|{{pageoldid|AxelEVB-Lite|2970}} [[AxelEVB-Lite|AxelEVB-Lite rev.A]] [[:Category:Dacu | Dacu]] [[: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.10-xelk-1.0.0

|-

|Linux version

|3.0.35-xelk-1.0.0

|Drivers

|valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA ~~HMDI~~HDMI ~~LVDS1~~LVDS0|valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA ~~HMDI~~HDMI ~~LVDS1~~LVDS0 NAND RTC I2C SPI|valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA ~~HMDI~~HDMI ~~LVDS1~~LVDS0 NAND RTC I2C SPI| valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA HDMI LVDS0 NAND RTC I2C SPI Video Input (MIPI)| valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA HDMI LVDS0 NAND RTC I2C SPI Video Input (MIPI) PCIe [[ConfigID_and_UniqueID | ConfigID]]| valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA HDMI LVDS0 NAND RTC I2C SPI Video Input (MIPI) PCIe [[ConfigID_and_UniqueID | ConfigID]] Splash screen (U-Boot) [1]| valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA HDMI LVDS0 NAND RTC I2C SPI Video Input (~~CSI~~MIPI) ~~Audio~~PCIe [[ConfigID_and_UniqueID | ConfigID]] Splash screen (U-Boot) [1]| valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA HDMI LVDS0 NAND RTC I2C SPI Video Input (MIPI) PCIe [[ConfigID_and_UniqueID | ConfigID]] Splash screen (U-Boot) [1]| valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA HDMI LVDS0 NAND RTC I2C SPI Video Input (MIPI) PCIe [[ConfigID_and_UniqueID | ConfigID]] Splash screen (U-Boot) [1] SPL boot[2]| valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA HDMI LVDS0 NAND RTC I2C SPI Video Input (MIPI) PCIe [[ConfigID_and_UniqueID | ConfigID]] Splash screen (U-Boot) [1] SPL boot[2]| valign="top" | SPI NOR Flash (boot) UART debug (2-wire) USB Host USB OTG SD/MMC1 CAN Touch screen controller EMAC SATA HDMI LVDS0 NAND RTC I2C SPI Video Input (MIPI) PCIe [[ConfigID_and_UniqueID | ConfigID]] Splash screen (U-Boot) [1] SPL boot[2]

|-

|NXP/Freescale BSP version|L3.0.35-4.1.0

|L3.0.35-4.1.0

| L3.0.35-4.1.0 | L3.10.17- 1.0.0|L3.10.17-1.0.0|L3.10.17-1.0.3|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 4.8|Qt 4.8|Qt 4.8|Qt 5.3.2|Qt 5.3.2|Qt 5.3.2|Qt 5.3.2|Qt 5.6.2|Qt 5.6.2|Qt 5.9.8|Qt 5.9.8|-|Build System|LTIB|LTIB|LTIB|Yocto Dora (1.5) |Yocto Dora (1.5) |Yocto Dora (1.5) |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==== All binary images for XELK are hosted on [[mirror:axel|DAVE Embedded System mirror server]]. There you can find a sub directory for each version of this development kit. A summary of images with a brief description can be found into the table below: {{ImportantMessage|text=In order to boot Linux from SD card files, '''the binary files must be renamed''' as follows:*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"|-! Image !! colspan="5" |XELK version 2.3.1|-| Platform || XELK rev.A || SBCX rev.A || SBCX rev.A || SBCX rev.B || SBCX rev.B|-| Carrier Board [[ConfigID_and_UniqueID | ConfigID]]|| 0001 || 0002 || 0003 || 0012 || 0013|-| LCD panel || colspan="5" style="text-align: center" | Ampire 800 x 480 7" LVDS 262K colors (RGB666) (AM-800480STMQW-TA1 or AM-800480SETMQW-TA1H)|-| Touchscreen || colspan="1" | resistive || colspan="1" | resistive || colspan="1" | capacitive || colspan="1" | resistive || colspan="1" style="text-align: center" | capacitive|-| bootscript || colspan="1" style="text-align: center" |[[mirror:axel/xelk-2.3.1/xelk-2.3.1_boot.scr|boot.scr]] || colspan="4" style="text-align: center" |[[mirror:axel/xelk-2.3.1/xelk-2.3.1_sbcx_boot.scr|boot.scr]]|-| U-Boot || colspan="1" style="text-align: center" |[[mirror:axel/xelk-2.3.1/xelk-2.3.1_mx6qaxel_spi_u-boot.imx|u-boot (Quad - boot from NOR)]] || colspan="4" style="text-align: center" |[[mirror:axel/xelk-2.3.1/xelk-2.3.1_mx6dlaxel_nand_u-boot.imx|u-boot (DualLite - boot from NAND)]] |-| Linux kernel || colspan="5" style="text-align: center" |[[mirror:axel/xelk-2.3.1/xelk-2.3.1_uImage|uImage]]|-| Linux kernel (Android 4.4.2) || colspan="5" style="text-align: center" |[[mirror:axel/xelk-2.3.1/xelk-2.3.0-andr_uImage|uImage]]|-| Device tree (Quad processor) || [[mirror:axel/xelk-2.3.1/xelk-2.3.1_imx6q-xelk-l.dtb|imx6q-xelk-l.dtb]] || [[mirror:axel/xelk-2.3.1/xelk-2.3.1_imx6q-sbcx.dtb|imx6q-sbcx-cb0002.dtb]] || Not available || [[mirror:axel/xelk-2.3.1/xelk-2.3.1_imx6q-sbcx-cb0012.dtb|imx6q-sbcx-cb0012.dtb]] || Not available|-| Device tree (DualLite processor) || [[mirror:axel/xelk-2.3.1/xelk-2.3.1_imx6dl-xelk-l.dtb|imx6dl-xelk-l.dtb]] || [[mirror:axel/xelk-2.3.1/xelk-2.3.1_imx6dl-sbcx.dtb|imx6dl-sbcx-cb0002.dtb]] || [[mirror:axel/xelk-2.3.1/xelk-2.3.1_imx6dl-sbcx-cb0003.dtb|imx6dl-sbcx-cb0003.dtb]] || [[mirror:axel/xelk-2.3.1/xelk-2.3.1_imx6dl-sbcx-cb0012.dtb|imx6dl-sbcx-cb0012.dtb]] || [[mirror:axel/xelk-2.3.1/xelk-2.3.1_imx6dl-sbcx-cb0013.dtb|imx6dl-sbcx-cb0013.dtb]]|}{| class="wikitable"|-! Image !! colspan="5" |XELK version 3.0.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) (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-3.0.1/xelk-3.0.1_boot.scr|boot.scr]] || colspan="4" style="text-align: center" |[[mirror:axel/xelk-3.0.1/xelk-3.0.1_boot.scr|boot.scr]]|-| U-Boot || colspan="1" style="text-align: center" |[[mirror:axel/xelk-3.0.1/xelk-3.0.2_mx6qaxel_spi_u-boot.imx|u-boot (Quad - boot from NOR)]] || colspan="4" style="text-align: center" |[[mirror:axel/xelk-3.0.1/xelk-3.0.2_mx6dlaxel_nand_u-boot.imx|u-boot (DualLite - boot from NAND)]] |-| Linux kernel || colspan="5" style="text-align: center" |[[mirror:axel/xelk-3.0.1/xelk-3.0.0_uImage|uImage]]|-| Device tree (Quad processor) || [[mirror:axel/xelk-3.0.1/xelk-3.0.0_imx6q-xelk-l.dtb|imx6q-xelk-l.dtb]] || [[mirror:axel/xelk-3.0.1/xelk-3.0.0_imx6q-sbcx-cb0012.dtb|imx6q-sbcx-cb0012.dtb]] || [[mirror:axel/xelk-3.0.1/xelk-3.0.0_imx6q-sbcx-cb0013.dtb|imx6q-sbcx-cb0013.dtb]]|-| 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) (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]]

|}

* XELK root file system partition (mmcblk0p2, ext3)

XELK contains all the required software and documentation to start developing Linux application on the Axel platform. In particular, XELK provides a virtual machine, called DVDK, with the following features:

~~XELK contains all the required software and documentation to start developing Linux application~~ * VirtualBox virtual machine (.OVA archive)* Based on ~~the Axel platform~~Lubuntu 14. ~~In particular, XELK provides a Virtualbox virtual machine with two emulated disks:~~04 LTS (64-bit version)* Pre-installed VirtualBox Guest Additions* LXDE desktop environment* Boot disk with ~~pre-installed Ubuntu Linux 12.04.2 LTS~~ 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 ** Linux kernel source tree cloned from ~~'''~~DAVE Embedded Systems~~'''~~ public git repository** ~~Toolchain~~External pre-built toolchain** ~~Root file systems:~~Yocto bsp for AXEL*** '''LTIB''' Pre-installed Yocto- based root file ~~system provided by Freescale~~ systems with ~~the BSP and built with LTIB~~ setup scripts, makefiles, example applications, ...* Administrator account (~~/home/~~dvdk~~/xelk/rfs/ltib~~)with autologin. ~~This is~~ Please note that the ~~default root file system~~*** '''Yocto''' - root file system built user account credentials are provided with the ~~Yocto build system~~ development kit (~~/home~~you can find them into the README file contained in the sw/dvdk~~/xelk/rfs/yocto). Since Yocto is not officially supported by Freescale, this is a preliminary version, included in the XELK 1.0.0 release as a preview~~ folder of the ~~future advancements.~~kit distribution)

Please note that XELK u-boot and kernel source trees are derived from the official trees released by NXP/Freescale; these trees have been customized to add support for the Axel SOM.

=== XELK Updates ===

==== Updating git repositories ====

In XELK, the following source trees are clones of the correspondent '''DAVE Embedded Systems''' git repositories:

{| class="wikitable"

|-

!| Component

!GIT Remote

|-

|U-Boot

|<code>git@git.dave.eu:dave/axel/u-boot-imx.git</code>

|-

|Linux kernel

|<code>git@git.dave.eu:dave/axel/linux-2.6-imx.git</code>

|-

|Yocto BSP

|<code>git@git.dave.eu:dave/axel/axel-bsp.git</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 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 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]].

== Release notes ==

{{ImportantMessage|text=After the XELK DVDK installation, please check for updates of the source tree repositories provided with the kit, as described in [[Axel_Embedded_Linux_Kit_(XELK)#XELK_Updates | XELK Updates]].}}

=== XELK 4.1.1 ===

Release notes:

* Added kernel support for AxelLite SOM with iMX6Q @1.2GHz and NOR SPI ISSI model

=== XELK 4.1.0 ===

Release notes:

* Updated Yocto targets recipes: added X11, browser, Qt5 Wayland root file system images

=== XELK 4.0.0 ===

{{ImportantMessage|text=New MVM must be installed for using XELK-4.0.0. The VM is available for download on DAVE's XELK Reserved Area for registered users.}}

Release notes:

* Major change to NXP BSP 4.9.11

* Updated u-boot and kernel versions

* Updated Yocto version

* Updated Qt version

==== Known Limitations ====

The following table reports the known limitations of this XELK release:

{| 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 not yet supported

|-

|}

=== XELK 3.5.0 ===

{{ImportantMessage|text=NXP iMX6 silicon revision 1.4 limited the u-boot binary size (due to bug fix in bootrom code). This required the switch to u-boot SPL version (first and second stage).}}

Release notes:

* Major change to u-boot SPL version

* Updated u-boot version

=== 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 u-boot and kernel versions

* Updated Yocto version

* Updated Qt version

=== XELK older releases ===

For XELK older ''unsupported'' releases information, please click on Expand here below (on the right)

==== 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

* Added support for other ConfigID on linux with related device-tree source code and binaries

* Bug fixes and minor changes

==== XELK 2.2.0 ====

~~In XELK,~~ {{ImportantMessage|text=It's highly recommended to read the [[ConfigID and UniqueID]] page.}} * Added splash screen support in U-Boot* Added support for SBCX carrier board* Updated u-boot and kernel versions* Bug fixes and minor changes ===== Known Limitations ===== The following ~~source trees are clones~~ table reports the known limitations of ~~'''DAVE Embedded Systems''' public git repositories~~this XELK release:

{| class="wikitable"

|-

!Issue!Description| ~~Component~~-~~!GIT Remote~~|USB OTG~~!XELK Installation Directory~~|Verified in Host and Device modes

|-

|~~Linux~~Reboot from software (not on SBC AXEL)|~~git@git.dave.eu~~Rebooting the system from software (eg:~~dave/axel/linux-2~~launching the reboot command from Linux user space) can lead to a system lock.~~6-imx~~To solve it, reset the board with the dedicated button (S10).~~git|/home/dvdk/xelk/linux-2~~SBC AXEL is not affected by this issue.~~6-imx~~

|-

|~~U-Boot~~Ethernet|~~git@git.dave.eu:dave/axel/u-boot-imx.git|/home/dvdk/xelk/u-boot-imx~~10 Mbps connections have not been tested

|-

|}

~~This means that these components can be kept in sync~~ ==== XELK 2.1.0 ==== {{ImportantMessage|text=It's highly recommended to read the [[ConfigID and ~~up to date with '''DAVE Embedded Systems''' repositories~~UniqueID]] page.}} * Updated u-boot and kernel versions* Bug fixes and minor changes ===== Known Limitations =====

~~==== RSA key generation ====~~The following table reports the known limitations of this XELK release:

~~Please follow~~ {| class="wikitable" |-!Issue!Description|-|USB OTG|Verified in Host and Device modes|-|Reboot from software|Rebooting the ~~procedure reported below~~ system from software (eg: launching the reboot command from Linux user space) can lead to ~~generate~~ a system lock. To solve it, reset the board with the ~~RSA ssh key:~~dedicated button (S10)|-|Ethernet|10 Mbps connections have not been tested|-|} ==== XELK 2.0.0 ====

* ~~select your username (ad es~~Added support for Yocto 1. ~~username@myhost.com)~~5* ~~start the DVDK~~ Updated u-boot 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: <pre>ssh-keygen -t rsa -C "username@myhost.com"</pre>kernel versions* ~~this command creates the files <code>~/.ssh/username@myhost.com</code> ('''private key''')~~ Bug fixes and ~~<code>~/.ssh/username@myhost.com.pub</code> ('''public key''')~~* edit your <code>~/.ssh/config</code> adding the following lines:minor changes

~~<pre>Host git.dave.eu~~ ~~User git~~ ~~Hostname git.dave.eu~~ ~~PreferredAuthentications publickey~~ ~~IdentityFile ~/.ssh/username@myhost.com.pub</pre>~~===== Known Limitations =====

~~Please send~~ The following table reports the ~~public key file to one~~ known limitations of ~~the following email support addresses (depending on which SOM is included in your kit version)~~this XELK release:

* [mailto{| class="wikitable" |-!Issue!Description|-| ETH0 interface| On AxelEVB-Lite, there is a mistake in the connection of the center tap pins. They should be separated from one another and connected through separate 0.1μF common-mode capacitors to ground (for further details (eg:~~support~~connection and selection of the magnetics), please refer to the Micrel KSZ9031RNX datasheet).|-~~axel@dave~~|USB OTG|Verified in Host and Device modes|-|Reboot from software|Rebooting the system from software (eg: launching the reboot command from Linux user space) can lead to a system lock.~~eu support~~To solve it, reset the board with the dedicated button (S10)|-~~axel@dave.eu]~~|Ethernet|10 Mbps connections have not been tested|-|}

~~with the request for the creation of a new public git account associated to your username~~==== XELK 1. ~~The support team will enable the account and send you a confirmation as soon as possible~~2.0 ====

~~==== Synchronizing the repository ====~~* Added support for Axel Lite SOM* Bug fixes and minor changes

~~When the account is enabled, you can synchronize a source tree entering the repository directory and launching the <code>git fetch</code> command, like in the following example:~~===== Known Limitations =====

~~<pre class="workstation-terminal">dvdk@dvdk-vm~~The following table reports the known limitations of this XELK release:~~~$ cd /home/dvdk/xelk/linux-2.6-imx/dvdk@dvdk-vm:/home/dvdk/xelk/linux-2.6-imx$ git fetch origin</pre>~~

~~Please note that <code>git fetch</code> doesn't merge~~ {| class="wikitable" |-!Issue!Description|-|USB OTG|Verified in Host and Device modes|-|SD1|SD1 interface (available on the Axel Lite adapter board as microSD connector) detects the card only if it is inserted before booting Linux|-|Reboot from software|Rebooting the ~~commits on~~ system from software (eg: launching the ~~current branch~~reboot command from Linux user space) can lead to a system lock. To ~~do that~~solve it, ~~you should run~~ reset the board with the dedicated button (S10)|-|Ethernet|10 Mbps connections have not been tested|-|}

~~<pre class~~=~~"workstation-terminal">git merge origin/axel</pre>~~=== XELK 1.1.0 ====

~~or replace the ''fetch-merge'' process with a single <code>git pull</code> command. Please note~~ * Minor update that ~~the recommended method is the ''fetch-merge'' process. For further information on Git~~adds support for more peripherals: nand, rtc, i2c, ~~please refer to [http://git-scm.com/documentation Git Documentation].~~spi* Touch screen works properly* CAN works @ 1Mbps* The system can boot from SD

== ~~Release notes~~ === Known Limitations =====

~~===~~ The following table reports the known limitations of this XELK ~~1.0.0 ===~~release:

* Release date: November{| class="wikitable" |-!Issue!Description|-|Boot modes|This kit version supports boot from USB (for recovery purpose), from SPI nor flash and from SD card. Boot from NAND flash will be available on a future release.|-|CPU cores|Max 2 cores. 3rd and 4th ~~2013~~cores will be available on a future release.* Status|-|USB OTG|Verified in Host and Device modes|-|Reboot from software|Rebooting the system from software (eg: ~~released~~* Freescale launching the reboot command from Linux ~~BSP: L3~~user space) can lead to a system lock.~~0.35~~To solve it, reset the board with the dedicated button (S10)|-4.|Ethernet|Verified speeds: 1.0Gbps and 100 Mbps* Supported carrier boards: AxelEVB|-~~Lite on Dacu~~|}

==== ~~Notes~~ XELK 1.0.0 ====

* 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 boot.scr 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 boot.scr 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 XELK Reserved area 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 ==

* [[~~Axel_Ultra_SOM~~ :Category:AxelUltra|AXEL ULTRA]]* [[:Category:AxelLite|AXEL LITE]]* [[AxelEVB-Lite | AxelEVB-Lite]]* [[FAQs_(Axel) | Axel ~~Ultra SOM~~FAQs]]

* [[Hardware Manual (AxelUltra) | Axel Ultra Hardware Manual]]

* [[~~XELK Quick Start Guide]]~~* [[AxelEVB-Lite Hardware Manual (AxelLite) | ~~AxelEVB-~~Axel LiteHardware Manual]]

* [[:Category:Dacu | Dacu category page]]

* [[Dacu | Dacu carrier board]]

* [[Dacu_for_the_Axel_SOM | Dacu for the Axel SOM]]

[[Category:SBC-AXEL]]

U0007

Bureaucrats, dave_user, Administrators

8,220

edits

DAVE Developer's Wiki β

Changes

Axel Embedded Linux Kit (XELK)

DAVE Developer's Wiki ^β