Template:DebianVM Development

From Wiki-DB
Jump to navigationJump to search

Introduction

For cross developing of applications we provide virtual machines with preinstalled toolchains. Choose the virtual machine which fits to your DHCOM target (Debian 8 on target -> Debian 8 virtual machine). Debian 8 does include support for architecture armhf and armel (Debian 6 only armel). By default Debian 8 is configured for armhf. The sections Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more and Booting via NFS apply for Debian 6 and Debian 8.

Debian 8 "Jessie" VMware Image

Get the virtual machine

Version: File: Changes:
v1.2 Debian Jessie v1.2.zip - Debian Security updates
- Qt Creator + Support for imx6 modules + Demos
- Update elbe to v1.0
- Add some tools / editors
v1.1 Debian Jessie v1.1.zip - Compatibility VMware player 6.0
v1.0 Debian Jessie v1.0.zip - New Debian 8 VM

Installed Toolchains

Debian Multiarch Cross Toolchain

Both armhf and armel Cross Toolchains are preinstalled. They should be used for cross development of native Linux applications. They are downloaded and installed with the Debian Package Manager.

  • armhf: arm-linux-gnueabihf-
  • armel: arm-linux-gnueabi-

Install directory is /usr/bin/. Please have a look at the preconfigured Examples for cross development using the Eclipse IDE.

Linaro GCC 4.9 armhf

Used for building the Linux Kernel for our ARMv7 DHCOM devices.

  • armhf: arm-linux-gnueabihf-

Install directory is /opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/. Please refere the section "Linux Kernel" for the matching DHCOM device.

CodeSourcery GCC 4.5 armel

Used for building the Linux Kernel for our ARMv5 DHCOM devices.

  • armel: arm-none-linux-gnueabi-

Install directory is /opt/CodeSourcery-2011.03-41/bin/. Please refere the section "Linux Kernel" for the matching DHCOM device.

Qt5 Development

Qt5.5.1 prebuilt and preinstalled

We provide the prebuilt Qt5.5.1 libraries including WebEngine (only QtQuick) and WebKit in /work/qt5/sysroot/. This directory contains a Debian 8 based rootfilesystem which is prepared for DHCOM i.MX6, the matching sysroot (*-dev packages), and the Qt5.5.1 libraries installed.

Qt5.7.1

We support the latest Qt5.7.1 on our DHCOM i.MX6 and DHCOM am335x. Please download and install the qmake-sysroot-mx6-crossarmhf_5.7.1-1.0 or qmake-sysroot-am33-crossarmhf_5.7.1-1.0 package to the DebianVM:

  1. open a terminal
  2. # for i.MX6: wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb
  3. # for AM335x: wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb
  4. install the package
  5. # sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb
  6. now the sysroot and qmake is ready to use
  7. path to qmake is /work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake

Build a Qt5 Application via console

  1. open a terminal
  2. navigate to your Qt5 sources
  3. # /work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro
  4. # make

Qt Creator

  1. Start Qt Creator IDE
  2. Open demo project TwoLED: /work/qt5_Demos/TwoLED
  3. There you can find the configurations for your own project.

Debian 6 "Squeeze" VMware Image

Get the virtual machine

Version: File: Changes:
v1.5 Debian Squeeze v1.5pw.zip - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
v1.4 Debian Squeeze v1.4pw.zip - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
v1.3 Debian Squeeze v1.3.zipx - Mono 2.10<br\>- mtd-utils<br\>- System updates
v1.2 Debian Squeeze v1.2.zipx - Emdebian Toolchain gcc 4.3 / g++ 4.3 (arm-linux-gnueabi-...)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
v1.1 Debian Squeeze v1.1.zipx - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
v1.0 Debian Squeeze.zipx - First Release<br\>- CodeSourcery Toolchain (arm-none-linux-gnueabi-...)<br\>- Eclipse Helios & Indigo

Setting up a Eclipse Cross Executable Project:

  • Use Eclipse Indigo (version 3.7.1) for your project.
  • Create a new C++ Project and choose as Executable Project type Cross-Compile Project and as Toolchains Cross GCC
  • Click the Button "Next" and specify under Tool command path the Toolchain path.
  • CodeSourcery:
Folder "/opt/CodeSourcery/Sourcery_G++_Lite/bin"
Prefix type "arm-none-linux-gnueabi-"
  • Emdebian Toolchain:
Folder "/usr/bin"
Prefix type "arm-linux-gnueabi-"

Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more

  • The following code samples are designed to get you started quickly with the device interfaces to SPI, I2C, GPIOs and more in Linux userspace applications.
  • Within Eclipse you can Import the provided projects:
  1. Execute ">File>Import ..."
  2. Navigate to ">General>Existing Projects into Workspace" within the import dialog
  3. Follow the dialog until you have finished.

Download Code Examples SPI, I2C, GPIOs and more

Included Demos:

  • SPI
  • I2C
  • GPIO
  • RTC
  • UART
  • Watchdog
  • ADC (only for i.MX25)

Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access

Booting via NFS

Prepare the virtual machine

  • Place the root file system in the folder "/work/nfsroot"
  • Check whether the line below is part of the "/etc/exports" file
/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)
The X must be substituted by our network settings
  • Restart the nfs-server by using this commando
/etc/init.d/nfs-kernel-server restart

Setup the DHCOM Module for TFTP/NFS Boot

This example works with static IP addresses. It is possible to work with DHCP, too.

  • Enter U-Boot console by pressing DEL/BACKSPACE on a RS232 terminal while switching on the power supply of the target
  • Set IP addresses
# env set serverip 192.168.178.90
# env set ipaddr 192.168.178.91
  • bootargs for nfs root
# env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/net/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'
  • load Linux kernel and devicetree with tftp (change filename and path to match you setup)
# tftp ${loadaddr} zImage
# tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb
  • set bootcmd
# env set bootcmd 'run linuxargs; bootz ${loadaddr} - ${fdt_addr}'
  • optional: save it to be permanent
# env save
  • boot target
# boot