__NOTOC__
[[Image:DHCOM.jpg|1200px|Computer On Module - DHCOM Standard]]

== Computer On Module ==

*'''[[COM iMX6-D2]]'''

*'''[[COM AM35-D2]]'''

*'''[[COM iMX25-D2]]'''

*'''[[COM PXA270-D2]]'''

== Development Kit ==
*'''[[DHCOM Premium Developer Kit]]'''

== Software Development ==
=== Linux ===
*'''[[Virtual Machine for Application Development]]'''
*'''[[ELBE Overview| Embedded Linux Build Environment (ELBE)]]'''
*'''[[Yocto | Yocto]]'''
*'''[[Linux Kernel Features | Optional Linux Kernel Features ]]'''
*'''[[UBI/UBIFS Filesystem|UBI/UBIFS Filesystem Basics]]'''


== FAQ ==
*'''[[FAQ_General | General]]'''
*'''[[FAQ_Get Started | Get Started]]'''

DHSOM

2015-03-11T15:30:30Z

Rgoellner:

File:2012-08-10 Linux-3.2.12 DHCOM AM35 config.zip

2012-08-17T13:02:27Z

Rgoellner:

File:2012-08-10 Linux-3.2.12 DHCOM AM35 patch.zip

2012-08-17T13:01:28Z

Rgoellner:

COM AM35 Linux

2012-08-17T13:00:52Z

Rgoellner: /* Building your own Kernel */

== FAQ ==

=== Ethernet does not work ===
Check if the line "allow-hotplug eth0" in the file "/etc/network/interfaces" is activated. You can activate the ethernet interface on a running system with the command:
:{| class="wikitable"
|<code>''ifconfig eth0 up''</code>
|}
:'''Remark:''' To work with a nfs-rootfilesystem you have to disable the line "allow-hotplug eth0" in the file "/etc/network/interfaces". Maybe the system was prepared for this method for development and nobody did change it back.

=== How to set a Linux environment variable? ===
This example shows you how to configure the system to use a proxy-server with a environment variable.
:{| class="wikitable"
|<code>''export http_proxy=http://192.168.xxx.xxx:xxxx</code>
|}

=== How to schedule jobs to run periodically at certain times or dates? ===
You can use the cron daemon and/or anacron. To use anacron you have to copy or link your program or script into one of the the following folders:
:{| class="wikitable"
|<code>/etc/cron.hourly</code>
|-
|<code>/etc/cron.daily</code>
|-
|<code>/etc/cron.weekly</code>
|-
|<code>/etc/cron.monthly</code>
|}
For further information have a look at the general linux documentation.

== Linux virtual machine for development ==
{{DebianVM Development}}

== Building your own Kernel ==

=== Sources for the AM35 Kernel: ===

:* [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:2012-08-10_Linux-3.2.12_DHCOM_AM35_patch.zip|Patch to DHCOM AM35 Linux (2012-08-10)]]

:* [[media:2012-08-10_Linux-3.2.12_DHCOM_AM35_config.zip|Kernel configuration for DHCOM AM35 Linux (2012-08-10)]]

=== How to build a kernel: ===

:{| class="wikitable"
|1. Start the Console on Linux
|-
|2. Copy the above mentioned source files into our <code>work_path</code>
|-
|3. <code>''cd work_path''</code>
|-
|4. <code>''tar xfjv linux-3.2.12.tar.bz2''</code>
|-
|5. <code>''cd work_path/linux-3.2.12''</code>
|-
|6. <code>''patch -p1 <xxxx-xx-xx_linux-3.2.12_DHCOM_AM35.patch''</code>
|-
|7. <code>''cp xxxx-xx-xx_Linux-3.2.12_DHCOM_AM35.config work_path/linux-3.2.12/.config''</code>
|-
|8. <code>''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage''</code>
|}
:The <code>uImage</code> file will you find in <code>../build-linux/arch/arm/boot</code>

== 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:Linux-3.2.12_DHCOM_AM35_kernel.zip|Current built of the 3.2.12 DHCOM AM35 linux kernel (2012-08-10)]]

:{| 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 '''DEL''' on a RS232 terminal (during startup)
|-
|4. <code>''update linux''</code>
|}

== Debian system ==

=== How to create a microSD-card with a rootfilesystem on it ===

:1. Format a microSD card like following (in linux e.g. you can use palimpsest) with '''Master Boot Record''' partition scheme
::{| class="wikitable"
|P1 '''FAT''' (Primary partition: 100MB)
|-
|P2 '''ext3''' (Primary partition: Residual space)
|}

: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"
|Start the Console on Linux
|-
|<code>''su''</code>
|-
|<code>''chmod 755 /path/of/the/microSD_card''</code>
|-
|<code>''cd /path/of/the/microSD_card''</code>
|-
|<code>''tar xfjv path/to/RootFS/Name_of_RootFS_file.tar.bz2''</code>
|}
:'''Remark:''' If you got a *.tar.gz file so type <code> tar xfzv ... </code> to extract the rootfilesystem.

=== Login/Shutdown system ===
:{| class="wikitable" style="width: 120px"
||Username: ||root
|-
||Password: ||foo
|}
:{| class="wikitable"
|<code>''shutdown -h now''</code>
|}

=== Calibrating the touchscreen ===
:{| class="wikitable"
|<code>''ts_calibrate''</code>
|}
:Check the enviroment variable "TSLIB_TSDEVICE=/dev/input/event0" with <code> printenv </code> if an error occurs.

===Running Qt Demos ===
:{| class="wikitable"
|<code>''cd /usr/qt/demos/demoname''</code>
|-
|<code>''demoname -qws''</code>
|}
: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"
|<code>''cd /usr/qt/demos/embedded/demoname''</code>
|-
|<code>''demoname -qws''</code>
|}

'''''Run demos with a usb-mouse as input device:'''''
:{| class="wikitable"
|<code>''cd /usr/qt/demos/demoname''</code>
|-
|<code>''/QWS_MOUSE_PROTO=Auto:/dev/input/mice demoname -qws''</code>
|}

:'''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 control the display brightness ===
:{| class="wikitable"
|<code>''echo <value> >/sys/class/backlight/omap-pwm-backlight/brightness''</code>
|}
:value range: 0..255

=== How to control the 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 ===
: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>
|}

File:Linux-3.2.12 DHCOM AM35 kernel.zip

2012-08-14T08:46:20Z

Rgoellner: uploaded a new version of "File:Linux-3.2.12 DHCOM AM35 kernel.zip": DHUpdate.ini entfernt

Kernel mit SPI aktiviert im Userspace.

COM AM35 Linux

2012-08-14T08:44:17Z

Rgoellner:

== FAQ ==

=== Ethernet does not work ===
Check if the line "allow-hotplug eth0" in the file "/etc/network/interfaces" is activated. You can activate the ethernet interface on a running system with the command:
:{| class="wikitable"
|<code>''ifconfig eth0 up''</code>
|}
:'''Remark:''' To work with a nfs-rootfilesystem you have to disable the line "allow-hotplug eth0" in the file "/etc/network/interfaces". Maybe the system was prepared for this method for development and nobody did change it back.

=== How to set a Linux environment variable? ===
This example shows you how to configure the system to use a proxy-server with a environment variable.
:{| class="wikitable"
|<code>''export http_proxy=http://192.168.xxx.xxx:xxxx</code>
|}

=== How to schedule jobs to run periodically at certain times or dates? ===
You can use the cron daemon and/or anacron. To use anacron you have to copy or link your program or script into one of the the following folders:
:{| class="wikitable"
|<code>/etc/cron.hourly</code>
|-
|<code>/etc/cron.daily</code>
|-
|<code>/etc/cron.weekly</code>
|-
|<code>/etc/cron.monthly</code>
|}
For further information have a look at the general linux documentation.

== Linux virtual machine for development ==
{{DebianVM Development}}

== Building your own Kernel ==

== 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:Linux-3.2.12_DHCOM_AM35_kernel.zip|Current built of the 3.2.12 DHCOM AM35 linux kernel (2012-08-10)]]

:{| 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 '''DEL''' on a RS232 terminal (during startup)
|-
|4. <code>''update linux''</code>
|}

== Debian system ==

=== How to create a microSD-card with a rootfilesystem on it ===

:1. Format a microSD card like following (in linux e.g. you can use palimpsest) with '''Master Boot Record''' partition scheme
::{| class="wikitable"
|P1 '''FAT''' (Primary partition: 100MB)
|-
|P2 '''ext3''' (Primary partition: Residual space)
|}

: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"
|Start the Console on Linux
|-
|<code>''su''</code>
|-
|<code>''chmod 755 /path/of/the/microSD_card''</code>
|-
|<code>''cd /path/of/the/microSD_card''</code>
|-
|<code>''tar xfjv path/to/RootFS/Name_of_RootFS_file.tar.bz2''</code>
|}
:'''Remark:''' If you got a *.tar.gz file so type <code> tar xfzv ... </code> to extract the rootfilesystem.

=== Login/Shutdown system ===
:{| class="wikitable" style="width: 120px"
||Username: ||root
|-
||Password: ||foo
|}
:{| class="wikitable"
|<code>''shutdown -h now''</code>
|}

=== Calibrating the touchscreen ===
:{| class="wikitable"
|<code>''ts_calibrate''</code>
|}
:Check the enviroment variable "TSLIB_TSDEVICE=/dev/input/event0" with <code> printenv </code> if an error occurs.

===Running Qt Demos ===
:{| class="wikitable"
|<code>''cd /usr/qt/demos/demoname''</code>
|-
|<code>''demoname -qws''</code>
|}
: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"
|<code>''cd /usr/qt/demos/embedded/demoname''</code>
|-
|<code>''demoname -qws''</code>
|}

'''''Run demos with a usb-mouse as input device:'''''
:{| class="wikitable"
|<code>''cd /usr/qt/demos/demoname''</code>
|-
|<code>''/QWS_MOUSE_PROTO=Auto:/dev/input/mice demoname -qws''</code>
|}

:'''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 control the display brightness ===
:{| class="wikitable"
|<code>''echo <value> >/sys/class/backlight/omap-pwm-backlight/brightness''</code>
|}
:value range: 0..255

=== How to control the 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 ===
: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>
|}

File:Linux-3.2.12 DHCOM AM35 kernel.zip

2012-08-14T08:40:14Z

Rgoellner: Kernel mit SPI aktiviert im Userspace.

Kernel mit SPI aktiviert im Userspace.

COM iMX25 Linux

2012-08-14T08:35:29Z

Rgoellner: /* Update the kernel with U-Boot */

== FAQ ==

:What are the names of the UARTs in Linux?
:*FF-UART: <code>/dev/ttymxc1</code>
:*BT-UART: <code>/dev/ttymxc2</code>
:*STD-UART: <code>/dev/ttymxc4</code>

== Linux virtual machine for development ==
{{DebianVM Development}}

== Building your own Kernel ==

=== Sources for the iMX25 Kernel: ===

:* [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.tar.bz2 Kernel version: 2.6.38 from www.kernel.org]

:* [[media:Linux-2.6.38_DHCOM_iMX25_patch.zip|Patch to DHCOM iMX25 Linux (2012-02-02)]]

:* [[media:Linux-2.6.38_DHCOM_iMX25_config.zip|Kernel configuration for DHCOM iMX25 Linux (2012-02-02)]]

=== How to build a kernel: ===

:{| class="wikitable"
|1. Start the Console on Linux
|-
|2. Copy the above mentioned source files into our <code>work_path</code>
|-
|3. <code>''cd work_path''</code>
|-
|4. <code>''tar xfjv linux-2.6.38.tar.bz2''</code>
|-
|5. <code>''cd work_path/linux-2.6.38''</code>
|-
|6. <code>''patch -p1 <linux-2.6.38_DHCOM_iMX25.patch''</code>
|-
|7. <code>''cp .config work_path/linux-2.6.38''</code>
|-
|8. <code>''ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage''</code>
|}
:The <code>uImage</code> file will you find in <code>../build-linux/arch/arm/boot</code>

== 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|Current built of the 2.6.38 DHCOM iMX25 linux kernel (2012-02-02)]]

:{| 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 '''DEL''' on a RS232 terminal (during startup)
|-
|4. <code>''update linux''</code>
|}

== How to use/update our root file system ==

:* [[media:RootFS_DN_20110805et4_HL5 (03.02.2012).tar.bz2|Current Debian root file system, based on Debian 6.0 "Squeeze" (2012-02-03)]]
:: [[COM iMX25 Linux#Debian system|Login data for the Debian system]]

:1. Format a microSD card like following (in linux e.g. you can use palimpsest) with '''Master Boot Record''' partition scheme
::{| class="wikitable"
|P1 '''FAT''' (Primary partition: 100MB)
|-
|P2 '''ext3''' (Primary partition: Residual space)
|}

: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"
|Start the Console on Linux
|-
|<code>''su''</code>
|-
|<code>''chmod 755 /path/of/the/microSD_card''</code>
|-
|<code>''cd /path/of/the/microSD_card''</code>
|-
|<code>''tar xfjv path/to/RootFS/Name_of_RootFS_file.tar.bz2''</code>
|}

== How to control the display brightness ==
:{| class="wikitable"
|<code>''echo <value> >/sys/devices/platform/imx-fb.0/backlight/imxfb-bl/brightness''</code>
|}
:value range: 0..255

== How to control the GPIOs ==
:{|class="wikitable" style="text-align: center; width: 400px"
|-
! DHCOM Name: !! Port: !! Pin: !! Linux GPIO #
|-
| GPIO A || 2 || 12 || 44
|-
| GPIO B || 3 || 21 || 85
|-
| GPIO C || 2 || 4 || 36
|-
| GPIO D || 2 || 5 || 37
|-
| GPIO E || 2 || 6 || 38
|-
| GPIO F || 2 || 7 || 39
|-
| GPIO G || 2 || 8 || 40
|-
| GPIO H || 2 || 9 || 41
|-
| GPIO K || 2 || 10 || 42
|}

:Export
:{| class="wikitable"
|<code>''echo <GPIO#> >/sys/class/gpio/export''</code>
|}
:Set direction
:{| class="wikitable"
|<code>''echo in >/sys/class/gpio/gpioXX/direction''</code>
|-
|<code>''echo out >/sys/class/gpio/gpioXX/direction''</code>
|}
:Set value
:{| class="wikitable"
|<code>''echo 0 >/sys/class/gpio/gpioXX/value''</code>
|-
|<code>''echo 1 >/sys/class/gpio/gpioXX/value''</code>
|}
:Get value
:{| class="wikitable"
|<code>''cat /sys/class/gpio/gpioXX/value''</code>
|}

:unexport
:{| class="wikitable"
|<code>''echo <GPIO#> >/sys/class/gpio/unexport''</code>
|}

== Debian system ==
=== Calibrating the touchscreen ===
:{| class="wikitable"
|<code>''TSLIB_TSDEVICE=/dev/input/event0 ts_calibrate''</code>
|}
===Running example Qt Apps ===
:{| class="wikitable"
|<code>''QWS_MOUSE_PROTO=Tslib:/dev/input/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: ||foo
|}
:{| class="wikitable"
|<code>''shutdown -h now''</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>
|}

== Busybox system ==
=== 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>
|}

COM iMX25 Linux

2012-05-22T12:41:11Z

Rgoellner: /* Get the Virtual machine */

== FAQ ==

== Linux virtual machine for development ==

=== Get the Virtual machine ===
* [http://www.vmware.com/go/get-player-de Get the VMware player]

* [[media:Debian Squeeze v1.3.zipx|(mirror 1)]] Password for devel user: '''devel''' Password for root user: '''root'''

History:

v1.3 - Debian Squeeze v1.3.zipx - Mono 2.10
- mtd-utils
- Install system updates

v1.2 - Debian Squeeze v1.2.zipx - Emdebian Toolchain gcc 4.3 / g++ 4.3
- TortoiseHg + TortoiseHg for Nautilus
- Add Plugin "REST Client" in Iceweasel

v1.1 - Debian Squeeze v1.1.zipx - Update Eclipse to Indigo with CDT 8.0
- Add demo project "crosshelloworld"

v1.0 - Debian Squeeze.zipx - First release

=== 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. For Codesourcery it is the folder "CodeSourcery/Sourcery_G++_Lite/bin". Under Prefix type "arm-none-linux-gnueabi-".

== Building your own Kernel ==

=== Sources for the iMX25 Kernel: ===

* [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.tar.bz2 Kernel version: 2.6.38 from www.kernel.org]

* [[media:Linux-2.6.38_DHCOM_iMX25_patch.zip|Patch to DHCOM iMX25 Linux (2012-02-02)]]

* [[media:Linux-2.6.38_DHCOM_iMX25_config.zip|Kernel configuration for DHCOM iMX25 Linux (2012-02-02)]]

=== How to build a kernel: ===

1. Start the Console on Linux
2. $ tar xfjv linux-2.6.38.tar.bz2 (in work_path)
3. $ cd /work_path/linux-2.6.38
4. $ patch -p1 <linux-2.6.38_DHCOM_iMX25.patch
5. $ cp .config /work_path/linux-2.6.38
6. $ ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage

The uImage file will you find in ../build-linux/arch/arm/boot

== Update the kernel with U-Boot ==

You can update the linux kernel with [[COM iMX25 Bootloader U-Boot#Flash Update|U-Boot flash update]].

* [[media:Linux-2.6.38_DHCOM_iMX25_kernel.zip|Current built of the 2.6.38 DHCOM iMX25 linux kernel (2012-02-02)]]

1. Copy the "uImage" and "uImage.env" 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 DEL on a RS232 terminal (during startup)
4. $ update linux

== How to use/update our root file system ==

* [[media:RootFS_DN_20110805et4_HL5 (03.02.2012).tar.bz2|Current Debian root file system, based on Debian 6.0 "Squeeze" (2012-02-03)]]
: [[COM iMX25 Linux#Debian system|Login data for the Debian system]]

1. Format a microSD card like following (in linux e.g. you can use palimpsest) with "Master Boot Record" partition scheme
P1 FAT (Primary partition: 100MB)
P2 ext3 (Primary partition: Residual space)
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)
Start the Console on Linux
$ su
$ chmod 755 /path/of/the/microSD_card
$ cd /path/of/the/microSD_card
$ tar xfjv path/to/RootFS/Name_of_RootFS_file.tar.bz2

== How to control the display brightness ==
$ echo <value> >/sys/devices/platform/imx-fb.0/backlight/imxfb-bl/brightness

value range: 0..255

== Debian system ==
=== Calibrating the touchscreen ===
$ TSLIB_TSDEVICE=/dev/input/event0 ts_calibrate
===Running example Qt Apps ===
$ QWS_MOUSE_PROTO=Tslib:/dev/input/event0 /usr/qt/demos/demoname/demoname -qws
For the Qt-Browser change demoname to browser
=== Login/Shutdown system ===
Login:
Name: root
password: foo

Shutdown:
$ shutdown -h now
=== Initialize and test CAN ===
Initialize:
$ ip link set can0 up type can bitrate 500000

Send test message via cansend (part of can-utils):
$ cansend can0 100#11.2233.44556677.88

== Busybox system ==
=== Calibrating the touchscreen ===
$ TSLIB_TSDEVICE=/dev/event0 ts_calibrate
===Running example Qt Apps ===
$ QWS_MOUSE_PROTO=Tslib:/dev/event0 /usr/qt/demos/demoname/demoname -qws
For the Qt-Browser change demoname to browser
=== Login/Shutdown system ===
Login:
Name: root
password: n/a

Shutdown:
$ halt

COM iMX25 Linux

2012-02-22T16:14:18Z

Rgoellner: /* Get the Virtual machine */

== FAQ ==

== Linux virtual machine for development ==

=== Get the Virtual machine ===
* [http://www.vmware.com/go/get-player-de Get the VMware player]

* [[media:Debian Squeeze v1.2.zipx|(mirror 2)]] Password for devel user: '''devel''' Password for root user: '''root'''

History:

v1.2 - Debian Squeeze v1.2.zipx - Emdebian Toolchain gcc 4.3 / g++ 4.3
- TortoiseHg + TortoiseHg for Nautilus
- Add Plugin "REST Client" in Iceweasel

v1.1 - Debian Squeeze v1.1.zipx - Update Eclipse to Indigo with CDT 8.0
- Add demo project "crosshelloworld"

v1.0 - Debian Squeeze.zipx - First release

=== 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. For Codesourcery it is the folder "CodeSourcery/Sourcery_G++_Lite/bin". Under Prefix type "arm-none-linux-gnueabi-".

== Building your own Kernel ==

=== Sources for the iMX25 Kernel: ===

* [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.38.tar.bz2 Kernel version: 2.6.38 from www.kernel.org]

* [[media:Linux-2.6.38_DHCOM_iMX25_patch.zip|Patch to DHCOM iMX25 Linux (2012-02-02)]]

* [[media:Linux-2.6.38_DHCOM_iMX25_config.zip|Kernel configuration for DHCOM iMX25 Linux (2012-02-02)]]

=== How to build a kernel: ===

1. Start the Console on Linux
2. $ tar xfjv linux-2.6.38.tar.bz2 (in work_path)
3. $ cd /work_path/linux-2.6.38
4. $ patch -p1 <linux-2.6.38_DHCOM_iMX25.patch
5. $ cp .config /work_path/linux-2.6.38
6. $ ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage

The uImage file will you find in ../build-linux/arch/arm/boot

== Update the kernel with U-Boot ==

You can update the linux kernel with [[COM iMX25 Bootloader U-Boot#Flash Update|U-Boot flash update]].

* [[media:Linux-2.6.38_DHCOM_iMX25_kernel.zip|Current built of the 2.6.38 DHCOM iMX25 linux kernel (2012-02-02)]]

1. Copy the "uImage" and "uImage.env" 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 DEL on a RS232 terminal (during startup)
4. $ update linux

== How to use/update our root file system ==

* [[media:RootFS_DN_20110805et4_HL5 (03.02.2012).tar.bz2|Current Debian root file system (2012-02-03)]]
: [[COM iMX25 Linux#Debian system|Login data for the Debian system]]

1. Format a microSD card like following (in linux e.g. you can use palimpsest)
MBR partition scheme
P1 FAT (Primary partition: 100MB)
P2 ext3 (Primary partition: Residual space)
2. Copy root file system onto the ext3 partition of the microSD card
Start the Console on Linux
$ su
$ chmod 755 /path/of/the/microSD card
$ cd /path/of/the/microSD card
$ tar xfjv Name_of_RootFS_file.tar.bz2

== How to control the display brightness ==
$ echo <value> >/sys/devices/platform/imx-fb.0/backlight/imxfb-bl/brightness

value range: 0..255

== Debian system ==
=== Calibrating the touchscreen ===
$ TSLIB_TSDEVICE=/dev/input/event0 ts_calibrate
===Running example Qt Apps ===
$ QWS_MOUSE_PROTO=Tslib:/dev/input/event0 /usr/qt/demos/demoname/demoname -qws
For the Qt-Browser change demoname to browser
=== Login/Shutdown system ===
Login:
Name: root
password: foo

Shutdown:
$ shutdown -h now
=== Initialize and test CAN ===
Initialize:
$ ip link set can0 up type can bitrate 500000

Send test message via cansend (part of can-utils):
$ cansend can0 100#11.2233.44556677.88

== Busybox system ==
=== Calibrating the touchscreen ===
$ TSLIB_TSDEVICE=/dev/event0 ts_calibrate
===Running example Qt Apps ===
$ QWS_MOUSE_PROTO=Tslib:/dev/event0 /usr/qt/demos/demoname/demoname -qws
For the Qt-Browser change demoname to browser
=== Login/Shutdown system ===
Login:
Name: root
password: n/a

Shutdown:
$ halt