For more information about the access to these repositories, please refer to [[Building_the_Yocto_BSP_(XELK)|this link]].
This means that these components can be kept in sync and up Access to date with '''DAVE Embedded Systems''' git repositories.==== RSA key generation ====Please follow the procedure reported below is granted to generate the RSA ssh key:* select your username (ad es. username@myhost.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> (development kit'''private key''') and <code>~/.ssh/username@myhosts owners only.com.pub</code> ('''public key''')* edit your <code>~/.ssh/config</code> adding the following lines:<pre>Host git.dave.eu User git Hostname git.dave.eu PreferredAuthentications publickey IdentityFile ~/.ssh/username@myhost.com</pre> Please send the public key file refer to one of the following email support addresses (depending on which SOM is included in your kit version)* [mailto:support-axel@dave.eu support-axel@dave.eu[Accessing_DAVE_Embedded_Systems_restricted_git_repositories|this page]] with the request for the creation of a new public git account associated detailed instructions on how to your username. The support team will enable the account and send you a confirmation as soon as possibleget access.
==== Synchronizing the repository ====
When The components listed in the account is enabled, you table above can synchronize a source tree entering the repository directory be kept in sync and launching the <code>git fetch</code> command, like in the following example:<pre class="workstation-terminal">dvdk@dvdk-vm:~$ 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> doesnup to date with DAVE Embedded Systems't merge the commits on the current branchrepositories. To do that, you should run
Once the git account has been enabled, the developer can:*clone the repository with the <code>git clone <git_remote_repository><pre class="workstation-terminal"/code>command *synchronize a source tree entering the repository directory and launching the <code>git merge fetch origin/axel</precode>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/documentation Git Documentation].
== Release types ==
{{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.01.1 === Release notes: * Added kernel support for AxelLite SOM with iMX6Q @1.2GHz and NOR SPI ISSI model === XELK 4.1.0 ===
* Release datenotes: N.A.* Status: Working In Progress* NXP Linux BSP: L4.9.11-1.0.0* Supported carrier boards: AxelEVB-Lite on Dacu, SBCX
{{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 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.1 === {{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 <b>SPL</b> version (first and second stage).}}
* Release datenotes: 17/11/2017* Status: released* NXP Linux BSP: L4.1.15-2.0.0* Supported carrier boards: AxelEVB-Lite on Dacu, SBCX
* Major change to u-boot SPL version* Updated u-boot 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)
* 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== 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.[[File:AxelUltra-AxelEVB.jpg|thumb|center|600px|Axel Ultra/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 12Vcc power supply to JP2 on the DACU board#(optional) Connect a serial cable between the J251 connector on the DACU board and PC COM port through a NULL-modem (https://en.wikipedia.org/wiki/Null_modem) cable (not provided)#(optional) start your favorite terminal software on PC; communication parameters are:#(optional) to connect the system to Ethernet LAN, please plug cable on connector J6 connector of the AXELEVB-LiteThe system is configured to boot automatically from the SD card when powered up.<pre class="mw-collapsible mw-collapsed"></pre>==== 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"'
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]].