Difference between revisions of "Diva Embedded Linux Kit (DIVELK)"

From DAVE Developer's Wiki
Jump to: navigation, search
(Release notes)
(Target setup and first boot)
 
(7 intermediate revisions by the same user not shown)
Line 79: Line 79:
 
|2.2.0
 
|2.2.0
 
|3.0.0
 
|3.0.0
|4.0.1
+
|4.0.2
 
|-
 
|-
 
|Status
 
|Status
Line 95: Line 95:
 
|October 2015
 
|October 2015
 
|June 2017
 
|June 2017
|March 2019
+
|May 2019
 
|-
 
|-
 
|'''Release notes'''
 
|'''Release notes'''
Line 103: Line 103:
 
|[[Diva_Embedded_Linux_Kit_(DIVELK)#DIVELK_2.2.0 | Ver 2.2.0]]
 
|[[Diva_Embedded_Linux_Kit_(DIVELK)#DIVELK_2.2.0 | Ver 2.2.0]]
 
|[[Diva_Embedded_Linux_Kit_(DIVELK)#DIVELK_3.0.0 | Ver 3.0.0]]
 
|[[Diva_Embedded_Linux_Kit_(DIVELK)#DIVELK_3.0.0 | Ver 3.0.0]]
|[[Diva_Embedded_Linux_Kit_(DIVELK)#DIVELK_4.0.1 | Ver 4.0.1]]
+
|[[Diva_Embedded_Linux_Kit_(DIVELK)#DIVELK_4.0.2 | Ver 4.0.2]]
 
|-
 
|-
 
|SOM PCB version
 
|SOM PCB version
Line 127: Line 127:
 
|2013.10-divelk-2.2.0
 
|2013.10-divelk-2.2.0
 
|2015.07-divelk-3.0.0  
 
|2015.07-divelk-3.0.0  
|2017.01-divelk-4.0.0
+
|2017.01-divelk-4.0.2
 
|-
 
|-
 
|Linux version
 
|Linux version
Line 135: Line 135:
 
|3.12.10-divelk-2.2.0
 
|3.12.10-divelk-2.2.0
 
|4.1.18-divelk-3.0.0(LTS)
 
|4.1.18-divelk-3.0.0(LTS)
|4.9.28-divelk-4.0.1(LTS)
+
|4.9.28-divelk-4.0.2(LTS)
 
|-  
 
|-  
 
|Drivers
 
|Drivers
Line 193: Line 193:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Image !! colspan="2" |DIVELK version 3.0.0||colspan="2" |DIVELK version 4.0.1
+
! Image !! colspan="2" |DIVELK version 3.0.0||colspan="2" |DIVELK version 4.0.2
 
|-
 
|-
 
| Platform || DIVELK || SBCD || DIVELK || SBCD  
 
| Platform || DIVELK || SBCD || DIVELK || SBCD  
Line 203: Line 203:
 
| Touchscreen || colspan="4" style="text-align: center" | resistive  
 
| Touchscreen || colspan="4" style="text-align: center" | resistive  
 
|-
 
|-
| bootscript || colspan="2" style="text-align: center" |[[mirror:diva/divelk-3.0.0/boot.scr|boot.scr]]||colspan="2" style="text-align: center" |[[mirror:diva/divelk-4.0.1/boot.scr|boot.scr]]
+
| bootscript || colspan="2" style="text-align: center" |[[mirror:diva/divelk-3.0.0/boot.scr|boot.scr]]||colspan="2" style="text-align: center" |[[mirror:diva/divelk-4.0.2/boot.scr|boot.scr]]
 
|-
 
|-
| U-Boot || colspan="2" style="text-align: center" |[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_MLO|u-boot (MLO)]]<br>[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_spiboot_MLO.byteswap|u-boot SPI (MLO)]]<br>[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_spiboot_u-boot.img|u-boot SPI]]<br>[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_nandboot_MLO|u-boot NAND (MLO)]]<br>[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_nandboot_u-boot.img|u-boot NAND]]<br>||colspan="2" style="text-align: center" |[[mirror:diva/divelk-4.0.0/divelk-4.0.0_diva_MLO|u-boot (MLO)]]<br>[[mirror:diva/divelk-4.0.0/divelk-4.0.0_diva_spiboot_MLO.byteswap|u-boot SPI (MLO)]]<br>[[mirror:diva/divelk-4.0.0/divelk-4.0.0_diva_spiboot_u-boot.img|u-boot SPI]]<br>[[mirror:diva/divelk-4.0.0/divelk-4.0.0_diva_nandboot_MLO|u-boot NAND (MLO)]]<br>[[mirror:diva/divelk-4.0.0/divelk-4.0.0_diva_nandboot_u-boot.img|u-boot NAND]]<br>
+
| U-Boot || colspan="2" style="text-align: center" |[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_MLO|u-boot (MLO)]]<br>[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_spiboot_MLO.byteswap|u-boot SPI (MLO)]]<br>[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_spiboot_u-boot.img|u-boot SPI]]<br>[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_nandboot_MLO|u-boot NAND (MLO)]]<br>[[mirror:diva/divelk-3.0.0/divelk-3.0.0_diva_nandboot_u-boot.img|u-boot NAND]]<br>||colspan="2" style="text-align: center" |[[mirror:diva/divelk-4.0.2/divelk-4.0.2_diva_MLO|u-boot (MLO)]]<br>[[mirror:diva/divelk-4.0.2/divelk-4.0.2_diva_spiboot_MLO.byteswap|u-boot SPI (MLO)]]<br>[[mirror:diva/divelk-4.0.2/divelk-4.0.2_diva_spiboot_u-boot.img|u-boot SPI]]<br>[[mirror:diva/divelk-4.0.2/divelk-4.0.2_diva_nandboot_MLO|u-boot NAND (MLO)]]<br>[[mirror:diva/divelk-4.0.2/divelk-4.0.2_diva_nandboot_u-boot.img|u-boot NAND]]<br>
 
|-
 
|-
| Linux kernel || colspan="2" style="text-align: center" |[[mirror:diva/divelk-3.0.0/divelk-3.0.0_uImage|uImage]]|| colspan="2" style="text-align: center" |[[mirror:diva/divelk-4.0.1/divelk-4.0.1_uImage|uImage]]
+
| Linux kernel || colspan="2" style="text-align: center" |[[mirror:diva/divelk-3.0.0/divelk-3.0.0_uImage|uImage]]|| colspan="2" style="text-align: center" |[[mirror:diva/divelk-4.0.2/divelk-4.0.2_uImage|uImage]]
 
|-
 
|-
| kernel modules || colspan="2" style="text-align: center" |[[mirror:diva/divelk-3.0.0/divelk-3.0.0_modules.tar.gz|modules]]|| colspan="2" style="text-align: center" |[[mirror:diva/divelk-4.0.1/divelk-4.0.1_modules.tar.gz|modules]]
+
| kernel modules || colspan="2" style="text-align: center" |[[mirror:diva/divelk-3.0.0/divelk-3.0.0_modules.tar.gz|modules]]|| colspan="2" style="text-align: center" |[[mirror:diva/divelk-4.0.2/divelk-4.0.2_modules.tar.gz|modules]]
 
|-
 
|-
| Device tree  || [[mirror:diva/divelk-3.0.0/divelk-3.0.0_am335x-divelk.dtb|am335x-divelk.dtb]] || [[mirror:diva/divelk-3.0.0/divelk-3.0.0_am335x-sbcd.dtb|am335x-sbcd.dtb]]|| [[mirror:diva/divelk-4.0.1/divelk-4.0.1_am335x-divelk.dtb|am335x-divelk.dtb]] || [[mirror:diva/divelk-4.0.1/divelk-4.0.1_am335x-sbcd.dtb|am335x-sbcd.dtb]]
+
| Device tree  || [[mirror:diva/divelk-3.0.0/divelk-3.0.0_am335x-divelk.dtb|am335x-divelk.dtb]] || [[mirror:diva/divelk-3.0.0/divelk-3.0.0_am335x-sbcd.dtb|am335x-sbcd.dtb]]|| [[mirror:diva/divelk-4.0.2/divelk-4.0.2_am335x-divelk.dtb|am335x-divelk.dtb]] || [[mirror:diva/divelk-4.0.2/divelk-4.0.2_am335x-sbcd.dtb|am335x-sbcd.dtb]]
 
|}
 
|}
  
Line 366: Line 366:
 
{{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 [[Diva_Embedded_Linux_Kit_(DIVELK)#Release_notes|Release notes]] for further information.}}
 
{{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 [[Diva_Embedded_Linux_Kit_(DIVELK)#Release_notes|Release notes]] for further information.}}
  
{{ImportantMessage|text='''N.B.''' '''Customers who want to update from DIVELK 2.x.x to DIVELK 3.0.0 or DIVELK 4.0.0 must install new DIVELK VM'''.}}
+
{{ImportantMessage|text='''N.B.''' '''Customers who want to update from DIVELK 2.x.x to DIVELK 3.0.0 or DIVELK 4.0.x must install new DIVELK VM'''.}}
  
 
== Release notes ==
 
== Release notes ==
=== DIVELK 4.0.1 ===
+
=== DIVELK 4.0.2 ===
  
* Release date: March 2019
+
* Release date: May 2019
 
* Status: Released
 
* Status: Released
 
* Processor SDK version: 04.00.00
 
* Processor SDK version: 04.00.00
 
* Supported carrier boards: DIVAEVB-Lite, Dacu, SBC-DIVA
 
* Supported carrier boards: DIVAEVB-Lite, Dacu, SBC-DIVA
 +
** added support for NOR ISSI SPI
  
 
==== Notes ====
 
==== Notes ====
Line 671: Line 672:
 
[[File:DIVELK-NOR.png|thumb|center|400px|NOR flash default partitioning]]
 
[[File:DIVELK-NOR.png|thumb|center|400px|NOR flash default partitioning]]
  
 +
 +
{{ImportantMessage|text=The DIVELK bootable microSD card delivered along with the kit is set up to do a full bootstrap sequence. For more details, please refer to [[Working_with_the_Yocto_build_system#bootscript|this section]].}}
  
 
By default, U-Boot is configured to retrieve Linux kernel image stored in the microSD card [1]. In turn, Linux kernel shall mount root file system from the <code>mmcblk0p2</code> partition of the [[#DIVELK microSD Layout|microSD card itself]]. At the end of boot process, Linux shell shall be available on the serial console.
 
By default, U-Boot is configured to retrieve Linux kernel image stored in the microSD card [1]. In turn, Linux kernel shall mount root file system from the <code>mmcblk0p2</code> partition of the [[#DIVELK microSD Layout|microSD card itself]]. At the end of boot process, Linux shell shall be available on the serial console.
Line 1,239: Line 1,242:
  
 
===Target configuration for the development stage (<code>net_nfs</code>)===
 
===Target configuration for the development stage (<code>net_nfs</code>)===
 +
 +
{{ImportantMessage|text=The default DIVELK Virtual Machine network configuration is using NAT: this allows to accessing external network (i.e. Internet) using the host computer's networking connection.
 +
For software development using <code>net_nfs</code> with tftp/nfs protocols, please configure your VM network interface in ''Bridge mode'' (see below)}}
 +
 
During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:
 
During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:
 
*retrieve binary images (i.e. Linux kernel) via TFTP protocol
 
*retrieve binary images (i.e. Linux kernel) via TFTP protocol
*mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted [[Deploying_Embedded_Linux_Systems#The_development_environment|here]].
+
*mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted [[Deploying_Embedded_Linux_Systems#The_development_environment|here]]. An example of ''Bridge mode'' configuration for DIVELK can be found [[Booting_the_system_via_NFS_(DIVELK) | here]]
 
In DAVE Embedded Systems development kits, this configuration is generally denoted as <code>net_nfs</code>. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up. They are detailed [[Booting_Linux_Kernel#Configuration_net_nfs|here]].
 
In DAVE Embedded Systems development kits, this configuration is generally denoted as <code>net_nfs</code>. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up. They are detailed [[Booting_Linux_Kernel#Configuration_net_nfs|here]].
  
 
For more details about TFTP and NFS servers on host side, please refer to this [[Setting_up_tftp_and_nfs|page]].
 
For more details about TFTP and NFS servers on host side, please refer to this [[Setting_up_tftp_and_nfs|page]].
 +
 
===Target configuration for standalone boot===
 
===Target configuration for standalone boot===
 
Please refer to [[Standalone_boot_(DIVELK)|this page]].
 
Please refer to [[Standalone_boot_(DIVELK)|this page]].

Latest revision as of 10:25, 4 September 2019

Info Box
Dacu-top-view.png Applies to Dacu
Diva-am335x-overview.png Applies to Diva

Introduction[edit | edit source]

Divelk 01.png

Diva Embedded Linux Kit (DIVELK 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 Diva-based systems
  • build Linux applications that will run on the target.

The main kit components are:

  • hardware platform composed by Diva system-on-module (SOM for short) and carrier board. Supported carrier boards are:
    • DivaEVB-Lite standalone
    • DivaEVB-Lite plugged on Dacu carrier board
  • Development virtual machine containing:
    • Toolchain
    • U-Boot bootloader sources
    • Linux kernel sources
    • Build system
    • Pre-built 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 Diva hardware characteristics, please refer to the Diva Hardware Manual. An account for the reserved area of DAVE Embedded Systems website is required to access the kit contents.

Kit Contents[edit | edit source]

Component Description Notes
Diva-400.png Diva SOM
CPU: TI AM3359
SDRAM: 512 MB DDR3
NOR: bootable SPI flash 32 MB
NAND: 1GB
Please refer to Diva Hardware Manual
Divaevb-divelk 01.png Diva-EVB-Lite Carrier board Please refer to DivaEVB-Lite page
Dacu-top-view.png Dacu Carrier board Please refer to Dacu page
Display.jpg Ampire AM-800480STMQW
7” 800x480 LCD display
LVDS interface
Please refer to First boot
Alimentatore.jpg AC/DC Single Output Wall Mount adapter
Output: +12V – 2.0 A
Please refer to First boot
Cavetto-seriale2.jpg DB9 Male Serial port adapter Please refer to First boot
ProdSDC-MBLY-thumb.png MicroSDHC card with SD adapter and USB adapter Please refer to First boot

DIVELK software components[edit | edit source]

DAVE Embedded Systems adds to the latest AMSDK from Texas Instruments the customization required to support the 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.

The following table shows how DIVELK releases are related to AMSDK or Processor SDK releases.

DIVELK version
Release number 1.0.0 2.0.0 2.1.0 2.2.0 3.0.0 4.0.2
Status Released Released Released Released Released Released
Release date June 2013 October 2014 June 2015 October 2015 June 2017 May 2019
Release notes Ver 1.0.0 Ver 2.0.0 Ver 2.1.0 Ver 2.2.0 Ver 3.0.0 Ver 4.0.2
SOM PCB version CS133012A CS133012C CS133012C CS133012C CS133012C CS133012C
Supported carrier boards DivaEVB-Lite
Dacu
DivaEVB-Lite
Dacu
DivaEVB-Lite
Dacu
DivaEVB-Lite
Dacu
SBC-DIVA
DivaEVB-Lite
Dacu
SBC-DIVA
DivaEVB-Lite
Dacu
SBC-DIVA
U-Boot version 2012.10-divelk-1.0.0 2013.10-divelk-2.0.0 2013.10-divelk-2.1.0 2013.10-divelk-2.2.0 2015.07-divelk-3.0.0 2017.01-divelk-4.0.2
Linux version 3.2.0-divelk-1.0.0 3.12.10-divelk-2.0.0 3.12.10-divelk-2.1.0 3.12.10-divelk-2.2.0 4.1.18-divelk-3.0.0(LTS) 4.9.28-divelk-4.0.2(LTS)
Drivers SPI NOR Flash (boot)
NAND 8 bit (boot)
UART0 (2-wire)
USB Host
SD/MMC1
GPIO
LCD
Touch screen controller
EMAC0 RMII (Fast Ethernet)
PMIC RTC (battery powered)

Audio (ALSA)

SPI NOR Flash (boot)
NAND 8 bit (boot)
UART0 (2-wire)
USB Host
SD/MMC1
GPIO
LCD
Touch screen controller
EMAC0 RMII (Fast Ethernet)
PMIC RTC (battery powered)

Audio (ALSA)
USB OTG
CAN (*)
ADC

SPI NOR Flash (boot)
NAND 8 bit (boot)
UART0 (2-wire)
USB Host
SD/MMC1
GPIO
LCD
Touch screen controller
EMAC0 RMII (Fast Ethernet)
PMIC RTC (battery powered)

Audio (ALSA)
USB OTG
CAN (*)
ADC
Splash screen in u-boot
ConfigID

SPI NOR Flash (boot)
NAND 8 bit (boot)
UART0 (2-wire)
USB Host
SD/MMC1
GPIO
LCD
Touch screen controller
EMAC0 RMII (Fast Ethernet)
PMIC RTC (battery powered)

Audio (ALSA)
USB OTG
CAN (*)
ADC
Splash screen in u-boot
ConfigID

SPI NOR Flash (boot)
NAND 8 bit (boot)
UART0 (2-wire)
USB Host
SD/MMC1
GPIO
LCD
Touch screen controller
EMAC0 RMII (Fast Ethernet)
PMIC RTC (battery powered)

Audio (ALSA)
USB OTG
CAN (*)
ADC
Splash screen in u-boot
ConfigID

SPI NOR Flash (boot)
NAND 8 bit (boot)
UART0 (2-wire)
USB Host
SD/MMC1
GPIO
LCD
Touch screen controller
EMAC0 RMII (Fast Ethernet)
PMIC RTC (battery powered)

Audio (ALSA)
USB OTG
CAN (*)
ADC
Splash screen in u-boot
ConfigID

TI AMSDK 05.06.00.00 AMSDK 07.00.00.00 AMSDK 07.00.00.00 AMSDK 07.00.00.00 Processor SDK 02.00.02 Processor SDK 04.00.00
Build System - Yocto Dylan (1.4) Yocto Dylan (1.4) Yocto Dylan (1.4) Yocto Fido (1.8) Yocto Morty (2.2)
Graphic libraries Qt 4.8.4 Qt 4.8.4
Qt 5.x
Qt 4.8.4
Qt 5.3
Qt 4.8.4
Qt 5.3
Qt 5.5 Qt 5.7.1

(*) CAN support is limited to CAN driver and dtb configuration: ONLY SBCD Eval Kit has CAN PHY installed on board. DIVELK Evaluation Kit has to be properly hardware modified for providing Physical access to external CAN bus interface

Downloadable binary images[edit | edit source]

All binary images for DIVELK are hosted on 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:


200px-Emblem-important.svg.png

In order to boot Linux from SD card files, the binary files must be renamed as follows: U-boot 1st stage MLO

U-boot file u-boot.img

Image DIVELK version 3.0.0 DIVELK version 4.0.2
Platform DIVELK SBCD DIVELK SBCD
Carrier Board ConfigID 0001 0002 0001 0002
LCD panel Ampire 800 x 480 7" LVDS 262K colors (RGB666)
Touchscreen resistive
bootscript boot.scr boot.scr
U-Boot u-boot (MLO)
u-boot SPI (MLO)
u-boot SPI
u-boot NAND (MLO)
u-boot NAND
u-boot (MLO)
u-boot SPI (MLO)
u-boot SPI
u-boot NAND (MLO)
u-boot NAND
Linux kernel uImage uImage
kernel modules modules modules
Device tree am335x-divelk.dtb am335x-sbcd.dtb am335x-divelk.dtb am335x-sbcd.dtb

DIVELK microSD Layout[edit | edit source]

The microSD card provided with DIVELK is partitioned as shown in the following image:


microSD card partitioning

Most of storage space is occupied by two partitions:

  • a FAT32 partition (mmcblk0p1) containing:
    • U-Boot bootscript
    • Linux kernel and DTB binary images
    • DIVELK virtual machine image in OFV format (MVM basic version)
    • 7-zip Windows executable file
  • an ext3 partition (mmcblk0p2) containing the root file system for the target.

bootscript and root file system are used to boot the target as described in this section.

It is worth remembering that the microSD card is bootable, because U-Boot image files (MLO and u-boot.img) and kernel image (uImage) are present into first FAT32 partition: filename MUST be the one written before.

However, even if U-Boot is run from the microSD card, the environment is retrieved from NOR flash.

How to create a bootable microSD card[edit | edit source]

For creating a bootable microSD card, simply follows the following steps:

  • create two partition: first partition FAT32 and a second partition ext3
  • mark as "bootable" the first partition (using for example gparted on VM)
  • copy MLO, u-boot.img and boot.scr on FAT32 partition
    • copy kernel and dtb on the same partition
    • all files can be retrieved from here
  • extract rfs on ext3 partition

Alternatively, it is also possible to create a bootable sd using this script:

#!/bin/bash

if [[ -z $1 || -z $2 || -z $3 ]]
then
    echo "$0 Usage:"
    echo "  $0 <device> <binaries directory> <rootfs tar.bz2>"
    echo "  Example: $0 /dev/sdc binaries/ rootfs.tar.bz2"
    exit
fi

if [ "$(whoami)" != "root" ]
then
    echo "you must be root to run this script!"
    exit
fi

if ! [[ -b $1 ]]
then
    echo "$1 is not a valid block device!"
    exit
fi

if ! [[ -d $2 ]]
then
    echo "Incorrect Binaries location!"
    exit
fi

if ! [[ -f $3 ]]
then
    echo "Incorrect rootfs location!"
    exit
fi

DRIVE=$1
if [[ "$DRIVE" == *"mmcblk"* ]]
then
    echo "You're using a mmc device, I need to fix partition names"
    PART="p"
else
    PART=""
fi
BINARIES=$2
RFS=$3

echo "All data on "$DRIVE" now will be destroyed! Continue? [y/n]"
read ans
if ! [ $ans == 'y' ]
then
    exit
fi

echo "[Partitioning $1...]"

dd if=/dev/zero of=$DRIVE bs=1024 count=1024

SIZE=`fdisk -l $DRIVE | grep Disk | awk '{print $5}'`

echo DISK SIZE - $SIZE bytes

CYLINDERS=`echo $SIZE/255/63/512 | bc`

# check if we're running an old (e.g. 2.20.x) or new (e.g. 2.24.x) sfdisk
sfdisk --help | grep -- -H

if [ "$?" -eq "0" ]
then
    {
        echo 10,1380,0x0c,*
        echo 1390,,83,-
    } | sfdisk -D -H 255 -S 63 -C $CYLINDERS $DRIVE
else
{
    echo 10,4086M,0x0c,*
    echo 4096M,,83,-
} | sfdisk $DRIVE
fi

partprobe


echo "[Making filesystems...]"
mkfs.vfat -F 32 -n BOOT "$DRIVE$PART"1 #> /dev/null
mkfs.ext3 -L ROOTFS "$DRIVE$PART"2 #> /dev/null

echo "[Copying files...]"

binaries_dir=${BINARIES%/}
mount "$DRIVE$PART"1 /mnt
cp -av --no-preserve=ownership $binaries_dir/* /mnt/
umount "$DRIVE$PART"1

echo "[Extracting rfs (this may take a while...)]"
mount "$DRIVE$PART"2 /mnt
tar jxf $RFS -C /mnt > /dev/null
chmod 755 /mnt
umount "$DRIVE$PART"2

echo "[Done]"

To use this script, simply copy its content to a mksd.sh file.

Then, run:

chmod a+x mksd.sh

to give executable permissions to the file.

Once this has been done, insert a 16gb microsd card and run:

./mksd /dev/sdX binaries-folder rootfs.tar.bz2

The script will partition the sd card and copy the binaries and rootfs to the correct partition on the sd card. The operation will take few minutes.

DIVELK Updates[edit | edit source]

200px-Emblem-important.svg.png

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 support-diva@dave.eu. Please refer to Release notes for further information.


200px-Emblem-important.svg.png

N.B. Customers who want to update from DIVELK 2.x.x to DIVELK 3.0.0 or DIVELK 4.0.x must install new DIVELK VM.

Release notes[edit | edit source]

DIVELK 4.0.2[edit | edit source]

  • Release date: May 2019
  • Status: Released
  • Processor SDK version: 04.00.00
  • Supported carrier boards: DIVAEVB-Lite, Dacu, SBC-DIVA
    • added support for NOR ISSI SPI

Notes[edit | edit source]

  • Fix of manual reset for the gigabit ethernet phy eht1 for SBCD boards.

Known limitations[edit | edit source]

Issue # Component Subsystem Description
0001 Linux USB USB0, when configured as OTG, requires loading of the gadget module for detecting devices (and entering host mode)
0002 Linux Audio Codec on the DACU board does not supported anymore.


DIVELK 3.0.0[edit | edit source]

  • Release date: June 2017
  • Status: Released
  • Processor SDK version: 02.00.02
  • Supported carrier boards: DIVAEVB-Lite, Dacu, SBC-DIVA

Notes[edit | edit source]

  • Major update release to TI Processor SDK
  • Updated kernel and u-boot according to TI Processor SDK
  • Qt 5.5 support on top of Weston
  • DIVELK Virtual Machine with updated cross-toolchain (MVM generated)

Known limitations[edit | edit source]

Issue # Component Subsystem Description
0001 Linux USB USB0, when configured as OTG, requires loading of the gadget module for detecting devices (and entering host mode)
0002 Linux Audio Codec on the DACU board does not supported anymore.
0003 MVM Toolchain Support for C++ application cross-building failure
C++ cross-building patch[edit | edit source]

For issue 003, please apply the following patch:

cd diva/sdk/divelk-3.0.0
wget https://mirror.dave.eu/diva/divelk-3.0.0/update/environment-setup.patch
patch < environment-setup.patch

The output should be something like:

dvdk@vagrant-ubuntu-trusty-64:~$ cd diva/sdk/divelk-3.0.0
dvdk@vagrant-ubuntu-trusty-64:~/diva/sdk/divelk-3.0.0$ wget https://mirror.dave.eu/diva/divelk-3.0.0/update/environment-setup.patch
--2018-12-18 08:37:49--  https://mirror.dave.eu/diva/divelk-3.0.0/update/environment-setup.patch
Resolving mirror.dave.eu (mirror.dave.eu)... 79.143.179.155
Connecting to mirror.dave.eu (mirror.dave.eu)|79.143.179.155|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1225 (1.2K) [text/x-diff]
Saving to: ‘environment-setup.patch’

100%[======================================>] 1,225       --.-K/s   in 0s

2018-12-18 08:37:49 (64.4 MB/s) - ‘environment-setup.patch’ saved [1225/1225]

dvdk@vagrant-ubuntu-trusty-64:~/diva/sdk/divelk-3.0.0$ patch < environment-setup.patch
patching file environment-setup-cortexa8hf-vfp-neon-linux-gnueabi 
dvdk@vagrant-ubuntu-trusty-64:~/diva/sdk/divelk-3.0.0$ 

DIVELK older releases[edit | edit source]

For DIVELK older releases information, please click on Expand here below (on the right)

N.B. Customers who want to update from DIVELK 1.0.0 to DIVELK 2.x.x can send an email to support-diva@dave.eu.

DIVELK 2.2.0[edit | edit source]

  • Release date: October 2015
  • Status: Released
  • AMSDK version: 07.00.00.00
  • Supported carrier boards: DIVAEVB-Lite, Dacu, SBC-DIVA

Notes[edit | edit source]

200px-Emblem-important.svg.png

It's highly recommended to read the ConfigID_and_UniqueID page.

  • Maintenance release
  • Bug fixes
  • Added support for SBC-DIVA
  • Updated kernel and u-boot versions

Known limitations[edit | edit source]

Issue # Component Subsystem Description
0001 Linux USB USB0, when configured as OTG, requires loading of the gadget module for detecting devices (and entering host mode)
0002 Yocto ADT The Yocto ADT plugin for Eclipse doesn't work
0003 Linux Audio Codec on the DACU board doesn't work out-of-the-box. A software patch is required, please contact support-diva@dave.eu for information on how to enable the audio codec.

DIVELK 2.1.0[edit | edit source]

  • Release date: June 2015
  • Status: Released
  • AMSDK version: 07.00.00.00
  • Supported carrier boards: DIVAEVB-Lite, Dacu

Notes[edit | edit source]

200px-Emblem-important.svg.png

It's highly recommended to read the ConfigID_and_UniqueID page.

  • Maintenance release
  • Updated kernel and u-boot versions
  • Bug fixes

Known limitations[edit | edit source]

Issue # Component Subsystem Description
0001 Linux USB USB0, when configured as OTG, requires loading of the gadget module for detecting devices (and entering host mode)
0002 Yocto ADT The Yocto ADT plugin for Eclipse doesn't work
0003 Linux Audio Codec on the DACU board doesn't work out-of-the-box. A software patch is required, please contact support-diva@dave.eu for information on how to enable the audio codec.

DIVELK 2.0.0[edit | edit source]

  • Release date: October 2014
  • Status: Released
  • AMSDK version: 07.00.00.00
  • Supported carrier boards: DIVAEVB-Lite, Dacu

Notes[edit | edit source]

  • First major update
  • Added Yocto support
  • Updated kernel and u-boot versions
  • Bug fixes

Known limitations[edit | edit source]

Issue # Component Subsystem Description
0001 Linux USB USB0, when configured as OTG, requires loading of the gadget module for detecting devices (and entering host mode)
0002 Yocto ADT The Yocto ADT plugin for Eclipse doesn't work

DIVELK 1.0.0[edit | edit source]

  • Release date: June 2013
  • Status: released
  • AMSDK version: 05.06.00.00
  • Supported carrier boards: DIVAEVB-Lite, Dacu

Notes[edit | edit source]

  • First official release

Quick start guide[edit | edit source]

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

DIVA SOM[edit | edit source]

Diva-400.png

The heart of DIVA SOM is Texas Instruments "Sitara". From a software point of view, Texas Instruments supports this processor family through so-called Processor Software Development Kit (Processo SDK for short). Processor SDK releases are published on a regular basis. For more details please refer to:

DIVA Embedded Linux Kit, in turn, is directly derived from Processor SDK. Hence DIVELK documentation often refers to this resource.

Carrier boards[edit | edit source]

DIVAEVB-Lite[edit | edit source]

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

Diva-evb-with-som.png

For further information on the DIVAEVB-Lite, please refer to DivaEVB-Lite

The following figure shows the carrier board block diagram:

Divaevb-bd.png

Dacu[edit | edit source]

DIVAEVB-Lite can be plugged on the Dacu carrier board to extend the set of available interfaces.

Diva divaevb dacu.png

For further information on Dacu, please refer to:

The following figure shows the carrier board block diagram:

Dacu-diva-block diagram.png

Kit registration[edit | edit source]

200px-Emblem-important.svg.png

Customers are strongly recommended to register their kits. Registration grants access to reserved material such as source code and additional documentation.

Please register your development kit by sending an email to support-diva@dave.eu, providing the kit P/N and CODE.

Target setup and first boot[edit | edit source]

This section describes how to quick start DIVA board delivered along with DIVELK kit:

  • connect the DB9 serial cable adapter to J25 pin-strip connector on DACU as shown on picture below
  • insert microSD card in the DACU slot J34
  • optionally connect the system to Ethernet LAN by plugging cable into connector J7
  • 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 provided 12V power supply to JP2 DACU connector


Target setup for first boot


Once power has been applied to the target, U-Boot bootloader will be fetched from the SPI NOR flash and executed. Boot messages will be printed out to the serial console. Redundant U-Boot environment is stored in the NOR flash as well, as depicted in the following image.


NOR flash default partitioning


200px-Emblem-important.svg.png

The DIVELK bootable microSD card delivered along with the kit is set up to do a full bootstrap sequence. For more details, please refer to this section.

By default, U-Boot is configured to retrieve Linux kernel image stored in the microSD card [1]. In turn, Linux kernel shall mount root file system from the mmcblk0p2 partition of the microSD card itself. At the end of boot process, Linux shell shall be available on the serial console.

The following dump shows the typical messages printed out to the console during bootstrap process.

U-Boot SPL 2015.07-divelk-3.0.0 (May 31 2017 - 10:13:07)
WARNING: ConfigID on block 3 is UNLOCKED
reading u-boot.img
reading u-boot.img


U-Boot 2015.07-divelk-3.0.0 (May 31 2017 - 10:13:07 +0200)

AM335X-GP rev 2.1 800 MHz
I2C:   ready
DRAM:  512 MiB
NAND:  1024 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB
CB ConfigID CRC mismatch for 0x00000000 (was 0x00000000, expected 0x2144df1c) at block 3 (offset 96): using default
Display: AM800480STMQW_TA1 (800x480)
SF: Detected S25FL256S_64K with page size 256 Bytes, erase size 64 KiB, total 32 MiB
device 0 offset 0x780000, size 0x119436
SF: 1152054 bytes @ 0x780000 Read: OK
WARNING: ConfigID on block 3 is UNLOCKED
SOM ConfigID#: 00000001
SOM UniqueID#: 0000c661:1c0bc968
CB ConfigID CRC mismatch for 0x00000000 (was 0x00000000, expected 0x2144df1c) at block 3 (offset 96): using default
CB ConfigID#: ffffffff
CB UniqueID#: 00000000:00000000
Net:   cpsw, usb_ether
Hit any key to stop autoboot:  0
starting USB...
USB0:   Port not available.
USB is stopped. Please issue 'usb start' first.
** Bad device usb 0 **
switch to partitions #0, OK
mmc0 is current device
reading boot.scr
787 bytes read in 4 ms (191.4 KiB/s)
Running bootscript from mmc ...
## Executing script at 80200000
bootscript generated with command "mkimage -A ARM -T script -C none -n DIVA -d bootscript.txt boot.scr"
Booting DIVELK via mmcboot with divelk-3.0.0_am335x-divelk.dtb as device tree
reading divelk-3.0.0_uImage
4148488 bytes read in 243 ms (16.3 MiB/s)
reading divelk-3.0.0_am335x-divelk.dtb
39558 bytes read in 9 ms (4.2 MiB/s)
FDT: override 'som_uniqueid' with '0000c661:1c0bc968'
FDT: override 'cb_uniqueid' with '00000000:00000000'
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-4.1.18-divelk-3.0.0-gdc012
   Created:      2017-05-30  21:54:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4148424 Bytes = 4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   XIP Kernel Image ... OK
   reserving fdt memory region: addr=80f80000 size=a000
   Using Device Tree in place at 80f80000, end 80f8cfff
WARNING: could not find splashscreen reserved memory path

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.1.18-divelk-3.0.0-gdc0123a (jenkins@trustybakery) (gcc version 4.9.3 20150413 (prerelease) (Linaro GCC 4.9-2015.05) ) #1 PREEMPT Tue May 30 23:53:41 CEST 2017
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: DAVE Embedded System DIVELK
[    0.000000] cma: Reserved 24 MiB at 0x9e800000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] On node 0 totalpages: 131072
[    0.000000] free_area_init_node: node 0, pgdat c0b4453c, node_mem_map de36d000
[    0.000000]   Normal zone: 1152 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 131072 pages, LIFO batch:31
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM335X ES2.1 (sgx neon )
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129920
[    0.000000] Kernel command line: root=/dev/mmcblk0p2 rw rootdelay=2 console=ttyS0,115200n8 earlyprintk no_console_suspend loglevel=8 mtdparts=8000000.nand:128k(NAND.SPL),128k(NAND.SPL.backup1),128k(NAND.SPL.backup2),128k(NAND.SPL.backup3),1920k(NAND.u-boot),128k(NAND.u-boot-env),128k(NAND.u-boot-env.backup1),128k(NAND.fdt),6m(NAND.kernel),4m(NAND.splash),-(NAND.file-system);spi1.0:256k(MLO),512k(u-boot),256k(env1),256k(env2),256k(fdt),6m(kernel),4m(splash),-(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: 482636K/524288K available (8111K kernel code, 321K rwdata, 2800K rodata, 276K init, 253K bss, 17076K reserved, 24576K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 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 - 0xc0ab005c   (10913 kB)
[    0.000000]       .init : 0xc0ab1000 - 0xc0af6000   ( 276 kB)
[    0.000000]       .data : 0xc0af6000 - 0xc0b46670   ( 322 kB)
[    0.000000]        .bss : 0xc0b49000 - 0xc0b88638   ( 254 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Additional per-CPU info printed with stalls.
[    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] OMAP clockevent source: timer2 at 24000000 Hz
[    0.000015] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000037] clocksource timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000049] OMAP clocksource: timer1 at 24000000 Hz
[    0.000243] Console: colour dummy device 80x30
[    0.000283] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[    0.088988] pid_max: default: 32768 minimum: 301
[    0.089106] Security Framework initialized
[    0.089162] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.089173] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.089891] Initializing cgroup subsys blkio
[    0.089922] Initializing cgroup subsys memory
[    0.089967] Initializing cgroup subsys devices
[    0.089983] Initializing cgroup subsys freezer
[    0.089999] Initializing cgroup subsys perf_event
[    0.090027] CPU: Testing write buffer coherency: ok
[    0.090445] Setting up static identity map for 0x80008200 - 0x80008270
[    0.092148] devtmpfs: initialized
[    0.104305] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.120351] omap_hwmod: debugss: _wait_target_disable failed
[    0.175690] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.178078] pinctrl core: initialized pinctrl subsystem
[    0.179590] NET: Registered protocol family 16
[    0.182090] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.208983] cpuidle: using governor ladder
[    0.238973] cpuidle: using governor menu
[    0.243773] OMAP GPIO hardware version 0.1
[    0.252215] omap-gpmc 50000000.gpmc: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/nandflash_pins_default, deferring probe
[    0.254899] No ATAGs?
[    0.254928] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.299641] edma 49000000.edma: TI EDMA DMA engine driver
[    0.303407] vgaarb: loaded
[    0.304037] SCSI subsystem initialized
[    0.304344] libata version 3.00 loaded.
[    0.304718] usbcore: registered new interface driver usbfs
[    0.304801] usbcore: registered new interface driver hub
[    0.304897] usbcore: registered new device driver usb
[    0.305537] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring probe
[    0.305694] media: Linux media interface: v0.10
[    0.305771] Linux video capture interface: v2.00
[    0.305823] pps_core: LinuxPPS API ver. 1 registered
[    0.305830] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.305861] PTP clock support registered
[    0.306777] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400
[    0.307046] Advanced Linux Sound Architecture Driver Initialized.
[    0.307759] Bluetooth: Core ver 2.20
[    0.307836] NET: Registered protocol family 31
[    0.307845] Bluetooth: HCI device and connection manager initialized
[    0.307862] Bluetooth: HCI socket layer initialized
[    0.307874] Bluetooth: L2CAP socket layer initialized
[    0.307910] Bluetooth: SCO socket layer initialized
[    0.308320] cfg80211: Calling CRDA to update world regulatory domain
[    0.308944] Switched to clocksource timer1
[    0.320226] NET: Registered protocol family 2
[    0.321119] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.321172] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.321219] TCP: Hash tables configured (established 4096 bind 4096)
[    0.321302] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.321322] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.321497] NET: Registered protocol family 1
[    0.321905] RPC: Registered named UNIX socket transport module.
[    0.321919] RPC: Registered udp transport module.
[    0.321925] RPC: Registered tcp transport module.
[    0.321932] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.321958] PCI: CLS 0 bytes, default 64
[    0.323047] CPU PMU: Failed to parse /pmu/interrupt-affinity[0]
[    0.323101] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
[    0.325328] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.325428] audit: initializing netlink subsys (disabled)
[    0.325506] audit: type=2000 audit(0.300:1): initialized
[    0.333485] VFS: Disk quotas dquot_6.6.0
[    0.333723] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.335976] NFS: Registering the id_resolver key type
[    0.336064] Key type id_resolver registered
[    0.336072] Key type id_legacy registered
[    0.336151] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.339892] NET: Registered protocol family 38
[    0.339977] io scheduler noop registered
[    0.339993] io scheduler deadline registered
[    0.340060] io scheduler cfq registered (default)
[    0.341385] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.343807] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[    0.345031] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled
[    0.348866] console [ttyS0] disabled
[    0.349130] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158, base_baud = 3000000) is a 8250
[    1.098594] console [ttyS0] enabled
[    1.103968] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20
[    1.110848] [drm] Initialized drm 1.1.0 20060810
[    1.115911] panel panel: pins are not configured
[    1.122127] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.128781] [drm] No driver support for vblank timestamp query.
[    1.143320] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000020): FIFO underfow
[    1.148142] Console: switching to colour frame buffer device 100x30
[    1.160878] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000104): Sync lost
[    1.174180] tilcdc 4830e000.lcdc: fb0:  frame buffer device
[    1.179802] tilcdc 4830e000.lcdc: registered panic notifier
[    1.208973] [drm] Initialized tilcdc 1.0.0 20121205 on minor 0
[    1.226384] brd: module loaded
[    1.234846] loop: module loaded
[    1.241223] mtdoops: mtd device (mtddev=name/number) must be supplied
[    1.249677] m25p80 spi1.0: s25fl256s1 (32768 Kbytes)
[    1.254728] 8 cmdlinepart partitions found on MTD device spi1.0
[    1.260799] Creating 8 MTD partitions on "spi1.0":
[    1.265621] 0x000000000000-0x000000040000 : "MLO"
[    1.271586] 0x000000040000-0x0000000c0000 : "u-boot"
[    1.277627] 0x0000000c0000-0x000000100000 : "env1"
[    1.283419] 0x000000100000-0x000000140000 : "env2"
[    1.289243] 0x000000140000-0x000000180000 : "fdt"
[    1.294905] 0x000000180000-0x000000780000 : "kernel"
[    1.300884] 0x000000780000-0x000000b80000 : "splash"
[    1.306861] 0x000000b80000-0x000002000000 : "free"
[    1.313838] CAN device driver interface
[    1.378977] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    1.385118] davinci_mdio 4a101000.mdio: detected phy mask ffffffbf
[    1.392242] libphy: 4a101000.mdio: probed
[    1.396290] davinci_mdio 4a101000.mdio: phy[6]: device 4a101000.mdio:06, driver SMSC LAN8710/LAN8720
[    1.406385] cpsw 4a100000.ethernet: Detected MACID = 00:50:c2:1e:af:e0
[    1.414520] usbcore: registered new interface driver asix
[    1.420272] usbcore: registered new interface driver ax88179_178a
[    1.426454] usbcore: registered new interface driver cdc_ether
[    1.432459] usbcore: registered new interface driver smsc95xx
[    1.438316] usbcore: registered new interface driver net1080
[    1.444120] usbcore: registered new interface driver cdc_subset
[    1.450148] usbcore: registered new interface driver zaurus
[    1.455897] usbcore: registered new interface driver cdc_ncm
[    1.462330] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.468998] ehci-pci: EHCI PCI platform driver
[    1.473558] ehci-omap: OMAP-EHCI Host Controller driver
[    1.479169] usbcore: registered new interface driver cdc_wdm
[    1.484935] usbcore: registered new interface driver usb-storage
[    1.491222] usbcore: registered new interface driver usbserial
[    1.497124] usbcore: registered new interface driver usbserial_generic
[    1.503777] usbserial: USB Serial support registered for generic
[    1.509890] usbcore: registered new interface driver ftdi_sio
[    1.515702] usbserial: USB Serial support registered for FTDI USB Serial Device
[    1.524826] 47401300.usb-phy supply vcc not found, using dummy regulator
[    1.561232] musb-hdrc musb-hdrc.0.auto: Failed to request rx1.
[    1.567257] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517
[    1.575880] 47401b00.usb-phy supply vcc not found, using dummy regulator
[    1.611082] musb-hdrc musb-hdrc.1.auto: Failed to request rx1.
[    1.617082] musb-hdrc musb-hdrc.1.auto: musb_init_controller failed with status -517
[    1.632643] mousedev: PS/2 mouse device common for all mice
[    1.639264] input: ti-tsc as /devices/platform/ocp/44e0d000.tscadc/TI-am335x-tsc/input/input0
[    1.649064] omap_rtc 44e3e000.rtc: already running
[    1.654286] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    1.661790] i2c /dev entries driver
[    1.665396] Driver for 1-wire Dallas network protocol.
[    1.672274] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    1.679407] Bluetooth: HCI UART driver ver 2.3
[    1.683917] Bluetooth: HCI UART protocol H4 registered
[    1.689107] Bluetooth: HCI UART protocol BCSP registered
[    1.694441] Bluetooth: HCI UART protocol LL registered
[    1.699638] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    1.706046] usbcore: registered new interface driver btusb
[    1.739645] ledtrig-cpu: registered to indicate activity on CPUs
[    1.746027] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    1.753527] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    1.760841] usbcore: registered new interface driver usbhid
[    1.766565] usbhid: USB HID core driver
[    1.771126]  remoteproc0: wkup_m3 is available
[    1.775601]  remoteproc0: Note: remoteproc is still under development and considered experimental.
[    1.784757]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    1.795455]  remoteproc0: Direct firmware load for am335x-pm-firmware.elf failed with error -2
[    1.805442] usbcore: registered new interface driver snd-usb-audio
[    1.811799]  remoteproc0: Falling back to user helper
[    1.820189] oprofile: using arm/armv7
[    1.824298] Initializing XFRM netlink socket
[    1.828725] NET: Registered protocol family 17
[    1.833328] NET: Registered protocol family 15
[    1.837796] can: controller area network core (rev 20120528 abi 9)
[    1.844147] NET: Registered protocol family 29
[    1.848653] can: raw protocol (rev 20120528)
[    1.852972] can: broadcast manager protocol (rev 20120528 t)
[    1.858833] Bluetooth: RFCOMM TTY layer initialized
[    1.863869] Bluetooth: RFCOMM socket layer initialized
[    1.869088] Bluetooth: RFCOMM ver 1.11
[    1.872872] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    1.878231] Bluetooth: BNEP filters: protocol multicast
[    1.883510] Bluetooth: BNEP socket layer initialized
[    1.888503] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    1.894488] Bluetooth: HIDP socket layer initialized
[    1.899554] 8021q: 802.1Q VLAN Support v1.8
[    1.903845] Key type dns_resolver registered
[    1.908623] omap_voltage_late_init: Voltage driver support not added
[    1.915576] cpu cpu0: of_pm_voltdm_notifier_register: Failed to get cpu0 regulator/voltdm: -517
[    1.924429] cpu cpu0: cpu0 clock notifier not ready, retry
[    1.930614] PM: bootloader does not support rtc-only!
[    1.935937] ThumbEE CPU extension supported.
[    1.940360] Registering SWP/SWPB emulation handler
[    1.948031] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    1.953388] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000
[    1.961151] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xdc
[    1.967549] nand: AMD/Spansion S34ML04G1
[    1.971688] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    1.979385] nand: using OMAP_ECC_BCH8_CODE_HW ECC scheme
[    1.984753] 11 cmdlinepart partitions found on MTD device 8000000.nand
[    1.991332] Creating 11 MTD partitions on "8000000.nand":
[    1.996787] 0x000000000000-0x000000020000 : "NAND.SPL"
[    2.003285] 0x000000020000-0x000000040000 : "NAND.SPL.backup1"
[    2.010360] 0x000000040000-0x000000060000 : "NAND.SPL.backup2"
[    2.017196] 0x000000060000-0x000000080000 : "NAND.SPL.backup3"
[    2.024090] 0x000000080000-0x000000260000 : "NAND.u-boot"
[    2.031243] 0x000000260000-0x000000280000 : "NAND.u-boot-env"
[    2.037995] 0x000000280000-0x0000002a0000 : "NAND.u-boot-env.backup1"
[    2.045563] 0x0000002a0000-0x0000002c0000 : "NAND.fdt"
[    2.051769] 0x0000002c0000-0x0000008c0000 : "NAND.kernel"
[    2.060575] 0x0000008c0000-0x000000cc0000 : "NAND.splash"
[    2.068551] 0x000000cc0000-0x000020000000 : "NAND.file-system"
[    2.353666] tps65910-rtc tps65910-rtc: rtc core: registered tps65910-rtc as rtc1
[    2.362885] ina2xx 0-0041: power monitor ina226 (Rshunt = 10000 uOhm)
[    2.369482] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 100 kHz
[    2.381945] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.392603] musb-hdrc: MHDRC RTL version 2.0
[    2.396980] musb-hdrc: setup fifo_mode 4
[    2.400966] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.406347] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
[    2.412480] musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1
[    2.420630] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    2.427453] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.434758] usb usb1: Product: MUSB HDRC host driver
[    2.439763] usb usb1: Manufacturer: Linux 4.1.18-divelk-3.0.0-gdc0123a musb-hcd
[    2.447105] usb usb1: SerialNumber: musb-hdrc.0.auto
[    2.452922] hub 1-0:1.0: USB hub found
[    2.456733] hub 1-0:1.0: 1 port detected
[    2.495372] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.506064] musb-hdrc: MHDRC RTL version 2.0
[    2.510458] musb-hdrc: setup fifo_mode 4
[    2.514412] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.519830] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    2.525935] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 2
[    2.534098] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    2.540951] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.548230] usb usb2: Product: MUSB HDRC host driver
[    2.553236] usb usb2: Manufacturer: Linux 4.1.18-divelk-3.0.0-gdc0123a musb-hcd
[    2.560813] usb usb2: SerialNumber: musb-hdrc.1.auto
[    2.566602] hub 2-0:1.0: USB hub found
[    2.570488] hub 2-0:1.0: 1 port detected
[    2.600226] vmmc: supplied by vin
[    2.639413] vdd_mpu: supplied by vin
[    2.646445] cpu cpu0: of_pm_voltdm_notifier_register: Fail calculating voltage latency[950000<->1260000]:-22
[    2.656864] cpu cpu0: of_pm_voltdm_notifier_register: Fail calculating voltage latency[950000<->1260000]:-22
[    2.668215] omap_rtc 44e3e000.rtc: setting system clock to 2017-04-26 15:46:51 UTC (1493221611)
[    2.685225] ALSA device list:
[    2.688272]   No soundcards found.
[    2.692725] Waiting 2 sec before mounting root device...
[    2.727127] mmc0: host does not support reading read-only switch, assuming write-enable
[    2.737406] mmc0: new high speed SDHC card at address 0001
[    2.743604] mmcblk0: mmc0:0001 SD16G 14.9 GiB
[    2.749551]  mmcblk0: p1 p2 p3
[    3.459071] cfg80211: Calling CRDA to update world regulatory domain
[    4.706466] kjournald starting.  Commit interval 5 seconds
[    4.849696] EXT3-fs (mmcblk0p2): using internal journal
[    4.855149] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
[    4.862237] VFS: Mounted root (ext3 filesystem) on device 179:2.
[    4.871847] devtmpfs: mounted
[    4.875784] Freeing unused kernel memory: 276K (c0ab1000 - c0af6000)
INIT:version 2.88 booting
using "DejaVu Sans Mono-16", pixelsize=16.67 file=/usr/share/fonts/truetype/DejaVuSansMono.ttf
[    6.609097] cfg80211: Calling CRDA to update world regulatory domain
Starting udev
[    6.924115] udevd[104]: starting version 182
[    9.540313] [drm] Initialized pvr 1.14.3699939 20110701 on minor 1
[    9.716535]  remoteproc0: powering up wkup_m3
[    9.742023]  remoteproc0: Booting fw image am335x-pm-firmware.elf, size 219727
[    9.759127] cfg80211: Calling CRDA to update world regulatory domain
[    9.796287]  remoteproc0: remote processor wkup_m3 is now up
[    9.796324] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x191
[   12.565461] cfg80211: World regulatory domain updated:
[   12.596790] cfg80211:  DFS Master region: unset
[   12.615473] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   12.665673] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   12.684253] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   12.699149] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   12.727527] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   12.769159] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   12.778715] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   12.850883] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   12.895545] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   12.928219] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   12.955516] cfg80211: Calling CRDA to update world regulatory domain
[   13.005089] cfg80211: World regulatory domain updated:
[   13.022569] cfg80211:  DFS Master region: unset
[   13.037433] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[   13.059178] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   13.067249] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[   13.088401] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[   13.096690] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[   13.106300] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[   13.116002] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[   13.124179] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[   13.132270] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[   13.407322] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[   13.768334] cryptodev: driver 1.6 loaded.
[   13.892293] udc musb-hdrc.0.auto: registering UDC driver [g_multi]
[   13.910617] using random self ethernet address
[   13.915115] using random host ethernet address
[   13.919846] using host ethernet address: 68:C9:0B:1C:39:22
[   13.925271] using random self ethernet address
[   13.929973] using random host ethernet address
[   13.934442] using host ethernet address: 68:C9:0B:1C:39:22
[   13.944227] usb0: HOST MAC 68:c9:0b:1c:39:22
[   13.958134] usb0: MAC 3a:71:aa:ff:d9:09
[   13.988032] userial_init: registered 4 ttyGS* devices
[   14.005813] Mass Storage Function, version: 2009/09/11
[   14.019336] LUN: removable file: (no medium)
[   14.030898] lun0: open backing file: /dev/mmcblk0p1
[   14.035837] LUN: file: /dev/mmcblk0p1
[   14.039801] Number of LUNs=1
[   14.042718] g_multi gadget: adding config #1 'Multifunction with RNDIS'/bf0ce9b8
[   14.050218] rndis_register: configNr = 0
[   14.054164] g_multi gadget: adding 'rndis'/ddde0e40 to config 'Multifunction with RNDIS'/bf0ce9b8
[   14.063176] rndis_set_param_medium: 0 0
[   14.067036] g_multi gadget: RNDIS: dual speed IN/ep1in OUT/ep1out NOTIFY/ep2in
[   14.074356] g_multi gadget: adding 'acm'/ddde0240 to config 'Multifunction with RNDIS'/bf0ce9b8
[   14.083142] g_multi gadget: acm ttyGS0: dual speed IN/ep3in OUT/ep2out NOTIFY/ep4in
[   14.090878] Number of LUNs=1
[   14.093927] g_multi gadget: I/O thread pid: 660
[   14.098499] g_multi gadget: adding 'Mass Storage Function'/db279a80 to config 'Multifunction with RNDIS'/bf0ce9b8
[   14.108958] g_multi gadget: cfg 1/bf0ce9b8 speeds: high full
[   14.114645] g_multi gadget:   interface 0 = rndis/ddde0e40
[   14.120174] g_multi gadget:   interface 1 = rndis/ddde0e40
[   14.125705] g_multi gadget:   interface 2 = acm/ddde0240
[   14.131059] g_multi gadget:   interface 3 = acm/ddde0240
[   14.136395] g_multi gadget:   interface 4 = Mass Storage Function/db279a80
[   14.143344] g_multi gadget: adding config #2 'Multifunction with CDC ECM'/bf0cea5c
[   14.150977] g_multi gadget: adding 'cdc_ethernet'/ddde0600 to config 'Multifunction with CDC ECM'/bf0cea5c
[   14.160729] g_multi gadget: CDC Ethernet: dual speed IN/ep1in OUT/ep1out NOTIFY/ep2in
[   14.168600] g_multi gadget: adding 'acm'/ddde0780 to config 'Multifunction with CDC ECM'/bf0cea5c
[   14.177565] g_multi gadget: acm ttyGS0: dual speed IN/ep3in OUT/ep2out NOTIFY/ep4in
[   14.185356] g_multi gadget: I/O thread pid: 661
[   14.189972] g_multi gadget: adding 'Mass Storage Function'/db279200 to config 'Multifunction with CDC ECM'/bf0cea5c
[   14.200483] g_multi gadget: cfg 2/bf0cea5c speeds: high full
[   14.206188] g_multi gadget:   interface 0 = cdc_ethernet/ddde0600
[   14.212326] g_multi gadget:   interface 1 = cdc_ethernet/ddde0600
[   14.218445] g_multi gadget:   interface 2 = acm/ddde0780
[   14.223814] g_multi gadget:   interface 3 = acm/ddde0780
[   14.229166] g_multi gadget:   interface 4 = Mass Storage Function/db279200
[   14.236108] g_multi gadget: Multifunction Composite Gadget
[   14.241638] g_multi gadget: userspace failed to provide iSerialNumber
[   14.248105] g_multi gadget: g_multi ready
[   14.252174] g_multi musb-hdrc.0.auto: usb_gadget_udc_start
[   17.663641] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000020): FIFO underfow
[   17.668701] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000004): Sync lost
[   17.669343] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000004): Sync lost
bootlogd: cannot allocate pseudo tty: No such file or directory
[   24.354944] random: dd urandom read with 123 bits of entropy available
Populating dev cache
[   26.119081] random: nonblocking pool is initialized
ALSA: Restoring mixer settings...
/usr/sbin/alsactl: load_state:1729: No soundcards found...
Wed May 31 09:45:12 UTC 2017
INIT: Entering runlevel: 5
Configuring network interfaces... [   40.860824] net eth0: initializing cpsw version 1.12 (0)
[   40.868746] net eth0: phy found : id is : 0x7c0f1
[   40.881890] 8021q: adding VLAN 0 to HW filter on device eth0
udhcpc (v1.23.1) started
Sending discover...
[   43.939734] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Sending discover...
Sending discover...
No lease, forking to background
[   50.945002] usb0: eth_open
done.
Starting system message bus: dbus.
UIM SYSFS Node Not Found
[   53.654856] PVR_K: UM DDK-(3699939) and KM DDK-(3699939) match. [ OK ]
Loaded PowerVR consumer services.
Calibrating touchscreen (first time only)

*** To continue, please complete the touchscreen calibration
*** by touching the crosshairs on the LCD screen[   54.016321] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000020): FIFO underfow
[   54.028738] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000004): Sync lost
.
[   61.413350] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000020): FIFO underfow
[   61.426322] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000004): Sync lost
[   61.426962] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000004): Sync lost
[   63.321703] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000020): FIFO underfow
[   63.322426] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000004): Sync lost
[   63.323063] tilcdc 4830e000.lcdc: tilcdc_crtc_irq(0x00000004): Sync lost
Starting Dropbear SSH server: Generating key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCBXMbgUD7BQFkKD9c/Cz1YCcQn+wT193amGd3EFLt0vBYKpSbD9AKOgwqO23Mg8fNh/2hhZI+aTbsSprjEu+lf43cC6qFCFe/1CPAM6BWaX5zD0Iif/CKaljCKdDY4XiEKbwROobCgWYBuTlPlADK7sw5fGyPO0Km3F2Br13kLFNyrb11juKF3mkBCODgZFbRK5BviZ359+4WdJWycVzOX3MwRTJY7i4pUMH5rzK1eZpEfmlRDvFKAlI9jA6z3e/ZB4YCLDCs9mw+CDSicYt9KUac2DOs70lr+tzJMI6EqtPQcltGDjl92d9moMSdg5gKZ5OnoojNRIYUF6hc1RdtJ root@diva
Fingerprint: md5 fd:a2:9d:bc:a5:71:5c:e8:c2:5d:a9:f5:f7:c5:fe:0b
dropbear.
Starting telnet daemon.
Starting rpcbind daemon...rpcbind: cannot create socket for udp6
rpcbind: cannot create socket for tcp6
done.
starting statd: done
starting Busybox UDHCP Server: udhcpd... done.
Starting syslogd/klogd: done
Starting thttpd.
Starting Lighttpd Web Server: lighttpd.
2017-05-31 09:45:49: (/mnt/devel/divelk-3.0.0-ci/build/tmp-external-linaro-toolchain/work/cortexa8hf-vfp-neon-linux-gnueabi/lighttpd/1.4.35-r1/lighttpd-1.4.35/src/log.c.164) server started
/
Starting Matrix GUI application.
Enabling thermal zones...
/etc/rc5.d/S98thermal-zone-init: line 7: /sys/class/thermal/thermal_zone*/mode: No such file or directory
***************************************************************
***************************************************************
NOTICE: This file system contains the following GPLv3 packages:
        autoconf
        binutils
        cpp-symlinks
        cpp
        g++-symlinks
        g++
        gcc-symlinks
        gcc
        gdb
        gdbserver
        gstreamer1.0-libav
        libgmp10
        libmpc3
        libmpfr4
        make

If you do not wish to distribute GPLv3 components please remove
the above packages prior to distribution.  This can be done using
the 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
***************************************************************
***************************************************************
Starting tcf-agent: OK

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org diva /dev/ttyO0

Arago 2016.03 diva /dev/ttyO0

diva login:

[1] bootscript is used to do this task.

Host setup[edit | edit source]

As stated previously, DIVELK host tools are based on a Managed Virtual Machine. As indicated here, microSD card delivered along with DIVELK includes basic version of MVM that is the default option.

In case you choose to use the Advanced version of the MVM instead, the project-name to be used is diva.

Either version you choose, please follow the procedure described here to install the MVM.

It is also worth remembering that access to git repositories is required to download target source code. To enable it, please refer to this page.


200px-Emblem-important.svg.png

Either version of MVM is installed, it provides the tools required to build U-boot and Linux kernel. It does not include the tools required to run Yocto build system instead.


DIVELK MVM can be downloaded here. For accessing DIVELK Reserved area please contact our sales department

Target configuration for the development stage (net_nfs)[edit | edit source]

200px-Emblem-important.svg.png

The default DIVELK Virtual Machine network configuration is using NAT: this allows to accessing external network (i.e. Internet) using the host computer's networking connection. For software development using net_nfs with tftp/nfs protocols, please configure your VM network interface in Bridge mode (see below)

During the development stage, the target is usually connected via Ethernet LAN to the host machine and is configured to:

  • retrieve binary images (i.e. Linux kernel) via TFTP protocol
  • mount the development root file system via NFS protocol. This root file system is physically in the file system of the host machine as depicted here. An example of Bridge mode configuration for DIVELK can be found here

In DAVE Embedded Systems development kits, this configuration is generally denoted as net_nfs. U-Boot bootloader supports this configuration. Some U-Boot environment variables are needed to set it up. They are detailed here.

For more details about TFTP and NFS servers on host side, please refer to this page.

Target configuration for standalone boot[edit | edit source]

Please refer to this page.

Developing the software for the target[edit | edit source]

Please refer to this page.

Advanced topics[edit | edit source]

Debugging with Eclipse[edit | edit source]

Please refer to this page.