Wiki-DB - User contributions [en]

DHCOM iMX6-D2

2018-09-21T08:16:25Z

Lzenz: /* Linux Kernel Sources / Prebuilt Kernels */

{|
|
|
|-
|__TOC__
|[[Image:IM6Modul.png|600px|COM iMX6-D2]]
|}

== Hardware ==
*[[COM iMX6 Hardware|Hardware]]

{| class="wikitable" align="center" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* '''Cortex-A9 Freescale i.MX6 Solo/Dual(Lite)/Quad up to 1.2GHz'''
* 2D/3D graphics accelerator
* 0 - 512 MByte NAND flash memory (8 bit bus width) or 2 - 16 GByte eMMC flash
* 2 MB SPI boot flash
* 256 - 2048 MByte DDR3-1066 or DDR3-800
* On-board microSD card socket
* SD/MMC card interface, 4 bit SDIO
* LC display controller, 24 bit colors, 2048x1536 pixels
* LVDS 4-channel, max. 165 Mpixels/s
* On-board touch controller for 4-wire resistive touch screens
* Ethernet controller 10/100 Mbit, IEEE1588 conform
* USB 2.0 OTG high-speed
* USB 2.0 host high speed
* Full function UART
* Standard UART with hardware handshake support
* Standard UART
|valign="top" style="border: 0pt;" |
* CAN interface
* 2 x SPI interface
* 2 x I2CTM interface
* I²S Audio codec (1 x microphone, 1 x Line in, 1x Line out)
* Real-time clock (I2CTM connection), low power temperature compensated
* 12 bit analog input
* 1 kbit EEPROM with integrated MAC address
* 16 bit address/databus interface on SODIMM-200 socket
* PWM channel
* 23 GPIOs
* JTAG debug connection via FFC plug connector
* Industrial temperature range (-40°C to +85°C)
* SODIMM-200 socket with DHCOM pin assignment
|}

== Software Support ==
*[[COM iMX6 Bootloader U-Boot|Bootloader U-Boot]]
*[[DHCOM Update Mechanism|DHCOM Update Mechanism for i.MX6]]

*[[COM iMX6 Linux|Linux]]
*[[Yocto | Yocto on DHCOM i.MX6]]
*[[COM iMX6 WinCE|WinCE]]

== Downloads ==
==== U-Boot Sources ====
* [https://github.com/dh-electronics/u-boot-imx6qdl u-boot source code (GitHub)]
* [[media:U-boot-2015.10_iMX6_V1.1.0.6.zip|Download the latest U-Boot binary (V1.1.0.6)]]

==== Update-Kernel ====
* [[media:2018-02-01_imx6_updatekernel.zip|2018-02-01 update kernel (binary)]]

====Linux Kernel Sources / Prebuilt Kernels====
* Mainline
:* [https://github.com/dh-electronics/linux-imx6qdl/tree/dev/4.4.60_dhcom 4.4.60 mainline (GitHub)]
:* [[media:2017-07-25_imx6_4.4.60_boot.tar.bz2|4.4.60 mainline prebuilt Kernel (boot partition)]]
* Vendor
:* [https://github.com/dh-electronics/linux-imx6-vendor/tree/release/v4.1.15/20171102 4.1.15 vendor 2017-11-02 (GitHub)]
:* [[media:2017-11-02_imx6_4.1.15_boot.tar.bz2|4.1.15 vendor prebuilt Kernel (boot partition)]]
:* [https://github.com/dh-electronics/linux-imx6-vendor/tree/release/v3.10.17/20170804 3.10.17 vendor 2017-08-04 (GitHub)]
:* [[media:2017-08-04_imx6_3.10.17_boot.tar.bz2|3.10.17 vendor prebuilt Kernel (boot partition)]]

==== Debian based root file systems ====
* Debian alone

:* [[media:2017-05-29_jessie-armhf-base-rootfs.tar.gz|Based on Debian 8 "Jessie" (2017-05-29)]]

:* [[media:2014-10-30_developer-rootfs_DN6_imx6.tar.bz2|Based on Debian 6 "Squeeze" (2014-10-30)]] ''Remark:'' Shellshock (CVE-2014-6271) is already fixed.

* Debian Qt5

:* [[media:2017-10-06_jessie-armhf-imx6_fsl_4.1.15-rootfs.tar.gz|Based on Debian 8 "Jessie" + Qt5.9.1 (2017-10-06)]] ''Remark:'' It must be used with i.MX6 Vendor Kernel 4.1.15

:* [[media:2016-12-19_jessie-armhf-imx6_fsl_3.10.17-rootfs.tar.gz|Based on Debian 8 "Jessie" + Qt5.7.1 (2016-12-19)]] ''Remark:'' It must be used with i.MX6 Vendor Kernel 3.10.17

==== Virtual Machine for Application Development ====
* [[media:Debian Jessie v1.3.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

* [[media:Debian Squeeze v1.5pw.zip|Debian 6 "Squeeze" VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

==== Mainline Linux 4.4.x eMMC update package ====
* [[media:HD00035_2017-07-25_USBStick_eMMC_update_package.zip|i.MX6 Linux Kernel 4.4.60 with Debian Jessie Rootfilesystem]] Extract files to USB stick and use stick to update i.MX6 Solo, DualLite or Quad

==== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ====
* [[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs, RTC, UART, Watchdog, and more ]]
* [[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

==== WEC7 DHHalLib.dll (function library) ====
* [[media:DHHalLib_R04_2016_10_19.zip|Download DHHalLib Library Version 1.3.0.0]]
* [[media:DHHalLib_Test_App_Source_R03_2016_10_19.zip|DHHalLib Demo App Source Code ]]
* [[media:DHHalLib_Test_App_Binary_R03_2016_10_19.zip|DHHalLib Demo App Binary File]]
* [[media:CSharp_LibWrapper.zip|Download DHHalLib CSharp Demo Wrapper App ]]
* [[media:CSharp_LibWrapper_Binary.zip|Download DHHalLib CSharp Demo Wrapper App Binary File]]

==== WEC7 binary BSP ====
* [[media:2016-05-19_DHCOM_iMX6_BSP_BIN.zip|Download WEC7 binary BSP (date: 2016-05-19)]]

==== WEC2013 DHHalLib.dll (function library) ====
* [[media:DHHalLib_WEC2013_R10_2018_06_12.zip|Download DHHalLib Library Version 1.4.2.0]]
* [[media:DHHalLib_Test_App_Source_WEC2013_R07_2018_06_12.zip|DHHalLib Demo App Source Code ]]
* [[media:DHHalLib_Test_App_Binary_WEC2013_R07_2018_06_12.zip|DHHalLib Demo App Binary File]]
* [[media:CSharp_LibWrapper_Source_WEC2013_R06_2017_08_08.zip|Download DHHalLib CSharp Wrapper]]
* [[media:CSharp_DHHalLib_Wrapper_App_Source_WEC2013_R05_2017_08_08.zip|DHHalLib C# Demo App Source Code]]
* [[media:CSharp_DHHalLib_Wrapper_App_Binary_WEC2013_R05_2017_08_08.zip|DHHalLib C# Demo App Binary File]]

Main Page

2018-08-02T09:33:54Z

Lzenz:

__NOTOC__
{| style="width: 100%; color: #000000; border-spacing: 2px; border: 1px solid darkgray;" valign="top" |
| style="width: 25%; text-align: center;" |
| style="width: 50%; text-align: center;" |
| style="width: 25%; text-align: center;" |
|-
| style="text-align: center;" | [[Image:Welcome.jpg|200px|Welcome to DH electronics MediaWiki]]
| style="text-align: center;" | [[Image:LOGO_DH_electronics.jpg|200px|Welcome to DH electronics MediaWiki]]
| style="text-align: center;" | [[Image:Mediawiki.jpg|183px|Welcome to DH electronics MediaWiki]]
|}

''Welcome to DH electronics new MediaWiki. This Wiki has the aim to provide our customers technical support for DH electronics products.''

{| style="width: 100%; color: #000000; border-collapse:collapse; border: darkgray; border-style: solid; border-width: 1px 0 1px 0"
| [[Image:DHCM-120pix-ws.jpg|center|DH Computer on Module|link=DHCOM]]
|style="padding:10px;"|
=== [[DHCOM|DHCOM]] ===

A '''Computer On Module''' (COM) is a powerful embedded computer on a compact circuit board.

Our DHCOM modules offer high performance coupled with extensive features and interfaces, low power consumption as well as compact size.Possible applications for our modules are in visualization, multimedia, automation and communication devices

Click '''[[DHCOM|here]]''' to get support information for our '''[[DHCOM]]''' products.
| style="text-align: right;" |[[Image:IM6Modul.png|center|300px|COM iMX6-D2|link=COM iMX6-D2]]
|-
|style="border: darkgray; border-style: solid; border-width: 1px 0 0 0;"|[[Image:XLON Logo in Schwarz von SD Kopie.jpg|center|120px|DH electronics XLON|link=DHCOM]]
|style="padding:10px; border: darkgray; border-style: solid; border-width: 1px 0 0 0;"|
=== [[XLON|XLON]] ===

Our '''XLON''' products are network interfaces for LonWorks-Technology.

Click '''[[XLON|here]]''' to get support information for our '''[[XLON]]''' products.
| style="text-align: right; border: darkgray; border-style: solid; border-width: 1px 0 0 0;" |[[Image:XLON U10.png|center|275px|XLON U10|link=COM iMX6-D2]]
|}

Main Page

2018-08-02T09:28:26Z

Lzenz:

__NOTOC__
{| style="width: 100%; color: #000000; border-spacing: 2px; border: 1px solid darkgray;" valign="top" |
| style="width: 25%; text-align: center;" |
| style="width: 50%; text-align: center;" |
| style="width: 25%; text-align: center;" |
|-
| style="text-align: center;" | [[Image:Welcome.jpg|200px|Welcome to DH electronics MediaWiki]]
| style="text-align: center;" | [[Image:LOGO_DH_electronics.jpg|200px|Welcome to DH electronics MediaWiki]]
| style="text-align: center;" | [[Image:Mediawiki.jpg|183px|Welcome to DH electronics MediaWiki]]
|}

''Welcome to DH electronics new MediaWiki. This Wiki has the aim to provide our customers technical support for DH electronics products.''

{| style="width: 100%; color: #000000; border-collapse:collapse; border-style: solid; border-width: 1px 0 1px 0"
| [[Image:DHCM-120pix-ws.jpg|center|DH Computer on Module|link=DHCOM]]
|style="padding:10px;"|
=== [[DHCOM|DHCOM]] ===

A '''Computer On Module''' (COM) is a powerful embedded computer on a compact circuit board.

Our DHCOM modules offer high performance coupled with extensive features and interfaces, low power consumption as well as compact size.Possible applications for our modules are in visualization, multimedia, automation and communication devices

Click '''[[DHCOM|here]]''' to get support information for our '''[[DHCOM]]''' products.
| style="text-align: right;" |[[Image:IM6Modul.png|center|300px|COM iMX6-D2|link=COM iMX6-D2]]
|-
|style="border-style: solid; border-width: 1px 0 0 0;"|[[Image:XLON Logo in Schwarz von SD Kopie.jpg|center|120px|DH electronics XLON|link=DHCOM]]
|style="padding:10px; border-style: solid; border-width: 1px 0 0 0;"|
=== [[XLON|XLON]] ===

Our '''XLON''' products are network interfaces for LonWorks-Technology.

Click '''[[XLON|here]]''' to get support information for our '''[[XLON]]''' products.
| style="text-align: right; border-style: solid; border-width: 1px 0 0 0;" |[[Image:XLON U10.png|center|275px|XLON U10|link=COM iMX6-D2]]
|}

DHCOM iMX6-D2

2018-02-01T09:27:41Z

Lzenz: /* Update-Kernel */

{|
|
|
|-
|__TOC__
|[[Image:IM6Modul.png|600px|COM iMX6-D2]]
|}

== Hardware ==
*[[COM iMX6 Hardware|Hardware]]

{| class="wikitable" align="center" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* '''Cortex-A9 Freescale i.MX6 Solo/Dual(Lite)/Quad up to 1.2GHz'''
* 2D/3D graphics accelerator
* 0 - 512 MByte NAND flash memory (8 bit bus width) or 2 - 16 GByte eMMC flash
* 2 MB SPI boot flash
* 256 - 2048 MByte DDR3-1066 or DDR3-800
* On-board microSD card socket
* SD/MMC card interface, 4 bit SDIO
* LC display controller, 24 bit colors, 2048x1536 pixels
* LVDS 4-channel, max. 165 Mpixels/s
* On-board touch controller for 4-wire resistive touch screens
* Ethernet controller 10/100 Mbit, IEEE1588 conform
* USB 2.0 OTG high-speed
* USB 2.0 host high speed
* Full function UART
* Standard UART with hardware handshake support
* Standard UART
|valign="top" style="border: 0pt;" |
* CAN interface
* 2 x SPI interface
* 2 x I2CTM interface
* I²S Audio codec (1 x microphone, 1 x Line in, 1x Line out)
* Real-time clock (I2CTM connection), low power temperature compensated
* 12 bit analog input
* 1 kbit EEPROM with integrated MAC address
* 16 bit address/databus interface on SODIMM-200 socket
* PWM channel
* 23 GPIOs
* JTAG debug connection via FFC plug connector
* Industrial temperature range (-40°C to +85°C)
* SODIMM-200 socket with DHCOM pin assignment
|}

== Software Support ==
*[[COM iMX6 Bootloader U-Boot|Bootloader U-Boot]]
*[[DHCOM Update Mechanism|DHCOM Update Mechanism for i.MX6]]

*[[COM iMX6 Linux|Linux]]
*[[Yocto | Yocto on DHCOM i.MX6]]
*[[COM iMX6 WinCE|WinCE]]

== Downloads ==
==== U-Boot Sources ====
* [https://github.com/dh-electronics/u-boot-imx6qdl u-boot source code (GitHub)]
* [[media:U-boot-2015.10_iMX6_V1.1.0.6.zip|Download the latest U-Boot binary (V1.1.0.6)]]

==== Update-Kernel ====
* [[media:2018-02-01_imx6_updatekernel.zip|2018-02-01 update kernel (binary)]]

====Linux Kernel Sources / Prebuilt Kernels====
* Mainline
:* [https://github.com/dh-electronics/linux-imx6qdl/tree/dev/4.4.60_dhcom 4.4.60 mainline (GitHub)]
:* [[media:2017-07-25_imx6_4.4.60_boot.tar.bz2|4.4.60 mainline prebuilt Kernel (prepared for boot partition)]]
* Vendor
:* [https://github.com/dh-electronics/linux-imx6-vendor/tree/release/v4.1.15/20171102 4.1.15 vendor 2017-11-02 (GitHub)]
:* [[media:2017-11-02_imx6_4.1.15_boot.tar.bz2|4.1.15 vendor prebuilt Kernel (prepared for boot partition)]]
:* [https://github.com/dh-electronics/linux-imx6-vendor/tree/release/v3.10.17/20170804 3.10.17 vendor 2017-08-04 (GitHub)]
:* [[media:2017-08-04_imx6_3.10.17_boot.tar.bz2|3.10.17 vendor prebuilt Kernel (prepared for boot partition)]]

==== Debian based root file systems ====
* Debian alone

:* [[media:2017-05-29_jessie-armhf-base-rootfs.tar.gz|Based on Debian 8 "Jessie" (2017-05-29)]]

:* [[media:2014-10-30_developer-rootfs_DN6_imx6.tar.bz2|Based on Debian 6 "Squeeze" (2014-10-30)]] ''Remark:'' Shellshock (CVE-2014-6271) is already fixed.

* Debian Qt5

:* [[media:2017-10-06_jessie-armhf-imx6_fsl_4.1.15-rootfs.tar.gz|Based on Debian 8 "Jessie" + Qt5.9.1 (2017-10-06)]] ''Remark:'' It must be used with i.MX6 Vendor Kernel 4.1.15

:* [[media:2016-12-19_jessie-armhf-imx6_fsl_3.10.17-rootfs.tar.gz|Based on Debian 8 "Jessie" + Qt5.7.1 (2016-12-19)]] ''Remark:'' It must be used with i.MX6 Vendor Kernel 3.10.17

==== Virtual Machine for Application Development ====
* [[media:Debian Jessie v1.3.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

* [[media:Debian Squeeze v1.5pw.zip|Debian 6 "Squeeze" VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

==== Mainline Linux 4.4.x eMMC update package ====
* [[media:HD00035_2017-07-25_USBStick_eMMC_update_package.zip|i.MX6 Linux Kernel 4.4.60 with Debian Jessie Rootfilesystem]] Extract files to USB stick and use stick to update i.MX6 Solo, DualLite or Quad

==== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ====
* [[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs, RTC, UART, Watchdog, and more ]]
* [[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

==== WEC7 DHHalLib.dll (function library) ====
* [[media:DHHalLib_R04_2016_10_19.zip|Download DHHalLib Library Version 1.3.0.0]]
* [[media:DHHalLib_Test_App_Source_R03_2016_10_19.zip|DHHalLib Demo App Source Code ]]
* [[media:DHHalLib_Test_App_Binary_R03_2016_10_19.zip|DHHalLib Demo App Binary File]]
* [[media:CSharp_LibWrapper.zip|Download DHHalLib CSharp Demo Wrapper App ]]
* [[media:CSharp_LibWrapper_Binary.zip|Download DHHalLib CSharp Demo Wrapper App Binary File]]

==== WEC7 binary BSP ====
* [[media:2016-05-19_DHCOM_iMX6_BSP_BIN.zip|Download WEC7 binary BSP (date: 2016-05-19)]]

==== WEC2013 DHHalLib.dll (function library) ====
* [[media:DHHalLib_WEC2013_R08_2017_11_20.zip|Download DHHalLib Library Version 1.4.0.2]]
* [[media:DHHalLib_Test_App_Source_WEC2013_R05_2017_08_08.zip|DHHalLib Demo App Source Code ]]
* [[media:DHHalLib_Test_App_Binary_WEC2013_R05_2017_08_08.zip|DHHalLib Demo App Binary File]]
* [[media:CSharp_LibWrapper_Source_WEC2013_R06_2017_08_08.zip|Download DHHalLib CSharp Wrapper]]
* [[media:CSharp_DHHalLib_Wrapper_App_Source_WEC2013_R05_2017_08_08.zip|DHHalLib C# Demo App Source Code]]
* [[media:CSharp_DHHalLib_Wrapper_App_Binary_WEC2013_R05_2017_08_08.zip|DHHalLib C# Demo App Binary File]]

DHCOM iMX6-D2

2018-01-16T10:42:42Z

Lzenz: /* Debian based root file systems */

{|
|
|
|-
|__TOC__
|[[Image:IM6Modul.png|600px|COM iMX6-D2]]
|}

== Hardware ==
*[[COM iMX6 Hardware|Hardware]]

{| class="wikitable" align="center" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* '''Cortex-A9 Freescale i.MX6 Solo/Dual(Lite)/Quad up to 1.2GHz'''
* 2D/3D graphics accelerator
* 0 - 512 MByte NAND flash memory (8 bit bus width) or 2 - 16 GByte eMMC flash
* 2 MB SPI boot flash
* 256 - 2048 MByte DDR3-1066 or DDR3-800
* On-board microSD card socket
* SD/MMC card interface, 4 bit SDIO
* LC display controller, 24 bit colors, 2048x1536 pixels
* LVDS 4-channel, max. 165 Mpixels/s
* On-board touch controller for 4-wire resistive touch screens
* Ethernet controller 10/100 Mbit, IEEE1588 conform
* USB 2.0 OTG high-speed
* USB 2.0 host high speed
* Full function UART
* Standard UART with hardware handshake support
* Standard UART
|valign="top" style="border: 0pt;" |
* CAN interface
* 2 x SPI interface
* 2 x I2CTM interface
* I²S Audio codec (1 x microphone, 1 x Line in, 1x Line out)
* Real-time clock (I2CTM connection), low power temperature compensated
* 12 bit analog input
* 1 kbit EEPROM with integrated MAC address
* 16 bit address/databus interface on SODIMM-200 socket
* PWM channel
* 23 GPIOs
* JTAG debug connection via FFC plug connector
* Industrial temperature range (-40°C to +85°C)
* SODIMM-200 socket with DHCOM pin assignment
|}

== Software Support ==
*[[COM iMX6 Bootloader U-Boot|Bootloader U-Boot]]
*[[DHCOM Update Mechanism|DHCOM Update Mechanism for i.MX6]]

*[[COM iMX6 Linux|Linux]]
*[[Yocto | Yocto on DHCOM i.MX6]]
*[[COM iMX6 WinCE|WinCE]]

== Downloads ==
==== U-Boot Sources ====
* [https://github.com/dh-electronics/u-boot-imx6qdl u-boot source code (GitHub)]
* [[media:U-boot-2015.10_iMX6_V1.1.0.6.zip|Download the latest U-Boot binary (V1.1.0.6)]]

==== Update-Kernel ====
* [[media:2018-01-16_imx6_updatekernel.zip|2018-01-16 update kernel (binary)]]

====Linux Kernel Sources / Prebuilt Kernels====
* Mainline
:* [https://github.com/dh-electronics/linux-imx6qdl/tree/dev/4.4.60_dhcom 4.4.60 mainline (GitHub)]
:* [[media:2017-07-25_imx6_4.4.60_boot.tar.bz2|4.4.60 mainline prebuilt Kernel (prepared for boot partition)]]
* Vendor
:* [https://github.com/dh-electronics/linux-imx6-vendor/tree/release/v4.1.15/20171102 4.1.15 vendor 2017-11-02 (GitHub)]
:* [[media:2017-11-02_imx6_4.1.15_boot.tar.bz2|4.1.15 vendor prebuilt Kernel (prepared for boot partition)]]
:* [https://github.com/dh-electronics/linux-imx6-vendor/tree/release/v3.10.17/20170804 3.10.17 vendor 2017-08-04 (GitHub)]
:* [[media:2017-08-04_imx6_3.10.17_boot.tar.bz2|3.10.17 vendor prebuilt Kernel (prepared for boot partition)]]

==== Debian based root file systems ====
* Debian alone

:* [[media:2017-05-29_jessie-armhf-base-rootfs.tar.gz|Based on Debian 8 "Jessie" (2017-05-29)]]

:* [[media:2014-10-30_developer-rootfs_DN6_imx6.tar.bz2|Based on Debian 6 "Squeeze" (2014-10-30)]] ''Remark:'' Shellshock (CVE-2014-6271) is already fixed.

* Debian Qt5

:* [[media:2017-10-06_jessie-armhf-imx6_fsl_4.1.15-rootfs.tar.gz|Based on Debian 8 "Jessie" + Qt5.9.1 (2017-10-06)]] ''Remark:'' It must be used with i.MX6 Vendor Kernel 4.1.15

:* [[media:2016-12-19_jessie-armhf-imx6_fsl_3.10.17-rootfs.tar.gz|Based on Debian 8 "Jessie" + Qt5.7.1 (2016-12-19)]] ''Remark:'' It must be used with i.MX6 Vendor Kernel 3.10.17

==== Virtual Machine for Application Development ====
* [[media:Debian Jessie v1.3.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

* [[media:Debian Squeeze v1.5pw.zip|Debian 6 "Squeeze" VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

==== Mainline Linux 4.4.x eMMC update package ====
* [[media:HD00035_2017-07-25_USBStick_eMMC_update_package.zip|i.MX6 Linux Kernel 4.4.60 with Debian Jessie Rootfilesystem]] Extract files to USB stick and use stick to update i.MX6 Solo, DualLite or Quad

==== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ====
* [[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs, RTC, UART, Watchdog, and more ]]
* [[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

==== WEC7 DHHalLib.dll (function library) ====
* [[media:DHHalLib_R04_2016_10_19.zip|Download DHHalLib Library Version 1.3.0.0]]
* [[media:DHHalLib_Test_App_Source_R03_2016_10_19.zip|DHHalLib Demo App Source Code ]]
* [[media:DHHalLib_Test_App_Binary_R03_2016_10_19.zip|DHHalLib Demo App Binary File]]
* [[media:CSharp_LibWrapper.zip|Download DHHalLib CSharp Demo Wrapper App ]]
* [[media:CSharp_LibWrapper_Binary.zip|Download DHHalLib CSharp Demo Wrapper App Binary File]]

==== WEC7 binary BSP ====
* [[media:2016-05-19_DHCOM_iMX6_BSP_BIN.zip|Download WEC7 binary BSP (date: 2016-05-19)]]

==== WEC2013 DHHalLib.dll (function library) ====
* [[media:DHHalLib_WEC2013_R08_2017_11_20.zip|Download DHHalLib Library Version 1.4.0.2]]
* [[media:DHHalLib_Test_App_Source_WEC2013_R05_2017_08_08.zip|DHHalLib Demo App Source Code ]]
* [[media:DHHalLib_Test_App_Binary_WEC2013_R05_2017_08_08.zip|DHHalLib Demo App Binary File]]
* [[media:CSharp_LibWrapper_Source_WEC2013_R06_2017_08_08.zip|Download DHHalLib CSharp Wrapper]]
* [[media:CSharp_DHHalLib_Wrapper_App_Source_WEC2013_R05_2017_08_08.zip|DHHalLib C# Demo App Source Code]]
* [[media:CSharp_DHHalLib_Wrapper_App_Binary_WEC2013_R05_2017_08_08.zip|DHHalLib C# Demo App Binary File]]

DHCOM iMX6-D2

2018-01-16T10:41:40Z

Lzenz: /* Update-Kernel */

{|
|
|
|-
|__TOC__
|[[Image:IM6Modul.png|600px|COM iMX6-D2]]
|}

== Hardware ==
*[[COM iMX6 Hardware|Hardware]]

{| class="wikitable" align="center" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* '''Cortex-A9 Freescale i.MX6 Solo/Dual(Lite)/Quad up to 1.2GHz'''
* 2D/3D graphics accelerator
* 0 - 512 MByte NAND flash memory (8 bit bus width) or 2 - 16 GByte eMMC flash
* 2 MB SPI boot flash
* 256 - 2048 MByte DDR3-1066 or DDR3-800
* On-board microSD card socket
* SD/MMC card interface, 4 bit SDIO
* LC display controller, 24 bit colors, 2048x1536 pixels
* LVDS 4-channel, max. 165 Mpixels/s
* On-board touch controller for 4-wire resistive touch screens
* Ethernet controller 10/100 Mbit, IEEE1588 conform
* USB 2.0 OTG high-speed
* USB 2.0 host high speed
* Full function UART
* Standard UART with hardware handshake support
* Standard UART
|valign="top" style="border: 0pt;" |
* CAN interface
* 2 x SPI interface
* 2 x I2CTM interface
* I²S Audio codec (1 x microphone, 1 x Line in, 1x Line out)
* Real-time clock (I2CTM connection), low power temperature compensated
* 12 bit analog input
* 1 kbit EEPROM with integrated MAC address
* 16 bit address/databus interface on SODIMM-200 socket
* PWM channel
* 23 GPIOs
* JTAG debug connection via FFC plug connector
* Industrial temperature range (-40°C to +85°C)
* SODIMM-200 socket with DHCOM pin assignment
|}

== Software Support ==
*[[COM iMX6 Bootloader U-Boot|Bootloader U-Boot]]
*[[DHCOM Update Mechanism|DHCOM Update Mechanism for i.MX6]]

*[[COM iMX6 Linux|Linux]]
*[[Yocto | Yocto on DHCOM i.MX6]]
*[[COM iMX6 WinCE|WinCE]]

== Downloads ==
==== U-Boot Sources ====
* [https://github.com/dh-electronics/u-boot-imx6qdl u-boot source code (GitHub)]
* [[media:U-boot-2015.10_iMX6_V1.1.0.6.zip|Download the latest U-Boot binary (V1.1.0.6)]]

==== Update-Kernel ====
* [[media:2018-01-16_imx6_updatekernel.zip|2018-01-16 update kernel (binary)]]

====Linux Kernel Sources / Prebuilt Kernels====
* Mainline
:* [https://github.com/dh-electronics/linux-imx6qdl/tree/dev/4.4.60_dhcom 4.4.60 mainline (GitHub)]
:* [[media:2017-07-25_imx6_4.4.60_boot.tar.bz2|4.4.60 mainline prebuilt Kernel (prepared for boot partition)]]
* Vendor
:* [https://github.com/dh-electronics/linux-imx6-vendor/tree/release/v4.1.15/20171102 4.1.15 vendor 2017-11-02 (GitHub)]
:* [[media:2017-11-02_imx6_4.1.15_boot.tar.bz2|4.1.15 vendor prebuilt Kernel (prepared for boot partition)]]
:* [https://github.com/dh-electronics/linux-imx6-vendor/tree/release/v3.10.17/20170804 3.10.17 vendor 2017-08-04 (GitHub)]
:* [[media:2017-08-04_imx6_3.10.17_boot.tar.bz2|3.10.17 vendor prebuilt Kernel (prepared for boot partition)]]

==== Debian based root file systems ====
* Debian alone

:* [[media:2017-05-29_jessie-armhf-base-rootfs.tar.gz|Based on Debian 8 "Jessie" (2017-05-29)]]

:* [[media:2014-10-30_developer-rootfs_DN6_imx6.tar.bz2|Based on Debian 6 "Squeeze" (2014-10-30)]] ''Remark:'' Shellshock (CVE-2014-6271) is already fixed.

* Debian Qt5

:* [[media:2017-10-06_jessie-armhf-imx6_fsl_4.1.15-rootfs.tar.gz|Based on Debian 8 "Jessie" + Qt5.9.1 (2017-10-06)]] ''Remark:'' It must be used with i.MX6 Vendor Kernel 4.1.15

:* [[media:2016-12-19_jessie-armhf-imx6_fsl_3.10.17-rootfs.tar.gz|Based on Debian 8 "Jessie" + Qt5.7.1 (2016-12-19)]] ''Remark:'' It must be used with i.MX6 Vendor Kernel 3.10.17

==== Virtual Machine for Application Development ====
* [[media:Debian Jessie v1.3.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

* [[media:Debian Squeeze v1.5pw.zip|Debian 6 "Squeeze" VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

==== Mainline Linux 4.4.x eMMC update package ====
* [[media:HD00035_2017-07-25_USBStick_eMMC_update_package.zip|i.MX6 Linux Kernel 4.4.60 with Debian Jessie Rootfilesystem]] Extract files to USB stick and use stick to update i.MX6 Solo, DualLite or Quad

==== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ====
* [[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs, RTC, UART, Watchdog, and more ]]
* [[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

==== WEC7 DHHalLib.dll (function library) ====
* [[media:DHHalLib_R04_2016_10_19.zip|Download DHHalLib Library Version 1.3.0.0]]
* [[media:DHHalLib_Test_App_Source_R03_2016_10_19.zip|DHHalLib Demo App Source Code ]]
* [[media:DHHalLib_Test_App_Binary_R03_2016_10_19.zip|DHHalLib Demo App Binary File]]
* [[media:CSharp_LibWrapper.zip|Download DHHalLib CSharp Demo Wrapper App ]]
* [[media:CSharp_LibWrapper_Binary.zip|Download DHHalLib CSharp Demo Wrapper App Binary File]]

==== WEC7 binary BSP ====
* [[media:2016-05-19_DHCOM_iMX6_BSP_BIN.zip|Download WEC7 binary BSP (date: 2016-05-19)]]

==== WEC2013 DHHalLib.dll (function library) ====
* [[media:DHHalLib_WEC2013_R08_2017_11_20.zip|Download DHHalLib Library Version 1.4.0.2]]
* [[media:DHHalLib_Test_App_Source_WEC2013_R05_2017_08_08.zip|DHHalLib Demo App Source Code ]]
* [[media:DHHalLib_Test_App_Binary_WEC2013_R05_2017_08_08.zip|DHHalLib Demo App Binary File]]
* [[media:CSharp_LibWrapper_Source_WEC2013_R06_2017_08_08.zip|Download DHHalLib CSharp Wrapper]]
* [[media:CSharp_DHHalLib_Wrapper_App_Source_WEC2013_R05_2017_08_08.zip|DHHalLib C# Demo App Source Code]]
* [[media:CSharp_DHHalLib_Wrapper_App_Binary_WEC2013_R05_2017_08_08.zip|DHHalLib C# Demo App Binary File]]

DHCOM Flash Update

2017-08-21T09:24:09Z

Lzenz: /* Step by Step */

The following updates are possible with the Bootloader:
# Bootloader
# Splashimage
# Settings
# Linux kernel
# Linux rootfilesystem
# WinCE image
# Display adaptor EEPROM

If you are working with DHCOM AM335x or DHCOM i.MX6 please have a look at [[DHCOM_Update_Mechanism|DHCOM Update Mechanism]].

= User Manual =
== Step by Step ==
If you received an ''Update Image'' follow these steps to flash it to your target:
[[File:Update_stick_v1.PNG|thumb|right|200px|Files on the update media]]
# untar or unzip (or just copy if not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick
#* see picture on the right for an example how your update media should look after this step
# plug your usb stick into the USB Host port of the target
# switch on the power supply
# wait until the update has completed
#* progress can be followed at serial console
#* or on the LCD Display (if you have any)
# switch off the power supply
# remove the usb stick
# done

== Pitfalls ==
# Bootloader U-Boot does not recognice all types of usb sticks. FAT32 und MSDOS master boot record is required.
# ''Update Image'' is written to a subdirectory on the usb stick. This is not supported.

= Modes =
== Automatic Mode ==
:Is called after the start of the bootloader if the environment variable '''bootcmd''' contains '''update auto'''. The functionality tries to update the flash content '''via the DHupdate.ini file''' (Please have a look at [[DHCOM Flash Update#DHupdate.ini file|DHupdate.ini file]]). The update mechanism is searching for the update files on the specified storage devices. The update devices must be defined at the settings block (Please have a look at [[DHCOM Settings|DHCOM settings]]). With the DHupdate.ini file you have the possibility to run more then one updates, e.g. OS image and settings block.

== Commandline Mode ==
#Instruction: "update"
#:The functionality tries to update the flash content '''via the DHupdate.ini file'''. In contrast to Automatically Update (which you can start with '''update auto''') the update mechanism is searching on every available storage device for the update files.
#Instruction: "update <type> [filename]"
#:The functionality '''doesn't use the DHupdate.ini file'''. It allows only one update and the update mechanism is searching on every available storage device for the update files. With the <type> parameter you have to specify the update type.
#:The <type> parameter could be specified as follows:
#::* wince = WinCE image update + ENV update
#::* linux = Linux image update + ENV update
#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
#::* rootfs = Create or replace the linux root-filesystem which is stored in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the <code>reset</code> command) in the DHupdate.ini file. For further Details: [[DHCOM Update: Linux Root Filesystem|DHCOM Update: Linux Root Filesystem]]
#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.
#::* bootloader = Bootloader update
#:::Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.
#::* splash = Bootbitmap update
#::* settings = Settings block update
#::: Note: Please have a look at [[COM iMX25 Bootloader U-Boot#DHCOM settings|DHCOM settings]].
#::* eeprom = Display adaptor EEPROM update with DH settings
#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.
#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.
#:The [filename] parameter could be used to specify a non default filename. The default filenames are:
#::* wince = default file names nk.gz or nk.bin
#::* linux = default file name uImage + default script file name uImage.env
#::* rootfs = default file name fsroot.tar.gz
#::* bootloader = default file name u-boot.bin
#::* splash = default file name splash.bmp
#::* settings = default file name settings.bin
#::* eeprom = default file name eeprom.bin
#::* reset = no file to specify

= DHupdate.ini file =
:The DHupdate.ini file is a text file, which describes the user specified update mechanism.

:[[Image:DHupdate_file_layout.png|700px]]

:For DHupdate.ini File Example, please have a look at the Please have a look at [[COM iMX25 Bootloader U-Boot#Downloads|Download area iMX25]] or [[COM AM35 Bootloader U-Boot#Downloads|Download area AM35x]].
:'''Notes:'''
:*If you update the [[DHCOM Settings|DHCOM settings]], it is possible to use the new settings for the update progress notifications on the display, by inserting the "refresh" command to the [update] section. Example:
[update]
settings 00_PV.bin
refresh
splash DH_800x480.bmp
...
[end]

:*It is necessary to use UNIX End Of Line conversion!!!
:*The order of the bitmap-filenames in the section <code>display</code> tells the system when to display which bitmap.

:'''Update progress LED description''':
::The LED GPIO is activated as soon as update has started. This takes roughly 6 - 8 seconds. If the update was finished without an error, the LED GPIO is deactivated. If an error occurs during the update the LED GPIO begins blinking.
::LED error code:
::1 LED blinking interval = DHupdate.ini File error (Wrong file content or no valid file found)
::2 LED blinking interval = Necessary File for Update not found
::3 LED blinking interval = Flash write or erase error
::4 LED blinking interval = Wrong OS Image type (e.g. no WinCE *.gz or *.bin file)
::5 LED blinking interval = Specified file not valid (e.g. linux *.env file)
::6 LED blinking interval = Image file size is to large

= Overview - Flow Chart =
:[[Image:Flash Update Overview.png|1020px]]

DHCOM Flash Update

2017-08-21T07:57:29Z

Lzenz: /* User Manual */

The following updates are possible with the Bootloader:
# Bootloader
# Splashimage
# Settings
# Linux kernel
# Linux rootfilesystem
# WinCE image
# Display adaptor EEPROM

If you are working with DHCOM AM335x or DHCOM i.MX6 please have a look at [[DHCOM_Update_Mechanism|DHCOM Update Mechanism]].

= User Manual =
== Step by Step ==
If you received an ''Update Image'' follow these steps to flash it to your target:
[[File:Update_stick_v1.PNG|thumb|right|200px|Files on the update media]]
# untar or unzip (or just copy of not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick
#* see picture on the right for an example how your update media should look after this step
# plug your usb stick into the USB Host port of the target
# switch on the power supply
# wait until the update has completed
#* progress can be followed at serial console
#* or on the LCD Display (if you have any)
# switch off the power supply
# remove the usb stick
# done
== Pitfalls ==
# Bootloader U-Boot does not recognice all types of usb sticks. FAT32 und MSDOS master boot record is required.
# ''Update Image'' is written to a subdirectory on the usb stick. This is not supported.

= Modes =
== Automatic Mode ==
:Is called after the start of the bootloader if the environment variable '''bootcmd''' contains '''update auto'''. The functionality tries to update the flash content '''via the DHupdate.ini file''' (Please have a look at [[DHCOM Flash Update#DHupdate.ini file|DHupdate.ini file]]). The update mechanism is searching for the update files on the specified storage devices. The update devices must be defined at the settings block (Please have a look at [[DHCOM Settings|DHCOM settings]]). With the DHupdate.ini file you have the possibility to run more then one updates, e.g. OS image and settings block.

== Commandline Mode ==
#Instruction: "update"
#:The functionality tries to update the flash content '''via the DHupdate.ini file'''. In contrast to Automatically Update (which you can start with '''update auto''') the update mechanism is searching on every available storage device for the update files.
#Instruction: "update <type> [filename]"
#:The functionality '''doesn't use the DHupdate.ini file'''. It allows only one update and the update mechanism is searching on every available storage device for the update files. With the <type> parameter you have to specify the update type.
#:The <type> parameter could be specified as follows:
#::* wince = WinCE image update + ENV update
#::* linux = Linux image update + ENV update
#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
#::* rootfs = Create or replace the linux root-filesystem which is stored in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the <code>reset</code> command) in the DHupdate.ini file. For further Details: [[DHCOM Update: Linux Root Filesystem|DHCOM Update: Linux Root Filesystem]]
#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.
#::* bootloader = Bootloader update
#:::Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.
#::* splash = Bootbitmap update
#::* settings = Settings block update
#::: Note: Please have a look at [[COM iMX25 Bootloader U-Boot#DHCOM settings|DHCOM settings]].
#::* eeprom = Display adaptor EEPROM update with DH settings
#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.
#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.
#:The [filename] parameter could be used to specify a non default filename. The default filenames are:
#::* wince = default file names nk.gz or nk.bin
#::* linux = default file name uImage + default script file name uImage.env
#::* rootfs = default file name fsroot.tar.gz
#::* bootloader = default file name u-boot.bin
#::* splash = default file name splash.bmp
#::* settings = default file name settings.bin
#::* eeprom = default file name eeprom.bin
#::* reset = no file to specify

= DHupdate.ini file =
:The DHupdate.ini file is a text file, which describes the user specified update mechanism.

:[[Image:DHupdate_file_layout.png|700px]]

:For DHupdate.ini File Example, please have a look at the Please have a look at [[COM iMX25 Bootloader U-Boot#Downloads|Download area iMX25]] or [[COM AM35 Bootloader U-Boot#Downloads|Download area AM35x]].
:'''Notes:'''
:*If you update the [[DHCOM Settings|DHCOM settings]], it is possible to use the new settings for the update progress notifications on the display, by inserting the "refresh" command to the [update] section. Example:
[update]
settings 00_PV.bin
refresh
splash DH_800x480.bmp
...
[end]

:*It is necessary to use UNIX End Of Line conversion!!!
:*The order of the bitmap-filenames in the section <code>display</code> tells the system when to display which bitmap.

:'''Update progress LED description''':
::The LED GPIO is activated as soon as update has started. This takes roughly 6 - 8 seconds. If the update was finished without an error, the LED GPIO is deactivated. If an error occurs during the update the LED GPIO begins blinking.
::LED error code:
::1 LED blinking interval = DHupdate.ini File error (Wrong file content or no valid file found)
::2 LED blinking interval = Necessary File for Update not found
::3 LED blinking interval = Flash write or erase error
::4 LED blinking interval = Wrong OS Image type (e.g. no WinCE *.gz or *.bin file)
::5 LED blinking interval = Specified file not valid (e.g. linux *.env file)
::6 LED blinking interval = Image file size is to large

= Overview - Flow Chart =
:[[Image:Flash Update Overview.png|1020px]]

DHCOM Flash Update

2017-08-21T07:52:11Z

Lzenz: /* User Manual */

The following updates are possible with the Bootloader:
# Bootloader
# Splashimage
# Settings
# Linux kernel
# Linux rootfilesystem
# WinCE image
# Display adaptor EEPROM

If you are working with DHCOM AM335x or DHCOM i.MX6 please have a look at [[DHCOM_Update_Mechanism|DHCOM Update Mechanism]].

= User Manual =
If you received an ''Update Image'' follow these steps to flash it to your target:
[[File:Update_stick_v1.PNG|thumb|right|200px|Files on the update media]]
# untar or unzip (or just copy of not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick
#* see picture on the right for an example how your update media should look after this step
# plug your usb stick into the USB Host port of the target
# switch on the power supply
# wait until the update has completed
#* progress can be followed at serial console
#* or on the LCD Display (if you have any)
# switch off the power supply
# remove the usb stick
# done

= Modes =
== Automatic Mode ==
:Is called after the start of the bootloader if the environment variable '''bootcmd''' contains '''update auto'''. The functionality tries to update the flash content '''via the DHupdate.ini file''' (Please have a look at [[DHCOM Flash Update#DHupdate.ini file|DHupdate.ini file]]). The update mechanism is searching for the update files on the specified storage devices. The update devices must be defined at the settings block (Please have a look at [[DHCOM Settings|DHCOM settings]]). With the DHupdate.ini file you have the possibility to run more then one updates, e.g. OS image and settings block.

== Commandline Mode ==
#Instruction: "update"
#:The functionality tries to update the flash content '''via the DHupdate.ini file'''. In contrast to Automatically Update (which you can start with '''update auto''') the update mechanism is searching on every available storage device for the update files.
#Instruction: "update <type> [filename]"
#:The functionality '''doesn't use the DHupdate.ini file'''. It allows only one update and the update mechanism is searching on every available storage device for the update files. With the <type> parameter you have to specify the update type.
#:The <type> parameter could be specified as follows:
#::* wince = WinCE image update + ENV update
#::* linux = Linux image update + ENV update
#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
#::* rootfs = Create or replace the linux root-filesystem which is stored in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the <code>reset</code> command) in the DHupdate.ini file. For further Details: [[DHCOM Update: Linux Root Filesystem|DHCOM Update: Linux Root Filesystem]]
#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.
#::* bootloader = Bootloader update
#:::Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.
#::* splash = Bootbitmap update
#::* settings = Settings block update
#::: Note: Please have a look at [[COM iMX25 Bootloader U-Boot#DHCOM settings|DHCOM settings]].
#::* eeprom = Display adaptor EEPROM update with DH settings
#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.
#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.
#:The [filename] parameter could be used to specify a non default filename. The default filenames are:
#::* wince = default file names nk.gz or nk.bin
#::* linux = default file name uImage + default script file name uImage.env
#::* rootfs = default file name fsroot.tar.gz
#::* bootloader = default file name u-boot.bin
#::* splash = default file name splash.bmp
#::* settings = default file name settings.bin
#::* eeprom = default file name eeprom.bin
#::* reset = no file to specify

= DHupdate.ini file =
:The DHupdate.ini file is a text file, which describes the user specified update mechanism.

:[[Image:DHupdate_file_layout.png|700px]]

:For DHupdate.ini File Example, please have a look at the Please have a look at [[COM iMX25 Bootloader U-Boot#Downloads|Download area iMX25]] or [[COM AM35 Bootloader U-Boot#Downloads|Download area AM35x]].
:'''Notes:'''
:*If you update the [[DHCOM Settings|DHCOM settings]], it is possible to use the new settings for the update progress notifications on the display, by inserting the "refresh" command to the [update] section. Example:
[update]
settings 00_PV.bin
refresh
splash DH_800x480.bmp
...
[end]

:*It is necessary to use UNIX End Of Line conversion!!!
:*The order of the bitmap-filenames in the section <code>display</code> tells the system when to display which bitmap.

:'''Update progress LED description''':
::The LED GPIO is activated as soon as update has started. This takes roughly 6 - 8 seconds. If the update was finished without an error, the LED GPIO is deactivated. If an error occurs during the update the LED GPIO begins blinking.
::LED error code:
::1 LED blinking interval = DHupdate.ini File error (Wrong file content or no valid file found)
::2 LED blinking interval = Necessary File for Update not found
::3 LED blinking interval = Flash write or erase error
::4 LED blinking interval = Wrong OS Image type (e.g. no WinCE *.gz or *.bin file)
::5 LED blinking interval = Specified file not valid (e.g. linux *.env file)
::6 LED blinking interval = Image file size is to large

= Overview - Flow Chart =
:[[Image:Flash Update Overview.png|1020px]]

File:Update stick v1.PNG

2017-08-21T07:48:32Z

Lzenz:

DHCOM Flash Update

2017-08-21T07:47:45Z

Lzenz: /* User Manual */

The following updates are possible with the Bootloader:
# Bootloader
# Splashimage
# Settings
# Linux kernel
# Linux rootfilesystem
# WinCE image
# Display adaptor EEPROM

If you are working with DHCOM AM335x or DHCOM i.MX6 please have a look at [[DHCOM_Update_Mechanism|DHCOM Update Mechanism]].

= User Manual =
If you received an ''Update Image'' follow these steps to flash it to your target:
# untar or unzip (or just copy of not bundled and/or compressed) the ''Update Image'' to the root directory of a usb stick
# plug your usb stick into the USB Host port of the target
# switch on the power supply
# wait until the update has completed
## progress can be followed at serial console
## or on the LCD Display (if you have any)
# switch off the power supply
# remove the usb stick
# done

= Modes =
== Automatic Mode ==
:Is called after the start of the bootloader if the environment variable '''bootcmd''' contains '''update auto'''. The functionality tries to update the flash content '''via the DHupdate.ini file''' (Please have a look at [[DHCOM Flash Update#DHupdate.ini file|DHupdate.ini file]]). The update mechanism is searching for the update files on the specified storage devices. The update devices must be defined at the settings block (Please have a look at [[DHCOM Settings|DHCOM settings]]). With the DHupdate.ini file you have the possibility to run more then one updates, e.g. OS image and settings block.

== Commandline Mode ==
#Instruction: "update"
#:The functionality tries to update the flash content '''via the DHupdate.ini file'''. In contrast to Automatically Update (which you can start with '''update auto''') the update mechanism is searching on every available storage device for the update files.
#Instruction: "update <type> [filename]"
#:The functionality '''doesn't use the DHupdate.ini file'''. It allows only one update and the update mechanism is searching on every available storage device for the update files. With the <type> parameter you have to specify the update type.
#:The <type> parameter could be specified as follows:
#::* wince = WinCE image update + ENV update
#::* linux = Linux image update + ENV update
#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
#::* rootfs = Create or replace the linux root-filesystem which is stored in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the <code>reset</code> command) in the DHupdate.ini file. For further Details: [[DHCOM Update: Linux Root Filesystem|DHCOM Update: Linux Root Filesystem]]
#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.
#::* bootloader = Bootloader update
#:::Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.
#::* splash = Bootbitmap update
#::* settings = Settings block update
#::: Note: Please have a look at [[COM iMX25 Bootloader U-Boot#DHCOM settings|DHCOM settings]].
#::* eeprom = Display adaptor EEPROM update with DH settings
#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.
#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.
#:The [filename] parameter could be used to specify a non default filename. The default filenames are:
#::* wince = default file names nk.gz or nk.bin
#::* linux = default file name uImage + default script file name uImage.env
#::* rootfs = default file name fsroot.tar.gz
#::* bootloader = default file name u-boot.bin
#::* splash = default file name splash.bmp
#::* settings = default file name settings.bin
#::* eeprom = default file name eeprom.bin
#::* reset = no file to specify

= DHupdate.ini file =
:The DHupdate.ini file is a text file, which describes the user specified update mechanism.

:[[Image:DHupdate_file_layout.png|700px]]

:For DHupdate.ini File Example, please have a look at the Please have a look at [[COM iMX25 Bootloader U-Boot#Downloads|Download area iMX25]] or [[COM AM35 Bootloader U-Boot#Downloads|Download area AM35x]].
:'''Notes:'''
:*If you update the [[DHCOM Settings|DHCOM settings]], it is possible to use the new settings for the update progress notifications on the display, by inserting the "refresh" command to the [update] section. Example:
[update]
settings 00_PV.bin
refresh
splash DH_800x480.bmp
...
[end]

:*It is necessary to use UNIX End Of Line conversion!!!
:*The order of the bitmap-filenames in the section <code>display</code> tells the system when to display which bitmap.

:'''Update progress LED description''':
::The LED GPIO is activated as soon as update has started. This takes roughly 6 - 8 seconds. If the update was finished without an error, the LED GPIO is deactivated. If an error occurs during the update the LED GPIO begins blinking.
::LED error code:
::1 LED blinking interval = DHupdate.ini File error (Wrong file content or no valid file found)
::2 LED blinking interval = Necessary File for Update not found
::3 LED blinking interval = Flash write or erase error
::4 LED blinking interval = Wrong OS Image type (e.g. no WinCE *.gz or *.bin file)
::5 LED blinking interval = Specified file not valid (e.g. linux *.env file)
::6 LED blinking interval = Image file size is to large

= Overview - Flow Chart =
:[[Image:Flash Update Overview.png|1020px]]

DHCOM Flash Update

2017-08-21T07:35:15Z

Lzenz:

The following updates are possible with the Bootloader:
# Bootloader
# Splashimage
# Settings
# Linux kernel
# Linux rootfilesystem
# WinCE image
# Display adaptor EEPROM

If you are working with DHCOM AM335x or DHCOM i.MX6 please have a look at [[DHCOM_Update_Mechanism|DHCOM Update Mechanism]].

= User Manual =

= Modes =
== Automatic Mode ==
:Is called after the start of the bootloader if the environment variable '''bootcmd''' contains '''update auto'''. The functionality tries to update the flash content '''via the DHupdate.ini file''' (Please have a look at [[DHCOM Flash Update#DHupdate.ini file|DHupdate.ini file]]). The update mechanism is searching for the update files on the specified storage devices. The update devices must be defined at the settings block (Please have a look at [[DHCOM Settings|DHCOM settings]]). With the DHupdate.ini file you have the possibility to run more then one updates, e.g. OS image and settings block.

== Commandline Mode ==
#Instruction: "update"
#:The functionality tries to update the flash content '''via the DHupdate.ini file'''. In contrast to Automatically Update (which you can start with '''update auto''') the update mechanism is searching on every available storage device for the update files.
#Instruction: "update <type> [filename]"
#:The functionality '''doesn't use the DHupdate.ini file'''. It allows only one update and the update mechanism is searching on every available storage device for the update files. With the <type> parameter you have to specify the update type.
#:The <type> parameter could be specified as follows:
#::* wince = WinCE image update + ENV update
#::* linux = Linux image update + ENV update
#:::Note: If you run <code>update linux</code>, u-boot is searching for an update ENV script too. This script modifies the u-boot environment for Linux. The name of the script has to be the same as the kernel-image-name with the additional ending .env. You can also run an update without a script file. In this case u-boot only updates the kernel-image and the ENV remains unchanged. It is possible to update only the environment of u-boot without a kernel update by inserting the filename of the ENV script too.
#::* rootfs = Create or replace the linux root-filesystem which is stored in the NAND-Flash. The rootfs update has to be the last item (or second to last item if you insert the <code>reset</code> command) in the DHupdate.ini file. For further Details: [[DHCOM Update: Linux Root Filesystem|DHCOM Update: Linux Root Filesystem]]
#::: Note: To run a ''"NAND-Flash root-filesystem update"'' you need a special linux-kernel which must have the filename ''"uImage.update"''. This kernel must be available in the same diretory on your update-media as the DHupdate.ini file. Depending on your setup you have to update the u-boot environment too.
#::* bootloader = Bootloader update
#:::Note: The ENV in Flash memory is created on the first start of u-boot. If you run a bootloader update and the ENV at the new bootloader has changed, the ENV in Flash memory remains unchanged with the bootloader update. But you could delete the ENV block in flash memory before the update, then u-boot will create the new default ENV at the next start after the bootloader update.
#::* splash = Bootbitmap update
#::* settings = Settings block update
#::: Note: Please have a look at [[COM iMX25 Bootloader U-Boot#DHCOM settings|DHCOM settings]].
#::* eeprom = Display adaptor EEPROM update with DH settings
#::* reset = Execute a reset after a successfull update. A reset can only be the last item in a DHupdate.ini file.
#::: Note: Be careful with the reset command. You can easily build a endless update loop by mistake.
#:The [filename] parameter could be used to specify a non default filename. The default filenames are:
#::* wince = default file names nk.gz or nk.bin
#::* linux = default file name uImage + default script file name uImage.env
#::* rootfs = default file name fsroot.tar.gz
#::* bootloader = default file name u-boot.bin
#::* splash = default file name splash.bmp
#::* settings = default file name settings.bin
#::* eeprom = default file name eeprom.bin
#::* reset = no file to specify

= DHupdate.ini file =
:The DHupdate.ini file is a text file, which describes the user specified update mechanism.

:[[Image:DHupdate_file_layout.png|700px]]

:For DHupdate.ini File Example, please have a look at the Please have a look at [[COM iMX25 Bootloader U-Boot#Downloads|Download area iMX25]] or [[COM AM35 Bootloader U-Boot#Downloads|Download area AM35x]].
:'''Notes:'''
:*If you update the [[DHCOM Settings|DHCOM settings]], it is possible to use the new settings for the update progress notifications on the display, by inserting the "refresh" command to the [update] section. Example:
[update]
settings 00_PV.bin
refresh
splash DH_800x480.bmp
...
[end]

:*It is necessary to use UNIX End Of Line conversion!!!
:*The order of the bitmap-filenames in the section <code>display</code> tells the system when to display which bitmap.

:'''Update progress LED description''':
::The LED GPIO is activated as soon as update has started. This takes roughly 6 - 8 seconds. If the update was finished without an error, the LED GPIO is deactivated. If an error occurs during the update the LED GPIO begins blinking.
::LED error code:
::1 LED blinking interval = DHupdate.ini File error (Wrong file content or no valid file found)
::2 LED blinking interval = Necessary File for Update not found
::3 LED blinking interval = Flash write or erase error
::4 LED blinking interval = Wrong OS Image type (e.g. no WinCE *.gz or *.bin file)
::5 LED blinking interval = Specified file not valid (e.g. linux *.env file)
::6 LED blinking interval = Image file size is to large

= Overview - Flow Chart =
:[[Image:Flash Update Overview.png|1020px]]

USB Mass Storage Gadget (or MSG)

2017-06-09T05:38:21Z

Lzenz: /* Apply Backing Storage */

The Mass Storage Gadget (MSG) provides support for the USB Mass Storage class. The System appears to the host (PC) as a SCSI disk drive if the USB-OTG port is used for the connection. A file or a block device is used as a backing store for the drive.

__TOC__

== General Information ==

For further information about details of the USB Mass Storage Gadget Driver and how to use it have a look at [http://www.linux-usb.org/gadget/file_storage.html www.linux-usb.org/gadget/file_storage.html] and [https://www.kernel.org/doc/Documentation/usb/mass-storage.txt www.kernel.org]. It is possible to run the driver as loadable kernel module. The steps below descripe how to compile the g_mass_storage module statically into the kernel image.

== Configure the USB-OTG Port ==

On i.MX25 and AM35x to use USB Gadget features the USB-OTG Port has to be initialized in USB slave mode. Add <code>"otg_mode=device"</code> to the kernel commandline on the bootloader console.

On DHCOM boards it is possible to use the u-boot environment variable <tt>"linux_add_param"</tt>:
# enter bootloader console with DEL/BS Key
# <tt>setenv linux_add_param otg_mode=device</tt>
# <tt>saveenv</tt>

'''Remark:''' The DHCOM i.MX6 and AM335x have dual role usb controllers und drivers. It is not necessary to specify the otg_mode if you use this platforms.

== Prepare the Kernel ==

Prepare the Linux Kernel Sources to be able to compile.

Open a console window and go to the root directory of the kernel sources and start the kernel configuration dialog:
* <tt> ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make menuconfig </tt>

Enable the following items:
* Device Drivers --> USB Support --> USB Gadget Support
* Device Drivers --> USB Support --> USB Gadget Support --> USB Peripheral Controller
:: choose the matching device controller:
::: * DHCOM AM35x, AM335x: Inventra HDRC USB Peripheral (TI, ADI, ...)
::: * DHCOM iMX25, iMX6: Freescale Highspeed USB DR Peripheral Controller
* Device Drivers --> USB Support --> USB Gadget Support --> USB Gadget Drivers --> Mass Storage Gadget

Rebuild the Linux kernel and install the kernel to your board. (See DHCOM Update for details.)

== How to Use? ==

=== Static Kernel Module ===
If the '''g_mass_storage''' module has been statically built into the kernel image you have to provide the following parameters to the kernel module via kernel command line (bootargs in u-boot):
* <tt> g_mass_storage.removable=1 </tt>
* <tt> g_mass_storage.luns=1 </tt>

=== Apply Backing Storage ===
On the running device you can use the following line to add the FAT32 partition of the microSD-card to the usb gadget driver:
* <tt>am35x# echo /dev/mmcblk0p1 > /sys/devices/platform/omap/musb-am35x/musb-hdrc/gadget/lun0/file</tt>
If you do not work the AM35x there are some differences in the path of the sysfs. (Easy to find when you go to <tt> cd /sys </tt> and type <tt> find . -name "lun*" </tt>)

Now, if you connect the USB-OTG port to your host pc the specified device appears as a drive.

'''Remark:'''
* If you run windows then you can only use block devices with filesystems supported by windows (FAT32).
* Do not use the rootfilesystem partition. This will cause damage to the filesystem. Only one "Writer" on each Filesystem is allowed!

=== '''IMPORTANT WARNING!''' ===
* While MSG is running and the gadget is connected to a USB host, that USB host will use the backing storage as a private disk drive. It will not expect to see any changes in the backing storage other than the ones it makes. Extraneous changes are liable to corrupt the filesystem and may even crash the host. Only one system (normally, the USB host) may write to the backing storage, and if one system is writing that data, no other should be reading it. The only safe way to share the backing storage between the host and the gadget's operating system at the same time is to make it read-only on both sides.

Have a look at [http://www.linux-usb.org/gadget/file_storage.html www.linux-usb.org/gadget/file_storage.html] to get a step by step guide how to work with „Backing Storage Files“.

Template:DebianVM Development

2017-05-17T06:12:35Z

Lzenz: /* Use Virtualbox instead of VMware Player/Workstation */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code>$ sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code>$ mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>$ cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code>$ rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server with <code>4 /etc/init.d/nfs-kernel-server restart</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code>$ sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code>$ mkdir /work/tftp </code>
#* Edit config: <code>$ sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server with <code>$ /etc/init.d/tftp-hpa restart</code>

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== Use Virtualbox instead of VMware Player/Workstation ==

[[media:DOC_VMware_Machine_mit_VirtualBox_starten_V1.0_2015-10-21.pdf| VMware Maschine mit VirtualBox starten (German)]]

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2017-05-17T06:12:18Z

Lzenz: /* Use Virtualbox instead of VMware Player/Workstation */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code>$ sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code>$ mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>$ cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code>$ rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server with <code>4 /etc/init.d/nfs-kernel-server restart</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code>$ sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code>$ mkdir /work/tftp </code>
#* Edit config: <code>$ sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server with <code>$ /etc/init.d/tftp-hpa restart</code>

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== Use Virtualbox instead of VMware Player/Workstation ==

[[media:DOC_VMware_Maschine_mit_VirtualBox_starten_V1.0_2015-10-21.pdf| VMware Machine mit VirtualBox starten (German)]]

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2017-05-17T06:11:06Z

Lzenz: /* Use Virtualbox instead of VMware Player/Workstation */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code>$ sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code>$ mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>$ cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code>$ rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server with <code>4 /etc/init.d/nfs-kernel-server restart</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code>$ sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code>$ mkdir /work/tftp </code>
#* Edit config: <code>$ sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server with <code>$ /etc/init.d/tftp-hpa restart</code>

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== Use Virtualbox instead of VMware Player/Workstation ==

[[media:DOC_VMware_Machine_mit_VirtualBox_starten_V1.0_2015-10-21.pdf| VMware Machine mit VirtualBox starten (German)]]

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

File:DOC VMware Machine mit VirtualBox starten V1.0 2015-10-21.pdf

2017-05-17T06:09:35Z

Lzenz: Guide: How to starte a VM created with VMware with VirtualBox

Guide: How to starte a VM created with VMware with VirtualBox

Template:DebianVM Development

2017-05-17T06:08:18Z

Lzenz: /* Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code>$ sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code>$ mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>$ cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code>$ rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server with <code>4 /etc/init.d/nfs-kernel-server restart</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code>$ sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code>$ mkdir /work/tftp </code>
#* Edit config: <code>$ sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server with <code>$ /etc/init.d/tftp-hpa restart</code>

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== Use Virtualbox instead of VMware Player/Workstation ==

[[media:DHCOM_HAL.zip| VMware Machine mit VirtualBox starten (German)]]

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2017-03-27T11:46:52Z

Lzenz: /* Prepare the virtual machine */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code>$ sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code>$ mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>$ cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code>$ rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server with <code>4 /etc/init.d/nfs-kernel-server restart</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code>$ sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code>$ mkdir /work/tftp </code>
#* Edit config: <code>$ sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server with <code>$ /etc/init.d/tftp-hpa restart</code>

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2017-03-27T11:45:21Z

Lzenz: /* Prepare the virtual machine */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code> sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code> mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code> rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code> sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code> mkdir /work/tftp </code>
#* Edit config: <code> sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory
#* Restart the tftp-server by using this commando
#*<code>''/etc/init.d/tftp-hpa restart''</code>

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2017-03-27T11:44:06Z

Lzenz: /* Prepare the virtual machine */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code> sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code> mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code> rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#* <code>/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)</code>
#** The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code> sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code> mkdir /work/tftp </code>
#* Edit config: <code> sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2017-03-27T11:43:14Z

Lzenz: /* Setup the DHCOM Module for TFTP/NFS Boot */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code> sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code> mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code> rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#*: <code>'''/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
#*: The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code> sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code> mkdir /work/tftp </code>
#* Edit config: <code> sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. It is possible to work with DHCP, too. For further information see [https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt]
* Enter U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal while switching on the power supply of the target
* Set IP addresses
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2017-03-27T11:39:00Z

Lzenz: /* Booting via TFTP/NFS */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code> sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code> mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code> rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#*: <code>'''/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
#*: The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code> sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code> mkdir /work/tftp </code>
#* Edit config: <code> sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

Template:DebianVM Development

2017-03-27T11:37:00Z

Lzenz: /* Setup the DHCOM Module for TFTP/NFS Boot */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code> sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code> mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code> rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#*: <code>'''/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
#*: The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code> sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code> mkdir /work/tftp </code>
#* Edit config: <code> sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># env set rootfs 'root=/dev/nfs nfsroot=192.168.178.90:/work/nfsroot/ ip=192.168.178.91:192.168.178.90::255.255.255.0:dhcom:eth0:none'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T11:36:37Z

Lzenz: /* Prepare the virtual machine */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code> sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code> mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code> rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the <tt>'''/etc/exports'''</tt> file
#*: <code>'''/work/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
#*: The <tt>'''X'''</tt> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code> sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code> mkdir /work/tftp </code>
#* Edit config: <code> sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T11:35:28Z

Lzenz: /* Prepare the virtual machine */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Install thf nfs server: <code> sudo apt-get install nfs-kernel-server </code>
#* Create a nfsservice directory: <code> mkdir /work/nfsroot </code>
#* Place the root file system in the folder <code>cd /work/nfsroot; sudo tar xf jessie....tar.gz </code>
#* Remove network config from rootfs <code> rm /work/nfsroot/etc/systemd/network/wired-dhcp.network</code>
#* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
#*: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
#*: The <code>'''X'''</code> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code> sudo apt-get install tftpd-hpa </code>
#* Create a tftp service directory: <code> mkdir /work/tftp </code>
#* Edit config: <code> sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T11:29:54Z

Lzenz: /* Booting via TFTP/NFS */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
#* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
#*: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
#*: The <code>'''X'''</code> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''
#* Install a tftp server : <code> sudo apt-get install tftpd-hpa </code>
#* Edit config: <code> sudo vi /etc/default/tftpd-hpa </code>
#** Take care that TFTP_DIRECTORY points to your tftp service directory, for example '/work/tftp'
#* Copy Kernel and DeviceTree into the tftp service directory

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T10:52:47Z

Lzenz: /* Prepare the virtual machine */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
#* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
#* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
#*: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
#*: The <code>'''X'''</code> must be substituted by our network settings
#* Restart the nfs-server by using this commando
#*<code>''/etc/init.d/nfs-kernel-server restart''</code>
# '''Setup tftp-hpa server'''

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T10:51:03Z

Lzenz: /* Prepare the virtual machine */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
# '''Setup nfs-kernel-server'''
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
# '''Setup tftp-hpa server'''

==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T10:49:19Z

Lzenz: /* Debian 8 "Jessie" VMware Image */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

=== Booting via TFTP/NFS ===
==== Prepare the virtual machine ====
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
==== Setup the DHCOM Module for TFTP/NFS Boot ====
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T10:36:56Z

Lzenz: /* Setup the DHCOM Module for TFTP/NFS Boot */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: '''save it to be permanent'''
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T10:36:28Z

Lzenz: /* Setup the DHCOM Module for TFTP/NFS Boot */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootargs and boot
{| class="wikitable"
|<tt># run linuxargs</tt> <tt># bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: save it to be permanent
{| class="wikitable"
|<tt># env set bootcmd 'tftp ${loadaddr} zImage; tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb; run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt> <tt># env save</tt>
|}

Template:DebianVM Development

2017-03-27T10:31:33Z

Lzenz: /* Setup the DHCOM Module for TFTP/NFS Boot */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Setup the DHCOM Module for TFTP/NFS Boot ===
This example works with static IP addresses and is tested with DHCOM i.MX6 U-Boot 2015.10 and Kernle 4.4.38. 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootcmd
{| class="wikitable"
|<tt># env set bootcmd 'run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: save it to be permanent
{| class="wikitable"
|<tt># env save</tt>
|}
* boot target
{| class="wikitable"
|<tt># boot</tt>

Template:DebianVM Development

2017-03-27T10:30:28Z

Lzenz: /* Booting via NFS */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via TFTP/NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootcmd
{| class="wikitable"
|<tt># env set bootcmd 'run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: save it to be permanent
{| class="wikitable"
|<tt># env save</tt>
|}
* boot target
{| class="wikitable"
|<tt># boot</tt>

Template:DebianVM Development

2017-03-27T10:30:04Z

Lzenz: /* Booting via NFS */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Jessie v1.2.zip|Debian 8 "Jessie" VMware Image]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [[media:Qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb|'''qmake-sysroot-am33-crossarmhf_5.7.1-1.0''']] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [[media:Debian Squeeze v1.5pw.zip|Debian Squeeze VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== 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
{| class="wikitable"
|<tt># env set serverip 192.168.178.90</tt> <tt># env set ipaddr 192.168.178.91</tt>
|}
* bootargs for nfs root
{| class="wikitable"
|<tt># 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'</tt>
|}
* load Linux kernel and devicetree with tftp (change filename and path to match you setup)
{| class="wikitable"
|<tt># tftp ${loadaddr} zImage</tt> <tt># tftp ${fdt_addr} dtbs/imx6dl-dhcom3B-pdk2.dtb</tt>
|}
* set bootcmd
{| class="wikitable"
|<tt># env set bootcmd 'run linuxargs; bootz ${loadaddr} - ${fdt_addr}'</tt>
|}
* optional: save it to be permanent
{| class="wikitable"
|<tt># env save</tt>
|}
* boot target
{| class="wikitable"
|<tt># boot</tt>

COM AM335x Bootloader U-Boot

2017-01-18T07:32:43Z

Lzenz: /* Start Build */

== FAQ ==
:'''Q: Initialization of MAC address in the bootloader?'''
:'''A:''' At the first start, the bootloader reads the MAC addresses (2x) from internal Control Module of the AM335x and creates env variable ethaddr and eth1addr. The env variable ethaddr or eth1addr could be changed during lifetime to any other MAC address. If you like to get back the original MAC address, please remove ethaddr, save environment and restart the system.

:'''Q: The automatic update is not executed before the operating system boots!'''
:'''A:''' Check if the command <code> update auto </code> is included in the bootloader environment variable <code>bootcmd</code> or in a script-variable which is called within <code> bootcmd </code> before <code> bootm </code>.

:'''Q: The automatic update does not work with my desired update-media!'''
:'''A:''' The command <code> update auto </code> can be configured with flags within the DHCOM settings.bin block. It is possible to disable a interface for the update mechanism. You can run a update from a disabled interface if you use the command <code> update </code> without the argument <code> auto </code>. Take care about the correct setup of your media.

== Downloads ==
Please have a look at the[[COM_AM335-D2#Downloads| AM335x Downloads]] section.

== Enter Bootloader Console ==
#Connect DHCOM UART1) via null modem cable to the RS232 Port of your PC
#Start terminal program (e.g. Tera Term) on the Host PC with the following settings:
#:Baud rate: 115200
#:Data: 8 bit
#:Parity: none
#:Stop bits: 1 bit
#:Flow control: none
#Press "del" on the Host PC during Core Module system start to enter bootloader console

==U-boot console commands==
=== SPI Flash ===

:'''SPI Flash Init'''

:{| class="wikitable"
|''<tt>sf probe</tt>''
|}

:Example: <tt>sf probe</tt>

:Description: Initializes the OnBoard SPI Flash

:'''SPI Flash Read'''

:{| class="wikitable"
|''<tt>sf read <SDRAM address> <SPI Flash address> <Bytes></tt>''
|}

:Example: <tt>sf read 80000000 0 100</tt>

:Description: Copies 256Bytes from SPI Flash address 0x0 to SDRAM address 0x1000_0000

:'''SPI Flash Write'''

:{| class="wikitable"
|''<tt>sf write <SDRAM address> <SPI Flash address> <Bytes></tt>''
|}

:Example: <tt>sf write 80000000 40000 10000</tt>

:Description: Copies 64kByte from SDRAM address 0x8000_0000 to SPI Flash address 0x4_0000

:'''SPI Flash Erase'''

:{| class="wikitable"
|''<tt>sf erase <SPI Flash address> <Bytes></tt>''
|}

:Example: <tt>sf erase 100000 1000</tt>

:Description: Deletes SPI Flash content from address 0x10_0000 to 0x10_0FFF

:Note: The Bytes information needs to be sector size aligned!

=== NAND-Flash ===
We provide the DHCOM AM335x with NAND '''or''' eMMC. The following commands are reserved for the NAND version of DHCOM AM335x.

:'''Read from NAND-Flash Device'''

:{| class="wikitable"
|''<tt>nand read <SDRAM address> <NAND Flash address> <Bytes></tt>''
|}

:Example: <tt>nand read 80000000 400000 b40000</tt>

:Description: Copies 11,25MByte from NAND Flash address 0x40_0000 to SDRAM address 0x8000_0000

:'''Erase NAND-Flash blocks'''

:{| class="wikitable"
|''<tt>nand erase <Block base address> <Bytes></tt>''
|}

:Example: <tt>nand erase 400000 40000</tt>

:Description: Deletes NAND Flash content from address 0x40_0000 to 0x43_FFFF

:Note: The Bytes information needs to be block size aligned!

:'''Write to NAND-Flash Device'''

:{| class="wikitable"
|''<tt>nand write <SDRAM address> <NAND-Flash address> <Bytes></tt>''
|}

:Example: <tt>nand write 80000000 400000 b40000</tt>

:Description: Copies 11,25MByte from SDRAM address 0x8000_0000 to NAND Flash address 0x40_0000

:Note: The Bytes information needs to be page size aligned!

:'''Show bad NAND-Flash blocks'''

:{| class="wikitable"
|''<tt>nand bad</tt>''
|}

:Description: Shows the bad NAND-Flash blocks.

:'''Show NAND-Flash content'''

:{| class="wikitable"
|''<tt>nand dump <NAND-Flash address></tt>''
|}

:Example: <tt>nand dump 400000</tt>

:Description: Shows the content of the specified NAND-Flash block

=== UBI Filesystem ===

:'''Partition Definition'''

:{| class="wikitable"
|''<tt>mtdparts</tt>''
|}

:Example: <tt>mtdparts</tt>

:Description: Shows the current nand flash partitions. In case of AM335x one default partition set, which includes the entire flash. For linux that partition is used to create two volumes "boot" and "rootfs".
:Note: In case of UBIFS it is better to have one big partition with different volumes instead of many small partitions, because the wear leveling process is always applied to every partition.

device nand0 <gpmi-nand>, # parts = 1
#: name size offset mask_flags
0: gpmc-nand 0x20000000 0x00000000 0
active partition: nand0,0 - (gpmc-nand) 0x20000000 @ 0x00000000

:'''Set or show active partition'''

:{| class="wikitable"
|''<tt>ubi part <partition name></tt>''
|}

:Example: <tt>ubi part gpmi-nand</tt>

:Description: Show or set current partition. In AM335x default case this is shold always set to gpmc-nand.

:'''Mount UBI volume'''

:{| class="wikitable"
|''<tt>ubifsmount <UBI device>:<volume name></tt>''
|}

:Example: <tt>ubifsmount ubi0:boot</tt>

:Description: Mount UBIFS volume. The default name of the first AM335x volume is "boot".

:'''List files'''

:{| class="wikitable"
|''<tt>ubifsls <directory></tt>''
|}

:Example 1: <tt>ubifsls</tt>

:Description: List files in a UBIFS directory.

:'''Load Files from UBI volume'''

:{| class="wikitable"
|''<tt>ubifsload <SDRAM address> <directory+filename></tt>''
|}

:Example 1: <tt>ubifsload 10100000 zimage</tt>

:Description: Load file from an UBIFS filesystem to memory.

:'''Unmount UBI volume'''

:{| class="wikitable"
|''<tt>ubifsumount</tt>''
|}

:Example: <tt>ubifsumount</tt>

:Description: Unmount current volume.

=== SD/MMC Card ===

:'''Switch between MicroSD, SD Slot and eMMC'''

:{| class="wikitable"
|''<tt>mmc dev <Slot number> <Partition number></tt>''
|}

:Example: <tt>mmc dev 0</tt>

:Description: Switch between SD/MMC Slots:
:* 0 --> SD/MMC or MicroSD Slot
:* 1 --> eMMC Flash

:'''Initialize SD/MMC Card'''

:{| class="wikitable"
|''<tt>mmc rescan</tt>''
|}
:Description: Initialize new inserted SD Card

:'''Show SD/MMC information'''

:{| class="wikitable"
|''<tt>mmcinfo</tt>''
|}

:Description: Shows SD/MMC device information
Device: FSL_SDHC
Manufacturer ID: 45
OEM: 100
Name: SEM08
Tran Speed: 52000000
Rd Block Len: 512
MMC version 4.41
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit

:'''Write to MicroSD, SD Slot and eMMC'''

:{| class="wikitable"
|''<tt>mmc write <SDRAM address> <block number> <block count> </tt>''
|}

:Example: <tt>mmc write 81000000 5000 400</tt>
:Description: Write 512kByte (device block size is 512Byte) to the eMMC offset 10MByte.

:'''Read from MicroSD, SD Slot and eMMC'''

:{| class="wikitable"
|''<tt>mmc read <SDRAM address> <block number> <block count> </tt>''
|}

:Example: <tt>mmc read 81000000 5000 400</tt>
:Description: Read 512kByte (device block size is 512Byte) from the eMMC offset 10MByte.

=== FAT - EXT2 - EXT4 - Filesystem ===

:'''NOTE: All EXT2 commands must also be used for ext4'''

:'''Show Filesystem information'''

:{| class="wikitable"
|''<tt>fatinfo <interface> <device></tt>''
|}

:Example: <tt>fatinfo mmc 1</tt>

Interface: MMC
Device 1: Vendor: Man 094150 Snr 266e068c Rev: 1.0 Prod: AF UD
Type: Removable Hard Disk
Capacity: 121.2 MB = 0.1 GB (248320 x 512)
Partition 1: Filesystem: FAT16 "NO NAME "

:'''List files'''

:{| class="wikitable"
|''<tt>fatls <interface> <device> <directory></tt>''
|}

:{| class="wikitable"
|''<tt>ext2ls <interface> <device> <directory></tt>''
|}

:Example 1: <tt>fatls mmc 1</tt>

:Example 2: <tt>fatls mmc 1 /folder</tt>

:'''Load Files from SD Card to SDRAM'''

:{| class="wikitable"
|''<tt>fatload <interface> <device> <SDRAM address> <directory+filename></tt>''
|}

:{| class="wikitable"
|''<tt>ext2load <interface> <device> <SDRAM address> <directory+filename></tt>''
|}

:Example 1: <tt>fatload mmc 1 80100000 nk.gz</tt>

:Example 2: <tt>fatload mmc 1 80100000 /folder/nk.gz</tt>

=== Ethernet ===

:'''Load File via TFTP to SDRAM'''

:{| class="wikitable"
|''<tt>tftp <SDRAM address> <directory+filename></tt>''
|}

:Example: <tt>tftp 80100000 nk.gz</tt>

:Example TFTP Server: "Winagents TFTP Server Manager"

:Note: For TFTP download it is necessary to config the ENV variables "ipaddr" and "serverip"

:'''Load File via TFTP to SDRAM using DHCP'''

:{| class="wikitable"
|''<tt>dhcp <SDRAM address> <directory+filename></tt>''
|}

:Example: <tt>dhcp 80100000 nk.gz</tt>

:Example TFTP Server: "Winagents TFTP Server Manager"

:Note: It is necessary to config the ENV variable "serverip" with the ip-address of your TFTP-Server

:'''Ping'''

:{| class="wikitable"
|''<tt>ping <IP address></tt>''
|}

:Example: <tt>ping 192.168.55.32</tt>

:'''Read PHY register via MII interface'''

:{| class="wikitable"
|''<tt>mii dump <PHY address> <PHY register></tt>''
|}

:Example: <tt>mii dump 0 0</tt>

:Remark: The standard MII registers 0-5 are supported by this command.

=== Unzip ===

:{| class="wikitable"
|''<tt>unzip <source address> <destination address></tt>''
|}

:Example: <tt>unzip 82900000 80100000</tt>

:Note: The unzip command is supporting the gzip file format.

=== Bitmap ===

:'''Information'''

:{| class="wikitable"
|''<code>bmp info <Bitmap address></code>''
|}

Image size : 800 x 480
Bits per pixel: 8
Compression : 0

:'''Display'''

:{| class="wikitable"
|'' <code>bmp display <Bitmap SDRAM address> [x y]</code>''
|}
:Note: It is necessary to load bitmap file to memory address with an offset of an odd multiple of +2, since the use of a four-byte alignment will cause alignment exceptions at run-time.

=== Memory ===

:'''Display'''

:{| class="wikitable"
|''<tt>md[.b, .w, .l] <address> [count]</tt>''
|}

:Example: <tt>md.b 80100000 100</tt>

:'''Write'''

:{| class="wikitable"
|''<tt> mw[.b, .w, .l] <address> <value> [count]</tt>''
|}

:Example: <tt>mw.b 80100000 aa 100</tt>

:Description: Writes the value 0xaa to the next 0x100 bytes from the address 0x8010_0000.

:'''Copy'''

:{| class="wikitable"
|''<tt> cp[.b, .w, .l] <source> <destination> <count></tt>''
|}

=== Show DHCOM Settings ===

:{| class="wikitable"
|''<tt> settings </tt>''
|}

:Example:
VALIDATION_ID: "DH"
DISPLAY_ID: 0x00
LENGTH: 0x2c
X_RESOLUTION: 800 pixel
Y_RESOLUTION: 480 pixel
PIXEL_CLOCK: 22200 kHz
LCD_CONFIG_FLAGS: 0x3e3
HSW: 64 pixel clocks
VSW: 2 line clocks
HFP: 42 pixel clocks
HBP: 86 pixel clocks
VFP: 10 line clocks
VBP: 33 line clocks
DATALINES: 16
ACB: 0
ACBI: 0
GPIO_DIR: 0x01ff
GPIO_STATE: 0x0000
HW_CONFIG_FLAGS: 0x001e

=== I2C ===

:'''List available devices'''

:{| class="wikitable"
|''<tt>i2c probe</tt>''
|}

Valid devices:
0 = OnBoard I2C portDHCOM I2C port 1
1 = not connected
2 = DHCOM I2C port 1

:'''Read'''

:{| class="wikitable"
|''<tt>i2c md <I2C address> <start address> <end address></tt>''
|}

:Example: <tt>i2c md 57 10 20</tt>

:Description: Reads 16 Bytes from the address 0x10 to address 0x20.

:'''Write'''

:{| class="wikitable"
|''<tt>i2c mw <I2C address> <I2C register> <Value> <Bytes></tt>''
|}

:Example: <tt>i2c mw 57 0 aa 5</tt>

:Description: Writes 0xaa to 5 Bytes from the offset 0.

=== Environment ===
==== Print Variables ====
{| class="wikitable"
|''<tt>env print</tt>''
|}

==== Set Variables ====
{| class="wikitable"
|''<tt>env set [-f] name [arg ...]</tt>''
|}
''Example:'' <code>env set ipaddr 192.168.55.2</code>

''Note:'' If you need to edit "bootcmd" it is necessary to insert ";" between the unique commands. You can enter ";" at the command line with "\;".

==== Save Variables ====
{| class="wikitable"
|''<code>env save</code>''
|}

==== Delete Variable ====
{| class="wikitable"
|''<code>env delete <ENV name></code>''
|}

==== Revert Complete Environment to Default ====
{| class="wikitable"
|''<code>env default -a</code>''
|}

==== Import from Textfile ====
{| class="wikitable"
|''<code>env import -t <SDRAM address> $filesize</code>''
|}

Example:
<code>fatload mmc 0 0x10000000 uEnv.txt</code>
<code>env import -t 0x10000000 $filesize</code>

Important:
The uEnv.txt file should be in unix format. Also make sure that there is an empty line at the end of the file.

==[[DHCOM Update Mechanism |How to do Updates]]==

== Display and Hardware settings ==
=== DHCOM settings and Splash bitmap ===
:The DHCOM settings are used to setup display and special hardware parameters. For detailed description please have a look at [[DHCOM Settings|'''How to create a settings.bin file''']].
:The DHCOM settings file and the splash bitmap are loaded via the env variables "'''load_settings_bin'''" and "'''load_splash'''" during startup from boot partition. The default content of these env variables is:
settings_bin_file=default_settings.bin
splash_file=splash.bmp
load_settings_bin=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${settings_bin_file}
load_splash=load mmc ${mmcdev}:${mmcpart} ${splashimage} ${splash_file}

:'''Note:''' The DHCOM display settings can also be stored in external eeprom (address 0x50 / 7bit I2C address) which is connected to DHCOM I2C1 port. If eeprom is available and DISP_ADPT_EEPRM flag is set to 1, the settings from eeprom override the settings from boot partition!
:Next you can see the settings load order:
:[[Image:DISP_ADPT_EE_check.png|600px]]

=== Displaying a splash screen with u-boot ===
'''Notes:'''
* This is possible with u-boot version v0.1.0.0 or newer.
* Only RGB interface is supported.
'''The process to set it up is the following:'''
* Configure your display parameters with DHCOM settings generator ([[DHCOM Settings|'''How to create a settings.bin file''']]) 
* Generate settings bin file with settings generator.
* Copy settings bin file to boot partition on boot media (eMMC, NAND or microSD card).
* Generate your splash bitmap (bitmap with 8 bit color depth).
* Copy also bmp file to boot partition.
* Start DHCOM module and enter u-boot console.
* Set env variable “<code>settings_bin_file</code>” with settings bin filename: Example: <code>env set settings_bin_file 10_LG_7inch_LB070WV8.bin</code>
* Set env variable “<code>splash_file</code>” with bitmap filename: Example: <code>env set splash_file 800x480_splash_DHCOM_iMX6.bmp</code>
:'''Remark:''' This can be done in the uLinuxEnv.txt, too.
* Save u-boot environment to flash: <code>saveenv</code>
* Restart the system --> Splash bitmap should now be displayed from the bootloader.

=== Display disabled by default ===
:With default u-boot configuration u-boot '''doesn't''' initialize the Display interface. This feature can be activated by deleting the "'''panel'''" environment variable. But also with deactivated display interface, the bootlaoder reads the display settings and pass the settings to the linux kernel.
panel="no_panel": Display interface is deactiveted in u-boot and backlight is powered off.
panel="RGB": Default DH 4,3" display is selected.
panel=deleted: u-boot initialize display by DH settings file.

=== Backlight enable GPIO ===
: If ENV variable "panel" is set to "no_panel" the backlight enable GPIO (defined via DHCOM settings file or eeprom settings) will be disabled from the bootloader during startup.
: If ENV variable "panel" is deleted, the backlight enable GPIO is activated or deactivated in relation to BL_ON flag of DHCOM settings file.
: Note: Supported by U-Boot DH VERSION v0.4.2.5 or higher for iMX6

== Building U-Boot (and MLO) ==
=== Prepare Build Environment ===
* Download and start the Virtual Machine based on Debian 8 (see [[COM_AM335-D2#Downloads| AM335x Downloads]])
* Install Denx ELDK 5.4 to /opt (Available at [ftp://ftp.denx.de/pub/eldk/5.4/iso/ ftp://ftp.denx.de/pub/eldk/5.4/iso/]: we use eldk-5.4-armv7a.iso)
=== Get Sources ===
{| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" |
|
1. Start a terminal on Linux 
2. <tt># ''git clone [https://github.com/dh-electronics/u-boot-am33x.git https://github.com/dh-electronics/u-boot-am33x.git]''</tt> 
3. <tt># ''cd u-boot-am33x''</tt> 
4. <tt># ''git checkout release/v0.4.0.1'' # checkout latest/required branch or tag</tt>
|}
=== Start Build===
{| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" |
|
6. <tt># ''./uboot_make [nand]''</tt> # add argument 'nand' to include nand support, not suitable for eMMC devices 
|}
* Your new <tt>u-boot.img</tt> file is available in <tt>u-boot-am33x/</tt>
* If your build does fail please check content of uboot_make and adjust PATH.
* Use <tt>MLO.byteswap</tt> if you need to replace the MLO.
'''''Attention: Risk of bricking the Device!!'''''

COM iMX6 Bootloader U-Boot

2017-01-18T07:30:45Z

Lzenz: /* Environment */

== FAQ ==
:'''Q: Initialization of MAC address in the bootloader?'''
:'''A:''' At the first start, the bootloader reads the MAC address from EEPROM, write it to eFuses and creates env variable ethaddr. The env variable ethaddr could be changed during lifetime to any other MAC address. If you like to get back the original MAC address, please remove ethaddr, save environment and restart the system. In addition to that the env variable ethaddr would be initialized again with eeprom MAC addresss.

:'''Q: The automatic update is not executed before the operating system boots!'''
:'''A:''' Check if the command <code> update auto </code> is included in the bootloader environment variable <code>bootcmd</code> or in a script-variable which is called within <code> bootcmd </code> before <code> bootm </code>.

:'''Q: The automatic update does not work with my desired update-media!'''
:'''A:''' The command <code> update auto </code> can be configured with flags within the DHCOM settings.bin block. It is possible to disable a interface for the update mechanism. You can run a update from a disabled interface if you use the command <code> update </code> without the argument <code> auto </code>.

== Downloads ==
Please have a look at the[[COM_iMX6-D2#Downloads| i.MX6 Downloads]] section.

== Enter Bootloader Console ==
:#Connect DHCOM UART1 (FF UART) via null modem cable to the RS232 Port of your PC
:#Start terminal program (e.g. Tera Term) on the Host PC with the following settings:
:#:Baud rate: 115200
:#:Data: 8 bit
:#:Parity: none
:#:Stop bits: 1 bit
:#:Flow control: none
:#Press "del" on the Host PC during Core Module system start to enter bootloader console

==U-boot console commands==
=== SPI Flash ===

:'''SPI Flash Init'''

:{| class="wikitable"
|''<code>sf probe</code>''
|}

:Example: <code>sf probe</code>

:Description: Initializes the OnBoard SPI Flash

:'''SPI Flash Read'''

:{| class="wikitable"
|''<code>sf read <SDRAM address> <SPI Flash address> <Bytes></code>''
|}

:Example: <code>sf read 10000000 0 100</code>

:Description: Copies 256Bytes from SPI Flash address 0x0 to SDRAM address 0x1000_0000

:'''SPI Flash Write'''

:{| class="wikitable"
|''<code>sf write <SDRAM address> <SPI Flash address> <Bytes></code>''
|}

:Example: <code>sf write 10000000 40000 10000</code>

:Description: Copies 64kByte from SDRAM address 0x1000_0000 to SPI Flash address 0x4_0000

:'''SPI Flash Erase'''

:{| class="wikitable"
|''<code>sf erase <SPI Flash address> <Bytes></code>''
|}

:Example: <code>sf erase 100000 1000</code>

:Description: Deletes SPI Flash content from address 0x10_0000 to 0x10_0FFF

:Note: The Bytes information needs to be sector size aligned!

=== NAND-Flash ===

:'''Read from NAND-Flash Device'''

:{| class="wikitable"
|''<code>nand read <SDRAM address> <NAND Flash address> <Bytes></code>''
|}

:Example: <code>nand read 80000000 400000 b40000</code>

:Description: Copies 11,25MByte from NAND Flash address 0x40_0000 to SDRAM address 0x8000_0000

:'''Erase NAND-Flash blocks'''

:{| class="wikitable"
|''<code>nand erase <Block base address> <Bytes></code>''
|}

:Example: <code>nand erase 400000 40000</code>

:Description: Deletes NAND Flash content from address 0x40_0000 to 0x43_FFFF

:Note: The Bytes information needs to be block size aligned!

:'''Write to NAND-Flash Device'''

:{| class="wikitable"
|''<code>nand write <SDRAM address> <NAND-Flash address> <Bytes></code>''
|}

:Example: <code>nand write 80000000 400000 b40000</code>

:Description: Copies 11,25MByte from SDRAM address 0x8000_0000 to NAND Flash address 0x40_0000

:Note: The Bytes information needs to be page size aligned!

:'''Show bad NAND-Flash blocks'''

:{| class="wikitable"
|''<code>nand bad</code>''
|}

:Description: Shows the bad NAND-Flash blocks.

:'''Show NAND-Flash content'''

:{| class="wikitable"
|''<code>nand dump <NAND-Flash address></code>''
|}

:Example: <code>nand dump 400000</code>

:Description: Shows the content of the specified NAND-Flash block

=== UBI Filesystem ===

:'''Partition Definition'''

:{| class="wikitable"
|''<code>mtdparts</code>''
|}

:Example: <code>mtdparts</code>

:Description: Shows the current nand flash partitions. In case of i.MX6 one default partition set, which includes the entire flash. For linux that partition is used to create two volumes "boot" and "rootfs".
:Note: In case of UBIFS it is better to have one big partition with different volumes instead of many small partitions, because the wear leveling process is always applied to every partition.

device nand0 <gpmi-nand>, # parts = 1
#: name size offset mask_flags
0: gpmi-nand 0x20000000 0x00000000 0
active partition: nand0,0 - (gpmi-nand) 0x20000000 @ 0x00000000

:'''Set or show active partition'''

:{| class="wikitable"
|''<code>ubi part <partition name></code>''
|}

:Example: <code>ubi part gpmi-nand</code>

:Description: Show or set current partition. In i.MX6 default case this is shold always set to gpmi-nand.

:'''Mount UBI volume'''

:{| class="wikitable"
|''<code>ubifsmount <UBI device>:<volume name></code>''
|}

:Example: <code>ubifsmount ubi0:boot</code>

:Description: Mount UBIFS volume. The default name of the first i.MX6 volume is "boot".

:'''List files'''

:{| class="wikitable"
|''<code>ubifsls <directory></code>''
|}

:Example 1: <code>ubifsls</code>

:Description: List files in a UBIFS directory.

:'''Load Files from UBI volume'''

:{| class="wikitable"
|''<code>ubifsload <SDRAM address> <directory+filename></code>''
|}

:Example 1: <code>ubifsload 10100000 zimage</code>

:Description: Load file from an UBIFS filesystem to memory.

:'''Unmount UBI volume'''

:{| class="wikitable"
|''<code>ubifsumount</code>''
|}

:Example: <code>ubifsumount</code>

:Description: Unmount current volume.

=== SD/MMC Card ===

:'''Switch between MicroSD, SD Slot and eMMC'''

:{| class="wikitable"
|''<code>mmc dev <Slot number> <Partition number></code>''
|}

:Example: <code>mmc dev 0</code>

:Description: Switch between SD/MMC Slots: 0 --> SD/MMC Slot, 1 --> MicroSD Slot, 2 --> eMMC Flash
:Note eMMC flash partition number: 0 --> User partition, 1 --> Boot partition 1, 2 --> Boot partition 2

:'''Initialize SD/MMC Card'''

:{| class="wikitable"
|''<code>mmc rescan</code>''
|}
:Description: Initialize new inserted SD Card

:'''Show SD/MMC information'''

:{| class="wikitable"
|''<code>mmcinfo</code>''
|}

:Description: Shows SD/MMC device information
Device: FSL_SDHC
Manufacturer ID: 45
OEM: 100
Name: SEM08
Tran Speed: 52000000
Rd Block Len: 512
MMC version 4.41
High Capacity: Yes
Capacity: 7.3 GiB
Bus Width: 8-bit

:'''Write to MicroSD, SD Slot and eMMC'''

:{| class="wikitable"
|''<code>mmc write <SDRAM address> <block number> <block count> </code>''
|}

:Example: <code>mmc write 11000000 5000 400</code>
:Description: Write 512kByte (device block size is 512Byte) to the eMMC offset 10MByte.

:'''Read from MicroSD, SD Slot and eMMC'''

:{| class="wikitable"
|''<code>mmc read <SDRAM address> <block number> <block count> </code>''
|}

:Example: <code>mmc read 11000000 5000 400</code>
:Description: Read 512kByte (device block size is 512Byte) from the eMMC offset 10MByte.

=== FAT - EXT2 - EXT4 - Filesystem ===

:'''NOTE: All EXT2 commands must also be used for ext4'''

:'''Show Filesystem information'''

:{| class="wikitable"
|''<code>fatinfo <interface> <device></code>''
|}

:Example: <code>fatinfo mmc 1</code>

Interface: MMC
Device 1: Vendor: Man 094150 Snr 266e068c Rev: 1.0 Prod: AF UD
Type: Removable Hard Disk
Capacity: 121.2 MB = 0.1 GB (248320 x 512)
Partition 1: Filesystem: FAT16 "NO NAME "

:'''List files'''

:{| class="wikitable"
|''<code>fatls <interface> <device> <directory></code>''
|}

:{| class="wikitable"
|''<code>ext2ls <interface> <device> <directory></code>''
|}

:Example 1: <code>fatls mmc 1</code>

:Example 2: <code>fatls mmc 1 /folder</code>

:'''Load Files from SD Card to SDRAM'''

:{| class="wikitable"
|''<code>fatload <interface> <device> <SDRAM address> <directory+filename></code>''
|}

:{| class="wikitable"
|''<code>ext2load <interface> <device> <SDRAM address> <directory+filename></code>''
|}

:Example 1: <code>fatload mmc 1 10100000 nk.gz</code>

:Example 2: <code>fatload mmc 1 10100000 /folder/nk.gz</code>

=== Ethernet ===

:'''Load File via TFTP to SDRAM'''

:{| class="wikitable"
|''<code>tftp <SDRAM address> <directory+filename></code>''
|}

:Example: <code>tftp 80100000 nk.gz</code>

:Example TFTP Server: "Winagents TFTP Server Manager"

:Note: For TFTP download it is necessary to config the ENV variables "ipaddr" and "serverip"

:'''Load File via TFTP to SDRAM using DHCP'''

:{| class="wikitable"
|''<code>dhcp <SDRAM address> <directory+filename></code>''
|}

:Example: <code>dhcp 80100000 nk.gz</code>

:Example TFTP Server: "Winagents TFTP Server Manager"

:Note: It is necessary to config the ENV variable "serverip" with the ip-address of your TFTP-Server

:'''Ping'''

:{| class="wikitable"
|''<code>ping <IP address></code>''
|}

:Example: <code>ping 192.168.55.32</code>

:'''Read PHY register via MII interface'''

:{| class="wikitable"
|''<code>mii dump <PHY address> <PHY register></code>''
|}

:Example: <code>mii dump 0 0</code>

:Remark: The standard MII registers 0-5 are supported by this command. When you are working with a DHCOM i.MX6 module only PHY address "0" is allowed.

=== Unzip ===

:{| class="wikitable"
|''<code>unzip <source address> <destination address></code>''
|}

:Example: <code>unzip 12900000 10100000</code>

:Note: The unzip command is supporting the gzip file format.

=== Bitmap ===

:'''Information'''

:{| class="wikitable"
|''<code>bmp info <Bitmap address></code>''
|}

Image size : 800 x 480
Bits per pixel: 8
Compression : 0

:'''Display'''

:{| class="wikitable"
|'' <code>bmp display <Bitmap SDRAM address> [x y]</code>''
|}
:Note: It is necessary to load bitmap file to memory address with an offset of an odd multiple of +2, since the use of a four-byte alignment will cause alignment exceptions at run-time.

=== Memory ===

:'''Display'''

:{| class="wikitable"
|''<code>md[.b, .w, .l] <address> [count]</code>''
|}

:Example: <code>md.b 80100000 100</code>

:'''Write'''

:{| class="wikitable"
|''<code> mw[.b, .w, .l] <address> <value> [count]</code>''
|}

:Example: <code>mw.b 80100000 aa 100</code>

:Description: Writes the value 0xaa to the next 0x100 bytes from the address 0x8010_0000.

:'''Copy'''

:{| class="wikitable"
|''<code> cp[.b, .w, .l] <source> <destination> <count></code>''
|}

=== Show DHCOM Settings ===

:{| class="wikitable"
|''<code> settings </code>''
|}

:Example:
VALIDATION_ID: "DH"
DISPLAY_ID: 0x00
LENGTH: 0x2c
X_RESOLUTION: 800 pixel
Y_RESOLUTION: 480 pixel
PIXEL_CLOCK: 22200 kHz
LCD_CONFIG_FLAGS: 0x3e3
HSW: 64 pixel clocks
VSW: 2 line clocks
HFP: 42 pixel clocks
HBP: 86 pixel clocks
VFP: 10 line clocks
VBP: 33 line clocks
DATALINES: 16
ACB: 0
ACBI: 0
GPIO_DIR: 0x01ff
GPIO_STATE: 0x0000
HW_CONFIG_FLAGS: 0x001e

=== I2C ===

:'''List available devices'''

:{| class="wikitable"
|''<code>i2c probe</code>''
|}

Valid devices:
0 = DHCOM I2C port 1
1 = DHCOM I2C port 2
2 = i.MX6 OnBoard I2C port

:'''Read'''

:{| class="wikitable"
|''<code>i2c md <I2C address> <start address> <end address></code>''
|}

:Example: <code>i2c md 57 10 20</code>

:Description: Reads 16 Bytes from the address 0x10 to address 0x20.

:'''Write'''

:{| class="wikitable"
|''<code>i2c mw <I2C address> <I2C register> <Value> <Bytes></code>''
|}

:Example: <code>i2c mw 57 0 aa 5</code>

:Description: Writes 0xaa to 5 Bytes from the offset 0.

=== Environment ===

:'''Show ENV variables'''

:{| class="wikitable"
|''<code>env print</code>''
|}

bootdelay=0
baudrate=38400
ipaddr=192.168.55.230
serverip=192.168.55.36
gatewayip=192.168.55.36
netmask=255.255.255.0
frias=5
...
Environment size: 449/262140 bytes

:'''Set ENV variables'''

:{| class="wikitable"
|''<code>env set <ENV name> <ENV value></code>''
|}
:Example: <code>env set ipaddr 192.168.55.2</code>

:Note: If you need to edit "bootcmd" it is necessary to insert ";" between the unique commands. You can enter ";" at the command line with "\;".

:'''Save ENV variables'''

:{| class="wikitable"
|''<code>env save</code>''
|}

:'''Delete ENV variable'''

:{| class="wikitable"
|''<code>env delete <ENV name></code>''
|}

:'''Revert to default ENV'''

:{| class="wikitable"
|''<code>env default -a</code>''
|}

:'''Import ENV from textfile'''

:{| class="wikitable"
|''<code>env import -t <SDRAM address> $filesize</code>''
|}

:Example:
: <code>fatload mmc 0 0x10000000 uEnv.txt</code>
: <code>env import -t 0x10000000 $filesize</code>

:Important:
:The uEnv.txt file should be in unix format. Also make sure that there is an empty line at the end of the file.

bootargs=console=ttyO0,115200n8 root=/dev/mmcblk0p2 mem=128M rootwait
bootcmd=mmc rescan; fatload mmc 0 0x82000000 uImage; bootm 0x82000000
uenvcmd=boot

==[[DHCOM Update Mechanism |How to do Updates]]==

== Display and Hardware settings ==
=== DHCOM settings and Splash bitmap ===
:The DHCOM settings are used to setup display and special hardware parameters. For detailed description please have a look at [[DHCOM Settings|'''How to create a settings.bin file''']].
:The DHCOM settings file and the splash bitmap are loaded via the env variables "'''load_settings_bin'''" and "'''load_splash'''" during startup from boot partition. The default content of these env variables is:
settings_bin_file=default_settings.bin
splash_file=splash.bmp
load_settings_bin=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${settings_bin_file}
load_splash=load mmc ${mmcdev}:${mmcpart} ${loadaddr} ${splash_file}

:'''Note:''' The DHCOM display settings can also be stored in external eeprom (address 0x50 / 7bit I2C address) which is connected to DHCOM I2C1 port. If eeprom is available and DISP_ADPT_EEPRM flag is set to 1, the settings from eeprom override the settings from boot partition!
:Next you can see the settings load order:
:[[Image:DISP_ADPT_EE_check.png|600px]]

=== Displaying a splash screen with u-boot ===
'''Notes:'''
* This is possible with u-boot version v1.0.0.6 or newer.
* Only RGB interface and LVDS (only first channel) is supported.
* If you use lvds panel the linux patch <code>“imx6 clk: Init LDB (lvds) parent clock“</code> (19.Jan 2016) is needed, because otherwise the display isn’t working properly in linux. (https://github.com/dh-electronics/linux-imx6-vendor/commit/6f7cabb4d7504c4d1cfe244d460f9891d5a0e411 )
'''The process to set it up is the following:'''
* Configure your display parameters with DHCOM settings generator ([[DHCOM Settings|'''How to create a settings.bin file''']]) Here you can see an LVDS display example: [[Image:DHCOM_display_settings_description.png|1000px]]
* Generate settings bin file with settings generator.
* Copy settings bin file to boot partition on boot media (eMMC, NAND or microSD card).
* Generate your splash bitmap (bitmap with 8 bit color depth).
* Copy also bmp file to boot partition.
* Start core module and enter u-boot console.
* Delete env variable “<code>panel</code>”: <code>env delete panel</code>
* Set env variable “<code>settings_bin_file</code>” with settings bin filename: Example: <code>env set settings_bin_file 10_LG_7inch_LB070WV8.bin</code>
* Set env variable “<code>splash_file</code>” with bitmap filename: Example: <code>env set splash_file 800x480_splash_DHCOM_iMX6.bmp</code>
* Save u-boot environment to flash: <code>saveenv</code>
* Restart the system --> Splash bitmap should now be displayed from the bootloader.

=== Display disabled by default ===
:With default u-boot configuration u-boot '''doesn't''' initialize the Display interface. This feature can be activated by deleting the "'''panel'''" environment variable. But also with deactivated display interface, the bootlaoder reads the display settings and pass the settings to the linux kernel.
panel="no_panel": Display interface is deactiveted in u-boot and backlight is powered off.
panel="RGB": Default DH 4,3" display is selected.
panel=deleted: u-boot initialize display by DH settings file.

=== Backlight enable GPIO ===
: If ENV variable "panel" is set to "no_panel" the backlight enable GPIO (defined via DHCOM settings file or eeprom settings) will be disabled from the bootloader during startup.
: If ENV variable "panel" is deleted, the backlight enable GPIO is activated or deactivated in relation to BL_ON flag of DHCOM settings file.
: Note: Supported by U-Boot DH VERSION v0.4.2.5 or higher for iMX6

== Building U-Boot ==
=== Prepare Build Environment ===
* Download and start the Virtual Machine based on Debian 8 (see [[COM_iMX6-D2#Downloads| i.MX6 Downloads]])
* Install Denx ELDK 5.4 to /opt (Available at [ftp://ftp.denx.de/pub/eldk/5.4/iso/ ftp://ftp.denx.de/pub/eldk/5.4/iso/]: we use eldk-5.4-armv7a.iso)
=== Get Sources ===
{| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" |
|
1. Start a terminal on Linux 
2. <tt># ''git clone [https://github.com/dh-electronics/u-boot-imx6qdl.git https://github.com/dh-electronics/u-boot-imx6qdl.git]''</tt> 
3. <tt># ''cd u-boot-imx6qdl''</tt> 
4. <tt># ''git checkout release/v1.0.0.6'' # checkout latest/required branch or tag</tt>
|}
=== Start Build===
{| class="wikitable" style="width: 100%; color: #000000; background: #ffffff;" |
|
6. <tt># ''./uboot_make [q_d dl s s_1g]''</tt> # add argument 'dl' to build for Duallite (if unsure contact DH electronics) 
|}
* Your new <tt>u-boot.imx</tt> file is available in <tt>u-boot-imx6qdl/</tt>
* If your build does fail please check content of uboot_make and adjust PATH.
'''''Attention: Risk of bricking the Device!!'''''

Ingredients of a System Image

2017-01-16T10:41:02Z

Lzenz: /* Linux */

Our DHCOM computer on module units are supplied initially programmed with the bootloader U-Boot. We offer pre-programming with the complete system image (including customer application) for the delivery in the series. The following table indicates which components therefor necessarily have to be already provided by you and which are optional depending on the situation.

== Linux ==
In the following table lists all ingredients of a Linux system image. For automatic programming images the latter components are required in addition.

:{| class="wikitable" | style="width: 98%; color: #000000; background: #FFFFFF;" valign="top" |
!style="background: #076b8d; color: white" |<tt>Image Component </tt>
!style="background: #076b8d; color: white" |<tt>Required </tt>
!style="background: #076b8d; color: white" |<tt>Recommended </tt>
!style="background: #076b8d; color: white" |<tt>Note</tt>
|-
| Bootloader U-Boot
| No
| No
| In the most cases there are no project specific features in the bootloader. If you do not provide a customized bootloader we at DH electronics assume it is ok to use our latest version with the best hardware support.
|-
| U-Boot Environment
| No
| Yes
| If your project does not need any special variables or kernel arguments we use our latest standard bootloader u-boot environment. A quick change during the development can be missed likely. We recommend to provide your "printenv" output.
|-
| Settings
| Yes
| Yes
| For details have a look at [[DHCOM Settings]]
|-
| Splash Bitmap
| No
| Yes
|
|-
| uLinuxEnv.txt
| No
| Yes
| Please refer to "U-Boot Environment". uLinuxEnv.txt is a enhancement of the U-Boot Environment.
|-
| Linux Kernel
| Yes
| Yes
|
|-
| Linux Devicetree
| Yes
| Yes
|
|-
| Linux Rootfilesystem
| Yes
| Yes
| Your application and services should be installed in the rootfilesystem. Please provide '''*.tar.gz''' Archives.
|-
!colspan="3" style="background: #076b8d; color: white" |<tt>'''Automatic Prog. Images''' </tt>
!The following components are used to program the image. They are not programmed to the target, they are a tool for programming.
|-
| Update Kernel
| Yes
| Yes
| Please visit the download area of the appropriate DHCOM device.
|-
| Bitmaps - progress.bmp - error.bmp - done.bmp
| No
| Yes
| This Bitmaps are shown on the display during programming. Not required for headless systems.
|-
| DHupdate.ini
| Yes
| Yes
| For further information see [[I.MX6 Update | I.MX6 Update Mechanism]] or [[DHCOM Flash Update | DHCOM Flash Update (i.MX25 und AM35x)]]
|}

Template:DebianVM Development

2016-12-22T13:31:35Z

Lzenz: /* Qt5.7.1 */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/Debian%20Jessie%20v1.2.zip Debian 8 "Jessie" VMware Image] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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 [https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb '''qmake-sysroot-mx6-crossarmhf_5.7.1-1.0'''] or [https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb '''qmake-sysroot-am33-crossarmhf_5.7.1-1.0'''] package to the DebianVM:
# open a terminal
# # for i.MX6: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# # for AM335x: <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/am335x/qmake-sysroot-am33-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/Debian%20Squeeze%20v1.5pw.zip Debian Squeeze VMware Image (PW: dhelectronics)] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Prepare the DHCOM module ===
* Go to the U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal (during startup)
* Change to NFS mode
:{| class="wikitable"
|<code>''setenv bootcmd 'run nandbootlinuxnfs'''</code>
|}
:(Back to normal with <code>'run nandbootlinux'</code>)
* Set the IP address of the nfs-server (normally the IP address of the virtual machine)
:{| class="wikitable"
|<code>''setenv serverip X.X.X.X''</code>
|}
:The <code>X</code> must be substituted by our IP address
* Save environment
:{| class="wikitable"
|<code>''saveenv''</code>
|}

Template:DebianVM Development

2016-12-20T16:15:16Z

Lzenz: /* Qt5 Development */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/Debian%20Jessie%20v1.2.zip Debian 8 "Jessie" VMware Image] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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. Please download and install the [https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb '''qmake-sysroot-mx6-crossarmhf_5.7.1-1.0'''] package to the DebianVM:
# open a terminal
# # <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/Debian%20Squeeze%20v1.5pw.zip Debian Squeeze VMware Image (PW: dhelectronics)] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Prepare the DHCOM module ===
* Go to the U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal (during startup)
* Change to NFS mode
:{| class="wikitable"
|<code>''setenv bootcmd 'run nandbootlinuxnfs'''</code>
|}
:(Back to normal with <code>'run nandbootlinux'</code>)
* Set the IP address of the nfs-server (normally the IP address of the virtual machine)
:{| class="wikitable"
|<code>''setenv serverip X.X.X.X''</code>
|}
:The <code>X</code> must be substituted by our IP address
* Save environment
:{| class="wikitable"
|<code>''saveenv''</code>
|}

Template:DebianVM Development

2016-12-20T16:12:54Z

Lzenz: /* Qt5 Development */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/Debian%20Jessie%20v1.2.zip Debian 8 "Jessie" VMware Image] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. 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 <tt>/work/qt5/sysroot/</tt>. 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. Please download and install the [https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb '''qmake-sysroot-mx6-crossarmhf_5.7.1-1.0'''] package to the DebianVM:
# open a terminal
# # <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/Debian%20Squeeze%20v1.5pw.zip Debian Squeeze VMware Image (PW: dhelectronics)] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Prepare the DHCOM module ===
* Go to the U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal (during startup)
* Change to NFS mode
:{| class="wikitable"
|<code>''setenv bootcmd 'run nandbootlinuxnfs'''</code>
|}
:(Back to normal with <code>'run nandbootlinux'</code>)
* Set the IP address of the nfs-server (normally the IP address of the virtual machine)
:{| class="wikitable"
|<code>''setenv serverip X.X.X.X''</code>
|}
:The <code>X</code> must be substituted by our IP address
* Save environment
:{| class="wikitable"
|<code>''saveenv''</code>
|}

Template:DebianVM Development

2016-12-20T16:11:38Z

Lzenz: /* Qt5 Development */

== 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 ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/Debian%20Jessie%20v1.2.zip Debian 8 "Jessie" VMware Image] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.2 || style="text-align: left;width: 13em" | Debian Jessie v1.2.zip || style="text-align: left;width: 40em" | - Debian Security updates - Qt Creator + Support for imx6 modules + Demos - Update elbe to v1.0 - Add some tools / editors
|-
| v1.1 || style="text-align: left;width: 13em" | Debian Jessie v1.1.zip || style="text-align: left;width: 40em" | - Compatibility VMware player 6.0
|-
| v1.0 || style="text-align: left;width: 13em" | Debian Jessie v1.0.zip || style="text-align: left;width: 40em" | - 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 <tt>/usr/bin/</tt>. 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 <tt>/opt/gcc-linaro-4.9-2014.11-x86_64_arm-linux-gnueabihf/bin/</tt>. 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 <tt>/opt/CodeSourcery-2011.03-41/bin/</tt>. Please refere the section "Linux Kernel" for the matching DHCOM device.

=== Qt5 Development ===

==== Qt5.7.1 ====
We support the latest Qt5.7.1 on our DHCOM i.MX6. Please download and install the [https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb '''qmake-sysroot-mx6-crossarmhf_5.7.1-1.0'''] package to the DebianVM:
# open a terminal
# # <tt>wget https://dl.dropboxusercontent.com/u/19433555/DHCOM/imx6/qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# install the package
# # <tt>sudo dpkg -i qmake-sysroot-mx6-crossarmhf_5.7.1-1.0_amd64.deb</tt>
# now the sysroot and qmake is ready to use
# path to qmake is <tt>/work/qt5_mx6_armhf/sysroot/usr/local/qt5.7.1/bin/qmake</tt>

==== Qt5.5.1 prebuilt and preinstalled ====
We provide the prebuilt Qt5.5.1 libraries including WebEngine (only QtQuick) and WebKit in <tt>/work/qt5/sysroot/</tt>. 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.
==== Build a Qt5 Application via console ====
# open a terminal
# navigate to your Qt5 sources
# # <tt>/work/qt5/sysroot/usr/local/qt5.5.1/bin/qmake your_own_app.pro</tt>
# # <tt>make</tt>
==== Qt Creator ====
# Start Qt Creator IDE
# Open demo project TwoLED: <tt>/work/qt5_Demos/TwoLED</tt>
# There you can find the configurations for your own project.

== Debian 6 "Squeeze" VMware Image ==
=== Get the virtual machine ===
* [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/6_0 Get the VMware player]

* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/Debian%20Squeeze%20v1.5pw.zip Debian Squeeze VMware Image (PW: dhelectronics)] Password for devel user: '''devel''' Password for root user: '''root'''

{|class="wikitable" style="padding:5px;"
|-
! Version: !! File: !! Changes:
|- style="text-align: left" valign="top"
| v1.5 || style="text-align: left;width: 13em" | Debian Squeeze v1.5pw.zip || style="text-align: left;width: 40em" | - Update VMware Tools<br\>- DH UBI-Tools<br\>- Language: English<br\>- System updates
|- style="text-align: left" valign="top"
| v1.4 || Debian Squeeze v1.4pw.zip || style="text-align: left" | - ELBE v0.3.1<br\>- ELDK 4.2<br\>- Qt Creator 2.6.1 + Qt target libs 4.7.2<br\>- System updates
|- style="text-align: left" valign="top"
| v1.3 || Debian Squeeze v1.3.zipx || style="text-align: left" | - Mono 2.10<br\>- mtd-utils<br\>- System updates
|- style="text-align: left" valign="top"
| v1.2 || Debian Squeeze v1.2.zipx || style="text-align: left" | - Emdebian Toolchain gcc 4.3 / g++ 4.3 (<code>arm-linux-gnueabi-...</code>)<br\>- TortoiseHg + TortoiseHg for Nautilus<br\>- Add Plugin "REST Client" in Iceweasel
|- style="text-align: left" valign="top"
| v1.1 || Debian Squeeze v1.1.zipx || style="text-align: left" | - Update Eclipse Indigo with CDT 8.0<br\>- Add demo project "crosshelloworld"
|- style="text-align: left" valign="top"
| v1.0 || Debian Squeeze.zipx || style="text-align: left" | - First Release<br\>- CodeSourcery Toolchain (<code>arm-none-linux-gnueabi-...</code>)<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 "'''<code>/opt/CodeSourcery/Sourcery_G++_Lite/bin'''</code>"
::Prefix type "<code>'''arm-none-linux-gnueabi-'''</code>"
:*Emdebian Toolchain:
::Folder "<code>'''/usr/bin'''</code>"
::Prefix type "<code>'''arm-linux-gnueabi-'''</code>"

== 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:
:# Execute '''">File>Import ..."'''
:# Navigate to '''">General>Existing Projects into Workspace"''' within the import dialog
:# Follow the dialog until you have finished.

[[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs and more ]]

Included Demos:
* SPI
* I2C
* GPIO
* RTC
* UART
* Watchdog
* ADC (only for i.MX25)

[[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

* For further documentation have a look at [http://www.kernel.org/doc/Documentation/ http://www.kernel.org/doc/Documentation/].

== Booting via NFS ==
=== Prepare the virtual machine ===
* Place the root file system in the folder "<code>'''/work/nfsroot'''</code>"
* Check whether the line below is part of the "<code>'''/etc/exports'''</code>" file
: <code>'''/tftpboot/nfsroot X.X.X.0/255.255.255.0(rw,no_root_squash,no_subtree_check,insecure)'''</code>
: The <code>'''X'''</code> must be substituted by our network settings
* Restart the nfs-server by using this commando
:{| class="wikitable"
|<code>''/etc/init.d/nfs-kernel-server restart''</code>
|}
=== Prepare the DHCOM module ===
* Go to the U-Boot console by pressing '''DEL/BACKSPACE''' on a RS232 terminal (during startup)
* Change to NFS mode
:{| class="wikitable"
|<code>''setenv bootcmd 'run nandbootlinuxnfs'''</code>
|}
:(Back to normal with <code>'run nandbootlinux'</code>)
* Set the IP address of the nfs-server (normally the IP address of the virtual machine)
:{| class="wikitable"
|<code>''setenv serverip X.X.X.X''</code>
|}
:The <code>X</code> must be substituted by our IP address
* Save environment
:{| class="wikitable"
|<code>''saveenv''</code>
|}

File:DHCOM-linux-am3517-3.2.81 BUILD.zip

2016-10-07T12:58:58Z

Lzenz: Linux Kernel für DHCOM AM335x based on 3.2.81 git: 528c8761fef8fffba9607b665a53bb0669ab43a7 3.2.81-dhcom-g528c876

Linux Kernel für DHCOM AM335x based on 3.2.81

git: 528c8761fef8fffba9607b665a53bb0669ab43a7

3.2.81-dhcom-g528c876

DHCOM AM35-D2

2016-10-07T12:49:56Z

Lzenz: /* Linux Kernel Binary and Sources */

{|
|
|
|-
|__TOC__
|[[Image:COMAM35.png|600px|COM AM35-D2]]
|}

== Performance & Features ==
Have a look at this youtube video to get an overview of the performace of the am3517 with the NEON coprocessor and the SGX 530 Graphics Processing Unit (GPU) included.
:* [http://www.youtube.com/watch?v=5prkZHkeDFE Sitara AM3517 Processor Demonstration]

:* The NEON coprocessor implements the Advanced SIMD media processing architecture. Single instruction, multiple data (SIMD), is a class of parallel computers with multiple processing elements that perform the same operation on multiple data simultaneously. E. g. NEON is used for video encoding.
:* The SGX 530 Graphics Processing Unit includes the Universal Scalable Shader Engine (USSE™), with a feature set that exceeds the requirements of OpenGL 2.0 and Microsoft Shader Model 3, enabling 2D, 3D and general purpose (GP-GPU) processing in a single core. This GPU is not included in the AM3505.

== Hardware ==
* [[COM AM35 Hardware|Hardware]]

{| class="wikitable" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* Cortex-A8 AM3505/17 @ 600 MHz
* AM3517 inclusive 3d acceleration / AM3505 without 3d acceleration
* 0 - 2048 MB SLC-NAND flash
* 64 - 512 MB DDR2-333
* MicroSD socket onboard
* Bus interface: 16 addresslines and 16 datalines
* 4-bit SD/MMC card interface
* LC-Displaycontroller, RGB, 24 Bit colour depth, 1400 x 1050 Pixel
* Touchcontroller onboard, 4-wire resistive
|valign="top" style="border: 0pt;" |
* Ethernet 10/100 MBit
* 2x USB Host high-speed, USB OTG high-speed
* Serial Interfaces: 3x UART, 2x I²C, 2x SPI
* CAN Interface: 1 Mbit/s
* I²S Audiocodec
* Real-time Clock RTC onboard
* Temperature range: Operating -40 to +85 °C
* SODIMM-200 Connector DHCOM Standard
|}

== Software Support ==
*[[COM AM35 Bootloader U-Boot|Bootloader U-Boot]]
*[[DHCOM Flash Update|DHCOM Update Mechanism for AM35x]]
*[[COM AM35 WinCE|WinCE]]
*[[COM AM35 Linux|Linux]]

== Downloads ==
==== X-Loader Binary and Source ====
* [[media:X-load_am3517_binary.zip|Download the latest X-Load binary (v1.1.0.0)]]
* [[media:Src_x-load-1.46-am3517.zip|Download the latest X-Load Source (v1.1.0.0)]]
==== U-Boot Binary and Source ====
* [[media:U-boot_am3517_binary_V1.2.0.5.zip|Download the latest U-Boot binary (v1.2.0.5)]]
* [[media:Src_u-boot-2009.11-am3517_V1.2.0.5.zip|Download the latest U-Boot Source (v1.2.0.5)]]
==== Settings Files ====
* [[media:00_PrimeView_7inch_PM070WT3.zip|Settings PrimeView 7" Display (PM070WT3) ]]
* [[media:01_DataImage_4_3inch_FG040360DSSWBG03.zip|Settings DataImage 4,3" Display (FG040360DSSWBG03) ]]
==== DHupdate.ini example ====
* [[media:DHupdate_example.zip|DHupdate.ini file example ]]
==== Update Bitmap example files ====
* [[media:Update_Bitmaps_AM35x-Design_480x272.zip|Update Bitmap example files for 480x272 display]]
* [[media:Update_Bitmaps_AM35x-Design_800x480.zip|Update Bitmap example files for 800x480 display]]
==== Splash Image examples for AM35x ====
* [[media:DH_AM35x_SplashImages.zip|Example Splash Bitmaps for AM35x for different display resolutions (480x272, 800x480, 1024x768)]]
==== Root Filesystem Update Kernel ====
* [[media:AM35x_RootfsUpdateKernel.zip|Update Kernel (dh-version 1v7): A tiny linux kernel used to update the nand-flash root filesystem]]
==== Linux Kernel Binary and Sources ====
* [https://github.com/dh-electronics/linux-am35x Linux Kernel based on 3.2.xx mainline available on GitHub]
* [[media:DHCOM-linux-am3517_BUILD.zip |Current built of the 3.2.12 DHCOM AM35 linux kernel (2014-04-23)]]
* [[media:DHCOM-linux-am3517-3.2.81_BUILD.zip |Current built of the 3.2.81 DHCOM AM35 linux kernel (2016-10-07)]]

==== Debian Rootfilesystem ====
* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/am35x/2015-06-19_developer-rootfs_am3517.tar.gz Debian rootfilesystem, based on Debian 6 "Squeeze" incl. SGX kernel modules (3D acceleration)]
:'''latest changes: 2014-10-30 -> 2015-06-09'''
:: - Update dh gpio utils to v1.6
:: - Stop display blanking
:'''latest changes: 2014-08-22 -> 2014-10-30'''
:: - Fixed shellshock (CVE-2014-6271)

==== Virtual Machine for Application Development ====
* [[media:Debian Squeeze v1.5pw.zip|Debian 6 "Squeeze" VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

==== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ====
* [[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs, RTC, UART, Watchdog, and more ]]
* [[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

DHCOM iMX25-D2

2016-10-07T12:36:20Z

Lzenz: /* Linux Kernel Binary and Sources */

{|
|
|
|-
|__TOC__
|[[Image:COMiMX25.png|600px|COM iMX25-D2]]
|}

== Hardware ==
* [[COM iMX25 Hardware|Hardware]]

{| class="wikitable" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* Freescale ARM9 i.MX25 @ 400 MHz
* 0 - 2048 MB NAND-FLASH
* 64 - 128 MB DDR2-266
* MicroSD Sockel onboard
* SD/MMC card interface
* LC-Displaycontroller, 16 Bit colour depth, 800 x 600 Pixel
* Touchcontroller onboard, 4-wire resistive
|valign="top" style="border: 0pt;" |
* Ethernet 10/100 MBit
* 1x USB Host full-speed, USB OTG high-speed
* Serial Interfaces: 3x UART, 2x I²C, 2x SPI
* CAN Interface: 1 Mbit/s
* Real-time Clock RTC onboard
* Temperature range: Operating -40 to +85 °C
* SODIMM-200 Connector DHCOM Standard
|}

== Software Support ==
*[[COM iMX25 Bootloader U-Boot|Bootloader U-Boot]]
*[[DHCOM Flash Update|DHCOM Update Mechanism for i.MX25]]
*[[COM iMX25 WinCE|WinCE]]
*[[COM iMX25 Linux|Linux]]

== Downloads ==
==== Bootloader Binary ====
* [[media:U-boot_(V1.18.0.5).zip|Download U-Boot binary (v1.18.0.5)]] (for updating, please have a look at FAQ list)
==== Settings Files ====
* [[media:00_PrimeView_7inch_PM070WT3.zip|Settings PrimeView 7" Display (PM070WT3) (for U-Boot Version v1.11.2.0 or higher)]]
* [[media:01_DataImage_4_3inch_FG040360DSSWBG03.zip|Settings DataImage 4,3" Display (FG040360DSSWBG03) (for U-Boot Version v1.11.2.0 or higher)]]
==== DHupdate.ini example ====
* [[media:DHupdate_example.zip|DHupdate.ini file example (for U-Boot Version v1.10.0.0 or higher)]]
==== Update Bitmap example files ====
* [[media:Update_Bitmaps_800x480.zip|Update Bitmap example files for 800x480 display]]
==== Splash Image examples ====
* [[media:DH_480x272.zip|Example Splash Bitmap for 480x272 Display]]
* [[media:DH_800x480.zip|Example Splash Bitmap for 800x480 Display]]
==== Root Filesystem Update Kernel ====
* [[media:iMX25_RootfsUpdateKernel.zip|Update Kernel (dh-version 1v5): A tiny linux kernel used to update the nand-flash root filesystem]]
==== Linux Kernel Binary and Sources ====
* [https://github.com/dh-electronics/linux-imx25 Linux Kernel based on 3.2.xx mainline available on GitHub]
* [[media:DHCOM-linux-imx-3.2.9_BUILD.zip|Current built of the 3.2.9 DHCOM iMX25 linux kernel (2016-02-24)]]
* [[media:DHCOM-linux-imx-3.2.81_BUILD.zip|Current built of the 3.2.81 DHCOM iMX25 linux kernel (2016-10-07)]]

==== Debian Rootfilesystem ====
* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/rootFS_DN_20110805et4_HL7%20%2830.10.2014%29.tar.bz2 Current Debian root file system, based on Debian 6 "Squeeze" (2014-10-30)] Remark: Shellshock (CVE-2014-6271) is already fixed.

==== Virtual Machine for Application Development ====
* [[media:Debian Squeeze v1.5pw.zip|Debian 6 "Squeeze" VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

==== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ====
* [[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs, RTC, UART, Watchdog, and more ]]
* [[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

File:DHCOM-linux-imx-3.2.81 BUILD.zip

2016-10-07T12:34:51Z

Lzenz: Linux Kernel based on 3.2.81 git: 416610f78777a047de4aa1881fc35bb4c152c327 2016-10-07

Linux Kernel based on 3.2.81

git: 416610f78777a047de4aa1881fc35bb4c152c327

2016-10-07

DHCOM iMX25-D2

2016-10-07T12:32:13Z

Lzenz: /* Linux Kernel Binary and Sources */

{|
|
|
|-
|__TOC__
|[[Image:COMiMX25.png|600px|COM iMX25-D2]]
|}

== Hardware ==
* [[COM iMX25 Hardware|Hardware]]

{| class="wikitable" | style="width: 100%; color: #000000; background: #f3f3f3;" valign="top" |
|-
| style="width: 50%; background: #076b8d; border: 0pt;" |
| style="width: 50%; background: #076b8d; border: 0pt;" |
|-
|valign="top" style="border: 0pt;" |
* Freescale ARM9 i.MX25 @ 400 MHz
* 0 - 2048 MB NAND-FLASH
* 64 - 128 MB DDR2-266
* MicroSD Sockel onboard
* SD/MMC card interface
* LC-Displaycontroller, 16 Bit colour depth, 800 x 600 Pixel
* Touchcontroller onboard, 4-wire resistive
|valign="top" style="border: 0pt;" |
* Ethernet 10/100 MBit
* 1x USB Host full-speed, USB OTG high-speed
* Serial Interfaces: 3x UART, 2x I²C, 2x SPI
* CAN Interface: 1 Mbit/s
* Real-time Clock RTC onboard
* Temperature range: Operating -40 to +85 °C
* SODIMM-200 Connector DHCOM Standard
|}

== Software Support ==
*[[COM iMX25 Bootloader U-Boot|Bootloader U-Boot]]
*[[DHCOM Flash Update|DHCOM Update Mechanism for i.MX25]]
*[[COM iMX25 WinCE|WinCE]]
*[[COM iMX25 Linux|Linux]]

== Downloads ==
==== Bootloader Binary ====
* [[media:U-boot_(V1.18.0.5).zip|Download U-Boot binary (v1.18.0.5)]] (for updating, please have a look at FAQ list)
==== Settings Files ====
* [[media:00_PrimeView_7inch_PM070WT3.zip|Settings PrimeView 7" Display (PM070WT3) (for U-Boot Version v1.11.2.0 or higher)]]
* [[media:01_DataImage_4_3inch_FG040360DSSWBG03.zip|Settings DataImage 4,3" Display (FG040360DSSWBG03) (for U-Boot Version v1.11.2.0 or higher)]]
==== DHupdate.ini example ====
* [[media:DHupdate_example.zip|DHupdate.ini file example (for U-Boot Version v1.10.0.0 or higher)]]
==== Update Bitmap example files ====
* [[media:Update_Bitmaps_800x480.zip|Update Bitmap example files for 800x480 display]]
==== Splash Image examples ====
* [[media:DH_480x272.zip|Example Splash Bitmap for 480x272 Display]]
* [[media:DH_800x480.zip|Example Splash Bitmap for 800x480 Display]]
==== Root Filesystem Update Kernel ====
* [[media:iMX25_RootfsUpdateKernel.zip|Update Kernel (dh-version 1v5): A tiny linux kernel used to update the nand-flash root filesystem]]
==== Linux Kernel Binary and Sources ====
* [https://github.com/dh-electronics/linux-imx25 Linux Kernel based on 3.2.9 mainline available on GitHub]
* [[media:DHCOM-linux-imx-3.2.9_BUILD.zip|Current built of the 3.2.9 DHCOM iMX25 linux kernel (2016-02-24)]]
* [[media:DHCOM-linux-imx-3.2.81_BUILD.zip|Current built of the 3.2.81 DHCOM iMX25 linux kernel (2016-10-07)]]

==== Debian Rootfilesystem ====
* [https://dl.dropboxusercontent.com/u/19433555/DHCOM/rootFS_DN_20110805et4_HL7%20%2830.10.2014%29.tar.bz2 Current Debian root file system, based on Debian 6 "Squeeze" (2014-10-30)] Remark: Shellshock (CVE-2014-6271) is already fixed.

==== Virtual Machine for Application Development ====
* [[media:Debian Squeeze v1.5pw.zip|Debian 6 "Squeeze" VMware Image (PW: dhelectronics)]] Password for devel user: '''devel''' Password for root user: '''root'''

==== Code Examples for Userspace-Applications to Access SPI, I2C, GPIOs, and more ====
* [[media:Demos_SPI_I2C_GPIO.zip|Download Code Examples SPI, I2C, GPIOs, RTC, UART, Watchdog, and more ]]
* [[media:DHCOM_HAL.zip|Download C++ HAL class library for SPI, I2C, GPIO, UART and physical address space access]]

COM AM35 Linux

2016-10-07T12:16:24Z

Lzenz: /* Building your own Kernel */

== Linux virtual machine for development ==
* Please have a look at: '''[[Virtual Machine for Application Development]]'''

==Building your own Kernel ==

==== Sources for the AM35x Linux Kernel v3.2.12 / v3.2.81 ====
* The latest Linux Kernel source code is available on GitHub: [https://github.com/dh-electronics/linux-am35x https://github.com/dh-electronics/linux-am35x]
* We recommend to use on new projects the latest v3.2.81 Linux Kernel

==== How to build a kernel ====
Get sources from Github and build the linux kernel using 5 threads and a build directory
{| class="wikitable"
|1. Start a terminal on Linux
|-
|2. <tt># ''git clone [https://github.com/dh-electronics/linux-am35x.git https://github.com/dh-electronics/linux-am35x.git]''</tt>
|-
|3. <tt># ''mkdir build''</tt>
|-
|4. <tt># ''cd linux-am35x''</tt>
|-
|5. <tt># ''git checkout BRANCH'' (BRANCH=dev/3.2.12_dhcom or BRANCH=dev/3.2.81_dhcom)</tt>
|-
|6. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make O=../build/ dhcm3517_defconfig''</tt>
|-
|7. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make -j5 O=../build/ uImage''</tt>
|}
* Your new <tt>uImage</tt> file is available in <tt>../build/arch/arm/boot</tt>
'''Remark:'''
* On linux-am35x.git we use the git branch "master".

{| style="width: 100%; color: #000000; border-spacing: 2px; border: 1px solid darkgray; background: lightgrey;" valign="top" |
| style="width: 100%;" |
|-
|
=== ''Sources older than April 2014'' ===
==== Sources for the AM35 Kernel based on 3.2.12 Mainline ====

:* [http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.2.12.tar.bz2 Kernel version: 3.2.12 from www.kernel.org]

:* [[media:DHCOM-linux-am3517.patch.zip‎|Patch for DHCOM AM35 Linux (2014-04-23) [includes RT-Preemptiv patch]]]

:* [[media:DHCOM-linux-am3517.config.zip|Kernel configuration for DHCOM AM35 Linux (2014-04-23)]]

:* [[media:DHCOM-linux-am3517_BUILD.zip |Current built of the 3.2.12 DHCOM AM35 linux kernel (2014-04-23)]]

::* '''latest changes: 2013-12-05 -> 2014-04-23'''
::: - Add DH touch support
::: - Add Boardfile to use LCD-Interface with GPIO-functionality (DHpicoITX)

::* '''latest changes: 2013-06-17 -> 2013-12-05'''
::: - USB-OTG: Fixed mass storage operation (depends on latest kernel configuration, too)
::: - BUG-Fix: Set rtc default values to a valid status

::* '''latest changes: 2013-05-22 -> 2013-06-17'''
::: - (Minor) Customizations for 1 GByte Spansion NAND-Flash

::* '''latest changes: 2013-04-04 -> 2013-05-22'''
::: - (Minor) BUG-Fix: Initialization of DHCOM GPIO_E pad fixed

::* '''latest changes: 2012-12-14 -> 2013-04-04'''
::: - SPI BUG-Fix: Disabled "Turbo-Mode" to avoid wrong additional byte-reads (If used: Kernel-Update recommended)
::: - I2C BUG-Fix: AM35x Errata 1.1.26 (If used: Kernel-Update recommended)
::: - enabled ETH_VIO_GPIO (necessary for DHCOM pico-ITX) to supply ethernet transformer
::: - FF UART support added
::: - DHCOM (CAM) GPIO Padconfigurations changed to GPIO-Mode on default.
::: - removed USB-OTG-POWER-GPIO (Use kernel-argument [u-boot env bootargs] 'dheva01_version=200' to activate it again)
::: - backlight PWM default is now 205 (80%)

::* '''2012-11-08 -> 2012-12-14'''
::: - /dev/spidev1.1 is now /dev/spidev1.0
::: - watchdog driver support for magic close added

::* '''2012-08-29 -> 2012-11-08'''
::: - added audio support
::: - changed partitionsize of linux-kernel

==== How to build a kernel ====
{| class="wikitable"
|1. Start a terminal on Linux
|-
|2. Copy the above mentioned source files (linux-3.x.y.tar.bz2, .config, *.patch) into our <code>work_path</code>
|-
|3. <tt># ''cd work_path''</tt>
|-
|4. <tt># ''tar xfjv linux-3.2.12.tar.bz2''</tt>
|-
|5. <tt># ''cd work_path/linux-3.2.12''</tt>
|-
|6. <tt># ''patch -p1 < ../dh-linux-am35x_xxxxxxxx.patch''</tt>
|-
|7. <tt># ''cp ../dh-linux-am35x_xxxxxxxx.config .config'</tt>
|-
|8. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage''</tt>
|}
:* Your new <tt>uImage</tt> file is available in <tt>work_path/linux-3.2.12/arch/arm/boot</tt>
|}

== Update the kernel with U-Boot ==

:The linux kernel will be updated by the [[COM_AM35_Bootloader_U-Boot#Update|U-Boot flash update]].

:* [[media:DHCOM-linux-am3517_BUILD.zip |Binary Image DHCOM AM35 linux-3.2.12-rt20 kernel (details see above)]]

:{| class="wikitable"
|1. Copy the <code>'''uImage'''</code> and <code>'''uImage.env'''</code> file onto a microSD card with a FAT file system (you can use the 1st partition on the microSD card)
|-
|2. Insert the microSD card and start the system
|-
|3. Go to the U-Boot console by pressing '''BACKSPACE'''/'''DEL''' on a RS232 terminal (during startup)
|-
|4. <code>''update linux''</code>
|}

==Debian Rootfilesystem ==

=== Available Rootfilesystems ===
Please have a look at the [[COM_AM35-D2#Downloads | AM35x Downloads]] section.

=== External Documentation ===
* [https://debian-handbook.info/browse/stable/ The Debian Administrator's Handbook]: A reference book presenting the Debian distribution, from initial installation to configuration of services. The administration and configuration chapters apply to our Debian based root filesystems.
* [https://www.debian.org/doc/ Debian Documentation]

=== Login ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
||
<tt>
Debian GNU/Linux 6.0 dhcom ttyO0 

dhcom login: '''root''' 
Password: '''foo'''
</tt>
|}

=== Shutdown ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># shutdown -h now</tt>
|}

=== Calibrating the touchscreen ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># ts_calibrate</tt>
|}
*Check the enviroment variable "TSLIB_TSDEVICE=/dev/input/event0" with <code> printenv </code> if an error occurs.

===Running Qt Demos ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># cd /usr/qt/demos/demoname</tt> <tt># ./demoname -qws</tt>
|}
*For the Qt-Browser change <code>demoname</code> to <code>browser</code>
*If the touchscreen does not work please check the enviroment variable "QWS_MOUSE_PROTO=Tslib:/dev/input/event0" with <code> printenv</code>.

'''''Run Qt demos with powerVR (3d acceleration) support'''''
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># cd /usr/qt/demos/embedded/demoname</tt> <tt># ./demoname -qws</tt>
|}

'''''Run Qt demos with usb mouse input device'''''
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># cd /usr/qt/demos/demoname</tt> <tt># export QWS_MOUSE_PROTO=Auto:/dev/input/mice</tt> <tt># ./demoname -qws</tt>
|}

'''Remark:''' Just remember that you need to run the Qt demos with the options -qws. Omitting -qws results in the app waiting to connect to the QWS Server, which is not running.

== How to create a microSD-card with a rootfilesystem on it ==

1. Format a microSD card like following (in linux e.g. gparted, palimpsest) with '''Master Boot Record''' partition scheme
{| class="wikitable" | style="width: 450px; color: #000000; background: #FFFFFF;" valign="top" |
|
<tt>P1 '''FAT''' (Primary partition: 100MB)</tt> 
<tt>P2 '''ext3''' (Primary partition: Residual space)</tt>
|}
2. Untar the root file system to the ext3 partition of the microSD card (Don't copy the tar archive directly to the microSD card)
{| class="wikitable" | style="width: 450px; color: #000000; background: #FFFFFF;" valign="top" |
|
Start the Console on Linux 
<tt># ''su''</tt> 
<tt># ''chmod 755 /path/of/the/microSD_card''</tt> 
<tt># ''cd /path/of/the/microSD_card''</tt> 
<tt># ''tar xfjv path/to/RootFS/Name_of_RootFS_file.tar.bz2''</tt>
|}
'''Remark:''' If you got a *.tar.gz file so type <tt> tar xfzv ... </tt> to extract the rootfilesystem.

== Kernel Userspace Interfaces to Access Hardware ==

=== Serial (UART) Interfaces ===
:{| class="wikitable" style="width: 400px"
| style="width: 50%;"| DHCOM (FF) UART 1||<code>/dev/ttyO0</code>
|-
||DHCOM (BT) UART 2 ||<code>/dev/ttyO2</code>
|-
||DHCOM (STD) UART 3 ||<code>/dev/ttyO1</code>
|}

=== I2C Interfaces ===
:{| class="wikitable" style="width: 400px"
| style="width: 50%;"| DHCOM I2C 1||<code>/dev/i2c-3</code>
|-
||DHCOM I2C 2 ||<code>/dev/i2c-2</code>
|-
||On Module Devices ||<code>/dev/i2c-1</code>
|}

=== SPI Interfaces ===
:{| class="wikitable" style="width: 400px"
| style="width: 50%;"| DHCOM SPI 1||<code>/dev/spidev1.0</code>
|-
||DHCOM SPI 2 ||<code>/dev/spidev2.0</code>
|}

=== Control the display brightness ===
:{| class="wikitable"
|<code>''echo <value> >/sys/class/backlight/omap-pwm-backlight/brightness''</code>
|}
:value range: 0..255

=== Control GPIOs ===
:{|class="wikitable" style="text-align: center; width: 600px"
|-
! DHCOM Name: !! alt. DHCOM Name: !! SO-DIMM Pin# !! Linux <GPIO#>
|-
| GPIO A || || 154 || 116
|-
| GPIO B || || 156 || 117
|-
| GPIO C || || 162 || 118
|-
| GPIO D || || 163 || 119
|-
| GPIO E || || 164 || 125
|-
| GPIO F || || 165 || 140
|-
| GPIO G || || 167 || 141
|-
| GPIO H || || 173 || 155
|-
| GPIO I || || 175 || 152
|-
| CIF HSYNC || GPIO J || 74 || 96
|-
| CIF PCLK || GPIO K || 72 || 94
|-
| CIF MCLK || GPIO L || 70 || 58
|-
| CIF VSYNC || GPIO M || 68 || 97
|-
| CIF D9 || GPIO N || 66 || 98
|-
| CIF D8 || GPIO O || 64 || 95
|-
| CIF D7 || GPIO P || 62 || 106
|-
| CIF D6 || GPIO Q || 60 || 105
|-
| CIF D5 || GPIO R || 58 || 104
|-
| CIF D4 || GPIO S || 56 || 103
|-
| CIF D3 || GPIO T || 54 || 102
|-
| CIF D2 || GPIO U || 52 || 101
|-
| CIF D1 || GPIO V || 50 || 100
|-
| CIF D0 || GPIO W || 48 || 99
|}
:: '''Remark:''' Depending on your board configuration some of the additional gpios shared with the camera interface are not available on your system.

:Export
:{| class="wikitable"
|<code>''echo <GPIO#> >/sys/class/gpio/export''</code>
|}
:: '''Remark:''' Have a look into <code> /sys/class/gpio/ </code> for already configured gpios.
:Set direction
:{| class="wikitable"
|<code>''echo in >/sys/class/gpio/gpio<GPIO#>/direction''</code>
|-
|<code>''echo out >/sys/class/gpio/gpio<GPIO#>/direction''</code>
|}

:Set state
:{| class="wikitable"
|<code>''echo 0 >/sys/class/gpio/gpio<GPIO#>/value''</code>
|-
|<code>''echo 1 >/sys/class/gpio/gpio<GPIO#>/value''</code>
|}

=== Initialize and Test CAN Interface ===
:Initialize:
:{| class="wikitable"
|<code>''ip link set can0 up type can bitrate 500000''</code>
|}

:Send test message via cansend (part of can-utils):
:{| class="wikitable"
|<code>''cansend can0 100#11.2233.44556677.88''</code>
|}

:Receive can messages (part of can-utils):
:{| class="wikitable"
|<code>''candump can0''</code>
|}

:Get can-utils:
:* [[media:can-utils_armel.zip|Debian package containing can-utils (ARM)]]

=== Testing display / framebuffer ===
:In most common cases the "Display Bits" should be "8"
:With "fb" you select the number of the framebuffer device (e.g. /dev/fb0)
:{| class="wikitable" style="width: 1200px"
||<code>fb_1Colorfill</code>||Fills the framebuffer device with a given RGB color <code>fb_1Colorfill [fb (0..31)] [Display Bits (1..8)] [Red value (0..255)] [Green value (0..255)] [Blue value (0..255)]</code>
|-
||<code>fb_fb2BMP</code>||Copies the framebuffer device data into a 24Bit BMP-File <code>fb_fb2BMP [fb (0..31)] [24-Bit BMP-File]</code>
|-
||<code>fb_LoadBMP</code>||Loads a 24Bit BMP-file into a 32Bit framebuffer device <code>fb_LoadBMP [fb (0..31)] [24-Bit BMP-File] [Display Bits (1..8)] [Transparency (0..100)]</code>
|}

:Get DH farmebuffer tools:
:* [[media:dh_framebuffer_tools.zip|DH framebuffer tools version 1.0 (ARM)]]

== Additional Information ==
*[[Linux Kernel Features | Linux Kernel Features ]]
*[[ELBE Overview| Embedded Linux Build Environment (ELBE)]]

COM iMX25 Linux

2016-10-07T07:58:44Z

Lzenz: /* How to build a kernel */

== Linux virtual machine for development ==
* Please have a look at: '''[[Virtual Machine for Application Development]]'''

==Building your own Kernel ==

==== Sources for the iMX25 Linux Kernel v3.2.9 / v3.2.81: ====
* The latest Linux Kernel source code is available on GitHub: [https://github.com/dh-electronics/linux-imx25 https://github.com/dh-electronics/linux-imx25]
* We recommend to use on new projects the latest v3.2.81 Linux Kernel

==== How to build a kernel ====
Get sources from Github and build the linux kernel
{| class="wikitable"
|1. Start a terminal on Linux
|-
|2. <tt># ''git clone [https://github.com/dh-electronics/linux-imx25.git https://github.com/dh-electronics/linux-imx25.git]''</tt>
|-
|3. <tt># ''git checkout BRANCH'' (BRANCH=dev/3.2.9_dhcom or BRANCH=dev/3.2.81_dhcom)</tt>
|-
|4. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make imx25_dhcom_defconfig''</tt>
|-
|5. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage''</tt>
|}
* Your new <tt>uImage</tt> file is available in <tt>arch/arm/boot</tt>

{| style="width: 100%; color: #000000; border-spacing: 2px; border: 1px solid darkgray; background: lightgrey;" valign="top" |
| style="width: 100%;" |
|-
|

=== ''Sources older than February 2014'' ===
==== Sources for the iMX25 Linux Kernel v2.6.38: ====

:* [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.tar.bz2 Mainline Kernel version: 2.6.38 from www.kernel.org]

:* [[media:Linux-2.6.38_DHCOM_iMX25_patch.zip|Patch to DHCOM iMX25 Linux (2014-09-29)]]

:* [[media:Linux-2.6.38_DHCOM_iMX25_config.zip|Kernel configuration for DHCOM iMX25 Linux (2014-09-29)]]

==== Sources for the iMX25 Linux Kernel v3.2.9: ====

:* [http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.2.9.tar.bz2 Mainline Kernel version: 3.2.9 from www.kernel.org]

:* [[media:DHCOM-linux-imx-3.2.9.patch.zip|Patch to DHCOM iMX25 Linux 3.2.9 (2013-09-20)]]

:* [[media:DHCOM-linux-imx-3.2.9.config.zip|Kernel configuration for DHCOM iMX25 Linux 3.2.9 (2013-03-27)]]

==== How to build a kernel ====
{| class="wikitable"
|1. Start a terminal on Linux
|-
|2. Copy the above mentioned source files (linux-3.x.y.tar.bz2, .config, *.patch) into our <code>work_path</code>
|-
|3. <tt># ''cd work_path''</tt>
|-
|4. <tt># ''tar xfjv linux-2.6.38.tar.bz2''</tt>
|-
|5. <tt># ''cd work_path/linux-2.6.38''</tt>
|-
|6. <tt># ''patch -p1 <linux-2.6.38_DHCOM_iMX25.patch''</tt>
|-
|7. <tt># ''cp .config work_path/linux-2.6.38''</tt>
|-
|8. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage''</tt>
|}
:* Your new <tt>uImage</tt> file is available in <tt>work_path/linux-2.6.38/arch/arm/boot</tt>
|}

==Update the kernel with U-Boot ==

:The linux kernel will be updated by the [[COM iMX25 Bootloader U-Boot#Update|U-Boot flash update]].

:* [[media:Linux-2.6.38_DHCOM_iMX25_kernel.zip|Binary image 2.6.38 DHCOM iMX25 linux kernel (2014-09-29)]]
:* [[media:DHCOM-linux-imx-3.2.9_BUILD.zip|Binary image 3.2.9 DHCOM iMX25 linux kernel (2016-02-24)]]
:* [[media:DHCOM-linux-imx-3.2.78_BUILD.zip|Binary image 3.2.78 DHCOM iMX25 linux kernel (2016-03-08)]]

:{| class="wikitable"
|1. Copy the <code>'''uImage'''</code> and <code>'''uImage.env'''</code> file onto a microSD card with a FAT file system (you can use the 1st partition on the microSD card)
|-
|2. Insert the microSD card and start the system
|-
|3. Go to the U-Boot console by pressing '''BACKSPACE''' on a RS232 terminal (during startup)
|-
|4. <code>''update linux''</code>
|}

==Debian Rootfilesystem ==
=== Available Rootfilesystems ===
Please have a look at the [[COM_iMX25-D2#Downloads | iMX25 Downloads]] section.

=== External Documentation ===
* [https://debian-handbook.info/browse/stable/ The Debian Administrator's Handbook]: A reference book presenting the Debian distribution, from initial installation to configuration of services. The administration and configuration chapters apply to our Debian based root filesystems.
* [https://www.debian.org/doc/ Debian Documentation]

=== Login ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
||
<tt>
Debian GNU/Linux 6.0 dhcom ttymxc1 

dhcom login: '''root''' 
Password: '''foo'''
</tt>
|}
=== Calibrating the touchscreen ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># TSLIB_TSDEVICE=/dev/input/event0 ts_calibrate</tt>
|}
===Running example Qt Apps ===
{| class="wikitable" align="center" | style="width: color: #000000; background: #FFFFFF;" valign="top" |
|<tt># QWS_MOUSE_PROTO=Tslib:/dev/input/event0 /usr/qt/demos/demoname/demoname -qws</tt>
|}
*'''Remark:''' To start the Qt-Browser replace <tt>demoname</tt> with <tt>browser</tt>

=== Shutdown ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># shutdown -h now</tt>
|}

== How to create a microSD-card with a rootfilesystem on it ==

1. Format a microSD card like following (in linux e.g. gparted, palimpsest) with '''Master Boot Record''' partition scheme
{| class="wikitable" | style="width: 450px; color: #000000; background: #FFFFFF;" valign="top" |
|
<tt>P1 '''FAT''' (Primary partition: 100MB)</tt> 
<tt>P2 '''ext3''' (Primary partition: Residual space)</tt>
|}
2. Untar the root file system to the ext3 partition of the microSD card (Don't copy the tar archive directly to the microSD card)
{| class="wikitable" | style="width: 450px; color: #000000; background: #FFFFFF;" valign="top" |
|
Start the Console on Linux 
<tt># ''su''</tt> 
<tt># ''chmod 755 /path/of/the/microSD_card''</tt> 
<tt># ''cd /path/of/the/microSD_card''</tt> 
<tt># ''tar xfjv path/to/RootFS/Name_of_RootFS_file.tar.bz2''</tt>
|}
'''Remark:''' If you got a *.tar.gz file so type <tt> tar xfzv ... </tt> to extract the rootfilesystem.

==Busybox Rootfilesystem ==
=== Calibrating the touchscreen ===
:{| class="wikitable"
|<code>''TSLIB_TSDEVICE=/dev/event0 ts_calibrate''</code>
|}
===Running example Qt Apps ===
:{| class="wikitable"
|<code>''QWS_MOUSE_PROTO=Tslib:/dev/event0 /usr/qt/demos/demoname/demoname -qws''</code>
|}
:For the Qt-Browser change <code>demoname</code> to <code>browser</code>
=== Login/Shutdown system ===
:{| class="wikitable" style="width: 120px"
||Username: ||root
|-
||Password: ||n/a
|}
:{| class="wikitable"
|<code>''halt''</code>
|}

== Kernel Userspace Interfaces to Access Hardware ==

=== Serial (UART) Interfaces ===
:{| class="wikitable" style="width: 400px"
|style="width: 50%;"|DHCOM (FF) UART 1||<code>/dev/ttymxc1</code>
|-
||DHCOM (BT) UART 2 ||<code>/dev/ttymxc2</code>
|-
||DHCOM (STD) UART 3 ||<code>/dev/ttymxc4</code>
|}

=== I2C Interfaces ===
:{| class="wikitable" style="width: 400px"
|style="width: 50%;"|DHCOM I2C 1||<code>/dev/i2c-1</code>
|-
||DHCOM I2C 2 ||<code>/dev/i2c-2</code>
|}

=== SPI Interfaces ===
:{| class="wikitable" style="width: 400px"
|style="width: 50%;"|DHCOM SPI 1||<code>/dev/spidev1.0</code>
|-
||DHCOM SPI 2 ||<code>/dev/spidev2.0</code>
|}

=== Control the display brightness ===
:{| class="wikitable" style="width: 640px"
|<code>''echo <value> >/sys/devices/platform/imx-fb.0/backlight/imxfb-bl/brightness''</code>
|}
:value range: 0..255

=== Control GPIOs ===

:{|class="wikitable" style="text-align: center; width: 600px"
|-
! DHCOM Name: !! alt. DHCOM Name: !! Port: !! Pin: !! SO-DIMM Pin# !! Linux <GPIO#>
|-
| GPIO A || || 2 || 12 || 154 || 44
|-
| GPIO B || || 3 || 21 || 156 || 85
|-
| GPIO C || || 2 || 4 || 162 || 36
|-
| GPIO D || || 2 || 5 || 163 || 37
|-
| GPIO E || || 2 || 6 || 164 || 38
|-
| GPIO F || || 2 || 7 || 165 || 39
|-
| GPIO G || || 2 || 8 || 167 || 40
|-
| GPIO H || || 2 || 9 || 173 || 41
|-
| GPIO I || || 3 || 17 || 175 || 81
|-
| CIF HSYNC || GPIO J || 1 || 10 || 74 || 10
|-
| CIF PCLK || GPIO K || 1 || 11 || 72 || 11
|-
| CIF MCLK || GPIO L || 1 || 8 || 70 || 8
|-
| CIF VSYNC || GPIO M || 1 || 9 || 68 || 9
|-
| CIF D9 || GPIO N || 4 || 21 || 66 || 117
|-
| CIF D8 || GPIO O || 1 || 7 || 64 || 7
|-
| CIF D7 || GPIO P || 1 || 6 || 62 || 6
|-
| CIF D6 || GPIO Q || 1 || 31 || 60 || 31
|-
| CIF D5 || GPIO R || 1 || 30 || 58 || 30
|-
| CIF D4 || GPIO S || 1 || 29 || 56 || 29
|-
| CIF D3 || GPIO T || 1 || 28 || 54 || 28
|-
| CIF D2 || GPIO U || 1 || 27 || 52 || 27
|}

:Export
:{| class="wikitable" style="width: 640px"
|<code>''echo <GPIO#> >/sys/class/gpio/export''</code>
|}
:Set direction
:{| class="wikitable" style="width: 640px"
|<code>''echo in >/sys/class/gpio/gpioXX/direction''</code>
|-
|<code>''echo out >/sys/class/gpio/gpioXX/direction''</code>
|}
:Set value
:{| class="wikitable" style="width: 640px"
|<code>''echo 0 >/sys/class/gpio/gpioXX/value''</code>
|-
|<code>''echo 1 >/sys/class/gpio/gpioXX/value''</code>
|}
:Get value
:{| class="wikitable" style="width: 640px"
|<code>''cat /sys/class/gpio/gpioXX/value''</code>
|}

:unexport
:{| class="wikitable" style="width: 640px"
|<code>''echo <GPIO#> >/sys/class/gpio/unexport''</code>
|}

=== Initialize and test CAN ===
:Initialize:
:{| class="wikitable"
|<code>''ip link set can0 up type can bitrate 500000''</code>
|}

:Send test message via cansend (part of can-utils):
:{| class="wikitable"
|<code>''cansend can0 100#11.2233.44556677.88''</code>
|}

:Receive message via candump (part of can-utils):
:{| class="wikitable"
|<code>''candump can0''</code>
|}

:Get can-utils:
:* [[media:can-utils_armel.zip|Debian package containing can-utils (ARM)]]

=== Test display / framebuffer ===
:{| class="wikitable" style="width: 1200px"
||<code>fb_1Colorfill</code>|| Fills the framebuffer device with a given RGB color <code>Syntax: fb_1Colorfill [fb (0..31)] [Display Bits (1..8)] [Red value (0..255)] [Green value (0..255)] [Blue value (0..255)]</code>
|-
||<code>fb_fb2BMP</code>||Copies framebuffer device data into a 24Bit BMP-File <code>Syntax: fb_fb2BMP [fb (0..31)] [24-Bit BMP-File]</code>
|-
||<code>fb_LoadBMP</code>||Loads a 24Bit BMP-file into a 32Bit framebuffer device <code>Syntax: fb_LoadBMP [fb (0..31)] [24-Bit BMP-File] [Display Bits (1..8)] [Transparency (0..100)]</code>
|}
:In most common cases the "Display Bits" should be "8"

:Get DH framebuffer tools:
:* [[media:dh_framebuffer_tools.zip|DH framebuffer tools v1.0 (ARM)]]

== Additional Information ==
*[[Linux Kernel Features | Linux Kernel Features ]]
*[[ELBE Overview| Embedded Linux Build Environment (ELBE)]]

COM iMX25 Linux

2016-10-07T07:58:29Z

Lzenz: /* Sources for the iMX25 Linux Kernel v3.2.9 / v3.2.78: */

== Linux virtual machine for development ==
* Please have a look at: '''[[Virtual Machine for Application Development]]'''

==Building your own Kernel ==

==== Sources for the iMX25 Linux Kernel v3.2.9 / v3.2.81: ====
* The latest Linux Kernel source code is available on GitHub: [https://github.com/dh-electronics/linux-imx25 https://github.com/dh-electronics/linux-imx25]
* We recommend to use on new projects the latest v3.2.81 Linux Kernel

==== How to build a kernel ====
Get sources from Github and build the linux kernel
{| class="wikitable"
|1. Start a terminal on Linux
|-
|2. <tt># ''git clone [https://github.com/dh-electronics/linux-imx25.git https://github.com/dh-electronics/linux-imx25.git]''</tt>
|-
|3. <tt># ''git checkout BRANCH'' (BRANCH=dev/3.2.9_dhcom or BRANCH=dev/3.2.78_dhcom)</tt>
|-
|4. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make imx25_dhcom_defconfig''</tt>
|-
|5. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage''</tt>
|}
* Your new <tt>uImage</tt> file is available in <tt>arch/arm/boot</tt>

{| style="width: 100%; color: #000000; border-spacing: 2px; border: 1px solid darkgray; background: lightgrey;" valign="top" |
| style="width: 100%;" |
|-
|
=== ''Sources older than February 2014'' ===
==== Sources for the iMX25 Linux Kernel v2.6.38: ====

:* [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.tar.bz2 Mainline Kernel version: 2.6.38 from www.kernel.org]

:* [[media:Linux-2.6.38_DHCOM_iMX25_patch.zip|Patch to DHCOM iMX25 Linux (2014-09-29)]]

:* [[media:Linux-2.6.38_DHCOM_iMX25_config.zip|Kernel configuration for DHCOM iMX25 Linux (2014-09-29)]]

==== Sources for the iMX25 Linux Kernel v3.2.9: ====

:* [http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.2.9.tar.bz2 Mainline Kernel version: 3.2.9 from www.kernel.org]

:* [[media:DHCOM-linux-imx-3.2.9.patch.zip|Patch to DHCOM iMX25 Linux 3.2.9 (2013-09-20)]]

:* [[media:DHCOM-linux-imx-3.2.9.config.zip|Kernel configuration for DHCOM iMX25 Linux 3.2.9 (2013-03-27)]]

==== How to build a kernel ====
{| class="wikitable"
|1. Start a terminal on Linux
|-
|2. Copy the above mentioned source files (linux-3.x.y.tar.bz2, .config, *.patch) into our <code>work_path</code>
|-
|3. <tt># ''cd work_path''</tt>
|-
|4. <tt># ''tar xfjv linux-2.6.38.tar.bz2''</tt>
|-
|5. <tt># ''cd work_path/linux-2.6.38''</tt>
|-
|6. <tt># ''patch -p1 <linux-2.6.38_DHCOM_iMX25.patch''</tt>
|-
|7. <tt># ''cp .config work_path/linux-2.6.38''</tt>
|-
|8. <tt># ''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage''</tt>
|}
:* Your new <tt>uImage</tt> file is available in <tt>work_path/linux-2.6.38/arch/arm/boot</tt>
|}

==Update the kernel with U-Boot ==

:The linux kernel will be updated by the [[COM iMX25 Bootloader U-Boot#Update|U-Boot flash update]].

:* [[media:Linux-2.6.38_DHCOM_iMX25_kernel.zip|Binary image 2.6.38 DHCOM iMX25 linux kernel (2014-09-29)]]
:* [[media:DHCOM-linux-imx-3.2.9_BUILD.zip|Binary image 3.2.9 DHCOM iMX25 linux kernel (2016-02-24)]]
:* [[media:DHCOM-linux-imx-3.2.78_BUILD.zip|Binary image 3.2.78 DHCOM iMX25 linux kernel (2016-03-08)]]

:{| class="wikitable"
|1. Copy the <code>'''uImage'''</code> and <code>'''uImage.env'''</code> file onto a microSD card with a FAT file system (you can use the 1st partition on the microSD card)
|-
|2. Insert the microSD card and start the system
|-
|3. Go to the U-Boot console by pressing '''BACKSPACE''' on a RS232 terminal (during startup)
|-
|4. <code>''update linux''</code>
|}

==Debian Rootfilesystem ==
=== Available Rootfilesystems ===
Please have a look at the [[COM_iMX25-D2#Downloads | iMX25 Downloads]] section.

=== External Documentation ===
* [https://debian-handbook.info/browse/stable/ The Debian Administrator's Handbook]: A reference book presenting the Debian distribution, from initial installation to configuration of services. The administration and configuration chapters apply to our Debian based root filesystems.
* [https://www.debian.org/doc/ Debian Documentation]

=== Login ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
||
<tt>
Debian GNU/Linux 6.0 dhcom ttymxc1 

dhcom login: '''root''' 
Password: '''foo'''
</tt>
|}
=== Calibrating the touchscreen ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># TSLIB_TSDEVICE=/dev/input/event0 ts_calibrate</tt>
|}
===Running example Qt Apps ===
{| class="wikitable" align="center" | style="width: color: #000000; background: #FFFFFF;" valign="top" |
|<tt># QWS_MOUSE_PROTO=Tslib:/dev/input/event0 /usr/qt/demos/demoname/demoname -qws</tt>
|}
*'''Remark:''' To start the Qt-Browser replace <tt>demoname</tt> with <tt>browser</tt>

=== Shutdown ===
{| class="wikitable" align="center" | style="width: 400px; color: #000000; background: #FFFFFF;" valign="top" |
|<tt># shutdown -h now</tt>
|}

== How to create a microSD-card with a rootfilesystem on it ==

1. Format a microSD card like following (in linux e.g. gparted, palimpsest) with '''Master Boot Record''' partition scheme
{| class="wikitable" | style="width: 450px; color: #000000; background: #FFFFFF;" valign="top" |
|
<tt>P1 '''FAT''' (Primary partition: 100MB)</tt> 
<tt>P2 '''ext3''' (Primary partition: Residual space)</tt>
|}
2. Untar the root file system to the ext3 partition of the microSD card (Don't copy the tar archive directly to the microSD card)
{| class="wikitable" | style="width: 450px; color: #000000; background: #FFFFFF;" valign="top" |
|
Start the Console on Linux 
<tt># ''su''</tt> 
<tt># ''chmod 755 /path/of/the/microSD_card''</tt> 
<tt># ''cd /path/of/the/microSD_card''</tt> 
<tt># ''tar xfjv path/to/RootFS/Name_of_RootFS_file.tar.bz2''</tt>
|}
'''Remark:''' If you got a *.tar.gz file so type <tt> tar xfzv ... </tt> to extract the rootfilesystem.

==Busybox Rootfilesystem ==
=== Calibrating the touchscreen ===
:{| class="wikitable"
|<code>''TSLIB_TSDEVICE=/dev/event0 ts_calibrate''</code>
|}
===Running example Qt Apps ===
:{| class="wikitable"
|<code>''QWS_MOUSE_PROTO=Tslib:/dev/event0 /usr/qt/demos/demoname/demoname -qws''</code>
|}
:For the Qt-Browser change <code>demoname</code> to <code>browser</code>
=== Login/Shutdown system ===
:{| class="wikitable" style="width: 120px"
||Username: ||root
|-
||Password: ||n/a
|}
:{| class="wikitable"
|<code>''halt''</code>
|}

== Kernel Userspace Interfaces to Access Hardware ==

=== Serial (UART) Interfaces ===
:{| class="wikitable" style="width: 400px"
|style="width: 50%;"|DHCOM (FF) UART 1||<code>/dev/ttymxc1</code>
|-
||DHCOM (BT) UART 2 ||<code>/dev/ttymxc2</code>
|-
||DHCOM (STD) UART 3 ||<code>/dev/ttymxc4</code>
|}

=== I2C Interfaces ===
:{| class="wikitable" style="width: 400px"
|style="width: 50%;"|DHCOM I2C 1||<code>/dev/i2c-1</code>
|-
||DHCOM I2C 2 ||<code>/dev/i2c-2</code>
|}

=== SPI Interfaces ===
:{| class="wikitable" style="width: 400px"
|style="width: 50%;"|DHCOM SPI 1||<code>/dev/spidev1.0</code>
|-
||DHCOM SPI 2 ||<code>/dev/spidev2.0</code>
|}

=== Control the display brightness ===
:{| class="wikitable" style="width: 640px"
|<code>''echo <value> >/sys/devices/platform/imx-fb.0/backlight/imxfb-bl/brightness''</code>
|}
:value range: 0..255

=== Control GPIOs ===

:{|class="wikitable" style="text-align: center; width: 600px"
|-
! DHCOM Name: !! alt. DHCOM Name: !! Port: !! Pin: !! SO-DIMM Pin# !! Linux <GPIO#>
|-
| GPIO A || || 2 || 12 || 154 || 44
|-
| GPIO B || || 3 || 21 || 156 || 85
|-
| GPIO C || || 2 || 4 || 162 || 36
|-
| GPIO D || || 2 || 5 || 163 || 37
|-
| GPIO E || || 2 || 6 || 164 || 38
|-
| GPIO F || || 2 || 7 || 165 || 39
|-
| GPIO G || || 2 || 8 || 167 || 40
|-
| GPIO H || || 2 || 9 || 173 || 41
|-
| GPIO I || || 3 || 17 || 175 || 81
|-
| CIF HSYNC || GPIO J || 1 || 10 || 74 || 10
|-
| CIF PCLK || GPIO K || 1 || 11 || 72 || 11
|-
| CIF MCLK || GPIO L || 1 || 8 || 70 || 8
|-
| CIF VSYNC || GPIO M || 1 || 9 || 68 || 9
|-
| CIF D9 || GPIO N || 4 || 21 || 66 || 117
|-
| CIF D8 || GPIO O || 1 || 7 || 64 || 7
|-
| CIF D7 || GPIO P || 1 || 6 || 62 || 6
|-
| CIF D6 || GPIO Q || 1 || 31 || 60 || 31
|-
| CIF D5 || GPIO R || 1 || 30 || 58 || 30
|-
| CIF D4 || GPIO S || 1 || 29 || 56 || 29
|-
| CIF D3 || GPIO T || 1 || 28 || 54 || 28
|-
| CIF D2 || GPIO U || 1 || 27 || 52 || 27
|}

:Export
:{| class="wikitable" style="width: 640px"
|<code>''echo <GPIO#> >/sys/class/gpio/export''</code>
|}
:Set direction
:{| class="wikitable" style="width: 640px"
|<code>''echo in >/sys/class/gpio/gpioXX/direction''</code>
|-
|<code>''echo out >/sys/class/gpio/gpioXX/direction''</code>
|}
:Set value
:{| class="wikitable" style="width: 640px"
|<code>''echo 0 >/sys/class/gpio/gpioXX/value''</code>
|-
|<code>''echo 1 >/sys/class/gpio/gpioXX/value''</code>
|}
:Get value
:{| class="wikitable" style="width: 640px"
|<code>''cat /sys/class/gpio/gpioXX/value''</code>
|}

:unexport
:{| class="wikitable" style="width: 640px"
|<code>''echo <GPIO#> >/sys/class/gpio/unexport''</code>
|}

=== Initialize and test CAN ===
:Initialize:
:{| class="wikitable"
|<code>''ip link set can0 up type can bitrate 500000''</code>
|}

:Send test message via cansend (part of can-utils):
:{| class="wikitable"
|<code>''cansend can0 100#11.2233.44556677.88''</code>
|}

:Receive message via candump (part of can-utils):
:{| class="wikitable"
|<code>''candump can0''</code>
|}

:Get can-utils:
:* [[media:can-utils_armel.zip|Debian package containing can-utils (ARM)]]

=== Test display / framebuffer ===
:{| class="wikitable" style="width: 1200px"
||<code>fb_1Colorfill</code>|| Fills the framebuffer device with a given RGB color <code>Syntax: fb_1Colorfill [fb (0..31)] [Display Bits (1..8)] [Red value (0..255)] [Green value (0..255)] [Blue value (0..255)]</code>
|-
||<code>fb_fb2BMP</code>||Copies framebuffer device data into a 24Bit BMP-File <code>Syntax: fb_fb2BMP [fb (0..31)] [24-Bit BMP-File]</code>
|-
||<code>fb_LoadBMP</code>||Loads a 24Bit BMP-file into a 32Bit framebuffer device <code>Syntax: fb_LoadBMP [fb (0..31)] [24-Bit BMP-File] [Display Bits (1..8)] [Transparency (0..100)]</code>
|}
:In most common cases the "Display Bits" should be "8"

:Get DH framebuffer tools:
:* [[media:dh_framebuffer_tools.zip|DH framebuffer tools v1.0 (ARM)]]

== Additional Information ==
*[[Linux Kernel Features | Linux Kernel Features ]]
*[[ELBE Overview| Embedded Linux Build Environment (ELBE)]]