Embedded Computing Design February 2016 by OpenSystems Media

FEBRUARY 2016 VOLUME 14

embedded-computing.com

1 0

1 0 1 1

1 1 0

0 1

1 0

1 0 1

0 1 1

0 1 0

1 1 0

0 1 1

0 0

0 1

Silicon 1

1 1

PLUS 1 1 0

1 0

1 1

1 1 1 0 0 STARTS ON PAGE 22 1 0 1 1 0 0

0 1

1 1

WHAT DEVELOPERS NEED TO KNOW ABOUT CONNECTING TO THE CLOUD 1

1 0

0 1

1 1

1 0 0 1 1 1 Build an intelligent 1 1 1 1 1 0 0 1 0 1 1 0 0 0 0 1 irrigation system 1 1 1 1 1 1 1 1 0 0 1 1 0 1 1 0 0 guide on page 9 1 1 How-to 1 1 1 0 1 0 1 0 1 0 1 0 0 1 0 1 1 0 1 0 1 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Must-sees at0 1 1 1 1 1 1 1 1 1 0 0 0 1 1 1 1 0 1 Embedded World 0 1 1 1 1 1 1 0 0 1 1 1 0 1 PG. 30 1 1 1 1 1 1 1 1 0 1 0 1 1 1 1 1 1 1 1 0 1 0 0 1 1 0 1 0 1 1 1 0 0 1 0 0 1 1 0 1 0 1 1 0 0 1 0 1 0 1 0 1 0 1 1 0 1 0 1 1 1 1 1 1 1 1 1 0 0 1 0 1 1 0 0 1 1 1 0 0 0 1 0 1 1 0 1 1 1 0 1 1 0 0 1 0 0 0 1 0 0 0 0 1 0 0 1 1 1 0 1 1 1 0 1 0 1 1 0 1 0 0 1 1 1 1 0 0 1 0 0 1 1 1 1 0 0 0 0 1 0 1 1 1 1 0 0 0 1 0 0 1 1

TRACKING TRENDS

What I want to see at Embedded World 2016 By Rory Dear, Technical Contributor

“IoT,” “M2M,” and “Industrie 4.0” are a few obvious examples of the plethora of buzzwords I’ve little doubt I will be visually assaulted with as I meander around Nuremberg Messe’s Embedded World 2016, the same as I was last year, and the year before that. These technologies generally fit into the category of “connected” or “connected devices.” For me, Embedded World 2014 was when these connected-device terminologies really caught the imagination of exhibitors. Of course, as is the case with so many desperate to climb aboard the latest bandwagon, what they actually exhibited was often of the loosest relevance to the buzzwords emblazoned across their stands. Through interviewing, many conceded they simply had to publicly pay homage, and the substance would definitely come later. To be fair, many exhibitors had had time to ponder their “connected” strategies and were able to demonstrate which directions their connected solutions would take and speculate which applications they would end up in. I witnessed excitement, enthusiasm, and plans formulating, but that previous verb “speculate” is what defined the event for me: speculation. I entered Embedded World 2015 last year in trepidation, though I was pleasantly surprised to see so many exhibitors had responded to my (and no doubt countless others’) despondency in the lack of real substance to their connected visions. I witnessed a smart

2

rdear@opensystemsmedia.com

lighting example as "intelligent street lighting;" I observed a connected logistics solution for public transport; I even saw a demonstration of an IoT stair lift for the elderly; and whilst appearing initially farcical its value quickly became apparent to me. What the exhibition lacked, predominantly through lack of elapsed time since the previous event, was sufficient real-world usage examples to really drive home the benefits of what our industry is trying to achieve for “yet to convince” onlookers. If you haven’t guessed it yet, what I want to see at Embedded World 2016 is proof. I want to see, read, and hear about completed projects, finished deployments where statistics following smart connectivity prove to the world its value. I want to see case studies, with indisputable statistics and feedback from those well outside of our industry of the benefits they value, and from those with no vested interest – or even better no interest at all in fact – what the technology actually is at its core. This for me is what takes the connected devices movement beyond clever marketing fodder and presents a palpable benefit to people’s lives. Earlier this year I personally reviewed XeThru’s respiration detection evaluation kit on my (then) 2-month-old baby son before its official release. It promised a revolution in remote baby monitoring and the elderly (typically monitored far more remotely) alongside potential applications in point of sale. He’s now

a year old and having used the kit I’m desperate to see where this technology drove their clients and understand exactly where and how such sensors are being used today. I mention this (at its core) “unconnected” example as this revolution can be revolutionized itself by combining it with increased connectivity. Maternity wards or nursing homes can, for the first time, have centralized health and wellbeing monitoring without intrusive surveillance cameras. Perceptual computing is an emerging area that I covered recently that promises a new way to interact with machines in an immersive, seamless fashion. We’ve also seen advances this year in artificial intelligence (AI). Both technologies offer the opportunity for a fresh wave of innovation on show at Embedded World 2016, though I’m hoping for more than pure speculation. Quite how these technologies will combine in a decade’s time is potentially a scary thought; the complexity of security in such devices is already a huge challenge, and vulnerabilities in what we’d consider “safe” devices seem to be regularly revealed. The fear of relinquishing control, be that to a malicious “hacker” or a rogue artificial brain, I’m not sure which is the bigger threat. Our experience of AI for most of us now is restricted to trying to confuse online bots – just how comfortable will we feel once we concede or believe AI has the upper intellectual hand on ourselves, I don’t know.

Embedded Computing Design | February 2016

Small Form Factor Computers Intel® Atom™ E3800 and i.MX6 CPUs Fanless -40° to +85°C Operation Mini PCIe and IO60 Expansion

PC/104 Single Board Computers Rugged, Stackable Form Factor I/O Modules and Power Supplies

Industrial Computer Systems Off-the-shelf and Custom Solutions Fanless -40° to +85°C Operation

Single Board Computers COM Express Solutions Power Supplies I/O Modules Panel PCs

Accelerate Your Product Development Cycle

Speed up time-to-market with embedded solutions from WinSystems. Our industrial computers include expansion options, so customers can expedite prototyping and integration without the burden of CPU or carrier board design. These proven hardware platforms also provide the building blocks to create customized, application-specific designs. Products are in stock and available for immediate shipment from our Arlington, Texas facility. Let our factory Application Engineers accelerate your capabilities.

Come visit us in Hall 2 - Booth #644 715 Stadium Drive I Arlington, Texas 76 011 Phone: 817-274-7553 I Fax: 817-548-1358 www.winsystems.com I info@winsystems.com

0 0

1 0 1

1 1

0 1

1 0 0

1 1 0

0 0

0 0 0 1

1 1

0 0

0 1 1 0

0 0 0

0 1

1 0

1 1

0 0

0 1 1 0

0 0 0

0 0

1 0

0 1

1 0

FEBRUARY 2016 VOLUME 14

0 1 1 1 1 0 1 1 embedded-computing.com | 1 1 0 1 0 1 0 1 1 0 1 1 0 1 1 0 0 1 0 1 0 0 0 0 0 1 1 0 1 1 1 1 0 1 0 0 1 0 0 0 0 1 0 0 1 0 0 1 1 1 1 1 1 0 1 0 0 0 0 0 1 1 0 1 1 1 1 1 1 0 0 1 1 0 1 1 0 1 1 0 1 0 1 0 1 0 1 1 1 0 0 0 0 1 0 0 1 1 0 1 1 1 0 1 1 0 1 0 0 0 1 0 1 1 0 1 0 1 0 0 1 0 1 1 1 1 1 0 0 1 1 0 1 0 1 0 1 0 1 1 1 1 1 0 1 1 0 1 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 1 0 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 0 1 0 1 1 1 1 1 1 1 0 1 1 0 0 1 0 0 1 0 0 1 0 1 0 1 1 1 1 0 1 0 0 1 0 0 1 0 1 1 1 1 1 1 1 1 1 1 0 1 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 1 0 1 1 1 1 1 1 0 0 0 0 1 0 0 1 1 0 1 1 1 1 0 1 0 1 0 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 1 1 1 1 0 1 1 0 0 0 0 1 0 1 1 1 1 1 1 1 1 1 1 0 0 1 1 1 1 0 1 1 0 1 1 1 1 1 1 0 1 0 1 1 1 1 1 1 1 1 0 1 1 1 0 0 1 0 1 0 1 1 1 0 0 1 0 0 1 1 0 0 1 0 1 1 0 1 0 1 0 1 0 0 1 1 1 1 0 1 0 1 1 1 1 1 1 1 1 0 0 1 0 1 1 0 0 1 1 1 0 0 0 1 0 1 1 0 1 1 1 0 1 1 0 0 1 0 0 0 1 0 0 0 0 1 0 0 1 1 1 0 1 1 1 0 1 0 1 1 0 1 0 0 1 1 1 1 0 0 1 0 0 1 1 1 1 0 0 0 0 1 0 1 1 1 1 0 0 0 1 0 0 1 1 0 1 1 0 1 1 1

@embedded_comp |  opsy.st/ECDLinkedIn

Departments

2 Tracking Trends What I want to see at Embedded World 2016 IoT Insider 7

Rory Dear, Technical Contributor

Brandon Lewis, Technology Editor

An IoT development kit comparison

Editor's Choice

Silicon

an intelligent irrigation system using 9 Build Microchip Curiosity, part 1 momentum as new integration in 12 IoTMCUscontinues emerges 14 The expansion of a semiconductor contraction By Brandon Lewis, Technology Editor

By Curt Schwaderer, Editorial Director By Ray Zinn, Former Micrel CEO

Software Hardware emulation to debug embedded system software

16 Formal verification going mainstream for 19 SoC block verification By Dr. Lauro Rizzatti

By David Kelf, OneSpin Solutions

Strategies Maximizing cloud value with strategy before connectivity

22 Bluetooth Smart – What IoT developers 25 Evaluating need to know about getting connected 28 Embedded device security for the IoT By Catherine Ter Horst, Dedicated Computing

By Mark Bowyer, Anaren

Web Extras



Annual Reader Survey: What are your preferences? The results are in.

By Rich Nass, Embedded Brand Director opsy.st/ReaderSurvey15



Build versus buy when it comes to IoT



Floored: CES 2016 recap



IoT Design Weekly Newsletter

By Adebayo Onigbanjo, Zebra Technologies opsy.st/BuildvsBuyIoT

By Brandon Lewis, Technology Editor opsy.st/CES2016recap

Subscribe at opsy.st/IoTDesignENLsubscribe

DOWNLOAD THE APP Download the Embedded Computing Design app: iTunes: itun.es/iS67MQ Magzter: opsy.st/ecd-magzter

By Mike Rohrmoser, Digi International

4

Embedded Computing Design | February 2016

www.dspaceinc.com

dSPACE MicroLabBox â&#x20AC;&#x201C; Compact power in the lab Are you looking for a powerful development system for all kinds of laboratory tasks that takes up little space and comes at an attractive price? dSPACE MicroLabBox provides a SimulinkÂŽ-programmable real-time processor with high computing power, combined with an FPGA and over 100 I/O interfaces. All this with a desk space no larger than a conventional laptop computer. MicroLabBox is the ideal solution for conveniently creating, optimizing and testing controllers in drive technology, robotics, medical engineering, and many other areas. MicroLabBox - your new all-in-one system for research and development.

Advertiser Index

Advertiser Information

39 Annapolis Micro Systems, Inc. – High-performance signal and data processing in scalable COTS FPGA computing fabric

EMBEDDED COMPUTING BRAND DIRECTOR Rich Nass rnass@opensystemsmedia.com EMBEDDED COMPUTING EDITORIAL DIRECTOR Curt Schwaderer cschwaderer@opensystemsmedia.com MANAGING EDITOR Monique DeVoe mdevoe@opensystemsmedia.com

13 COMMELL Systems Corporation – Leading provider of SBCs

TECHNOLOGY EDITOR Brandon Lewis blewis@opensystemsmedia.com TECHNICAL CONTRIBUTOR Rory Dear rdear@opensystemsmedia.com

40 Dell – Dell Internet of Things Contest – Connect what matters

E-CAST MANAGER Joy Gilmore jgilmore@opensystemsmedia.com CREATIVE SERVICES DIRECTOR David Diomede ddiomede@opensystemsmedia.com

5 dSPACE dSPACE MicroLabBox – Compact power in the lab

GRAPHIC DESIGNER Chris Rassiccia crassiccia@opensystemsmedia.com SENIOR WEB DEVELOPER Konrad Witte kwitte@opensystemsmedia.com

17 Gigabyte – IoT cloud/embedded solutions – We are exactly what you need

CONTRIBUTING DESIGNER Joann Toth jtoth@opensystemsmedia.com

21 Micro Digital, Inc. – SMX RTOS is IoT ready

SALES SALES MANAGER Tom Varcie tvarcie@opensystemsmedia.com (586) 415-6500

3 WinSystems, Inc. – Accelerate your product development cycle

STRATEGIC ACCOUNT MANAGER Rebecca Barker rbarker@opensystemsmedia.com (281) 724-8021

STRATEGIC ACCOUNT MANAGER Eric Henry ehenry@opensystemsmedia.com (541) 760-5361

Embedded World Profiles

Category

STRATEGIC ACCOUNT MANAGER Twyla Sulesky tsulesky@opensystemsmedia.com (408) 779-0005

31 Acnodes Corporation

Industrial

31 ADL Embedded Solutions Inc.

Hardware

STRATEGIC ACCOUNT MANAGER Kathleen Wackowski kwackowski@opensystemsmedia.com (978) 888-7367 SOUTHWEST REGIONAL SALES MANAGER Barbara Quinlan bquinlan@opensystemsmedia.com (480) 236-8818 SOUTHERN CALIFORNIA REGIONAL SALES MANAGER Denis Seger dseger@opensystemsmedia.com (760) 518-5222 NORTHERN CALIFORNIA REGIONAL SALES MANAGER Sydele Starr sstarr@opensystemsmedia.com (978) 888-7367 ASIA-PACIFIC SALES ACCOUNT MANAGER Elvi Lee elvi@aceforum.com.tw EUROPE SALES ACCOUNT MANAGER James Rhoades-Brown james.rhoadesbrown@husonmedia.com

WWW.OPENSYSTEMSMEDIA.COM

30 Anaren IoT 34-35 Connect Tech, Inc. (CTI)

Hardware

32 Digi International

Hardware

32 Dolphin Interconnect Solutions Inc.

Networking

33 MicroMax Computer Intelligence

Hardware

33 Quantum Leaps

Operating Systems & Tools

36 VersaLogic Corp.

Hardware

37 WinSystems, Inc.

Hardware

PUBLISHER Patrick Hopper phopper@opensystemsmedia.com PRESIDENT Rosemary Kristoff rkristoff@opensystemsmedia.com EXECUTIVE VICE PRESIDENT John McHale jmchale@opensystemsmedia.com EXECUTIVE VICE PRESIDENT Rich Nass rnass@opensystemsmedia.com CHIEF TECHNICAL OFFICER Wayne Kristoff GROUP EDITORIAL DIRECTOR John McHale jmchale@opensystemsmedia.com

Get your free digital edition at embedded-computing.com/emag

ASSISTANT MANAGING EDITOR Lisa Daigle ldaigle@opensystemsmedia.com SENIOR EDITOR Sally Cole scole@opensystemsmedia.com ASSOCIATE EDITOR Mariana Iriarte miriarte@opensystemsmedia.com VITA EDITORIAL DIRECTOR Jerry Gipper jgipper@opensystemsmedia.com PICMG EDITORIAL DIRECTOR Joe Pavlat jpavlat@opensystemsmedia.com MANAGING EDITOR Jennifer Hesse jhesse@opensystemsmedia.com

Subscriptions: embedded-computing.com/subscribe subscriptions@opensystemsmedia.com

CREATIVE DIRECTOR Steph Sweet ssweet@opensystemsmedia.com FINANCIAL ASSISTANT Emily Verhoeks everhoeks@opensystemsmedia.com SUBSCRIPTION MANAGER subscriptions@opensystemsmedia.com CORPORATE OFFICE 16626 E. Avenue of the Fountains, Ste. 201 • Fountain Hills, AZ 85268 • Tel: (480) 967-5581 SALES AND MARKETING OFFICE 30233 Jefferson • St. Clair Shores, MI 48082

REPRINTS

2016 OpenSystems Media ® © 2016 Embedded Computing Design All registered brands and trademarks within Embedded Computing Design magazine are the property of their respective owners. iPad is a trademark of Apple Inc., registered in the U.S. and other countries. App Store is a service mark of Apple Inc. ISSN: Print 1542-6408, Online: 1542-6459

WRIGHT’S MEDIA REPRINT COORDINATOR Wyndell Hamilton whamilton@wrightsmedia.com (281) 419-5725 enviroink.indd 1

6

10/1/08 10:44:38 AM

Embedded Computing Design | February 2016

IoT INSIDER

An IoT development kit comparison By Brandon Lewis, Technology Editor

blewis@opensystemsmedia.com

Over the past couple of years, I have routinely hinted at the rise of development kits, the Internet of Things (IoT), and how the two go hand in hand. It’s a serendipitous relationship that facilitates quick development and prototyping in a large, fastgrowing market – not to mention that an increasing number of kits can be had on the cheap. Furthermore, where early dev boards offered a basic processing unit, some assortment of I/O, limited memory, and the expectation that engineers would navigate the web for open-source software and tools, today’s often provide connectivity, cloud access, and ship with low-cost or no-cost development environments and debuggers for a truly out-of-the-box experience.

õõ

While Arduino, BeagleBoard, and Raspberry Pi still dominate the space, data from Embedded Computing Design’s 2015 Reader Study shows that more than 38 percent of engineers planning to adopt a development kit in their next design will use one from a specific manufacturer. With that in mind – and after returning from the Consumer Electronics Show where dev kits were at the heart of countless demos – I decided to start compiling a list of IoT-centric kits available on the market today. Though apples-to-apples comparisons are difficult because each manufacturer’s kit emphasizes different features based on their silicon and tools, I was able identify seven categories of interest to IoT developers that are common across most kits. Represented in Table 1 (next page), these are Wireless, Compute, Memory, I/O & Peripherals, Tools, Cloud, and Cost:

õõ

õõ õõ õõ õõ

õõ õõ

Wireless is essential to classification as an “IoT dev kit,” and as such includes information about on-board connectivity like Bluetooth, Wi-Fi, 6LoWPAN, etc.; Compute attempts to isolate a board’s general-purpose/ applications processor (or core in the case of systems-onchip (SoCs)) Memory can include on-chip RAM or ROM as well as any additional storage provided on the board I/O & Peripherals is defined loosely as physical access to any onboard resources for the purposes of low-level programming (expansion headers are assumed) Tools highlights software made accessible to developers with the purchase of a particular kit The Cloud section outlines compatibility with various backend services, either exclusive to the manufacturer or available through partnerships Cost is the final measure, which is subject to change Sensors are not included since many dev kit ecosystems rely on third-party or add-on sensors

The initial comparison includes five kits from Anaren, Atmel, Imagination Technologies, Marvell Semiconductor, and Texas Instrument, although the list will certainly grow as the price of electronic components drops and manufacturers look to eliminate barriers to entry. Over time, I hope this proves a valuable resource for the next generation of IoT app developers. With that, I leave the evaluation to you.

Clockwise from top left: • Anaren Bluetooth Smart Development Kit (A20737A-MSDK1) • Atmel SAM W25 Xplained Pro Evaluation Kit • Imagination Technologies Creator Ci40 IoT Kit • Texas Instruments SimpleLink Wi-Fi CC3200 LaunchPad development kit • Marvell Semiconductor EZ-Connect MW302 IoT Starter Kit

www.embedded-computing.com

7

IoT INSIDER Compute

Memory

I/O & Peripherals

Wireless

Tools

Anaren A20737AMSDK1¹

ARM CortexM3

• 320 KB ROM • 64 KB EEPROM

• ADC • I2C • UART • SPI • PWM • GPIO • I2S audio

• Bluetooth 4.1

• Anaren • Anaren Strato- $30-$35 Atmosphere sphere (TBA)

Atmel SAM W25 Xplained Pro²

48 MHz ARM Cortex-M0+ MCU

• 8 MB Serial Flash

• Atmel Data Gateway Interface • GPIO • I2C • UART • USB • SPI • Virtual COM

• 802.11 b/g/n Wi-Fi

• Atmel Studio • Embedded Debugger

Imagination 550 MHz Creator dual-core, Ci40³ dual-threaded MIPS32 InterAptiv CPU

• 256 MB DDR3 SDRAM • 512 MB NAND Flash

• ADC • EJTAG • GPIO • I2C • mikroBUS • PWM • Raspberry Pi B+ • SPI • UART

• 2x2 802.11 • FlowCloud • FlowCloud b/g/n/ac Wi-Fi SDK • 802.15.4 (6LoWPAN) • Bluetooth 4.1

$52

Marvell EZ-Connect MW302⁴

• 512 KB SRAM • External QSPI Flash

• ADC • DAC • GPIO • I2C • I2S • JTAG • PWM • SPI • UART • USB 2.0

• 1x1 802.11 b/g/n Wi-Fi

• Marvell AWS IoT Starter SDK • Eclipse • ARM GNU Compiler/ Debugger • OpenOCD

• AWS IoT • Arrayent • Ayla • Evrythng • Xively

$49

• 256 KB RAM • External SPI Flash • ROM Bootl- oader • 32-chan- nel µDMA

• ADC • I2C • I2S • Parallel Camera • PWM • SDMMC • SPI • UART

• 802.11 b/g/n Wi-Fi

• Code Composer Studio • GNU Com- piler/De bugger • OpenOCD • IAR Embed- ded Work- bench

• AWS IoT • Arrayent • Exosite • IBM IoT Cloud • Xively

$29.99

200 MHz Cortex-M4F MCU

Texas 80 MHz ARM Instruments Cortex-M4 SimpleMCU Link Wi-Fi CC3200 LaunchPad⁵

Cloud

• Arrayent • Exosite • Proximetry • PubNub • wot.io • Zatar

Cost

$42.65

Notes: 1. Anaren Atmosphere enables simultaneous embedded code generation and app creation in online development tool 2. Current measurement header allows real-time monitoring of the low-power SAM W25 Wi-Fi module with ammeter 3. Supported distributions include OpenWrt, Debian, and Google’s Brillo operating system 4. Hardware root-of-trust enables secure boot for trusted storage and communications 5. Embedded Wi-Fi security and TCP/IP stack includes protocols such as mDNS, DNS, HTTP, and example code for XMPP and SMTP

8

Embedded Computing Design | February 2016

Integrated MCUs

Build an intelligent irrigation system using Microchip Curiosity, part 1 By Brandon Lewis, Technology Editor

Goal: The following is the first in a multipart series describing how to build an intelligent irrigation system using the Microchip Curiosity Development Board and associated tools as a foundation. Building off of our introduction to the Curiosity board, MPLAB X Integrated Development Environment (IDE), and MPLAB Code Configurator (MCC), part 1 of the series details how to generate two pulse-width modulated

waveforms and process them through a configurable logic cell (CLC) to create a heartbeat LED that will indicate when watering is needed based on the voltage output received by a comparator from a Grove moisture sensor. Developing the logic for this portion of the application requires no coding when using a CLC and MCC. Difficulty level: Beginner Hardware/Software required:

õõ

www.embedded-computing.com

Microchip Curiosity Development Board (Outfitted with PIC16(L) F161X MCUs – Used here is the PIC16F1619) Grove Moisture Sensor – Available from Seeed Studio

õõ õõ õõ

Microchip MPLAB X IDE version 3.05 or later MPLAB XC Compiler MPLAB Code Configurator version 2.25 plugin

Creating a breathing LED The first step of our project is to create a breathing LED. Typically this is achieved using a software algorithm that includes loops to slowly increase and decrease the duty cycle of the LED. To achieve this without writing any code, however, we’re going to use two pulse-width modulators (PWMs) with the same pulse width but slightly offset timer periods and frequencies. The duty cycle for each PWM will be set to 50 percent, but one PWM (PWM3) clock cycle will be set to 31 ms while the other (PWM4) is set to 32 ms so that the signals driving the LED (LED D7) pass each other in time, resulting in a transition that creates a “breathing” effect. The configurable logic cell (CLC) peripheral integrated into Curiosity’s onboard PIC16F1619 microcontroller handles the “AND-OR” function required for this operation.

9

SILICOn

Integrated MCUs

Setting up PWM periods and frequencies To get started, create a New Project in the MPLAB X IDE and launch the MPLAB Code Configurator and name it “Curiosity_ WaterSensor (for detailed instructions on how to do this, as well as enabling LowVoltage Programming [IMPORTANT!], read the previous tutorial. Once you have created a new project, select both available PWMs (PWM3 and PWM4) from the Device Resources window by double clicking them. Adding a PWM will automatically include an 8-bit timer (TMR2) in your project, to which both PWM3 and PWM4 will default as their time base. However, to generate a breathing LED we’ll need two separate time bases, and an additional timer is needed. You can easily add one to your project by clicking PWM4 (now in your Project Resources window) and selecting Timer4 from the “Select a timer:” dropdown menu in the MPLAB Code Configurator window. TMR4 (also an 8-bit timer) should now be added to your project. At this point you need to configure the PWMs to generate two waveforms at different frequencies. The timers governing the PWMs are based on the system clock source; so in order to slow down the rate of the system clock oscillator for our breathing LED, navigate to the System window under Project Resources and make sure that the System Clock Select is set to the frequency of the oscillator (FOSC). In the same window set the Internal Clock frequency to 31KHz_LF, a rate slow enough for our application. Now that you’ve configured the system clock, it’s time to set up the timers. Back in the Project Resources window, select the TMR2 timer and change the Clock Source to FOSC/4 in the MPLAB Code Configurator window (as its name suggests, selecting a FOSC/4 clock is going to provide a clock source that is one-fourth the frequency of the System Clock). You’re also going to want to set the Prescaler to a 1:2 ratio in order to get a more precise Timer Period (for an explanation of Prescaler and Postscaler, see the “PWM control” section of the

 10

Curiosity introduction article). In the Timer Period box you will now enter a value of “31.0 ms” and hit enter. This hasn’t been an incredibly scientific exercise, but the system should return a value very close to 31 ms (30.968 ms in my case). In the Project Resources window navigate to TMR4 and perform these exact steps, but set the Timer Period to “32.0 ms.” By navigating to either PWM3 or PWM4 and ensuring they are configured to different timers, you’ll note that each has a slightly different PWM Period and Frequency. Using configurable logic cells to circumvent coding In order to create a breathing LED the two PWM outputs will need to be combined using “AND-OR” logic and driven to the same microcontroller pin. As mentioned, AND-OR functions are typically performed in software, but by using CLC peripherals you can achieve this without having to write any code. Under Device Resources, add a CLC resource to your project by doubleclicking “CLC1,” then select it in the Project Resources menu. In the MCC window a graphical representation of logic gates will appear that allows you to select the input/output of various resources and apply combinational or sequential logic to them. To drive the two PWM outputs to generate the breathing LED you’re going to select the “ANDOR” combinational logic setting from the menu at the top of the graphical representation, and then select “PWM3_ OUT” and “PWM4_OUT” from the first two dropdowns on the left-hand side of the graphic, respectively. Now, trace the signal from the PWM3 output to its corresponding input on “GATE 1” and open the connection by clicking the overlaying X once until you have a solid line. Do the same for the PWM4 output on “GATE 2” (the solid black dots represent the signal trace to each gate, so you should have selected the first input on GATE 1 and the second input on GATE 2). You’ve just established some simple logic. If a 1 (or “on high”) registers on

both of the PWM inputs, the output of the CLC will register as a 1, running the LED high. Conversely, if a 0 registers on either or both of the outputs, the combined output will be a zero (for some basic background on logic gates, check out Wikipedia). The overlapping PWM periods created earlier produce alternating intervals of 1 and 0, which provides the breathing effect. All that’s left to do for the breathing LED is connect our CLC to the pins driving our LEDs. Open up the MCC Pin Manager, and locate CLC1OUT from the available modules in the table on the left and connect it to the RC5 pin that drives LED D7 by closing the lock in the corresponding grid cell (once you click the blue open lock, it will close and turn green). Select “yes” when you are prompted to change the pin allocation. Now click “Generate Code” from the top left of the MCC window, and select “yes” when asked if you’d like to generate a main.c file. From the top navigation select “Make and Program Device Main Project” from the menu next to the downward-facing arrow. LED D7 should now be “breathing.”

Setting up a comparator and incorporating the moisture sensor Because this is an irrigation system, we of course need to incorporate a moisture sensor into our project. This project uses a Grove Moisture Sensor from Seeed Studio, though any basic moisture sensor with an analog output should do. What allows the use of such a basic sensor in a smart irrigation system, however, is that by leveraging the intelligent analog peripherals on the PIC16F1619 microcontroller you are able to instruct a comparator (a device that compares two analog voltage inputs then outputs a digital signal) to trip at different values depending on the time of day, time of year, the type of plant being watered, etc. For this project, the comparator inputs will be a multiple of the fixed voltage reference (FVR) of 1.024 V (C1IN+) and the voltage obtained from the pin tied to the moisture sensor (C1IN1-). The comparator output

Embedded Computing Design | February 2016

will be a “1” if the C1IN1- voltage is greater than the C1IN+ value, and otherwise, will be a “0.” To add a comparator to the project, select it from the Device Resources window and double-click CMP1. Programming options will now appear for the comparator in the MCC window, and you’ll want to ensure that the Negative Input is set to “C1IN1-” and the Positive Input is set to “FVR_pin.” Additionally, click the “Enable Low Power” check box because this application doesn’t require high-performance

Figure 1

interfacing with the microcontroller, and you’ll want to be as energy efficient as possible since the eventual power source will be four AA batteries.

properly at this point, a 2.048 V FVR provides a more median value on the system’s 5 V range for indicating the presence or lack of moisture).

You’ll notice that when you selected the FVR_pin as your Positive Input reference, an FVR was added to your Project Resources. To configure the FVR, select it from the Project Resources menu, and in the MCC window change the “FVR sent to Comparators, DAC and CPS” to 2x to give us an FVR of 2.048 V (since we’re just installing the moisture sensor to make sure everything is working

Now, in the MCC Pin Manager, connect CMP1 to a pin by locating the lock that corresponds with C1IN1- and the RC1 port, and clicking so the lock icon closes and is encircled by a green box.

If you want Curiosity’s LED to breathe when the sensor is in the water, you have to invert the comparator input on logic GATE 2. To do so, trace the signal for CMP1 and click the X until a hollow circle appears. To have the LED report when the sensor is dry, just click the X until a solid line appears.

Tying the breathing LED to the comparator output With the goal in mind of having the breathing LED report when a plant needs water, you now need to create a condition that combines the outputs of the first CLC and the comparator and runs them through a second CLC. To do so, add CLC2 to your project by selecting it from the Device Resources menu, then highlight it once it’s been added to your Project Resources. In the graphical representation that appears in the MCC window, again make sure that the AND-OR logic setting is selected, and choose the “LC1_out” signal from the first dropdown on the left to include CLC1 and “C1OUT” from the second dropdown for CMP1. Again, trace the LC1_out signal to the corresponding input on GATE 1 and click the X until you have a solid line, and do the same for the C1OUT on GATE 2 (if you want the breathing LED to report when the sensor is in the water, you’ll need to invert the comparator output; to do so, click the corresponding trace signal until a circle appears where there was originally an X (Figure 1)). In the MCC pin manager, you can now connect the CLC2OUT to port RA2. Click Generate Code, then Make and Program Device. At this point, all that’s left to do is wire the Grove – Moisture Sensor to your Curiosity board. Connect the sensor’s black wire to the ground (GND) pin to ensure that both the board and sensor are using the same baseline, and run the yellow wire to the RC1 pin, which we selected as the Comparator 1 input (both of these pins are located on the J11 expansion header). On the J3 expansion header, run the red wire to the Vdd port to power the sensor.

Figure 2

Once the sensor is properly wired to Curiosity, dip it in a glass of water. When dry, LED D6 will respond by breathing; when the sensor’s wet, LED D6 will be off.

www.embedded-computing.com

Curiosity’s LED D6 is now also breathing. Fill a cup of water and dip the end of the sensor in. When it’s wet, LED D6 will turn off (Figure 2).

11 

Integrated MCUs

IoT continues momentum as new integration in MCUs emerges By Curt Schwaderer, Editorial Director

cschwaderer@opensystemsmedia.com

Wireless connectivity is a big driver in the world of IoT. Combining wireless protocols with compute power, power management, and sensor technologies has opened the door to a wide variety of IoT applications. In this feature, we’ll look at how Redpine Signals leveraged their expertise in wireless technology to create integrated MCUs for the IoT market. In many ways the Internet of Things (IoT) represents the convergence of the increased usefulness of information from network embedded systems within a variety of industries with the cost economics of the mobile phone industry whose economy of scale drives down costs of components and technologies. The result is IoT: Internet-connected devices collecting information that, when deployed on a large scale, collected, and analyzed, can change the way the world lives, learns, works, and plays. Venkat Mattela, Chairman and Chief Executive Officer at Redpine Signals (www.redpinesignals.com) describes IoT as “an inch-deep, mile-wide” market. “When you look at the IoT space, it spans virtually every market in existence – medical, industrial, consumer, automotive, building automation, and smart energy among others,” Mattela says. “All these markets have vastly different characteristics and use cases, but there are a few common underlying themes – compute, power management, and wireless connectivity. That’s why we decided to leverage our core expertise in wireless protocols and integrate this within an MCU architecture.” Redpine was originally going after the mobile phone market with a convergence IC. They started with wireless, incorporating dual-band 802.11 Wi-Fi with a/b/g/n variants. Bluetooth EDR and LE have also become important wireless device technologies. ZigBee is a third that has been gaining critical mass. Mattela views the IoT market as starting in 2008. Redpine recognized they needed an effective low-power CPU core

 12

architecture to blend with their wireless capabilities as an IoT System on Chip (SoC). They decided to use the Cortex-M4 for the compute core in order to leverage the right mix of compute performance and power efficiency. The result is called the WiSeMCU (Wireless Secure MCU) product line. The WiSeMCU is based on their own silicon and certified modules. The result is the ability for IoT developers to leverage a mix of modules on a single MCU to put together their device quickly and easily with optimized cost. Mattela also mentioned another aspect of the IoT “inch-deep, mile-wide” attribute is there are millions of customers, but each only consumes modules in the 10s, 100s, or 1,000s of units as opposed to consuming millions of specific SoC silicon like the smartphone market. This represents unique challenges to module developers to identify a common-denominator set of capabilities and provide a fixed range of capabilities that address the majority of these customers. “We have about 4,000 customers today spread across lots of markets and applications versus one or a few customers purchasing millions of devices,” Mattela says. “This is a very big challenge if you don’t understand how to sustain an inch-deep, mile-wide paradigm.” Redpine has identified three main variants – the RS10001 Wireless MCU single band module with multi-protocol capability and Cortex-M4 processor. The M4 runs at 100 MHz Embedded Computing Design | February 2016

Another interesting feature relevant to IoT is the “Security Accelerator” block. This enables a binding of silicon and software that provides an added measure of protection. Redpine calls this “physically unclonable functions” (PUFs). Every chip has an integrated signature that can be used for software verification to prevent malicious malware updating or illegal software down unlicensed systems.

Figure 1

The Redpine RS10002 block diagram.

Of course IoT support isn’t complete without some kind of software development kit (SDK) and development board to prototype device features and capabilities. There is a development board available for this purpose along with an SDK including a wireless applications library with example projects using Wi-Fi, Bluetooth, and ZigBee (Figure 2). Demonstration applications make it easy to bring up prototype environments and there are tool chains and integrated development environments (IDEs) from CoIDE, Keil, and IAR available. Mattela finished with an illustration of how their WyzBee platform and product synthesis concept is so important. “Redpine has gone through many projects where customers historically took up to 18 months to develop and integrate, only to give them a 10,000 unit order,” Mattela says. “We asked ourselves why it was taking so long?”

Figure 2

A software development kit (SDK) and development board are available for prototyping.

with 512 KB of flash and 104 KB of SRAM. It is also the smallest module of its kind at 8.6 mm x 8.6 mm x 1.7 mm. The part features integrated Wi-Fi, Bluetooth 4.0, and ZigBee. Mattela mentioned that people also wanted a drop-in replacement for their popular RS9113 module. Thus the RS10002 was born – same capabilities and specs as the RS10001, but in a footprint compatible with existing RS9113 connectivity modules. For larger IoT applications, the RS10003 provides a 160 MHz Cortex-M4 processor with up to 1 MB of flash and 128 KB of SRAM plus dual-band Wi-Fi, Bluetooth, and ZigBee protocol support. Figure 1 shows the RS10002 block diagram. There are a number of available peripherals for the device that provides a robust set of features for peripherals for a variety of IoT applications. The Cortex-M4 and peripherals combine with the four integrated types of wireless connectivity protocols for a unique one-chip IoT solution that can address inch-deep, mile-wide markets. www.embedded-computing.com

It turned out to be the product synthesis. When customers were pulling in the Cortex-M4 and sensors, and then had to deal with the wireless on-ramp connectivity to the Internet to get the data to the cloud, it became very time consuming and challenging where some companies had to grow core competencies from scratch. Then when integration issues occurred, there were delays. Redpine decided to create the integrated WyzBee IoT Device Maker Platform with a goal of being able to create the prototype with a push-button. “The WyzBee platform shrinks prototype execution to a couple days as opposed to months,” Mattela says. “Customers can now choose the right products from a library, then push a button and produce the prototype quickly including creating a cloud instance. In addition, the single-source-solution eliminates integration delays. The WiSeMCU is a one-stop-shop for an IoT processor.” IoT is giving rise to innovative integration from unlikely sources. New integrated environments that target IoT applications and shrink development time for this “inch-deep, mile-wide” market promises to advance concepts quickly and enable more innovative applications of IoT for all industries.

13 

Mergers & Acquisitions

The expansion of a semiconductor contraction By Ray Zinn

The semiconductor industry is consolidating as it is expanding. This seemingly contradictory situation has an origin, but no end in sight. industry grows in spurts. It has to endure relatively sudden changes in direction. Micrel rode the consumer products chip wave for a while, and saw many competitors disappear due to seemingly minor mistakes and sudden market changes.

I’ve seen this before, having founded Micrel 37 years ago and having been in the semiconductor industry for 50 years. At Micrel, we rode out many cycles, survived the dot-com imposition (our only unprofitable year), and have seen fabrications facilities (fabs) grow from a handful, mainly in Silicon Valley, to more than a thousand scattered around the world. Semiconductors went from specialized chips used primarily by the military to consumer goods to ever more powerful (yet shrinking) IT servers to putting a wireless computer into nearly every pocket. The industry is currently contracting because it grew rapidly, with demand for chips growing, with new device types arriving weekly. But with industry standards driving specialized chips to the margins, the semiconductor

 14

In short, for every growth spurt in the industry – whether due to chasing a market or a market segment, or innovations that become commoditized – the number of semi companies and fabs grows. Then when markets change, some companies suffer revenue hits and have to sell out. Others plateau and shareholders force a sale. Others simply die. Thus the number of semi companies shrinks. This current contraction is just another cycle, though amplified by recent growth history. Two factors – industry standards for products and shrinking silicon geometries – caused demand to skyrocket and margins to shrink. In high growth periods, especially ones with new markets, more companies come online to fulfill demand. Once industry standards and competition increases to a fever pitch, margins fall and consolidation begins. It seems impossible that consolidation is starting in this era when the consumer electronics markets – from iPhones to Nests to FitBits – are exploding. But the trend will not abate for now. Capacity is larger than even

consumers and recovering economies can absorb. Combine this natural boom/bust cycle with a global economy that has been growing very slowly over the past six years. Since so much of the semiconductor industry is now based on consumer products, and with the economy ailing, growth for all these semiconductor companies has been poor despite larger markets – the pie is being divided into very thin slices. To meet the demands of institutional and activist investors, some companies are forced to grow via acquisition, driving consolidation even faster. Between the normal cycle, massive overbuild, and economic amplifications, we have a perfect storm for industry consolidation. Two other reasons, horribly combined, are making the current round of consolidation extreme. These are cheap money and inorganic growth. Interest rates have been held artificially low for years in an effort to stabilize world economies. Borrowing money effectively costs nothing today. Companies interested in buying other companies have to either have a lot of treasury shares (stock they kept for themselves and not sold on the open market) to trade for shares in the acquired company, or they need a lot of cash. Normally, an acquiring company would not borrow money for M&A activities because the cost to borrow

Embedded Computing Design | February 2016

hundreds of millions of dollars or more would be ruinous. But today it is quite feasible. Cheap money paired with treasury shares can make acquisitions financially painless. The question then is, “Why?” Solid bottom line growth comes from growing organically. But many semiconductor companies have not experienced reasonable revenue growth despite the largest and fastest growing demand in human history. Be it executive inability to navigate markets, engineering inability to conceive of new and viable products, or just plain bad luck, many semiconductor companies are not growing and their shareholders are not happy. This causes some CEOs of semiconductor companies to launch M&A sprees, most with the same tragic results. Years ago, a CEO I knew headed a major semiconductor company. He decided he needed to get his company’s top-line revenues up to one billion dollars. Yet the industries in which his company worked were not going to grow at the pace he desired results, and he was unwilling to take the time to build the teams, technology, and market strength to grow. Instead, he launched an M&A campaign with artificial deadlines for gaining top-line revenues. This led to sloppy merging of the acquired companies, frustrated employees, falling product quality, chaotic customer support, and more. In the end the CEO never achieved his billiondollar dream, and was sacked when the weight of the acquisitions destabilized the company. This time around, it may be worse. Sad as the corporate failures from irrational consolidation may be, the human toll is worse still. Real people lose their jobs when companies merge. This means real families with real hopes and dreams are cast aside. They don’t take vacations, never fund their children’s college fund, and even lose their homes. Messianic CEOs don’t much care. Nor do activist investors, or even shareholders. I see this daily as people I know and meet in the industry no longer ask about the industry, but ask me if I know where they can find a job. www.embedded-computing.com

The changes coming won’t stay dismal forever. Through this consolidation you will see greater divisions between design and fabrication (Micrel had the last Silicon Valley silicon plant – so expect all manufacturing to go elsewhere). Those fabs will have the mission of scale to serve a few billion consumers and the nascent Internet of Things (IoT) markets. Design will become uniquely divorced from fabrication, splitting the market risk. Design firms will survive best by innovation, and fabs through ruthless efficiency. The question is now, “What comes next?” There will inevitably be new markets and devices that will drive a new growth spurt. The IoT is the sleeping giant, but I doubt the only one snoozing. Raymond D. “Ray” Zinn is an inventor, entrepreneur, and the longest serving CEO of a publicly traded company in Silicon Valley. He is best known for creating and selling the first wafer stepper (an industry standard piece of semiconductor manufacturing equipment), and for co-founding semiconductor company Micrel (acquired by Microchip in 2015), which provided essential components for smartphones, consumer electronics, and enterprise networks. He served as Chief Executive Officer, Chairman of the Board of Directors, and President from Micrel’s inception in 1978 until his retirement in August 2015. Zinn’s philosophy on people, servant leadership, humanistic management, and the ethics of corporate culture are credited with Micrel’s nearly unbroken profitability. Zinn also holds over 20 patents for semiconductor design. A proud great-grandfather, he is actively retired and mentoring entrepreneurs. His new book, Tough Things First (McGraw Hill), is available at ToughThingsFirst.com, Amazon and other fine booksellers. Ray Zinn  ToughThingsFirst.com @Ray_Zinn_ www.linkedin.com/in/rayzinn

 

15 

Test, Verification, and Analysis Tools

Hardware emulation to debug embedded system software By Dr. Lauro Rizzatti

In today’s competitive landscape, getting complex electronic devices rich in embedded software to market faster while making them cheaper and more reliable is a very risky proposition. Not thoroughly testing hardware designs inexorably lead to respins, increasing design costs and lengthening delivery of the netlist to the layout process, and ultimately delaying the time-to-market target with devastating effects on the revenue stream. Even more dramatic outcomes of missing market windows hide in late testing of embedded software. It’s no surprise that the verification portion of the project cycle takes a disproportionately large amount of the schedule. That’s because tracking and eliminating bugs is no small feat, especially when the software content of a system on chip (SoC) is growing at a rate of approximately 200 percent per year. By contrast, the growth of the hardware portion of the design is only about 50 percent.

Hardware emulation as the foundation of system verification While virtual prototyping and field-programmable gate array (FPGA) prototyping have gained attention for early embedded software testing, they cannot help with the integration of software and hardware. The former lacks the hardware accuracy required for tracking hardware bugs. The latter provides limited hardware debugging capabilities necessary to quickly zoom in on a bug.

 16

Embedded Computing Design | February 2016

In the past, if there was a hardware problem once the design was taped out to silicon, the software developer had to work out how to code around it, if at all possible. By validating the software before the SoC is complete, the design team has the opportunity to fix hardware issues before they’re set in silicon. As already stated, emulation checks to make sure the embedded software is running on the supporting hardware according to the specification. Software debug had been done in the past using a variety of debug engines. With one per core, they took advantage of hardware features that provided visibility into and control over the inner workings of a processor. While some debug capabilities were offered, the ability to diagnose Hardware emulation can handle designs of more than one billion ASIC gates and process issues was limited by the kind of access Figure 1 billions of verification cycles at high rates of speed, which makes it an ideal verification tool that the processor provided. Moreover, for embedded software. because traditional software debug typically happened on the actual system, softAs a result, development teams and project managers have ware developers were executing real code on real hardware turned to hardware emulation as the foundation for their veriat target system speeds. This allowed them to work quickly fication strategy. Emulation is a versatile verification tool with through large volumes of code to find the errant routine. many associated benefits, including hardware/software co-verification, or the ability to test the integration of hardware and These traditional techniques broke down when debugging software. Software developers have taken notice because it is an SoC. Because there is no real hardware, the code cannot the only verification tool able to ensure that the embedded system software works properly with the underling hardware. It’s noteworthy, as well, for hardware engineers working to debug a complex SoC design since it can trace a software bug into the hardware or a hardware bug within the software’s behavior. Other benefits include its fast compilation capabilities, another plus for software verification, thorough design debugging and scalability to accommodate designs that encompass more than one billion application-specific integrated circuit (ASIC) gates. Additionally, it can process billions of verification cycles at high rates of speed mandatory to validate embedded software and perform system validation (Figure 1). In the past, hardware debug and testing was the sole reason for the verification portion of the project cycle, something managed by logic simulation driven by hardware description language (HDL) testbenches. Traditional big-box emulation was employed solely for the largest designs. Formal verification has been adopted by many development teams to supplement simulation, increasing basic coverage and ensuring that corner cases aren’t missed. However, only hardware emulation can complete the entire verification task for SoC designs within a practical timeframe and alleviate the runtime problems associated with event-based simulation.

It’s all about the software content An SoC’s software content makes co-verification an all-important part of the verification strategy because it confirms that the hardware and software parts of an embedded SoC are verified concurrently and interact correctly before committing to silicon. www.embedded-computing.com

17 

SoftwaRE

Test, Verification and Analysis Tools high-level abstraction model of a peripheral function or protocol. Transactors, often provided as off-the-shelf IP, are available for a variety of different protocols. A typical catalog includes PCIe, USB, FireWire, Ethernet, Digital Video, RGB, HDMI, I2C, UART, and JTAG components.

Better verification for more complex systems Previously, hardware design was indepenSoC is loaded with peripherals and protocols that need to be fully verified. Hardware emulation uses dent from the creFigure 2 Today’s transactors to fully test that these components work as intended. ation of the software to be executed on be executed at true system speed. can be finished in as quickly as 15 minthose chips. That’s no longer the case. Supposedly, hardware can be simulated utes, depending on the actual speed As SoCs double in number of procesas the code is executed and all of the being run. Hardware emulation prosors and incorporate twice the software hardware visibility would be provided by vides similar control and visibility to content with each product generation, the simulator. The problem is speed – it’s that of a hardware debugger with both concerns about software becomes a pria slow way to debug code. breakpoints and waveforms. ority for development teams and project managers. Now, an SoC isn’t complete For example, if an SoC is designed to Confirming an SoC design will until the development team has proven run programs over Linux, the software work as intended that the intended software works on the developer would have to complete the Hardware emulation differentiates hardware platform. Linux boot with billions of clock cycles itself from other verification tools with before the software can begin executing. its high performance – an increasingly An SoC is a full-fledged embedded The rough estimate is that it would take important requirement driven by softsystem and needs hardware emulation more than 28 years using typical simuware requirements. It is able to confirm to verify it works correctly. With hardlation speeds of about 10 hertz (Hz) to that an SoC design will work as planned ware emulation, development teams complete a Linux boot. and is suitable for handling complex can plan more strategically and impledesigns that can be as large as one ment a debugging approach based on Regardless of whether it’s hardware or billion ASIC-equivalent gates and conmultiple abstraction levels. They can software being debugged, traditional sume more than one trillion verification track concurrently a bug between the hardware and software debug tools cycles per month. Even so, thorough hardware and embedded software to don’t know anything about the other. and exhaustive functional verification identify where the problem lies. In the With large and complex SoC designs, using hardware emulation at this stage process, they are saving time in a costit’s inefficient for two types of debug to continues to be the most cost-effective effective and efficient manner, dramatibe done independently in an attempt to and effective debugging approach cally reducing the risk of missing the locate a problem. available (Figure 2). market window. Allowing the two to work together is the ideal scenario and this is where emulation saves the day. The SoC hardware is implemented in hardware, typically an FPGA or some other programmable element, giving it a higher speed. With this setup, the Linux boot

 18

The introduction of transaction-level modeling (TLM) and availability of transactors can turn hardware emulation into a virtual platform test environment for a range of vertical markets. A transactor, part of verification intellectual property (IP) portfolio, is a

Dr. Lauro Rizzatti is a verification consultant and industry expert on hardware emulation. Previously, Dr. Rizzatti held positions in management, product marketing, technical marketing, and engineering.

Embedded Computing Design | February 2016

Test, Verification, and Analysis Tools

Formal verification going mainstream for SoC block verification By David Kelf

The use of formal verification technology as a mainstream technique for system-on-chip (SoC) designs is, at last, becoming a recognized approach to combat the verification gap. A recent survey suggests that formal assertion-based verification (ABV) is now used on 26 percent of chip design projects. However, the promise of this alternative approach to classic simulation has taken many years to bear fruit, and still only advanced verification environments incorporate it. Why is this and what can we learn from its use so far to make it available to the SoC engineering community at large? SoC block verification hitting a wall Since their inception, SoC devices have presented a verification nightmare to development teams. While the verification of a complete SoC is now a task best left to emulation and rapid prototyping systems, even the larger blocks on these devices have outgrown simulationonly environments. The advent of emulation, everfaster simulators, verification intellectual property (VIP) for key tests, and the Universal Verification Methodology (UVM) have all helped to mitigate this. Still, the verification requirement exceeds available processing time in simulationbased environments. Formal verification has helped to improve block verification through the use of automated “apps” that target specific needs, which otherwise require significant simulation effort. www.embedded-computing.com

Checking the correct operation of standard communication protocols, ensuring key connections and register operation, analyzing correct startup sequences on

domain resets, and many other tasks are now handled by these solutions. However, we have just begun to tap into the true power of formal verification. Many of its usage issues have been eliminated leaving us at the forefront of what may be an entirely new era in verification, as this technology is deployed for hardcore verification.

Formal verification: If it’s so good, where is it today? First, a quick review of formal verification technology, why it has the potential to create this fundamental shift, and what is stopping it today. Hardware simulation works by cycling a block of hardware description language (HDL) code through a serial sequence of meaningful states to demonstrate its operation. This state sequence is driven by input stimulus (an HDL description

19 

SoftwaRE

Test, Verification and Analysis Tools ABV application There are two common methods that ABV is applied during the verification process. The first is to check for specific, corner case style issues, usually of a nature that would otherwise require a significant effort to build a simulation testbench for the problem to be analyzed. The second is the more general checking of a block, either in conjunction with simulation or standalone.

The first use model for formal verification is valuable and can shave a reasonable percentage off the verification schedule. A combined simulation and formal verification flow would include simulation for analysis and an impression Figure 1 of how the design will behave and perform. The second model has the potential to alter the characteristic verification process, saving sigof a set of events on the input of the The real power of formal verification is nificant time and resource expenditure, device) designed to explore the right exercised when engineers ask the queswhile increasing the overall potential states to identify operational issues. tions themselves. This requires the questo discover every bug in the design. tions, or properties, to be written using Already some industry segments are This approach begs the question: If we assertions and applied to the design in a using ABV in this second mode extenknow all the states a code block can get process known as assertion-based verifisively. These include automotive and into and the inter-state transitions, then cation or ABV. aeronautical electronics where high can’t we simply ask questions about quality and reliability is a factor. the code operation to ensure it is corOf course, this high-level description rect? This would avoid having to write masks the issues with ABV, including the In a combined simulation-formal verimany lines of stimulus to try and get the capacity and performance requirements fication flow, as shown in Figure 1, it code block into the correct, informationof a tool that stores this much informais common to use simulation for genbearing states. This is the approach used tion are already being solved with the eral operational analysis and to “get by formal verification tools. latest technologies. a feel” for the design’s behavior and performance. In addition, there are This basic approach can be morphed Two issues remain as barriers for the some functions where simulation is into a number of useful applications. For widespread use of ABV: more appropriate, such as matheexample, if the questions to be asked matical data processing or signal procan be created automatically based 1. The authoring of assertions, often cessing. However, formal verification is on an aspect of the design code and using the SystemVerilog standard well suited to functions of a control or a verification scenario to be checked, syntax, can be complex and difficult data transport variety like finite state then an automated app for a verification to visualize machines, data communication, and purpose can be created. This would not 2. The understanding of verification protocol checks. In addition, ensuring require the user to write the question. If progress, or coverage, is difficult to certain kinds of verification scenarios, the formal tool can demonstrate specific comprehend and collate with that of such as Safety Checks (e.g. can a cersequences of states (a state machine other verification methods tain activity ever happen), is also a operation, for instance) with minimal Although improvements have been made sweet spot for this technology. These input, then a design engineer can in both of these areas, more is required code and scenario examples commonly understand how his or her code might to lower the learning curve, allowing the require a high proportion of the verifiexecute, revealing possible mistakes. general proliferation of ABV. cation resource.

 20

Embedded Computing Design | February 2016

Assertion authoring improvements In the same way that UVM drove a layered approach to simulation testbench creation, new techniques are emerging that introduce abstraction into assertion authoring. These abstractions reduce the complexity by masking assertion detail, while allowing the engineers to think about the verification task rather than individual characteristics of the assertions. For example, OneSpin Solution’s Operational Assertions is a SystemVerilog library that allows formal tests to be represented in a transactional timing diagram-like manner, not unlike high-level UVM sequences, widely recognized by verification engineers. Breker Verification Systems’ graph-based test sequences, now under consideration by the Accellera Portable Stimulus standards committee, is another abstraction form that could also be applied to assertion authoring. These techniques, while easing the application of formal tests, have the advantage of providing a recognizable and more natural input scheme, allowing engineers to relate to the verification process underway by eliminating some of the formal verification mystery.

Common coverage models Simplifying assertions is just one part of the puzzle. At the other end of the process is the collation of coverage information from various sources to understand overall verification progress regardless of the tools used. Simulation progress still is primarily focused on code coverage of one sort or another, with some functional coverage thrown in. Formal verification coverage focuses on assertions (so called “Assertion Coverage”), whether they were executed, did they pass or fail, or did they pass with a caveat (e.g., a bounded proof such as “the code passes within a set number of clock cycles”). This information may be fed back to a verification planning system to provide some useful data. However, measuring formal coverage, where the actual code tested by specific assertions is identified, is an area of interest to leading formal verification vendors. Schemes have been proposed www.embedded-computing.com

that vary both in terms of precision and execution resources required. The key is the ability to compare these formal models with that of simulation to provide a combined, meaningful coverage assessment. The Accellera Unified Coverage Interoperability Standard (UCIS) committee is focused on this goal and has proposed methods by which the two may be compared. More work is required in this area, but it is clear that several of the formal verification vendors have solutions that allow a reasonable metric of progress to be calculated.

Simulation style debug The debug of formal verification code in a manner that is meaningful to a simulation-centric engineer has, to a large extent, been solved by many of he formal verification vendors. Most tools can output a “witness” in the event of an assertion failure. That is, a sequence of events in the form of a simulation waveform that led to the assertion failure. Indeed, some of the vendors, including OneSpin, can output simulation tests that allow the failure to be reproduced in the simulator for further study.

Cracking the code of mainstream ABV It is clear that the use of ABV is starting to become mainstream. In recent papers, both ARM and Oracle declared the full power of ABV in their environments and noted that it was now being used at a significant level on their projects. Solving the three legged stool of Assertion Authoring, Collated Coverage and Simulation-centric Debug, and combining it with a clear understanding of the design areas and scenarios where formal verification excels will propel this approach into the mainstream of SoC verification. Once this happens, it will have a dramatic impact on future design quality and development schedules. David Kelf is Vice President Marketing at OneSpin Solutions. OneSpin Solutions  www.onespin.com @OneSpinSolution www.linkedin.com/company/ onespin-solutions

 

SMX RTOS is IoT Ready. ®

SMX has what you need to connect to the IoT. • smxWiFi 802.11 a/b/g/i/n Wi-Fi stack with P2P, WSC, SoftAP • MediaTek/Ralink USB chipset drivers • TCP/IP: IPv6, mDNS, SNMPv3, SNTP, Web, and many more protocols

mdi_iot_ad_ECD.indd 1

Y O U R

R T O S

P A R T N E R

• Security: SSL/SSH, SNMPv3, WPA2 Personal & Enterprise • smxUSBH USB host for Wi-Fi dongles • smx multitasking kernel • Full source code – No royalty

www.smxrtos.com/iot 21 

10/8/14 1:20 PM

Connecting to the Cloud

Maximizing cloud value with strategy before connectivity By Catherine Ter Horst

Connected embedded systems are all about the data – enabling information access now, or fueling analytics in the future. Addressing the right questions will help uncover a manageable path to connectivity, enabling cloud efficiencies where they make sense today and keeping business poised for inevitable evolution. Connecting edge devices to the cloud is technically something most of us do every day, yet connectivity itself is not the end-all for adding cloud value to the enterprise. Connectivity allows for gathering and accessing business data in a timely and actionable way, but does not consider strategic use or analytics of the data. And without focusing on data as the end game, transitioning operations and applications to the cloud can create enough uncertainty to roadblock a company daunted by the immense impact on business technology, equipment, operations, personnel, and even company culture. Rather than connecting to just be connected, the process must entail a deep understanding of a longterm business strategy and a smart approach to what goes in the cloud and why. Addressing the right questions will help uncover a manageable path – it’s typically not a quantum leap, but rather incremental steps that consider cost, performance, storage, security, and scalability as flexible, individualized options.

Onsite or outsourced? Considering a hardware investment or an infrastructure investment is often the strongest starting point for determining a cloud strategy, it can be eye opening in terms of altering a company perspective towards outsourcing. For instance, the cost of deploying a new upgraded application in a cloud facility could compare favorably against migration costs related to traditional infrastructure investments.

 22

Onsite systems require not only capital expenditure for the systems themselves, but also ongoing resources devoted to their care and feeding. Power, physical space, timely maintenance, planning for obsolescence and procuring trained technical staff all add expense. This can increase with company growth when tied to rapid expansion or a spike in customer activity fueled by a new product or service. Cloud strategies reduce this challenge by taking on many of the complex backend processes that can consume an internal IT department. Highly trained technical staff and extensive hardware and software expertise are part of the service, reducing the need to procure or sustain such talents in-house. Overall, capital expenditures change to operating expenditures, adding value in delivery of services rather than longterm, multi-million dollar purchases of hard goods. How fast and how often must data be accessed? Accessing information quickly can make a difference in how a business operates, how a customer is served, or how a patient is treated. Medical imaging is a prime example, representing data that is not necessarily accessed 24/7, but could be required urgently in a medical application where a diagnosis relies on the information. Data-on-demand is redefining the standard of care, driving healthcare

providers and their technology specialists to develop strategies for supporting doctors who may be accessing data from non-traditional environments. Partnerships or multiple cloud vendors can ensure fast, efficient data access. For instance, even though a larger medical device manufacturer may already have a data center or cloud solution, partnering with a regional cloud hosting vendor would address latency and bandwidth challenges by offering point-to-point connectivity to local/regional healthcare end-users. Connectivity remains seamless, no major infrastructure changes are required in the existing datacenter, yet service improves with quicker response time and lower latency. Using the training and simulation industry as an alternate example, cloud connectivity may not yet be ideal for an application with high determinism and low latency – yet the industry must capitalize on strategies to reduce costs, improve services, and enhance performance by streamlining data access. These future business strategies are integral to how hardware and software assets are tracked, and can also help OEMs become more strategic in overall maintenance, management, and product planning. For example, the cloud can act as a storehouse for training manuals, curriculums, and other types of technical information that helps drive the training experience. Data becomes a

Embedded Computing Design | February 2016

Figure 1

Cloud technologies add value in training and simulation applications, centralizing technology to benefit system performance. Options include a centralized data repository used to store, manage, and simplify access to training information, and secure remote capabilities for effective management and tracking of assets.

a cloud vendor’s data center designed to handle a specific company’s workload. With services and infrastructure maintained on a private network, private clouds provide the greatest level of security and control, yet they are more costly because the user purchases and maintains all software, hardware, and in the case of being inside the company firewall, infrastructure as well. This option is ideal for businesses that are driven by data and applications, or must conform to strict security and data privacy requirements. Cloud vendors may already be compliant with complex and costly requirements such as ISO, Service Organizational Controls (SOCs), and HIPAA, enabling manufacturers to capitalize on specific markets rather than compliance processes themselves.

In contrast, public clouds are a “multi-tenant environment,” where users share their portion of a server with other clients or tenants. Services and infrastructure are provided offsite via Internet connectivity, offering efficiency in shared resources. Public clouds are ideal for companies using secure third-party Softwareas-a-Service (SaaS) applications, or managing workloads for applications such as email. Public, private, or hybrid options cover the bases for cloud connectivity, with most users opting for hybrid A public cloud user may want Figure 2 strategies that encompass secure data, legacy applications on- and off-site, and services tailored for different markets. to develop and test their own application code, collaborate secure, encoded video stream with fully Is data secure and industrywith other entities on specific projects, rendered images sent wirelessly to a compliant while being stored as or add incremental capacity for peak trainee’s personal device. Other advanwell as used? service times. tages include streamlining hardware Determining performance needs, along resources, networking data repositories, with an evaluation of the type of data Hybrid clouds are the most complex and and monitoring, managing, and tracking being gathered, stored, and accessed, varied, coordinating a number of public training assets remotely. helps define the ideal type of cloud conand private options from multiple pronectivity. Comparing public, private, and viders and delivering services and infraEnabling new or enhanced services hybrid clouds must include a look at the structure both onsite and via Internet is another consideration. The cloud different levels of security and manageconnectivity. While hybrid environments enables OEMs to remotely monitor ment required. offer the most overall efficiency, they and manage their systems, such as require management of multiple platsoftware updates and proactive mainA private cloud is a highly virtualized forms to ensure all aspects of the busitenance, improving uptime and cusdatacenter located safely inside a comness can communicate. A company using tomer satisfaction. pany’s firewall, or a private space within a SaaS application but concerned about www.embedded-computing.com

23 

Strategies

Connecting to the Cloud architect. This individual has a deep understanding of a company’s current and future data usage and storage needs, and can design a complete infrastructure that is securely built to address high performance and bandwidth latency.

Fostering cloud strategy The flexibility inherent to cloud technologies can enable a company-wide shift in perspective, changing the conversation about how to handle growth. To determine an ideal path, OEMs Choices depend on the desired level of control. Greater end-user control equals greater responsibility and the need must answer a full for more internal resources on-site; greater outsourcing capitalizes on the overall cloud value proposition in terms of Figure 3 reducing operating expenses, accessing specific hardware, and software expertise, and quickly increasing scalability slate of questions for of services. end-users, addressing costs, performance, security could use a private cloud inside more options, such as scalable storage storage, security, scalability, and even their firewall to host the application and to handle large datasets and fully reduncultural challenges that result from busiadd a virtual private network (VPN) for dant, replicated, and secure systems. ness transformation. increased security. Another company may handle their customer interactions Adapting organizations for the While recognizing the need for data is via a public cloud while company data is future essential, the key to making it happen hosted privately. Organizations are becoming more comis to find incremental ways to embrace plex; the type of employees that are cloud efficiencies rather than just conAre you prepared to handle needed to run them are required to nectivity. Cloud technology partnerships Big Data as a long-term asset? have peripheral vision to see beyond add value by simplifying the strategy Big Data is a rising business considerwhat is considered their normal scope and respecting the level of control a ation, and its anticipated growth will of responsibilities. They need to be business wants to outsource or maintain compound the challenge for existing more proactive and creative in how they internally. Most importantly, cloud effiIT resources. Because trends and issues find and resolve issues. With the shift ciencies for one customer may not make are revealed by executing analytics and to greater connectivity, they will have sense for another – it’s not a one-sizeevaluating information over time, data a greater focus on identifying issues to fits-all proposition to either embrace or must be properly gathered, stored, and drive new opportunities, and will use not. Focus on the end game of getting protected. It is the payoff for connected those opportunities to generate new access to data for the long term, driving embedded systems, and planning for it revenue. Instead of monitoring equipnew revenue and creating a pace of now assures its long-term strategic value ment and managing day-to-day requirechange that makes sense today and for as a business asset. ments for keeping operations at peak the future. performance, key staff members are When a large onsite server was the core focused on designing an infrastructure Catherine Ter Horst is Senior Product storage tool, the only reasonable growth to drive and optimize Big Data analytics Manager for IoT at Dedicated path was to purchase another server. – ultimately helping derive meaningful Computing. Increased load on the IT team was business insights and improve results part of the natural progression, as well across the organization. Dedicated Computing as more integration, operating costs,  www.dedicatedcomputing.com power, and maintenance. Today, the For example, the role of an infrastructure opsy.st/DedicatedLinkedIn cloud alternative offers more space and architect is becoming a solutions



 24

Embedded Computing Design | February 2016

Connecting to the Cloud

Evaluating Bluetooth Smart – What IoT developers need to know about getting connected By Mark Bowyer

This article serves as an initial guideline to help those with little-to-no RF or Bluetooth expertise get started on Internet of Things (IoT) designs and get to market quickly.

The IoT landscape continues to grow at a rapid pace. Between fitness and activity trackers, smart watches, connected cars, and more, the consumer-driven desire to utilize a vast variety of sensors within devices and gadgets to retrieve measurable data is at an all-time high. The challenge for IoT will be mass-market enablement and creating accessibility to IoT through easy-touse, easy-to-deploy wireless technology and sophisticated sensors that can drive computational resources to the device. This approach may reduce the heavy lifting otherwise delegated to the cloud and can thereby create more power efficient solutions that offer world-class performance and environment/use case accuracy. Original equipment manufacturers (OEMs) looking to make their way into the IoT need to consider several factors, including their design philosophy. Entering the consumer IoT market space typically drives design toward a balance of simple, intuitive setup and operation with increased battery lifespan, while decreasing power, cost, and form factor. In order to meet these needs, the right communication technology should be selected from the start. Bluetooth Low Energy (BLE or Bluetooth Smart to many) can be a snap to use. When the Bluetooth SIG announced the www.embedded-computing.com

formal adoption of Bluetooth Core Specification version 4.0, it included the Bluetooth Smart (low energy) feature giving developers an easy and efficient way to enable Internet connectivity for embedded devices through BLE-enabled platforms like mobile phones and tablets (Figure 1). A slew of accelerometers; magnetometers; IR temperature, hall-effect, position, radar, and light sensors; and hundreds of other devices can now be enabled quickly and deployed as Internet-connected “things.” Nevertheless, developers should be aware that there are several project-level challenges when it comes to creating an Internet of Things (IoT)-enabled product. Understanding the challenges before beginning a project can save time, effort, and money, and being versed in the emerging application development solutions and ecosystems deployed by device and module providers can benefit developers as well. Most importantly, keeping in mind that “ease of use” is the predominant driver of integration with previously “tethered” solutions is critical to a successful device.

Choosing the right wireless technology As stated, choosing a technology to enable connectivity for IoT devices is key. As consumer IoT products progressively get smaller and more convenient for portability, mobility, and

25 

Strategies

Connecting to the Cloud

longer battery life, circuitry for direct Internet connectivity is sacrificed. But, smartphones and tablets allow external devices to connect and send data to the Internet by acting as a gateway through their own means of connectivity. This makes phones and tablets ideal candidates for developers seeking to connect sensorbased embedded devices to the Internet. The list of available wireless connectivity options for external devices to smartphones and tablets can be narrowed to Wi-Fi, Bluetooth, and near-field communication (NFC), with the characteristics of each listed in Figure 2. Classic Bluetooth and Wi-Fi are known to steadily drain battery life as they operate based on the application and use case, hence such protocols may be Figure better suited for streaming and high-data rate applications instead of sending small bursts of data packets. By comparison, BLE’s power consumption is very low thanks to the nature of its data exchange. Determining which method of wireless connectivity your product should use depends on the application needs. In most circumstances, IoT devices fit within the same set of principles for design: enabling connectivity while maintaining good battery life, being small and lightweight, and keeping costs low. BLE has Figure therefore found itself a niche within IoT devices due to a few distinguishing factors that address these very needs:

õõ

Many IoT devices are driven by short-range communication. BLE operates under the lowest possible power consumption within low ranges, which is ideal for such communication. IoT devices are typically in edge device roles, aiding to lower their power consumption. Devices

 26

Bluetooth Low Energy (BLE) is being deployed in countless applications in virtually every field - with new applications arriving almost on a daily basis.

Wi-Fi, Bluetooth, and near-field communication (NFC) are the most common wireless connectivity options available to design engineers. Listed here are some of their basic characteristics.

õõ

in central roles — usually the smartphone or tablet itself — are subject to slightly higher power consumption due to their continuous scanning nature and number of devices connecting to them. BLE’s low power consumption attributes directly to the size a device can be. BLE-enabled devices can often operate on only a coin-cell. This contributes to reduced overall size, weight, and cost of such devices.

õõ

BLE maintains a low data rate and exchanges small packets of information over extended intervals. This is great for devices sending short bits of data infrequently, as it can maximize the time spent idle while in low power mode. BLE is optimized to minimize the time between connection and data exchange to within a few milliseconds, with a typical connection and tear-off cycle only

Embedded Computing Design | February 2016

Figure 3

õõ

The Atmosphere cloud- and-web-based integrated development environment (IDE) allows users to easily create and build applications using drag-anddrop elements. The application for a mobile device and the firmware for the connected hardware are created simultaneously.

lasting around 6 ms. The protocol then severs the connection and returns to idle mode. This is key for devices that send data. Many BLE-enabled devices are natively compatible with mobile operating systems. This makes them great for use with most smartphones and tablets

Each of the connectivity options has its benefits, though, so choosing one over the other is application-specific. While Bluetooth does not provide the data rate and speed of Wi-Fi, it offers a better power-to-battery life ratio. NFC devices offer the lowest power consumption but are range-limited. Additionally, Bluetoothenabled devices can be paired to smartphones and tablets easily to create an ad hoc network with access to the Internet. In light of the methods outlined above, BLE appears to stand out as the most viable standard to enable IoT connectivity for embedded devices by using a mobile device as a gateway.

Getting started with development With a basic understanding of BLE under our belt, let’s consider application www.embedded-computing.com

development. There’s much to choose from when starting the process as there are numerous development tools available to assist in app creation and custom design. Platforms such as App Inventor, Appcelerator, Atmosphere, MoSync, Phonegap, and others allow easy development of mobile apps that can be customized for embedded solutions and tested across multiple platforms. Users with little-to-no RF or BLE expertise will find the Atmosphere development platform particularly intriguing (Figure 3). With it, developers can create embedded device firmware and mobile apps simultaneously using a web-based drag and drop tool. Further, Atmosphere provides a library of sensors that can be incorporated into designs without coding. Atmosphere uses a variety of “elements” to help create a project easily. Elements are blocks of pre-made code that perform various functions and can also represent sensors when added into a project, allowing users to easily create a project without understanding programming languages or coding. Whenever an element is placed in the user interface, it automatically creates code for both the mobile app (which can

be designed and modified at will) and the embedded system. Elements can be connected in countless ways to utilize a variety of sensors and expand the functionality of a project.

Tools and tech to get started Among all wireless standards, the gadget-oriented Bluetooth has become a mainstay of personal device interconnectivity, and with BLE we are about to see exponential growth in the emerging IoT space. Developers can greatly accelerate time to market by choosing the right wireless technology, tools, and software to connect their sensor-based embedded devices to the Internet. Mark Bowyer is Director of Business Development for Anaren’s Wireless business unit, where he leads and deploys the company’s strategy for the Internet of Things. Anaren  www.anaren.com  air@anaren.com @AnarenInc linkedin.com/company/anaren  opsy.st/AnarenYouTube

 

27 

Connecting to the Cloud

Embedded device security for the IoT By Mike Rohrmoser

When it comes to security for the Internet of Things (IoT), the sum of the parts may be lesser than the whole.

As more devices become networkenabled, public or private, there’s an increasing concern around the security profile of those devices. There’s been a fair amount of discussion regarding the concepts of “security by design” and “defense in depth,” and in these areas components can represent either a gaping hole or another line of defense. Ultimately, the security of any device is dependent on its components — any connected device is only as secure as its hardware and software building blocks — and if those components aren’t part of a secure system architecture, they almost certainly can invite unauthorized access and use. Let’s take look at some of the recent vulnerabilities that were exposed in devices in both consumer and non-consumer industrial applications:

õõ

In July 2015, security researchers demonstrated how they could wreak havoc with a Jeep Grand Cherokee’s

 28

õõ

systems by disabling brakes or manipulating the transmission, despite the driver’s actions. The exploit was based on a vulnerable component in the carmaker’s Uconnect vehicle connectivity system, enabling hackers to connect through the cellular connection as long as the vehicle’s IP address is known. After that, the firmware in the vehicle’s entertainment system was replaced with a version incorporating malicious code that allowed access to the vehicle’s internal CAN bus system. All this led to a recall of about 1.4 million vehicles by Fiat Chrysler. In the Summer of 2015, it was reported that three hospitals suffered data breaches after some of their medical devices, ranging from blood gas analyzers to radiology and X-ray equipment, had been infected with malware, allowing hackers to access sensitive patient data. Not to mention the widely publicized case of a popular

õõ

IV pump model being vulnerable to relatively unprotected malicious firmware updates through its external serial port, granting access to dosage control and other key operational aspects. At the USENIX Security Symposium 2015, a group of researchers claimed that it’s possible to wirelessly hack into vehicles equipped with cellular-enabled dongles that track location, speed, and efficiency. These devices are simply plugged into a vehicle’s standard OBD-II port and are commonly used by insurance companies and commercial trucking fleet operators to gather information on driving habits or manage vehicle and delivery logistics. In late 2015, multiple security vulnerabilities related to connected cameras, ranging from video baby monitors to public CCTV systems, were published, exposing them to brute-force dictionary attacks by working through a list of likely

Embedded Computing Design | February 2016

passwords, including default or “hidden” passwords, due to their weak traditional user/password authentication. There are countless other similar examples, and many of these attacks mark a departure from the usual methods that target network security vulnerabilities and signify that, in addition to firewall-based perimeter defenses and network security controls, the embedded devices and their components must be locked down.

Secure connections aren’t enough With more and more devices joining the IoT on a daily basis, these issues are amplifying already existing concerns, making it a vital requirement that connected devices (both legacy and new) are adequately covering device identity and device integrity aspects, as well as connection security. The previous examples cover almost the entire gamut of embedded device security issues – issues that could have been addressed with certificate-based implementations of firmware updates, user authentication, and encrypted storage. Additional use of hardwarebased capabilities, including tamper detection and locking down backdoors, such as the ubiquitous JTAG interface, provide another proactive layer against local attacks. Any connected device represents a potentially vulnerable access point to hackers seeking to either control or disable a device, or to find an access point to proprietary data or networks. In fact, the issue of security in a connected world was recently addressed in a Federal Trade Commission report and an FBI Public Service Announcement regarding the IoT that recognized the rapid growth of connected devices and their benefits, but also cited risks that could seriously undermine those benefits.[1,2] The old-fashioned concept “security by obscurity” for embedded devices, if it was ever really valid to begin with, is no longer sufficient in today’s connected world. A vast number of IoT devices are, by definition, embedded devices, and especially in non-consumer applications require a device security approach that also supports their often-long product www.embedded-computing.com

lifecycles of seven-to-ten years or more. What’s needed is a comprehensive Embedded Device Security System Architecture that’s suited to follow the security trends and threats throughout a device’s lifespan.

Device-level security measures Apart from including key security technologies and measures for connected devices when considering system architecture and design, a securityby-design strategy must be adopted at the embedded component level to effectively block potential pathways that could permit unauthorized access or control of connected devices and/or data. Key recommendations include:

õõ

Design and build to a Device Security System Architecture that meets current and future requirements, including building products with appropriate “headroom” for future extensions (performance, memory, connectivity, and hardware support) to ensure that products will stand the test of time. Leveraging appropriate training and tools, ranging from security coding techniques to properly and fully assessing the risks of system designs holistically. It’s crucial to invest in and maintain up-to-date tools such as source code analyzers that can scan for vulnerabilities and test suites to perform network security vulnerabilities analysis. Securing data connections is key, but the need for device security extends to an integrated system concept with encrypted local data storage, digitally-signed firmware, certificate-based authentication, a proper certificate management strategy, locking down debug ports such as JTAG for production units, and tamper-proofing against local access to hardware. Lastly and perhaps most importantly, there must be a secure and scalable process that lets the device automatically update itself remotely, or to allow authorized users to update the device locally. This allows manufacturers to quickly and reliably respond to most recent vulnerabilities and continue to enhance their products’ capabilities

in lockstep with the current state of technology. Especially in light of some of the fundamental concerns that current security algorithms could be broken within this decade, there’s a need to include new implementations such as Elliptic Curve Cryptography in future products. Ultimately, the burden falls on manufactures to determine the level of security that’s added to their IoT devices, which capabilities are enabled, what those devices do on their customers’ networks, and which services are open. The benefits of the IoT are undeniable, but its inherent risks need to be addressed and an intelligent security concept must be an integral component of the “things.” Manufacturers should turn to embedded component suppliers that can address those security needs and understand the embedded market and its specific needs, both now and in the future. Manufacturers needn’t assume the entire burden, but they should ensure that the suppliers they work with have the required track record and will be around to support them for years to come. Security issues have the potential to affect not just the end user, but also severely tarnish the device maker’s reputation. Mike Rohrmoser is Director of Product Management for Embedded Systems at Digi International, where he is responsible for the definition and delivery of Digi’s current embedded product solutions offerings and future direction. Digi International @digidotcom  mike.rohrmoser@digi.com opsy.st/DigiLinkedIn  opsy.st/DigiYouTube

 

References 1. “FTC Report on Internet of Things Urges Companies to Adopt Best Practices to Address Consumer Privacy and Security Risks.” Federal Trade Commission. Accessed January 14, 2016. www.ftc.gov/news-events/press-releases/2015/01/ ftc-report-internet-things-urges-companies-adoptbest-practices. 2. “Internet of Things Poses Opportunities for Cyber Crime.” Internet Crime Complaint Center (IC3). Accessed January 14, 2016. www.ic3.gov/ media/2015/150910.aspx.

29 

IoT

Air for WICED Anaren's AIR modules are low-cost, surface-mount radio modules featuring Bluetooth® Smart and Wifi technology. Bluetooth module incorporates the Broadcom ultra-low-power BCM20737 SoC, a 24MHz crystal, an EEPROM, and a choice of integrated or connectorized antenna. All modules are supported by Anaren's exclusive Atmosphere development toolset. Delivered on tape and reel or matrix tray in an all-in-one package that measures only 11x13x2.5mm – the modules eliminate the need to develop a radio from scratch. Even better, they are globally certified and Bluetooth SIG qualified, making it easier than to deploy in the markets important to you. Atmosphere Anaren Atmosphere combines an easy-to-use, drag-and-drop development environment and local programming software that provides an efficient means of building BLE applications. Think. Build. Connect. The Atmosphere IDE is the only platform available thatcan build an app for your mobile device and a program for your embedded system simultaneously. This capabilityallows developers to seamlessly create a mobile user interface that interacts with an embedded system. Think it up, build it up, and connect it all within minutes!Best of all, Atmosphere is currently free to use! As a member of the Atmosphere community, users and developers will have access to a wide range of helpful tools, including the Atmosphere wiki, forum, and video library.

FEATURES ∠

Minimal RF engineering experience necessary

∠

Minimal Bluetooth Smart experience necessary

∠

Easy to implement, short design cycle when used with Anaren’s Atmosphere development tool

∠

No additional “Intentional Radiator” certification required

∠

Minimal real estate required

∠

Only requires a 2 layer Host PCB implementation

∠

No additional harmonic filtering required

∠

100% RF-tested in production

Anaren Atmosphere puts unprecedented wireless development power in the hands of developers of all skill levels.

embedded-computing.com/p373267

Anaren, Inc.

www.anaren.com/airforwiced/

 30

AIR@Anaren.com

linkedin.com/company/anaren

800-411-6596

@anareninc

Embedded Computing Design | February 2016

Industrial

FES9280 – Rugged Embedded Computer for Compact Military Applications Features Newest Intel Skylake 6th Generation Core i7 Military standards compliance in temperature, vibration, and shock, the fully IP67 with dust and water proofing completed with anti-corrosion housing fanless embedded box is complimented with DDR3L 1600MHz 16GB, removable 1-bay 2.5" SSD, and multiple I/O ports. Acnodes Corporation, a leading manufacturer of industrial and embedded computer platforms and technologies, introduced today the launch of FES9280, a fanless embedded PC, powering high-performance military applications with space constraints. Computations will be of acceleration with the newest Intel Skylake 6th Generation Core i7-6600U 2.6GHz. With a wide range temperature, it is complimented with anti-vibration and anti-shock resistance of MIL-STD. These features meet the severe environment operational demands in many industries creating reliability in the multitude of conditions. The fully IP67 rated enclosure provides for complete dust proofing, water immersion durability, and anti-corrosion housing yet maintaining its lightweight capability. FES9280 has 16 GB of DDR3L 1600MHz, as well as a 2.5" SSD in Hot swappable array and a mSATA SSD 64GB cache for system boot. VGA and DVIoutput accepted. It includes multiple optional features such as HDMI, DP output, full size miniPCIe for wireless card IEEE 802.11 a/b/g/n 2x2 Dual Band, and full size miniPCIe for WWAN 3G/4G card integrated. I/O for Signal includes two USB 2.0 interfaces, RS232, RS422, GbE LAN, DVI port, and VGA port. The power input supports DC 9~36V input.

FEATURES ö ö ö ö ö ö ö ö ö ö ö ö ö

Fanless rugged embedded micro box Intel Skylake 6th Generation Core i7-6600U 2.6GHz DDR3L 1066MHz SODIMM 8 GB Memory 1 x mSATA SSD 64GB and 1 bay swappable slot for 1 x 2.5" SATA HDD storage MIL-STD-810F in temperature, vibration, and shock Fully IP67 rated Wide range operating temperature -30°C ~ 65°C (-13°F ~ 158°F) VGA and DVI video input with option for VGA and HDMI 1 LAN, 2 COM, and 2 USB ports DC 9~36V power supply I/O ports includes two USB 2.0, RS232, RS422, GbE LAN 8.56"(W) x 1.77"(H) x 5.83"(D) 8.82 lbs embedded-computing.com/p373134

Acnodes Corporation www.acnodes.com



info@acnodes.com

 linkedin.com/company/acnodes-corporation

 909-597-7588

 @acnodescorp

Hardware

ADLE3800HDC – Intel E3800-Series (Industrial IoT-Ready) 3.5" SBC Come visit the ADL Embedded Solutions booth (#1-554, Hall 1) at the Embedded World Exposition & Conference in Nurnberg, Germany, February 23-25th 2016 to view the latest products and to see multiple live product demos or visit http://ew2016.adl-usa.com. For system pricing, contact ADL Embedded Solutions at 858-490-0597 www.adl-usa.com or email sales@adl-usa.com.

FEATURES ∠ Intel Atom E3845 Quad; E3827 Dual Core ∠ Up to 8GB DDR3L 1333MHz ∠ I/O: 3x GLAN, 4x USB2.0, 1x USB 3.0 (I-PEX conn) ∠ Graphics: DVI-I conn, Optional HDMI or DP (via I-PEX conn) ∠ Storage: 1x SATA (3Gbit/s), 1x M.2 Type B Key 2242 SATA ∠ Expansion: M.2 Key B 2280 with PCIe x1 with Optional

miniPCIe Adapter

∠ -20C to +70C Standard, Optional -40C to +85C embedded-computing.com/p373268

ADL Embedded Solutions www.adl-usa.com

www.embedded-computing.com

sales@adl-usa.com

858-490-0597

31 

Hardware ConnectCore® for i.MX6UL Digi's new ConnectCore® for i.MX6UL module delivers a secure and extremely cost-effective embedded communication module platform in a low-profile form factor slightly bigger than a postage stamp. Its innovative and scalable Digi SMTplus™ surface mount form factor (28x28 mm) supports virtually unlimited design integration and flexibility without the burden of manufacturing complexity. Built as the intelligent and reliable communication engine for today’s secure connected devices, it integrates dual-Ethernet, dual-band Wi-Fi (802.11a/b/g/n/ac), and Bluetooth Smart Ready connectivity options. Security for embedded devices is a critical design aspect and the ever-growing array of connected applications (“IoT”) is further driving the need for a solid and consistent embedded device security story. The 6UL module is tailored to fit the needs of your secure connected product applications out-of-the-box. It fully integrates specialized hardware and software components as part of a complete, secure turnkey Linux development platform solution with a customizable device security approach supporting the long lifecycles of your products. Ultra-low power modes and advanced wake-up state management are through Digi’s unique Kinetis Microcontroller Assist™ with complete software support.

FEATURES ∠ Secure, connected, highly cost-effective system-on-module ∠ NXP i.MX6UL-2, Cortex-A7 @ 528 MHz ∠ Up to 2 GB NAND flash, up to 1 GB DDR3 ∠ Unique ultra-low power and wake-up state management ∠ Easy-to-use, stamp-sized, and flexible SMTplus™ form factor ∠ Integrated dual 10/100 Ethernet connectivity ∠ Pre-certified 802.11a/b/g/n/ac + Bluetooth 4.1 option ∠ Dedicated on-module security + authentication controller ∠ Secure turnkey embedded Linux device software platform ∠ Off-the-shelf SBC and development board platform options embedded-computing.com/p373269

Digi International www.digi.com

embedded@digi.com

linkedin.com/company/digi-international

+49-89-540-428-0

@digidotcom

Networking

PCI Express Network Take advantage of the PCI Express interconnect in your embedded system. PCI Express networking connects multiple processors, FPGAs, GPUs and I/O devices into an intelligent network. Dolphin’s PCI Express Networking solution includes standard hardware components, middleware software, and customized system support for various embedded systems. PLX/Avago and IDT PCIe switches can be used by designers to create new more powerful systems build on a powerful software stack. For high performance applications, Dolphin’s solution supports Gen 3 PCIe performance, which combines 8 Gbit/s per lane performance with latencies as low as 540 nanoseconds. This performance is ideal for reflective memory applications, high speed transfers, and low latency tightly coupled systems. Dolphin’s software suite shortens the time to product with an advanced software suite including a Shared- Memory Cluster Interconnect (SISCI) API as well as a TCP/IP driver and SuperSockets software.

FEATURES ∠ PCIe Gen 3 support with backward compatibility to Gen1and Gen2 PCIe ∠ Complete software development environment including Sockets, TCP/IP,

and shared memory support

∠ VxWorks, Linux, Windows, RTX and RedHawk linux OS support ∠ Cross platform data transfers between Linux, Windows, and VxWorks

through the SISCI API

∠ Reflective memory support through high speed low latency ∠ ∠ ∠ ∠ ∠

switched network FPGA and GPU connections through PCIe Network RDMA support through PIO and DMA Connections through back-planes, copper cables and fiber cables PCIe iPass connectors and cabling support Clock isolation support, CFC or SSC on cable embedded-computing.com/p373270

Dolphin Interconnect Solutions www.dolphinics.com

 32

paraison@dolphinics.com

214-960-9066

Embedded Computing Design | February 2016

Hardware

M-Max ATR-chassis Rugged ATR Conduction-Cooled Enclosure for Housing Conduction-Cooled PC/104 Modules. The M-Max ATR-compliant chassis is a fully sealed rugged enclosure with passive cooling, providing extreme physical protection for high performance systems. The machine-worked aluminum chassis is especially designed for the most challenging environments. The ATR-compliant enclosure excels in critical applications needing to operate under extreme temperatures, dust and humidity. Providing excellent shock and vibration protection, the completely fanless chassis uses natural convection and conduction cooling. Typical systems housed in this ATR-compliant enclosure deliver IP66 dust and moisture protection, withstand shocks up to 10g and vibration up to 2g. The fully sealed enclosure houses up to 8 PC/104 or similar-sized boards. The configurable front panel can be outfitted with variety of customer-defined connectors.

FEATURES ∠ Fully sealed rugged chassis for aircraft, marine and vehicle

applications

∠ Dissipates up to 95W of power, using only passive cooling ∠ Shock handling up to 10g, Vibration up to 2g ∠ Configured to house PC/104, ComExpress and EBX boards

simultaneously

∠ Up to 8 PC/104 or similar-sized boards

Looking forward to seeing you in Hall 2, Stand 451 at Embedded World. embedded-computing.com/p373271

MicroMax Computer Intelligence

info@micromax.com

+1 212-968-1060

linkedin.com/company/micromax-computer-intelligence

www.micromax.com

Operating Systems and Tools

Modern Embedded Systems Programming Embedded software developers are independently re-discovering patterns for building concurrent software that is safer, more responsive and easier to understand than naked threads of a Real-Time Operating System (RTOS). These best practices universally favor non-blocking, asynchronous, event-driven, encapsulated state machines instead of naked, blocking RTOS threads. While these concepts can be implemented manually on top of the “free threading” approach, a better way is to use an active object (actor) framework, which inherently supports and automatically enforces the best practices of concurrent programming. The QP™ family of active object frameworks from Quantum Leaps provides a lightweight, reusable architecture designed specifically for deeply embedded systems. The QP family consists of QP/C, QP/C++, and QP-nano frameworks, which are all strictly quality controlled and thoroughly documented. The frameworks are licensed as GPL open source as well as commercially. The behavior of active objects is specified in QP by means of hierarchical state machines (UML statecharts). The frameworks support manual coding of UML state machines in C or C++ as well as fully automatic code generation by means of the free QM™ graphical modeling tool. All QP frameworks contain a selection of built-in real-time kernels and can run on baremetal microcontrollers, completely replacing a conventional RTOS. Native QP ports and ready-to-use examples are provided for major CPU families, such as ARM Cortex-M. QP/C and QP/C++ frameworks can also be used with many traditional RTOSes and desktop OSes (such as Windows and Linux).

Quantum Leaps, LLC

www.state-machine.com www.embedded-computing.com





FEATURES ĄĄ safer actor-based concurrency ĄĄ hierarchical state machines ĄĄ software tracing ĄĄ graphical modeling ĄĄ automatic code generation

info@state-machine.com www.linkedin.com/company/quantum-leaps

embedded-computing.com/p372195

 919-360-5668 twitter.com/mirosamek



33 

Hardware

Linq/GbE - Rugged Managed Ethernet Switch Box LINQ/GbE is a Rugged Managed Ethernet Switch Box. LINQ/GbE series of products offers 12 or 24 Ethernet ports of 10/100/1000 Mbps. Using the Vitesse switch engine VSC7429, users have access to a wide range of Layer 2+ Switching features including but not limited to VLAN support, IPv4/IPv6 multicast, QoS, link aggregation and more. Management access is available via web interface, software API, SNMP or command line interface which is ideal for remote multi-unit updates. LINQ/GbE is a natural progression to an extensive line of small form factor embedded Managed Ethernet Switches readily available from Connect Tech. LINQ/GbE uses a rugged enclosure design that is rated IP68 using solid Aluminum Alloy construction ideal for harsh high-shock and vibration environments.

FEATURES LINQ/GbE - Feature Highlights ∠ ∠ ∠ ∠ ∠ ∠

12 and 24 Port 10/100/1000 Mbps Managed Switch Box Ruggedized Sealed RJ-45 Acclimate Connector Series IP68 Dust and Waterproof Solid Aluminum Enclosure Layer 2+ Carrier Ethernet Management Low Power Passively Cooled Construction Extended Temperature Range -40°C to +85°C

embedded-computing.com/p373273

Connect Tech

http://bit.ly/1n14INp

sales@connecttech.com

linkedin.com/company/connect-tech-inc

519-836-1291

@connect-tech-inc Hardware

Xtreme/10G, Xtreme/GbE Managed Carrier Ethernet Switch Connect Tech’s expansive line of Xtreme/GbE and Xtreme/10G Managed Carrier Ethernet Switches provide Carrier Grade Ethernet switching capabilities in an extremely small embedded form factor, excellent for high-end applications such as Mobile and Microwave backhaul. NEW! The natural progression of our growing line of Managed Ethernet Switches now includes a small form factor 10GbE Managed Carrier Ethernet Switch. Connect Tech’s Xtreme/10G Managed Ethernet Switch provides high density, high port count Layer 2 switching and Layer 3 routing with 10G uplinks. A total of 36 switchable ports, with 4 x 10G, 8 x 1G (SGMII) and 24 x 1G (Copper 10/100/1000Mbps) ports in an extremely small form factor, 85mm x 85mm. Xtreme/10G targets managed Layer 2 and Layer 3 equipment in SMB, SME, and industrial applications where high port count, 1G switching with 10G aggregation/uplinks are required. Choose RJ-45's, Rugged Positive Locking Headers or our Board to Board connector scheme that connects to readily available break out boards or high speed cables.

FEATURES ∠ 24 x 1G Copper (10/100/1000 Mbps), 8 x 1G (SGMII)

and 4 x 10G uplinks (SFI) 8, 12 or 24 x 10/100/1000 Mbps Port Switch Latest Generation 32-bit Switch Engine Web GUI or CLI Management Carrier Grade Ethernet Switching Air Cooled or Conduction Cooled options Suitable for standalone use or choose from PC/104 compatible footprints ∠ Single Wide Range Input Voltage +9V to 36V or +4V to 14V ∠ Extended Temperature Range -40°C to +85°C ∠ ∠ ∠ ∠ ∠ ∠

embedded-computing.com/p373274

Connect Tech

http://bit.ly/1Q3qY2Z

 34

sales@connecttech.com

linkedin.com/company/connect-tech-inc

519-836-1291

@connect-tech-inc

Embedded Computing Design | February 2016

Hardware

COM Express® + GPU Embedded System The COM Express + GPU Embedded System from Connect Tech combines the latest generation x86 processors with high-end Graphics Processing Units (GPU) all into a ruggedized small form factor embedded system. Choose from the latest Generation Intel® Core™ i7 or i5 x86 processors; and from either the AMD GPU (ideal for driving multiple displays) or the NVIDIA GPU (ideal for CUDA Core processing applications) lineup. This embedded system exposes all of the latest generation interconnect including: Gigabit Ethernet, USB 3.0 and 2.0, DisplayPort++, VGA, LVDS, SATA III, GPIO, I2C, mSATA, miniPCIe, PCIe/104 and SD Card Expansion. This embedded system uses all locking ruggedized positive latching connectors and eases the challenge of cooling multiple processors with the use of our Unified Thermal Extraction Baseplate which can be mounted directly into an enclosure or chassis for further thermal dissipation.

FEATURES ∠ Combines High-End GPUs with Latest Generation x86 Processors in a

ruggedized small form factor

∠ Choose from NVIDIA GeForce GTX 950M or GTX 970M

or AMD E6760 or E8860

∠ GPUs can be targeted for 4 independent display outputs OR for a

headless GPU processing system utilizing CUDA cores

∠ All thermal extraction points from COM Express and GPU are brought

out to a single unified plane

embedded-computing.com/p373275

Connect Tech

http://bit.ly/205iYn5

sales@connecttech.com

linkedin.com/company/connect-tech-inc

519-836-1291

@connect-tech-inc Hardware

COM Express® Type 6 and Type 10 Rugged Carriers Connect Tech’s COM Express® Type 10 Mini Carrier Board is an extremely small carrier board (84mm x 55mm) . This Type 10 Mini Carrier Board is ideal for space constrained applications, harsh environments, demanding conditions, and supports extended temperature ranges of -40°C to +85°C. Choose from on board low profile, locking pin header connectors, or our latest model with board to board connectors, allowing for easy mating to off-the-shelf or custom designed breakout boards. This option dramatically reduces your cabling requirements and allows for the most compact packaging of your system. Connect Tech’s COM Express® Type 6 Carrier Boards are compact carriers that match the dimensions of a COM Express® Basic module (95mm x 125mm) and offer a variety of connector options. Choose from PC-style connectors to easily bring out to the front of a chassis or select options with durable locking pin headers connectors. Our latest offering provides board to board connectors allowing for easy mating to our off-the-shelf or custom designed breakout boards. Both our COM Express Type 10 and Type 6 Carrier board options are designed with a variety of easy expansion methods via Mini PCI Express, M.2, XMC, PMC, or on-board PCIe/104 connectors.

FEATURES COM Express Type 10

∠ Extremely small size, 84mm x 55mm ∠ Choose from Rugged Latching or Board to Board Connectors ∠ 2 x mini PCIe, mSATA, SATA, 2 x GBE, 6 x USB, LVDS,

DisplayPort/HDMI/DVI/VGA, HD Audio, 2 x RS-232/422/485

∠ Support for the latest generation of low powered CPU's ∠ Extended Temperature Range

COM Express Type 6 Choice of PC Style, Rugged Latching or Board to Board connectors Expansion via Mini PCIe, M.2, XMC, PMC or on-board PCIe/104 Small size, 95mm x 125mm Supports the latest Intel Processors Extended Temperature Range

∠ ∠ ∠ ∠ ∠

embedded-computing.com/p373276

Connect Tech

http://bit.ly/1Ki4o2f www.embedded-computing.com

sales@connecttech.com

linkedin.com/company/connect-tech-inc

519-836-1291

@connect-tech-inc 35 

Hardware Hawk (VL-EPU-3310) Ultra Small “Bay Trail” Embedded Computer This next gen Embedded Processing Unit (EPU) format combines processor, memory, video, and system I/O into an extremely compact embedded computer, with a footprint the size of a credit card! The Hawk was engineered to meet the military, avionic, and medical industries’ evolving requirements for smaller, lighter, and more powerful embedded systems. Roughly the size of a credit card and less than one inch thick, it combines the new 4th generation Intel® Atom™ “Bay Trail” processor, with on-board I/O, in a format designed to withstand extreme temperature, impact, and vibration. Hawk is available in single-, dual-, and quad-core models. The quad-core model delivers more than 5X the performance of previous generation products with an 18% reduction in power consumption! The single-core version provides over 2X the performance of the previous generation product, with a 25% reduction in power. The quad-core is ideal for UAV video applications where higher performance and light weight are critical. The Hawk is backed by VersaLogic’s 5-year warranty and product life extension programs that can continue delivery well past the year 2025.

FEATURES ∠ Quad-, dual-, and single-core models ∠ 4th Generation “Bay Trail” processor ∠ -40°C to +85°C operation ∠ Wide input voltage (8V – 17V) ∠ Soldered-on RAM (up to 4 GB) ∠ Soldered-on Flash (up to 8 GB) ∠ Mini PCIe / mSATA expansion socket ∠ Two serial / COM ports; Four USB 2.0 ports ∠ MIL-STD-202G Shock and Vibration embedded-computing.com/p372877

VersaLogic Corporation

www.VersaLogic.com/05Hawk

sales@VersaLogic.com

503-747-2261

linkedin.com/company/versalogic-corporation @versalogic

Hardware Fox (VL-EPM-19) Rugged PC/104-Plus Embedded Computer Fox is a rugged new PC/104-Plus™ single board computer (SBC). It features the compactness of the PC/104 form-factor, and the compatibility of the classic PC/104-Plus expansion interface—with ISA and PCI bus expansion. It also features extensive I/O capabilities, low power consumption, and fanless operation over the full industrial temperature range. The Fox is a full-featured SBC for low power embedded environments that require passive cooling. It delivers mid-range performance and lower power draw along with industry-standard PC/104-Plus compatibility. The Fox leverages DMP’s Vortex86DX2 System on Chip. It offers full industrial temperature (-40º to +85ºC) operation, and low power requirements (5.3 Watts). It provides I/O expansion through the PC/104-Plus stackable bus (PCI + ISA), as well as a Mini PCIe socket, MicroSD socket, and a SPI/SPX interface. Designed and tested to withstand extreme temperatures, high-impact, and vibration, Fox features no moving parts and soldered-on RAM. This single board computer is an ideal choice for applications that require a rugged, high reliability computer. The Fox is backed by VersaLogic’s 5-year warranty and product life extension programs that can continue delivery well past the year 2025.

FEATURES High Reliability -40° to +85°C Operating Temperature Soldered-on RAM (up to 1 GB) Fanless Operation High shock and vibe

∠ ∠ ∠ ∠

Product Highlights DMP Vortex86DX2 32-bit Processor VGA and LVDS video outputs Mini PCIe / mSATA socket Two 10/100 Ethernet ports Four USB 2.0 ports PC/104-Plus expansion SPI/SPX expansion Windows, Linux, VxWorks, etc.

∠ ∠ ∠ ∠ ∠ ∠ ∠ ∠

embedded-computing.com/p373277

VersaLogic Corporation

www.VersaLogic.com/05Fox

 36

sales@VersaLogic.com

503-747-2261

linkedin.com/company/versalogic-corporation @versalogic

Embedded Computing Design | February 2016

Hardware

PPM-C407 - Low Power PC/104 SBC with Long Term Availability The PPM-C407 from WinSystems utilizes the E3800 family of Atom™ processors from Intel® to provide low power and performance in the versatile PC/104 form factor. Designed for harsh environments and reliability, it includes soldered RAM for added shock and vibration resistance with an operating temperature range from -40°C up to +85°C. WinSystems is offering the PPM-C407 in multi-core options depending on the application requirements. The scalable performance allows you to choose between low power single-core and higher performance dual or quad-core solutions. Linux, Windows, and other x86 operating systems can be booted from the mSATA, or USB interfaces, providing flexible data storage options.

FEATURES ∠ Multi-Core Intel® Atom™ E3800 Processors ∠ Up to 2 GB Soldered Down DDR3 RAM ∠ Two Fully Independent Displays (VGA, DisplayPort & LVDS) ∠ 1 Gb Ethernet Controller ∠ Fanless -40° to +85°C operational temperature ∠ 4 Serial Ports and 4 USB 2.0 ports ∠ 24 Bidirectional GPIO with event sense ∠ Bus Expansion: MiniPCIe, PC/104 & PC/104-Plus ∠ Bootable SATA and mSATA embedded-computing.com/p372685

WinSystems

www.winsystems.com

sales@winsystems.com

linkedin.com/company/winsystems-inc-

817-274-7553

@WinSystemsInc Hardware

PPC-10W-398D WinSystems’ PPC-10W-398D dual-core open frame Panel PC combines high performance multimedia graphics with a rich mix of industrial I/O. The Freescale i.MX 6DL processor’s integrated power management provides excellent efficiency and allows operation from -40° to +85°C. WinSystems series of ARM®-based embedded solutions are reliable yet versatile to meet a variety of applications with a remarkable power-toperformance ratio. They are designed for demanding applications in security, transportation, medical, and digital signage.

FEATURES ∠ 1024×600 Resolution 10” Panel PC with Touchscreen ∠ Dual-core Freescale® i.MX 6DL Cortex A9 Industrial ∠ ∠ ∠ ∠ ∠ ∠ ∠ ∠ ∠

ARM CPU @ 800 MHz 2GB of Soldered DDR3 RAM Gigabit Ethernet with IEEE-1588™ Six USB 2.0 ports and one USB On-The-Go Port Two CAN Bus ports, One High Speed Serial port 24 lines GPIO tolerant up to 30 VDC SD/SDIO and MicroSD sockets MiniPCIe and IO60 expansion Wide range DC or Power over Ethernet (PoE) PD Power Input Fanless -40° to +85°C operational temperature embedded-computing.com/p373278

WinSystems

www.winsystems.com www.embedded-computing.com

sales@winsystems.com linkedin.com/company/winsystems-inc-

817-274-7553 @WinSystemsInc

37 

Editor’s Choice

embedded-computing.com/editors-choice

Small, rugged XMC form factor Linux/Windows embedded computer The Innovative Integration SBC-Nano is a diminutive single board computer and XMC carrier with full Windows/Linux functionality that boots from eMMC. Combine with Innovative’s FPGA-based XMC mezzanine cards to reduce time to market while providing extreme performance for deeply embedded applications. The FPGA on each XMC is user-programmable using the FrameWork Logic in MATLAB or VHDL, with pristine analog I/O configurations from ultra-sonic to 6 GHz. Innovative Integration

www.innovative-dsp.com embedded-computing.com/p373107

3D image sensor chips bringing virtual reality to smartphones Infineon and pmdtechnologies announced the second generation of the jointly developed REAL3 3D image sensor chip portfolio. Combined with infrared cameras, imaging systems based on REAL3 chips can enhance virtual reality game experiences that involve gamer’s hands and their living environment. Other applications involve spatial measurement of rooms and objects, indoor navigation, and implementation of special photo effects. The new generation 3D image sensor chips double the pixel sensitivity to measure intensity of emitted and reflected infrared light. Google’s “project Tango” uses this technology to provide 3D perception in smartphones and tablets. Infineon Technologies

www.infineon.com embedded-computing.com/p373239

Easy integration of device data into M2M applications

Digi International

The Digi International Digi Device Cloud enables easy integration of device data by integrating access from any device through an open API and cloud connector. The devices can be securely managed and grouped for increased efficiency in M2M applications. Devices can also be managed along with providing software update capabilities. Alarms and notifications can be configured based on data conditions. The environment also includes open APIs that enable device data to be pushed into any third party application or custom-built M2M applications. The cloud systems are located in certified SSAE-16 and ISO27001 facilities for security purposes, are ISO27001 and PCI certified, and conform to many of the controls for NERC/CIP and HIPAA.

www.digi.com embedded-computing.com/p373240

 38

Embedded Computing Design | February 2016

Dell Internet of Things Contest. Connect What Matters. Apply by March 31, 2016 for a chance to win. Does your company want to bring the Internet of Things to life? Design your innovative IoT solution with real business impact based on the Dell Edge Gateway for a chance to win one of 16 amazing prizes worth $600,000 in total value*. Make the Internet of Things real. Today. Learn More at Dellconnectwhatmatters.com Find out how the Dell Edge Gateway 5000 series for IoT can help you accelerate your IoT return on investment. Visit Dell.com/IoTgateway today.

*NO PURCHASE NECESSARY. VOID WHERE PROHIBITED. Contest ends 3/31/2016. For Official Rules and complete details, visit Dellconnectwhatmatters.com Sponsor: Dell Marketing, L.P. ÂŠ2016 Dell Inc. All rights reserved. Dell and the Dell logo are trademarks of Dell Inc. Intel and the Intel logo are trademarks of Intel Corporation in the U.S. and/or other countries.