{{template>en:templates:tabs_yocto_bootstrap|product_type="Embedded module"|lang="en"|mod_name="tqmls1028a"|mod_name_head="TQMLS1028A"|mod_arch="layerscape"|bsp_name="linux"|build_system="yocto"|build_system_head="YOCTO"|bsp_name_head="Linux"}}



===== Starterkit Interfaces and Functions =====

<panel type="default" title="Buttons">
There are two GPIO buttons on the MBL1028A. They are bound to the gpio-keys driver, and can be tested with the evtest tool.
<grid>
<col sm="6">
<panel type="primary" title="GPIO Button Overview">
^  Reference  ^  Button  ^ 
| S4 | Button 0 |
| S5 | Button 1 |
</panel>
</col>
<col sm="6">
<panel type="primary" title="GPIO Button Location">
{{ :en:layerscape:tqmls1028a:linux:yocto:tqmls1028a_gpio-button.png?nolink&400 | }}
</panel>
</col>
</grid>

The buttons are available in the sysfs via the device /dev/input/event0 and can be tested with the evtest tool.
<code>
evtest /dev/input/event0
</code>
</panel>



{{template>en:templates:howto:can|can_description="The STKLS1028A provides the CAN Interfaces can0 and can1."|dipdescription="DIP switch S1 is used to configure the CAN interfaces CAN0 and CAN1."|dip1="S1-1"|dip2="S1-2"|can_image="{{ :en:layerscape:tqmls1028a:linux:yocto:tqmls1028a_can_loopback.png?nolink&400 \|}}


<panel type="default" title="Ethernet">
The STKLS1028A provides one 4 Port TSN Gbit Ethernet Switch and two 10/100/1000 Ethernet Interfaces.
=== Configure the ethernet switch in bridge mode ===

The TSN switch of the STKLS1028A is not configured by default. The master interface eno2 is enabled by default, so it is not necessary to bring it up manually.


== Single port configuration ==

Every single switch port acts as a configurable Ethernet port
<code bash>

# Configure each single switch interface and bring it up.

$ ip addr add 192.168.1.2 dev swp0 && ip link set swp0 up
$ ip addr add 192.168.1.3 dev swp1 && ip link set swp1 up
$ ip addr add 192.168.1.4 dev swp2 && ip link set swp2 up
$ ip addr add 192.168.1.5 dev swp3 && ip link set swp3 up
</code>

== Bridge configuration ==

Every switch port is part of one configurable Ethernet bridge.
<code bash>
# Create a bridge device in this example it is called switch

$ ip link add name switch type bridge

# Bring up the bridge device 

$ ip link set switch up

# Add the interfaces to the bridge device switch and bring them up.

$ ip link set swp0 master switch && ip link set swp0 up
$ ip link set swp1 master switch && ip link set swp1 up
$ ip link set swp2 master switch && ip link set swp2 up
$ ip link set swp3 master switch && ip link set swp3 up

# Configure bridge device

$ ip addr add 192.168.1.2 dev switch 
</code>
<accordion collapsed="true">
<panel title="U-Boot">

In U-Boot enetc-1 is configured as default interface. The IP configuration can be done statically or by a DHCP server in the network.

** IP configuration via DHCP **

For a configuration via a DHCP server, use the ''dhcp'' command in U-Boot.

** Static IP configuration **
For a static IP configuration the following, U-Boot environment variables must be set:
<code>setenv ipaddr <ipaddr> 
(e.g.: setenv ipaddr 192.168.100.111)
setenv netmask <netmask> 
(e.g.: setenv netmask 255.255.255.0)
</code>

</panel>
<panel title="Linux">
Both Ethernet Interfaces, eno0 and eno1, are activated in Linux. 

For a temporary static configuration the ip command can be used, below some useful ip commands are listed:\\ 
\\
**Activate a specific interface**\\
e.g. eno1
<code>
ip link set eno1 up
</code>
\\
**Disable a specific interace**\\
e.g. eno1
<code>
ip link set eno1 down
</code>
\\
**Show ip address for a specific interface**\\
e.g. eno1
<code>
ip addr show eno1
</code>
\\
**Show statistic for a specific interface**\\
e.g. eno1

<code> 
ip -s link show eno1
</code>
\\
**Set ip address for a specific interface**\\
e.g. eno1

<code>
ip addr add 192.168.1.100/24 dev eno1
</code>
\\
**Show statistic of all interfaces**\\

<code>
ip -s link
</code>
\\
**Set default gateway for a specific interfaces**\\
e.g. set gateway ip 192.168.1.1 for eno1
<code>
ip route add default via 192.168.1.1 dev eno1
</code>
----

If a DHCP server is available in the network environment the ip configuration can be received from it. To do so execute the ''udhcpc'' command, by default eth0 is used.\\
To configure another interface via dhcp the parameter ''-i''  followed by the interface name e.g. eno1 must be given.\\
e.g. eno1

<code>
udhcpc -i eno1
</code>

</panel>
</accordion>
</panel>

{{template>en:templates:howto:i2c|mod_name="tqmls1028a"|mod_arch="layerscape"|ubooti2c="[0,2]"|linuxi2c="[0,2]"}}

{{template>en:templates:howto:rtc|}}
<hidden>
{{template>en:templates:howto:temperature|}}
</hidden>
{{template>en:templates:howto:usb|}}

<panel type="default" title="User LED">

The MBLS1028A has two user controllable LEDs, the behavior of these LEDs can be selected by several triggers.

<div>
<panel type="primary" title="User LED Location" no-body="true">
{{ :en:layerscape:tqmls1028a:linux:yocto:mbls1028a_user_led.png?nolink&400 |}}
</panel>
</div>

The user LED's are located in /sys/devices/platform/gpio-leds/leds/.\\
To change the behaviour a specific LED, the value in the file trigger must be overwritten.

++++The following values are valid:|

  * none 
  * bluetooth-power 
  * kbd-scrolllock 
  * kbd-numlock 
  * kbd-capslock 
  * kbd-kanalock 
  * kbd-shiftlock 
  * kbd-altgrlock   
  * kbd-altlock
  * kbd-shiftllock
  * kbd-shiftrlock
  * kbd-ctrllock
  * kbd-ctrlllock
  * kbd-ctrlrlock
  * mmc0
  * disk-activity
  * disk-read
  * disk-write
  * ide-disk
  * heartbeat
  * cpu
  * cpu0
  * cpu1
  * cpu2
  * cpu3
  * default-on
  * panic
  * mmc1

++++

For example set the trigger of led1 to heartbeat 

<code>
echo heartbeat > /sys/class/leds/led1/trigger
</code>

</panel>