ATMEGA 4808 - Datasheet

• CPU
  • 8 bit AVR CPU running up to 20MHz
  • Single-cycle I/O access
  • Two-level interrupt controller
  • Two-cycle hardware multiplier
• Memory
  • 48KB Flash Memory
  • 256Byte EEPROM
  • 6KB SRAM
• System
  • Power-on Reset (POR) circuit
  • Brown-out Detection (BOD)
  • Clock options:
    • 20 MHz low power internal oscillator with fuse-protected frequency setting
    • 32.768 kHz Ultra Low Power (ULP) internal oscillator
    • 32.768 kHz external crystal oscillator
    • External clock input
  • Single pin Unified Program Debug Interface (UPDI)
  • Three sleep modes:
    • Idle with all peripherals running and mode for immediate wake-up time •
    • Standby –
      • Configurable operation of selected peripherals SleepWalking peripherals • Power Down with limited wake-up functionality • Peripherals – One 16-bit Timer/Counter type A with dedicated period register, three compare channels (TCA) – Three 16-bit Timer/Counter type B with input capture (TCB) – One 16-bit Real Time Counter (RTC) running from external crystal or internal RC oscillator – Three USART with fractional baud rate generator, autobaud, and start-of-frame detection – Master/slave Serial Peripheral Interface (SPI) – Dual mode Master/Slave TWI with dual address match • Standard mode (Sm, 100 kHz) • Fast mode (Fm, 400 kHz) • Fast mode plus (Fm+, 1 MHz) – Event System for CPU independent and predictable inter-peripheral signaling – Configurable Custom Logic (CCL) with up to four programmable Lookup Tables (LUT) – One Analog Comparator (AC) with scalable reference input – One 10-bit 150 ksps Analog to Digital Converter (ADC) – Five selectable internal voltage references: 0.55V, 1.1V, 1.5V, 2.5V, and 4.3V – CRC code memory scan hardware • Optional automatic scan after reset – Watchdog Timer (WDT) with Window Mode, with separate on-chip oscillator – External interrupt on all general purpose pins • I/O and Packages: – 27 programmable I/O lines – 32-pin VQFN 5x5 and TQFP 7x7 • Temperature Range: -40°C to 125°C • Speed Grades: – 0-5 MHz @ 1.8V – 5.5V – 0-10 MHz @ 2.7V – 5.5V – 0-20 MHz @ 4.5V – 5.5V, -40°C to 105°C

MCP73871 LiPo Charger with Power Path Management - Datasheet

This little IC is a fully integrated power management and Li-Ion battery charging solution for small electronic systems.

It will take power sourced both from a wall AC-DC adaptor, USB ports or from a connected Li-Ion battery.

It requires a very low number of components to operate making it great to use on a small embedded board such as this one.

Here is a complete example circuit implementation from the datasheet:

MIC33050 Voltage Regulator - Datasheet

Features

• Input Voltage: 2.7V to 5.5V
• 600 mA Output Current
• Fixed and Adjustable Output Voltage Options
• No External Inductor Required
• Ultra-Fast Transient Response
• 20 µA Quiescent Current
• 4 MHz Switching in PWM Mode
• Low Output Voltage Ripple
• >93% Peak Efficiency
• >85% Efficiency at 1 mA
• Micropower Shutdown
• 12-Pin 3 mm x 3 mm HDFN
• –40°C to +125°C Junction Temperature Range

ATECC608A Security IC - Datasheet

This security IC gives this board one of the key differentiating features when compared to other IoT development boards on the market.

It has a number of excellent security features that if used correctly will make a solution based on this very secure with a high resistance to hacks.

One great feature is the key production and management.  It is able to create a high quality random private/public key pair where the private key is stored internally and will never be made available outside of the IC.  The public key can then be read using functions contained in the cryptoauth library supplied by Microchip. Keeping the private key secured is extremely important in any secure application to ensure the data can't be compromised.  In IoT and other products where a security IC is not used but that require secure communications, a private/public key combination needs to be provisioned in a manner where it is possible the private key could be compromised.  This IC removes this possibility.

Here are the main features taken from the datasheet:

• Cryptographic Co-Processor with Secure Hardware-Based Key Storage:
  • Protected storage for up to 16 keys, certificates or data
• Hardware Support for Asymmetric Sign, Verify, Key Agreement:
  • ECDSA: FIPS186-3 Elliptic Curve Digital Signature
  • ECDH: FIPS SP800-56A Elliptic Curve Diffie-Hellman
  • NIST Standard P256 Elliptic Curve Support
• Hardware Support for Symmetric Algorithms:
  • SHA-256 & HMAC Hash including off-chip context save/restore
  • AES-128: Encrypt/Decrypt, Galois Field Multiply for GCM
• Networking Key Management Support:
  • Turnkey PRF/HKDF calculation for TLS 1.2 & 1.3
  • Ephemeral key generation and key agreement in SRAM
  • Small message encryption with keys entirely protected •
• Secure Boot Support:
  • Full ECDSA code signature validation, optional stored digest/signature
  • Optional communication key disablement prior to secure boot
  • Encryption/Authentication for messages to prevent on-board attacks
• Internal High-Quality NIST SP 800-90A/B/C Random Number Generator (RNG)
• Two High-Endurance Monotonic Counters
• Unique 72-Bit Serial Number
• Two Interface Options Available:
  • High-speed Single Pin Interface with One GPIO Pin
  • 1 MHz Standard I2C Interface
• 1.8V to 5.5V IO Levels, 2.0V to 5.5V Supply Voltage
• <150 nA Sleep Current
• 8-pad UDFN and 8-lead SOIC

MCP9808 Temperature Sensor - Datasheet

This is a digital temperature sensor that will measure and convert a temperature of between -20degC and +100degC to a digital word with a typical accuracy of +/- 0.25degC and maximum of +/-0.5degC.

It communicates over a 400kHz 2wire I2C bus.

The key features from the datasheet are:

• Accuracy: - ±0.25 (typical) from -40°C to +125°C
• ±0.5°C (maximum) from -20°C to 100°C
• ±1°C (maximum) from -40°C to +125°C •
• User-Selectable Measurement Resolution:
  • +0.5°C, +0.25°C, +0.125°C, +0.0625°C
• User-Programmable Temperature Limits:
  • Temperature Window Limit
  • Critical Temperature Limit
• User-Programmable Temperature Alert Output
• Operating Voltage Range: 2.7V to 5.5V
• Operating Current: 200 µA (typical)
• Shutdown Current: 0.1 µA (typical)
• 2-wire Interface: I2C™/SMBus Compatible

Here is the Functional Block Diagram taken from the datasheet:

TEMT6000 Light Sensor -https://www.sparkfun.com/datasheets/Sensors/Imaging/TEMT6000.pdfDatasheet

This is simply a silicon NPN phototransistor that is sensitive to the visible spectrum of light.

It is adapted to human eye responsivity and has a wide angle of half sensitivity - +/- 60deg

WINC1510 WiFi Module - Datasheet | Wi-Fi Network Controller Software Design Guide

This component is a Certified 802.11 b/g/n IoT network controller System on Chip.  It abstracts a large portion of the network communications away from the host processor making it much simpler to implement a WiFi base IoT system.

It is especially optimized for low power IoT applications.

It contains a fully integrated power amplifier, LNA, switch and power management and printed antenna.

The module hosts the WiFi Stack, TCP/IP and TLS stacks with corresponding API and an SPI driver.

One interesting feature I found that would make this module very appealing for use in Industrial IoT products where the product may be used on networks controlled by large corporations is the support for Enteprise security with WPA/WPA2 (802.1X).

Here is a summary of the features from the datasheet:

• IEEE® 802.11 b/g/n 20 MHz (1x1) solution
• Single spatial stream in 2.4 GHz ISM band
• Integrated Transmit/Receive switch
• Integrated PCB antenna or u.FL micro co-ax connector for external antenna
• Superior sensitivity and range via advanced PHY signal processing
• Advanced equalization and channel estimation • Advanced carrier and timing synchronization
• Wi-Fi® Direct (supported till firmware release 19.5.2)
• Soft-AP support • Supports IEEE 802.11 WEP, WPA, WPA2 security
• Support Enterprise security with WPA/WPA2 (802.1X)(1)
  • EAP-TLS – EAP-PEAPv0/1 with TLS
  • EAP-TTLSv0 with MSCHAPv2
  • EAP-PEAPv0/1 with MSCHAPv2
• Superior MAC throughput via hardware accelerated two-level A-MSDU/A-MPDU frame aggregation and block acknowledgment
• On-chip memory management engine to reduce host load
• SPI host interface © 2018 Microchip Technology Inc. Datasheet DS70005304C-page 1
• Operating temperature range from -40°C to +85°C. RF performance at room temperature of 25oC with a 2-3 db change at boundary conditions
• I/O operating voltage of 2.7V to 3.6V
• Built-in 26 MHz crystal
• Integrated Flash memory for system software
• Power Save modes
  • 4 µA Power-Down mode typical at 3.3V I/O
  • 380 µA Doze mode with chip settings preserved (used for beacon monitoring)(2)
  • On-chip low power sleep oscillator
  • Fast host wake-up from Doze mode by a pin or SPI transaction
• Fast Boot options
  • On-chip boot ROM (Firmware instant boot)
  • SPI flash boot
  • Low-leakage on-chip memory for state variables
  • Fast AP re-association (150 ms)
• On-chip Network stack to offload MCU
  • Integrated Network IP stack to minimize host CPU requirements
  • Network features TCP, UDP, DHCP, ARP, HTTP, TLS, and DNS
  • Hardware accelerators for Wi-Fi and TLS security to improve connection time
• Hardware accelerator for IP checksum
• Hardware accelerators for OTA security
• Small footprint host driver
• Wi-Fi Alliance® certifications for Connectivity and Optimizations

nEDBG Circuit

The board features a complete Embedded Debugger that allows on-board programming and debugging.  It has a number of interfaces making it very useful!.....

• A Debugger - this allows a range of debugging features that can be used from within MPLAB or Atmel Studio
• Mass Storage - This makes available a number of files such as the public key and a website shortcut to get you connected to the Microchip sandbox account
• Virtual COM port - this is directly connected to the UART on the 4808 MCU.  This is very useful as it allows some handy run-time debugging messages to be sent from the application and displayed in a suitable terminal emulation program such as PuTTY.

The Embedded Debugger connects to the MCU via the Unified Program and Debug Interface which is an Atmel proprietary 1-wire debug and programming interface.

The board was well protected in the package

The box that the board came in was nice a compact

The board was protected in a small Anti-Static bag

The board itself is very compact

Microchip have published a great video on YouTube which gives a really good overview of setting up the board.

Edit media

Dimensions x Small Medium Large Custom

Subject (required) Brief Description Tags (separated by comma) Video visibility in search results Visible Hidden

Parent content

Microchip AVR-IoT WG Dev Board - Review

Poster

Upload Preview

Ok

Cancel

They have also published a user manual that takes you through each part of setting up the board and gives an overview of the board

Plug the board in to a computer

Double click on the CLICK-ME.HTM link on the CURIOSITY drive

This file contains a link to AVR-IOT.com - Microchips sandbox account that will show data received in real time from the board.

<meta http-equiv="refresh" content="0; url=https://AVR-IOT.com/device/01235779C93D870BFE"/>

Generate WiFi Connection File

When navigating to the sandbox page initially, as the board is not connected, you are presented with a page to enter the details for a local WiFi network.

Once the WiFi details have been entered, you simply click the Download Configuration button to download a small text file containing the WiFi connection details.

You save this file to the Mass Storage drive which then loads the Wifi credentials into the MCUs EEPROM

Step 1 - Open MPLAB X IDE

When I first opened MPLAB X IDE, I was presented with the Start Page that has some quick links on the left and allowed me to sign in to my Microchip account.  It Also shows a summary of recent projects.

to go to the next step, I had to have the Microchip Code Configurator Add-In downloaded and enabled.  To install this, I clicked on Tools->Plugins then choose the Available Plugins tab, found and selected MPLAB Code Configurator, then clicked install.

As I had already installed it when I took the screen shots, it does not show up in the screenshot above - instead it shows up in the Installed Tab:

So far, so good!!

Create New Project

I next clicked on Create New in the Startup Page

and then left the standard selections of Microchip Embedded and Standalone Project

Choose MCU

Next I selected the MCU that is on the board - 8-bit AVR MCUs (XMega/Mega/Tiny) and then ATmega4808

Choose Debugger/Programmer

I then chose the debugger that is part of the board - the nEDBG.  This is under the Alternate Tools tab.

Choose Compiler

At this point, I had the AVR GNU or avrasm2 compilers available to select as I already had these installed.  If I had the XC8 compiler installed, I would should this option as well.

I chose the AVR GNU compiler / toolchain and clicked Next>

Choose Project Name

Finally for this part of the set up, I chose the Project Name and Folder location.  I called it IoT_Node_MCC for easy future reference:

Once this was done, a bare bones project was created - at this point there is only a basic Makefile and a basic project configuration.

Begin Configuration of the Project with MCC

This is the part where it gets a little more interesting as the MCC tool bulks the project out with all of the necessary functionality........

I clicked on the MCC icon on the tool bar to invoke the configurator....

I then got a dialog to save the MCC project file..... for this I chose the default filename and location.

Load the AVR-IoT WG Sensor Node Example

I next picked the AVR-IoT WG Sensor Node example from the Device Resources pane by double clicking on it.

This loaded all of the relevant libraries and configuration for this board.

A number of tabs are then presented across the top with various configuration options for a customised application.

For example, the Cloud Services Registry ID can be changed for migrating away from the Microchip sandbox account and to a personal cloud account.

In the AVR-IoT WG Sensor Node tab, I selected the Debug Messages option as this was initially off.

For this part, I left all of the other settings unmodified.

You can also navigate to the different settings in the Project Resource Pane, either in a Tree view or Flat View

Generate the Code

I now clicked the Generate button in the Project Resources pane to create the code from the MCC project set up.

Once complete, I had a Generation Complete message in the MPLAB Code Configurator status pane.

To check the file generation, I had a look at the Project Tree Pane where I could see the various project files.....

I thought the folder organisation is actually pretty good - it is well structured and easy to navigate.

Change the Optimizations

As per the manual, the code optimization needs to be changed for the code to run at the optimal level.  To do this, I right clicked on the top level project folder and selected properties.

As I only have the AVR compiler installed, I selected avr-gcc on the left hand side, then chose Optimization under Option categories and selected s for the optimization level.  This optimizes the project favouring size.

Building and Loading

Building and loading the project is very simple - you simply click the Make and build icon....

and then chose Make and Program Device Main Project.

I was asked which debugging tool I wanted to use - my board was already plugged in, so it showed up with the serial number in the list under nEDBG....

I selected this, click OK -

The compiler then compiled the program, once it was compiled it was automatically loaded to the board.

Follow Link to Leverage GitHub

I first clicked on the Graduate button at the bottom of the Microchip Sandbox webpage which takes you to the Leverage GitHub page that hosts the instructions and set up files for this board.

This link took me here:

Leverage have created a set of videos that take you through the process which is very useful.  They also have also described the process.  I will document the steps I took here.....

Sign Up / Configure Google Cloud

If you are not already signed up to Google Cloud, then you will need to do this before anything else.  In my case, I had already set up an account before the Road Test started.  One of the nice things about Google Cloud is that you get a bunch of credits for free when you sign up and configure billing.  This allows you to experiment without landing a big bill.

The address for the Google Cloud Platform Management Console is: console.cloud.google.com

Create Google Cloud Project

Within the Console, I first clicked on Home to open the Dashboard

and then clicked on CREATE to begin a new project.

I then gave my new project a name and clicked CREATE.

It took a few seconds to create the project, but once it was created I was presented with a range of widgets on a dashboard to give a project overview

On the Leverage instructions, it states that you need to enable billing for the project.  In my case as I am the billing administrator on one billing account, this new project was automatically linked to my billing account.

When I set up my Google Cloud account up, I had to add my card details to enable billing - as I have the free credit and am only running basic functions, I had no concerns I would get any charges.

You can see the status of your account at any time by going to the GCP console menu and selecting billing.

Create Firebase Project

I navigated to the Firebase console and clicked on Add project

I then had a dialogue where I added my Google Cloud Project just created to Firebase.

Once I had selected to accept the terms, the Create project button changed to Add Firebase and became clickable.  Once clicked, a dialogue opens to confirm the billing plan.

Once I had clicked Confirm Plan, the project was created in Firebase and the dashboard opened.

Set Up Leverage UI in Google Cloud Account

I first activated the Google Cloud Shell which gives a command line access to configure your project. I did this by clicking the CLI button in the tool bar.....

This then opens a command line shell at the bottom of the page.

This is quite a neat and powerful feature.  The Cloud Shell evironment is a Docker Container that is started from a Google-maintained image.  It is also possible to create your own Docker image and use that!

There is a README file located on the folder that contains the following:

To be able to set up the Leverage application, I first cloned the Leverege project into my shell environment by running the following command:

git clone https://github.com/Leverege/microchip-avr-iot.git && cd microchip-avr-iot/setup && bash setup.sh

This command completed pretty quickly and then presented me with the following

I then copied my UID from the last part of the address in the CLICK-ME.HTM file on the board and pasted it into the shell.

I then had the option to chose my IoT Core registry name - I changed this to AVR-IOT-RoadTest

The script then ran and set everything up in the project that was required.

It carries out the following tasks:

• Enable Cloud Functions, IoT Core, and Pub Sub in your GCP project

• Create an IoT Core registry called AVR-IOT and register your device

• Install, build, and deploy Cloud Functions and the UI

This whole task is very well automated and made the set up very easy! It took a few minutes, but does report the progress well.

Once complete I had the following in the shell:

Add Device Public Key to IoT Core Registry

To allow my device to talk to Google Cloud, I need to add the Public Key to my account.  To do this, I selected IoT Core from the Google Cloud Console Menu.

Then selected my registry that had been created.

Then selected Devices

And then selected my device that had also been created.

From there I could see the option to add a public key

The key is contained in the PUBKEY.TXT file on the board.  I simply copied the text from this and pasted it into the Add authentication key dialogue.

I had to also select ES256 as the key type as it is a key based on Elliptic Curve Cryptography.

Modify Firmware Settings to Connect to Private Cloud

In the Leverege instructions, they state to use the Atmel START web based utility, which is what I tried initially.  However I am going to use the Microchip Code Configurator in this write up for 2 reasons -

1. To show an alternative method
2. The Microchip Code Configurator version of the firmware has implemented a subscription to the /config MQTT topic allowing the potential for 2 way communication.

First with the MPLAB AVR-IOT project still open, I had to re-open the MCC from within MPLAB by clicking the MCC button on the toolbar.

Then, in the Cloud Services Google tab, I entered the corresponding details for my project.

Then, in the WINC tab, I entered my WiFi details so these would be saved in the firmware.

Build and Load Project

Click to build and load the project.

Once loaded successfully, I saw the following in the Output and nEDBG panes:

View Data

Finally, I navigated to the web page that was now being hosted on my private cloud.  This web page takes the format: https://avr-iot-roadtest.firebaseapp.com/device/XXXXXXXXX where the XXXXXXXXX is the corresponding device ID.

In this video, you can see the live data coming into my app:

Edit media

Dimensions x Small Medium Large Custom

Subject (required) Brief Description Tags (separated by comma) Video visibility in search results Visible Hidden

Parent content

Microchip AVR-IoT WG Dev Board - Review

Poster

Upload Preview

Ok

Cancel

In this video, you can see the data populating the database as it is being delivered:

Edit media

Dimensions x Small Medium Large Custom

Subject (required) Brief Description Tags (separated by comma) Video visibility in search results Visible Hidden

Parent content

Microchip AVR-IoT WG Dev Board - Review

Poster

Upload Preview

Ok

Cancel

cli Command Line Interface

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

cloud (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

cloud (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

credentials_storage (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

cryptoauthlib (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

doxygen (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

examples (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

include (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

mqtt (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

src (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

utils (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

winc (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>

Top Level Application Files (shows up in the second tab)

<html><head><title>Jive SBS</title></head>
<body><font face="arial,helvetica,sans-serif">
<b>Error</b><br><font size="-1">
An general error occurred while processing your request.
</font></font></body></html>