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}}
* 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
|Linux
|git@git.dave.eu:dave/axel/linux-2.6-imx.git
|/home/dvdk/xelkaxel/linux-2.6-imx
|-
|U-Boot
|git@git.dave.eu:dave/axel/u-boot-imx.git
|/home/dvdk/xelkaxel/u-boot-imx
|-
|Yocto BSP
|git@git.dave.eu:dave/axel/axel-bsp.git
|/home/dvdk/xelkaxel/axel-bsp
|-
|}
<pre class="workstation-terminal">
dvdk@dvdk-vm:~$ cd /home/dvdk/xelkaxel/linux-2.6-imx/dvdk@dvdk-vm:/home/dvdk/xelkaxel/linux-2.6-imx$ git fetch origin
</pre>
=== XELK 4.0.0 ===
* Release date: N.A.08/2019* Status: Working In ProgressReleased
* NXP Linux BSP: L4.9.11-1.0.0
* Supported carrier boards: AxelEVB-Lite on Dacu, SBCX
* 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
|-
|}
=== XELK 3.5.0 ===
* Release date: 04/2019
* Status: Released
* NXP Linux BSP: L4.1.15-2.0.0
* Supported carrier boards: AxelEVB-Lite on Dacu, SBCX
==== Notes ====
{{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).}}
* Major change to u-boot SPL version
* Updated u-boot version
=== XELK 3.0.1 ===
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]].