AXEL ULite and SBC Lynx Embedded Linux Kit (XUELK)

Info Box Applies to SBC Lynx

Introduction

caption

SBC Lynx Embedded Linux Kit (XUELK for short) provides all the necessary components required to set up the developing environment to:

• build the bootloader (U-Boot)
• build and run Linux operating system on SBC Lynx board
• build Linux applications that will run on the target.

The main kit components are:

• hardware platform composed of
  • TBD
• Development Managed Virtual Machine containing:
  • Toolchain
  • U-Boot bootloader sources
  • Linux kernel sources
  • Root file systems
• Technical documentation such hardware manuals, mechanical drawings, reference schematics, application notes etc.

The documents related to the software issues help the user to quickly start configuring the bootloader and the operating system, by hiding most of the complexity of the underlying hardware. For more details about SBC Lynx hardware characteristics, please refer to the SBC Lynx Hardware Manual. An account for the reserved area of DAVE Embedded Systems website is required to access the kit contents.

Kit Contents

Component	Description	Notes
	SBC Lynx CPU: Freescale i.MX6 SDRAM: 512 GB DDR3 NOR: bootable SPI flash 32 MB NAND: 1GB	Please refer to Axel Ultra Hardware Manual
	AC/DC Single Output Wall Mount adapter Output: +12V – 2.0 A
	FTDI TTL/USB cable
	MicroSDHC card with SD adapter and USB adapter

XUELK software components

SBC Lynx Embedded Linux Kit is largely derived from the Yocto distributions released by NXP for the i.MX6 product family. For this reason most of the documentation provided by NXP remains valid for the XUELK development kit.

The following table reports the XUELK releases information.

	XUELK version
Release number	1.0.0
Release type	Major
Status	Beta
Release date	March 2016
Release notes	Ver 1.0.0
PCB version	CS214515
ConfigIDs (core/interfaces)	TBD/TBD
MVM version	TBD
U-Boot version/release	TBD/TBD
Linux version/release	TBD/TBD
Drivers	TBD
Freescale BSP version	TBD
Build System	TBD

MVM specific information

For general structure of the MVM please refer to this link.

TBD

• TFTP server root directory: TBD
• target's development root file system path: TBD
• cross-tool chain path: TBD
• target-specific source code paths:
  • TBD

XUELK microSD Layout

TBD

The microSD provided with XUELK is used to store:

• A FAT32 partition (mmcblk0p1) containing:
  • Linux kernel and DTB binary images
  • XUELK documentation
  • XUELK DVDK virtual machine image
• XUELK root file system partition (mmcblk0p2, ext3)

XUELK Updates

TBD

It's recommended to use the latest available XUELK version. Please refer to Release notes for further information.

Updating git repositories

In XUELK, the following source trees are clones of DAVE Embedded Systems public git repositories:

Component	GIT Remote	XUELK Installation Directory
Linux	git@git.dave.eu:lynx/linux-2.6-imx.git	/home/dvdk/lynx/linux-2.6-imx
U-Boot	git@git.dave.eu:lynx/u-boot-imx.git	/home/dvdk/lynx/u-boot-imx
Yocto BSP	git@git.dave.eu:lynx/axel-bsp.git	/home/dvdk/lynx/lynx-bsp

This means that these components can be kept in sync and up to date with DAVE Embedded Systems repositories.

RSA key generation

Please follow the procedure reported below 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: cd ~/.ssh/
• launch the following command:
  

  ssh-keygen -t rsa -C "username@myhost.com" -f username@myhost.com

• this command creates the files ~/.ssh/username@myhost.com (private key) and ~/.ssh/username@myhost.com.pub (public key)
• edit your ~/.ssh/config adding the following lines:

Host git.dave.eu
    User git
    Hostname git.dave.eu
    PreferredAuthentications publickey
    IdentityFile ~/.ssh/username@myhost.com

Please send the public key file to one of the following email support addresses (depending on which SOM is included in your kit version)

• support-axel@dave.eu

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

Synchronizing the repository

When the account is enabled, you can synchronize a source tree entering the repository directory and launching the git fetch command, like in the following example:

dvdk@dvdk-vm:~$ cd /home/dvdk/xelk/linux-2.6-imx/
dvdk@dvdk-vm:/home/dvdk/xelk/linux-2.6-imx$ git fetch origin

Please note that git fetch doesn't merge the commits on the current branch. To do that, you should run

git merge origin/axel

or replace the fetch-merge process with a single git pull command. Please note that the recommended method is the fetch-merge process. For further information on Git, please refer to Git Documentation.

Release notes

After the XUELK DVDK installation, please check for updates of the source tree repositories provided with the kit, as described in XUELK Updates.

XUELK 1.0.0

Notes

TBD

Known limitations

TBD

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

Issue	Description

Quick start guide

This chapter describes how to quickly start working with the XUELK kit. The following paragraphs will guide you through the setup and installation procedures.

Unboxing

TBD

Host setup

Please install and configure XUELK MVM as described here.

Target setup

This section describes how to quick start an SBC Lynx board.

• connect a TTL/USB serial cable to J42 connector; J42 pinout is:
  • 1: TX data
  • 2: RX data
  • 3: 3.3V
  • 4: GND
• on host side start your favorite terminal that will be used to interact with the target's serial console; communication parameters are 115200-8-N-1
• connect the system to Ethernet LAN by plugging cable into connector J16
• connect 12V power supply to J35 connector; J35 pinout is:
  • 1: GND
  • 2: VIN.

First boot

Once power has been applied to the target, U-Boot bootloader will be executed from the SPI NOR flash. Boot messages will be printed out on the serial console. U-Boot automatically runs the autoboot macro, that loads the kernel and launches it with the options for mounting the root fi le system from the mmcblk0p2 partition. At the end of the boot process, a demo application is launched and you can interact with the system using the touchscreen. Moreover, the Linux shell is available on the serial console. Lastly, both telnet and ssh services are available to connect to the system through the network. Please refer to Appendix 6.3 for an example of the boot messages.

Advanced topics

Debugging with Eclipse

Please refer to this page.

Related Documents

TBD