== Diva DIVA Embedded Linux Kit: what is it? == [[File:Divelk_01.png|500px]]

Diva DIVA Embedded Linux Kit (DIVELK for short) provides all the necessary components required to set up the developing environment to:

* build and run Linux operating system on DivaDIVA-based systems

The kit is composed byof:* hardware platform composed by Diva DIVA system-on-module (SOM for short) and carrier board. Supported carrier boards are:** DivaEVBDIVAEVB-Litestandalone** SOMDIVAEVB-EVB Lite plugged on Dacu carrier board

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 Diva DIVA hardware characteristics, please refer to the Diva DIVA Hardware Manual. An account for the reserved area of [http://www.dave.eu DAVE's website] is required to access the kit contents.

== Diva DIVA Embedded Linux Kit: what is not? ==

This document describes how to run Linux on the DivaDIVA/DivaEVBDIVAEVB-Lite/Carrier-board systemand how to work with '''DIVELK version 2.0.0''' and above. For novice users who have no experience at all about embedded Linux systems, reading of [http://shop.oreilly.com/product/9780596002220.do Building Embedded Linux Systems By Karim Yaghmour] is strongly recommended. Practically speaking, the book covers all matters involved in developing software for such systems (from tool-chain organization to the most famous file systems running on top of MTD). It is not a reference guide, but it provides a complete and exhaustive overview that helps the developer save a lot of time in searching for such information on the Internet. For a brief but still exhaustive overview of the Linux and Embedded Linux world, please look at the Training and Docs sections of [http://free-electrons.com Free Electrons website].

We are committed to making our products user-friendly and will help customers use our CPU modules in their systems. Technical support is delivered through email. Support requests can be sent to [mailto:support-divahelpdesk@dave.eu support-divahelpdesk@dave.eu]. Software upgrades are available in the restricted download area of '''DAVE web siteEmbedded Systems''' git server: http://www<code>git@git.dave.eu</reserved-area. code> An account is required to access this area (please contact [mailto:support-divahelpdesk@dave.eu support-divahelpdesk@dave.eu] for account requests). 

=== Diva DIVA SOM ===

The heart of Diva DIVA SOM is Texas Instruments "Sitara" [http://www.ti.com/lsds/ti/arm/sitara_arm_cortex_a_processor/sitara_arm_cortex_a8/am335x_arm_cortex_a8/products.page?paramCriteria=no AM335x microprocessors]. From a software point of view, Texas Instruments supports this processor family through so-called Linux EZ AM Software Development Kit (EZSDK AMSDK for short). EZSDK AMSDK releases are published on a regular basis. For more details please refer to:

Diva DIVA Embedded Linux Kit, in turn, is directly derived from EZSDKAMSDK. Hence DIVELK documentation often refers to EZSDK AMSDK resources.

DivaEVB==== DIVAEVB-Lite ==== DIVAEVB-Lite is an adapter board designed to evaluate the functions of Diva DIVA system-on-module.

For further information on the DIVAEVB-Lite, please refer to [[DivaEVB-Lite provides ]] The following figure shows the carrier board block diagram: [[File:Divaevb-bd.png|600px]] ==== Dacu ==== DIVAEVB-Lite can be plugged on the following Dacu carrier board to extend the set of available interfaces.  [[File:Diva divaevb dacu.png|450px]] For further information on Dacu, please refer to:

* On board peripherals:[[Dacu]]** SPI NOR flash** 1x UART RS232 on DB9 connector** 1x Ethernet port on RJ45 connector** 1x USB 2.0 port on MiniAB connector** I/Os on expansion connectors** 12V power connector* Routed to J1 and J2 (140-pin) connectors:** 18-bit RGB LCD** 1x SD/MMC** 1x SPI** 2x UART** 2x I2C** JTAG** 2x USB** 1x McASP** Touch screen / AD signals[[Dacu_for_the_Diva_SOM]]

The following figure shows the carrier board block diagram:

[[File:DivaevbDacu-bddiva-block diagram.png|600px]]

The typical developing environment for an Embedded Linux system is composed of a host machine and a target machine. The host is used by the developer to compile the code that will run on the target. In our case the target is obviously the Diva DIVA module, while the host is assumed to be a PC running the Linux operating system. The Linux kernel running on the target can mount the root file system from different physical media. During the software development, we strongly recommend using a directory exported via NFS by the host for this purpose (see the example configuration called [[Prodotti_-_Dave_-_Diva_(DDx)_-_doc_-_Software_ManualBooting_Linux_Kernel#Net_nfs Configuration_net_nfs | net_nfs]]). Please note that DIVELK u-boot and kernel source trees are derived from the official trees released by TI; these trees have been customized to add support for the DIVA SOM. For further information on AMSDK, please refer to [http://processors.wiki.ti.com/index.php/Sitara_SDK_5.06.00_Release_Notes Sitara SDK release notes].

Dave ==== DIVELK software components ==== '''DAVE Embedded Systems''' adds to the latest EZSDK AMSDK from Texas Instruments the customization required to support the Diva DIVA platform. For this reason most of the documentation provided by TI remains valid for the DIVELK development kit. However, some customization is required, in particular at bootloader and linux kernel levels. [[Diva_Embedded_Linux_Kit_(DIVELK)#DIVELK_software_components | Please refer to this table how DIVELK releases are related to AMSDK releases]] === DIVELK Updates === {{ImportantMessage|text=It's recommended to use the latest available DIVELK version. Customer who want to update to the latest DIVELK release can send an email to [mailto:support-diva@dave.eu support-diva@dave.eu]. Please refer to [[Software_Manual_(Diva)#Release notes | Release notes]] for further information.}} ==== Updating git repositories ==== In DIVELK, the following source trees are clones of '''DAVE Embedded Systems''' public git repositories:

!|Release dateComponent|May 2013!GIT Remote!DIVELK Installation Directory

|'''Release notes'''Linux|[[Software_Manual_(Diva)#DIVELK_1git@git.0dave.0 eu:dave/diva/linux-am33x.git| Ver 1.0/home/dvdk/divelk/linux-am33x.0]]git

|SOM PCB versionU-Boot|git@git.dave.eu:dave/diva/u-boot-am33x.git|/home/dvdk/divelk/u-boot-am33x.git

|Supported carrier boardsYocto BSP|git@git.dave.eu:dave/diva/diva-bsp.git|Please refer to [[Software_Manual_(Diva)#Building the software components with Yocto | Building the software components with Yocto]]

DIVELK contains all the required software This means that these components can be kept in sync and up to develop Linux application on the Diva platformdate with '''DAVE Embedded Systems''' repositories. ==== RSA key generation ====

* Virtualbox virtual machine image with pre-installed Ubuntu Linux and pre-configured basic Linux services (Tftp, NFS, ...) * Virtualbox disk containing source code and toolsPlease follow the procedure reported below to generate the RSA ssh key:** Bootloader (u-boot) source tree cloned from DAVE's public git repository ** Linux kernel source tree cloned from DAVE's public git repository** Pre-installed AM335x EZSDK with setup scripts, makefiles, example applications, ...** Toolchain

Please note that DIVELK u-boot * select your username (ad es. username@myhost.com)* start the DVDK and kernel source trees are derived from login into the official trees released by TI; these trees have been customized to add support for virtual machine* start a shell session* enter the Diva SOM.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> ('''private key''') and <code>~/.ssh/username@myhost.com.pub</code> ('''public key''')* edit your <code>~/.ssh/config</code> adding the following lines:

For further information on EZSDK, please refer to [http://processors<pre>Host git.dave.wikieu User git Hostname git.tidave.comeu PreferredAuthentications publickey IdentityFile ~/index.phpssh/Sitara_SDK_5.06.00_Release_Notes Sitara SDK release notes]username@myhost.com</pre>

Please send the public key file to one of the following email support addresses (depending on which SOM is included in your kit version) * [mailto:support-diva@dave.eu support-diva@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. == Release notes ==Synchronizing the repository ==== When the account is enabled, you can synchronize a source tree entering the repository directory and launching the <code>git fetch</code> command, like in the following example: <pre class="workstation-terminal">dvdk@dvdk-vm:~$ cd /home/dvdk/divelk/linux-am33x.git/dvdk@dvdk-vm:/home/dvdk/divelk/linux-am33x.git$ git fetch origin</pre> Please note that <code>git fetch</code> doesn't merge the commits on the current branch. To do that, you should run

<pre class=== DIVELK 1.0.0 ==="workstation-terminal">git merge origin/diva</pre>

* Release date: May 2013* Status: planned* EZSDK version: 5or replace the ''fetch-merge'' process with a single <code>git pull</code> command.0?Please note that the recommended method is the ''fetch-merge'' process.??.??* Supported carrier boardsFor further information on Git, please refer to [http: DivaEVB//git-Lite, Dacuscm.com/documentation Git Documentation].

=== Notes =Release notes ==

The typical developing environment for an Embedded Linux system is composed of a host machine and a target machine. The host is used by the developer to (cross-)compile the code that is to run on the target. In our case the target is the Diva DIVA CPU module, while the host is assumed to be a PC running the Linux operating system, either in a physical installation or as a virtual machine. The bootloader running on the target can download the Linux kernel image through the network ([http://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol tftpTFTP]), as well as the u-boot binary images (useful when an update of the bootloader is required). Moreover, the Linux kernel running on the target is able to mount the root file system from different physical media, for example from a directory exported via [http://en.wikipedia.org/wiki/Network_File_System Network File System (NFS)] by the host. This strategy (kernel image and RFS retrieved from the network) saves time during the development phase, since no flash reprogramming or removable storage (SD, usb pen drives, external disks) is required to test new versions or updates of the software components.

Linux kernel for Sitara processors is maintained primarily by Texas Instruments, that constantly <strike>carries on a major effort to</strike> works in close cooperation with Linux community in order to push all the released drivers into mainstream kernel. Periodically TI releases the so-called Platform Support Product (PSP for short). PSP provides updated kernel sources.

Dave '''DAVE Embedded Systems''' Virtual Development Kit is a virtual machine, based on Oracle VirtualBox that allows developers to start using Dave's ''DAVE Embedded Systems'''' platform without wasting time in installing the development environment. The Virtual Machine comes with all the development tools and source code, pre-configured, and requires only a minimal setup by the end user (usually only to adapt network interface to the user environment).

Please refer to [http://wiki.dave.eu/index.php/Category:DVDK DVDK page on Dave '''DAVE Embedded Systems''' Developer's Wiki] for further information on DVDK. == DVDK installation == === DVDK features ===

* VirtualBox virtual machine (.OVA archive)* Based on Lubuntu 12.04 LTS (64-bit version)* Pre-installed VirtualBox Guest Additions* LXDE desktop environment* Boot disk with the distro and pre-configured basic Linux services:** TFTP: with base directory /srv/tftp/ (please refer to [[VirtualBox_Network_Configuration]])** NFS: configured through the /etc/exports file (please refer to [[VirtualBox_Network_Configuration]])* Secondary disk containing source code and tools:** Bootloader (u-boot) source tree cloned from DAVE Embedded Systems public git repository ** Linux kernel source tree cloned from DAVE Embedded Systems public git repository** External pre-built toolchain** Yocto bsp for DIVA* Pre-installed Yocto-based root file systems with setup scripts, makefiles, example applications, ...* Administrator account (dvdk) with autologin. Please note that the user account credentials are provided with the development kit (you can find them into the README file contained in the sw/dvdk folder of the kit distribution) == Quick start = DIVELK microSD Layout ===

=== DivaEVBThe microSD provided with DIVELK is used to store:* A bootable partition (mmcblk0p1, vfat) containing:** binary images (MLO, u-Lite ===boot and kernel images)** DIVELK documentation** DIVELK DVDK virtual machine image* DIVELK root file system partition (mmcblk0p2, ext3)

This section describes how DIVELK contains all the required software and documentation to quick start a DivaEVB-Lite system, provided that it is programmed according to DIVELK configurationdeveloping Linux application on the DIVA platform.

# connect === Importing the serial cable, provided with the board, to J6# connect this cable to PC COM port through a NULL-modem cable (not provided)# start your favourite terminal software on PC; 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 J7# connect a 12Vcc power supply to J8Virtual Machine ===

Once power has been appliedDIVELK provides a virtual machine image as a .ova file, U-Boot bootloader will be executed and which is a virtual application exported in Open Virtualization Format (OVF). Please find below the following messages will be printed on serial console (please note that messages may vary instructions for different U-Boot releases)creating the Virtualbox virtual machine:

# Start the Oracle VM VirtualBox Manager <pre class=br><br>[[File: Screenshot-Oracle VM VirtualBox Manager.png|600px]]<br><br># Click on File and select "boardImport Virtual Application", then click on "Open Virtual Application": <br><br>[[File: import-ova-terminal"01.png|600px]]<br><br>U# Navigate your file system and select the .ova file provided with the DIVELK: <br><br>[[File: import-ova-Boot 201001b.06png|600px]]<br><br># Click "Next" and on the next window click on "Import" <br><br>[[File: import-dirty (May 29 2012 ova- 16:02:39) [nelk-0.9.0-minpng|600px]] <br><br>

TI8148=== Launching the Virtual Machine ===# Now that the virtual machine is ready, launch it by clicking on the start icon: <br><br>[[File:Divelk-GP rev 2dvdk-configuration.png|600px]]<br><br># VirtualBox will open three message windows like the following, you can click "Ok" to close them<br><br>[[File:VirtualBox Info.png]]<br><br># When the boot process is completed, you can login into the Ubuntu system with the credentials provided with the development kit (you can find them into the '''README''' file contained in the '''dvdk''' folder of the kit distribution)# Mount the sdk disk launching the sdk-mount.sh script contained into /home/dvdk directory as shown on the image below:<br><br>[[File:divelk-dvdk-sdk-mount.1png|600px]]<br><br>

ARM clk<pre>dvdk@dvdk:~$ sh sdk-mount.sh divelk[sudo] password for dvdk: 600MHzDDR clkdvdk@dvdk: 400MHz~$</pre>

TI8148# Check if your keyboard layout matches the Ubuntu keyboard settings. You can change the keyboard layout selecting System->Preferences-GP rev 2>Keyboard from the top panel menù.1# Configure the Virtual Machine network interface: [[VirtualBox_Network_Configuration]]# Start working with the development kit

These messages are printed by U-BootA build system is a set of source trees, Makefiles, patches, configuration files, which has a serial console tools and scripts that allows basic interaction with makes it easy to generate all the components of a complete embedded Linux system.A build system, once properly set up, automates the configuration and cross-compilation processes, generating all the required targets (userspace packages (libraries, programs), the kernel, the bootloader and root filesystem images) depending on the configuration. Some well known build systems are the following:

At the end of its boot sequence, U-Boot prints <code style="board-terminal">DIVA#<* OpenEmbedded (http:/code> prompt and waits for user commands/wiki.openembedded.net/index.php/Main_Page)* Yocto (https://www.yoctoproject.org/)* Buildroot (http://buildroot.uclibc.org)

The default uTexas Instruments Arago distribution (http://arago-boot environment can be printed using the <code style="board-terminal">print<project.org/wiki/index.php/code> command:Main_Page) and therefore DIVELK 2.0.0 are based on Yocto.

<pre class="board-terminal">NAON#printbootcmd=run net_nfsbootdelay=3baudrateOverview of the installed components =115200autoload=yesverify=yesbootfile=naon/uImageramdisk_file=ramdisk.gzloadaddr=0x81000000spi_update_1st=sf probe 0:0; sf erase 0x0 0x20000; sf write ${loadaddr} 0x0 0x20000spi_update=sf probe 0:0; sf erase 0x20000 0x40000; sf write ${loadaddr} 0x20000 0x40000loadk=tftp ${loadaddr} ${bootfile}spi_updatek=sf probe 0:0; sf erase 0x80000 0x300000; sf write ${loadaddr} 0x80000 0x300000console=ttyO0addcons=setenv bootargs ${bootargs} console=${console},115200n8 earlyprintkaddmem=setenv bootargs ${bootargs} mem=${mem} vram=${vram} notifyk.vpssm3_sva=${notify_mem}addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gateway}:${netmask}:${hostname}:${ethdev}nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} panic=5net_nfs=run loadk nfsargs addip addcons addmem; bootm ${buf}nandargs=setenv bootargs root=/dev/mtdblock12 rw rootfstype=jffs2spi_nand=run nandargs addip addcons addmem; sf probe 0:0; sf read ${loadaddr} 0x80000 0x300000; bootm ${loadadd}mmcargs=setenv bootargs root=/dev/mmcblk0p1 rwspi_mmc=run mmcargs addip addcons addmem; sf probe 0:0; sf read ${loadaddr} 0x80000 0x300000; bootm ${loadaddr}ipaddr=192.168.0.77serverip=192.168.0.23netmask=255.255.255.0gateway=192.168.0.254hostname=naonrootpath=/home/shared/devel/dave/naon-DAA/sw/linux/sdk/rfs/nelkethdev=eth0mem=176Mvram=46Mnotify_mem=0xBF900000ethaddr=d4:94:a1:8e:68:24ethact=cpswspi_load_1st=tftp ${loadaddr} naon/u-boot.min.spiload=tftp ${loadaddr} naon/u-boot_new.binstdin=serialstdout=serialstderr=serial

Environment size: 1588Once the virtual machine is ready, the actual development kit can be found into the directory <code>/home/dvdk/65532 bytesdivelk</precode>: <br><br>[[File:Divelk-dvdk-divelk-content.png|600px]]<br><br>

A build system is a set of <pre>source trees, Makefiles, patches, configuration files, tools and scripts that makes it easy to generate all the components of a complete embedded Linux system~/divelk/yocto/sdk/diva-qt5/environment-setupexport LDFLAGS=-L${PKG_CONFIG_SYSROOT_DIR}/usr/lib/4. A build system, once properly set up, automates the configuration and cross7.3export CFLAGS=""export CPPFLAGS=""export CXXFLAGS=""export CPATH=""export ARCH=armexport CROSS_COMPILE=arm-compilation processes, generating all the required targets (userspace packages (libraries, programs), the kernel, the bootloader and root filesystem images) depending on the configuration. Some well known build systems are the following: linux-gnueabihf-</pre>

* Arago (httpUsing the following command, the environment shell variables required during the building procedure are set up://arago-project.org/wiki/index.php/Main_Page)* OpenEmbedded (http://wiki.openembedded.net/index.php/Main_Page)<pre>* Yocto (https:source ~/divelk/wwwenv.yoctoproject.org/)sh* Buildroot (http:<//buildroot.uclibc.org)pre>

One of the most useful features of a bootloader during development is the capability to download the Linux kernel from the network. This saves a lot of time because developer doesn't have to program the image in flash every time he/she modifies it. U-Boot implements the TFTP protocol (see the <code>tftp </code> command), so the host system must be configured to enable the TFTP service. Installation and configuration of a tftp TFTP server depends on the host Linux distribution. The default DVDK <code>tftp</code> installation has <code>/srv/tftp</code> as work directory. A subdirectory dedicated to the image files associated to the DIVELK (/srv/tftp/divelk) is available, but developers can add their custom subdirectories when required.

 One of the most important components of a Linux system is the root file system. A good development root file system provides the developer with all the useful tools that can help him/her developers on his/her their work. Such a root file system can become very big in size, so it's hard to store it in flash memory. User could split the file system in different parts, mounting them from different media (flash, network, usb...). But the most convenient thing is to mount the whole root file system from the network, allowing the host system and the target to share the same files. In such a this way, the developer developers can quickly modify the root file system, even “on the fly” (meaning that the file system can be modified while the system is running).The most common way to setup a system like the one described is through NFS(Network File System). As for tftpTFTP, installation and configuration depends on the host linux Linux distribution. The default DVDK NFS installation is configured for sharing <code>/home/dvdk/divelk</code> directory and all the subdirectories. We recommend reading the [[VirtualBox_Network_Configuration]] page for additional details on the DVDK networking configuration and on how to enable NFS.

To start developing software for the Diva DIVA platform, users need a proper toolchain, which can be pre-built or built-from-scratch. Building a toolchain from scratch is not a trivial task (though using a recent build system is easier than in the past), so the recommended approach consists in using a pre-built toolchain, like the Sourcery G++ Lite 2009q1-203 for ARM GNU/Linux. To install it, user should simply download the installer from the http://www.codesourcery.com/sgpp/lite/arm/portal/release858 web page and run it.

At DIVELK provides the time of this writing several tool chains – free and commercial – are availableLinaro gnueabihf-4.7-2013. The Codesourcery 03 toolchain (Sourcery G++ Lite 2009q1-203 for ARM GNU/Linux (http://wwwGCC version is 4.codesourcery7.com/sgpp/lite/arm/portal/release858)3) will be the default choice and all the compiling examples will be based on it.

DIVELK provides a pre-built root file systemsystems, that can be used during the evaluation/development phase, since it provides a sufficient set of they contains the software packages for working with the Diva DIVA platform. However, there are other pre-built file systems that can be used:

* Arago (httpDIVELK root file systems are built with the Yocto build system and are stored into the following directories://arago-project.org/files/releases/)* Angstrom/Narcissus (http://www.angstrom-distribution.org/narcissus/)* Beaglebone (http://www.angstrom-distribution.org/demo/beaglebone/)

=== Creating Building the Virtual Machine =software components with Yocto ==The build process creates an entire Linux distribution from source. The build process can be summarized as follows:* Make sure that all the prerequisites are met* Initialize the build environment, as described in the following sections* Optionally ensure the conf/local.conf configuration file, which is found in the Build Directory, is set up how you want it. This file defines many aspects of the build environment including the target machine architecture through the MACHINE variable, the development machine's processor use through the BB_NUMBER_THREADS and PARALLEL_MAKE variables, and a centralized tarball download directory through the DL_DIR variable.* Build the image using the bitbake command. If you want information on BitBake, see the BitBake User Manual.N.B. Since the DIVELK virtual machine is already configured to match all the requirements for using the Yocto build system, developers who wants to quickly build a Yocto image can directly go to section [[Software_Manual_(Diva)#Building the Yocto image]].

DIVELK provides a virtual machine image as a .ova file, which is a virtual application exported in Open Virtualization Format (OVF). Please find below the instructions for creating the Virtualbox virtual machine: # Start the Oracle VM VirtualBox Manager <br><br>[[File: Screenshot-Oracle VM VirtualBox Manager.png|600px]]<br><br># Click on File and select "Import Virtual Application", then click on "Open Virtual Application": <br><br>[[File: import-ova-01.png|600px]]<br><br># Navigate your file system and select the .ova file provided with the DIVELK: <br><br>[[File: import-ova-01b.png|600px]]<br><br># Click "Next" and on the next window click on "Import" <br><br>[[File: import-ova-02.png|600px]]<br><br>=== Prerequisites ===

=== Launching the VM ===# Now The following prerequisites are required and only need to be done once. Please note that the DIVELK virtual machine is ready, launch it by clicking already configured to match all the requirements for using the Yocto build system.Some generic development tools are required on the start iconhost Linux machine: <br><br>[[File:Divelk* git* curl* build-dvdk-configuration.png|600px]]<br><br>essential* diffstat* texinfo* gawk# VirtualBox will open three message windows like the following, you can click "Ok" to close them<br><br>[[File:VirtualBox Info.png]]<br><br>* chrpath# When * ia32-libs (if the boot process host machine is completed, you can login into the Ubuntu system with the credentials provided with the development kit (you can find them into the '''README''' file contained in the '''dvdk''' folder of the kit distributionrunning a 64-bit OS)# Mount the sdk disk launching the sdk-mount.sh script contained into /home/dvdk directory as shown on the image below:<br><br>[[File:divelk-dvdk* python-sdk-mount.png|600px]]<br><br>m2crypto

Once logged in, It is also recommended to switch the system could suggest shell from Ubuntu's standard dash to update the [httpmore universal bash:<pre>$ sudo dpkg-reconfigure dash<//www.virtualbox.org/manual/ch04.html Virtualbox Guest Additions package]. You can follow the on-screen instructions to easily install the updated package.pre>

==== Further steps =Initializing the build environment ===

# Check if your keyboard layout matches In the Ubuntu keyboard settingsDIVELK, we have simplified the Yocto initialization phase, relying on the repo tool and on a DIVA bsp git repository, so that the initialization can be completed with a few commands as reported below:<pre>$ curl http://commondatastorage.googleapis. You can change the keyboard layout selecting Systemcom/git-repo-downloads/repo >Preferencesrepo$ chmod +x repo$ ./repo init -u git@git.dave.eu:dave/diva/diva->Keyboard from the top panel menùbsp.git -b diva# Configure the Virtual Machine network interface: [[VirtualBox_Network_Configuration]]$ ./repo sync# Start working with the development kit</pre>

=== DIVELK HowTos Building the Yocto image ===

Once Please note that even building the basic root file system requires a few hours to complete the process on a mid-hi range desktop PC (4-6 cores, 8-12 GiB RAM), also depending on the Internet connection speed (all source are fetched from the network). Nearly 20GiB of disk space is required for the build. Moreover, building inside the DVDK adds some overhead, since the performances of a virtual machine are reduced if compared to the physical hardware. Thus, it's recommended to check the hardware capabilities of the host system and, when building with Yocto is readyrequired, developers should consider the actual development kit can be found into the directory <code>/home/dvdk/delk</code>: <br><br>[[Filefollowing options:Divelk-dvdk-divelk-content.png|600px]]<br><br>

The delk directory contains * migrating the following subdirectoriesbuild system to a physical machine* assuming that the host system has the required resources, extending the hardware capabilities of the default DVDK (eg:adding more cores and disk space)

* arago-2012.10: Once completed the cross-toolchain. GNU Compiler Collection (GCC) version is 4.5.3* linux-am33x: the Linux source tree* u-boot-am33x: initialization phase, developers can launch the U-Boot source tree* rfs: DIVELK provides two root file systems:** arago-base: minimal root file system Yocto image build process with basic packages** tisdk: full root file system with lots of packages, useful during the development phase* env.sh: a bash script containing the following linescommands:

export PATH=$ cd ~/divelk/diva-bsp$ source ~/divelk/arago-2012env.10/bin:sh$PATHexport ARCH=armexport CROSS_COMPILE=armsource diva-bsp-aragoinit-linuxenv.sh$ bitbake matrix-gnueabirootfs-image

By issuing the following command, some environment shell variables required during the building procedure Please note that three different images are set upavailable: * matrix-rootfs-image (includes the matrix gui application from Texas Instruments)* qt5-rootfs-image (root file system with Qt 5.1.1 libraries and examples)* base-rootfs-image (minimal root file system)

<pre>source ~The resulting files (kernel, device tree and u-boot binaries, plus root file system in a .tar.gz archive) will then be available inside the build/tmp/deploy/images/diva/envdirectory.sh</pre>

Enter the Linux sources directory (''~/divadivelk/linux-am33x.git'') and run the following commands:

dvdk@dvdk-vm:~/divadivelk/linux-am33x.git$ make diva_defconfigdvdk@dvdk-vm:~/divadivelk/linux-am33x.git$ make uImageam335x-divelk.dtb

The former command select selects the default Diva DIVA configuration, while the latter build builds the kernel binary image with the required u-boot headerand the dtb binary.

Enter the Linux U-Boot sources directory (''~/divadivelk/u-boot-am33x.git'') and run the following commands:

dvdk@dvdk-vm:~/divadivelk/u-boot-am33x.git$ make diva_spibootdvdk@dvdk-vm:~/divadivelk/u-boot-am33x.git$ make

The former command select selects the default Diva DIVA configuration which is used to boot from SPI NOR Flash, while the latter build builds the u-boot binary images.

Once the build process is complete, the binary images can be copied to the <code>/srv/tftp/divelk/</code> directory with the following command: <pre>dvdk@dvdk-vm:~/divelk/u-boot-am33x$ sudo cp MLO MLO.byteswap u-boot.img /srv/tftp/divelk/</pre> === Build the graphics components a custom application === Some users may prefer to cross-compile their applications outside of the Yocto flow. It maybe specifically useful and easier for new projects in their prototyping and proof-of-concept stages or for any smaller applications in general. This way users don't have to worry about creating Yocto "recipes" for their applications and becoming familiar with the entire Yocto build system.In order to cross-compile an application, written in C/C++, the cross-toolchain provided with the DIVELK is required.Assuming that the environment variables have been configured with the <code>env.sh</code> script, developers can write a simple "Hello world" application, called for example hello.c:<pre>#include <stdio.h>int main(){ printf("Hello world\n"); return 0;}</pre>To cross-compile it:<pre>$ arm-none-linux-gnueabi-gcc -o hello hello.c</pre>Copy the executable file to the root file system, and execute it from the DIVA system:<pre>root@diva:~#./helloHello world</pre>

<pre>DIVA# nand infoDevice 0: nand0, sector size 128 KiB Page size 2048 b OOB size 64 b Erase size 131072 b</pre> === Net_nfs Default flash NOR SPI partitions ===

=> setenv serverip 192[ 1.168370563] Creating 7 MTD partitions on "spi1.0.72 ":=> saveenv Saving Environment to NAND..[ 1. 375888] 0x000000000000-0x000000040000 : "MLO"Erasing Nand[ 1... Erasing at 0x0 383286] 0x000000040000-0x0000000c0000 : "u- 2490368% completeboot"[ 1. 390594] 0x0000000c0000-0x000000100000 : "env1"Writing to Nand[ 1.397868] 0x000000100000-0x000000140000 : "env2"[ 1.405253] 0x000000140000-0x000000180000 : "fdt"[ 1. done 412191] 0x000000180000-0x000000780000 : "kernel"=>[ 1.419714] 0x000000780000-0x000002000000 : "free"

To run this configuration, just issue the command following command:=== Default flash NAND partitions === 

==Quick start = Automatic = This section describes how to quick start a DIVA system composed of a DIVA SOM plugged into the DIVAEVB-Lite and then mounted on the Dacu carrier board, provided that it is programmed according to DIVELK configuration. The SD provided with the DIVELK can be used to boot the system, since it contains a bootable partition (mmcblk0p1) and a root file system partition (mmcblk0p2). # connect the serial cable, provided with the board, to the J25 pin-strip connector on the Dacu board# insert the microSD card provided with the development kit into the microSD slot# connect a 12Vcc power supply to JP2 on the Dacu board# (optional) connect this cable to PC COM port through a NULL-modem cable (not provided)# (optional) start your favourite terminal software on PC; 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 J7 of the DIVAEVB-Lite The system is configured to boot automatically, when powered up, from the SD card, loading u-boot which runs the<code>mmcboot</code> macro, that loads the kernel and launches it with the options for mounting the root file system from the mmcblk0p2 partition. The following messages will be printed on serial console (please note that messages may vary for different U-Boot releases): <pre class="board-terminal"> U-Boot SPL 2013.10 (Sep 13 2014 - 10:43:18) [divelk-2.0.0]reading u-boot.imgreading u-boot.img  U-Boot 2013.10 (Sep 13 2014 - 10:43:18) [divelk-2.0.0] AM335X-GP rev 1 720 MHzI2C: readyDRAM: 512 MiBWARNING: Caches not enabledNow running in RAM - U-Boot at: 9ff50000NAND: 1024 MiBMMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB*** Warning - bad CRC, using default environment Net: cpsw, usb_etherHit any key to stop autoboot: 0 trying to boot from DIVELK MMC reading boot.scr419 bytes read in 5 ms (81.1 KiB/s)## Executing script at 80900000reading uImage4714280 bytes read in 490 ms (9.2 MiB/s)reading am335x-divelk.dtb37129 bytes read in 11 ms (3.2 MiB/s)## Booting kernel from Legacy Image at 80200000 ... Image Name: Linux-3.12.10-divelk-2.0.0 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4714216 Bytes = 4.5 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK## Flattened Device Tree blob at 80f80000 Booting using the fdt blob at 0x80f80000 Loading Kernel Image ... OK Loading Device Tree to 9fe02000, end 9fe0e108 ... OK Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0[ 0.000000] Linux version 3.12.10-divelk-2.0.0 (amon@linuxserver2) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #26 SMP Sat Sep 13 10:45:59 CEST 2014[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache[ 0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: DAVE Embedded System DIVELK[ 0.000000] cma: CMA: reserved 24 MiB at 9e000000[ 0.000000] Memory policy: ECC disabled, Data cache writeback[ 0.000000] CPU: All CPU(s) started in SVC mode.[ 0.000000] AM335X ES1.0 (sgx neon )[ 0.000000] PERCPU: Embedded 8 pages/cpu @c0d9a000 s9024 r8192 d15552 u32768[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 129280[ 0.000000] Kernel command line: root=/dev/mmcblk0p2 rw console=ttyO0,115200n8 consoleblank=0 mtdparts=omap2-nand.0:128k(SPL),128k(SPL.backup1),128k(SPL.backup2),128k(SPL.backup3),1920k(u-boot),128k(u-boot-env),128k(fdt),6m(kernel),-(rootfs);spi1.0:256k(MLO),512k(u-boot),256k(env1),256k(env2),256k(fdt),6m(kernel),-(free)[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)[ 0.000000] Memory: 482188K/521216K available (6358K kernel code, 562K rwdata, 2168K rodata, 368K init, 254K bss, 39028K reserved, 0K highmem)[ 0.000000] Virtual kernel memory layout:[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)[ 0.000000] vmalloc : 0xe0800000 - 0xff000000 ( 488 MB)[ 0.000000] lowmem : 0xc0000000 - 0xe0000000 ( 512 MB)[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)[ 0.000000] .text : 0xc0008000 - 0xc085bf9c (8528 kB)[ 0.000000] .init : 0xc085c000 - 0xc08b8340 ( 369 kB)[ 0.000000] .data : 0xc08ba000 - 0xc09468b0 ( 563 kB)[ 0.000000] .bss : 0xc09468b8 - 0xc09863f4 ( 255 kB)[ 0.000000] Hierarchical RCU implementation.[ 0.000000] RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.[ 0.000000] NR_IRQS:16 nr_irqs:16 16[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts[ 0.000000] Total of 128 interrupts on 1 active controller[ 0.000000] OMAP clockevent source: timer2 at 24000000 Hz[ 0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms[ 0.000000] OMAP clocksource: timer1 at 24000000 Hz[ 0.000000] Console: colour dummy device 80x30[ 0.000409] Calibrating delay loop... 479.23 BogoMIPS (lpj=2396160)[ 0.119684] pid_max: default: 32768 minimum: 301[ 0.119839] Security Framework initialized[ 0.119964] Mount-cache hash table entries: 512[ 0.131811] CPU: Testing write buffer coherency: ok[ 0.132332] CPU0: thread -1, cpu 0, socket -1, mpidr 0[ 0.132408] Setting up static identity map for 0xc063b648 - 0xc063b6b8[ 0.137504] Brought up 1 CPUs[ 0.137533] SMP: Total of 1 processors activated.[ 0.137544] CPU: All CPU(s) started in SVC mode.[ 0.138587] devtmpfs: initialized[ 0.143587] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3[ 0.209601] omap_hwmod: debugss: _wait_target_disable failed[ 0.210581] pinctrl core: initialized pinctrl subsystem[ 0.211857] regulator-dummy: no parameters[ 0.214690] NET: Registered protocol family 16[ 0.217798] DMA: preallocated 256 KiB pool for atomic coherent allocations[ 0.221492] cpuidle: using governor ladder[ 0.221516] cpuidle: using governor menu[ 0.230756] platform mpu.1: FIXME: clock-name 'fck' DOES NOT exist in dt![ 0.232413] platform 49000000.edma: FIXME: clock-name 'fck' DOES NOT exist in dt![ 0.234218] OMAP GPIO hardware version 0.1[ 0.247827] omap-gpmc 50000000.gpmc: could not find pctldev for node /pinmux@44e10800/nandflash_pins_default, deferring probe[ 0.247871] platform 50000000.gpmc: Driver omap-gpmc requests probe deferral[ 0.248489] platform 56000000.sgx: FIXME: clock-name 'fck' DOES NOT exist in dt![ 0.253038] DSS not supported on this SoC[ 0.253065] No ATAGs?[ 0.253079] hw-breakpoint: debug architecture 0x4 unsupported.[ 0.295970] bio: create slab <bio-0> at 0[ 0.319222] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver[ 0.321038] vin: 5000 mV [ 0.323718] SCSI subsystem initialized[ 0.325674] usbcore: registered new interface driver usbfs[ 0.325939] usbcore: registered new interface driver hub[ 0.326254] usbcore: registered new device driver usb[ 0.327385] omap_i2c 44e0b000.i2c: could not find pctldev for node /pinmux@44e10800/pinmux_i2c0_pins, deferring probe[ 0.327421] platform 44e0b000.i2c: Driver omap_i2c requests probe deferral[ 0.327950] pps_core: LinuxPPS API ver. 1 registered[ 0.327964] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>[ 0.328161] PTP clock support registered[ 0.330978] Advanced Linux Sound Architecture Driver Initialized.[ 0.332716] Switched to clocksource timer1[ 0.363794] NET: Registered protocol family 2[ 0.364657] TCP established hash table entries: 4096 (order: 3, 32768 bytes)[ 0.364762] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)[ 0.364847] TCP: Hash tables configured (established 4096 bind 4096)[ 0.364928] TCP: reno registered[ 0.364948] UDP hash table entries: 256 (order: 1, 8192 bytes)[ 0.364976] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)[ 0.365256] NET: Registered protocol family 1[ 0.365759] RPC: Registered named UNIX socket transport module.[ 0.365774] RPC: Registered udp transport module.[ 0.365783] RPC: Registered tcp transport module.[ 0.365793] RPC: Registered tcp NFSv4.1 backchannel transport module.[ 0.367016] NetWinder Floating Point Emulator V0.97 (double precision)[ 0.367827] PM: Loading am335x-pm-firmware.bin[ 0.530548] VFS: Disk quotas dquot_6.5.2[ 0.530738] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)[ 0.531740] NFS: Registering the id_resolver key type[ 0.531867] Key type id_resolver registered[ 0.531880] Key type id_legacy registered[ 0.532254] NTFS driver 2.1.30 [Flags: R/W].[ 0.532307] jffs2: version 2.2. (NAND) (SUMMARY) �© 2001-2006 Red Hat, Inc.[ 0.532535] msgmni has been set to 989[ 0.535449] NET: Registered protocol family 38[ 0.535511] io scheduler noop registered[ 0.535523] io scheduler deadline registered[ 0.535560] io scheduler cfq registered (default)[ 0.538175] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568[ 0.590593] Console: switching to colour frame buffer device 100x30[ 0.598277] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled[ 0.601816] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88, base_baud = 3000000) is a OMAP UART0[ 1.281209] console [ttyO0] enabled[ 1.286942] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20[ 1.310673] brd: module loaded[ 1.323060] loop: module loaded[ 1.333908] mtdoops: mtd device (mtddev=name/number) must be supplied[ 1.343735] edma-dma-engine edma-dma-engine.0: allocated channel for 0:17[ 1.350969] edma-dma-engine edma-dma-engine.0: allocated channel for 0:16[ 1.358842] m25p80 spi1.0: s25fl256s1 (32768 Kbytes)[ 1.364293] 7 cmdlinepart partitions found on MTD device spi1.0[ 1.370563] Creating 7 MTD partitions on "spi1.0":[ 1.375888] 0x000000000000-0x000000040000 : "MLO"[ 1.383286] 0x000000040000-0x0000000c0000 : "u-boot"[ 1.390594] 0x0000000c0000-0x000000100000 : "env1"[ 1.397868] 0x000000100000-0x000000140000 : "env2"[ 1.405253] 0x000000140000-0x000000180000 : "fdt"[ 1.412191] 0x000000180000-0x000000780000 : "kernel"[ 1.419714] 0x000000780000-0x000002000000 : "free"[ 1.428475] CAN device driver interface[ 1.434708] c_can_platform 481cc000.d_can: c_can_platform device registered (regs=fa1cc000, irq=68)[ 1.446015] usbcore: registered new interface driver asix[ 1.452044] usbcore: registered new interface driver ax88179_178a[ 1.458930] usbcore: registered new interface driver cdc_ether[ 1.465550] usbcore: registered new interface driver r815x[ 1.471615] usbcore: registered new interface driver smsc95xx[ 1.477990] usbcore: registered new interface driver net1080[ 1.484283] usbcore: registered new interface driver cdc_subset[ 1.490779] usbcore: registered new interface driver zaurus[ 1.497093] usbcore: registered new interface driver cdc_ncm[ 1.503937] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver[ 1.510886] ehci-omap: OMAP-EHCI Host Controller driver[ 1.517235] usbcore: registered new interface driver cdc_wdm[ 1.523592] usbcore: registered new interface driver usb-storage[ 1.530485] usbcore: registered new interface driver usbserial[ 1.537087] usbcore: registered new interface driver usbserial_generic[ 1.544375] usbserial: USB Serial support registered for generic[ 1.550984] usbcore: registered new interface driver ftdi_sio[ 1.557337] usbserial: USB Serial support registered for FTDI USB Serial Device[ 1.569745] musb-hdrc musb-hdrc.0.auto: Enabled SW babble control[ 1.576609] musb-hdrc musb-hdrc.0.auto: Falied to request rx1.[ 1.583022] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517[ 1.591267] platform musb-hdrc.0.auto: Driver musb-hdrc requests probe deferral[ 1.601463] musb-hdrc musb-hdrc.1.auto: Enabled SW babble control[ 1.608210] musb-hdrc musb-hdrc.1.auto: Falied to request rx1.[ 1.614488] musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517[ 1.622856] platform musb-hdrc.1.auto: Driver musb-hdrc requests probe deferral[ 1.653327] mousedev: PS/2 mouse device common for all mice[ 1.660663] input: ti-tsc as /devices/ocp.2/44e0d000.tscadc/TI-am335x-tsc/input/input0[ 1.671593] i2c /dev entries driver[ 1.678569] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec[ 1.688151] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25[ 1.695572] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24[ 1.702910] omap_hsmmc 48060000.mmc: unable to get vmmc regulator -517[ 1.709845] edma-dma-engine edma-dma-engine.0: freeing channel for 24[ 1.716920] edma-dma-engine edma-dma-engine.0: freeing channel for 25[ 1.723910] platform 48060000.mmc: Driver omap_hsmmc requests probe deferral[ 1.732299] ledtrig-cpu: registered to indicate activity on CPUs[ 1.739174] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36[ 1.746525] omap-sham 53100000.sham: hw accel on OMAP rev 4.3[ 1.754574] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2[ 1.760718] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5[ 1.768028] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6[ 1.777248] usbcore: registered new interface driver usbhid[ 1.783237] usbhid: USB HID core driver[ 1.791362] usbcore: registered new interface driver snd-usb-audio[ 1.801674] UDA134X SoC Audio Codec[ 1.824052] davinci_evm sound.4: uda134x-hifi <-> 48038000.mcasp mapping ok[ 1.837299] oprofile: no performance counters[ 1.842555] oprofile: using timer interrupt.[ 1.847618] TCP: cubic registered[ 1.851130] Initializing XFRM netlink socket[ 1.855784] NET: Registered protocol family 17[ 1.860546] NET: Registered protocol family 15[ 1.865336] can: controller area network core (rev 20120528 abi 9)[ 1.872096] NET: Registered protocol family 29[ 1.876881] can: raw protocol (rev 20120528)[ 1.881397] can: broadcast manager protocol (rev 20120528 t)[ 1.887520] 8021q: 802.1Q VLAN Support v1.8[ 1.892100] Key type dns_resolver registered[ 1.897496] cpu cpu0: cpu0 regulator not ready, retry[ 1.903001] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral[ 1.911300] PM: CM3 Firmware Version = 0x187[ 1.916487] ThumbEE CPU extension supported.[ 1.923680] omap-gpmc 50000000.gpmc: GPMC revision 6.0[ 1.929131] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000[ 1.937019] NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit), 1024MiB, page size: 2048, OOB size: 64[ 1.949754] omap2-nand: detected x8 NAND flash[ 1.954499] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme[ 1.960175] omap2-nand: using custom ecc layout[ 1.965136] 9 cmdlinepart partitions found on MTD device omap2-nand.0[ 1.971955] Creating 9 MTD partitions on "omap2-nand.0":[ 1.977663] 0x000000000000-0x000000020000 : "SPL"[ 1.985117] 0x000000020000-0x000000040000 : "SPL.backup1"[ 1.993214] 0x000000040000-0x000000060000 : "SPL.backup2"[ 2.001160] 0x000000060000-0x000000080000 : "SPL.backup3"[ 2.009145] 0x000000080000-0x000000260000 : "u-boot"[ 2.018198] 0x000000260000-0x000000280000 : "u-boot-env"[ 2.026420] 0x000000280000-0x0000002a0000 : "fdt"[ 2.033730] 0x0000002a0000-0x0000008a0000 : "kernel"[ 2.046645] 0x0000008a0000-0x000040000000 : "rootfs"[ 2.910559] vrtc: 1800 mV [ 2.914394] vrtc: supplied by vin[ 2.921442] vio: 1500 <--> 3300 mV at 1500 mV [ 2.926452] vio: supplied by vin[ 2.934061] vdd_mpu: 600 <--> 1500 mV at 1137 mV [ 2.939149] vdd_mpu: supplied by vin[ 2.947000] vdd_core: 600 <--> 1500 mV at 1137 mV [ 2.952150] vdd_core: supplied by vin[ 2.959384] vdd3: 5000 mV [ 2.965617] vdig1: 1200 <--> 2700 mV at 1800 mV [ 2.970598] vdig1: supplied by vin[ 2.977702] vdig2: 1200 <--> 1800 mV at 1800 mV [ 2.982663] vdig2: supplied by vin[ 2.989856] vpll: 1800 <--> 2500 mV at 1800 mV [ 2.994840] vpll: supplied by vin[ 3.001759] vdac: 1800 <--> 2850 mV at 1800 mV [ 3.006728] vdac: supplied by vin[ 3.013866] vaux1: 1800 <--> 2850 mV at 1800 mV [ 3.018861] vaux1: supplied by vin[ 3.026421] vaux2: 1800 <--> 2800 mV at 3300 mV [ 3.031390] vaux2: supplied by vin[ 3.038485] vaux33: 1800 <--> 3300 mV at 3300 mV [ 3.043689] vaux33: supplied by vin[ 3.050823] vmmc: 1800 <--> 3300 mV at 3300 mV [ 3.055802] vmmc: supplied by vin[ 3.073949] tps65910-rtc tps65910-rtc: rtc core: registered tps65910-rtc as rtc0[ 3.083252] at24 0-0050: 4096 byte 24c32 EEPROM, writable, 32 bytes/write[ 3.092440] ina2xx 0-0041: power monitor ina226 (Rshunt = 10000 uOhm)[ 3.099442] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 100 kHz[ 3.106054] musb-hdrc musb-hdrc.0.auto: Enabled SW babble control[ 3.114825] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver[ 3.121563] musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1[ 3.130296] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002[ 3.137543] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 3.145203] usb usb1: Product: MUSB HDRC host driver[ 3.150459] usb usb1: Manufacturer: Linux 3.12.10-divelk-2.0.0 musb-hcd[ 3.157470] usb usb1: SerialNumber: musb-hdrc.0.auto[ 3.164033] hub 1-0:1.0: USB hub found[ 3.168106] hub 1-0:1.0: 1 port detected[ 3.173859] musb-hdrc musb-hdrc.1.auto: Enabled SW babble control[ 3.182507] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver[ 3.189383] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 2[ 3.198116] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002[ 3.205382] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1[ 3.213083] usb usb2: Product: MUSB HDRC host driver[ 3.218342] usb usb2: Manufacturer: Linux 3.12.10-divelk-2.0.0 musb-hcd[ 3.225358] usb usb2: SerialNumber: musb-hdrc.1.auto[ 3.231979] hub 2-0:1.0: USB hub found[ 3.236124] hub 2-0:1.0: 1 port detected[ 3.241593] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25[ 3.248906] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24[ 3.341278] mmc0: host does not support reading read-only switch. assuming write-enable.[ 3.352042] mmc0: new high speed SDHC card at address 1234[ 3.358955] mmcblk0: mmc0:1234 SA16G 14.6 GiB [ 3.363802] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6[ 3.370249] davinci_mdio 4a101000.mdio: detected phy mask ffffffbf[ 3.379000] libphy: 4a101000.mdio: probed[ 3.383422] davinci_mdio 4a101000.mdio: phy[6]: device 4a101000.mdio:06, driver SMSC LAN8710/LAN8720[ 3.393289] mmcblk0: p1 p2[ 3.398432] Detected MACID = 00:50:c2:1e:af:e0[ 3.409822] tps65910-rtc tps65910-rtc: setting system clock to 2014-10-03 10:36:29 UTC (1412332589)[ 3.425312] ALSA device list:[ 3.428505] #0: Diva Dacu[ 3.440728] kjournald starting. Commit interval 5 seconds[ 3.461578] EXT3-fs (mmcblk0p2): using internal journal[ 3.467158] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode[ 3.474540] VFS: Mounted root (ext3 filesystem) on device 179:2.[ 3.483932] devtmpfs: mounted[ 3.487639] Freeing unused kernel memory: 368K (c085c000 - c08b8000)INIT: version 2.88 bootingStarting udev[ 4.382357] udevd[954]: starting version 182[ 9.887444] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.[ 10.144522] cryptodev: driver 1.6 loaded.Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directorybootlogd.ALSA: Restoring mixer settings...Configuring network interfaces... [ 13.122234] net eth0: initializing cpsw version 1.12 (0)[ 13.130330] net eth0: phy found : id is : 0x7c0f1[ 13.144609] 8021q: adding VLAN 0 to HW filter on device eth0udhcpc (v1.20.2) startedSending discover...Sending discover...[ 16.362961] libphy: 4a101000.mdio:06 - Link is Up - 100/FullSending discover...No lease, failingdone.INIT: Entering runlevel: 5Starting system message bus: dbus.UIM SYSFS Node Not FoundStarting Dropbear SSH server: dropbear.Starting telnet daemon.Starting syslogd/klogd: doneStarting thttpd.Starting PVR******************************************************************************************************************************NOTICE: This file system contains the followin GPLv3 packages: binutils-symlinks binutils gdbserver If you do not wish to distribute GPLv3 components please removethe above packages prior to distribution. This can be done usingthe opkg remove command. i.e.: opkg remove <package>Where <package> is the name printed in the list above NOTE: If the package is a dependency of another package you will be notified of the dependent packages. You should use the --force-removal-of-dependent-packages option to also remove the dependent packages as well******************************************************************************************************************************Stopping Bootlog daemon: bootlogd.umount: can't umount /mnt/.psplash: Device or resource busy  _____ _____ _ _ | _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_ | | _| .'| . | . | | __| _| . | | | -_| _| _||__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_| |___| |___|  Arago Project http://arago-project.org diva ttyO0 Arago 2013.12 diva ttyO0 diva login:  </pre> The console dump below (obtained using the <code>print</code> command) shows the default u-boot environment: <pre class="board-terminal">DIVA# printaddcons=setenv bootargs ${bootargs} console=${console} earlyprintk no_console_suspend loglevel=8addip=setenv bootargs ${bootargs} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off panic=1 eth=${ethaddr}addmisc=setenv bootargs ${bootargs} ${mtdparts}\\;${mtdparts_spi}arch=armbaudrate=115200board=divaboard_name=divabootcmd=echo trying to boot from DIVELK MMC; mmc rescan 0; fatload mmc 0 80900000 boot.scr; source 80900000; dcache on; run net_nfsbootdelay=3bootfile=diva/uImageconsole=ttyO0,115200n8cpu=armv7eth1addr=c4:ed:ba:7f:c1:46ethact=cpswethaddr=00:50:c2:1e:af:e0ethdev=eth0fdtaddr=0x80F80000fdtfile=diva/am335x-divelk.dtbgatewayip=192.168.0.254hostname=divelkipaddr=192.168.0.89kloadaddr=0x80007fc0load=tftp ${loadaddr} diva/u-boot.imgloadaddr=0x80200000loadfdt=tftp ${fdtaddr} ${fdtfile}loadk=tftp ${kloadaddr} ${bootfile}mtdids=nand0=omap2-nand.0mtdparts=mtdparts=omap2-nand.0:128k(SPL),128k(SPL.backup1),128k(SPL.backup2),128k(SPL.backup3),1920k(u-boot),128k(u-boot-env),128k(fdt),6m(kernel),-(rootfs)mtdparts_spi=spi1.0:256k(MLO),512k(u-boot),256k(env1),256k(env2),256k(fdt),6m(kernel),-(free)nand_load_1st=tftp ${loadaddr} diva/MLOnand_nfs=nand read ${kloadaddr} kernel 0x600000; nand read ${fdtaddr} fdt 0x40000; run nfsargs addip addcons addmisc; dcache on; bootm ${kloadaddr} - ${fdtaddr}nand_update=nand erase.part u-boot; nand write ${loadaddr} u-boot ${filesize}nand_update_1st=nand erase.part SPL; nand write ${loadaddr} SPL ${filesize}nand_updatefdt=nand erase.part fdt; nand write ${fdtaddr} fdt ${filesize}nand_updatek=nand erase.part kernel; nand write ${kloadaddr} kernel ${filesize}net_nfs=run loadk loadfdt nfsargs addip addcons addmisc; dcache on; bootm ${kloadaddr} - ${fdtaddr}netdev=eth0netmask=255.255.255.0nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} rootdelay=2rootpath=/opt/nfsroot/diva/divelkserverip=192.168.0.13soc=am33xxspi_load_1st=tftp ${loadaddr} diva/MLO.byteswapspi_nfs=sf probe;sf read ${kloadaddr} 0x180000 0x600000; sf read ${fdtaddr} 0x140000 0x40000; run nfsargs addip addcons addmisc; dcache on; bootm ${kloadaddr} -}spi_update=sf probe 0:0; sf erase 0x40000 0x80000; sf write ${loadaddr} 0x40000 0x80000spi_update_1st=sf probe 0:0; sf erase 0x0 0x40000; sf write ${loadaddr} 0x0 0x40000spi_updatefdt=sf probe 0:0; sf erase 0x140000 0x40000; sf write ${fdtaddr} 0x140000 0x40000spi_updatek=sf probe 0:0; sf erase 0x180000 0x600000; sf write ${kloadaddr} 0x180000 0x600000stderr=serialstdin=serialstdout=serialusbnet_devaddr=c4:ed:ba:7f:c1:46vendor=davever=U-Boot 2013.10 (Sep 13 2014 - 10:43:18) [divelk-2.0.0] Environment size: 2786/262139 bytesDIVA#</pre> = DIVELK use cases = == DIVA Frequency Scaling == The frequency of the CPU can be changed on the run using the Cpufreq framework (please refer to the documentation included into the linux-am33x/Documentation/cpu-freq directory of the kernel source tree). The cpufreq framework works in conjunction with the related driver & governor. Cpufreq implementation controls the Linux OPP (Operating Performance Points) adjusting the Cortex-A8 core voltages and frequencies. CPUFreq is enabled by default in the DIVA kernel configuration. To view the available governors: <pre class="board-terminal">root@am335x-evm:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governorsconservative ondemand powersave userspace performanceroot@am335x-evm:~#</pre> To view the supported OPP's (frequency in KHz): <pre class="board-terminal">root@am335x-evm:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies275000 500000 600000 720000root@am335x-evm:~#</pre> To change the OPP: <pre class="board-terminal">root@am335x-evm:~# echo 275000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeedroot@am335x-evm:~#</pre> Please note that OPP can be changed only using the '''userspace''' governor. If governors like ondemand is used, OPP change happens automatically based on the system load. For further details, please refer to the [http://processors.wiki.ti.com/index.php/AM335x_Linux_Power_Management_User_Guide AM335x Linux Power Management User Guide]. == Forcing the kernel to use a limited amount of RAM == To evaluate the performances of the system with a specific amount of available RAM, the user can pass the ''mem'' parameter to the kernel, by setting the command line arguments in u-boot (for detailed instruction, please refer to the [[Change_Linux_Command_Line_Parameter_from_U-boot]] page). For example, to limit the amount of RAM to 128 MB, create the following variables in u-boot : <pre class="board-terminal">DIVA# setenv mem 128MBDIVA# setenv addmem 'setenv bootargs ${bootargs} mem=${mem}'</pre> And add the addmem variable to the boot macro: <pre class="board-terminal">DIVA# setenv net_nfs 'run loadk nfsargs addip addcons addmem; bootm ${buf}'</pre> For further details, please refer to the linux-am33x/Documentation/kernel-parameters.txt file of the kernel source tree provided with the DIVELK. == Using GPIOs from userspace == Please refer to the official documentation from the TI wiki: http://processors.wiki.ti.com/index.php/GPIO_Driver_Guide#User_Space_-_Sysfs_control ==Running QT applications == The root file system provided with the DIVELK (/home/dvdk/divelk/rfs/tisdk on the DVDK virtual machine) contains a pre-built version (4.8.0) of the QT libraries:

=dvdk@dvdk-vm:~/divelk/rfs/tisdk/usr/lib$ ll libQ*........lrwxrwxrwx 1 root root 19 Dec 17 2012 libQtCoreE.so.4 -> libQtCoreE.so.4.8.0*lrwxrwxrwx 1 root root 19 Dec 17 2012 libQtCoreE.so.4.8 -> libQtCoreE.so.4.8.0*-rwxr-xr-x 1 root root 3233396 Dec 16 2012 libQtCoreE.so.4.8.0*lrwxrwxrwx 1 root root 19 Dec 17 2012 libQtDBusE.so.4 -> libQtDBusE.so.4.8.0*lrwxrwxrwx 1 root root 19 Dec 17 2012 libQtDBusE.so.4.8 -> libQtDBusE.so.4.8.0*-rwxr-xr-x 1 root root 497236 Dec 16 2012 libQtDBusE.so.4.8.0*lrwxrwxrwx 1 root root 26 Dec 17 2012 libQtDeclarativeE.so.4 -> libQtDeclarativeE.so.4.8.0*lrwxrwxrwx 1 root root 26 Dec 17 2012 libQtDeclarativeE.so.4.8 -> libQtDeclarativeE.so.4.8.0*-rwxr-xr-x 1 root root 3850720 Dec 16 2012 libQtDeclarativeE.so.4.8.0*lrwxrwxrwx 1 root root 33 Dec 17 2012 libQtDesignerComponentsE.so.4 -> setenv setenv bootcmd $(flash_self)libQtDesignerComponentsE.so.4.8.0*=lrwxrwxrwx 1 root root 33 Dec 17 2012 libQtDesignerComponentsE.so.4.8 -> setenv serverip 192libQtDesignerComponentsE.168so.4.8.0*-rwxr-xr-x 1 root root 3012324 Dec 16 2012 libQtDesignerComponentsE.72 so.4.8.0*=lrwxrwxrwx 1 root root 23 Dec 17 2012 libQtDesignerE.so.4 -> saveenv libQtDesignerE.so.4.8.0*Saving Environment to NANDlrwxrwxrwx 1 root root 23 Dec 17 2012 libQtDesignerE.so.4. 8 -> libQtDesignerE.so.4.8.0*Erasing Nand-rwxr-xr-x 1 root root 5246140 Dec 16 2012 libQtDesignerE.so.4.8. 0*Erasing at 0x0 lrwxrwxrwx 1 root root 18 Dec 17 2012 libQtGuiE.so.4 -> libQtGuiE.so.4.8.0*lrwxrwxrwx 1 root root 18 Dec 17 2012 libQtGuiE.so.4.8 - 2490368% complete> libQtGuiE.so.4.8.0*-rwxr-xr-x 1 root root 9852452 Dec 16 2012 libQtGuiE.so.4.8. 0*Writing to Nandlrwxrwxrwx 1 root root 19 Dec 17 2012 libQtHelpE.so.4 -> libQtHelpE.so. done 4.8.0*=lrwxrwxrwx 1 root root 19 Dec 17 2012 libQtHelpE.so.4.8 ->libQtHelpE.so.4.8.0*-rwxr-xr-x 1 root root 523292 Dec 16 2012 libQtHelpE.so.4.8.0*.........dvdk@dvdk-vm:~/divelk/rfs/tisdk/usr/lib

The root file system also provides a lot of pre-built demos and examples (with the related source code and project files), contained in the following directories: * /home/dvdk/divelk/rfs/tisdk/usr/bin/qtopia/demos* /home/dvdk/divelk/rfs/tisdk/usr/bin/qtopia/examples The Matrix-Gui application (http://processors.wiki.ti.com/index.php/Matrix_Users_Guide) that launched automatically after DIVELK startup is based on QT and can directly show some demos (simply touching the QT icon). Moreover, additional examples can be launched, for example the "calculator" QML demo: <pre># stop the Matrix Gui application, in case it is running/etc/init.d/matrix-gui-2.0 stop# enter the demo application directorycd /usr/bin/qtopia/demos/declarative/calculator# launch the application./calculator -qws</pre> === Building a QT application === The following page describes how to build a simple application: http://processors.wiki.ti.com/index.php/Using_Qt_4.7#Creating_a_.22Hello_World.22_QtQuick_application === Opening/importing an example project from the DIVELK root file system ===  Qt Creator (http://qt-project.org/wiki/Category:Tools::QtCreator) can open/import the example projects provided with the DIVELK Updates root file system. The developer can explore the project to read and analyse the source code and configuration file and learn how the Qt libraries work: [[File:Qt-creator-import-example-from-rfs.png|800px|frameless|border]] === Resources === For additional information, please refer to the following pages:

* http://processors.wiki.ti.com/index.php/Category:Qt * http://processors.wiki.ti.com/index.php/Qt_Tips* http://processors.wiki.ti.com/index.php/Using_Qt_4.7* http://processors.wiki.ti.com/index.php/Building_Qt* http://qt-project.org/doc/* http://qt-project.org/doc/qt-5/gettingstarted.html* http://qt-project.org/doc/qt-5/qtexamplesandtutorials.html* http://qt-project.org/doc/qtcreator-3.1/creator-qml-application.html* http://qt-project.org/wiki/Category:HowTo* https://www.youtube.com/watch?v= Use cases 6KtOzh0StTc&list=PL2D1942A4688E9D63* https://www.youtube.com/watch?v=1ILvH24PYHg