Bureaucrats, dave_user, Administrators
8,184
edits
Changes
→Support service
{{Applies To Diva}}
{{InfoBoxBottom}}
{{WarningMessage|text=The following information are valid for <b>DIVELK</b> version up to release <b>2.2.0</b>}}
= Introduction =
== About this manual ==
This document describes how to run Linux on the DIVA/DIVAEVB-Lite/Carrier-board system and 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].
== Support service ==
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 Embedded Systems''' web sitegit 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).
Please refer to our Web site at http://www.dave.eu/dave-cpu-module-am335x-diva.html for the latest product documents, utilities, drivers, Product Change Notices, Board Support Packages, Application Notes, mechanical drawings and additional tools and software.
'''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.
=== DIVELK Updates ===
* start a shell session
* enter the .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:
== Release notes ==
= Developing environment =
* 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
The divelk directory contains the following subdirectories:
* gcc-linaro-arm-linux-gnueabihf-4.7-2013.03-20130313_linuxyocto: the Yocto SDK installation directory (containing the cross-toolchain. GNU Compiler Collection (GCC) version is 4.7.3
* linux-am33x: the Linux source tree
* u-boot-am33x: the U-Boot source tree
<pre>
export ARCH=arm
export CROSS_COMPILE=arm-linux-gnueabihf-
==== NFS Server ====
One of the most useful features important components of a bootloader during development Linux system is the capability to download root file system. A good development root file system provides the Linux kernel from developer with all the networkuseful tools that can help developers on their work. This saves Such a lot of time because developer doesnroot file system can become very big in size, so it't have s hard to program store it in flash memory. User could split the image file system in different parts, mounting them from different media (flash every time he/she modifies it, network, usb...). U-Boot implements But the most convenient thing is to mount the TFTP protocol (see whole root file system from the tftp command)network, so allowing the host system must and the target to share the same files. In this way, developers can quickly modify the root file system, even “on the fly” (meaning that the file system can be configured modified while the system is running). The most common way to enable setup a system like the one described is through NFS (Network File System). As for TFTP service. Installation , installation and configuration of a TFTP server depends on the host Linux distribution. The default DVDK tftp NFS installation has is configured for sharing <code>/srvhome/dvdk/tftpdivelk</code> as work directoryand all the subdirectories. A subdirectory dedicated to We recommend reading the [[VirtualBox_Network_Configuration]] page for additional details on the image files associated DVDK networking configuration and on how to the DIVELK (<code>/srv/tftp/divelk</code>) is available, but developers can add their custom subdirectories when requiredenable NFS.
==== Pre-built toolchain ====
