tslib Error & Solution

Task: Build Qt 4.7.1 for board armsys-6410.

Toolchain: supplier provided toolchain (4.2.2-eabi-arm)

Error: When start a Qt example, the following error message show

QWSTslibMouseHandlerPrivate: ts_config() failed with error: 'No such file or directory'

Please check your tslib installation!

The problem is solved by following:

Download & build the latest tslib again from http://tslib.berlios.de/

> tar xzvf tslib-1.4.gz
> cd tslib
>./autogen.sh
>./configure -host=arm-linux -prefix=/usr/local/tslib

>make
>make install

Qt was successfully build with the toolchain:

./configure -prefix /usr/local/qt-4.7.1-armsys-6410 -embedded arm -xplatform qws/linux-arm-g++ -depths 16 -qt-mouse-tslib -I/usr/local/tslib/include -L/usr/local/tslib/lib -R /usr/local/tslib/lib -xmlpatterns -exceptions

make
make install

Copy the installed Qt into root file system, which will be nfs mounted by board

sudo cp -rf /usr/local/qt-4.7.1-armsys-6410 /home/max/work/arena/rootf/armsys6410/root/usr/local/

Start the board by nfs mounting  /home/max/work/arena/rootf/armsys6410/root/
I use minicom here, the parameters are

setenv bootargs "root=/dev/nfs nfsroot=192.168.2.118:/home/max/work/arena/rootf/armsys6410/root/ ip=192.168.2.10:192.168.2.118:192.168.2.1:255.255.255.0:armsys.hzlitai.com:eth0:off console=ttySAC0,115200" 

Check the device file of touchscreen. Assume the device of board is /dev/input/event1

cat /dev/input/event1| hexdump

Now when you move the mouse in the touchscreen, the similar texts will be displayed on the console. It means that /dev/input/event1 is the correct device file of touchscreen on board.

...

0000300 7cc6 3a50 bb73 000b 0003 0001 1f94 0000                                

0000310 7cc6 3a50 bb7d 000b 0000 0000 0000 0000                                
0000320 7cc6 3a50 cee6 000b 0003 0000 0fbb 0000                                
0000330 7cc6 3a50 cefa 000b 0003 0001 1fff 0000                                
0000340 7cc6 3a50 cf03 000b 0000 0000 0000 0000                                
0000350 7cc6 3a50 e269 000b 0001 014a 0000 0000                                
0000360 7cc6 3a50 e27c 000b 0003 0018 0000 0000                                
0000370 7cc6 3a50 e281 000b 0000 0000 0000 0000
....

Add following enviromental variables into /etc/profile

export TSLIB_ROOT=/usr/local/tslib
export TSLIB_TSDEVICE=/dev/input/event1
export TSLIB_CONFFILE=$TSLIB_ROOT/etc/ts.conf
export TSLIB_PLUGINDIR=$TSLIB_ROOT/lib/ts
export TSLIB_CALIBFILE=/etc/pointercal
export TSTS_INFO_FILE=/sys/devices/virtual/input/input0/uevent
export QWS_MOUSE_PROTO=tslib:/dev/input/event1
export QWS_KEYBOARD=TTY:/dev/tty1
export HOME=/root
export QTDIR=/usr/local/qt-4.7.1-armsys-6410
export QPEDIR=/usr/local/qt-4.7.1-armsys-6410
export PATH=$PATH:/usr/local/tslib/lib:$QTDIR/bin
export LD_LIBRARY_PATH=$QTDIR/lib:/usr/local/tslib/lib:/usr/local/lib:$LD_LIBRARY_PATH






Run calibration again.

/usr/local/tslib/bin/ts_calibrate

Try a Qt example,

/usr/local/qt-4.7.1-armsys-6410/examples/widgets/calculator/calculator -qws

The error messages didn't show again.

References

Nice man doc of tslib
http://www.blogger.com/post-edit.g?blogID=5974839100591333846&postID=6336916594199395808

About QWS_MOUSE_PROTO
http://doc.qt.nokia.com/4.7-snapshot/qt-embedded-pointer.html

homepage of tslib
http://tslib.berlios.de/

minicom nfs copy kernel to board
http://www.armsystem.com.cn/bbs/redirect.php?fid=29&tid=12260&goto=nextnewset

http://www.qtcentre.org/threads/23353-Qt-Embedded-4.5-TsLib-and-TSC-10-touch-screen-(Solved)

Build Qt 4.7 for armsys-6410

=======================
Install the crossing toolchain
=======================
refer to chapter 4 安装交叉编译器

交叉编译工具链的安装文件为“ARMSYS6410-B基础配置光盘资料\Linux相关\linux2.6标准版\交叉编译器”目录下的 cross-4.2.2-eabi.tar.bz2.

>tar xjvf cross-4.2.2-eabi.tar.bz2 –C /usr/local/arm
>export PATH=$PATH:/opt/toolchains/arm920t-eabi/bin

=======================
Build tslib (touch screen)
=======================

Install necessary tools

> apt-get install autoconf automake libtool

Download souce of tslib from http://tslib.berlios.de/


Build tslib

> tar xzvf tslib-1.4.gz
> cd tslib
>./autogen.sh
>./configure -host=arm-linux -prefix=/usr/local/tslib -enable-input=no (wrong???)

tslib will be install at /usr/local/tslib. If get error, you may comment out the line " '#define malloc rpl_malloc" in config.h

>make
>make install

Reference: http://blog.chinaunix.net/u2/75270/showart_1793535.html

=======================
Build Qt 4.7.1
=======================

Download qt-4.7.1

>wget http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.7.1.tar.gz
>tar xfzv qt-everywhere-opensource-src-4.7.tar

Configure the Qt Embedded.

>./configure -prefix /usr/local/qt-4.7.1-armsys-6410 -embedded arm -xplatform qws/linux-arm-g++ -depths 16 -qt-mouse-tslib -I/usr/local/tslib/include -L/usr/local/tslib/lib -R /usr/local/tslib/lib -xmlpatterns -exceptions

• -qt-mouse-tslib: Qt will use tslib for touch screen
• -I/usr/local/tslib/include: lib path of tslib
• -L/usr/local/tslib/lib: includepath of tslib
• -qconfig nocursor: no cursor is shown in touch screen
• -xplatform qws/linux-arm-g++: see http://doc.qt.nokia.com/main-snapshot/qt-embedded-crosscompiling.html

Build Qt

>make
>make install

Reference: http://doc.qt.nokia.com/main-snapshot/qt-embedded-crosscompiling.html

A walkaround: assign a static IP to eth0 for nfs remotely start system

I tried to boot the target board "armsys6410" by remotely loading a root file system through nfs. According to the given user manual, the argument of u-boot is

setenv bootargs "root=/dev/nfs nfsroot=192.168.253.2:/hom/localhost/armsys6410/root/ ip=192.168.253.12:192.168.253.2:192.168.253.2:255.255.255.0:armsys.hzlitai.com:eth0:off console=ttySAC0,115200"

Here /home/localhost/armsys6410/root is the file system located at my host machine. 192.168.253.12 is the static ip of board, while 192.168.253.2 should be static ip of host machine.

The problem of mine is I cannot fix a static IP to eth0, when I use at the same time wlan0. I didn't find a ultimate solution for the problem. Here is just walkaround:

Precondition: minicom has been correctly configured, serial port and cross-over cable have been correctly connected between host and target.

1) reset the board
2) press any key to suspend the booting (I use u-boot here)
3) >sudo ifconfig eth0 192.168.253.2 netmask 255.255.255.0 up
4) in minicom, input "reset"


Then the board can start with given root file system

Setup minicom for mini2440

For windows, it is recommended to use Hyperterminal for serial port communication. In order to develop under linux via nfs, a terminal software 'Minicom' is installed and applied instead of Hyperterminal. The USB to serial adapter is used for my laptop. The following items are related for Minicom.

• Install minicom package
• Check if there is active serial ports:

>dmesg | grey tty

[    0.004000] console [tty0] enabled

[    1.174860] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

[ 2237.927394] usb 3-1: pl2303 converter now attached to ttyUSB0

• Check read/write permissions on /dev/ttyUSB0 file:

>ls -la /dev | grep ttyUSB0

crw-rw----  1 root dialout 188,   0 2009-10-10 13:59 ttyUSB0

• If the permissions are not set as above, it can be configured as below:

>chown root /dev/ttyUSB0

>chgrp dialout /dev/ttyUSB0

>chmod 660 /dev/ttyUSB0

• Add debian user in the dialout group (for me the user is 'lp')

>adduser lp dialout

• To see which users are members of the dialout group, open the /etc/group file and look for th eline beginning with dialout

>cat /etc/group | grep dialout

• Start and configure minicom under superuser mode

>minicom -s

>Select 'Select port setup'

>Change Serial Device from '/dev/ttyS1' to '/dev/ttyUSB0'

>Set Hardware Flow Control from 'Yes' to 'No'

>'Save setup as ...' mini2440_config'

• Start minicom using 'mini2440_config'

>minicom mini2440_config

• Leave minicom

>Ctrl A->X

IMPORTANT NOTES:
If you use a linux system in vmware, this configuration may not work. You need to

1. check if your vmware is a bridged network
2. disable your firewall in your host machine.
3. read this tutorial.

Several Patent Search Engines

 

• Free Patents Online: http://www.freepatentsonline.com/
• Patent Storm: http://www.patentstorm.us/
• Google Patents: http://www.google.com/patents
• United States Patent: http://www.uspto.gov/
• World Intellectual Property Organization: http://www.wipo.int/

Build an Angstrom Image & Toolcain for mini2440

According to the tutorial in [1], an Angstrom image has been successfully bitbaked for mini2440. But an Angstrom toolchain is still missing. Analog to [2], the following commands can bitbake a compatible toolchain for this image.

>source source-me.txt
>bitbake meta-toolchain

The toolchain can be found at "angstrom-dev/deploy/glibc/sdk"

angstrom-2010.7-test-20101117-i686-linux-armv4t-linux-gnueabi-toolchain-extras.tar.bz2
angstrom-2010.7-test-20101117-i686-linux-armv4t-linux-gnueabi-toolchain.tar.bz2

To install the toolchains:

> tar -C / -jxvf *.tar.bz2

The toolchain is installed at /usr/local/angstrom/arm/
To use the toolchain, source the script[3]:
>. /usr/local/angstrom/arm/environment-setup

Reference:
[1] http://www.electronics.diycinema.co.uk/embedded/mini2440/configuring-open-embedded-to-bake-angstrom-images-for-the-mini2440/
[2] http://groups.google.com/group/beagleboard/browse_thread/thread/b11d9c53d6f09536/33c537f7d08f1952
[3] http://docs.openembedded.org/usermanual/html/ch05s08.html

Update date&time in Debian

>sudo apt-get update
>sudo apt-get install ntpdate
>sudo ntpdate  ntp.ubuntu.com