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 [[:Category:SBC Lynx|SBC Lynx board]]
* build and debug applications that will be executed on top of Yocto-based Linux distribution running on the target.
The main kit components are:
* hardware platform composed (SBC Lynx)
* development host released in the form of [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine]], tailored for [[Managed_Virtual_Machine_(MVM)#Yocto-based_Linux_distribution|Yocto-based distribution]]
* 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. '''Reading of the [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine documentation]] is strongly recommended''', as it plays a '''major role''' in the XUELK organization. For more details about SBC Lynx hardware characteristics, please refer to the [[Hardware_Manual_(SBC_Lynx)|SBC Lynx Hardware Manual]]. An account for the reserved area of [http://www.dave.eu '''DAVE Embedded Systems''' website] is required to access the kit contents.
SBC Lynx documentation is provided on [[:Category:SBC_Lynx|Wiki]] product pages. The most important documents are listed below:
* [[XUELK Quick Start Guide]]
* [[Hardware_Manual_(SBC_Lynx)|Hardware Manual]]
* [[Mechanicals_(SBC_Lynx)|Mechanicals]]
== XUELK software components ==
{{ImportantMessage|text=From the software perspective, XUELK supports SBC Lynx and [[:Category:AXEL_ULite|AXEL ULite SOM]]. However, physical contents of the kit include SBC Lynx only.
}}
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.
[2] Carrier Board 0x00000013 (SBC Lynx CS214515B) uses same dtb file as 0x0000000C
[3] Carrier Board 0x0000002D/2E/2F/30 have its own device tree file for different peripherals mapping
====Downloadable binary images====
All binary images for XUELK are hosted on [[mirror:lynx|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=For [[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#XUELK_software_components|XUELK releases]] 1.1.3 and older, in order to boot Linux from SD card files, '''the binary files must be renamed''' as follows:
*bootscript: <code>boot.scr</code>
*Linux kernel: <code>uImage</code>
*Device tree: <code>imx6ul-lynx.dtb</code>
The default U-Boot enviroment variables assume in fact that these names are used.}}
The microSD provided with XUELK Most of storage space is used to storeoccupied by two partitions:* A a <code>FAT32 </code> partition (<code>mmcblk0p1</code>) containing:** U-Boot <code>bootscript</code>** Linux kernel and DTB binary images** XUELK documentationvirtual machine image in OFV format ([[Managed_Virtual_Machine_(MVM)|MVM]] basic version)** XUELK DVDK virtual machine image7-zip Windows executable file* XUELK an <code>ext3</code> partition (<code>mmcblk0p2</code>) containing the root file system for the target. <code>bootscript</code> and root file system partition are used to boot the target as described in [[#Target_setup_and_first_boot|this section]]. It is worth remembering that the microSD card is [[Booting_options_(mmcblk0p2SBC_Lynx)|bootable]], because U-Boot image is stored at address 0x400. However, even if U-Boot is run from the microSD card, ext3'''the environment is retrieved from NOR flash'''.====How to create a bootable microSD card====Please refer to this [[How_to_create_a_bootable_microSD_card_(XUELK)|this page]].
=== XUELK updates ===
XUELK updating process consists of updating the [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine]] it is based on. The procedure is described [[Managed_Virtual_Machine_(MVM)#Updating_MVM|here]].
Please note that this process '''implicitly updates git source code repositoriesof U-Boot and/or Linux kernel'''. Thus '''it is strongly recommended to create new local branches if you need to modify source code'''. ==== Updating git repositories ==== In XUELK, the following source trees are clones of '''DAVE Embedded Systems''' public git repositories: {| class="wikitable" |-!| Component!GIT Remote!XUELK Installation Directory|-|Linux|git@git.dave.eu:lynx/linux-2.6-imx.git|/home/dvdk/lynx/linux|-|U-Boot|git@git.dave.eu:lynx/u-boot-imx.git|/home/dvdk/lynx/u-boot|-|Yocto BSP|git@git.dave.eu:lynx/lynx-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.
=== Release notes ===
{{ImportantMessage|text=After the === XUELK 2.0.1/2.0.2/2.0.3 ==== ===== Notes 2.0.3 ===== * Add support for ISSI SPI NOR flash ===== Notes 2.0.2 ===== * Update Yocto BSP to latest Krogoth to fix WPA2 key replay security bug (for more details see [http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=krogoth&id=54e3f82bd77203c3d578e26c86506e6ef5c27000]) ===== Notes 2.0.1 =====Major update on XUELK DVDK installation, please check 1.2.0:* BSP update to NXP 4.1.15-2.0.0_ga* Minor fixes for updates Wifi and BT ===== Known issues and limitations ===== The following table reports the known limitations of the source tree repositories provided with the kit, as described this XUELK release: {| class="wikitable" |-!Limitations!Description|-|USB OTG Current Limit|USB OTG current limit is set at 75mA in Host mode|-|Low Power Idle not supported|Low Power Idle is not supported in [[Axel_Embedded_Linux_Kit_(XUELK)#XUELK_Updates this release| } ==== XUELK Updates]]1.2.}}0 ====
==== = Notes ===== Minor update on XUELK 01.91.0 3:* add CPU temperature for thermal thresholds settings* add rf kill support for Bluetooth on device tree* add [[ConfigID and UniqueID|ConfigID]] support for different hardware configurations: SOM_ConfigID and CB_ConfigID* minor fixes and enhancement ===== Known issues and limitations ===== The following table reports the known limitations of this XUELK release: {| class="wikitable" |-!Issue!Description|-|USB OTG Current Limit|USB OTG current limit is set at 75mA in Host mode|-|Low Power Idle not supported|Low Power Idle is not supported in this release|-|Bridged network configuration without DHCP server|See [[VirtualBox_Network_Configuration#LXDE|this section]].|} ==== XUELK 1.1.3 ====
===== Notes =====
First beta Minor update on XUELK 1.1.0:* add some useful networking support (wireless WPA and bonding)* add configid support for new hardware revision* add support for Xenomai extension* fix XUELK-1.1.0 commercial microSD mount issue* fix XUELK-1.1.0 reboot when rfs is on SD/MMC* minor fixes and enhancement ===== Known issues and limitations ===== The following table reports the known limitations of this XUELK release: {| class="wikitable" |-!Issue!Description|-|USB OTG Current Limit|USB OTG current limit is set at 75mA in Host mode|-|Low Power Idle not supported|Low Power Idle is not supported in this release|} ==== XUELK 1.1.0 ==== ===== Notes =====
===== Known limitations =====Minor update on XUELK 1.0.0:* add some useful networking support (on both Linux and file system)* fix XUELK-1.0.0 shutdown issue* fix XUELK-1.0.0 MVM network-manager issues* minor fixes and enhancement
===== Known issues and limitations =====
The following table reports the known limitations of this XUELK release:
{| class="wikitable"
|Rebooting in Linux may hang
|Software reboot on Linux may hang (without rebooting the board) when root file system in on SD/MMC
|-
|USB OTG Current Limit
|USB OTG current limit is set at 75mA in Host mode
|-
|Low Power Idle not supported
|Low Power Idle is not supported in this release
|-
|Failing mount of root file system on microSD card
|Some commercial microSD cards occasionally prevent the target from mounting the root file system stored on themselves. microSD cards delivered along with XUELK do not exhibit this problem.
|-
|Missing firmware file for Bluetooth
|In case [[XUELK-AN-001:_Using_WiFi-Bluetooth_combo_plugin_with_SBC_Lynx|DWM wireless plugin]] is used, the following file need to be copied in <code>/lib/firmware/ti-connectivity/</code>:
*<code>TIInit_7.6.15.bts</code> (please click [https://github.com/TI-ECS/bt-firmware/blob/master/am335x/TIInit_7.6.15.bts here] to download it)
|}
==== XUELK 1.0.0 ====
===== Notes =====
First stable release with support for SBC Lynx revision A and Axel ULite
===== Known issues and limitations =====
The following table reports the known limitations of this XUELK release:
{| class="wikitable"
|-
!Issue
!Description
|-
|Rebooting in Linux may hang
|Software reboot on Linux may hang (without rebooting the board) when root file system in on SD/MMC
|-
|USB OTG Current Limit
|USB OTG current limit is set at 75mA in Host mode
|-
|Low Power Idle not supported
|Low Power Idle is not supported in this release
|-
|XUELK environment fixup for SD boot<br/>on SBC Lynx
|To boot with the XUELK SD card, user may need to execute the following commands at u-boot prompt<br/>
|Failing mount of root file system on microSD card
|Some commercial microSD cards occasionally prevent the target from mounting the root file system stored on themselves. microSD cards delivered along with XUELK do not exhibit this problem.
|-
|System shutdown mode using the <code>shutdown -h now</code> command prevent the subsequent system's power-up
|Issuing a system shutdown by the command <code>shutdown -h now</code> as described in [[Supported power mode transitions (SBC Lynx)]] will prevent the subsequent system's boot.
|-
|Missing 7-zip Windows executable in microSD card
|Please download it from http://www.7-zip.org.
|-
|In the MVM, <code>network-manager</code> applet is not installed by default.
| Please refer to [[VirtualBox_Network_Configuration#VBox_Bridged_configuration|this page]] to install it.
|-
|Missing firmware file for Bluetooth
|In case [[XUELK-AN-001:_Using_WiFi-Bluetooth_combo_plugin_with_SBC_Lynx|DWM wireless plugin]] is used, the following file need to be copied in <code>/lib/firmware/ti-connectivity/</code>:
*<code>TIInit_7.6.15.bts</code> (please click [https://github.com/TI-ECS/bt-firmware/blob/master/am335x/TIInit_7.6.15.bts here] to download it)
|}
==== XUELK 0.9.0 ====
===== Notes =====
First beta release.
===== Known issues and limitations =====
The following table reports the known limitations of this XUELK release:
{| class="wikitable"
|-
!Issue
!Description
|-
|Rebooting in Linux may hang
|Software reboot on Linux may hang (without rebooting the board) when root file system in on SD/MMC
|-
|USB OTG Current Limit
|USB OTG current limit is set at 75mA in Host mode
|-
|LDO Mode not supported
|LDO Mode is not supported in this SW release
|-
|Low Power Idle not supported
|Low Power Idle is not supported in this release
|-
|DDR3 Frequency limited at 306 MHz
|The DDR3 RAM frequency is limited at 306 MHz in this release
|-
|}
==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
===Kit registration===
{{ImportantMessage|text='''Customers are strongly recommended to register their kits'''. This allows them to get Registration grants access to additional information and upgrades that are available in the [http://www.dave.eu/reserved-area|restricted download area of DAVE Embedded Systems web site]. Please register your development kit by sending an email to [mailto:support-lynx@dave.eu support-lynx@dave.eu], providing the kit P/N material such as source code and CODE.===Host setup===As stated previously, XUELK is based on a [[Managed_Virtual_Machine_(MVM)|Managed Virtual Machine]]. To install it, please follow the procedure described [[Managed_Virtual_Machine_(MVM)#Installation_and_configuration|here]]additional documentation.
In case you chose To register the kit, please send an email to use the [mailto:support-lynx@dave.eu support-lynx@lynx.eu], [[Managed_Virtual_Machine_(MVM)#Advanced_versionDevelopment_Kits_Identification_Codes|''Advanced'' version]] of providing the MVM, the <code><i>project-name<kit P/i><N and S/code> to be used is <code>lynx</code>N]].
For more details about MVM contents If you also wish to access git repositories containing source code, please see follow the procedure described [[Managed_Virtual_Machine_(MVM)#Contents_and_provided_services|here]] and [[Managed_Virtual_Machine_(MVM)#Yocto-based_Linux_distributionAccessing_DAVE_Embedded_Systems_restricted_git_repositories|here]].}}
===Target setupand first boot===This section describes how to quick start an SBC Lynx board.delivered along with XUELK kit (see also the following image):
*connect a TTL/USB serial cable to J42 connector; J42 pinout is:
** 1: TX data
** 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
*optionally connect the system to Ethernet LAN by plugging cable into connector J16
*connect 12V power supply to J35 connector; J35 pinout is:
===First boot= Update rfs on a Linux PC====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 * insert the serial console. U-Boot automatically runs the autoboot macro, that loads the kernel SD card and check its mount pointlaunches it with the options for mounting * change dir to the root fi le system from the mmcblk0p2 ext3 SD card partition. At the end of the boot process, a demo application is launched * delete previous files and you can extract new files from tarball archive as described [[AXEL_ULite_and_SBC_Lynx_Embedded_Linux_Kit_(XUELK)#Update_rfs_on_target|here]]interact with ===Developing the system using software for 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.target===Please refer to Appendix 6.3 [[Developing the software for an example of the boot messagestarget (XUELK)|this page]].
==Physical devices mapping==
Please refer to [[Physical_devices_mapping_(XUELK)|this page]].
==Advanced topics==
===Debugging with Eclipse===
Please refer to [[Debugging with Eclipse (MVM)|this page]].