Tag Archives: 32-bit Microcontrollers

Securing the Internet of Streams


The evolution of IoT is now at a point that it will require a comprehensively redesigned approach to security threats in order to ensure its continuous growth and expansion.


The relentless flow of new product introductions keeps fueling the gargantuan estimates of billions of connected communicating computing devices which is projected to imminently make the Internet of Things ubiquitous within every facet of our lives. The IoT has been portrayed as the key enabler of a smarter world with compelling use cases that cut across a wide array of both personal and industrial ecosystems.

A great description is that the IoT is the global nervous system. This could be a pun, as IoT is increasingly producing troubling headlines. Stories abound, detailing security breaches that sound as if they were taken from a sci-fi movie, from hacked security cameras to a spamming refrigerator.

IoT-Global-Nervous-System

Figure 1 (Source: re-workblog.tumblr.com)

The explosive growth of the IoT coincides with an alarming increase in reported rates of identity theft and hacker attacks on everyday gadgets and appliances. Security researchers have easily established the feasibility of attacks against TVs, cars, security cameras, and medical equipment. There is much more than stolen money on the line if these types of attacks are carried out. The evidence demonstrates that existing security mechanisms are insufficient or ill-suited to address the risks inherent with the ubiquitous deployment of the IoT.

The need for a new original approach

The traditional approach to security, applied to both consumer and business domains, is one of separation – preventing those who are considered bad actors from accessing devices and networks. However, the dynamic topology of the network environments in which IoT applications are deployed largely invalidates the separation approach, making it both impractical and overly rigid. For example, with BYOD (bring-your-own-device), enterprises struggle to apply traditional security schemes to devices that may have been compromised while outside the perimeter firewall.

Many IoT devices self-configure and run autonomously. User interaction is limited to the devices’ operations, and there are no means to change security parameters. These devices rely on the manufacturer to implement security, both in the hardware and the software.

Moreover, manufacturers have to consider the broader ecosystem, not just their own products. For example, recent research has revealed inherent security flaws in USB memory stick controller hardware and firmware. Users must be concerned not only about the safety of the data on the memory stick, but if the memory stick controller itself has somehow been compromised.

To thwart similar issues, IoT device vendors are rushing to upgrade their product portfolios to low-power, high-performance microcontrollers that include firmware upgrade and data encryption mechanisms.

Atmel's IoT Layered Security Solutions

Figure 2 (Source: Atmel’s White Paper: Integrating the Internet of Things)

In the hyper-connected world of IoT, security breaches will gravitate towards the weakest link in the chain. It will become very hard to maintain the confidence that any particular device, user, application or service maintains its integrity; instead, the assumption will be that things will occasionally break for a variety of reasons, over which there is little control and no method for fixing. As a result, IoT will force the adoption of new concepts for the establishment of trust.

A smarter network combined

In the loosely coupled world of IoT, security issues are driving a need for greater collaboration among the vendors participating in the ecosystem, recognizing their respective core competencies. Hardware vendors make devices smarter. Software developers make applications and services smarter. The connective tissue, the global Internet with its myriad of communication transports and protocols, is tasked with carrying the data that powers IoT. This begs the question – can the network be made an enabler of IoT security by becoming smarter in its own right?

Context is essential for identifying and handling security threats and is best understood at the application level, where the intent of information is processed. This points towards a higher-level communication framework for IoT – the Internet of Data Streams. This framework enables apps and services to view things as consumers and producers of data. It allows for descriptive representations of devices’ operational status and real-time detection of their presence or absence.

Elevating the functional value of the Internet, from a medium of communication to a network of data streams for IoT, would be highly beneficial to ease collaboration among the IoT ecosystem participants. The smarter network can provide apps and services with the ability to implement logic that detects things that break or misbehave, flagging them as suspect while ensuring graceful and consistent operation using the redundant resources.

InternetOfThingsHorizontal

For example, a smarter network can detect that a connected sensor stopped functioning (e.g. due to a denial of power attack, possibly triggered through some obscure security loophole) and allow the apps that depend on the sensor to provide uninterrupted service to users. Additionally, a network of data streams can foster a global industry of security-as-a-service solutions, which can, as an example, send real-time security alerts to app administrators and device manufacturers.

The evolution of IoT is now at a point that it will require a comprehensively redesigned approach to security threats in order to ensure its continuous growth and expansion. Addressing the surfaced issues from an ecosystem standpoint calls for apps, services and “things” to explicitly handle communication via a smarter data network, which has the promise of placing IoT in safer hands, courtesy of the Internet of Streams.

And the Simply AVR Design Contest winners are…

Back in March, Atmel launched the second stage of its Simply AVR Design Contest, which encouraged Makers, designers and engineers to develop clever, ground-breaking 8-bit microcontroller-based designs using its highly-popular AVR family. After several months of ideation and submissions, we’re excited to announce that the grand prize winner of the contest is Juan Gonzalez for his IoT ATmega2560-powered robot.

AVRHero1

Programmed with Atmel Studio 6.2, the winning IoT project — which garnered nearly 116,000 votes — runs in three modes including Wi-Fi via an Android application, object-tracking mode and MIMIC mode via TCP/IP.

“Atmel AVR MCUs are simple to use, have a robust ecosystem and are extremely flexible, allowing beginner developers to create innovative, out-of-the-box embedded designs beyond traditional applications,” explained Gonzalez.

“The ATmega-powered IoT robot only took me a couple days to put together and I was thrilled when I was notified. Thank you to the Atmel team for enabling me to showcase my design. I will continue to design with AVR MCUs.”

AVRhero2

In total, five winners were selected through public voting on the contest site and Facebook; meanwhile, a separate Simply AVR Design Contest was conducted in parallel in China. Runner-ups included:

Sumit Grover, Remote and GSM-based home automation system

Savvas-George Kokkinidis-Loungos, Wireless remote car device using hand movements

Shreyas Gite, Arduino-powered medical scanner to measure body temperature and other vitals

Rahul Kar, Digital Soduku solver

“I’d like to congratulate our winners for the Simply AVR Design Contest,” said Sander Arts, Atmel Vice President of Marketing. “With over 300,000 votes for all five winners, there was clearly a lot of enthusiasm for the second phase of the Simply AVR Contest. All these projects showcased creative, impressive designs that demonstrate the simplicity of Atmel’s AVR MCUs which extend beyond the traditional boundaries. With a community of AVR enthusiasts, we are looking forward to the continuation of this program.”

With another successful challenge in the books, we’re eager to see what the future holds for these Makers’ prototypes. Perhaps, they will follow in the footsteps of previous design contest champion Pamungkas Prawisuda Sumasta, who recently launched a Kickstarter campaign for his team’s Phoenard all-in-one prototyping device.

Those wishing to browse through some of the other submitted creations can head over to the contest’s official gallery here.

MQTT not IoT “god protocol,” but getting closer

One protocol, and its descendants, drove the success of the World Wide Web. IP, or Internet Protocol, is the basis of every browser connection and the backbone of IT data centers. Some assumed that the Internet of Things would follow suit, with the thought that having an IP address would be a sufficient condition to connect.

The problem on the IoT isn’t IP – the problem is all the stuff layered on top of it. Running protocols such as HTTP, SSL, and XML requires significant compute power and memory space. The average PC, smartphone, or tablet has enough horsepower today to do that, but the average sensor running on a smaller microcontroller does not. (ARM Cortex-M7 notwithstanding.)

To combat that, the industry has spawned a huge list of alternative, mostly non-interoperable IoT protocols. A partial list: 6LoWPAN, AllJoyn, AMQP, ANT+, Bluetooth, CoAP, DASH7, DDS, INSTEON, KNX, MQTT, NFC, RFID, STOMP, Thread, Weightless, XMPP, ZigBee, and Z-Wave. New consortia are popping up weekly with more ideas.

Searching for an IoT “god protocol”, one unifying end-to-end protocol serving all things, is silly. At one end, sensors have different requirements such as range, RF spectrum, security, topology, and power consumption. At the other, any successful IoT strategy will ultimately need to integrate with an IP-based cloud in some form. Greenfields of any scale rarely exist. IoT applications need to connect and exchange data.

The answer is building a multi-protocol bridge between sensors and actuators, mobile devices, and the cloud. Ideally, code would be open source, and would provide scalability to span a wide range of devices in large numbers. Additionally, transport would be reliable, surviving brief intermittency in wireless connections.

IBM Internet of Things Foundation

More and more organizations are embracing MQTT as part of the bridge. MQTT offers a full-up version running over TCP/IP, and a slimmed down version MQTT-SN for non-IP devices. Its publish/subscribe model allows topologies to scale while retaining real-time characteristics and configurable quality of service.

IBM started the whole MQTT movement as a message broker for mainframes and servers, with integration into WebSphere for web services. They then opened it up for embedded use in a release to OASIS and the Eclipse Foundation.

A big piece of IBM Bluemix is the IoT Foundation, a cloud-based instance of MQTT with predefined topic structures and message formats. Mobile apps are already using MQTT, with applications such as Facebook Messenger and Salesforce.com. IBM also has an e-book on MQTT in mobile.

Other recent developments to consider:

  • ARM’s mbed device server seeks to replace a generic web server with one tailored for the IoT. Built from technology in the Sensinode acquisition, ARM has brought HTTP, CoAP, and MQTT together in one platform.
  • 2lemetry has taken that a step further with ThingFabric, integrating protocol actors including MQTT, CoAP, and STOMP, along with extensibility.
  • PubNub has taken a websocket connections approach running over MQTT, focusing on low latency, reliable delivery from a cloud implementation. There is a good PubNub guest post on Atmel Bits & Pieces describing the approach.
  • Speaking of Atmel and Arduino, IBM has several recipes for leveraging Arduino with the IoT Foundation, such as an Arduino Uno connection example, and a series on implementing a cloud-ready temperature sensor.
  • Open source motivates many folks, and one of the more interesting individual projects out there is a bridge for AllJoyn to MQTT. If successful, the implications could be significant, such as controlling home entertainment devices directly from Facebook on a mobile device.

Again, I don’t think there is a “god protocol” that will take over the IoT once and for all, satisfying each and every use case. The winners are going to integrate multi-protocol bridges to serve as wide a range of use cases as possible. The ability of MQTT to connect sensors and mobile devices to big data systems in real time is drawing more participants in.

This post has been republished with permission from SemiWiki.com, where Don Dingee is a featured blogger. It first appeared there on November 5, 2014.

Fusing fashion and tech with an Atmel powered robotic dress

A collaboration between 360 Fashion Network CEO Anina Net, Polish couture designer Michal Starost and IT architect Bruce Bateman has led to world’s first robotic dress powered by Atmel microcontrollers (MCUs).

gsma-360fashion-robotic-dress-1024x579

The dress made its catwalk debut at the “When Technology Meets Fashion” event held during Beijing Design Week.

Aside from an Atmel MCU, the robotic garment features 6 servo-controlled support arms comprised of fiberglass reinforced with aluminum, custom software and a high-powered battery pack. In what sounds like something out of Hunger Games, the arms lift in sync to convert the dress from a day dress to an evening gown.

While the current version of the dress is not Internet-connected and does not employ any sensors, we can surely expect to see further advancements in coming months.

360Fashion-Robotic-dress-gsma-2

In fact, Anina says 360Fashion Network is currently on another version that will be smartphone-controlled to lift the dress to the wearer’s desired length. Additionally, future iterations may even monitor vital signs and change color or form depending on the body temperature or heart rate of the wearer.

“More advanced iterations might also communicate with networked databases, adapting the color, weave, pattern, length, and style of the dress based on real-time information on new cultural trends, environmental changes, news developments, or weather conditions. The speed at which such innovations can be realized, however, will depend heavily on progress in fabric technology,” the company wrote in a recent blog post.

360fashion-laser-dress-michal-starost

This robotic dress wasn’t the only eye-opening garment exhibited during Design Week. The team at 360Fashion Network also unveiled four dresses that integrated lasers into the fabric as a key design element.

From an [ATmega32u4 based] Katniss Everdeen LED dress to an [Arduino powered] personal space skirt, we are only at the mere beginning of fashion and technology’s coalescence. Like stylists to the latest trends, we’ll be there to piece together these next-gen creations using an assortment of 8- and 32-bit MCUs.

 

 

Atmel samples new family of Atmel | SMART ARM Cortex-M7-based MCUs

As previously reported on Bits & Pieces, ARM recently unveiled a new 32-bit Cortex-M7 microcontroller (MCU) targeted at high-end, next generation embedded applications and has named Atmel as one of the early lead licensees of the processor, enabling the company to deliver exciting new products to the market in the forthcoming months.

Today, in the midst of ARM TechCon, Atmel has announced the development of a new family of Atmel | SMART ARM Cortex-M7-based MCUs that are sampling to select customers now. Broadening Atmel’s current MCU/MPU portfolio, the family is well positioned between Atmel’s ARM Cortex-M-based MCUs and Cortex-A-based MPUs enabling designers to select from a greater range of processing solutions. The new devices will address high-growth markets including the Internet of Things (IoT) and wearables, as well as automotive and industrial applications that require both high performance and power efficiency.

think

The Atmel | SMART Cortex-M-based MCUs allow customers to scale-up performance, SRAM and system functionality, while keeping the Cortex-M class ease-of-use and maximizing software reuse. The first devices will run up to 300MHz, with up to 384kByte SRAM configurable as Tightly Coupled Memory (TCM) or System Memory, and up to 2Mbyte on-chip Flash. They will be comprised of three series: general purpose, connectivity and automotive-qualified.

“As one of the first ARM licensees, we are excited to add the Cortex-M7 core to our already broad portfolio of MCUs and MPUs,” explained Jacko Wilbrink, Atmel Senior Marketing Director. “The new Cortex-M7-based MCUs leverage our advanced peripherals and flexible SRAM architecture for higher performance applications, while keeping the Cortex-M class ease-of-use. This new addition enables our customers to select from an even larger portfolio of Atmel | SMART ARM-based MCUs to optimize system designs from consumer IoT devices to automotive applications.”

“Atmel’s new family of microcontrollers helps to bridge the gap between existing microprocessors and highly-efficient microcontrollers on the market,” shared Noel Hurley, General Manager, CPU Group. “The ARM Cortex-M7 core drives innovation and pushes the performance envelope for embedded devices.”

All devices come standard with high-speed USB On-the-Go (OTG) and on-chip high-speed USB PHY, the connectivity series offers 10/100 TBase Ethernet MAC and Dual CAN-FD from Bosch. The automotive series offers Ethernet AVB support and Media LB, which when combined with the Cortex-M7 DSP extensions, make the series ideal for infotainment connectivity and audio applications.

Atmel is working closely with the ARM ecosystem partners on development tool support and RTOS BSPs for the new Atmel | SMART Cortex-M7-based MCUs. In addition, Atmel will offer complete support for this new MCU family on Atmel Studio and Atmel ICE. A comprehensive set of peripheral drivers and examples will be provided, as well as Xplained evaluation kits.

“The Cortex-M7 is well positioned between Atmel’s Cortex-M based MCUs and Cortex-A based MPUs enabling Atmel to offer an even greater range of processing solutions,” Reza Kazerounian, Atmel Senior Vice President and General Manager, recently revealed. “Customers using the Cortex-M-based MCU will be able to scale up performance and system functionality, while keeping the Cortex-M class ease- of-use and maximizing software reuse.”

While sampling to select customers is currently underway, general sampling and availability of the Xplained kit is expected in early 2015. Those interested in learning more can come visit us at ARM TechCon in Santa Clara, California October 1-3, 2014 at booth #205.

All tiny AVR parts in a spreadsheet

I just made a spreadsheet of all the tinyAVR parts. All my pals love the MCU selector guide, but I have a lot of analog dinosaur buddies that prefer a spreadsheet to a web-based interface. You can sort the data and this spreadsheet has the filter box on the columns, so you can sort out things you care about and exclude the things you don’t. The spreadsheet fits on a 24-inch display, and you can print it out on a single B-sized sheet and use it as an infographic.

ATtinyAVR-product-line_2014-08-20

This screenshot shows how all the tinyAVR parts will fit on one 11×17 ledger-sized or B-sized sheet of paper.

I started with an Excel dump of the selector guide after adding every single parameter to the search. I then took all the tinyAVR parts, and rearranged the columns, throwing out the irrelevant ones. I also combined the automotive parts with the basic parts. That added two columns for automotive temp and automotive Vcc range. Adding 2 columns to remove 13 rows seemed like a good deal. The part name links to the product page on our website.

I made a column for each package. That took a long time. Semiconductor companies think of a part as the silicon die, with the package being almost irrelevant. We systems folk know the package might be the most important thing. I tried to put the smaller packages on the left, with those big ol’ DIP (dual-inline plastic) parts on the right side. There is a second sheet in the spreadsheet that shows all the parts by number and there I put the package size, in mm. In both sheets, the package name links to the definition page on our website.

ATtinyAVR-product-line_2014-08-20_sheet-2

The second sheet of the spreadsheet shows all the tinyAVR parts by number. I put the exact package size on this page.

Besides the packages and package size, I also spent a long time getting pricing. My buddy Wayne Yamaguchi requested this, and he is absolutely right, price is the most important spec of any part, and I hate when it takes 5 clicks to find it. These prices are a bit sketchy. All I did was click on the “Buy” link and select a handful of parts from each family, and then looked at the Digi-Key price, in 1000s. I put in the highest and lowest of the few I selected, but this is by no means scientific or dispositive, as the lawyers would say. What I should do is put the price in the “Package” column, so you know what the package is and what price we charge, but many parts are in the same package but have two Vcc ranges, so there is no unique way to encode this and keep the spreadsheet on one printable page. Maybe I can blow out the second page to show every orderable part number and its price and specs. Always time to do it over, never time to do it right.

The major thing I want to add is the OrCAD 9.2 footprint name for the packages. I am afraid to do this now, since we have all been burned by narrow-DIP/wide-DIP and narrow -SOIC/wide-SOIC and what pin numbering to use on SOT parts, so that will have to wait for next time. If anyone has a proven definitive list of the OrCAD footprints, please let me know. paul.rako[yeah, the at sign]atmel.com

You can highlight all the parts and use the “Data>Sort” function to order them any way you want. I did it by Flash memory size and part name. You can also use the little filter boxes on each column to include or exclude, or even put in a logical range with equal or less than or all the other things. Its not exactly grep or regular expressions, but it can get the job done helping you to find the right part.

Spreadsheet-filter-function

Excel filter boxes let you select just the parameters you care about.

I am told this spreadsheet works OK in Open Office/Libre. My pal Dave asked that any columns that are filtered be lit up red, but that takes a macro, and the VB macro may not work in Open Office, we are checking for that. Meanwhile, check there are 36 part families or that the little filter box does not have 3 pixels different to show the filter is on.

Microscopically-differerent-filter-icon

When you have filtered a column, it is almost impossible to tell, since the only indication is the icon makes this 3-pixel change.

Weasel weasel, CYA CYA, legal boilerplate—this is a hobby job, not an official Atmel document. If the selector guide had it wrong, it is wrong here too. I made my own mistakes too. And I already told you the pricing and the tiny1634 stuff was dicey. What I am hoping is that I can get some community support where you point out the errors, and tell me what to add. paul.rako[yeah, the at sign]atmel.com I also ask that you send this URL link to your pals, instead of just emailing the spreadsheet. That way the bosses will see you like this, and I can have the time to keep working on it.

Hans-Camenzind_tinyAVR-spreadsheet

If Hans Camenzind, the inventor of the 555 timer chip was still alive, he might have a copy of the tinyAVR spreadsheet up on his office wall. I miss Hans, at least he came to my Analog Aficionados party one year, before we lost him to the Grim Reaper.

 

Atmel and the Maker Revolution

I was part of the “original” Maker revolution. This was years ago, in the late 1980’s, and I was a latecomer. We used to make our own circuit boards, but slightly different from the ones today.

There was a 386 computer on my desk. My trusty 386 had ISA ports, extension card space, that most of us used as a basis for our designs. The ISA bus was easy to use, and the connector was large, meaning we could use simple, basic, cheap equipment to make our boards. What did we make? Everything! Digital IO, radio, remote control systems, everything. When I was a student, my flat was controlled entirely by one of these cards. Of course, the brain of my invention was the computer itself, it wasn’t easy to create a computer system.

A computer system requires several components. It requires a processor, and there were quite a few on the market at the time. It also requires memory, but two kinds; random access memory, RAM for short, is where variables are stored, and is the memory that a program uses to copy, calculate and modify data. A computer also requires read-only memory, ROM for short, and this is where the program is placed. Even that was tricky. You see, at the time, in order to “flash” a new program, we had to remove the EPROM device (short for Erasable Programmable Read Only Memory) and place it in ultraviolet light for up to 30 minutes. That was only the beginning. In order to flash a new program, you had to put it into a programmer, a device attached to the computer that wrote data into the device. Once that was done (it took a few minutes), then you could put the chip back onto the circuit board, and away you went. If you made a mistake, or if your program didn’t work, then you had to redo everything, which took over half an hour.

All of this was complicated, and required multiple components. The processor was one component. The RAM was another. So was the ROM. Interrupt controllers? Digital IO? PWM? They were all external components too. There was a reason why computers used to be that big. So we simplified things. The processor was the PC, and we just made extension boards. Of course, this made making things like robots difficult, but we had lots of fun.

The ISA bus was slow, and users wanted PCs to become faster and faster. The ISA bus was soon replaced by VLB, short for VESA Local Bus. It added an extension to the ISA bus, allowing for faster memory transfers. We had faster computers, better graphics, and we could still use our boards. However, it also sent a clear message; we were soon to find a new way of doing things. VLB was replaced by PCI, which was replaced by PCI Express. This bus is lightning fast, but requires complex electronics, and very good equipment to make boards with connectors that fine. Our trusty ISA cards soon ended up in the dustbin. We could still use the serial port or the parallel port, but it wasn’t the same. Most of us stopped.

It was depressing. We tried making our own computers, but they were complicated. External components, long flash times, prohibitive prices… One company was listening.

Atmel's ATMEGA328P-PU an AVR 8-bit processor

Atmel’s ATMEGA328P-PU an AVR 8-bit processor

In 1996, Atmel shipped the AVR processor. It was an 8-bit processor, with a twist. It had internal RAM, and internal flash. No more external components. It could be flashed within seconds, and reflashed. You didn’t even need to take it off the breadboard to reflash it. Founded in 1984, Atmel had already made semiconductor devices for the professional market, but was also very close to Makers. They heard our cry for help, and they delivered. The AVR changed everything.

AVR-XMEGA

The AVR chip was an 8-bit device (32-bit devices also exist), but the computer we used to control our ISA cards was 32-bit. The thing is, we didn’t need 32-bits, and an 8-bit microcontroller was perfect for our needs. The AVR was small, cheap, reliable, and really, really easy to use. We flooded back, we redesigned our boards, and we made. We made everything. How good were the AVR chips? By 2003, Atmel had shipped 500 million devices.

Fast forward a few years, and here we are today. Makers are everywhere. We are back. We are making more than ever. And with awesome sponsors like Atmel, we are here to stay. 2013 was the year of 100 Maker Faires, and they were full of Arduinos.

New Breed of Maker Movement Engineers Blooming from Garages, Maker Faire, Hackerspaces, and Makerspaces

New Breed of Maker Movement Engineers Blooming from Garages, Maker Faire, Hackerspaces, and Makerspaces

What is on the Arduino? Well, most of them have an AVR. The Arduino Due isn’t an AVR-based device, it is an ARM device, but even that is made by Atmel too, and is just as easy to use. 2014 promises to be even more exciting!

New Breed of Engineers - Some Images from Maker Faire Bay Area, there were over 100 Maker Faires in 2013 budding in cities all across the globe

New Breed of Engineers – Some Images from Maker Faire Bay Area 2014. There were over 100 Maker Faires in 2013 budding in cities all across the globe

Arduino Due

Here’s the Arduino Due – with an Atmel ARM Based Processor

With Atmel as a sponsor, Makers are here to stay. If you haven’t tried to make your own device yet, try it! It doesn’t cost a lot, and you don’t need all the complicated hardware we used to have. You will be up and running in mere minutes, and believe me, it is fun! If you have any questions, go and see Atmel at one of the Maker Faires. If you come by the Maker Faire Rome, come say hello, I’ll be there with Atmel to show you just how much this technology has changed my life, and show you how to start.