Tag Archives: Andreas Eieland

4 reasons why Atmel is ready to ride the IoT wave

The IoT recipe comprises of three key technology components: Sensing, computing and communications.

In 2014, a Goldman Sachs’ report took many people by surprise when it picked Atmel Corporation as the company best positioned to take advantage of the rising Internet of Things (IoT) tsunami. At the same time, the report omitted tech industry giants like Apple and Google from the list of companies that could make a significant impact on the rapidly expanding IoT business. So what makes Atmel so special in the IoT arena?

The San Jose, California–based chipmaker has been proactively building its ‘SMART’ brand of 32-bit ARM-based microcontrollers that boasts an end-to-end design platform for connected devices in the IoT realm. The company with two decades of experience in the MCU business was among the first to license ARM’s low-power processors for IoT chips that target smart home, industrial automation, wearable electronics and more.

Atmel and IoT (Internet of Things)

Goldman Sachs named Atmel a leader in the Internet of Things (IoT) market.

Goldman Sachs named Atmel a leader in the Internet of Things (IoT) market

A closer look at the IoT ingredients and Atmel’s product portfolio shows why Goldman Sachs called Atmel a leader in the IoT space. For starters, Atmel is among the handful of chipmakers that cover all the bases in IoT hardware value chain: MCUs, sensors and wireless connectivity.

1. A Complete IoT Recipe

The IoT recipe comprises of three key technology components: Sensing, computing and communications. Atmel offers sensor products and is a market leader in MCU-centric sensor fusion solutions than encompass context awareness, embedded vision, biometric recognition, etc.

For computation—handling tasks related to signal processing, bit manipulation, encryption, etc.—the chipmaker from Silicon Valley has been offering a diverse array of ARM-based microcontrollers for connected devices in the IoT space.


Atmel has reaffirmed its IoT commitment through a number of acquisitions.

Finally, for wireless connectivity, Atmel has cobbled a broad portfolio made up of low-power Wi-Fi, Bluetooth and Zigbee radio technologies. Atmel’s $140 million acquisition of Newport Media in 2014 was a bid to accelerate the development of low-power Wi-Fi and Bluetooth chips for IoT applications. Moreover, Atmel could use Newport’s product expertise in Wi-Fi communications for TV tuners to make TV an integral part of the smart home solutions.

Furthermore, communications across the Internet depends on the TCP/IP stack, which is a 32-bit protocol for transmitting packets on the Internet. Atmel’s microcontrollers are based on 32-bit ARM cores and are well suited for TCP/IP-centric Internet communications fabric.

2. Low Power Leadership

In February 2014, Atmel announced the entry-level ARM Cortex M0+-based microcontrollers for the IoT market. The SAM D series of low-power MCUs—comprising of D21, D10 and D11 versions—featured Atmel’s signature high-end features like peripheral touch controller, USB interface and SERCOM module. The connected peripherals work flawlessly with Cortex M0+ CPU through the Event System that allows system developers to chain events in software and use an event to trigger a peripheral without CPU involvement.

According to Andreas Eieland, Director of Product Marketing for Atmel’s MCU Business Unit, the IoT design is largely about three things: Battery life, cost and ease-of-use. The SAM D microcontrollers aim to bring the ease-of-use and price-to-performance ratio to the IoT products like smartwatches where energy efficiency is crucial. Atmel’s SAM D family of microcontrollers was steadily building a case for IoT market when the company’s SAM L21 microcontroller rocked the semiconductor industry in March 2015 by claiming the leadership in low-power Cortex-M IoT design.

Atmel’s SAM L21 became the lowest power ARM Cortex-M microcontroller when it topped the EEMBC benchmark measurements. It’s plausible that another MCU maker takes over the EEMBC benchmarks in the coming months. However, according to Atmel’s Eieland, what’s important is the range of power-saving options that an MCU can bring to product developers.

“There are many avenues to go down on the low path, but they are getting complex,” Eieland added. He quoted features like multiple clock domains, event management system and sleepwalking that provide additional levels of configurability for IoT product developers. Such a set of low-power technologies that evolves in successive MCU families can provide product developers with a common platform and a control on their initiatives to lower power consumption.

3. Coping with Digital Insecurity

In the IoT environment, multiple device types communicate with each other over a multitude of wireless interfaces like Wi-Fi and Bluetooth Low Energy. And IoT product developers are largely on their own when it comes to securing the system. The IoT security is a new domain with few standards and IoT product developers heavily rely on the security expertise of chip suppliers.

Atmel offers embedded security solutions for IoT designs.

Atmel, with many years of experience in crypto hardware and Trusted Platform Modules, is among the first to offer specialized security hardware for the IoT market. It has recently shipped a crypto authentication device that has integrated the Elliptic Curve Diffie-Hellman (ECDH) security protocol. Atmel’s ATECC508A chip provides confidentiality, data integrity and authentication in systems with MCUs or MPUs running encryption/decryption algorithms like AES in software.

4. Power of the Platform

The popularity of 8-bit AVR microcontrollers is a testament to the power of the platform; once you learn to work on one MCU, you can work on any of the AVR family microcontrollers. And same goes for Atmel’s Smart family of microcontrollers aimed for the IoT market. While ARM shows a similarity among its processors, Atmel exhibits the same trait in the use of its peripherals.

Low-power SAM L21 builds on features of SAM D MCUs.

A design engineer can conveniently work on Cortex-M3 and Cortex -M0+ processor after having learned the instruction set for Cortex-M4. Likewise, Atmel’s set of peripherals for low-power IoT applications complements the ARM core benefits. Atmel’s standard features like sleep modes, sleepwalking and event system are optimized for ultra-low-power use, and they can extend IoT battery lifetime from years to decades.

Atmel, a semiconductor outfit once focused on memory and standard products, began its transformation toward becoming an MCU company about eight years ago. That’s when it also started to build a broad portfolio of wireless connectivity solutions. In retrospect, those were all the right moves. Fast forward to 2015, Atmel seems ready to ride on the market wave created by the IoT technology juggernaut.

Interested? You may also want to read:

Atmel’s L21 MCU for IoT Tops Low Power Benchmark

Atmel’s New Car MCU Tips Imminent SoC Journey

Atmel’s Sensor Hub Ready to Wear

Majeed Ahmad is author of books Smartphone: Mobile Revolution at the Crossroads of Communications, Computing and Consumer Electronics and The Next Web of 50 Billion Devices: Mobile Internet’s Past, Present and Future.

ARM @ Atmel’s EELive! ToT booth

ARM’s Andy Frame stopped by Atmel’s EELive! 2014 ToT booth to chat with our very own Andreas Eieland (@AndreasMCUguy), who looks after Atmel’s SAM D Cortex-M0+ based family of devices.

As you can see, Frame snapped a great picture of Andreas standing next to Atmel’s tricked-out Tech on Tour Truck which travels around the US showcasing a wide range of Atmel-powered products, including those based on ARM’s Cortex-M and Cortex-A5.

ARM’s Ronan Synnott was also at Atmel’s EELive! booth giving a presentation about ARM’s DS-5 support for Atmel SAMA5D3 devices. Ronan described how, with DS-5 Professional Edition, ARM provides a leading-edge software development tool chain for bare-metal, RTOS and Linux based projects. 

For the SAMA5D3 devices, ARM offers full debug support out of the box when used in conjunction with DSTREAM or ULINKproD JTAG debug units, the Streamline System Performance Analysis tool and the highly optimizing ARM C compiler.

We hope to hear more from Ronan over the next few weeks, so be sure to check Bits & Pieces for additional embedded news and reports.

Meanwhile, Atmel’s Tech on Tour trailer will be headed to Austin, Texas on April 8th. We’ll be talking about low-power system design using Atmel’s ARM-based SAM4L MCU, touch and wireless solutions, as well as offering an introduction to Atmel’s versatile SAM D20 microcontroller.


Interested in learning more? You can register here and check out future ToT stops here.

Atmel’s MCU maestro talks IoT

Atmel Sr. Product Marketing Manager Andreas Eieland (@AndreasMCUguy) recently sat down with Graham Pitcher of NewElectronics to discuss the Internet of Things (IoT). As Pitcher notes, the IoT is exerting a major influence on the evolution of microcontroller (MCU) technology in 2014 and beyond.

“In broad terms, the IoT comprises three elements: edge devices, which often perform one dedicated function; hubs or fusion devices, which integrate data from edge devices; and larger processing elements,” said Pitcher. 

”It’s the first two categories which are currently focusing the minds of MCU developers. The reason? The IoT demands two things above all others – minimal power consumption and the lowest possible cost.”

Eieland concurred.

“Being able to have the right features at the right power consumption will be critical,” he said. “Edge devices will need to run from harvested energy or for their full lifetime from a single battery.”

According to Eieland, MCUs will ultimately have to consume less than 1µA and less than 200nA in deep sleep.

“Atmel makes 8051 based MCUs, but if you want to connect to ZigBee, for example, our AVR cores are a better choice,” he explained. “But we also have a Cortex-M0+ part that competes in that sector.”

In terms of specific product examples, Eieland highlighted Atmel’s close collaboration with Bosch Sensortec on the development of the BNO055.

“There are six dice in the package, including a SAM D20 MCU,” Eieland confirmed.

“It’s a good example of how we are working with sensor manufacturers to get the most size efficient solutions possible.”

Eieland also commented on low geometry processes, noting that refinement of existing technology may very well be sufficient.

“We don’t think we want to go to 55nm because leakage at that node will be significant. Processes in the range from 100nm to 150nm may well be suitable, with one more product generation needed to evolve the low power aspects,” he concluded.

SAM D20 hits EDN’s Hot 100 list

Atmel’s SAM D20 microcontroller (MCU) was recently spotted on EDN’s 2013 Hot 100 Products list. Based on ARM’s powerful Cortex M0+ core, the SAM D20 builds on decades of innovation and experience in embedded Flash microcontroller (MCU) technology. Indeed, Atmel’s SAM D20 lineup sets a new benchmark for flexibility and ease-of-use, while combining the performance and energy efficiency of the ARM Cortex-M0+ core with an optimized architecture and peripheral set.

“We’ve learned a lot about microcontrollers (MCUs) since Atmel launched the first 8051 micro in 1995 and the first AVR in 1996,” Atmel Sr. Product Marketing Manager Andreas Eieland (@AndreasMCUguy) told ARM’s Andrew Frame in July.

“A lot of this know-how is included in the new SAM D20 family: from simple things that make the devices easy to develop with like making the devices pin and code compatible, to more advanced system integration technologies.”

According to Eieland, there are a number of reasons why Atmel decided to move forward and bring a Cortex-M0+ based family to the market.

“First of all, we are a dedicated ARM partner and already have Cortex-M3, Cortex-M4 and Cortex-A5 products available, as well as products based on the ARM9 and ARM7 cores, so ensuring a complete ARM portfolio for our customers by extending the product offering downwards with a Cortex-M0+ was a natural thing to do,” he said.

“Secondly, the Cortex-M0+  market space is growing and we want to make sure that those developers who need more computational power than what you find in an 8 or 16-bit solution can find a product fit with Atmel. And last, but certainly not least, we are confident that mixing our AVR knowledge with an industry standard core allows us to bring a really good, unique and easy to use product to the market.”

As we’ve previously discussed on Bits & Pieces, Atmel’s SAM D20 family is ideal for a wide range of low-power, cost-sensitive industrial and consumer applications including board management controllers, GPS trackers, optical transceivers, appliance UI control units and intelligent remotes.

According to Atmel engineering manager Bob Martin, the SAM D20′s power-saving techniques include an event system that allows peripherals to communicate directly with each other without involving the CPU – with SleepWalking peripherals waking the CPU only upon a pre-qualified event.

“In terms of peripheral flexibility, a serial communication module (SERCOM) is fully software configurable to handle I2C, USART/UART and SPI communications,” he explained. “Meaning, with multiple SERCOM modules on a device, designers can precisely tailor the peripheral mix to their applications.”

Meanwhile, the SAM D20′s QTouch Peripheral Touch Controller offers integrated hardware support for buttons, sliders, wheels and proximity – as well as supporting both mutual and self-capacitive touch (without the need for external components), along with noise tolerance and self-calibration.

Additional key hardware specs include high-precision, 12-bit analog and internal oscillators; 8 16-bit timer/counters; 32-bit real time clock and calendar; real-time performance; peripheral event system, as well as flexible clocking options and sleep modes.

As noted above, the SAM D20 lineup boasts 6 serial communication modules (SERCOM) that can be configured to act as an USART, UART, SPI or I2C. On the scalability side, Flash memory densities range from 16KB to 256KB, with devices available in 32-, 48- and 64-pin QFP and QFN package options.

“In a nutshell, the SAM D20 family extends the lower end Atmel Cortex portfolio, closing the gap between the AVR XMEGA and the Cortex-M3 and Cortex-M4 products,” Martin continued. “The SAM D20 – the first series in this new family – offers 48MHz operation (1.77 CoreMark/MHz), single-cycle IO access and supports a pin-toggling frequency up to 24MHz along with an 8-channel event system. In terms of low-power sipping, we’re looking at <150µA/MHz, ~2µA RAM retention and RTC as well as options between internal and external oscillators and on-the-fly clock switching.”

Interested in learning more? Additional information about Atmels’ s SAMD20 MCU series can be found here.

Atmel @ 2013 World Maker Faire: Day 2

On day one of the 2013 World Maker Faire in NYC, Atmel showcased a number of uber-cool exhibits and demos, including Hexbugs, the wildly popular Makerbot 2 3D printer, Pensa, ArduLab and Fuzzbots.

Atmel’s booth in the Arduino pavilion continued to draw large crowds on day two of the Faire, with 12-year-old Maker and CEO Quin Etnyre proudly showing off the Educator’s Choice award and open source maven Eric Weddington displaying his Editor’s Award for a slick bunny suit demo of how Atmel AVR MCUs are made, from start to finish.

Meanwhile, Andreas Eieland (aka Atmel’s “MCU Guy”) talked a little SAM4N with attendees, while Atmel’s Bob Martin offered up some more Hexbug hacking to eager booth visitors.

Martin later took a break from the Atmel booth to give an electronics presentation titled “Prototyping is as Easy as Uno, Due, Tres.”

Although the 2013 World Maker Faire may be drawing to a close, Atmel continues to challenge Makers, designers and engineers to develop new AVR-powered gadgets and gizmos with commercial potential.

So do you think you have what it takes to be a Master Maker?

If you do, be sure to check out Atmel’s ongoing AVR Hero Maker Faire Contest. We’ll feature the projects and the people will vote, with the Master Maker receiving a $1,000 cash prize, one-year discount on Atmel products, four tickets to upcoming (local) Maker Faires and some cool Atmel swag!

Chalk Talk with Atmel’s MCU maestro

Connecting your device to the rapidly expanding Internet of Things (IoT) opens up a wide world of potential new capabilities. In this episode of EE Journal’s Chalk Talk, Amelia Dalton chats with Andreas Eieland (Atmel) about some amazing new devices that can dramatically simplify the task of getting your next design into the IoT party.


As Eieland notes, the first ARM Cortex-M0+ powered lineup from Atmel is the general purpose SAM D20 family – ranging all the way from 32 pin devices with 16KB of embedded Flash to 64 pin 256KB devices.

“We have learnt a lot about microcontrollers (MCUs) since Atmel launched the first 8051 micro in 1995 and the first AVR in 1996,” Eieland explained. “A lot of this know-how is included in the new SAM D20 family: from simple things that make the devices easy to develop with like making the devices pin and code compatible, to more advanced system integration technologies.”

As previously discussed on Bits & Pieces, the Internet of Things (IoT) refers to a future world where all types of electronic devices link to each other via the Internet. Today, it’s estimated that there are nearly 10 billion devices in the world connected to the Internet, a figure expected to triple to nearly 30 billion by 2020.

According to lead IDATE analyst Samuel Ropert, the IoT actually aims to go beyond M2M by enabling any object to connect and leverage the Internet (Internet of Objects – IoO) even if it does not contain the electronics required to connect directly to the Internet; it connects to the internet with the use of an intermediate device.

“[Based on] this definition, 15 billion things (machines, connected devices and objects) were connected to the Internet in 2012, up from 4 billion in 2010. In 2020, there will be 80 billion where IoO will represent 85% of the total IoT, ahead of communicating devices with 11% and M2M with only 4%,” Ropert added.

An MCU or MPU, that is the question: Part 2

In part one of this series, Bits & Pieces discussed a number of differences between an MCU and MPU, including memory and power consumption methodology. In part two of this installment, we take a closer look at processing power, UI, TFT controllers, connectivity and real-time/deterministic behavior.


As previously discussed on Bits & Pieces, an ARM Cortex-M4-based microcontroller such as Atmel’s SAM4 MCU is rated at 150 DMIPS (Dhrystone MIPS ) while an ARM Cortex-A5 application processor (MPU) such as Atmel’s SAMA5D3 is capable of delivering up to 850 DMIPS.

“One way of estimating the DMIPS required is by looking at the parts of the application that may be performance hungry. Running a full operating system (OS), such as Linux, Android or Windows CE would demand at least 300 – 400 DMIPS,” Frédéric Gaillard, product marketing manager and Andreas Eieland, senior product marketing manager, told Bits & Pieces.

“For many applications, a straightforward RTOS might suffice and an allowance of 50 DMIPS would be more than adequate. Using an RTOS also has the benefit that it requires little memory space; a kernel of just a few kB being typical. Unfortunately, a full OS demands a memory management unit (MMU) in order to run; this in turn specifies the type of processor core to be used and require more processor capability.”

Gaillard and Eieland also noted that DMIPS allowance needs to be reserved on top of any OS and other communication and control tasks for running applications that are more number-crunching intensive enough. Meaning, the more numeric-based the application, the more likely a MPU is required.

The user interface (UI), say Gaillard and Eieland, is also a serious consideration for engineers, whether the intended application is targeted at consumer electronics or industrial automation. Indeed, consumers have grown accustomed to colorful and intuitive graphical UIs, with industrial applications increasingly using this method of operator interaction (although the operating environment can limit how much this is warranted).

“For the UI there are a number of factors. Firstly, is a processing overhead required? For a UI library such as Qt, which is widely used on top of Linux, an overhead of 80 – 100 DMIPS might suffice,” the two explained.”The second factor is to do with the complexity of the UI. The more you have animations, effects, multimedia content, the more changes are applied to the image to be displayed, the more processing power and memory you need.”

Of course, requirements do scale up with the resolution, which is why UI-centric applications are probably best suited for an MPU. On the other hand, a simpler UI with pseudo-static images on a lower resolution screen can easily be addressed by an MCU. Indeed, MPUs typically include an embedded TFT LCD controller, while very few MCUs are packaged with this feature. Meaning, the TFT LCD controller, along with a number of external driver components, have to be added externally to MCUs.

“Yes, some Flash MCUs are now hitting the market with TFT LCD controllers embedded, although there still must be enough embedded SRAM memory available to drive the display. For example, the QVGA 320 x 240 16-colour format requires 150 kB of SRAM to feed and refresh the display,” Gaillard and Eieland noted.

“This is a fairly high amount of SRAM to dedicate; so extra memory might be required – further adding to the BOM and bridging the gap with the MPU solution. More complex and advanced graphical UIs, especially using screens larger than 4.3-inches, would stipulate an MPU. If MPUs are seen to dominate when it comes to run a UI on a color TFT screen then MCU are the kings for segment or dot matrix LCD control and other screens with serial interfaces.”

In short, the decisions involved in selecting either an MCU  or MPU-based approach are varied, with engineers carefully weighing a number of factors, including performance, capability and BOM (budget).

Broadly speaking, MCUs  tend to be used in cost-optimized solutions where a tight control of BOM and power saving is essential. MPUs are typically chose for functionally, as well as rich and high performance applications. In contrast, MCUs tend to be deployed in ultra low power applications such as remote controls, consumer electronics and smart meters where the design emphasis puts longevity of battery life and none or little UI interaction. And lastly, MCUs are also used where a highly deterministic behavior is needed, while MPUs are ideal for OS-based industrial and consumer applications that might be compute intensive, requiring multiple high-speed connectivity or a rich UI.

“Selecting a vendor offering highly compatible MCU  and MPU products where you can easily migrate up and down and maximize software reuse provides the best return on investment over time,” Gaillard and Eieland added.

An MCU or MPU, that is the question: Part 1

Selecting the most appropriate device (an MCU or MPU) for a new project or design can be somewhat daunting. Indeed, engineers typically analyze a wide range of variables, including price, performance and power consumption.

To make the process easier, we will examine some of the primary differences between an MCU (microcontroller) and MPU (microprocessor).

“Typically, an MCU uses on-chip embedded Flash memory in which to store and execute its program,” Frédéric Gaillard, product marketing manager and Andreas Eieland, senior product marketing manager, told Bits & Pieces.

“Storing the program in this way means that the MCU has a very short start-up period and can be executing code very quickly. The only practical limitation to using embedded memory is that the total available memory space is finite. Indeed, most Flash MCU devices available on the market have a maximum of two Mbytes of program memory and, depending on the application, this could prove to be a limiting factor.”

In contrast, MPUs are not limited by memory constraints in quite the same way, as they employ external memory to provide program and data storage. The program – typically stored in non-volatile memory such as NAND or serial Flash – and is loaded into an external DRAM at start-up and subsequently commences execution. On a practical level, this means the MPU will not be up and running as quickly as an MCU, although the amount of DRAM and NVM engineers can connect to the processor is in the range of hundreds of Mbytes and even Gbytes for NAND.

Another notable difference between MPUs and MCUs is power consumption methodology. By embedding its own power supply, an MCU is fine with just one single voltage power rail. However, an MPU typically requires several different voltage rails, prompting the use of additional on-board power ICs/converters. And while MPUs do have low power modes there are not as many or as low as the ones you would find on a typical MCU.

“With the external hardware supporting an MPU has an added factor, putting an MPU into a low power mode might also be slightly more complex,” the two explained. “In addition, the actual consumption of an MCU is magnitudes lower than an MPU, in low power mode for example with SRAM and register retention, you can consider a factor 10 to 100. Obviously this is directly related to the amount of RAM an operating system requires and therefore to be powered to resume operation instantaneously.”

Clearly, design specs are critical when it comes time for an engineer to select an appropriate device for a specific application. For example, is the number of MCU peripheral interface channels sufficient? Do marketing specifications stipulate a user interface (UI) capability that is simply impossible with an MCU due to a lack of on-chip memory and performance?

“When embarking on the first design engineers know it is highly likely there will be many product variations,” said Gaillard and Eieland. “As such, it is very possible a platform-based design approach will be preferred. This would stipulate more ‘headroom’ in terms of processing power and interface capabilities in order to accommodate future feature upgrades.”

Want to learn more about the differences between MPUs and MCUs? Stay tuned to Bits & Pieces for part 2 of “An MCU or MPU, that is the question.”

A closer look at Atmel’s Peripheral Event System

As previously discussed on Bits & Pieces, Atmel recently introduced the SAM D20 MCU, an extensive product lineup based on ARM’s Cortex -M0+.

The SAM D20 boasts a number of power-saving techniques, including an event system that allows peripherals to communicate directly with each other without involving the CPU or bus resources. This is known as the Peripheral Event System.

According to Andreas Eieland, Sr. Product Marketing Manager at Atmel, the Peripheral Event System can best be described as a routing network independent of the traditional data bus paths. Meaning, different triggers at the peripheral level can result in an event, like a timer tick triggering a reaction in another peripheral.

“Comprising 8 independent channels, the Event System offers a fixed latency of 2 cycles. Without any jitter it is a 100% deterministic method and a perfect fit for real-time applications,” Eieland explained.

“No events are lost and they are handled at a peripheral level in two cycles, even if the CPU is performing a non maskable interrupt. Traditionally the way of handling actions for a low power application would be through the use of interrupts, although they wake up the CPU.”


To better illustrate the advantages of an Event System, Eieland cited an example of a motor drive application using PWM.

“To detect erroneous situations, many motor applications use an analog comparator or ADC to measure the current going into the motor drive, in an over current situation you want to shut down the PWM channels driving the motor as soon as you can to prevent permanent damage to the circuit and for safety reasons,” he said.

“Without an Event System the overcurrent situation will trigger an interrupt, but the interrupt service request might be delayed if the CPU is performing other higher priority tasks. Using the Event System you can connect the analog comparator or ADC directly to the timer and always shut down the timer in two cycles, regardless of what the rest of the MCU is doing.”

Although Peripheral Event capabilities are useful on many different levels, the primary advantages of such a feature include minimizing power consumption, optimizing the off-loading of routine tasks from the CPU and achieving a totally predictable reaction time.

Additional information about Atmel’s Peripheral Event System can be found here.

The Atmel-ARM connection

Atmel currently offers the broadest portfolio of MCUs (microcontroller units) based on the two most popular 8- and 32-bit architectures – AVR and ARM. 

“Flexible, highly integrated Atmel ARM-based MCUs are designed to optimize system control, user interface (UI) management and ease of use,” Atmel Digital Marketing Manager Tom Vu told Bits & Pieces.


“Indeed, the ARM Cortex-M3 and M4 based architectures share a single integrated development platform (IDP)—Atmel Studio 6. This platform provides time-saving source code with more than 2,000 example projects, access to debuggers/simulators, integration with Atmel QTouch tools for capacitive touch applications and access to the Atmel Gallery online apps store for embedded software or extensions.”

Vu also noted that Atmel’s ARM-based MPUs range from entry-level devices to advanced integrated devices with extensive connectivity, refined interfaces and a plethora of security options.

“Whether you are working on new, existing or legacy designs, a wide range of Atmel ARM-based devices provides the latest features and functionality. These devices also feature the lowest power consumption, a comprehensive set of integrated peripherals and high-speed connectivity,” he added.

As previously discussed on Bits & Pieces, Atmel’s SAM4 and SAMA5D3 ARM-based MCUs are used to power a number of industrial and consumer devices including thermostats, remote process control nodes, smart glucose meters, gateway concentrators, bar-code scanners and portable outdoor equipment.


Earlier this week, Atmel rolled out its SAM D20 MCU, a comprehensive product lineup based on ARM’s Cortex -M0+. Essentially, the new microcontroller series combines the performance and energy efficiency of an ARM Cortex-M0+ based MCU with an optimized architecture and peripheral set and 8-bit AVR for ease of use – enabling Atmel to reach new markets.

According to Atmel engineering manager Bob Martin, the SAM D20 offers a “truly differentiated” general-purpose lineup that is ideal for a wide range of low-power, cost-sensitive devices, including GPS trackers, appliance controllers, intelligent remotes and optical transceivers.


“The SAM D20’s power-saving techniques include an event system that allows peripherals to communicate directly with each other without involving the CPU, while SleepWalking peripherals wake up the CPU only upon a pre-qualified event, reducing overall power consumption,” Martin told Bits & Pieces.

“In terms of peripheral flexibility, a serial communication module (SERCOM) is fully software configurable to handle I2C, USART/UART and SPI communications. Meaning, with multiple SERCOM modules on a device, designers can precisely tailor the peripheral mix to their applications.”

Bits & Pieces also asked Andreas Eieland, Atmel Sr. Product Marketing Manager, to describe his favorite SAM D20 features.

“Personally, I like the Peripheral Touch Controller and SERCOM. The PTC is by far the easiest way to add capacitive buttons, sliders wheels and proximity to an application. Plus, there is no need for external components and very little SW overhead, as the module is self calibrating – supporting up to 256 channels,” said Eieland.

“Previously, if you wanted 4 UARTs you had to buy a device equipped with 4SPIs and 4 I2Cs. However, the SAM D20’s SERCOM module allows users to configure the SERCOMs to what they need, meaning devs no longer have to pay for serial interfaces they do not use. Lastly, the SERCOM module is fitted with a multiplexer, offering flexibility in regards to what pin different signals are outputted on, thereby simplifying board layout and reducing board area.”

Meanwhile, Brian Hammill, Atmel Sr. Staff Field Applications Engineer, said he most appreciates the SAM D20’s high end analog to digital converter feature.

“The hardware averaging feature facilitates oversampling, making high resolution at sample rates that apply to many real-world sensor requirements reality without extra software overhead,” he explained,


“Sensor nodes in the Internet of Things (IoT) collectively generate a tremendous amount of data. When you’ve got that much data, it had better be good. And reducing the CPU cycles cuts energy use, especially important in applications that use energy harvesting or are battery powered.”