What’s new in Atmel’s ARM MCU? picoPower!!

The SAM4L it is the first ARM device to feature Atmel’s picoPower technology, and takes low power to a new level.   There are many different characteristics that make a low power device; foremost it is the active power, the wake-up time and sleep mode power consumption. For the SAM4L, this can go down to 90 µA/MHz in active, down to 700 nA in sleep mode and down to 1.5 µs wake-up. Additionally the Cortex-M4 and Atmel’s fast flash technology allows your application to spend a shorter amount of time in active and spend more time in low power modes. All of this significantly reduces the total power consumption for your application.

Atmel SAM4L MCUs redefine the power benchmark, delivering the lowest power in both active (90uA/MHz) and sleep
modes (1.5uA with full random access memory (RAM) retention and 700nA in backup mode). They are the most efficient
MCUs available today, achieving up to 28 CoreMark™/mA using the IAR Embedded Workbench, version 6.40.

Check out this video for more information about picoPower in the SAM4L.  Also, please be sure to follow us on this blog to learn more on how these ARM devices become so power conscious and other neat application tutorials.  Or share, collaborate, and innovate with the other tens of thousands of engineers/builders in the vibrant AT91 community.

What is the Difference Between Encryption and Authentication?

By: Gunter Fuchs

Not considering how to actually do encryption or authentication, it is fairly simple for a native Latin speaker (http://www.etymonline.com/index.php?term=authentic, http://www.etymonline.com/index.php?term=crypto) to distinguish between the two. We authenticate something to prove to the receiver of the “something” that it actually came from us. We encrypt a message so nobody, including us, can read it. Why do we authenticate or encrypt? We authenticate so that the receiver is assured that what she received came from us and not from an imposter. This “thing” can be an item – a coin or painting for instance, or a piece of information, an email attachment or a speed command to a uranium centrifuge. We encrypt information so that only the intended receiver(s) can understand it.

So that was simple. But why do computer gurus go through great efforts to provide means of information authentication? Wouldn’t encrypting information be enough? Couldn’t the sender just include its name and address in the information and then encrypt? Well, no. The problem is that although a “man in the middle” will not understand the information, he will still be able to change it. For instance, in computer communication protocols a destination address (port) might be at a fixed position in a message. An adversary could copy such a message when it is on its way through some wire, change this value randomly, and monitor its own port/s until one of these messages – though still garbled – arrives. Once the adversary has received one message, he can now inject the encrypted port value for his own port for every message. One message would not be enough for a hacker to perform decryption,  but many makes this possible.  Not only would an adversary then be able to decipher messages that were not meant for her, but she can now also “break the code”, meaning deduce the encryption key. And with that key in hand, she can now send messages that are not authentic.

Therefore, a secure communication consists of authenticating the message and encrypting it.  To learn more about the importance of protecting your trade secrets, check out this white paper.