Keeping consumables real

---

The most cost-effective and secure way to keep things real is through symmetric authentication without secret storage on the host using a fixed challenge.

---

With the ever present threat of counterfeiting, having a cost-effective and highly-secure way to ensure that a consumable product is real is a great idea. In fact, there is a proven industry standard approach to apply sophisticated cryptographic engineering and mathematics to fight counterfeiting; namely, crypto elements like the Atmel ATSHA204A device.

Crypto elements can attach to a consumable good, such as the classic example of an ink cartridge, even without being soldered in. The device can be glued directly outside of the product. When the ink or other consumable is inserted into the host system (where the MCU is), the crypto element makes contact and the host is able to communicate with the item to validate whether or not it is real. This is called authentication.

The most cost-effective yet secure way to authenticate is through symmetric authentication without secret storage on the host using a fixed challenge.

With symmetric authentication, a client and the host run the exact same calculation on each side, and if the client (the consumable) is real, then the results of those calculations (called the “responses”) will match. There is a way to go about using a very inexpensive MCU without running the crypto calculations within the host side’s MCU. That is where the concept of fixed challenge comes into play. The idea of a fixed challenge is that the calculation done for the host is conducted ahead of time, and the challenge/response pair from that calculation is loaded into the host.

The fixed challenge method is ideal when certain considerations are in play, such as the folowing:

1. Very limited processing power (e.g. low-cost MCU)
2. Abundance of available memory to easily store challenge-response pairs (e.g. in a smartphone)
3. Need to get something out quickly or temporarily (e.g. time to market)
4. Need a very low cost on the host (e.g. can’t afford adding a key storage device)
5. Desire to not store a secret key in the host

So, how does a fixed challenge work? Like with other challenge-response operations, the process starts with the host controller sending the client a numerical challenge to be used in a calculation to create a response, which then gets compared to a “response” number in the host. What makes this “fixed” is that, because there is no crypto device in the host to generate random numbers (or make digests using hashing algorithms), the challenge cannot be random. That means that the challenges and their corresponding responses must be pre-calculated using the client’s secret key and the challenge and response pair loaded into the memory of the host. This can be looked at as effectively time-shifting the calculations used for authentication.

Let’s look at an example using the ATSHA204A installed in the client.

Step 1: In the factory when the host manufactured challenges are loaded into the host MCU memory together with a response that is calculated by hashing the client’s secret with that challenge.

Step 2: When the consumable is inserted into the host machine out in the field, the host MCU will ask the client (consumable) to prove it is real by sending it the preloaded challenge.

Step 3: The client will then run the hash algorithm on that challenge number using its stored secret key to generate a response, which it sends back to the host.

Step 4: The host will compare the response from the clients with the preloaded response value stored in its memory.

Step 5: If the client is real, the response from the client (which is the hash value based on the secret key and the challenge) will be the same as the response value that was preloaded in the host.

Since each host is loaded with a different challenge/response pair, each product that the host is incorporated into is then unique by definition. Cloning beyond only one copy is impossible; thus, this is a highly-secure and very cost-effective technique as it can be easily implemented with very inexpensive MCUs.

This approach can be used for firmware protection and designs with no secrets in the host (as noted), as well as be implemented with very low-cost MCUs that do not have the processing power to run the hashing algorithms.

The many benefits of fixed challenge authentication:

• Symmetric authentication is fast
• No secrets in the host
• Can use low-cost MCU of host because less computation is needed for a fixed challenge
• Prevents cloning
• Protects investments in firmware
• Enhances safety
• Protects revenue stream
• Protects brand image
• Better control of the supply channel

Atmel crypto element devices — including ATSHA204A, ATECC108A, ATECC508A and ATAES132A — implement hardware-based key storage, which is much stronger than software based storage due to the defense mechanisms that only hardware can provide against attacks. Secure storage in hardware beats storage in software every time. Adding secure key storage is an inexpensive, easy, and ultra-secure way to protect firmware, software, and hardware products from cloning, counterfeiting, hacking, and other malicious threats.

Neobase is a cloud-free private social network device

---

Neobase is turning the concept of a social media upside down, shifting the balance of ownership, control and security back to users. 

---

It’s nearly impossible to envision a time when social media didn’t exist. From how we receive our news to how we engage with friends and family, sites like Facebook and Twitter have truly revolutionized the way in which we interact with the world around us. Given our modern-day state of interconnectivity, it seems like just about everything we see, do and feel is shared online. However, as recent breaches have made apparent, do we truly know who has access to all of that content? Fortunately, the Neone crew has designed a solution that hopes to rid this problem.

Billed as the world’s first private network device, Neobase is an encrypted, cylindrical gadget that allows owners to create an online community that only they control. Sharing with friends and family is seamless as users decide exactly what to share and who to share it with. And unlike many services before, the unit doesn’t rely on the cloud. Instead, all posts, comments, links, photos and files shared are stored on a user’s Neobase. This keeps information protected as it never has to pass through a website, a third party vendor or the cloud — and theoretically, cuts out the middlemen. What’s more, an Atmel ATSHA204 crypto engine plays an integral role in establishing its secure architecture.

“This means that no one — not even us here at Neone  — can know anything about you, your activities or what you share. Neone doesn’t host or operate your social network. You do,” the team writes.

Neobase’s plug-and-play functionality makes it easy to install and even easier to use. To get started, owners simply connect the device to their in-home network via Wi-Fi or Ethernet and begin assigning up to five family and friends as additional users. You can even connect with other Neobase users in the Neone Network if you choose.

As posts are created, users can pick and choose specific friends from their network that will be able to see the content and any links, photos and files associated with it. Neobase then syncs directly to the other Neobase units that information is being shared with, and only relays the specific content that has been selected.

Beyond that, the folks at Neone have developed the device so that, no matter where a user is located and how they are connected while on-the-go, the Neobase mobile app uses a fully-encrypted connection that links directly to their respective Neobase. Once again, no cloud required.

“The decentralized, peer-to-peer architecture of the Neone Network is a fundamental change in how your activities and information are stored and shared on the Internet, making it the heart of the Neobase’s security and privacy,” the team adds. “We’ve added additional security technology and encryption throughout the Neobase. Your computer or mobile device uses a secure SSH tunnel to connect to your Neobase and the Neone Network, which is much more secure than a browser with SSL.”

Given its sleek, polished white design and compact size (6″ tall with a diameter of 3.5” and weighs only 15 ounces), Neobase will be a welcomed, aesthetically-pleasing addition to any living room, office or dorm room. The device itself offers one Terabyte of storage and a USB port for expanding storage. The drive runs a customized version of Linux to support its social networking functions.

Sound like something you and your family would like to have? Neobase is currently live on Kickstarter, where its team is seeking $100,000. If all goes to plan, shipment is expected to begin by August 2015.

IT cloud vs. IoT cloud

---

Kaivan Karimi, Atmel VP and GM of Wireless Solutions, shares the top 10 factors to consider when transitioning from IT cloud to IoT cloud.

---

In mid-2013, the buzz phrase “Internet of Things,” also known as the “IoT,” set the technology world on fire. As a result of this craze, a lot of products that were developed for completely different end applications changed all their marketing collateral overnight to become IoT products. We saw companies that added the acronym “IoT” to the title of every executive and gadgets that became a part of an IoT enablement ecosystem. New tradeshows claimed their authoritative position on IoT, and angel investors and venture capitalists started IoT funds feeding incredible ideas — some which reminded me of the late 1990s bubble when Lemonade.com was funded. New standard bodies were formed around provisioning IoT devices, and all of a sudden, overnight, most of us in the technology community became IoT experts.

Cloud companies are not an exception. While the physical infrastructure of the cloud didn’t change, the platform and software services that were developed for enterprise IT management and mobility apps support became IoT PaaS & SaaS platforms with claims of “IoT compliance.” By late 2013, at an IoT event in Barcelona, every keynote not only talked about the “metaphorical pyramid” of Infrastructure as a Service (IaaS), Platform as a Service (PaaS) and Software as a Service (SaaS), but almost every keynote talked about “Everything as a Service (EaaS)” thanks to IoT.

With so much hype and noise, it is hard to separate fact from fiction — unless you dig deep, really deep. This fuzziness is caused by the breath of IoT and the many vertical markets it encompasses, covering all aspects of life as we know it. And each vertical has its own unique “things,” so one size doesn’t fit all from a device perspective, requiring different types of standards and transport layers with silicon and software infrastructure to support this vast frontier. What has further muddied the water is that many large industry players look at IoT as an inflection point that they can transform themselves to something else and get into other businesses. Because of this, these players are looking at their current assets and are defining the infrastructure required for IoT differently than what logically and technically makes sense. For companies that have no play in hardware or software for the data centers, they publicly promote that the majority of the data processing should be done in other parts of the network (“closer to the source”). And, while the others promote just the opposite, a third group advocates that much of the processing should be done directly by the hierarchy of smart gateways boxes in the customer premises, along with everything in-between. The same goes for the choice of RF communications protocols, gateways, definition of things, provisioning schemes, etc.

A great example of what gets heavily promoted by one of the biggest industry players is calling IoT an “always ON revolution” and allowing sensor data collected at the edge/sensing nodes (thing side) to ALWAYS be sent to the cloud. This method requires a lot of bandwidth and storage capacity to collect data in the cloud, and encourages the promotion of their passive big data analytics capabilities to process this volume of data in the cloud. Clearly they sell hammers here, and see everything in the world as a nail. In reality IoT is a “mostly OFF revolution,” with significantly less data created than portrayed, and few of that data will make it to the cloud. For instance:

1. A door or a key lock is mostly sleeping, until a sensor triggers a wake-up command during an opening or proximity event, in which case it communicates a few bytes of data to a gateway and then goes back to sleep.
2. The temperature sensors on a bridge wakes-up every so often to report temperature fluctuation to the gateway on the side of the road, and report if the bridge is frozen and then telling the department of transportation to send the sand trucks to avoid accidents.
3. The seismic sensors on the A/C unit in an office building located in Texas monitoring of the sound of the motor every 2 hours. If the motor sounds as if it will be breaking down in a couple weeks, the sensors inform the building manager to call a technician to fix what is going bad, so that they will not be stuck without air conditioning in the middle of July.
4. The ethylene gas sensors (ripening phytohormone of fruits and plants) on fruit containers in the back of an eighteen wheeler wake up every 30 minutes and send the data to the gateway in the cabin of the truck. These signals predict the decay rate of the fruit and allow the driver to change the destination to a close by city if needed, and give some additional shelf life to the fruit, or allowing the driver to send the fruits straight to the jam factory, avoiding fuel waste of carrying a bad cargo.

In each of the aforementioned cases, and in other examples similar to these, the things (fruit container, A/C unit, bridge, home door, etc.) spend a majority of their time sleeping and only wake up based on an event trigger or predetermined wake up time based on programmed policy. This is the only way these devices can operate on batteries for years of usage. How many bytes (not mbps or even kbps) of data is really required to report those events? Would all of these events be worthy of sending to the cloud? In fact, the local event processing and analytics engine running on the local gateway will determine what will go to the cloud and only the exception events (door is open, fruit is going bad, motor is going to break down, bridge is frozen, etc.) will go to the cloud right away. But, as long as everything is normal (within policy range events), it will get registered on predetermined intervals (e.g. once every 24 hours) and the meta data will get uploaded to the cloud. Even if video capture was involved, no more than 2Mbps of bandwidth is needed.

Based on my experience with the analysis of multiple large enterprise campuses with many buildings, without video for IoT-type services, only an aggregate level of 15Mbps bandwidth max is required to fully support this type of IoT communication to the cloud for provisioning services. So one should question the folks who promote the fallacy that all types of applications, things will always be ON and lots of bandwidth will be needed. What’s in it for them to portray IoT in this manner? Of course if you are considering an enterprise campus full of smart devices with people moving massive amount of data with “chatty and persistent communication agents”, then you will need a lot more than 15mbps of connectivity to cloud, for sure. Could it be these folks are confusing an IT infrastructure with an IoT infrastructure?

For a comprehensive IoT implementation, a system-level approach is required to cover the tiniest edge/sensing nodes (things), to various types of gateways, all the way to the cloud and data centers, applications and service providers. These include data analytic engines embedded both on premise and in the cloud with a variety of SDKs and communication agents, data caching and bandwidth management as different layer and levels of hierarchy, etc. There aren’t many companies in the world that cover all of these (single-digit) items. Even if they do, these companies still require partnerships with the gadget/things side companies. Therefore, when someone claims that they are a one-stop shop, they can either: support an existing infrastructure of things to a cloud and add a new twist to it (subset of most IoT verticals), OR their system is not as comprehensive as they claim, OR ultimately a combination of both.

Not to mention, at this moment we are exclusively dealing with silo-ed clouds, and silo-ed IoT systems. While an ecosystem of cloud (cloud of clouds) is in a nascent stage for some companies, it is far from a true IoT cloud ecosystem that it will become in the near future.

The IT cloud ecosystem (versus the IoT cloud ecosystem) has had a journey of its own in the past few years. This ecosystem has shown signs of success as originally predicted with the technology distributed to provide a virtually seamless and infinite environment for communications, storage, computing, Web and mobile services, analytics, and other business uses. The cloud benefit model has come to fruition, with many examples of upfront CAPEX largely minimized or eliminated. This includes increased flexibility and control to scale users and the ability to add functionality by various organizations on demand, with the added pay-as-you-go benefit. Cloud providers have taken over the responsibility of IT requirements for many organizations, and have become vital business and channel partners.

That said, the fundamental question still remains: Is the traditional IT cloud and its ecosystem the same as an IoT cloud and its ecosystem?

The answer: While 60-70 percent is the same, a 30-40 percent difference can kill your IoT roll-out and make a seemingly IoT-ready cloud almost useless for your applications.

The differences are present throughout the full end-to-end system, from the “thing” side, all the way to the data centers on the cloud side. The traditional IT cloud, web or mobility applications cloud mirrors much bigger devices with more resources on the cloud side. Over the last couple of years, a “thing” for the traditional cloud system consisted of a computer, a vending machine, a car, a gateway in customer premise, or a smart device (laptops, tablets, Smartphone, etc.). These devices are typically connected to the cloud via direct cellular links, a cellular (WAN) + Wi-Fi (LAN), or Fiber (WAN) + Wi-Fi (LAN). With the new generation of IoT “things,” you can find much more resource-constrained devices such as small battery operated sensors on doorways to keep track of people entering through the back gate of the house, battery-operated seismic sensors on roadway infrastructures (bridges, etc.), or any of the examples earlier. Instead of 20 smart devices in an office that are plugged into the wall outlet or through a large battery capacity recharging on a regular basis, you will be dealing with 500 different types of sensors and things covering that office. With multiple offices, 1000s of things at the same time, most of which are powered by batteries for years (4-5 years of battery life in consumer IoT, and 8-12 years of battery life in industrial IoT). Some of these things have a small 8-bit MCU as its brain, with very little memory and other resources, and may be hiding behind layers of gateways, relays, switches, even other things, in sleepy networks. The communication link when available (remember that they are mostly in an off state), may have very little bandwidth, and communication may go through multiple hops in mesh networks. A “Chatty” communication system that pings on the things on regular basis defeats the purpose here.

The important thing is to remember that a system needs to be fully extendable and scalable not just on the cloud side, but also on the link side from the cloud to the things–and finally on the thing side. You also need scalable data capture and aggregation to go along with a secure communication system. If you are targeting a consumer application, then a solid mobile application development platform working with your popular Smartphone operating system is a basic requirement, meaning you need to rewrite your middleware to become more agile, scalable, and be able to manage many more things simultaneously. You also need to rethink your whole communication topologies of the past. Lastly you need to pay more attention to your analytic engines and applications development environment, and depending on your IoT application, it may require completely different visualization tools and business models.

Here are some factors that an IT cloud provider transitioning to an IoT cloud provider needs to consider:

• Understand the verticals you target; become a one-stop shop for a given vertical. In IoT, one size does not fit all. Understanding a vertical includes the evolution of that vertical and future business models that need to be considered. For example, if you are targeting the tracking of people in a hospital and their location at any given time, in the future that group would require wearables with biometric sensors, and their vital statistics would also need to be monitored. The expectation would be that your service can also cover the tracking of biometric sensors, which are usually battery-operated constraint devices with minimal bandwidth. Working with one PaaS or SaaS supplier for managing one set of its assets in the same premise and another cloud provider for a separate set of assets is not an option. The issues to consider include the protocols, networks, bandwidth management and transport technologies your IoT cloud framework would need to support.

• Scalable data analytics and event processing engine is a must-have as the majority of the IoT value creation comes from the data analytics, and “data capital” is where the differentiation will come from. Do you have the right analytics engine on both the cloud side as well as the premise/gateways? The new in-memory streaming technologies which change the rate we can act on data will be required for some IoT applications. Hence the traditional extraction, transformation and loading (ETL)will give way to just in time (JIT) methodologies (real-time vs. batch-oriented). Can you manage fast/streaming data analytics processing for applications where extremely fast processing of (near) real-time data is required? For instance, in tele-health and elderly monitoring where passive data analytics in the cloud is not adequate, and local fast data analytics running on the local smart gateway is required to report a heart attack, or a fire in home automation, etc. Also it is imperative that you find a service provider for a given vertical—if you are not a service provider, partner with one—so that your event processing and data analytics engines are tuned for specific use cases and business logic. If your analytics engine only provides insight into the visibility or availability of a limited set of parameters in the network, work with a partner that brings the rest.

• Know the specific type of data required to monitor/gather, the insight required for your customers. That means developing a diverse set of device data models for specific functionalities. Don’t try to be the Swiss Army Knife of the IoT cloud providers. Remember, while a Swiss Army Knife can perform many functions, they are not good at doing anything well. Understanding the verticals you need to support (item number 1) will also help you with this item. For certain applications, before the data sets get processed by analytics and visualization tools, it gets combined with external algorithmic classification and enrichment tools. This increases productivity and ease-of-use dramatically (e.g. user will know where the water tables are before drilling for a well, or what the maps of other distribution centers are before redirecting a cargo).

• Develop a fully modularized end-to-end system. As most large OEMs may already have their own branded cloud and would only want to use a part of the functionality you offer. Arm yourselves with well defined APIs, and firewall-friendly adaptive connectivity architecture and become comfortable with working with your customers’ infrastructure, analytics engine, applications, visualization tools, things, etc. They may only be interested in your communication system. Or, ask for a mix of capabilities. The more flexible your approach, the better you can customize your offerings to their needs. On the cloud side, the formation of the cloud ecosystem (cloud of clouds – server to server(s) communication) is right around the corner. A robust ecosystem is at the heart of the IoT cloud management.

A modularized system as described above may mean a different tiered pricing approach to your business model. Flexibility needs to extend beyond your technology offerings, so be open to new business models.

• Follow the new service delivery frameworks with large ecosystems, such as the Open Interconnect Consortium (OIC), etc. Standardization will eventually dominate both the consumer and industrial IoT space. While the alphabet soup of protocols may be expanding (e.g. MQTT, XMPP, DDS, AMQP, CoAP, RESTful HTTP, etc.), standardization is also happening and provide more clarity. Standards are being developed so there are “horses for different courses.” Get used to the idea that your proprietary system of today requires an upgrade to a standard system tomorrow or your ecosystem will leave you behind. How would you change your system today with that knowledge in hand?

• Develop RF communication specialization (Cellular, WiFi, BLE, 802.15.4/Zigbee, 6LowPan, subGig, SigFox, etc), or partner with someone who has that expertise. A lot of the IT Cloud companies today have a big gap here and need to find a partner to optimize their IT Cloud to use such complex RF Communication protocols. They also need to optimize their systems based on the type of RF links and bandwidth limitations they will be using. This also affects the application development side, as such customization is essential for IoT, and what normally works for Cellular might not work for WiFi or BLE or Zigbee, etc. This is especially important to consider when it comes to target vertical markets, as different verticals might need different RF communication protocols or even multiple ones simultaneously, with all the coexistence issues that one may encounter. A semiconductor partner, who understands your IoT cloud requirements, can help you optimize your system from an RF communications and bandwidth management perspective.

• Whether you have an SDK or agent-based mechanism, implement a lightweight communication system. Typical SDKs make the development and management of mobile apps easy, but remember that your smart phone has a lot more resources on it than a tiny resource-constraint sensor feeding data into an IoT system. A lightweight SDK, or agent-based system is a lot more predictable and simpler to integrate into low memory or battery-operated devices. Lightweight agents reduce device complexity and cost and can incrementally add to their capabilities depending on where they reside on the system. Obviously the more ‘bells and whistles’ you add to your system on the thing side (number of statistics to track or alarm states), the larger footprint of your SDK or agent. As you move to gateway levels of hierarchy and have more types of mechanisms, functionalities, sensors, communications, and alarms to monitor, the size of your agent or SDK will grow. One size will not fit all, but be frugal with your application and data management. So far working with various IoT cloud ecosystem partners, I have seen SDK and agent sizes varying from 3K to 150K of memory footprint. IoT cloud journey has already started, and I have no doubt the higher end of the spectrum (and some of the intermediate steps) will be shrinking in the near future, while the caching mechanism will become more robust.

Also deploy a context-centric bandwidth management system that won’t hog the entire bandwidth for your management plane activities. The rule of thumb will tell you not to occupy more than 15% of the communication link with intermediate proxy and caching functionality.

• Pay attention to “things” with the focus on ease-of-use. That means an easy way of provisioning a device that even a nascent thing developer can follow the steps and do it on their own, regardless of the transport technology or resources available. If it takes too long, is error prone or requires an army of your developers to port and customize/optimize your agent for a particular architecture, you will be reducing your target market to only the very large OEMs. If you assume that you will be doing it for services fees, it won’t scale and you will only be targeting the large OEMs. If you partner with software services houses, you will scale better and gain additional bandwidth at a cost. And, this will still be reducing your market footprint to companies that can afford to pay for provisioning services. Why not make it easy right up front for maximum customer coverage? From the syntax of your APIs for things/sensor, to local gateways, cloud gateways, programming your agent logic and communications and service APIs, focus on simplicity, ease-of-use, and the out-of-the-box experience for your customers/developers.

• Pay attention to visualization tools and user experience in all parts of the system. “Thing virtualization and visualization,” (including elegant and robust application that turns the device data models to comprehendible information in the cloud) are great value propositions. If you are focusing on the consumer IoT verticals where smart phones will have a prominent role, include a robust mobile apps development environment. IT cloud and IoT cloud have different consumers of data, and elegant visualization features can set you apart from your competitors.

• Last but not least, do you have a robust and hardened security and authentication mechanism that works with advance encryption algorithms? Do you support both ECC and AES-128/256? How about PUF based key generation mechanism? In IoT, the stakes are very high and you need to spend more attention to the security of the system, from the tiniest resource constraint thing all the way to the cloud. Please note that the security knowledgebase between the thing developers is low at the moment, and the cloud partner needs to bring some of the competence needed as well as enforcing best practices. Some basic elements on the thing side that need to be protected include secure boot, thing authentication, message encryption and integrity, and a trusted key management and storage scheme. A semiconductor partner who understands your IoT cloud requirements can help you optimize your system from a “thing” security perspective.

The transition from the IT cloud to the IoT cloud has already started, and as the IT cloud was a journey, the transformation to support IoT applications will also be a journey. What’s the best way to go about this change? Make this a comprehensive approach that will make your IoT cloud sustainable as the market transitions forward.

X-Carve is an open-source, next-gen CNC carving machine

---

This CNC machine will let Makers carve the way they want.

---

For a couple of years, Inventables has been the CNC device of choice for Makers with their open-source, easily-modded Shapeoko 2. And while multi-axis, computerized milling machines are nothing new, the Chicago-based company continues to cater to the burgeoning DIY community with the launch of a new device. Dubbed X-Carve, the machine not only packs several upgrades from its older siblings but is entirely scalable as well.

You may recall the Shapeoko family from way back in 2011 when the concept CNC machine kit first made its Kickstarter debut. There, it well exceeded its initial goal having garnered over $11,000. This design would go on to inspire the market-ready Shapeoko 2 in 2012.

With X-Carve, Inventables brings a number of innovative elements to the CNC kit concept. Essentially, it features all the upgrades you wished the Shapeoko had, including stronger corner-mounting for increased rigidity, NEMA 23 motors and self-tapping screws. Beyond that, the latest machine uses 50% fewer parts and requires just half the build time.

“With a relentless focus on reducing the part count and improving rigidity, we designed single-piece extrusions for X‑Carve’s gantry and spindle mount. New Y-axis plates bring the spindle closer to the center, decreasing flex,” the team writes.

The kit comes in two size options — standard and large with 500mm and 1000mm rails, respectively. The workable space is about 12” x 12″x 2.7″ for the standard and 31″ x 31” x 2.7″ for the large. Inventables says the latter is even big enough to work on a full-sized longboard. What’s more, X-Carve can even be configured to any size, as long as it falls within the standard and large spectrum.

The X-Carve is also capable of creating precision parts from a wide range of materials including plastic, wood, metal, foam, cardboard and wax. Created for a workshop (and the occasional Makerspace) setting, the unit is both customizable and expandable. In other words, if a Maker already has one of Inventables previous machines, they can upgrade and scale their existing device by simply adding a few X-Carve components.

On the electronics side, the X-Carve boasts a 24VDC spindle with a single source power supply for its motor and spindle. This gives users spindle control through Gcode. The gadget is designed to be controlled using an Arduino (ATmega328) and gShield (an Arduino shield with three stepper motor drivers), but more advanced users can also leave off the controller and try their own. The open-source machine will run the Easel software along with other CAM options as well.

Interested? Good news, X-Carve will begin shipping April 30, 2015 and will begin at $799 with fully-souped up models upwards of $2,000.  Like its predecessor, it comes in kit form. An upgrade kit for the Shapeoko 2 will also be available for just $200. Until then, you can head over to its official page to learn more.

LIFX adds an affordable bulb to its smart lighting collection

---

With a retail price under $40, the White 800 is the perfect introduction to the world of smart lighting.

---

The battle for control of the burgeoning smart lighting market continues to heat up, with new products being introduced regularly by both large corporations and startups. Just this month, Philips Hue announced a pair of new solutions: the Phoenix and Go, a wireless white light lamp and a portable LED lamp, respectively. Not too far behind is Australian startup LIFX who has unveiled a new product of its own, the White 800.

The company, which was Wi-Fi-enabled lighting pioneer and one of the all-time most successful Kickstarter campaigns back in 2012 — has launched a $40 smart bulb capable of switching between both warm and cool white lights. As can be expected, the White 800 is equipped with built-in Wi-Fi technology (meaning no hub required) to allow users to control their lights, create one-touch presets and configure favorite settings, all from its accompanying mobile app.

Between the bulb’s sleek compact profile and 890 bright shining lumens (60W equivalent), the White 800 a perfect introduction into smart lighting for those looking to bring their homes into the Internet of Things era. Users can naturally wake up each morning with automatically increasing luminosity, schedule lights to turn on when upon arrival, or set the mood with a soft candle flicker.

Beyond that, owners can integrate their connected lights with IFTTT to make their own recipes pairing the lights with services such as social media, weather channels and calendars. According to LIFX, the bulb can live up to 23 years based on three hours of daily use. Those interested in installing White 800 lights in their home should head over to its official page here.

Philips Hue Go is like a portable bowl of ambient light

---

Bring this wireless lamp anywhere ‘Hue’ want to ‘Go.’

---

Since its inception, Philips Hue lightbulbs have allowed users to select the brightness and color of light they want for any room. Now, the company is taking that experience to a whole new level with its latest Hue device that lets users carry their chosen ambience around in a portable bowl-like light that can be controlled via smartphone.

Philips notes that the aptly named Philips Hue Go is designed to change the way in which light is used in the home. Unlike conventional fixed units, this one can be moved in and around a home, and serve as a “portable center piece” to let anyone experience the light that they want anywhere at anytime. It even has a battery life of up to three hours when left unplugged.

Go’s unique shape and thick-walled spherical body allows users to place it either on a flat surface facing down, facing up or tilted to one side.

“It can also be positioned in different ways to adapt to your needs; enhance a living space by positioning it to face a wall washing it with light, add ambience to an intimate dinner by placing it as a center piece on the table or focused on a piece of work by directing the light where you need it,” the company explains.

The Hue Go enables users to choose from more than 16 million colors and seven different lighting effects, ranging from functional warm white light to cool energizing daylight. It can be controlled via a button directly on the device itself or via the Philips Hue app on a user’s smartphone. As with other Hue gadgets, the Go can interact with more than 200 third-party apps, and features five new patented dynamic light effects to enrich those special moments and interaction.

Just like Philips Hue, the Go can discretely alert a user of an incoming email or change in weather via a gentle light notification, as well as enhance the TV viewing experience. Philips Hue Go works seamlessly with all Philips Hue and Friends of Hue products, and can be easily integrated into an existing network.

Looking for an ambient, portable lamp of your own? The $109 (€99.95) Philips Hue Go will be available this month in Europe and June in North America.

Atmel’s SAM L21 MCU for IoT tops low power benchmark

---

SAM L21 MCUs consume less than 940nA with full 40kB SRAM retention, real-time clock and calendar, and 200nA in the deepest sleep mode.

---

The Internet of Things (IoT) juggernaut has unleashed a flurry of low-power microcontrollers, and in that array of energy-efficient MCUs, one product has earned the crown jewel of being the lowest-power Cortex M-based solution with power consumption down to 35µA/MHz in active mode and 200nA in sleep mode.

How do we know if Atmel’s SAM L21 microcontroller can actually claim the leadership in ultra-low-power processing movement? The answer lies in the EEMBC ULPBench power benchmark that was introduced last year. It ensures a level playing field in executing the benchmark by having the MCU perform 20,000 clock cycles of active work once a second and sleep the remainder of the second.

 

ULPBench shows SAM L21 is lower power than any of its competitor’s M0+ class chips.

Atmel has released the ultra-low-power SAM L21 MCU it demonstrated at Electronica in Munich, Germany back in November 2014. Architectural innovations in the SAM L21 MCU family enable low-power peripherals — including timers, serial communications and capacitive touch sensing — to remain powered and running while the rest of the system is in a reduced power mode. That further reduces power consumption for always-on applications such as fire alarms, healthcare, medical and connected wearables.

Next, the 32-bit ARM-based MCU portfolio combines ultra-low-power with Flash and SRAM that are large enough to run both the application and wireless stacks. Collectively, these three features make up the basic recipe for battery-powered mobile and IoT devices for extending their battery life from years to decades. Moreover, they reduce the number of times batteries need to be changed in a plethora of IoT applications.

Low Power Leap of Faith

Atmel’s SAM L21 microcontrollers have achieved a staggering 185.8 ULPBench score, which is way ahead of runner-up TI’s SimpleLink C26xx microcontroller family that scored 143.6. The SAM L21 microcontrollers consume less than 940nA with full 40kB SRAM retention, real-time clock and calendar, and 200nA in the deepest sleep mode. According to Atmel spokesperson, it comes down to one-third the power of competing solutions.

Markus Levy, President and Founder of EEMBC, credits Atmel’s low-power feat to its proprietary picoPower technology and the company’s low-power expertise in utilizing DC-DC conversion for voltage monitoring. Atmel’s picoPower technology employs flexible clocking options and short wake-up time with multiple wake-up sources from even the deepest sleep modes.

ULPBench aims to provide developers with a reliable methodology to test MCUs.

In other words, Atmel has taken the low-power game beyond architectural improvements to the CPU while optimizing nearly every peripheral to operate in standalone mode and then use a minimum number of transistors to complete the given task. Most lower-power ARM chips simply disable the clock to various parts of the device. The SAM L21 microcontroller, on the other hand, turns off power to those chip parts; hence, there is no leakage current in thousands of transistors in that part.

Here is a brief highlight of Atmel’s low-power development efforts that now encompass almost every peripheral in an MCU device:

Sleep Modes

Sleep modes not only gate away the clock signal to stop switching consumption, but also remove the power from sub-domains to fully eliminate leakage. Atmel also employs SRAM back-biasing to reduce leakage in sleep modes.

Consider a simple application where the temperature in a room is monitored using a temperature sensor with the analog-to-digital converter (ADC). In order to reduce the power consumption, the CPU would be put to sleep and wake up periodically on interrupts from a real-time counter (RTC). The measured sensor data is checked against a predefined threshold to decide on further action. If the data does not exceed the threshold, the CPU will be put back to sleep waiting for the next RTC interrupt.

SleepWalking

SleepWalking is a technology that enables peripherals to request a clock when needed to wake-up from sleep modes and perform tasks without having to power up the CPU Flash and other support systems. For instance, Atmel’s ultra-low-power capacitive touch-sensing peripheral can run in all operating modes and supports wake-up on a touch.

For the temperature monitoring application, as mentioned above, this means that the ADC’s peripheral clock will only be running when the ADC is converting. When the ADC receives the overflow event from the RTC, it will request its generic clock from the generic clock controller and peripheral clock will stop as soon as the ADC conversion is completed.

Event System

The Event System allows peripherals to communicate directly without involving the CPU and thus enables peripherals to work together to solve complex tasks using minimal gates. It allows system developers to chain events in software and use an event to trigger a peripheral without CPU involvement.

Again, taking temperature monitor as a use case, the RTC must be set to generate an overflow event, which is routed to the ADC by configuring the Event System. The ADC must be configured to start a conversion when it receives an event. By using the Event System, an RTC overflow can trigger an ADC conversion without waking up the CPU. Moreover, the ADC can be configured to generate an interrupt if the threshold is exceeded, and the interrupt will wake up the CPU.

Low Power MCU Use Case

Paul Rako has mentioned a sensor monitor in his recent post in Atmel’s Bits & Pieces blog. Rako writes in his post titled “The SAM L21 pushes the boundaries of low power MCUs” about this sensor monitor being asleep 99.99 percent of the time, waking up once a day to take a measurement and send it wirelessly to a host. Such tasks can be conveniently handled by an 8-bit device.

However, moving to IoT applications, which constitute protocol stacks, there is number crunching involved and that requires a faster ARM-class 32-bit chip. So, for battery-powered IoT applications, Rako makes the case for 32-bit ARM-based chip that can wake up, do its thing, and go back to sleep. If a high-current chip wakes up 10 times faster but uses twice the power, it will still use less energy and less charge than the slower chip.

Next, Rako presents sensor fusion hub as a case study in which the device saves power by skipping the radio chip to send the data from each sensor and instead uses the ARM-based microcontroller that does the math and pre-processing to combine the raw data from all sensors and then assembles the result as a simple chunk of data.

Atmel has scored an important design victory in the ongoing low-power game that is now prevalent in the rapidly expanding IoT market. Atmel already boasts credentials in the connectivity and security domains — the other two key IoT building blocks. Its connectivity solutions cover multiple wireless arenas — Bluetooth, Wi-Fi, Zigbee and 6LoWPan — to enable IoT communications.

Likewise, Atmel’s CryptoAuthentication devices come with protected hardware key storage and are available with SHA256, AES128 or ECC256/283 cryptography. The IoT triumvirate of low power consumption, broad connectivity portfolio and crypto engineering puts Atmel in a strong position in the promising new market of IoT that is increasingly demanding low power portfolio of MCUs to be matched with high performance.

---

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.

Ars Technica, Daily Mail and other media talk SAM L21

---

The new Atmel | SMART L21 is expanding battery life from years to decades. 

---

This week, Atmel revealed the big news that the recently-unveiled Atmel | SMART SAM L family consumes just one-third the power of existing solutions already on the market. Having achieved a 185 EEMBC ULPBench score, the SAM L21 is now the world’s lowest power ARM Cortex-M based device.

Impressively, the series boasts power consumption down to 35µA/MHz in active mode and 200nA in sleep mode. The SAM L not only broadens the company’s current 32-bit ARM-based MCU lineup, but extends battery life from years to decades, reducing the number of times batteries need to be changed in devices such as fire alarms, wearables, medical gadgets and equipment placed in rural, agriculture, offshore and other remote areas. The SAM L21 combines ultra-low power with Flash and SRAM that are large enough to run both the application and wireless stacks — three features that are cornerstones of most Internet of Things (IoT) applications. Sampling now, the SAM L21 comes complete with a development platform including an Xplained Pro kit, code libraries and Atmel Studio support.

The SAM L21 MCUs will enable designers to solve their power challenges for battery-powered IoT devices — something that has caught the attention of mainstream media outlets including Ars Technica, Gizmodo, The Register, Network World and Daily Mail, as well as industry journals like Silicon Republic, New Electronics and EE Times.

 Sean Gallagher, Ars Technica 

“The number of things getting plugged into the Internet of Things has already reached the point of satire. But there’s a new, extremely low power technology that’s being prepared for market that could put computing power and network access into a whole new class of sensors, wearables, and practically disposable devices. That’s because it can run off a battery charge for over over 10 years.”

“The processor may not be enough to, say, run an Ubuntu desktop, but it’s certainly enough computing power and memory to run a real-time operating system with multiple programs, handle physical interfaces, stream media from a USB device or other external storage, and tweet you when your dishes are clean. It also can handle a lot of tasks that can reduce the power usage of other components in a device.”

Victoria Woollaston, Daily Mail 

“Battery life is consistently listed as a major flaw of smartphones, smartwatches and other wearables.  But this problem could soon be solved thanks to technology that promises to extend battery life for ‘decades.’ Atmel has released its latest microcontrollers (MCUs) for a variety of gadgets that are so low power they can even harvest energy from a person’s body.”

“They use a third of the power of rival chips and tests have shown they are the lowest power microprocessor ever made. The microcontrollers run on the firm’s picoPower technology and Atmel’s Event System that makes different parts of the device work together to carry out tasks. By effectively ‘sharing’ energy, the whole device uses less power and, subsequently, less battery.”

Jamie Condliffe, Gizmodo

“As everything around us, from phones and fridges to bicycles and trash cans, begins to connect to the Internet, there’s an increasing desire for low-power chips. Like this one, which can last for over ten years on a single battery charge. It has some other clever tricks up its sleeve. Usually in a chip like this, sleep mode sees everything but the clock function shut down, meaning it has to wake every time connected devices need to communicate; this new Atmel chip has different sleep states, allowing connected devices to communicate with each other while the chip continues to use very little power.”

“Of course, the chips don’t pack huge amounts of grunt. In fact, at best you’re looking at a 42 MHz Cortex M0+ CPU core, 256 kilobytes of Flash memory, 32 kilobytes of static RAM, and 8 kb of separate low-power static RAM. Not enough to run a desktop OS, then, but plenty to run small programs, power hardware interfaces, read and record data from sensors, tweet and the like.”

JC Torres, SlashGear

“Batteries, already the Achilles heel of mobile devices, present an even bigger challenge for even smaller devices, like wearables and the budding Internet of Things industry. These latter devices are not things that you would, or should, associate with the frequent charging and battery replacement we are used to on smartphones. How do you balance performance and battery life? Atmel, a micro-controller manufacturer based in San Jose, may have the answer. Its new ultra-low power SAM L21 32-bit ARM-based MCU (micro controller unit) is advertised to last more than a decade before needing a recharge or replacement.”

“That kind of battery life will be critical for a certain class of devices that include sensors, wearable, and smart home appliances. The SAM L21 advertises a power draw of only 35 microamps per MHz when awake and an even smaller 200 nanoamps when asleep. In comparison, current low-power MCUs already eat up to 120 to 160 microamps per MHz. The difference it definitely substantial.”

Patrick Nelson, Network World

“The Internet of Things is about to reverse a lot of what we’ve wanted in a chip. Soon, we won’t need vast amounts of calculations per second — just how many instructions does it take for your fridge to send an order to your supermarket? Not that many when you compare it to something complicated that chip design has been working towards, like a Computer Aided Design drawing in 3D, for example.”

“Size is important. However, the real big issue, when it comes to a ubiquitous IoT where everything is connected, will be battery life. The reason is that we are not going to want to change the batteries within the base of a dozen bottles of water that we may have sitting around just to discover whether we’ve drank their contents or not. Even if your fridge orders fresh stock, it wouldn’t be worth it.”

“That battery has to last the life of the connected object in the IoT. And that could be 10 years away, possibly longer. Atmel reckons it has a solution. It says its new 32-bit ARM-based chips will last decades. Note the plural. Atmel says its new chips combine battery-saving low power with flash and SRAM that is big enough to run both the application and the IoT-needed wireless stacks.”

Shaun Nichols, The Register

“Being a Cortex-M0+-powered chip, the SAM L21 is not particularly powerful: it tops out at 48MHz, and runs ARM Thumb (and some Thumb-2) code. But the family does pack a few features like USB interfacing, op-amps and comparators, DMA with peripherals, a random number generator, and AES cryptography in hardware, plus other bits and pieces. The idea is for each chip to sleep, wake up when something happens, make a decision on whether or not it needs to alert the wider world, and then go back to sleep.

“Constantly being in contact with its base over wired or wireless networking will drain its batteries; activating external electronics for power-hungry IP communications should only be done if its sensors detect something significant. Like an explosion or a fire.”

Gordon Hunt, Silicon Republic

“Sensors and batteries – the two keys to unlocking the future of IoT. Can we make small enough sensors to garner and exchange the right data? Can we make small enough, powerful enough, batteries that don’t need recharging every few hours?These are the two questions posed for today’s inventors, and they are being answered every day. Now, Atmel’s latest creation may have brought significant IoT engagement closer to reality, with its new low-powered 32-bit SAM L controller able extend the battery life of small, low-powered intelligent devices by decades.”

“The result is a far more efficient, small controller that, if advanced upon in the right way, will open up a whole new swathe of devices for IoT innovation. It’s just a sample, prototype release so far, but once the right people get their hands on this it’s only a matter of time before it creeps into suites of low-powered devices.”

Rich Quinnell, EE Times

“This week TI surpassed its own earlier result by announcing the MSP-432 family based on the Cortex M4F. It achieved a ULPBench score of 167.4. While TI was briefing the media on this product, however, Atmel quietly published a ULPBench score of 185.8 for its SAM L21 MCU based on the Cortex M0+, a product announced last year that was scheduled to be released at about this time. It’s reasonable to expect that a formal announcement of the product’s score and availability will be made soon.”

Clive Maxfield, Embedded

“When it comes to applications including the Internet of Things (IoT), consumer, industrial, medical, and other battery-powered devices — e.g., fire alarms, healthcare, medical, wearable, and devices placed in rural, agriculture, offshore, and other remote areas — ultra-low-power consumption is the name of the game. MCU manufacturers are constantly competing with each other to offer the lowest power consumption possible. The latest ultra-low-power offering comes from the folks at Atmel, who have just announced their SMART SAM L21 — an ARM Cortex-M0+ based family of MCUs that boast power consumption down to 35µA/MHz in active mode and 200nA in sleep mode — which is said to ‘extend battery life from years to decades.’”

“The L21 goes much further than simply gating the clocks — it also gates the power, completely disconnecting the power rails from functions that are not currently in use. In the case of the smart peripherals, even when they are powered down, a small part of each peripheral keeps a ‘watchful eye’ on what’s happening in the outside world. If it sees something interesting, it can request clock and data services and — if the peripheral decides the situation justifies such an action — it can wake the main CPU… Also of interest is the CCL (custom configurable logic) block, which boasts four 3-input lookup tables (LUTs) that can implement a mix of combinatorial logic functions (AND, NAND, OR, NOR, XOR, XNOR, NOT) and sequential logic functions (gates D-type flip-flop, JK-type flip-flop, gated D-type latch, RS latch). These can be connected to the event system (including the peripherals), the interrupt system, and general-purpose input/outputs; also, they can be cascaded together. This makes it possible to implement sophisticated customized “wake-up” conditions for the various functional blocks.”

Interested learning more? You can head over to our initial blog post on the topic, download its accompanying white paper, as well as delve deeper into the MCU lineup here.

SAM L family now the world’s lowest power ARM Cortex-M based solution

---

Consuming one-third the power of existing solutions, Atmel | SMART SAM L achieves 185 EEMBC ULPBench score.

---

System design used to be an exercise in optimizing speed. That has since changed. Nowadays, embedded systems pack plenty of performance to handle a number of task, leading the challenge for designers to shift to completing those tasks using as little energy as possible — but not necessarily making it as fast as possible. As you can imagine, this has created quite the competitive environment on the processor battlefield amongst vendors, each seeking to attain the lowest power solution on the market.

“The surge in popularity of battery-powered electronics has made battery life a primary system-design consideration. In extreme cases, the desire is not to run off of a battery at all, but to harvest energy from local sources to run a system — which requires the utmost power frugality,” writes Andreas Eieland, Atmel Director of Product Marketing. “In addition, there’s a growing family of devices like smoke detectors, door locks, and industrial sensors (4-20 mA and 10-50 mA) that can draw power through their inputs, and that power is limited.”

These sort of trends point to the significance of reducing the power requirements of electronic systems. However, the varying technologies that provide the necessary performance make power reduction harder. Fortunately, Atmel has been focusing on low power consumption for more than 10 years across its portfolio of AVR and Atmel ǀ SMART ARM-based processors. Many integrated peripherals and design techniques are used to minimize power consumption in real-world applications, such as integrated hardware DMA and event system to offload the CPU in active and standby modes, switching off or reducing clock or supply on device portions not in use, intelligent SleepWalking peripherals enabling CPU to remain in deep sleep longer, fast wake-up from low power modes, low voltage operation with full functionality, as well as careful balancing of high performance and low leakage transistors in the MCU design.

With picoPower technology found in AVR and Atmel ǀ SMART MCUs, Atmel has taken it a step further. Indeed, all picoPower devices are designed from the ground up for lowest possible power consumption from transistor design and process geometry, sleep modes, flexible clocking options, to intelligent peripherals. Atmel picoPower devices can operate down to 1.62V while still maintaining all functionality, including analog functions. They have short wake-up times, with multiple wake-up sources from even the deepest sleep modes. Some elements of picoPower technology cannot be directly manipulated by the user, but they form a solid base that enables ultra-low power application development without compromising functionality. Meanwhile, flexible and powerful features and peripherals lets users apply an assortment of techniques to reduce a system’s total power consumption even further.

Then, there’s the Atmel | SMART SAM L21 microcontroller, which has broken all ultra-low power performance barriers to date. These Cortex-M0+-based MCUs can maintain system functionality, all while consuming just one-third the power of comparable products on the market today. This device delivers ultra-low power running down to 35µA/MHz in active mode, consuming less than 900nA with full 32kB RAM retention. With rapid wake-up times, Event System, Sleepwalking and the innovative picoPower peripherals, the SAM L21 is ideal for handheld and battery-operated devices for a variety of Internet of Things (IoT) applications.

The ultra-low power SAM L family not only broadens the Atmel | SMART portfolio, but extends battery life from years to decades, reducing the number of times batteries need to be changed in devices such as fire alarms, healthcare, medical, wearable, and equipment placed in rural, agriculture, offshore and other remote areas. The SAM L21 combines ultra-low power with Flash and SRAM that are large enough to run both the application and wireless stacks — three features that are cornerstones of most IoT applications. Sampling now, the SAM L21 comes complete with a development platform including an Xplained Pro kit, code libraries and Atmel Studio support.

So how does the SAM L21 stack up against the others? Ahead of the pack, of course! As an alternative to so-called “bench marketing” of low power products, nearly ever large semiconductor company — and several smaller ones that focus on low power — have collaborated in a working group formed by the Embedded Microprocessor Benchmark Consortium (EEMBC). The EEMBC ULPBench uses standardized test measurement hardware to strictly define a benchmark code for use by vendors, considering energy efficiency and running on 8-, 16- and 32-bit architectures. At the moment, the Atmel | SMART SAM L21 product boasts the highest ULPBench score of any microcontroller, regardless of CPU.

“In Atmel’s announcement last year for the company’s SAM L21 family, I had pointed out the amazingly low current consumption ratings for both the active and sleep mode operation of this product family – now I can confirm this opinion with concrete data derived from the EEMBC ULPBench,” explained Markus Levy, EEMBC President and Founder. “Atmel achieved the lowest power of any Cortex-M based processor and MCU in the world because of its patented ultra-low power picoPower technology. These ULPBench results are remarkable, demonstrating the company’s low-power expertise utilizing DC-DC conversion for voltage monitoring, as well as other innovative techniques.”

While running the EEMBC ULPBench, the SAM L21 achieves a staggering score of 185, the highest publicly-recorded score for any Cortex-M based processor or MCU in the world — and significantly higher than the 167 and 123 scores announced by other vendors. The SAM L21 family consumes less than 940nA with full 40kB SRAM retention, real-time clock and calendar and 200nA in the deepest sleep mode.

In fact, a recent EE Times writeup delving deeper into competition even revealed, “TI surpassed its own earlier result by announcing the MSP-432 family based on the Cortex M4F. It achieved a ULPBench score of 167.4. While TI was briefing the media on this product, however, Atmel quietly published a ULPBench score of 185.8 for its SAM L21 MCU based on the Cortex M0+.”

Beyond the recently-unveiled ARM-based chip, it’s also important to note the 0.7V tinyAVR. A typical microcontroller requires at least 1.8V to operate, while the voltage of a single battery-cell typically ranges from 1.2V to 1.5V when fully charged, and then drops gradually below 1V during use, still holding a reasonable amount of charge. This means a regular MCU needs at least two battery cells. Whereas, Atmel has solved this problem by integrating a boost converter inside the ATtiny43U, converting a DC voltage to a higher level, and bridging the gap between minimum supply voltage of the MCU and the typical output voltages of a standard single cell battery. The boost converter provides the chip with a fixed supply voltage of 3.0V from a single battery cell even when the battery voltage drops down to 0.7V. This allows non-rechargeable batteries to be drained to the minimum, thereby extending the battery life. Programmable shut-off levels above the critical minimum voltage level avoid damaging the battery cell of rechargeable batteries.

Interested in learning more? You can explore Atmel’s low power technology here, as well as download the new white paper entitled “Turn Power-Reducing Features into Low-Power Systems” here.

Which Arduino board is right for you?

---

Picking an Arduino is as easy as Uno, Due, Tre! 

---

Thinking about starting a project? See which Arduino board is right for the job.

Arduino Uno

This popular board — based on the ATmega328 MCU — features 14 digital input/output pins (of which 6 can be used as PWM outputs), 6 analog inputs, a 16 MHz ceramic resonator, USB connection, power jack, an ICSP header and a reset button.

The Uno does not use the FTDI USB-to-serial driver chip. Instead, it features the ATmega16U2 (ATmega8U2 up to version R2) programmed as a USB-to-serial converter.

In addition, Revision 3 of the Uno offers the following new features:

• 
1.0 pinout: added SDA and SCL pins that are near to the AREF pin and two other new pins placed near to the RESET pin, the IOREF that allow the shields to adapt to the voltage provided from the board. Note: The second is not a connected pin.
• 
Stronger RESET circuit.
• ATmega16U2 replace the 8U2.

Arduino Leonardo

The Arduino Leonardo is built around the versatile ATmega32U4. This board offers 20 digital input/output pins (of which 7 can be used as PWM outputs and 12 as analog inputs), a 16 MHz crystal oscillator, microUSB connection, power jack, an ICSP header and a reset button.

The Leonardo contains everything needed to support the microcontroller; simply connect it to a computer with a USB cable or power it with a AC-to-DC adapter or battery to get started. Plus, the ATmega32U4 offers built-in USB communication, eliminating the need for a secondary processor. This allows it to appear as a mouse and keyboard, in addition to being recognized as a virtual (CDC) serial / COM port.

Arduino Due

The Arduino Due is an MCU board based on the Atmel | SMART SAM3X8E ARM Cortex-M3 CPU.

As the first Arduino built on a 32-bit ARM core microcontroller, Due boasts 54 digital input/output pins (of which 12 can be used as PWM outputs), 12 analog inputs, 4 UARTs (hardware serial ports), an 84 MHz clock, USB OTG capable connection, 2 DAC (digital to analog), 2 TWI, a power jack, an SPI header, a JTAG header, a reset button and an erase button.

Unlike other Arduino boards, the Due runs at 3.3V. The maximum voltage that the I/O pins can tolerate is 3.3V. Providing higher voltages, like 5V to an I/O pin, could damage the board.

Arduino Yún

The Arduino Yún features an ATmega32U4, along with an Atheros AR9331 that supports a Linux distribution based on OpenWRT known as Linino.

The Yún has built-in Ethernet and Wi-Fi support, a USB-A port, a microSD card slot, 20 digital input/output pins (of which 7 can be used as PWM outputs and 12 as analog inputs), a 16 MHz crystal oscillator, microUSB connection, an ICSP header and 3 reset buttons. The Yún is also capable of communicating with the Linux distribution onboard, offering a powerful networked computer with the ease of Arduino.

In addition to Linux commands like cURL, Makers and engineers can write their own shell and python scripts for robust interactions. The Yún is similar to the Leonardo in that the ATmega32U4 offers USB communication, eliminating the need for a secondary processor. This enables the Yún to appear as a mouse and keyboard, in addition to being recognized as a virtual (CDC) serial?COM port.

Arduino Micro

Developed in conjunction with Adafruit, the Arduino Micro is powered by ATmega32U4.

The board is equipped 20 digital input/output pins (of which 7 can be used as PWM outputs and 12 as analog inputs), a 16 MHz crystal oscillator, microUSB connection, a ICSP header and a reset button. The Micro includes everything needed to support the microcontroller; simply connect it to a computer with a microUSB cable to get started. The Micro even has a form factor that lets the device be easily placed on a breadboard.

Arduino Robot

The Arduino Robot is the very first official Arduino on wheels. The robot is equipped with two processors — one for each of its two boards.

The motor board drives the motors, while the control board is tasked with reading sensors and determining how to operate. Each of the ATmega32u4 based units are fully-programmable using the Arduino IDE. More specifically, configuring the robot is similar to the process with the Arduino Leonardo, as both MCUs offer built-in USB communication, effectively eliminating the need for a secondary processor. This enables the Robot to appear to a connected computer as a virtual (CDC) serial?COM port.

Arduino Esplora

The Arduino Esplora is an ATmega32u4 powered microcontroller board derived from the Arduino Leonardo. It’s designed for Makers and DIY hobbyists who want to get up and running with Arduino without having to learn about the electronics first.

The Esplora features onboard sound and light outputs, along with several input sensors, including a joystick, slider, temperature sensor, accelerometer, microphone and a light sensor. It also has the potential to expand its capabilities with two Tinkerkit input and output connectors, along with a socket for a color TFT LCD screen.

Arduino Mega (2560)

The Arduino Mega features an ATmega2560 at its heart.

It is packed with 54 digital input/output pins (of which 15 can be used as PWM outputs), 16 analog inputs, 4 UARTs (hardware serial ports), a 16 MHz crystal oscillator, USB connection, a power jack, an ICSP header and a reset button. Simply connect it to a computer with a USB cable or power it with a AC-to-DC adapter or battery to get started. The Mega is compatible with most shields designed for the Arduino Duemilanove or Diecimila.

Arduino Mini

Originally based on the ATmega168, and now equipped with the ATmega328, the Arduino Mini is intended for use on breadboards and projects where space is at a premium.

The board is loaded with 14 digital input/output pins (of which 6 can be used as PWM outputs), 8 analog inputs and a 16 MHz crystal oscillator. It can be programmed with the USB Serial adapter, the other USB, or the RS232 to TTL serial adapter.

Arduino LilyPad

The LilyPad Arduino is designed specifically for wearables and e-textiles. It can be sewn to fabric and similarly mounted power supplies, sensors and actuators with conductive thread.

The board is based on the ATmega168V (the low-power version of the ATmega168) or the ATmega328V. The LilyPad Arduino was designed and developed by Leah Buechley and SparkFun Electronics. Readers may also want to check out the LilyPad Simple, LilyPad USB and the LilyPad SimpleSnap.

Arduino Nano

The Arduino Nano is a tiny, complete and breadboard-friendly board based on the ATmega328 (Arduino Nano 3.x) or ATmega168 (Arduino Nano 2.x).

The Nano has more or less the same functionality of the Arduino Duemilanove, but in a different package. It lacks only a DC power jack and works with a Mini-B USB cable instead of a standard one. The board is designed and produced by Gravitech.

Arduino Pro Mini

Powered by an ATmega328, the Arduino Pro Mini is equipped with 14 digital input/output pins (of which 6 can be used as PWM outputs), 8 analog inputs, an on-board resonator, a reset button and some holes for mounting pin headers.

A 6-pin header can be connected to an FTDI cable or Sparkfun breakout board to provide USB power and communication to the board. Note: See also Arduino Pro.

Arduino Fio

The Arduino Fio (V3) is a microcontroller board based on Atmel’s ATmega32U4. It has 14 digital input/output pins (of which 6 can be used as PWM outputs), 8 analog inputs, an on-board resonator, a reset button and holes for mounting pin headers. It also offers connections for a lithium polymer battery and includes a charge circuit over USB. An XBee socket is available on the bottom of the board.

The Arduino Fio is intended for wireless applications. The user can upload sketches with an a FTDI cable or Sparkfun breakout board. Additionally, by using a modified USB-to-XBee adaptor such as XBee Explorer USB, the user can upload sketches wirelessly. The board comes without pre-mounted headers, facilitating the use of various types of connectors or direct soldering of wires. The Arduino Fio was designed by Shigeru Kobayashi and SparkFun Electronics.

Arduino Zero

Last year, the tandem of Atmel and Arduino debuted the Zero development board – a simple, elegant and powerful 32-bit extension of the platform. The Arduino Zero board packs an Atmel | SMART SAM D21 MCU, which features an ARM Cortex M0+ core. Additional key hardware specs include 256KB of Flash, 32KB SRAM in a TQFP package and compatibility with 3.3V shields that conform to the Arduino R3 layout.

The Arduino Zero boasts flexible peripherals along with Atmel’s Embedded Debugger (EDBG) – facilitating a full debug interface on the SAMD21 without the need for supplemental hardware. Beyond that, EDBG supports a virtual COM port that can be used for device programming and traditional Arduino bootloader functionality. This highly-anticipated board will be available for purchase from the Arduino Store in the U.S. on Monday June 15th.

Arduino AtHeart

The Arduino AtHeart program was specifically launched for Makers and companies with products based on the open-source board that would like to be clearly identified as supporters of the versatile platform. The program is available for any device that includes a processor that is currently supported by the Arduino IDE, including the following Atmel MCUs:

• ATMega328 clocked at 8 or 16 MHz
• ATMega1280 clocked at 16 MHz
• ATMega2560 clocked at 16 MHz
• ATMega32U4 clocked at 16MHz
• Atmel | SMART SAM3X

Participants in the program include startups like:

EarthMake – ArLCD

The touchscreen ArLCD combines the ezLCD SmartLCD GPU with the Arduino Uno.

Bare Conductive Touch Board

The ATmega32U4 based Touch Board can turn nearly any material or surface into a sensor by connecting it to one of its 12 electrodes, using conductive paint or anything conductive.

Blend Micro

The RedBearLab integrated dev platform “blends” the powers of Arduino with Bluetooth 4.0 Low Energy into a single board. It is targeted for Makers looking to develop low-power IoT projects in a quick, easy and efficient manner. The MCU is driven by an ATmega32U4 and a Nordic nRF8001 BLE chip.

littleBits Arduino Module

The fan-favorite Arduino module, which happens to also be based on an ATmega32U4, lets users easily write programs in the Arduino IDE to read sensors and control lights and motors within the littleBits system.

Smart Citizen Kit

An Arduino-compatible motherboard with sensors that measure air composition (CO and NO2), temperature, light intensity, sound levels, and humidity. Once configured, the Smart Citizen Kit is capable of streaming data collected by the sensors over Wi-Fi.