Developing for Industrial IoT with Linux OS on DragonBoard™ 410c: Session 1

Qualcomm Developer Network Presents
Developing for Industrial IoT with Embedded Linux OS on
DragonBoard™ 410c by Timesys University
SESSION 1: Introduction to DragonBoard 410 SoC
and Starting Development of Your Embedded Linux
based “Industrial Internet of Things” (IIoT) Device
Co-sponsored by Qualcomm Technologies, Inc. and Arrow Electronics

www.timesys.com ©2017 Timesys Corp.
Session 1
Introduction to DragonBoard 410c and Starting
Development of Your Embedded Linux based
Industrial Internet of Things (IIoT) Device
Maceij Halaz, Vice President of Technology
Timesys Corporation

3 Webinar Series
This is one of a 4-part webinar series Developing for Industrial IoT with Linux OS on DragonBoard™ 410c to explore the process of building an
embedded Linux based device using the Qualcomm® Snapdragon™ 410E powered DragonBoard 410c development board fromArrow
Electronics. With topics that cover build systems, deployment strategy, designing-in and managing security, device appearance and ease of user
interaction, you’ll gain insight into various aspects of technology and design decisions developers face when choosing to build embedded Linux
based products for this increasingly demanding and expanding connected world.All sessions in this Qualcomm Developer Network sponsored
series are designed to provide hands-on experience throughout the entire development process.
 Session 1: Introduction to DragonBoard 410 SoC and Starting Development of Your Embedded Linux
based “Industrial Internet of Things” (IIoT) Device
• Setup for designing IIoT products
• How to assemble and deploy initial BSP
 Session 2: Application Development for Embedded Linux
• Application development environment setup
• How to reflect product requirements in the BSP
• Communication in the IIoT system
 Session 3: Building a Cutting-Edge User Interface with Qt®
• Developing modern, rich UIs for factory terminals
 Session 4: Embedded Products Security
• Designing security-rich devices
Qualcomm Snapdragon is a product of Qualcomm Technologies, Inc.

4 Session 1 — Agenda
 Development Environment
 Deploying Yocto Project®/OpenEmbedded Linux BSP to your DragonBoard
410c
 Design considerations for IIoT products
• Requirements
 Yocto Project/Open Embedded introduction
• Yocto Project – what is it
• How to get and setup Yocto for the 96Boards™
• Re-building BSP image from scratch
 Software Development Kit
CLICK HERE TO VIEW WEBINAR RECORDING

5
Build Environment

6 What we need to build a product
 A host machine
• Linux is the best — any recent version is ok (Timesys® recommends Ubuntu® LTS)
• Windows is fine, but you’ll need a Windows ® 10 native Linux support or a virtual machine
with a Linux desktop OS installation (Timesys recommends Oracle® VirtualBox™)
 Cross-development environment / SDK
 Linux source code (BSP) for the product
• Bootloader
• Linux kernel
• APIs
 Various Linux host utilities needed by Yocto/OpenEmbedded Linux BSP
 IDE for application and system level development. WYSIWYG IDE for faster UI
development
 A hardware development kit

7 Workstation setup
USB
USB/Serial
ETH
eMMC
• Utilities
• Yocto Project-Core
• Metalayer from Qualcomm Technologies, Inc.
• Timesys metalayer
• 3rd party metalayers
• Development Tools
• Support
uSD

8
Initial Board Setup

9 Where to find Yocto/OpenEmbedded Linux BSP binaries for
deployment
 Files representing reference software for the DragonBoard 410c can be
downloaded from the 96Boards website:
http://builds.96boards.org/releases/dragonboard410c/linaro/openembedded/latest/rpb/
 Linux images
• Debian®
• OpenEmbedded (Yocto)
 Yocto images
• Split into deployable components
– Root filesystem
– Bootloader
– Linux kernel

10 Deploying Linux images to the DragonBoard 410c
 DragonBoard 410c supports two methods software of deployment
1. SD card (complete software image/rescue image)
2. USB connector (individual software images)
 Second method is intended for customizations and frequent updates
 Rescue images are provided at
http://builds.96boards.org/releases/dragonboard410c/linaro/rescue/latest/
 Board rescue process:
• Step 1: Download and unzip SD card Install Image
• Step 2: Find SD card device name
• Step 3: Install Rescue Image onto SD card
• Step 4: Boot DragonBoard 410c from an SD card
• Step 6: Flash Yocto/OpenEmbedded Linux BSP images
into EMMC™

11 Image Deployment — SD card (1)
 Helper for the flashing process:
• Step 1: From the URL provided on the previous slide download the rescue image for
the DragonBoard 410c. The image to be downloaded:
dragonboard410c_sdcard_rescue-79.zip
• Uncompress the archive with the command:
• Step 2: Find microSD card device name on your host. Run the following command in a
terminal window:
 Note: Run this command before and after inserting the microSD card into
host PC microSD card reader
• Step 3: Install rescue image onto microSD card. Use the following command to flash
image to microSD card
$ sudo dd if=db410c_sd_rescue.img of=/dev/XXX bs=4M oflag=sync status=noxfer
$ lsblk
$ unzip dragonboard410c_sdcard_rescue-79.zip

• Step 4: Booting DragonBoard 410c with SD card
– Make sure DragonBoard 410c is unplugged from power
– Set S6 switch on DragonBoard 410c to 0-1-0-0, “SD Boot switch” should be set to
“ON”.
– Insert the microSD card into the DragonBoard 410c
– Connect DragonBoard 410c microUSB port to PC’s USB Host with a cable
– Plug power adaptor into DragonBoard 410c, wait 5s for board to boot up.
Note: No onboard LED will light up in this process!
– We have set the DragonBoard in the “fastboot mode”

• Step 5: Flash Yocto/OpenEmbedded Linux BSP images
• In the fastboot mode, DragonBoard can accept images sent from the
Host PC via USB OTG port.
– On the Host PC, check for connected fastboot devices with the command:
– Create partitions on the EMMC and Flash the bootloader. Use flashall script provided
– Boot and filesystem images can be found in:
http://builds.96boards.org/releases/dragonboard410c/linaro/openembedded/latest/rpb/
– Flash the runtime files with the command
– Remove the SD Card
– Set S6 switch on DragonBoard 410c back to 0-0-0-0, all switches set to “OFF”
– Power cycle the DragonBoard 410c to reboot.
$ sudo fastboot devices
$ sudo ./flashall
$ sudo fastboot flash boot boot--4.9-r0-dragonboard-410c-20170803175648-18-18.img
$ sudo fastboot flash rootfs rpb-console-image-dragonboard-410c-20170803175648-
18.rootfs.ext4

14 LAB 1 — Yocto/OpenEmbedded Linux BSP Deployment
 Deploy Yocto Linux BSP images to the DragonBoard 410c using board recovery
method
 Boot the board to verify proper image flashing into eMMC

15
Developing Industrial IoT Devices

16 Industrial IoT has many requirements

17 Why IoT is important in Industrial setting
 Industrial plants
• Operate at capacity
• Operate at efficiency
 Challenges
• Predict undesired process conditions
• Minimize equipment failures
 Industrial IoT provides
• Optimal business performance
• Improved process reliability
– Capturing and analyzing data
– Identify warnings and potential issues
– Preemptive service of equipment

18 Example of an IIoT system
 Data collection end-point
• Sensors
• Local connectivity
• Actuators
• Displays
• Autonomous decision logic
 Data concentrator
• Sensors
• Local connectivity
• Resources for local data processing
• Cloud connection infrastructure
 Analytics
• Integrate multiple production processes
• Can be company wide

19 Why do companies care about IIoT?
 Increase asset utilization
• Reduce unplanned downtime
• Predict failures
• Pro-active response
 Increase operating efficiency
• Reduction in energy usage
• Increased engineering effectiveness by monitoring
• Integrated decision support mechanism
 Increase in Safety
• Minimize risks by ensuring stable operations
• No production interruptions due to safety check
 Reduce maintenance cost
• Optimize maintenance based on real asset conditions
• Pre-emptive addressing of issues

20 IIoT Point requirements
 Requirements are Industry Process
specific
 Topography of IIoT can vary
 Requirements typically include
• Connectivity:
– Bluetooth®
– Ethernet ®
– WiFi™
– BUS
• Sensors:
– Discrete
– Continuous
• Sensor examples
– Temperature
– Pressure
– Movement
– ON/OFF
HUB/Concentrator
Autonomous Decision
Humidity &
Temperature
Accelerometer
& Gyroscope
Luminosity &
Color Detection
Pressure
Sensing
Magnetic
Sensor

21 Software for IIoT device — baseline
Bootloader
Middleware
RFS (rootfs)
shell
Qualcomm
410c
USB
Touch
Screen
HDMI
Linux kernel
IIoT Sensor/Action Node
CameraUser Interface, Buttons, Stream sel, etc
SDIOGPIO
Button
Network control
interface
Auto-launch
Qt Embedded
Driver Driver
networking
Wireless tools
openssh
Driver Driver
Shared
MemoryDriver
sysfs
Splash
Screen
setup
scripts
Ethernet
Driver Driver
Serial
Sensor Control
QT MQTT
Memory
setup
script MQTT
API
1
2
3
Bluetooth
WIFI
Severalimagesusedin
YoctoBSPdeployment

22
Yocto Project

23 Yocto/Open Embedded build process

24 96Boards Yocto structure
96Boards Yocto Project Core
meta-openembedded
recipes-core recipes-bsp recipes-kernel
recipes-multimedia recipes-…
OpenEmbedded Core (openembedded-core)
Execution Engine
scripts Bitbake
meta-qcom meta-qt5 meta-timesys
meta-rpb
meta-96boards
meta-linaro

25 Building and Customizing Linux BSP
 Yocto based desktop tools
 BSP Customizations
• Reflecting IIoT specific device requirements
Download Yocto
Setup for
410c
Rebuild
reference
BSP image
Build SDK
Customize
BSP
96Boards forum Timesys ticket based
Support
Session 1 Session 2

26
1Initial Yocto Project Setup

27 Host Environment
 Depending on the Host System used, make sure that you have installed all
required packages to run Yocto
 Ubuntu/Debian
$ sudo apt-get install gawk wget git-core diffstat unzip texinfo
build-essential chrpath libsdl1.2-dev xterm curl
 CentOS™
$ sudo yum install gawk make wget tar bzip2 gzip python unzip perl
patch diffutils diffstat git cpp gcc gcc-c++ glibc-devel texinfo chrpath
socat SDL-devel xterm
 For other host OS
http://www.yoctoproject.org/docs/current/yocto-project-qs/yocto-project-qs.html

28 Repo tool and GIT™ setup
 Provides a unified command to download software from multiple sources
 Used by Android™ and leveraged by 96Boards
 Install the tool from Google®
$ mkdir ~/bin
$ curl http://commondatastorage.googleapis.com/git-repo-
downloads/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
 GIT setup
$ git config --global user.name "Your Name"
$ git config --global user.email "Your Email"
$ git config --list

29 Getting Yocto
 Yocto for the 96Boards can be assembled from two sources:
1. github.org
2. yoctoproject.org (Toaster option will be discussed in Session 2)
 Getting source code from GitHub™:
$ mkdir 96boards-rpb
$ cd 96boards-rpb
$ repo init -u https://github.com/96boards/oe-rpb-manifest.git -b morty
$ repo sync
 Core Yocto and additional metalayers are installed
• meta-96boards
– Holds definitions for 96Boards
• meta-qcom
– Provides definition for boards including DragonBoards
• meta-timesys

30 meta-timesys
 Provides additional features from Timesys which can be applied to any Yocto
• Helps share information about YOUR current Yocto configuration with Timesys
engineers and support teams
– Facilitates investigative work on YOUR specific questions
• Provides proactive update service
– Find out what are the new updates available from open source that are relevant to the
product
• Provides security feed that is relevant to your board and your BSP/Yocto configuration
– You decide when an update should be applied
– You get an on-demand list of vulnerabilities that affect your product
• Available from GitHub

31
2Configuring Yocto for DragonBoard 410c

32 LAB 2: Yocto configuration
 Running setup-environment script starts Yocto configuration wizard
• Command to configure and setup Yocto:
• In the setup wizard you can choose:
– MACHINE ID i.e. dragonboard410c
– DISTRO i.e. rpb
• Choices come from 96Boards specific metalayers
– meta-96boards
– meta-qcom
$ source setup-environment

33
3Running Yocto Build for the DragonBoard 410c

34 Exercise 3: Rebuilding console images
 96Boards Yocto takes advantage of “caches”
• The goal is to accelerate build process
• Can be copied to other machines
• Contain build output
• The following variables are typically placed in your conf/local.conf – in Linaro™ Yocto, it is placed in site.conf
– DL_DIR = /home/tsu/LAB-410c/96boards-yocto/downloads
– SSTATE_DIR = /home/tsu/LAB-410c/96boards-yocto/sstate-cache
 BSP image definition – special type of recipe
 Building a BSP image
$ bitbake rpb-console-image
Image Name Description
rpb-console-image Console image
rpb-desktop-image Image that’s based on X11, leveraging hardware acceleration
rpb-wayland-image Image with lightweight windowing system
rpb-qt5-image Image with QT5 toolkit

35 Yocto output
 Output from the build is stored in several directories
 tmp/deploy
 Images for deployment
 tmp/work
 Source code, the patches, last build
We can now re-test images built using deployment
process discussed earlier

36
4Building Yocto SDK for Application Development with
the DragonBoard 410c

37 LAB 4: Building a Yocto SDK
 The Yocto Project is not intended for application development
 A separate SDK can be generated from a Yocto Project build
• Once created, SDK is completely independent of the Yocto Project build system
• Come in a form of a shell script which facilitates SDK setup on a development host
 Yocto allows you to generate two types of SDKs:
1. Generic i.e.
2. Image based i.e.
$ bitbake meta-toolchain
$ bitbake –c populate_sdk rpb-console-image

38
Questions?
developer.qualcomm.com 96boards.org arrow.com timesys.com

Thank you
All data and information contained in or disclosed by this document is confidential and proprietary information of Qualcomm Technologies, Inc. and/or its affiliated
companies and all rights therein are expressly reserved. By accepting this material the recipient agrees that this material and the information contained therein is to
be held in confidence and in trust and will not be used, copied, reproduced in whole or in part, nor its contents revealed in any manner to others without the express
written permission of Qualcomm Technologies, Inc. Nothing in these materials is an offer to sell any of the components or devices referenced herein.
©2017 Qualcomm Technologies, Inc. and/or its affiliated companies. All Rights Reserved.
Qualcomm, Snapdragon and DragonBoard are trademarks of Qualcomm Incorporated, registered in the United States and other countries. Other products and
brand names may be trademarks or registered trademarks of their respective owners.
References in this presentation to “Qualcomm” may mean Qualcomm Incorporated, Qualcomm Technologies, Inc., and/or other subsidiaries or business units within
the Qualcomm corporate structure, as applicable.  Qualcomm Incorporated includes Qualcomm’s licensing business, QTL, and the vast majority of its patent
portfolio. Qualcomm Technologies, Inc., a wholly-owned subsidiary of Qualcomm Incorporated, operates, along with its subsidiaries, substantially all of Qualcomm’s
engineering, research and development functions, and substantially all of its product and services businesses, including its semiconductor business, QCT.
Follow us on:
For more information, visit us at:
www.qualcomm.com & www.qualcomm.com/blog

Developing for Industrial IoT with Linux OS on DragonBoard™ 410c: Session 1

More Related Content

What's hot (20)

Similar to Developing for Industrial IoT with Linux OS on DragonBoard™ 410c: Session 1 (20)

More from Qualcomm Developer Network (20)

Recently uploaded (20)

Developing for Industrial IoT with Linux OS on DragonBoard™ 410c: Session 1