Author Archives: Paul McLellan

About Paul McLellan

Paul has been in semiconductor for over 30 years. He primarily blogs at SemiWiki.com

Atmel and IoT and Crypto, oh my!

One of the companies that is best positioned to supply components into the Internet of Things (IoT) market is Atmel. For the time being most designs will be done using standard components, not doing massive integration on an SoC targeted at a specific market. The biggest issue in the early stage of market development will be working out what the customer wants and so the big premium will be on getting to market early and iterating fast, not premature cost optimization for a market that might not be big enough to support the design/NRE of a custom design.

Latest product in Atmel's SmartConnect family, the SAM W25 module

Here is Atmel’s latest product in the SmartConnect family, the SAM W25 module

Atmel has microcontrollers, literally over 500 different flavors and in two families, the AVR family and a broad selection of ARM microcontrollers ad processors. They have wireless connectivity. They have strong solutions in security.

Indeed last week at Electronica in Germany they announced the latest product in the SmartConnect family, the SAM W25 module. It is the industry’s first fully-integrated FCC-certified Wi-Fi module with a standalone MCU and hardware security from a single source. The module is tiny, not much larger than a penny. The module includes Atmel’s recently-announced 2.4GHz IEEE 802.11 b/g/n Wi-Fi WINC1500, along with an Atmel | SMART SAM D21 ARM Cortex M0+-based MCU and Atmel’s ATECC108A optimized CryptoAuthentication engine with ultra-secure hardware-based key storage for secure connectivity.

Atmel at Electronica 2014

Atmel at Electronica 2014

That last item is a key component for many IoT designs. Security is going to be a big thing and with so many well-publicized breaches of software security, the algorithms, and particularly the keys, are moving quickly into hardware. That component, the ATECC108A, provides state-of-the-art hardware security including a full turnkey Elliptic Curve Digital Signature Algorithm (ECDSA) engine using key sizes of 256 or 283 bits – appropriate for modern security environments without the long computation delay typical of software solutions. Access to the device is through a standard I²C Interface at speeds up to 1Mb/sec. It is compatible with standard Serial EEPROM I²C Interface specifications. Compared to software, the device is:

  • Higher performance (faster encryption)
  • Lower power
  • Much harder to compromise

Atmel has a new white paper out, Integrating the Internet of Things, Necessary Building Blocks for Broad Market Adoption. Depending on whose numbers you believe, there will be 50 billion IoT edge devices connected by 2020.

Edge nodes are becoming integrated into everyone’s life

As it says in the white paper:

On first inspection, the requirements of an IoT edge device appear to be much the same as any other microcontroller (MCU) based development project. You have one or more sensors that are read by an MCU, the data may then be processed locally prior to sending it off to another application or causing another event to occur such as turning on a motor. However, there are decisions to be made regarding how to communicate with these other applications. Wired, wireless, and power line communication (PLC) are the usual options. But, then you have to consider that many IoT devices are going to be battery powered, which means that their power consumption needs to be kept as low as possible to prolong battery life. The complexities deepen when you consider the security implications of a connected device as well. And that’s not just security of data being transferred, but also ensuring your device can’t be cloned and that it does not allow unauthorized applications to run on it.
IoT Design Requirements - Software / Development Tools Ecosystem

IoT design requirements: Software / development tools ecosystem

For almost any application, the building blocks for an IoT edge node are the same:

  • Embedded processing
  • Sensors
  • Connectivity
  • Security
  • And while not really a “building block,” ultra-low power for always-on applications

My view is that the biggest of these issues will be security. After all, even though Atmel has hundreds of different microcontrollers and microprocessors, there are plenty of other suppliers. Same goes for connectivity solutions. But strong cryptographhic solutions implemented in hardware are much less common.

The new IoT white paper is available for download here.

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

Exploring Atmel’s new microcontrollers, IoT and wearables

More and more companies, regardless of their vertical, are trying to get closer to their customers and see various aspects of the internet of things (IoT) as the way to do so. For a good example, here is Salesforce Wear Developer Pack which, as they say:

..is a collection of open-source starter apps that let you quickly design and build wearable apps that connect to the Salesforce1 Platform. Millions of wearable devices connected to the cloud will create amazing new application opportunities.

Since Salesforce.com cuts across all industries this has potential impact in many different market segments.

And, the wearable devices that they list are Google Glass, Android Wear, Samsung Gear Watch, Myo Armband, Nymi Bionym, Pebble Watch, Jawbone UP, Epson Moverio, Vuzix Smart Glasses, Oculus Rift, Meta Glasses.

This combination brings home that the internet of things isn’t just about the things, it is about connecting the things back to the cloud so that the data generated can be aggregated where it has much greater value.

I am sure that people will design SoCs for various aspects of IoT, but even if they do I think it will be in old processes, not even 28nm, so they can integrate sensors and analog and wireless on the same chip. But more likely a lot of these will be small boards with microcontrollers, wireless and sensors on different chips. For example, take a look at the iFixit teardown of the Fitbit, which in its current incarnation is about one inch by quarter of an inch.

atm1

An important aspect of doing this sort of design is having enough microcontrollers with the right combination of features. You can’t afford to have twice as much flash as you need or too many unused functions. The Atmel microcontroller product finder shows that at present they have 506 different ones to choose from.

The most recent two are SAMA5D4, and SAMD21 which are specifically targeted towards wearables and IoT projects. These are the latest two products in the Atmel SAM D family.

One area of especial concern in this market is security since it is too dangerous to simply try and do everything in software on the microcontroller. Keys can be stolen. Software can be compromised if it is in external RAM. An area of particular security concern is to make sure that any JTAG debug port is secure or it can be used to compromise almost anything on the chip.

So what are these chips?

The SAMA5D4 is an ARM Cortex-A5 device with a 720p hardware video decoder. It has high security with on-the-fly capability to run encrypted code straight out of external memory, tamper detection, secret key storage in hardware, hardware private and public key cryptography and ARM TrustZone. It supports both 16 and 32 bit memory interfaces for maximum flexibility. It is targeted at applications that require displays, such as home and industrial automation, vending machines, elevator displays with ads, or surveillance camera playback.

The SAMD21 is the latest Atmel microcontroller based on the ARM Cortex-M0+ but in addition to the features on earlier cores it also has:

  • Full speed USB device and embedded host
  • DMA
  • Enhanced timer/counters for high end PWM in Lighting and motor control – I2S
  • Increased I2C speed to 3.4Mbit/S
  • Fractional PLL for audio streaming

As you can deduce from the feature set it is target at medium end industrial and consumer applications, possibly involving audio and high power management.

And, to show that this sort of market is starting to become real, at the salesforce Dreamforce event earlier in the week a keynote was given by will.i.am of the Black Eyed Peas (and a founder of Beats that Apple recently acquired). In a chat with Marc Benoiff, CEO of Salesforce.com, he has already leaked that he will introduced a wearable wrist computer that doesn’t require a phone to piggy-back on (unlike the Apple Watch).

Watch the chat:

Looking for more information on the SAMA5D4It can be found here.

This post has been republished with permission from SemiWiki.com, where Paul McLellan is a featured blogger. It first appeared there on October 17, 2014.

Exploring smart meters in the Internet of Things

The Internet of Things (IoT) isn’t a single homogenous market but splits up into different segments with very different requirements. A lot of IoT markets are still in our future: next generation wearable medical devices, autonomous cars and more. One area where IoT has been going strong, long enough that it probably pre-dates the catchy buzzword IoT, is smart power meters.

Atmel recent announced their latest power line communications SoC specifically designed for this market. The SAM4CP16B is an extension of Atmel’s SAM4Cx smart energy platform built on a dual-core 32-bit ARM Cortex-M4 architecture. It is fully compatible with Atmel’s ATPL230A OFDM physical layer device compliant with PRIME standard specification. The flexible solution addresses OEM’s requirements for various system partitioning, BOM reduction and time-to-market requirements by incorporating independent application, protocol stack and physical layer processing functions within the same device. Key features of the SoC include integrated low-power driver, advanced cryptography, 1MB of embedded Flash, 152KB of SRAM, low-power real-time clock, and an LCD display controller.

I think that as various submarkets of the Internet of Things develop, we will see a lot of devices like this; SoCs that integrate everything that is required for a particular application, leaving the system company to customize the hardware, add their own software and so on. IoT will not be a market like mobile, with huge chips being done in the latest process generation. Many IoT designs will include analog, RF and sensors, all of which are best designed in older processes like 65nm or even 130nm.

The system volumes for many designs will be relatively low and so designing a specific chip for each application will be unattractive. Even in mobile where the volumes are much higher, only Apple and Samsung design their own application processors, as far as I know. Everyone else licenses one from Qualcomm, Mediatek or others… Even Apple gets the modem (radio) from Qualcomm. The aggregate volumes will end up being large (there will be a lot of things) so the prize goes to the semiconductor companies that do the best job of designing chips that match what the system companies require.

Interested in learning more? The data sheet for the part can be found here. (Warning: It’s 1,000 pages!)

This post has been republished with permission from SemiWiki.com, where Paul McLellan is a featured blogger. It first appeared there on August 13, 2014.

Exploring the Internet of Things and wearable tech market

Earlier this year, my wife and I drove to Southern California in search of information on the wearable computing market. After stops in Irvine, San Diego, and some play time in La Jolla we returned in time for the CASPA Symposium: “The Wearable Future: Moving Beyond the Hype; the Search for the Holy Grail and Practical Use Cases.” CASPA is the Chinese American Semiconductor Professionals Association and their Spring Symposium was at the Intel HQ Auditorium in Santa Clara with a standing room only crowd.

The big attraction for me was the keynote speaker Dr. Reza Kazerounian, SVP & GM, Microcontroller Business Unit of Atmel. I originally ran across his name during my research for “A Brief History of STmicroelectronics” (the piece I did last week) as he was CEO of ST Americas from 2000 to 2009. It was truly an honor to hear Dr. Reza Kazerounian speak.

“The Internet of Things (IoT) is opening up fresh horizons for a new generation of intelligent systems that leverage contextual computing and sensing platforms, creating new markets. One of these platforms is the wearable category of devices, where the combination of sensors using low-power sensor fusion platforms, and short-range wireless connectivity, are giving rise to a variety of exciting end markets. From self-quantification to a variety of location-based applications, to remote health monitoring, wearables are becoming the harbinger for a whole host of services. With the right set of biometric sensors combined with local fast data analytics, wearables have the potential to revolutionize the health care industry. These devices can provide real-time data and contextual information along with all the health care requirements, improving the quality of care, and lowering the overall cost of care. This discussion will review the underlying technologies needed to make the “always-on health care revolution” happen, and explore how the future of medicine is being shaped by wearable devices.”

Contextual computing is the key term here and, yes, I had to look it up. The application I’m most interested in, besides fitness, is security. I want my smartphone to know it is me holding it by my movements, voice, and usage. I remember back when my credit card kept getting security flagged when I started traveling internationally. Once Visa profiled my usage it never happened again. As the smartphone takes over our financial lives, security will be even more critical, absolutely.

There are three key components to wearable market silicon: Low power, low cost, and low area. Billions of these devices will be deployed over the next 10 years so the market will by far exceed smartphones. The wearable market will be very fragmented which opens up opportunities for entrepreneurs around the world. In fact, Dr. Kazerounian predicted that 15% of those devices will come from companies that are less than 3 years old to which I agree wholeheartedly.

One of the big challenges is low power connectivity. For now these devices will be talking to our smartphones and that means ultra-low power connectivity. Coincidentally, Atmel recently announced a new SmartConnect family that combines Atmel’s ultra-low power MCUs with its wireless solutions and complementary software into a single package:

“Ultra-low power wireless connectivity is critical for embedded applications in the era of the Internet of Things,” said Reza Kazerounian, Sr. Vice President and General Manager, Microcontroller Business Unit, Atmel Corporation. “Atmel’s SmartConnect technology is about simplifying the use of embedded wireless connectivity technologies and enabling users to accelerate their time-to-market. This simplicity allows all players to participate in the IoT market, fueling the innovation needed to accelerate adoption.”

Celebrating their 30th year, Atmel is an IoT market leader with an interesting history that you can read about it here. 

This post has been republished with permission from SemiWiki.com, where Daniel Nenni is a featured blogger. It first appeared there on Marcn 9, 2014.

Baskin-Robbins only has 31 flavors, Atmel has 505

Actually these days even Baskin-Robbins has more, but not 505 like Atmel. That’s a lot. While some are AVR, both 8-bit and 32-bit, others are various flavors of ARM (all 32-bit) ranging from older parts like the ARM9 to various flavors of Cortex ranging from the M0 (tiny microcontroller with no pipeline or cache) up to A5. Of course, the ARM product line goes all the way up to 64-bit Cortex-A57 and so on — but they are not in any sense of the word microcontrollers and are really only used in SoCs and not standalone products.

But with 505 choices, how do you pick one? Fortunately, Atmel has made it easy for you to navigate the various flavors. With the help of the company’s MCU product finder, you now have the ability to input your hard constraints, while the tool will narrow down the choices. For example, if you want your microcontroller to have at least 64 Kbytes of flash, then there are only 257 out of the 505 that will suit your needs. For each parameter, users can set minimums and maximums — except for the yes/no choices.

When it comes to the selection process, there are several things that you can constrain:

  • Flash memory (0 to 2Mbytes)
  • Pin count (6 to 324)
  • Operating frequency (1 to 536MHz)
  • CPU architecture (pick from 8-bit AVR, 32-bit AVR, ARM 926 and 920, ARM Cortex M0, M3, M4, A5)
  • SRAM (30 bytes to 256 Kbytes)
  • EEPROM (none to 8 Kbytes)
  • Max I/O pins (4 to 160)
  • picoPower (yes or no)
  • Operating voltage (various ranges from 0.7V to 6V)
  • Operating temperature (various from -20oC to 150oC)
  • Number of touch channels (none to 256)
  • Number of timers (1 to 10)
  • Watchdog (yes or no)
  • 32KHz real time clock (yes or no)
  • Analog comparators (0 to 8)
  • Temperature sensor (yes or no)
  • ADC resolution (8 to 16 bits)
  • ADC channels (2 to 28)
  • DAC channels (0 to 4)
  • UARTs (0 to 8)
  • SPI (1 to 12)
  • TWI (aka I2C) interface (none to 6)
  • USB interface (none, device only, host+OTG, host and device)
  • PWM channels (0 to 36)
  • Ethernet interfaces (none to 2)
  • CAN interfaces (none to 2)

Wow, that’s a lot of options! But after a couple of dozen selections, you can narrow down your choice to something manageable. Here’s how the interface will appear:

Say for instance, I wanted to pick a microcontroller, an ARM Cortex of some flavor. Already choices are down to 189. I want 32K to 128K of flash (now down to 73 choices). I want it to run at an operating frequency of at least 64 MHz (now down to 10). I want 4K of SRAM (turns out all 10 choices already have that much). I need 4 timers. I am now down to 2 choices:

These two choices are the ATSAM3S1C and the ATSAM3S2C — both ARM Cortex-M3s. The first has 64K of flash and the second 128K. I can click on the little PDF icon and access a full datasheet for these microprocessors. If I don’t like the choices and I have some flexibility on specs, then obviously I can go back and play with the parameters to get some new options.

I can click on the “S” to order samples. However, in order to do this, you must already have an Atmel account. Or, with just another click on the shopping cart icon, I can obtain a list of distributors throughout various geographic regions, where I can actually place an order. It even tells me how many each of them have in stock!

For those of you ready to start searching, you can find the Atmel Microcontrollers Selector here.

This post has been republished with permission from SemiWiki.com, where Paul McLellan is a featured blogger. It first appeared there on March 2, 2014.