===== Starterkit Quicksteps =====

The SBC @sbc_name@ consisting of the @mod_name@ module and @mb_name@ mainboard is intended as evaluation platform for the @mod_name@. To bring up the board a comprehensive set of accessories is supplied with the kit. The @sbc_name@ is delivered preconfigured to boot the latest released Linux BSP revision at the time of delivery, so only the Host Computer has to be set up properly to bring the @sbc_name@ up. This page guides through the first steps with the @sbc_name@.  
\\
\\  
===== Setup Host Computer =====
==== Serial Driver ====

{{section>@lang@:@mod_arch@:@mod_name@:@mb_name@:data#debug_connection&noheader}}
{{section>@lang@:templates:drivers:serial#@usb_to_serial_chip@&noheader}}



==== Terminal Emulator  ====
<accordion collapsed="true">
<panel title="Linux">
=== Minicom ===
Minicom is a command line based serial terminal for serial communication with hardware like our starterkits.\\
\\
== Install Minicom using APT(Debian/Ubuntu) ==
<code>
$ sudo apt install minicom
</code>
In order for the terminal to work properly with full rights you need to add your user to the dialout group:
<code>
$ sudo usermod -a -G dialout $USER
</code>
\\
== Connect Starterkit to Host ==
To determine the serial device name under linux you can use //dmesg//. Just run the command below and then plug in the starter kit to see the new detected interface names:
<code>
$ dmesg -w
</code>
once the interface name is clear you can abort //dmesg// with **ctrl** + **c**.\\
Now you can start minicom via the command line interface:
<code>
$ minicom -D /dev/ttySx
</code>
<callout type="warning" icon="true">
Make sure to replace ///dev/ttySx// with the serial interface you found out before with dmesg.
</callout>
== Configure minicom ==
The serial configuration should be correct by default. However, //hardware flow control// must be disabled for some starter kits, otherwise the communication works only in one direction.
  - Press **CTRL** + **A**, then press **O** to open the configuration menu
  - Go to Serial port setup
  - Press **F** to change //Hardware Flow Control// to //No//
  - Hit Return key
  - Select //Save setup as dfl// to save this configuration as default
  - Press **ESC** to exit the menu

Now you should be able to communicate with the starter kit\\
{{:en:templates:quicksteps_setup_minicom.gif  }}
</panel>

<panel title="Windows">
=== TeraTerm ===
TeraTerm is an open source terminal emulator for windows. it can be downloaded [[https://osdn.net/projects/ttssh2/releases/|here]].
\\
\\
== Configure TeraTerm ==
  - Download and install TeraTerm
  - Start TeraTerm and open the Serial Port Settings
  - select your serial port and configure it with the values defined in the chapter //Serial Configuration//
  - after passing the values click on the button //new Setting//
Now TeraTerm should be ready for use with our starter kits.
\\
\\
{{:en:templates:quicksteps_setup_teraterm.gif  }}


</panel>
</accordion>

==== Host PC Serial Port Configuration ====
The serial port which connects the @stk_name@ to the Host PC must be configured as follows:
<grid>
<col sm="4">
<panel no-body="true">
^  Bautrate: |  115200  |
^  Data bits: |  8  |
^  Parity: |  none  |
^  Stop bits: |  1  |
^  Handshake  : |  XON/XOFF  |
</panel>
</col>
</grid>

===== Connecting the Starterkit to the Development Host =====

Please follow the quick start guide delivered with the kit, or open it from the following link: {{@lang@:@mod_arch@:@qsg_name@.@qsg_revision@.pdf|Quick start guide}} \\  
\\  
\\
  
===== Linux =====

==== BSP Login Credentials ====

As soon as logging in on the Linux shell for the first time, the question about the login credential comes up.\\ 
By default the user **root** is used to log into the Linux shell, no password is set for  user **root**.
<grid>
<col sm="4">
<code>
tqmaxx-mbaxx login: root
</code>
</col>
</grid>

==== Testing Interfaces on @stk_name@ ==== 

To get familiar with the interfaces of the @stk_name@ we recommend to work through the [[en:@mod_arch@:@mod_name@:@mb_name@:linux:@build_system@:how_to:target|interface tutorials]] first.


===== Building the BSP =====

The Board Support Packages provided by TQ may not contain all software packages to evaluate the @stk_name@, therefore TQ provides some guides how to build the BSP and customize it for your needs,   

  * [[@lang@:@mod_arch@:@mod_name@:@mb_name@:@bsp_name@:@build_system@:quickstart_yocto|Build the BSP for @stk_name@]]
  * [[@lang@:@mod_arch@:@mod_name@:@bsp_name@:@build_system@:how_to:yocto_build_system|How To customize @stk_name@ Yocto BSP]]

In addition to the BSP documentation, the Yocto SDK build and Eclipse IDE setup for the @stk_name@ is also documented. 

  * [[@lang@:@mod_arch@:@mod_name@:<label mb-name>:@bsp_name@:@build_system@:how_to:development_host:yocto_sdk|Build the SDK for @stk_name@]]
  * [[@lang@:@mod_arch@:@mod_name@:@bsp_name@:@build_system@:how_to:development_host:eclipse|Setup Eclipse IDE for @stk_name@ on Development Host]]


===== Setup Starterkit for different boot sources =====

The @stk_name@ can be setup to boot from different sources please see the DIP switch settings below to change the boot source.

{{section>@lang@:@mod_arch@:@mod_name@:@mb_name@:dip_switches#boot_devices&noheader}}