Naon Embedded Linux Kit (NELK)

Info Box Applies to Naon Applies to NaonEVB-Lite Applies to NaonEVB-Mid

Introduction

Major software components of an Embedded Linux system are:

• bootloader
• operating system kernel
• root file system, including user-space application and libraries
• tool chain (on development host)

What is

Naon Embedded Linux Kit (NELK for short) provides all the necessary stuff required to set up the developing environment to:

• build the bootloader (U-Boot)
• build and run Linux operating system on Dave's DM814x/AM387x-based SOMs (Naon, Maya, Dido)
• build Linux applications that will run on the target.

The kit is composed by:

• hardware platform composed by Naon/Maya/Dido system-on-module (SOM for short) and carrier board. Supported carrier boards are:
  • NaonEVB-Lite
  • NaonEVB-Mid
• U-Boot bootloader sources
• Linux kernel sources
• Technical documentation such hardware manuals, mechanical drawings, reference schematics, application notes etc.

The documentation related to the software issues helps the user to start and configure the bootloader and the operating system quickly by hiding most of complexity of underlying hardware. For more details about hardware characteristics Naon, please refer to the Hardware Manual. Access to source files is granted to registered kit owners' only.

What is not

The kit is not a complete Linux programming guide nor a Linux Reference Guide. Internet provides tons of information, tutorials and examples about writing applications and drivers for this operating system and how to work with it from the user's point of view (just try to type “Linux programming” in your favourite search engine for example). As the kit is heavily based on open-source community-maintained software projects, NELK does not provide exhaustive documentation for these software items but it points out where to find the information on the Internet or books. For example, for the U-Boot bootloader, the kit does not list all the commands it handles but provides the link to the on-line documentation and to the public mailing list used by its community.

For novice users who have no experience at all about embedded Linux systems, reading of this section is recommended.

Support service

Technical support is delivered through email exclusively. Only kit owners can access the support service. The addresses are:

• support-naon@dave.eu
• support-maya@dave.eu
• support-dido@dave.eu

Technical support and access to download area are lifetime for processor module buyers and one year for the other customers.

The big picture

The heart of Naon/Maya/Dido SOMs is Texas Instruments DaVinci Digital Media Processor TMS320DM8148 (http://www.ti.com/product/tms320dm8148). From software standpoint, Texas Instruments supports this processor - and its derivatives such as Sitara AM387x http://www.ti.com/product/am3874 - through so-called Linux EZ Software Development Kit (EZSDK for short). EZSDK releases are published on a regular basis. For more details please refer to:

• http://www.ti.com/tool/linuxezsdk-davinci
• http://processors.wiki.ti.com/index.php/Category:EZSDK

Naon Embedded Linux Kit, in turn, is directly derived from EZSDK. Hence NELK documentation often refers to EZSDK resources.

The following table shows how NELK releases are related to EZSDK releases.

	NELK version
Release number	1.0.0	2.0.0	3.0.0	4.0.0
Status	Obsolete	Distributed as release candidate only	Released	Planned for release
Release date	May 2012	September 2012	December 2012	April 2013
Release notes	v1.0.0	v2.0.0	v3.0.0	v4.0.0
SOM PCB version	Naon: CS021211A	Naon: CS021211A	Naon: CS021211A	Naon: CS021211A Maya: Dido:
Supported carrier boards	NaonEVB-Lite (PCB CS051412)	NaonEVB-Lite NaonEVB-Mid	NaonEVB-Lite NaonEVB-Mid	NaonEVB-Lite NaonEVB-Mid
U-Boot version	2010.06-nelk-0.9.0	2010.06-nelk-2.0.0	2010.06-nelk-3.0.0	2010.06-nelk-4.0.0
Linux version	2.6.37-nelk-1.0.0	2.6.37-nelk-2.0.0	2.6.37-nelk-3.0.0	2.6.37-nelk-4.0.0
Drivers	SPI NOR Flash (boot) EEPROM Keypad controller Touch screen controller ADC EMAC0 RMII (Fast Ethernet) EMAC1 RGMII (Gigabit Ethernet) SD/MMC1 Video Output port VOUT0 (24 bit) UART0 (2-wire) SPI0 (boot flash) I2C0 I2C1 (DDC HDMI) I2C2 HDMI GPIO SGX 3D accelerator HDVICP2 codec engine	SPI NOR Flash (boot) EEPROM Keypad controller Touch screen controller ADC EMAC0 RMII (Fast Ethernet) EMAC1 RGMII (Gigabit Ethernet) SD/MMC1 Video output port VOUT0 (24 bit) UART0 (2-wire) SPI0 (boot flash) I2C0 I2C1 (DDC HDMI) I2C2 HDMI GPIO SGX 3D accelerator HDVICP2 codec engine Nand 8-bit USB Host USB OTG (NaonEVB-Mid only) Video Input port VIN0 (NaonEVB-Mid only)	SPI NOR Flash (boot) EEPROM Keypad controller Touch screen controller ADC EMAC0 RMII (Fast Ethernet) EMAC1 RGMII (Gigabit Ethernet) SD/MMC1 Video output port VOUT0 (24 bit) UART0 (2-wire) SPI0 (boot flash) I2C0 I2C1 (DDC HDMI) I2C2 HDMI GPIO SGX 3D accelerator HDVICP2 codec engine Nand 8-bit USB Host USB OTG (NaonEVB-Mid only) Video Input port VIN0 (NaonEVB-Mid only) Video Input port VIN1 (additional host required) SATA Suspend to RAM OPP Support DWM on SDIO (NaonEVB-Lite only)	SPI NOR Flash (boot) EEPROM Keypad controller Touch screen controller ADC EMAC0 RMII (Fast Ethernet) EMAC1 RGMII (Gigabit Ethernet) SD/MMC1 Video output port VOUT0 (24 bit) UART0 (2-wire) SPI0 (boot flash) I2C0 I2C1 (DDC HDMI) I2C2 HDMI GPIO SGX 3D accelerator HDVICP2 codec engine Nand 8-bit USB Host USB OTG (NaonEVB-Mid only) Video Input port VIN0 (NaonEVB-Mid only) Video Input port VIN1 (additional host required) SATA Suspend to RAM OPP Support DWM on SDIO (NaonEVB-Lite only) Support for Maya and Dido SOMs
TI EZSDK	5.03 (December 2011)	5.04 (April 2012)	5.05.01.04 (July 2012)	5.05.02.00 (Dec 2012)

Dave adds to the latest EZSDK the customization required to support Dave's platforms (Naon,Maya,Dido)

For this reason most of the documentation provided by TI itself is valid in the SDK provided by us too. Anyway some customization is required, in particular at bootloader and linux kernel levels.

NELK contains all the required software to develop Linux application on Naon, Maya and Dido platforms:

• u-boot bootloader source code and pre-built binaries
• Linux kernel source code and pre-built binaries
• pre-built OMX libraries (most OMX source code is under NDA from TI)
• gstreamer source code
• sample development (huge!) root file system
• sample production (small enough to fit Naon on-board storage) root file system
• tools and utilities

Release notes

Please refer to NELK Release Notes for detailed NELK release notes.

Naon/Maya/Dido overview

Please refer to Naon SOM, Maya SOM, Dido SOM for an overview about the DM814x/AM387x-based system-on-module architecture.

Quick start

Quick start procedure depends on the carrier board you are working with. Please click on the appropriate link below:

• NaonEVB-Lite Quick Start
• NaonEVB-Mid Quick Start

Developing environment

TI DM8148 EZSDK software organization

Please refer to this page for an introduction of EZSDK software organization: TI DM8148 EZSDK software organization.

For detailed documentation on software development using the TI EZSDK, please refer to the EZSDK Software Developers Guide

NELK Layout

NELK MMC Layout

The MMC provided with NELK is used for

• Naon/Maya/Dido MMC boot
• NELK demo root file system storage
• NELK DVDK virtual machine image

The MMC is divided into three partition:

• the first (FAT32) partition is used for MMC booting
• the second (NTFS) partition is used for:
  • NELK DVDK image (include source code!)
  • documentation and binary images (see readme.html inside this partition for more information)
• the third partition (ext3) is used for Naon root file system

NELK DVDK Layout

The base directory where the NELK is installed is

/home/shared/devel/dave/naon-DAA/sw/linux/sdk

Here the user can find the following subdirectories:

• arm-2009q1: is where the CodeSourcery toolchain is installed
• rfs: is where the root file system is installed. Inside this directory there are two subdirectories
  • nelk: this is the default (huge) root file system. Usually it's used only development environment (via NFS)
  • nelk-min: this is the sample, minimal, root file system. It can be used as starting point for manually create a production root file system.
• sdk-x.xx.xx.xx: is where the EZSDK, plus the Dave customization, is installed (e.g sdk-5.05.02.00)
  • this directory is usually named EZSDK_INSTALL_DIR inside Makefile and build scripts

NELK Update package

For customers who have already installed the full DVDK, an update package is available. The compressed archive (nelk-x.y.x.tar.bz2) contains:

• The new SDK release (sdk-x.xx.xx.xx)
• The new root file system (e.g.: rfs/nelk-x.xx.xx.x-sdk
• A symbolic link (rfs/nelk) to the new root file system

For the complete procedure for NELK updating, please refer to How to update NELK

HowTo Build

Generally speaking, if you are using Dave Virtual Development Kit building the whole kit is a matter of:

1. startup and login into the virtual machine
2. enter the EZSDK_INSTALL_DIR directory
3. execute make all && sudo make install

The make all command will build all the components of the development kit (e.g. U-Boot binaries, Linux kernel, custom libraries and utilities) while make install install them into the root file system

For a more detailed explanation of Development Environment see Development Environment HowTo (NELK)

Use cases

Please refer to Uses cases with Naon Embedded Linux Kit. See also NELK Power Management for a detailed description on how power management is implemented in NELK.