Ublox EVK-W16 User manual

EVK-W16
Evaluation kit for ELIN-W160 and
ODIN-W160 modules
User Guide
Abstract
This document describes how to set up the EVK-W16 evaluation kit
to evaluate u-blox ELIN-W160 and ODIN-W160 multiradio modules.
It also provides an overview of the ELIN-W160 module, the build
environment, how to download the firmware for ELIN-W160 and
brief information on how to modify and add new functionality to
Yocto build environment.
www.u-blox.com
UBX-15017061 - R02

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Contents
Page 2 of 38
Document Information
Title
EVK-W16
Subtitle
Evaluation kit for ELIN-W160 and
ODIN-W160 modules
Document type
User Guide
Document number
UBX-15017061
Revision, date
R02
1-Mar-2016
Document status
Advance Information
Document status information
Objective Specification
Document contains target values. Revised and supplementary data will be published later.
Advance Information
Document contains data based on early testing. Revised and supplementary data will be published later.
Early Production Information
Document contains data from product verification. Revised and supplementary data may be published later.
Production Information
Document contains the final product specification.
This document applies to the following products:
Product name
Type number
Firmware version
PCN / IN
ELIN-W160
ELIN-W160-00B-00
2.0.0.0
N/A
u-blox reserves all rights to this document and the information contained herein. Products, names, logos and designs described herein may in
whole or in part be subject to intellectual property rights. Reproduction, use, modification or disclosure to third parties of this document or
any part thereof without the express permission of u-blox is strictly prohibited.
The information contained herein is provided “as is” and u-blox assumes no liability for the use of the information. No warranty, either
express or implied, is given, including but not limited, with respect to the accuracy, correctness, reliability and fitness for a particular purpose
of the information. This document may be revised by u-blox at any time. For most recent documents, please visit www.u-blox.com.
Copyright © 2016, u-blox AG.
u-blox®is a registered trademark of u-blox Holding AG in the EU and other countries.

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Contents
Page 3 of 38
Contents
Contents..............................................................................................................................3
1Introduction..................................................................................................................5
1.1 Overview .............................................................................................................................................. 5
1.2 Development board .............................................................................................................................. 5
1.2.1 System requirements......................................................................................................................... 7
2Getting started .............................................................................................................8
2.1 Jumper configuration............................................................................................................................ 8
2.2 GPIO LED overview ............................................................................................................................... 9
2.3 UART Terminal.................................................................................................................................... 10
2.4 Ethernet over USB............................................................................................................................... 11
2.5 Working with Wi-Fi............................................................................................................................. 11
2.6 Bluetooth ........................................................................................................................................... 13
2.7 Ethernet ............................................................................................................................................. 15
2.8 Benchmark ......................................................................................................................................... 16
3Yocto environment setup ..........................................................................................17
3.1 Install environment ............................................................................................................................. 17
3.1.1 Build default distribution................................................................................................................. 20
3.2 Download firmware to target ............................................................................................................. 22
4Factory restore ...........................................................................................................23
4.1 USB Device firmware upgrade ............................................................................................................ 23
5Build and install package...........................................................................................25
5.1 Package server.................................................................................................................................... 25
5.2 Sample Python package...................................................................................................................... 26
6Overview of Yocto meta layers.................................................................................28
6.1 Developer layer................................................................................................................................... 28
6.2 Application layer................................................................................................................................. 28
6.3 u-blox layers ....................................................................................................................................... 28
6.3.1 meta-ublox Layer ............................................................................................................................ 29
6.3.2 meta-ublox-extras Layer .................................................................................................................. 30
6.3.3 Yocto, OpenEmbedded, and TI layers.............................................................................................. 31
6.4 Working with the meta layers............................................................................................................. 31
6.4.1 Creating a new meta layer .............................................................................................................. 31
6.4.2 Overriding or modifying a meta layer or an image........................................................................... 33
Appendix ..........................................................................................................................35
AGlossary ......................................................................................................................35
BPolicies and configuration .........................................................................................36

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Contents
Page 4 of 38
Related documents and links ..........................................................................................37
Revision history................................................................................................................37
Contact..............................................................................................................................38

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Introduction
Page 5 of 38
1Introduction
This document describes how to set up the u-blox EVK-W16 evaluation kit to perform some basic operations
with Wi-Fi, Bluetooth and the terminal. The EVK-W16 also serves as reference platform for the ODIN-W160
module and this guide also demonstrates the capabilities of the ODIN-W160 multiradio module. The setup
process takes around 10 minutes. This guide also provides information on how to build and customize the
firmware. You can build and customize the firmware in 1-2 hours, depending on the build system and speed of
the internet connection.
1.1 Overview
The ELIN-W160 is a system-on-module that uses an AM3352, 512 MB NAND, 256 MB RAM with a dual-band
802.11a/b/g/n Wi-Fi and Bluetooth 4.0 radio for OEMs. The ELIN-W160 module has the following three main
connectors:
Primary host connector
Secondary host connector
A U.FL. connector for connecting to an external antenna
Two LEDs indicate the power and the activity of the CPU as shown in Figure 1.
Figure 1: ELIN-W16 Connector LED overview
1.2 Development board
The ELIN-W160 requires a carrier board to provide power and connectors for the user interfaces, as needed for
operation. The EVK-W16 evaluation kit and its main parts are shown in Figure 2. The development board
provides convenient connectors for the ELIN-W160 for all default interfaces, as shown in Figure 3.
Socket for ELIN-W160
Dual 100 Mbit Ethernet PHY and RJ45 connectors
USB 2.0 OTG
oHost, Micro-AB
oDevice, Type-A
Console UART (UART0) via
oFTDI chip
oFull modem connector
UART1 with CTS/RTS signals

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Introduction
Page 6 of 38
oDSUB9
Signal pin headers
oAccess to almost all CPU signals
JTAG for ELIN-W160 CPU
Three GPIO buttons
Four user customizable LEDs
Antenna connector
Power switch
Figure 2: Overview of EVK-W16 evaluation kit

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Introduction
Page 7 of 38
Figure 3: Overview of EVK-W16 connectors
1.2.1 System requirements
The minimum system requirements are provided below:
EVK-W16 evaluation kit
oELIN-W160 module
oEVB-W16 evaluation board
o9-12 V power adapter 1A
oUSB A - B mini cable
oUSB A - B micro cable
oAntenna
ou.fl. to RPSMA antenna cable
PC with Linux or Windows
oMinimum recommended configuration: 2 core, 60 GB disk space and 4 GB RAM
oLinux build host is recommended for building the firmware. The build times can be long if done
through a virtual Linux system.

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 8 of 38
2Getting started
The setup process described in this section allows you to quickly get up and running with your development
board using Ethernet over USB and a console through FTDI chip UART:
Ensure that the development board is not connected to a power source.
2.1 Jumper configuration
1. Set the jumper on JP4 between pin 1 and 5. This selects 5V0 regulated as the power source for
ELIN-W1.
2. Set the jumper on JP6 between pin 1 and 2. This disables the UART0 DSUB transceiver, which could
cause interference with the FTDI chip.
3. Set three jumpers between pins on JP7 and JP8 between pairs of pins: JP7.19 - JP8.20, JP7.15 - JP8.16,
and JP7.9 - JP8.10. This enables the UART1 transceiver on the DSUB J24 and connects RXD and TXD to
the DSUB connector.
4. Set the jumper on JP12 between pin 1 and 2. This sets 3.3 V to the Ethernet PHYs.
Figure 4: EVK-W16 jumper configuration
5. Connect a regulated power supply to the J16.

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 9 of 38
2.2 GPIO LED overview
6. Turn on the power supply and turn on the power switch (SW8). The LED LD17 lights up to indicate
power to the board while the LED LD20 lights up to indicate power to the ELIN-W160 module.
7. Connect a USB cable to the FTDI chip. The LED LD18 will indicate USB Voltage.
Figure 5: EVK-W16 GPIO LED overview
8. Press PWR TGL (SW11) to start the OEM Module. Your OS should detect the FTDI chip and provide 4
UARTs. Connect to the console.
The FTDI chip has four channels and the console is on the third.
a. 115200 8N1
b. No hardware handshake
// On HOST PC
9. You can see that the module boots first the u-boot and then boots the kernel into user space.
10. You can now login as root and no password is required by default.
$ minicom -b 115200 -D /dev/ttyUSB2

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 10 of 38
2.3 UART Terminal
The UART0 serves as a terminal at 115200 8N1 and is accessible through the FTDI chip (port C) on J26 or RS232
on J22. If you use the FTDI chip, ensure that the JP6 jumper is in place. Remove J22 if you use RS232.
U-Boot SPL 2013.10 (Jun 10 2015 - 12:02:59)
U-Boot 2013.10 (Jun 10 2015 - 12:02:59)
I2C: ready
DRAM: 256 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Net: cpsw:3 is connected to cpsw. Reconnecting to cpsw
cpsw
Hit any key to stop autoboot: 1 ^H^H^H 0·
Booting from nand ...
NAND read: device 0 offset 0x200000, size 0x500000
5242880 bytes read: OK
NAND read: device 0 offset 0x1c0000, size 0x40000
262144 bytes read: OK
Kernel image @ 0x80008000 [ 0x000000 - 0x4104a8 ]
## Flattened Device Tree blob at 80f80000
Booting using the fdt blob at 0x80f80000
Using Device Tree in place at 80f80000, end 80f8b3fd
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.19.8 (msen@de-bln-lt-msen) (gcc version 4.9.2 (GCC) ) #1 Tue
Oct 20 12:14:28 CEST 2015
...
...
Starting rpcbind daemon...done.
Starting UART HCI interface: hciattach
Starting Bluetooth daemon: bluetoothd
starting Busybox UDHCP Server: udhcpd... done.
Starting syslogd/klogd: done
* Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon
...done.
Starting Hiawatha Web Server: hiawatha.
Poky (Yocto Project Reference Distro) 1.8.1 elin-w160-evk /dev/ttyO0
elin-w160-evk login:

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 11 of 38
2.4 Ethernet over USB
Connect the EVK-W16 to the PC using a USB cable (Type-A to Micro-AB) inserted into USB0 port. On Linux, you
should be able to find the USB device on your PC using the following commands:
// On HOST PC
The ELIN-W160 has a DHCP server, which provides an IP address for your PC. If required, you can request a new
IP address from the ELIN-W160 using the following command:
You should now be able to ping your target
If you use Windows, you must change the USB gadget driver to RNDIS and install the RNDIS driver on Windows
for Ethernet-Over-USB to work properly. Currently, there is no driver in Windows OS for USB NCM. For USB
RNDIS, use the linux.inf driver.
1. Open the Device Manager in Windows to install the driver.
2. Under Other devices, select the RNDIS device, right click and choose Update Driver Software.
3. In the Update Driver Software window, select Browse my computer for driver software.
4. On the next screen, where it prompts you to browse for driver software on your computer, select Let
me pick from a list of device drivers option and click Next.
5. In the next screen, click Have Disk button and select the driver you have already downloaded
(linux.inf).
6. Accept any warnings and the device should be installed.
2.5 Working with Wi-Fi
Connecting to a Wi-Fi is easy using wpa_cli. This also allows you to save your configuration after setting up the
network. You can also modify /etc/wpa_supplicant.conf directly if you are familiar with wpa_supplicant. Refer to
http://w1.fi/wpa_supplicant/ for more information regarding wpa_supplicant.
The wpa_supplicant must be started before using wpa_cli.
Steps
Instructions
Ensure that your Wi-Fi interface is
up.
# ifconfig wlan0 up
Start wpa_supplicant command
line interface.
# wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
# wpa_cli
wpa_cli v2.0
Copyright (c) 2004-2012, Jouni Malinen <[email protected]> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
$ ping 192.168.7.1
$ dhclient -i usb0
$ ifconfig usb0
usb0 Link encap:Ethernet HWaddr 02:25:f5:19:00:89
inet addr:192.168.7.8 Bcast:192.168.7.255 Mask:255.255.255.0
inet6 addr: fe80::25:f5ff:fe19:89/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6019 (5.8 KiB) TX bytes:428814 (418.7 KiB)

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 12 of 38
Steps
Instructions
Selected interface 'wlan0'
Interactive mode
Verify whether the wlan0
interface is up.
> status
wpa_state=DISCONNECTED
address=de:ad:be:ef:00:00
Perform a scan to see the
available networks.
> scan
OK
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
> scan_results
bssid / frequency / signal level / flags / ssid
00:11:22:33:44:55 2437 -77 [WPA-PSK-CCMP][WPA2-PSK-CCMP][WPS][ESS]TEST-AP
11:22:33:44:55:66 2447 -41 [WPS][ESS] TEST-AP2
22:33:44:55:66:77 2427 -36 [WPA2-EAP-CCMP-preauth][ESS] TEST-AP3
Associate with the network and
save the configuration.
> add_network
0
> set_network 0 ssid "TEST-AP"
OK
> set_network 0 psk "1234567"
OK
> enable_network 0
OK
<3>CTRL-EVENT-SCAN-RESULTS
<3>WPS-AP-AVAILABLE
<3>Trying to associate with 00:11:22:33:44:55 (SSID='TEST-AP' freq=2437
MHz)
<3>Associated with 00:11:22:33:44:55
<3>WPA: Key negotiation completed with 00:11:22:33:44:55 [PTK=CCMP
GTK=CCMP]
<3>CTRL-EVENT-CONNECTED - Connection to 00:11:22:33:44:55 completed [id=0
id_str=]
> save_config
OK
> quit
#
Check whether your
wpa_configuration is updated.
# cat /etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
update_config=1
network={
ssid="TEST-AP"
psk="1234567"
}
Once associated with the access
point, you can get an IP address.
You can obtain the IP address
either by using the network
configurations preset in the ELIN-
W16 or by using udhcpc DHCP
client.
# ifup wlan0
udhcpc (v1.21.1) started
Sending discover...
Sending select for 192.168.0.89...
Lease of 192.168.0.89 obtained, lease time 43200
/etc/udhcpc.d/50default: Adding DNS 192.168.0.1
#

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 13 of 38
Steps
Instructions
or
# udhcpc -i wlan0
udhcpc (v1.21.1) started
Sending discover...
Sending discover...
Sending discover...
Sending select for 192.168.0.89...
Lease of 192.168.0.89 obtained, lease time 43200
/etc/udhcpc.d/50default: Adding DNS 192.168.0.1
#
You can now ping the router to
verify the connection.
# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: seq=0 ttl=64 time=3.253 ms
64 bytes from 192.168.0.1: seq=1 ttl=64 time=2.856 ms
64 bytes from 192.168.0.1: seq=2 ttl=64 time=3.716 ms
Table 1: Steps to connect to Wi-Fi
2.6 Bluetooth
Bluetooth is handled through Bluez, a user space protocol/layer stack for Bluetooth. Use the steps mentioned in
Table 2 to scan and connect to different devices.
Steps
Instructions
Verify whether the Bluetooth interface is
started. The Bluetooth interface is started
automatically during boot.
# hcitool dev
Devices:
hci0 78:C5:E5:30:83:45
You can scan for Bluetooth devices.
# hcitool scan
Scanning ...
1C:BA:8C:7F:58:B3 Bluetooth Device
00:12:F3:1A:CA:89 n/a
00:12:F3:23:43:60 PB COM21
00:12:F3:1A:CA:F7 PB COM36
00:12:F3:17:C4:DE OBS421 echo device
Choose a device and obtain additional
information regarding the device.
# hcitool info 00:12:F3:17:C4:DE
Requesting information ...
BD Address: 00:12:F3:17:C4:DE
Device Name: OBS421 echo device
LMP Version: 4.0 (0x6) LMP Subversion: 0x1b55
Manufacturer: Texas Instruments Inc. (13)
Features page 0: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
<3-slot packets> <5-slot packets> <encryption> <slot
offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <power
control>
<transparent SCO> <EDR ACL 2 Mbps> <EDR ACL 3 Mbps>
<enhanced iscan> <interlaced iscan> <interlaced pscan>
<inquiry with RSSI> <extended SCO> <EV4 packets> <EV5
packets>
<AFH cap. slave> <AFH class. slave> <LE support>
<3-slot EDR ACL> <5-slot EDR ACL> <sniff subrating>
<pause encryption> <AFH cap. master> <AFH class. master>

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 14 of 38
Steps
Instructions
<EDR eSCO 2 Mbps> <EDR eSCO 3 Mbps> <3-slot EDR eSCO>
<extended inquiry> <LE and BR/EDR> <simple pairing>
<encapsulated PDU> <err. data report> <non-flush flag>
<LSTO>
<inquiry TX power> <EPC> <extended features>
Features page 1: 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Use the sdptool to find out the services
supported by the device.
# sdptool records 00:12:F3:17:C4:DE
Service Name: SPP
Service RecHandle: 0x10001
Service Class ID List:
"Serial Port" (0x1101)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Serial Port" (0x1101)
Version: 0x0102
If you have a serial port adapter such as the
OBS421, you can connect the device and
make it a serial port on the ELIN-W1.
Press CTRL-A + x to leave minicom.
Use "rfcomm release 0" to disconnect.
# rfcomm connect 0 00:12:F3:17:C4:DE 1 &
Connected /dev/rfcomm0 to 00:12:F3:17:C4:DE on channel 1
Press CTRL-C for hangup
# minicom -b 115200 -D /dev/rfcomm0
To accept incoming SPP connections, you
need to do the following on the ELIN-W1:
•Turn on both page and inquiry
scan (optional).
•Add a Serial port service.
•Start the RFCOMM listener.
Press CTRL-A + x to leave minicom.
Use "rfcomm release 0" to disconnect the
rfcomm listener.
# hciconfig hci0 piscan
# sdptool add SP
Serial Port service registered
# rfcomm listen /dev/rfcomm0 1 &
Waiting for connection on channel 1
Connection from 00:12:F3:17:C4:DE to /dev/rfcomm0
Press CTRL-C for hangup
# minicom -b 115200 -D /dev/rfcomm0
Table 2: Steps to connect to Bluetooth

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 15 of 38
2.7 Ethernet
Ethernet on the ELIN-W160 is set to obtain an IP address through DHCP automatically. To see the interfaces, use
ifconfig:
To bring up the interfaces, use ifup.This command uses the configuration in /etc/network/interfaces to
configure your Ethernet interface:
# ifup eth0
udhcpc (v1.21.1) started
Sending discover...
Sending discover...
# ifconfig -a
eth0 Link encap:Ethernet HWaddr 20:CD:39:FC:1F:42
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:56
eth1 Link encap:Ethernet HWaddr 20:CD:39:FC:1F:44
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Getting started
Page 16 of 38
2.8 Benchmark
Use iperf to test the throughput of the network connection. Install iperf on your PC if not installed previously
and start iperf as a server.
// On HOST PC
The iperf is pre-installed on the ELIN-W160 module. Start testing using UDP and 100 MBit throughput test.
Replace the IP address with the address you obtained during DHCP configuration.
// On Target
root@elin-w160-evk:~# iperf -c 192.168.1.1 -u -i 1 -b 100M
------------------------------------------------------------
Client connecting to 192.168.1.1, UDP port 5001
Sending 1470 byte datagrams
UDP buffer size: 160 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.1.146 port 40375 connected with 192.168.1.1 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0- 1.0 sec 11.5 MBytes 96.5 Mbits/sec
[ 3] 1.0- 2.0 sec 11.4 MBytes 95.7 Mbits/sec
[3] 2.0- 3.0 sec 11.4 MBytes 95.5 Mbits/sec
[ 3] 3.0- 4.0 sec 11.4 MBytes 96.0 Mbits/sec
[ 3] 4.0- 5.0 sec 11.4 MBytes 95.6 Mbits/sec
[ 3] 5.0- 6.0 sec 11.4 MBytes 95.5 Mbits/sec
[ 3] 6.0- 7.0 sec 11.4 MBytes 96.0 Mbits/sec
[ 3] 7.0- 8.0 sec 11.4 MBytes 95.6 Mbits/sec
[ 3] 8.0- 9.0 sec 11.4 MBytes 95.6 Mbits/sec
[ 3] 9.0-10.0 sec 11.4 MBytes 95.8 Mbits/sec
[ 3] 0.0-10.0 sec 114 MBytes 95.7 Mbits/sec
[ 3] Sent 81436 datagrams
[ 3] Server Report:
[ 3] 0.0-10.0 sec 114 MBytes 95.7 Mbits/sec 0.306 ms 0/81435 (0%)
[ 3] 0.0-10.0 sec 1 datagrams received out-of-order
$ sudo apt-get install iperf
$ iperf -s -u

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Yocto environment setup
Page 17 of 38
3Yocto environment setup
This section provides information on how to set up the yocto build environment and make the default factory
image download to the target. For more information, refer to Yocto Quick Start Guide [4], which provides
detailed information about the Yocto build system.
3.1 Install environment
Ensure that you have a PC with Linux installed. This guide assumes that you have installed Debian 7.4 and your
user has sudo privileges (if not, issue "sudo usermod -a -G sudo 'username'"). You should not be logged in as
root.
First, install the required packages for the build process:
Clone u-blox tools repository:
$ git clone https://github.com/u-blox/elin-tools
Cloning into 'elin-tools'...
remote: Counting objects: 37, done.
remote: Total 37 (delta 0), reused 0 (delta 0), pack-reused 37
Unpacking objects: 100% (37/37), done.
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential
chrpath libsdl1.2-dev xterm lzop

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Yocto environment setup
Page 18 of 38
For the next step, you should be a github user who has added an ssh key to your account. Refer
to the help section on GitHub [6] for more information on account settings and ssh key setup.
Run the following setup script that will download the required repositories and provide you with initial
configuration files required by Yocto. This will download the poky, openembedded, ti and u-blox meta layers
(roughly 150 MiB). On successful download, you should have a poky folder populated with the required meta
layers.
$ cd elin-tools/scripts
$ ./ublox-poky-setup.sh
Setting up poky
Cloning into 'poky'...
remote: Counting objects: 304080, done.
remote: Compressing objects: 100% (74926/74926), done.
remote: Total 304080 (delta 224033), reused 303244 (delta 223329)
Receiving objects: 100% (304080/304080), 117.71 MiB | 8.86 MiB/s, done.
Resolving deltas: 100% (224033/224033), done.
HEAD is now at b74ea96 build-appliance-image: Update to fido head revision
Setting up meta-openembedded
Cloning into 'meta-openembedded'...
remote: Counting objects: 54719, done.
remote: Compressing objects: 100% (20271/20271), done.
remote: Total 54719 (delta 32712), reused 53451 (delta 31788)
Receiving objects: 100% (54719/54719), 22.84 MiB | 1.78 MiB/s, done.
Resolving deltas: 100% (32712/32712), done.
HEAD is now at df2f700 geoclue: add PACKAGECONFIG for geoip
Setting up meta-ublox
Cloning into 'meta-ublox'...
remote: Counting objects: 148, done.
remote: Total 148 (delta 0), reused 0 (delta 0), pack-reused 148
Receiving objects: 100% (148/148), 26.81 KiB, done.
Resolving deltas: 100% (44/44), done.
HEAD is now at 47dbe3a elin-eeprom-reader: fix S and QA Issue warnings
Setting up meta-ublox-extras
Cloning into 'meta-ublox-extras'...
remote: Counting objects: 260, done.
remote: Total 260 (delta 0), reused 0 (delta 0), pack-reused 260
Receiving objects: 100% (260/260), 40.71 KiB, done.
Resolving deltas: 100% (100/100), done.
HEAD is now at 52e11eb elin-w1-webdocumentation: update operated temperature and include type
approvals for Japan

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Yocto environment setup
Page 19 of 38
Source the ublox environment script to initiate the Yocto build environment:
Now, Yocto would have generated a build folder, relocated your shell to the build folder and populated it with a
few files.
The following two files are used to configure your local build settings:
bblayers.conf is used to locate the build recipes used by bitbake during build time
local.conf is used to define local settings, target architecture, machine configuration, and many other
settings.
In the bblayers.conf file, you can see the paths for the different meta-layers, which bitbake requires to build the
u-blox distribution. Here, add your own meta-layer if you would like to add any layers of your own.
# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
LCONF_VERSION = "6"
BBPATH = "${TOPDIR}"
BBFILES ?= ""
BBLAYERS ?= " \
/home/ublox/projects/yocto/poky/meta \
/home/ublox/projects/yocto/poky/meta-yocto \
/home/ublox/projects/yocto/poky/meta-ublox \
/home/ublox/projects/yocto/poky/meta-ublox-extras \
/home/ublox/projects/yocto/poky/meta-openembedded/meta-networking \
/home/ublox/projects/yocto/poky/meta-openembedded/meta-oe \
/home/ublox/projects/yocto/poky/meta-openembedded/meta-webserver \
"
BBLAYERS_NON_REMOVABLE ?= " \
/home/ublox/projects/yocto/poky/meta \
/home/ublox/projects/yocto/poky/meta-yocto \
"
/
└── conf
├── bblayers.conf
├── local.conf
└── templateconf.cfg
$ cd poky/
$ source ublox-init-build-env
### Shell environment set up for builds. ###
You can now run 'bitbake <target>'
Common targets are:
core-image-minimal
core-image-ublox-dev
meta-toolchain

EVK-W16 - User Guide
UBX-15017061 - R02 Advance Information Yocto environment setup
Page 20 of 38
The local.conf file contains local settings, such as the machine on which distro can be built. The DL_DIR variable
should match the location where you want to save all your downloaded tarballs and git archives from the build
process. As this information enables you to save bandwidth and time, it is better to go through the different
settings and modify them, if required. The default settings are used in this document.
3.1.1 Build default distribution
You can now start the build and refer to the Yocto Quick Start Guide agreement [4] for additional information.
The build takes approximately 1 to 4 hours depending on the specifications of the compiling machine and the
speed of your internet connection.
...
...
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
DL_DIR := "/home/martin/projects/yocto/downloads"
...
...
# Make use of SMP:
# PARALLEL_MAKE specifies how many concurrent compiler threads are spawned
# per bitbake process
# BB_NUMBER_THREADS specifies how many concurrent bitbake tasks that spawns
PARALLEL_MAKE = "-j 3"
BB_NUMBER_THREADS = "3"
...
...