COM AM35 Linux

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
• 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

1. Start a terminal on Linux

2. # git clone https://github.com/dh-electronics/linux-am35x.git

3. # mkdir build

4. # cd linux-am35x

5. # git checkout BRANCH (BRANCH=dev/3.2.12_dhcom or BRANCH=dev/3.2.81_dhcom)

6. # ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make O=../build/ dhcm3517_defconfig

7. # ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make -j5 O=../build/ uImage

• Your new uImage file is available in ../build/arch/arm/boot

Remark:

• On linux-am35x.git we use the git branch "master".

Sources older than April 2014 Sources for the AM35 Kernel based on 3.2.12 Mainline Kernel version: 3.2.12 from www.kernel.org Patch for DHCOM AM35 Linux (2014-04-23) [includes RT-Preemptiv patch] Kernel configuration for DHCOM AM35 Linux (2014-04-23) 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 1. Start a terminal on Linux 2. Copy the above mentioned source files (linux-3.x.y.tar.bz2, .config, *.patch) into our work_path 3. # cd work_path 4. # tar xfjv linux-3.2.12.tar.bz2 5. # cd work_path/linux-3.2.12 6. # patch -p1 < ../dh-linux-am35x_xxxxxxxx.patch 7. # cp ../dh-linux-am35x_xxxxxxxx.config .config' 8. # ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- make uImage Your new uImage file is available in work_path/linux-3.2.12/arch/arm/boot

Update the kernel with U-Boot

The linux kernel will be updated by the U-Boot flash update.

• Binary Image DHCOM AM35 linux-3.2.12-rt20 kernel (details see above)

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 BACKSPACE/DEL on a RS232 terminal (during startup)

4. update linux

Debian Rootfilesystem

Available Rootfilesystems

Please have a look at the AM35x Downloads section.

External Documentation

• 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.
• Debian Documentation

Login

Debian GNU/Linux 6.0 dhcom ttyO0 dhcom login: root Password: foo

Shutdown

# shutdown -h now

Calibrating the touchscreen

# ts_calibrate

• Check the enviroment variable "TSLIB_TSDEVICE=/dev/input/event0" with printenv if an error occurs.

Running Qt Demos

# cd /usr/qt/demos/demoname # ./demoname -qws

• For the Qt-Browser change demoname to browser
• If the touchscreen does not work please check the enviroment variable "QWS_MOUSE_PROTO=Tslib:/dev/input/event0" with printenv.

Run Qt demos with powerVR (3d acceleration) support

# cd /usr/qt/demos/embedded/demoname # ./demoname -qws

Run Qt demos with usb mouse input device

# cd /usr/qt/demos/demoname # export QWS_MOUSE_PROTO=Auto:/dev/input/mice # ./demoname -qws

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

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

Remark: If you got a *.tar.gz file so type tar xfzv ... to extract the rootfilesystem.

Kernel Userspace Interfaces to Access Hardware

Serial (UART) Interfaces

DHCOM (FF) UART 1	/dev/ttyO0
DHCOM (BT) UART 2	/dev/ttyO2
DHCOM (STD) UART 3	/dev/ttyO1

I2C Interfaces

DHCOM I2C 1	/dev/i2c-3
DHCOM I2C 2	/dev/i2c-2
On Module Devices	/dev/i2c-1

SPI Interfaces

DHCOM SPI 1	/dev/spidev1.0
DHCOM SPI 2	/dev/spidev2.0

Control the display brightness

echo <value> >/sys/class/backlight/omap-pwm-backlight/brightness

value range: 0..255

Control GPIOs

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

echo <GPIO#> >/sys/class/gpio/export

Remark: Have a look into /sys/class/gpio/ for already configured gpios.

Set direction

echo in >/sys/class/gpio/gpio<GPIO#>/direction

echo out >/sys/class/gpio/gpio<GPIO#>/direction

Set state

echo 0 >/sys/class/gpio/gpio<GPIO#>/value

echo 1 >/sys/class/gpio/gpio<GPIO#>/value

Initialize and Test CAN Interface

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

Receive can messages (part of can-utils):

candump can0

Get can-utils:

• 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)

fb_1Colorfill	Fills the framebuffer device with a given RGB color fb_1Colorfill [fb (0..31)] [Display Bits (1..8)] [Red value (0..255)] [Green value (0..255)] [Blue value (0..255)]
fb_fb2BMP	Copies the framebuffer device data into a 24Bit BMP-File fb_fb2BMP [fb (0..31)] [24-Bit BMP-File]
fb_LoadBMP	Loads a 24Bit BMP-file into a 32Bit framebuffer device fb_LoadBMP [fb (0..31)] [24-Bit BMP-File] [Display Bits (1..8)] [Transparency (0..100)]

Get DH farmebuffer tools:

• DH framebuffer tools version 1.0 (ARM)

Additional Information

• Linux Kernel Features
• Embedded Linux Build Environment (ELBE)