Tutorial

Connect Host PC and STKa6x


Use the supplied null modem cable to connect COM1 of the STKa6x (X15) to a serial port on your host PC (e.g. COM1 / ttyS0).


Run terminal emulator and configure serial port

Run your favourite terminal emulator on the host PC (we recommend Tera Term Pro) and configure the serial port as follows :

Baudrate Data bits Parity Stop bits Handshake
115200 8 none 1 XON/XOFF

Supply the STKa6x with power


Double-check the mains voltage required for the included power supply, then connect it to connector X4 on the STKa6x.


Caution when using a different power supply! The Starterkit requires a regulated supply voltage of 24 V!

Establish Serial Connection

The boot messages of boot loader and operating system are displayed by the terminal emulator.

Download BSP Sources and PTXdist

We recommend using the correct PTXdist version to build the OSELAS.Toolchain This version may differ from the PTXdist version required to built the BSP itself.


Downloads TQMa6x

Setup PTXdist

To install PTXdist you need Linux on your development workstation (or a virtual machine running Linux).

Extracting PTXdist Sources

To install PTXdist, the archive Pengutronix provides has to be extracted: 

$ cd
$ mkdir local
$ cd local

Next step is to extract the archive: 

$ tar -xjf ptxdist-xxx.tar.bz2

Change to PTXdist directory: 

cd ptxdist-xxx

Prerequisites for PTXdist

The PTXdist installation is based on GNU autotools, so the first thing to be done now is to configure the packet: 

$ ./configure

The build system needs some additional packages which may be normally not installed by default. These packages are (names should match for Debian based systems):

  • gawk
  • dialog
  • ncurses-dev
  • bison
  • flex
  • quilt
  • texinfo
  • gettext
  • g++
  • libxml-parser-perl

When the configure script is finished successfully, we can now run: 

$ make

All program parts are being compiled, and if there are no errors we can now install PTXdist into it’s final location. In order to write to /usr/local, this step has to be performed as user root: 

$ sudo make install
[enter password]
[...]

The installation is now done, so the temporary folder may now be removed: 

$ cd ../../
rm -fr local

Configuring PTXdist

For PTXdist configuration run: 

$ ptxdist setup

You have to setup the following things:

  • ftp / http proxies
  • username and mail address
  • path for archive of downloaded source packages (aka local package pool)
  • for further setup details see PTXdist manual …

Note: you can install more than one PTXdist version in parallel. Then the best way ist to setup an symbolic link to the version needed in your BSP.

Building OSELAS Toolchain

Usually the /opt directory is not world writeable. So in order to build our OSELAS.Toolchain into that directory we need to use a root account to change the permissions. PTXdist detects this case and asks if we want to run sudo to do the job for us. Alternatively we can enter:
mkdir /opt/OSELAS.Toolchain-xxx
chown <username> /opt/OSELAS.Toolchain-xxx
chmod a+rwx /opt/OSELAS.Toolchain-xxx

Download toolchain sources

Unpacking sources and compiling toolchain

$ cd local
$ tar xf OSELAS.Toolchain-xxx.tar.bz2
$ cd OSELAS.Toolchain-2013.12.2
$ ptxdist select ptxconfigs/
arm-v4t-linux-gnueabi_gcc-4.8.2_glibc-2.18_binutils-2.24_kernel-3.12-sanitized.ptxconfig
$ ptxdist go

Now the toolcain is compiling this is taking a about 0,5 - 3 hours the time to compile depends on the hardware of your development host

Disclaimer
TQ-Systems GmbH provides the Board Support Packages (BSP) free of charge. The software included in the shipment has been configured individually for the starter kits. The software is only intended to evaluate the module. The use of the Board Support Packages (BSP) is only allowed within the scope of functionality described by TQ-Systems GmbH. TQ-Systems GmbH does not accept any liability for all further changes of the Board Support Package and for any damage resulting from its use.