Revision as of 12:38, 1 August 2012 (view source) Pau (talk | contribs) ← Older edit		Revision as of 13:04, 1 August 2012 (view source) Pau (talk | contribs) Newer edit →
Line 160:		Line 160:
	*Architecture: arm		*Architecture: arm
	*GNU target: arm-none-linux-gnueabi		*GNU target: arm-none-linux-gnueabi
−	*Sysroot: /opt/poky/1.2/sysroots/armv7a-vfp-neon-poky-linux-gnueabi	+	*Sysroot: (empty)<br>
	*Location of debugging information: (empty)		*Location of debugging information: (empty)
−	*Override host GDB start script: (empty)<br>	+	*Override host GDB start script: download [http://labs.isee.biz/images/a/a1/Gdbinit_for_qt.tar.bz2 gdbinit] file, uncompress to home folder and select it (/home/jdoe/gdbinit)<br>
	'''NOTE:''' You cannot use igep-remote-x program because Qt-demo image doesn't have X installed.<br>		'''NOTE:''' You cannot use igep-remote-x program because Qt-demo image doesn't have X installed.<br>

---

Revision as of 13:04, 1 August 2012

"CHECK ALL IN A NEW VIRTUAL MACHINE"

TODO: Note that you cannot use stepin only stepover (all debug chapters)

TODO: Explain that Eclipse only can build ARM projects

How to develop with Qt under IGEP

Overview

This guide can be helpful to learnt to develop Qt applications under IGEP Boards. Qt is a cross-platform application framework that is widely used for developing application software with a graphical user interface, and also used for developing non-GUI programs such as command-line tools and consoles for servers. You can get more information here.

Requirements

There are some requisites to follow this guide:

• IGEP SDK VM: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 2.3 "Setting up and running the VM")
  
• IGEP Qt Demo: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card") and install qt4e-demo-image-igep00x0.tar.bz2 instead IGEP firmware.
• IGEPv2, IGEP BERLIN or IGEP PARIS
• MicroSD Card (at least 2Gbytes)
  

Download and install Qt demo image to a SD

Once you have open IGEP SDK VM, launch a terminal and type:

cd Desktop/
wget http://downloads.isee.biz/denzil/binary/qt4e-demo-image-igep00x0.tar.bz2 
git clone git://git.isee.biz/pub/scm/igep-tools.git
cd igep-tools/scripts

Insert a SD-Card media and use the igep-media-create script to copy the firmware to SD-Card media, required options are:

• --mmc </dev/sdX>

       unformated MMC Card

• --image <filename>

       specify file used to create the bootable SD card.

• --machine <machine>

       specify the machine. Options are igep0020, igep0030 or igep0032

For example, assuming the SD card device takes "/dev/sdf" and you have and IGEPv2 board (igep0020), type:

./igep-media-create --mmc /dev/sdf --machine igep0020 --image /home/jdoe/Desktop/qt4e-demo-image-igep00x0.tar.bz2

This should give you a bootable SD-card

Prepare Qt demo image

Qt demo image is a root filesystem build by Yocto that contains Qt embedded libraries, also this image has some Qt examples for testing purposes.

This image doesn't have openssh and gdbserver, so we should install these packages to develop Qt applications. Open a shell prompt using serial communication (IGEP SDK SOFTWARE MANUAL chapter 3.1 "Using serial mode") and type the following commands:

zypper ref
zypper in openssh
zypper in gdbserver

Now you can connect between IGEP and VM using SSH protocol:

ssh root@"IGEP IP for example: 192.168.5.1"

Using Qt Creator

First Steeps

Open Program:

Go to Applications -> IGEP development -> Qt Creator

^{Click to enlarge image}

Open an example:

Copy your desired example from: /opt/QtSDK/Examples/4.7 to your desktop.

^{Click to enlarge image}

NOTE: some examples (like hellogl) cannot be compiled to ARM, for this How-to is used calculator example.

Open this example with Qt Creator, set Desktop target and use for each Qt Version one debug and one release

^{Click to enlarge image}

ARM Platform

Build Programs

To compile to ARM for IGEP go to Project use the following configuration at Projects field -> Build:

^{Click to enlarge image}

NOTE: Use Debug Release if you want to debug later

Compile with: Build->Clean All and Build->Build All (Ctrl+Shift+B).

Run Programs

Once you compiled the program pass it from VM to IGEP via SSH, launch a terminal and type:

scp "pathtobinary" root@"IGEP IP for example: 192.168.5.1":/home/root

Get a remote shell prompt and run your program:

ssh root@"IGEP IP for example: 192.168.5.1"
./"binary"  "optional:arguments"

^{Click to enlarge image}

NOTE: You cannot use igep-remote-x program because Qt-demo image doesn't have X installed.

Debug Programs

Once you compiled the program pass it from VM to IGEP via SSH, launch a terminal and type:

scp "pathtobinary" root@"IGEP IP for example: 192.168.5.1":/home/root

Get a remote shell prompt and run gdbserver:

ssh root@"IGEP IP for example: 192.168.5.1"
gdbserver "VM IP for example: 192.168.5.10":1000 "pathtobinary" "optional:armguments"

Now use the followings steps to debug program:

^{Click to enlarge image}

Image 1: set breakpoints in your source code

Image 3: use the following configuration:

• Debugger: /opt/poky/1.2/sysroots/i686-pokysdk-linux/usr/bin/armv7a-vfp-neon-poky-linux-gnueabi/arm-poky-linux-gnueabi-gdb
• Local executable: "pathtohostbinary"
• Host and port: "IGEP IP for example: 192.168.5.1":1000
• Architecture: arm
• GNU target: arm-none-linux-gnueabi
• Sysroot: (empty)
  
• Location of debugging information: (empty)
• Override host GDB start script: download gdbinit file, uncompress to home folder and select it (/home/jdoe/gdbinit)
  

NOTE: You cannot use igep-remote-x program because Qt-demo image doesn't have X installed.

x86 Platform

Build Programs

To compile to x86 go to Project use the following configuration at Projects field -> Build:

^{Click to enlarge image}

NOTE: Use Debug Release if you want to debug later

Compile with: Build->Clean All and Build->Build All (Ctrl+Shift+B).

Run Programs

Use run button (Ctrl+R).

^{Click to enlarge image}

Debug Programs

Set breakpoints in your source code and press debug button (F5)

^{Click to enlarge image}

Set up a NFS between IGEP Board and IGEP VM (check at prove it)

Overview

Network File System (NFS) is a Distributed file system protocol originally developed by Sun Microsystems in 1984, allowing a user on a client Computer to access files over a network in a manner similar to how local storage is accessed. NFS, like many other protocols, builds on the Open Network Computing Remote Procedure Call (ONC RPC) system. The Network File System is an open standard defined in RFCs, allowing anyone to implement the protocol. More information here.

In IGEP Boards, NFS protocol can be used to mount a whole rootfs partition located in a remote disk like Virtual Machine, this method can be useful for:

• Your remote rootfs will not be limited by flash or MicroSD memory storage
• You can transfer binaries without using remote connections
• You can test other rootfs only editing igep.ini configuration file.

^{Click to enlarge image}

Requirements

There are some requisites to follow this guide:

• IGEP SDK VM: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 2.3 "Setting up and running the VM")
  
• IGEP Qt Demo or IGEP Firmware: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card")
  
• IGEP Board with Ethernet or Wifi connection
  
• MicroSD Card (at least 2Gbytes)

Set up NFS at VM

Download and extract IGEP root filesystem

ISEE mantains two rootfs builded with Yocto tools:

• IGEP firmware: default software shipped in all IGEP Boards. It comes with some documentation and tools, so you need to uncompress again to extract rootfs

wget http://downloads.isee.biz/denzil/binary/igep_firmware-yocto-1.2.1-1.tar.bz2 
tar jxf igep_firmware-yocto-*.tar.bz2
cd igep_firmware-yocto-*
sudo mkdir /srv/{your_rootfs_dir}
sudo tar jxf demo-image-sato-igep00x0.tar.bz2 -C /srv/{your_rootfs_dir} 

• Qt demo: demo filesystem with Qt libraries and examples

wget http://downloads.isee.biz/denzil/binary/qt4e-demo-image-igep00x0.tar.bz2 
sudo mkdir /srv/{your_rootfs_dir}
sudo tar jxf qt4e-demo-image-igep00x0.tar.bz2 -C /srv/{your_rootfs_dir}

Configure NFS Server

• Install nfs-kernel-server:

sudo apt-get install nfs-kernel-server 

• Make directory exports.d:
  

sudo mkdir /etc/exports.d 

Edit /etc/exports file, add the following line and save the changes:

/srv/{your_rootfs_dir} *(rw,sync,no_subtree_check,no_root_squash)

Export NFS file system:

sudo exportfs -a

NOTE: You can have as many rootfs as you want

Set up NFS at IGEP Board

MicroSD boot

Configure igep.ini file located at boot partition:

• Comment MMC boot:

;  --- Configure MMC boot ---
;root=/dev/mmcblk0p2 rw rootwait

• Add NFS configuration:

;  --- Configure NFS boot ---
ip=192.168.5.1:192.168.5.10::255.255.255.0::eth0
root=/dev/nfs
nfsroot=192.168.5.10:/srv/{your_rootfs_dir}

Save changes, plug MicroSD card and power up your IGEP.

Flash boot

Boot IGEP with a MicroSD card without NFS support.

mkdir /tmp/temp
mount -t jffs2 /dev/mtdblock1 /tmp/temp 

Now, mtdblock1 partition is mounted at /tmp/temp directory. Modify igep.ini located in: /tmp/temp/igep.ini

• Comment JFFS2 FS boot:

;  --- Configure JFFS2 FS boot ---
;root=/dev/mtdblock2
;rootfstype=jffs2

• Add NFS configuration:

;  --- Configure NFS boot ---
ip=192.168.5.1:192.168.5.10::255.255.255.0::eth0
root=/dev/nfs
nfsroot=192.168.5.10:/srv/{your_rootfs_dir}

Save changes, power down IGEP, unplug MicroSD card and power up your board.

Install and configure codeblocks for IGEP devices (under construction)

Overview

Code::Blocks is a free and open source, cross-platform IDE which supports multiple compilers including GCC and MSVC. It is developed in C++ using wxWidgets as the GUI toolkit. Using a plugin architecture, its capabilities and features are defined by the provided plugins. Currently, Code::Blocks is oriented towards C and C++. It can also be used for creating ARM, AVR, D, DirectX, FLTK, Fortran, GLFW, GLUT, GTK+, Irrlicht, Lightfeather, MATLAB, OGRE, OpenGL, Qt, SDL, SFML, STL, SmartWin and wx programs and applications, although in some cases installing third-party SDKs or frameworks is necessary. More information here.

Code::Blocks is not installed by default in IGEP SDK VM, because Eclipse IDE is full integrated with IGEP Firmware. If you don't like Eclipse IDE or you want to use Code::blocks anyway this How-to can be helpful to install and set up it.

Requirements

There are some requisites to follow this guide:

• IGEP SDK VM: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 2.3 "Setting up and running the VM")
  
• IGEP Firmware: follow the IGEP SDK SOFTWARE USER MANUAL (chapter 6.1 "Create IGEP firmware bootable micro-sd card")
  
• IGEP Board
• MicroSD Card (optional)
  

"Link software "

Install Code::Blocks in VM

sudo apt-get install codeblocks codeblocks-contrib 

Configure Code::Blocks

Startup script

cd Desktop/IGEP\ development/
gedit Codeblocks.sh

Copy this code to Codeblocks.sh

#! /bin/bash
source /opt/poky/1.2/environment-setup-armv7a-vfp-neon-poky-linux-gnueabi 
exec codeblocks 

Give execute privileges to script:

chmod a+x ~/Desktop/IGEP\ development/Codeblocks.sh 

Codeblocks now will use IGEP SDK environtment variables every time you run this script.

Add IGEP SDK Compiler and Debugger

Follow the next instructions:

^{Click to enlarge image}

Using Code::Blocks

s

Build programs

s

Run programs

d

Debug programs

g