===== Tutorial =====

===== Connect Host PC and STKa6x =====
\\
{{:en:arm:tqma6x:a.jpg?nolink&50 |}}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 [[http://ttssh2.sourceforge.jp/index.html.en|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 =====
\\
{{:en:arm:tqma6x:b.jpg?nolink&50 |}}Double-check the mains voltage required for the included power supply,
then connect it to connector X4 on the STKa6x.
\\
\\
\\
<WRAP round important 70%>
Caution when using a different power supply!
The Starterkit requires a regulated supply voltage of 24 V!
</WRAP>


===== Establish Serial Connection =====

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

{{ :en:arm:tqma6x:starterkit_quick_tqma6x.jpg?nolink&600 |}}


===== Download BSP Sources and PTXdist =====

<WRAP round important 50%>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.</WRAP>

{{page>en:arm:tqma6x:linux:version-matrix}}
\\
<WRAP round info 40%>
++++ Downloads TQMa6x |
{{page>en:arm:tqma6x:linux:downloads&inline}}
++++
</WRAP>



===== Setup PTXdist  =====

<WRAP round important 60%>
To install PTXdist you need Linux on your development workstation (or a virtual machine running Linux).
</WRAP>


==== Extracting PTXdist Sources ====

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

<code bash>
$ cd
$ mkdir local
$ cd local
</code>

Next step is to extract the archive:

<code bash>
$ tar -xjf ptxdist-xxx.tar.bz2
</code>

Change to PTXdist directory:

<code bash>
cd ptxdist-xxx
</code>

==== Prerequisites for PTXdist ====

The PTXdist installation is based on GNU autotools, so the first thing to be done now is to configure the packet:
<code bash>
$ ./configure
</code>

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:

<code bash>
$ make
</code>

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:
<code bash>
$ sudo make install
[enter password]
[...]
</code>

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

<code bash>
$ cd ../../
rm -fr local
</code>

==== Configuring PTXdist ====

For PTXdist configuration run:

<code bash>
$ ptxdist setup
</code>

 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 …

<WRAP round tip 60%>
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. 
</WRAP>

==== Building OSELAS Toolchain ====

<WRAP round important 60%>
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\\
</WRAP>

==== Download toolchain sources ==== 



==== Unpacking sources and compiling toolchain ==== 
<code bash>
$ 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
</code>
<WRAP center round tip 60%>
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
</WRAP>