pic-iot wx hardware user guide · 2020. 3. 6. · pic-iot wx hardware user guide pic-iot wx...

PIC-IoT Wx Hardware UserGuide

PIC-IoT Wx Hardware User Guide

Preface

Important: This document is applicable for two different products; PIC-IoT WG (AC164164) and PIC-IoTWA (EV54Y39A). Both variants are referred to as PIC-IoT Wx in this document, and both products haveidentical hardware. PIC-IoT WG is preconfigured to send data through Google Cloud IoT Core, and PIC-IoT WA is preconfigured to send data through Amazon Web Services (AWS). Both products can bereconfigured to send data to different cloud providers.

IntroductionThe PIC-IoT Wx development board is a small and easily expandable demonstration and development platform forIoT solutions based on the PIC® microcontroller architecture using Wi-Fi® technology. It is designed to demonstratethat the design of a typical IoT application can be simplified by partitioning the problem into three blocks:

• Smart - represented by the PIC24FJ128GA705 microcontroller• Secure - represented by the ATECC608A secure element• Connected - represented by the ATWINC1510 Wi-Fi controller module

The PIC-IoT Wx Development Board features the following elements:• The on-board debugger (PKOB nano) supplies full programming and debugging support through MPLAB X IDE.

It also provides access to a serial port interface (serial to USB bridge) and one logic analyzer channel (debugGPIO).

• The on-board debugger enumerates on the PC as a mass storage interface device for easy ‘drag and drop’programming, Wi-Fi configuration, and full access to the microcontroller application Command Line Interface(CLI)

• A mikroBUS™ socket allows for the ability to expand the board capabilities with the selection from 450+ sensorsand actuators options offered by MikroElektronika (www.mikroe.com) via a growing portfolio of Click boards™

• A light sensor used to demonstrate published data• Microchip MCP9808 high-accuracy temperature sensor used to demonstrate published data• Microchip MCP73871 Li-Ion/LiPo battery charger with power path management

© 2020 Microchip Technology Inc. User Guide DS50002964A-page 1

https://www.microchip.com/PIC24FJ128GA705https://www.microchip.com/ATECC608Ahttps://www.microchip.com/ATwinc1500http://www.mikroe.comhttps://www.microchip.com/MCP9808https://www.microchip.com/MCP73871

• MPLAB® X IDE - Software to discover, configure, develop, program, and debug Microchip microcontrollers.• Application Code on GitHub - Get started with application code.• PIC-IoT WG website - Find schematics, design files, and purchase the board. Set up for Google Cloud IoT

Core.• PIC-IoT WA website - Find schematics, design files, and purchase the board. Set up for Amazon Web Services.



https://www.microchip.com/mplab/mplab-x-idehttps://github.com/microchip-pic-avr-solutions?q=pic-iothttp://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=AC164164https://www.microchip.com/developmenttools/ProductDetails/EV54Y39A

Table of Contents

Preface...........................................................................................................................................................1

1. Introduction............................................................................................................................................. 5

1.1. Features....................................................................................................................................... 51.2. Kit Overview................................................................................................................................. 5

2. Getting Started........................................................................................................................................ 7

2.1. Quick Start....................................................................................................................................72.2. Design Documentation and Relevant Links................................................................................. 7

3. Application User Guide........................................................................................................................... 8

4. Hardware User Guide............................................................................................................................. 9

4.1. On-Board Debugger Overview.....................................................................................................94.1.1. Debugger.......................................................................................................................94.1.2. Virtual Serial Port (CDC)................................................................................................94.1.3. Mass Storage Device...................................................................................................124.1.4. Data Gateway Interface (DGI)..................................................................................... 13

4.2. On-Board Debugger Connections..............................................................................................144.3. Power......................................................................................................................................... 15

4.3.1. Power Source.............................................................................................................. 154.3.2. Battery Charger........................................................................................................... 154.3.3. Hardware Modifications............................................................................................... 15

4.4. Peripherals................................................................................................................................. 164.4.1. PIC24FJ128GA705......................................................................................................164.4.2. mikroBUS™ Socket...................................................................................................... 164.4.3. WINC1510 Wi-Fi Module.............................................................................................174.4.4. ATECC608A................................................................................................................ 184.4.5. Temperature Sensor.................................................................................................... 184.4.6. Light Sensor.................................................................................................................194.4.7. LED..............................................................................................................................194.4.8. Mechanical Buttons..................................................................................................... 19

5. Regulatory Approval..............................................................................................................................20

5.1. United States..............................................................................................................................205.2. Canada.......................................................................................................................................205.3. Taiwan........................................................................................................................................ 215.4. List of Antenna Types.................................................................................................................21

6. Hardware Revision History and Known Issues..................................................................................... 22

6.1. Identifying Product ID and Revision........................................................................................... 226.2. PIC-IoT WG................................................................................................................................22

6.2.1. Revision 3....................................................................................................................226.2.2. Revision 2....................................................................................................................22

6.3. PIC-IoT WA................................................................................................................................ 226.3.1. Revision 1....................................................................................................................22

7. Document Revision History...................................................................................................................23



8. Appendix............................................................................................................................................... 24

8.1. Schematic...................................................................................................................................248.2. Assembly Drawing......................................................................................................................268.3. Mechanical Drawings................................................................................................................. 26

The Microchip Website.................................................................................................................................28

Product Change Notification Service............................................................................................................28

Customer Support........................................................................................................................................ 28

Microchip Devices Code Protection Feature................................................................................................ 28

Legal Notice................................................................................................................................................. 28

Trademarks.................................................................................................................................................. 29

Quality Management System....................................................................................................................... 29

Worldwide Sales and Service.......................................................................................................................30



1. Introduction

1.1 Features• PIC24FJ128GA705 Microcontroller• ATWINC1510 Wi-Fi Module• ATECC608A CryptoAuthentication™ Device• Preconfigured for Microchip Accounts with Different Cloud Providers

– Google Cloud IoT Core– Amazon Web Services (AWS)

• Four User LEDs• Two Mechanical Buttons• TEMT6000 Light Sensor• MCP9808 Temperature Sensor• mikroBUS Socket• On-board Debugger

– Board identification in Microchip MPLAB X IDE– One green board power and status LED– Virtual serial port (USB CDC)– One logic analyzer channel (debug GPIO)

• USB and Battery Powered• MCP73871 Li-Ion/LiPo Battery Charger• Fixed 3.3V

1.2 Kit OverviewThe PIC-IoT Wx development board is a hardware platform to evaluate and develop IoT solutions with the MicrochipPIC24FJ128GA705 16-bit microcontroller, ATECC608A secure element, and WINC1510 Wi-Fi controller module.

The preprogrammed demo application publishes data from the on-board light and temperature sensor read by thePIC24FJ128GA705 every second to the cloud. Any data received from the cloud over the subscribed topic is sent tothe virtual serial port and can be displayed in a serial terminal application. The WINC1510 needs a connection to aWi-Fi network with an internet connection. The ATECC608A is used to authenticate the hardware with the cloud touniquely identify every board. The demo application source code can be modified to publish data to a personal cloudaccount to get started with a custom cloud application.

The figure below shows the main features and pinout of the board.

PIC-IoT Wx Hardware User GuideIntroduction


https://www.microchip.com/PIC24FJ128GA705https://www.microchip.com/ATWINC1500https://www.microchip.com/ATECC608Ahttps://www.microchip.com/MCP9808https://www.microchip.com/MCP73871

Figure 1-1. PIC-IoT Wx Development Kit Overview

Timer/PWM

UART RX

RB14

RB15

RA0

RA1

RB0

RB1

3.3V

GND

SPI SCK

SPI MISO

SPI MOSI

RC6

RB7

RB6

RB5

RB8

RB9

5.0V

GND

UART TX

I2C SCL

I2C SDA

Wi-Fi Status LEDRC5

Connection Status LEDRC4

Data Trans fer LEDRC3

Error Status LEDRB4

RA10USER SWITCH 1

RA7USER SWITCH 0

ATWINC1510 Wi-Fi® Module

Micro USB Connector

Power/Status LED

PKoB4 nano Debugger/Programmer

ADC AIN7

PIC24FJ128GA705 Microcontroller

Charge Status LEDs

LiPo Connector

MCP73871 LiPo Charger

ATECC608A Secure Element

Light Sens or

MCP9808 Temperature Sens orMIC33050 Voltage Regulator

SPI CS

Res et Interrupt

PIC-IoT WG Development Board (AC164164)

PIC-IoT Wx Hardware User GuideIntroduction


2. Getting Started

2.1 Quick StartSteps to start exploring the board:

1. Connect the board to your computer.2. Open the “CLICK-ME.HTM” file on the “CURIOSITY” mass storage disk and follow the instructions.

2.1. Download the latest application .hex firmware.2.2. Download the Wi-Fi configuration file "WIFI.cfg".

3. Drag and drop the application .hex file on the "CURIOSITY" drive.4. Drag and drop the “WIFI.cfg” configuration file on the “CURIOSITY” drive.

The board will now connect to your Wi-Fi network and send data to the website opened in step 2 through a cloudprovider.

2.2 Design Documentation and Relevant LinksThe following list contains links to the most relevant documents and software for the PIC-IoT Wx.

• PIC-IoT WG website - Find schematics, design files, and purchase the board. Set up for Google Cloud IoTCore.

• PIC-IoT WG on microchipDIRECT - Purchase this board on Microchip Direct.• PIC-IoT WA website - Find schematics, design files, and purchase the board. Set up for Amazon Web Services.• PIC-IoT WA on microchipDIRECT - Purchase this board on Microchip Direct.• MPLAB Data Visualizer - MPLAB Data Visualizer is a program used for processing and visualizing data. The

Data Visualizer can receive data from various sources such as serial ports and on-board debugger’s DataGateway Interface, as found on Curiosity Nano and Xplained Pro boards.

• MPLAB® X IDE - MPLAB X IDE is a software program that runs on a PC (Windows®, Mac OS®, Linux®) todevelop applications for Microchip microcontrollers and digital signal controllers. It is called an IntegratedDevelopment Environment (IDE) because it provides a single integrated “environment” to develop code forembedded microcontrollers.

• Microchip Sample Store - Microchip sample store where you can order samples of devices.

PIC-IoT Wx Hardware User GuideGetting Started


http://www.microchip.com/DevelopmentTools/ProductDetails.aspx?PartNO=AC164164http://www.microchipdirect.com/ProductSearch.aspx?Keywords=AC164164https://www.microchip.com/developmenttools/ProductDetails/EV54Y39Ahttp://www.microchipdirect.com/ProductSearch.aspx?Keywords=EV54Y39Ahttps://gallery.microchip.com/packages?q=MPLAB-Data-Visualizerhttps://www.microchip.com/mplab/mplab-x-idehttps://www.microchip.com/samples/default.aspx

3. Application User GuideThe PIC24FJ128GA705 mounted on PIC-IoT Wx is preprogrammed with an application ready to publish data to aMicrochip account with a cloud provider, and subscribe to data sent from https://pic-iot.com through the cloudprovider. PIC-IoT WA is preconfigured for Amazon Web Services (AWS), and PIC-IoT WG is preconfigured forGoogle Cloud IoT Core. The data is read from the cloud and presented to the user on https://pic-iot.com.

PIC-IoT WAThe application publishes data through Amazon Web Services, and the firmware is available on GitHub: https://github.com/microchip-pic-avr-solutions/pic-iot-aws-sensor-node.

PIC-IoT WGThe application publishes data through Google Cloud IoT Core. For in-depth information about the preprogrammeddemo application and how to develop your application, see the full PIC-IoT WG Application User Guide: https://www.microchip.com/mymicrochip/filehandler.aspx?ddocname=en609711.

Setup for Different Cloud AccountsAny PIC-IoT Wx kit can be reprovisioned to publish data to either Microchips sandbox account at Amazon WebServices, Microchips sandbox account at Google Cloud IoT Core, or to a personal account.

Download the IoT Provisioning Tool package, compatible with Windows, Mac and Linux to get started: https://www.microchip.com/mymicrochip/filehandler.aspx?ddocname=en1001525.

PIC-IoT Wx Hardware User GuideApplication User Guide


https://pic-iot.comhttps://pic-iot.comhttps://github.com/microchip-pic-avr-solutions/pic-iot-aws-sensor-nodehttps://github.com/microchip-pic-avr-solutions/pic-iot-aws-sensor-nodehttps://www.microchip.com/mymicrochip/filehandler.aspx?ddocname=en609711https://www.microchip.com/mymicrochip/filehandler.aspx?ddocname=en609711https://www.microchip.com/mymicrochip/filehandler.aspx?ddocname=en1001525https://www.microchip.com/mymicrochip/filehandler.aspx?ddocname=en1001525

4. Hardware User Guide

4.1 On-Board Debugger OverviewPIC-IoT Wx contains an on-board debugger for programming and debugging. The on-board debugger is a compositeUSB device consisting of several interfaces:

• A debugger that can program and debug the PIC24FJ128GA705 in MPLAB X IDE• A mass storage device that allows drag-and-drop programming of the PIC24FJ128GA705• A virtual serial port (CDC) that is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the

PIC24FJ128GA705, and provides an easy way to communicate with the target application through terminalsoftware

• A Data Gateway Interface (DGI) for code instrumentation with logic analyzer channels (debug GPIO) to visualizeprogram flow

The on-board debugger controls a Power and Status LED (marked PS) on the PIC-IoT Wx Board. The table belowshows how the LED is controlled in different operation modes.

Table 4-1. On-Board Debugger LED Control

Operation Mode Power and Status LED

Boot Loader mode The LED blinks slowly during power-up

Power-up The LED is ON

Normal operation The LED is ON

Programming Activity indicator: The LED blinks slowly during programming/debugging

Drag-and-dropprogramming Success: The LED blinks slowly for 2 sec.

Failure: The LED blinks rapidly for 2 sec.

Fault The LED blinks rapidly if a power Fault is detected

Sleep/Off The LED is OFF. The on-board debugger is either in a sleep mode or powered down.This can occur if the board is externally powered.

Info: Slow blinking is approximately 1 Hz, and rapid blinking is approximately 5 Hz.

4.1.1 DebuggerThe on-board debugger on the PIC-IoT Wx Board appears as a Human Interface Device (HID) on the hostcomputer’s USB subsystem. The debugger supports full-featured programming and debugging of thePIC24FJ128GA705 using MPLAB X IDE.

Remember: Keep the debugger’s firmware up-to-date. Firmware upgrades are done automatically whenusing MPLAB X IDE.

4.1.2 Virtual Serial Port (CDC)The virtual serial port (CDC) is a general purpose serial bridge between a host PC and a target device.

PIC-IoT Wx Hardware User GuideHardware User Guide


4.1.2.1 OverviewThe on-board debugger implements a composite USB device that includes a standard Communications Device Class(CDC) interface, which appears on the host as a virtual serial port. The CDC can be used to stream arbitrary data inboth directions between the host computer and the target: All characters sent through the virtual serial port on thehost computer will be transmitted as UART on the debugger’s CDC TX pin, and UART characters captured on thedebugger’s CDC RX pin will be returned to the host computer through the virtual serial port.

Figure 4-1. CDC Connection

Target MCU

UART TX

UART RX

Debugger

USBCDC RX

CDC TX

PCTerminalSoftware

TargetReceive

TargetSend

TerminalReceive

TerminalSend

Info: As shown in Figure 4-1, the debugger’s CDC TX pin is connected to a UART RX pin on the targetfor receiving characters from the host computer. Similarly, the debugger’s CDC RX pin is connected to aUART TX pin on the target for transmitting characters to the host computer.

4.1.2.2 Operating System SupportOn Windows machines, the CDC will enumerate as Curiosity Virtual COM Port and appear in the Ports section of theWindows Device Manager. The COM port number can also be found there.

Info: On older Windows systems, a USB driver is required for CDC. This driver is included in installationsof MPLAB X IDE.

On Linux machines, the CDC will enumerate and appear as /dev/ttyACM#.

Info: tty* devices belong to the “dialout” group in Linux, so it may be necessary to become a member ofthat group to have permissions to access the CDC.

On MAC machines, the CDC will enumerate and appear as /dev/tty.usbmodem#. Depending on which terminalprogram is used, it will appear in the available list of modems as usbmodem#.

Info: For all operating systems: Be sure to use a terminal emulator that supports DTR signaling. SeeSection 3.1.2.4 “Signaling”.

4.1.2.3 LimitationsNot all UART features are implemented in the on-board debugger CDC. The constraints are outlined here:

• Baud rate: Must be in the range of 1200 bps to 500 kbps. Any baud rate outside this range will be set to theclosest limit, without warning. Baud rate can be changed on-the-fly.

• Character format: Only 8-bit characters are supported.



• Parity: Can be odd, even, or none.• Hardware flow control: Not supported.• Stop bits: One or two bits are supported.

4.1.2.4 SignalingDuring USB enumeration, the host OS will start both communication and data pipes of the CDC interface. At thispoint, it is possible to set and read back the baud rate and other UART parameters of the CDC, but data sending andreceiving will not be enabled.

When a terminal connects on the host, it must assert the DTR signal. As this is a virtual control signal implementedon the USB interface, it is not physically present on the board. Asserting the DTR signal from the host will indicate tothe on-board debugger that a CDC session is active. The debugger will then enable its level shifters (if available), andstart the CDC data send and receive mechanisms.

Deasserting the DTR signal will not disable the level shifters but will disable the receiver so no further data will bestreamed to the host. Data packets that are already queued up for sending to the target will continue to be sent out,but no further data will be accepted.

Remember: Set up the terminal emulator to assert the DTR signal. Without the signal, the on-boarddebugger will not send or receive any data through its UART.

Tip: The on-board debugger’s CDC TX pin will not be driven until the CDC interface is enabled by thehost computer. Also, there are no external pull-up resistors on the CDC lines connecting the debugger andthe target, which means that during power-up, these lines are floating. To avoid any glitches resulting inunpredictable behavior like framing errors, the target device should enable the internal pull-up resistor onthe pin connected to the debugger’s CDC TX pin.

4.1.2.5 Advanced Use

CDC Override ModeIn normal operation, the on-board debugger is a true UART bridge between the host and the device. However, incertain use cases, the on-board debugger can override the basic operating mode and use the CDC TX and RX pinsfor other purposes.

Dropping a text file into the on-board debugger’s mass storage drive can be used to send characters out of thedebugger’s CDC TX pin. The filename and extension are trivial, but the text file must start with the characters:CMD:SEND_UART=

The maximum message length is 50 characters – all remaining data in the frame are ignored.

The default baud rate used in this mode is 9600 bps, but if the CDC is already active or has been configured, thepreviously used baud rate still applies.

USB-Level Framing ConsiderationsSending data from the host to the CDC can be done byte-wise or in blocks, which will be chunked into 64-byte USBframes. Each such frame will be queued up for sending to the debugger’s CDC TX pin. Transferring a small amountof data per frame can be inefficient, particularly at low baud rates, because the on-board debugger buffers framesand not bytes. A maximum of four 64-byte frames can be active at any time. The on-board debugger will throttle theincoming frames accordingly. Sending full 64-byte frames containing data is the most efficient method.

When receiving data on the debugger’s CDC RX pin, the on-board debugger will queue up the incoming bytes into64-byte frames, which are sent to the USB queue for transmission to the host when they are full. Incomplete framesare also pushed to the USB queue at approximately 100 ms intervals, triggered by USB start-of-frame tokens. Up toeight 64-byte frames can be active at any time.



If the host (or the software running on it) fails to receive data fast enough, an overrun will occur. When this happens,the last-filled buffer frame will be recycled instead of being sent to the USB queue, and a full frame of data will belost. To prevent this occurrence, the user must ensure that the CDC data pipe is being read continuously, or theincoming data rate must be reduced.

4.1.3 Mass Storage DeviceThe on-board debugger includes a simple Mass Storage Device implementation, which is accessible for read/writeoperations via the host operating system to which it is connected.

It provides:• Read access to basic text and HTML files for detailed kit information and support• Write access for programming Intel® HEX formatted files into the target device’s memory• Write access for simple text files for utility purposes

4.1.3.1 Mass Storage Device ImplementationThe on-board debugger implements a highly optimized variant of the FAT12 file system that has several limitations,partly due to the nature of FAT12 itself and optimizations made to fulfill its purpose for its embedded application.

The Curiosity Nano USB Device is USB Chapter 9-compliant as a mass storage device but does not, in any way,fulfill the expectations of a general purpose mass storage device. This behavior is intentional.

When using the Windows operating system, the on-board debugger enumerates as a Curiosity Nano USB Devicethat can be found in the disk drives section of the device manager. The CURIOSITY drive appears in the file managerand claims the next available drive letter in the system.

The CURIOSITY drive contains approximately one MB of free space. This does not reflect the size of the targetdevice’s Flash in any way. When programming an Intel® HEX file, the binary data are encoded in ASCII withmetadata providing a large overhead, so one MB is a trivially chosen value for disk size.

It is not possible to format the CURIOSITY drive. When programming a file to the target, the filename may appear inthe disk directory listing. This is merely the operating system’s view of the directory, which, in reality, has not beenupdated. It is not possible to read out the file contents. Removing and replugging the board will return the file systemto its original state, but the target will still contain the application that has been previously programmed.

To erase the target device, copy a text file starting with “CMD:ERASE” onto the disk.By default, the CURIOSITY drive contains several read-only files for generating icons as well as reporting status andlinking to further information:

• AUTORUN.ICO – icon file for the Microchip logo• AUTORUN.INF – system file required for Windows Explorer to show the icon file• CLICK-ME.HTM – redirect to the PIC-IoT Wx web demo application• KIT-INFO.HTM – redirect to the development board website• KIT-INFO.TXT – a text file containing details about the board’s debugger firmware version, board name, USB

serial number, device, and drag-and-drop support• PUBKEY.TXT – a text file containing the public key for data encryption• STATUS.TXT – a text file containing the programming status of the board

Info: STATUS.TXT is dynamically updated by the on-board debugger. The contents may be cached bythe OS and, therefore, do not reflect the correct status.

4.1.3.2 Configuration Words

Configuration Words (PIC® MCU Targets)Configuration Word settings included in the project being programmed after program Flash is programmed. Thedebugger will not mask out any bits in the Configuration Words when writing them, but since it uses Low-VoltageProgramming mode, it is unable to clear the LVP Configuration bit. If the incorrect clock source is selected, for



example, and the board does not boot, it is always possible to perform a bulk erase (always done beforeprogramming) and restore the device to its default settings.

4.1.3.3 Special CommandsSeveral utility commands are supported by copying text files to the mass storage disk. The filename or extension isirrelevant – the command handler reacts to content only.

Table 4-2. Special File Commands

Command Content Description

CMD:ERASE Executes a chip erase of the targetCMD:SEND_UART= Sends a string of characters to the CDC UART. See “CDC Override Mode”.CMD:RESET Resets the target device by entering Programming mode and then exiting

Programming mode immediately thereafter. Exact timing can vary according tothe programming interface of the target device. (Debugger firmware v1.16 ornewer.)

Info: The commands listed here are triggered by the content being sent to the mass storage emulateddisk, and no feedback is provided in the case of either success or failure.

4.1.4 Data Gateway Interface (DGI)Data Gateway Interface (DGI) is a USB interface for transporting raw and time-stamped data between on-boarddebuggers and host computer-based visualization tools. MPLAB Data Visualizer is used on the host computer todisplay debug GPIO data. It is available as a plug-in for MPLAB® X IDE or a stand-alone application that can be usedin parallel with MPLAB X IDE.

Although DGI encompasses several physical data interfaces, the PIC-IoT Wx implementation includes logic analyzerchannels:

• One debug GPIO channel (also known as DGI GPIO)

4.1.4.1 Debug GPIODebug GPIO channels are timestamped digital signal lines connecting the target application to a host computervisualization application. They are typically used to plot the occurrence of low-frequency events on a time-axis – forexample, when certain application state transitions occur.

The figure below shows the monitoring of the digital state of a mechanical switch connected to a debug GPIO inMPLAB Data Visualizer.



https://gallery.microchip.com/packages?q=MPLAB-Data-Visualizer

Figure 4-2. Monitoring Debug GPIO with MPLAB Data Visualizer

Debug GPIO channels are timestamped, so the resolution of DGI GPIO events is determined by the resolution of theDGI timestamp module.

Important: Although bursts of higher-frequency signals can be captured, the useful frequency range ofsignals for which debug GPIO can be used is up to about 2 kHz. Attempting to capture signals above thisfrequency will result in data saturation and overflow, which may cause the DGI session to be aborted.

4.1.4.2 TimestampingDGI sources are timestamped as they are captured by the debugger. The timestamp counter implemented in theCuriosity Nano debugger increments at 2 MHz frequency, providing a timestamp resolution of a half microsecond.

4.2 On-Board Debugger ConnectionsThe table below shows the connections between the target and the debugger section. All connections between thetarget and the debugger are tri-stated as long as the debugger is not actively using the interface. Hence, since thereare little contaminations of the signals, the pins can be configured to anything the user wants.

For further information on how to use the capabilities of the on-board debugger, see 4.1 On-Board DebuggerOverview.

Table 4-3. Debugger Connections

Debugger Pin PIC24FJ128GA705 Pin Function Shared Functionality

DBG0 ICSPDAT Program/Debug Data —

DBG1 ICSPCLK Program/Debug Clock —

DBG2 RA11 DGI GPIO0 —

DBG3 MCLR RESET —

CDC TX RC9 UART RX —

CDC RX RC8 UART TX —



4.3 Power

4.3.1 Power SourceThe board can be powered through the USB port or by a Li-Ion/LiPo battery. The kit contains one buck converter forgenerating 3.3V for the debugger, target, and peripherals.

The maximum available current from the USB is limited to 500 mA. The current will be shared between charging thebattery (if connected) and the target application section.

Figure 4-3. Power Supply Block Diagram

USB Debugger

Power source

Cut strap

Power consumer

Power converter

VUSBMIC33050

(buck)

MCP73871Li-Ion / Li-Po

battery charger

Battery Charger

Battery Connector

(JST)

VCC_P3V3

VBAT

VMUX

cut-strap

Peripherals mBUS

WINC1510

PIC24FJ128GA705

cut-strap

4.3.2 Battery ChargerPIC-IoT Wx features an MCP73871 Li-Ion/LiPo charger and JST battery connector on board. The charger isconfigured to limit the charge current to 100 mA to prevent the overcharging of small capacity batteries. Minimumrecommended battery capacity is 400 mAh.

WARNINGThe MCP73871 has a battery charge voltage of 4.2V. Make sure your battery has the same chargevoltage.

Table 4-4. Charger Status LEDs

LEDs Function

Red (charging) The battery is being charged by the USB

Red (discharging) The battery voltage is low. Triggers if the voltage is under 3.1V.

Green Charge complete

Red and Green Timer Fault. The six-hour charge cycle has timed out before the completecharge.

4.3.3 Hardware ModificationsOn the bottom side of the PIC-IoT Wx board, there are two cut-straps as shown in the figure below. These areintended for current measurement purposes. Do not leave these unconnected as the microcontrollers might getpowered through the I/O’s.



Figure 4-4. VCC Cut-Straps

The 5V supply to the mikroBUS socket is connected by default. To remove 5V from the socket, desolder the 0-ohmresistor (0402) below the 5V text, as shown in the figure below.

Figure 4-5. mikroBUS™ 5V Footprint

4.4 Peripherals

4.4.1 PIC24FJ128GA705Microchip’s PIC24FJ128GA705 features 128KB of ECC Flash, 16KB of RAM, and eXtreme Low Power (XLP) with 16MIPS performance. It has 12-bit ADC at 200ksps with 14 analog inputs, and a robust set of digital communicationsand timer with peripheral pin select. Within the same family, there are variants with 64KB or 256KB Flash forapplications that require more or less memory. The PIC24FJ128GA705 is available in a 48-pin package, while othervariants are available in 28-pin and 44-pin packages. The PIC24F family is ideally suited for low power IoT sensornode applications.

4.4.2 mikroBUS™ SocketPIC-IoT Wx features a mikroBUS Socket footprint for expanding the functionality of the development kit usingMikroElektronika Click Boards and other mikroBUS add-on boards. The socket is populated with two 1x8 2.54 mmpitch female headers and is ready to mount add-on boards.

Table 4-5. mikroBUS™ Socket Pinout

mikroBUS™ Socket Pin PIC24FJ128GA705 Pin Function Shared Functionality

AN RB14 AN6 —

RST RB15 GPIO —

CS RA0 SPI2 SS —

SCK RA1 SPI2 SCK —

MISO RB0 SPI2 MISO —

MOSI RB1 SPI2 MOSI —

+3.3V VDD VCC_TARGET, 3.3Vsupply

—

GND GND Ground —

PWM RC6 MCCP —



...........continuedmikroBUS™ Socket Pin PIC24FJ128GA705 Pin Function Shared Functionality

INT RB7 GPIO —

RX RB6 UART2 RX —

TX RB5 UART2 TX —

SCL RB8 I2C SCL1 —

SDA RB9 I2C SDA1 —

+5V — VCC_MUX1, MCP73871output

—

GND GND Ground —

Info: 1) A 0-ohm resistor has been soldered to connect the VCC_MUX pin to the mikroBUS socket. If an add-onmodule cannot handle 5V on this pin, the 0-ohm resistor has to be removed. For more information, see 4.3.3 Hardware Modifications.

4.4.3 WINC1510 Wi-Fi ModuleMicrochip's WINC1510 is a low-power consumption 802.11 b/g/n IoT module, specifically optimized for low-power IoTapplications. The module integrates Power Amplifier (PA), Low-Noise Amplifier (LNA), switch, power management,and a printed antenna or a micro co-ax (U.FL) connector for an external antenna resulting in a small form factor(21.7x14.7x 2.1 mm) design. It is interoperable with various vendors’ 802.11 b/g/n access points. This moduleprovides SPI ports to interface with a host controller.

WINC1510 provides internal Flash memory as well as multiple peripheral interfaces, including UART and SPI. Theonly external clock source needed for WINC1510 is the built-in, high-speed crystal or oscillator (26 MHz). WINC1510is available in a QFN package or as a certified module.

The communication interface between the PIC24FJ128GA705 and the WINC1510 Wi-Fi module is SPI, together withsome enable signals and interrupt. The rest of the connections are left unconnected.

Table 4-6. WINC1510 Connections

WIN1510 Pin PIC24FJ128GA705 Pin Function Shared Functionality

4 RESET_N RA2 GPIO —

9 GND GND Ground —

10 SPI_CFG VCC_TARGET — —

11 WAKE RA8 GPIO —


13 IRQN RA12 EXT INT —

15 SPI_MOSI RC0 SPI1 MOSI —

16 SPI_SSN RC1 SPI1 SS —

17 SPI_MISO RA13 SPI1 MISO —

18 SPI_SCK RC2 SPI1 SCK —

20 VBAT VCC_TARGET 3.3V supply —

22 CHIP_EN RA3 GPIO —



...........continuedWIN1510 Pin PIC24FJ128GA705 Pin Function Shared Functionality

23 VDDIO VCC_TARGET 3.3V supply —


29 PADDLE GND — —

4.4.4 ATECC608AThe ATECC608A is a secure element from the Microchip CryptoAuthentication portfolio with advanced Elliptic CurveCryptography (ECC) capabilities. With ECDH and ECDSA being built right in, this device is ideal for the rapidlygrowing Internet of Things (IoT) market by easily supplying the full range of security, such as confidentiality, dataintegrity, and authentication to systems with MCU or MPUs running encryption/decryption algorithms. Similar to allMicrochip CryptoAuthentication products, the new ATECC608A employs ultra-secure, hardware-based cryptographickey storage and cryptographic countermeasures that eliminate any potential backdoors linked to softwareweaknesses.

ATECC608A CryptoAuthentication device on the PIC-IoT Wx board is used to authenticate the hardware with cloudproviders to uniquely identify every board.

Note: 7-bit I2C address: 0x58.

Table 4-7. ATECC608A Connections

ATECC608A Pin PIC24FJ128GA705 Pin

Function Shared Functionality

SDA RB2 I2C SDA2 MCP9808

SCL RB3 I2C SCL2 MCP9808

4.4.5 Temperature SensorThe MCP9808 digital temperature sensor converts temperatures between -20°C and +100°C to a digital word with±0.25°C/±0.5°C (typical/maximum) accuracy.

Additional features:• Accuracy:

– ±0.25°C (typical) from -40°C to +125°C– ±0.5°C (maximum) from -20°C to +100°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)

The MCP9808 temperature sensor is connected to the PIC24FJ128GA705 through I2C and a GPIO for the user-configurable alert output.

Note: 7-bit I2C address: 0x18.



Table 4-8. MCP9808

MCP9808 Pin PIC24FJ128GA705 Pin


SDA RB2 I2C SDA2 ATECC608A

SCL RB3 I2C SCL2 ATECC608A

Alert RB13 External Interrupt —

4.4.6 Light SensorA TEMT6000X01 light sensor is mounted on the PIC-IoT Wx board for measuring the light intensity. The sensor is acurrent source that will induce a voltage across the series resistor, which in turn can be measured by thePIC24FJ128GA705 ADC. The current is exponentially relative to illuminance, from about 10 µA@20lx to 50µA@100lx. The series resistor has a value of 10 kΩ.

Table 4-9. Light Sensor Connection

PIC24FJ128GA705Pin


RB12 ADC AN8 —

4.4.7 LEDThere are four LEDs available on the PIC-IoT Wx board that can be controlled with PWM or GPIO. The LEDs can beactivated by driving the connected I/O line to GND.

Table 4-10. LED Connections

PIC24FJ128GA705Pin

Function Description

RB4 OCM2A Red LED

RC3 OCM2B Yellow LED

RC4 OCM3A Green LED

RC5 OCM3B Blue LED

4.4.8 Mechanical ButtonsPIC-IoT Wx contains two mechanical buttons. These are generic user-configurable buttons. When a button ispressed, it will drive the connected I/O line to ground (GND).

Info: There are no pull-up resistors connected to the generic user buttons. Remember to enable theinternal pull-up in the PIC24FJ128GA705 to use the buttons.

Table 4-11. Mechanical Button

PIC24FJ128GA705Pin

Description Shared Functionality

RA7 User switch 0 (SW0) —

RA10 User switch 1 (SW1) —



5. Regulatory ApprovalThe PIC-IoT Wx development board has been testedby the following standards:

Emission:

• FCC Part 15 subpart B:2018 (Class B)• EN55032:2015 (Class B)

Immunity:• EN55024:2010+A1:2015• EN61000-4-2:2009 (contact: level 2 (±4 kV), air: level3 (±8 kV))• EN61000-4-3:2006+A2:2010 (80 - 1000 MHz, level 2 (3 V/M))• EN61000-4-8:2010 (level 2 (3 A/m), continuous field)

The development board contains the wireless transmitter module ATWINC1510-MR210PB, which has the followingapproval and/or registrations:

• United States/FCC ID: 2ADHKATWINC1510• Canada

– IC: 20266-ATWINC1510– HVIN: ATWINC1510-MR210PB– PMN: ATWINC1510-MR210PB

• Europe - CE• Japan/MIC: 005-101762• Korea/KCC: R-CRM-mcp-WINC1510MR210P• Taiwan/NCC: CCAN18LP0320T0• China/SRRC: CMIIT ID: 2018DJ1310

5.1 United StatesContains Transmitter Module FCC ID: 2ADHKATWINC1510.

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 ofthe FCC Rules. These limits are designed to provide reasonable protection against harmful interference in aresidential installation. This equipment generates, uses, and can radiate radio frequency energy, and if not installedand used in accordance with the instructions, may cause harmful interference to radio communications. However,there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmfulinterference to radio or television reception, which can be determined by turning the equipment off and on, the user isencouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna• Increase the separation between the equipment and receiver• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected• Consult the dealer or an experienced radio/TV technician for help

5.2 CanadaContains IC: 20266-ATWINC1510.

This device complies with Industry Canada's license-exempt RSS standard(s). Operation is subject to the followingtwo conditions:

(1) This device may not cause interference, and

(2) This device must accept any interference, including interference that may cause undesired operation of thedevice.

PIC-IoT Wx Hardware User GuideRegulatory Approval


Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence.L'exploitation est autorisée aux deux conditions suivantes:

(1) l'appareil ne doit pas produire de brouillage, et

(2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage est susceptibled'en compromettre le fonctionnement.

Guidelines on Transmitter Antenna for License Exempt Radio Apparatus:

Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum(or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users,the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is notmore than that necessary for successful communication.

Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut fonctionner avec une antenned'un type et d'un gain maximal (ou inférieur) approuvé pour l'émetteur par Industrie Canada. Dans le but de réduireles risques de brouillage radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et songain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas l'intensité nécessaire àl'établisse-ment d'une communication satisfaisante.

5.3 TaiwanContains module: CCAN18LP0320T0.

注意 !

依據低功率電波輻射性電機管理辦法

第十二條經型式認證合格之低功率射頻電機，非經許可，公司、商號或使用者均不得擅自變更頻率、加大功率或變更原設計之特性及功能。

第十四條低功率射頻電機之使用不得影響飛航安全及干擾合法通信；經發現有干擾現象時，應立即停用，並改善至無干擾時方得繼續使用。

前項合法通信，指依電信規定作業之無線電信。

低功率射頻電機須忍受合法通信或工業、科學及醫療用電波輻射性電機設備之干擾。

5.4 List of Antenna TypesATWINC1510-MR210 does not allow the use of external antennas and is tested with the PCB antenna on themodule.

PIC-IoT Wx Hardware User GuideRegulatory Approval


6. Hardware Revision History and Known IssuesThis user guide is written to provide information about the latest available revision of the board. The followingsections contain information about known issues, a revision history of older revisions, and how older revisions differfrom the latest revision.

6.1 Identifying Product ID and RevisionThe revision and product identifier of the PIC-IoT Wx board can be found in two ways: Either by utilizing the MPLABX IDE Kit Window or by looking at the sticker on the bottom side of the PCB.

By connecting a PIC-IoT Wx to a computer with MPLAB X IDE running, the Kit Window will pop up. The first six digitsof the serial number, which is listed under kit information, contain the product identifier and revision.

Tip: The Kit Window can be opened in MPLAB® X IDE through the menu bar Window > Kit Window.

The same information can be found on the sticker on the bottom side of the PCB. Most boards will have the identifierand revision printed in plain text as A09-nnnn\rr, where “nnnn” is the identifier, and “rr” is the revision. Boards withlimited space have a sticker with only a data matrix code, containing the product identifier, revision, and serialnumber.

The serial number string has the following format:

"nnnnrrssssssssss"

n = product identifier

r = revision

s = serial number

The product identifier for PIC-IoT WG is A09-3261.

The product identifier for PIC-IoT WA is A09-3352.

6.2 PIC-IoT WG

6.2.1 Revision 3Revision 3 of PIC-IoT WG has 5V applied to the mikroBUS socket by default (R204 is populated). It is otherwiseidentical to revision 2.

6.2.2 Revision 2Revision 2 of PIC-IoT WG is the initial released revision. R204, the 0-ohm resistor that applies 5V to mikroBUSsocket, is not populated on this revision.

6.3 PIC-IoT WA

6.3.1 Revision 1Revision 1 of PIC-IoT WA is the initial released revision. The hardware is identical to PIC-IoT WG revision 3.

Reconfiguration of Wi-Fi credentials does not work with the application firmware preprogrammed on this revision ofthe kit. Follow the instructions in 2.1 Quick Start to download and upgrade the application firmware.

PIC-IoT Wx Hardware User GuideHardware Revision History and Known Issues


7. Document Revision HistoryDoc. rev. Date Comment

A 03/2020 Initial document release.

PIC-IoT Wx Hardware User GuideDocument Revision History


8. Appendix

8.1 SchematicFigure 8-1. PIC-IoT Wx Schematic

11

22

33

44

55

66

77

88

DD

CC

BB

AA

2 of

4

PIC-

IoT

WA

2019

-12-

12PI

C-Io

T_W

A_T

arge

t_M

CU.S

chD

oc

Proj

ect T

itle

PCB

Ass

embl

y N

umbe

r:PC

BA R

evisi

on:

File

:PC

B N

umbe

r:PC

B Re

visio

n:

Des

igne

d wi

th

Dra

wn

By:

TF Shee

t Titl

eTa

rget

MCU

Engi

neer

:TF

A08

-299

31

Size

A3

A09

-335

21

Page

:D

ate:A

ltium

.com

100n

C204

GN

D

VCC

_TA

RGET

GN

D

100n

C200

1kR2

13

USE

R L

EDS

VCC

_TA

RGET

RA7_SW0

USE

R B

UTT

ON

S

330RR207

PIC2

4FJ1

28G

A70

5

DBG0

CDC_

UART

TX RXU

ART

DBG1

DBG2

2185-108SS0CYNP1

1 2 3 4 5 6 7 8

J201

2185-108SS0CYNP1

1 2 3 4 5 6 7 8

J202

mik

roBU

S

GN

DG

ND

AN

RST

CS SCK

MIS

OM

OSI

+3.3

VG

ND

PWM

INT

RX TX SCL

SDA

+5V

GN

D

Hea

der

(Fem

ale)

TM

WIN

C151

0

10uF

C203

10nF

C202

124 3

5KMR2

21G

SW20

0

330RR208 12

4 3

5KMR2

21G

SW20

1

1kR2

121kR2

091kR2

06

GN

D

SDA

5SC

L6

GND

4

VCC

8

PAD

9

NC1

NC2

NC3

NC7

U20

2

GN

D

GN

D

100kR200

RC1_

SPI_

SS

VCC

_TA

RGET

VCC

_TA

RGET

RB8_

I2C1

_SCL

RB9_

I2C1

_SD

A

VCC

_TA

RGET

GN

D

100n

C205

RB0_

SPI_

MIS

ORA

1_SP

I_SC

K

RB1_

SPI_

MO

SI

RA10_SW1

GN

D

Cry

ptoA

uthe

ntic

atio

nTM

Tem

pera

ture

Sen

sor

GN

D

VCC

_TA

RGET

100k

R211

VCC

_TA

RGET

4.7kR202

4.7kR203

VCC

_TA

RGET

VCC

_TA

RGET

TP20

2

TP204TP205TP206

TP20

3

21

GRE

EN L

EDSM

L-P1

2MTT

86R

D20

1RED

LED

SML-

P12V

TT86

R

21

D20

0

I2C

addr

ess:

0x18

WIN

C_U

ART

_RX

WIN

C_U

ART

_TX

RC6_

OCM

xn_P

WM

RA2_

WIN

C_RS

T

RB15

_MBU

S_RS

T

RA8_

WIN

C_W

AK

E RA3_

WIN

C_EN

WIN

C_SP

I_CF

G

RB3_I2C2_SCLRB2_I2C2_SDA

RB14

_MBU

S_A

INRB

7_M

BUS_

INT

RB13_TEMP_INT

VCC_P1V3

21

YEL

LOW

LED

SML-

P12Y

TT86

R

D20

3

Def

ault

I2C

addr

ess:

0x58

21

BLU

E LE

DSM

LP13

BC8T

T86

D20

2

VCC

_TA

RGET

VCC

_TA

RGET

1 2TEM

T600

0

Q20

0

GN

D

VCC

_TA

RGET

SDA

1SC

L2

ALER

T3

GND

4A2

5A1

6A0

7VD

D8

EP 9

MCP

9808

U20

3

GN

D

RB5_

UA

RT2_

TXRB

6_U

ART

2_RX

RA0_

SPI_

CS

Ligh

t Sen

sor

RB12

_LIG

HT_

SEN

S

TP20

1TP

200

10kR210

100n

C206

SW1

SW0

100kR201 G

ND

VCC

_MU

X0R R2

04+5

V

TP20

7

TP20

8TP

209

GN

D

GN

D

RB10

_ICS

PDA

TRB

11_I

CSPC

LK

MCL

R

ERR

DATA

CON

N

WIF

I

ATEC

C608

A

ATW

INC1

510-

MR2

10PB

1961

RESE

T_N

4

CHIP_EN 22VDDIO 23

VBAT 20

WAKE

11

UART

_TXD

14

UART

_RXD

19

NC7

1P3V_TP 24

SPI_

SCK

18SP

I_MI

SO17

SPI_

MOSI

15SP

I_SS

N16

SPI_

CFG

10

GPIO

_61

GPIO_5 27GPIO_4 26GPIO_3 25

I2C_

SCL

2I2

C_SD

A3

GPIO_1/RTC 21

NC5

NC6

NC8

IRQN

13

GND 28

GND

12

GND

9

PADDLE 29

U20

0

DBG3

RA13

_SPI

_MIS

ORC

2_SP

I_SC

K

RC0_

SPI_

MO

SI


RA11

_DG

I_D

BG2

4.7kR215

4.7kR216

VCC

_TA

RGET

4.7kR214

4.7kR205

GN

D

VCC

_TA

RGET

100n

C208

GN

DV

CC_T

ARG

ET

RB10

_ICS

PDA

TRB

11_I

CSPC

LK

MCLRG

ND


RB9_

I2C1

_SD

ARB8_I2C1_SCL

VCA

P

RB9

1RC

62

RC7

3RC

84

RC9

5VS

S6

VCAP

7RA

118

RB10

/PGD

29

RB11

/PGC

210

RB12

11RB

1312

RA10 13RA7 14RB14 15RB15 16AVSS 17AVDD 18MCLR 19RA12 20RA0 21RA1 22RB0/PGD1 23RB1/PGC1 24

RB2

25RB

326

RC0

27RC

128

RC2

29VD

D30

VSS

31RA

1332

OSCI

/RA2

33OS

CO/R

A334

RA8

35SO

SCI/

RB4

36

RA437 RA938 RC339 RC440 RC541 VSS42 VDD43 RA1444 PGD3/RB545 PGC3/RB646 RB747 RB848EP49

PIC2

4FJ1

28G

A70

5T-I/

M4

U20

1

RC0_

SPI_

MO

SI

RB14_MBUS_AINRB15_MBUS_RST

RB12

_LIG

HT_

SEN

S

RC1_

SPI_

SS

RB6_UART2_RXRB5_UART2_TX

RB7_MBUS_INT

RA13

_SPI

_MIS

O

RC2_

SPI_

SCK

RA3_

WIN

C_EN

RA8_

WIN

C_W

AK

E

RA2_

WIN

C_RS

T

RB4_

OCM

xn_E

RRO

R

RC4_

OCM

xn_C

ON

NRC

5_O

CMxn

_WIF

I

RC3_

OCM

xn_D

ATA

RA12_WINC_INT

RC8_

CDC_

TX

RB13

_TEM

P_IN

T

RC9_

CDC_

RX

RA10_SW1RA7_SW0

RA11

_DG

I_D

BG2

RA12

_WIN

C_IN

T

RB4_OCMxn_ERROR

RC4_OCMxn_CONNRC5_OCMxn_WIFI

RC3_OCMxn_DATARC

8_CD

C_TX

RC9_

CDC_

RX

RC6_

OCM

xn_P

WM

RB0_SPI_MISORA1_SPI_SCK

RB1_SPI_MOSI

RA0_SPI_CS10

uF/1

6VC2

07

10kR217

PIC-IoT Wx Hardware User GuideAppendix


11

22

33

44

55

66

77

88

DD

CC

BB

AA

3 of

4

PIC-

IoT

WA

2019

-12-

12PI

C-Io

T_W

A_D

ebug

ger.S

chD

oc

Proj

ect T

itle

PCB

Ass

embl

y N

umbe

r:PC

BA R

evisi

on:

File

:PC

B N

umbe

r:PC

B Re

visio

n:

Des

igne

d wi

th

Dra

wn

By:

TF Shee

t Titl

eD

ebug

ger

Engi

neer

:TF

A08

-299

31

Size

A3

A09

-335

21

Page

:D

ate:A

ltium

.com

DEB

UG

GER

USB

MIC

RO

-B C

ON

NEC

TOR

GN

D

USB

D_P

USB

D_N

100n

C107

100n

C108

RX TXU

ART

CDC_

UART

1kR1

06V

CC_D

EBU

GG

ER

100n

C105

GN

D

SRST

STAT

US_

LED

SHIE

LD

VBU

S

VCC

_DEB

UG

GER

GN

D

TP10

0

Testp

oint

Arra

y

12

34

56

78

910

TCK

TDO

TMS

Vsu

pTD

IG

ND

TRST

SRST

VTr

efG

ND

J102

DBG0

21

GRE

EN L

EDSM

L-P1

2MTT

86R

D10

2

VBUS

1D-

2D+

3

GND

5SH

IELD

16

SHIE

LD2

7

ID4

SHIE

LD3

8SH

IELD

49 M

U-M

B014

2AB2

-269

J103

PAD

33

PA00

1PA

012

PA02

3PA

034

GND 10VDDANA 9

PA04

5PA

056

PA06

7PA

078

PA08 11PA09 12PA10 13PA11 14PA14 15PA15 16

PA16

17PA

1718

PA18

19PA

1920

PA22

21US

B_SO

F/PA

2322

USB_

DM/P

A24

23US

B_DP

/PA2

524

PA2725 RESETN26 PA2827 GND28 VDDCORE29 VDDIN30 SWDCLK/PA3031 SWDIO/PA3132

SAM

D21

E18A

-MU

TU

100

USB

D_P

USB

D_N

GN

D

1uC106

VCC

_MCU

_CO

RE

VCC

_DEB

UG

GER

VCC

_DEB

UG

GER

GN

D GN

D

GN

D

GN

D

DBG2

S1_0

_TX

S0_2

_TX

DA

CV

TG_A

DC

RESE

RVED

S0_3

_CLK

DBG0_CTRL

CDC_

TX_C

TRL

BOO

T

DEB

UG

GER

PO

WER

/STA

TUS

LED

1kR1

10

DBG1

DBG1_CTRL

REG_ENABLE

100kR107

100kR108

SWCL

K

100kR113 G

ND

SRST

DEB

UG

GER

TES

TPO

INT DBG2_CTRL

CDC_

RX_C

TRL

100kR111

SWCL

K

DBG2_GPIO

VBUS_ADC

VTG_ADC

ID_S

YS

VTG

_EN

VBU

S_A

DC

SWD

IO

SWD

IO

GN

DV

OFF

VCC

_DEB

UG

GER

330R

R112330R

R114330R

R109

Cros

sing

RX/T

X h

ere!

DBG

0

DBG

2

S1_1

_RX

S0_0

_RX

VCC

_P3V

3

GN

D

GN

D

4.7u

FC1

00

GN

D

Li-P

o/Li

-Ion

Batte

ry

4.7u

FC1

01

GN

D

560p

C102

SW4

PGND 2

VOUT

7

SNS

10EN

9VO

UT8

SW5

VIN

1

AGND 12

EP 13

SW3

SW6

FB/C

FF11

MIC

3305

0-SY

HL

U10

2

100k

R100

1kR1

02RE

D L

EDSM

L-P1

2VTT

86R

21

D10

1

J100

10k

R103

GN

D

10uF

C103

MC

P738

71OU

T1

VPCC

2

SEL

3PR

OG2

4

THER

M5

PG6

STAT

27

STAT

1/LB

O8

TE9

IN18

IN19

CE17

VSS 10VSS 11EP 21

PROG

312

PROG

113

VBAT

14VB

AT15

VBAT

16OU

T20

U10

1

GN

D

4.7u

FC1

04

GN

D

VBU

S

10k

R104

GN

D

GN

DV

BUS

100k

R105

1kR1

01V

CC_B

AT

POW

ER S

UPP

LY A

ND

BA

TTER

Y C

HA

RG

ER

21

GRE

EN L

EDSM

L-P1

2MTT

86R

D10

0

1 2

J101

VCC

_MU

X

VCC

_MU

X

J104

VCC

_DEB

UG

GER

VCC

_TA

RGET

DBG

1

VBU

S

DBG3

GN

D

DBG

3_CT

RL1

23

DM

N65

D8L

FBQ

100

1kR1

15

DBG

3_CT

RL

DBG

3 O

PEN

DR

AIN

Sign

al

DBG

0

DBG

1

DBG

2

DBG

3

ICSP

Inte

rface

DAT

CLK

GPI

O

MCL

R

CD

C T

X

CD

C R

X

UA

RT R

X

UA

RT T

X

TAR

GET

VC

C-

Prog

ram

min

g co

nnec

tor

for f

acto

ry p

rogr

amm

ing

of

the

Deb

ugge

r

MIC

3305

0:Vi

n: 2

.5V

to 5

.5V

Vout

: Fix

ed 3

.3V

Imax

: 600

mA



8.2 Assembly DrawingFigure 8-2. PIC-IoT Wx Assembly Drawing Top

®PAC10002

PAC10001 COC100

PAC10102 PAC10101 COC101

PAC10201 PAC10202 COC102 PAC10302 PAC10301 COC103

PAC10402 PAC10401 COC104

PAC10502 PAC10501 COC105

PAC10602 PAC10601 COC106


PAC20002 PAC20001 COC200

PAC20202 PAC20201 COC202


PAC20502

PAC20501 COC205

PAC20602 PAC20601 COC206

PAC20701

PAC20702 COC207

PAC20801 PAC20802 COC208

PAD10002 PAD10001 COD100

PAD10101 PAD10102 COD101

PAD10201 PAD10202 COD102

PAD20001 PAD20002 COD200 PAD20101 PAD20102 COD201 PAD20201 PAD20202 COD202 PAD20301 PAD20302 COD203

PAJ10001

PAJ10002 COJ100

PAJ10102 PAJ10101 PAJ10100

COJ101

PAJ10206

PAJ10205

PAJ10204

PAJ10203

PAJ10202

PAJ10201 COJ102

PAJ103011

PAJ103010 PAJ10308

PAJ10309 PAJ10307

PAJ10306 PAJ10301

PAJ10302

PAJ10303

PAJ10304

PAJ10305

PAJ10300

COJ103

PAJ10402

PAJ10401 COJ104

PAJ20105 PAJ20106 PAJ20108 PAJ20107 PAJ20103 PAJ20104 PAJ20102 PAJ20101 PAJ20100 COJ201


COLABEL1 PAQ10001 PAQ10002 PAQ10003 COQ100

PAQ20002 PAQ20003

PAQ20001 COQ200

PAR10002 PAR10001 COR100

PAR10102 PAR10101 COR101

PAR10202 PAR10201 COR102

PAR10302 PAR10301 COR103

PAR10402 PAR10401 COR104

PAR10502 PAR10501 COR105

PAR10601 PAR10602 COR106

PAR10701 PAR10702 COR107 PAR10801 PAR10802 COR108

PAR10901 PAR10902 COR109

PAR11002 PAR11001 COR110

PAR11102 PAR11101 COR111

PAR11201 PAR11202 COR112

PAR11301 PAR11302 COR113

PAR11402 PAR11401 COR114

PAR11502 PAR11501 COR115

PAR20001 PAR20002 COR200

PAR20102

PAR20101 COR201

PAR20201 PAR20202 COR202 PAR20301 PAR20302 COR203 PAR20401 PAR20402 COR204

PAR20502 PAR20501 COR205

PAR20601 PAR20602 COR206

PAR20702

PAR20701 COR207

PAR20801

PAR20802 COR208

PAR20901 PAR20902 COR209

PAR21001 PAR21002 COR210

PAR21101

PAR21102 COR211


PAR21402 PAR21401 COR214


PAR21702 PAR21701 COR217

PASW20005

PASW20002

PASW20001 PASW20004

PASW20003 COSW200 PASW20105

PASW20102

PASW20101 PASW20104

PASW20103 COSW201

PATP10001 COTP100

PATP20001 COTP200 PATP20101 COTP201 PATP20201 COTP202 PATP20301 COTP203 PATP20401 COTP204 PATP20501 COTP205 PATP20601 COTP206

PATP20701 COTP207 PATP20801 COTP208 PATP20901 COTP209

PAU10009

PAU10008 PAU10007 PAU10006 PAU10005 PAU10004 PAU10003 PAU10002 PAU10001

PAU100010

PAU100011

PAU100012

PAU100013

PAU100014

PAU100015

PAU100016

PAU100017 PAU100018 PAU100019 PAU100020 PAU100021 PAU100022 PAU100023 PAU100024 PAU100025

PAU100026 PAU100027

PAU100028

PAU100029

PAU100030

PAU100031 PAU100032

PAU100033 COU100

PAU10101 PAU10102 PAU10103 PAU10104 PAU10105 PAU10106

PAU10107

PAU10108 PAU10109

PAU101010


PAU101017 PAU101018 PAU101019

PAU101020

PAU101021 COU101

PAU102013

PAU10207

PAU10208

PAU10209 PAU102010

PAU102011 PAU102012

PAU10206

PAU10205

PAU10204 PAU10203

PAU10202 PAU10201

COU102


PAU200020



PAU200010

PAU200029 COU200 PAU20101

PAU20102


PAU20109

PAU201010

PAU201011

PAU201012

PAU201013 PAU201014 PAU201015 PAU201016 PAU201017 PAU201018 PAU201019 PAU201020 PAU201021 PAU201022 PAU201023 PAU201024 PAU201025

PAU201026

PAU201027

PAU201028

PAU201029 PAU201030 PAU201031 PAU201032 PAU201033 PAU201034 PAU201035

PAU201036

PAU201037 PAU201038 PAU201039 PAU201040 PAU201041 PAU201042 PAU201043 PAU201044 PAU201045 PAU201046 PAU201047 PAU201048

PAU201049 PAU20100

COU201 PAU20208

PAU20207

PAU20206 PAU20205 PAU20204

PAU20203

PAU20202

PAU20201

PAU20209 COU202

PAU20309 PAU20301 PAU20302

PAU20304

PAU20303 PAU20306

PAU20305

PAU20307 PAU20308

PAU20300 COU203

Figure 8-3. PIC-IoT Wx Assembly Drawing Bottom

RB

5 / T

X

GN

DG

ND

LAB

ELA

N / R

B1

4R

C6

/ PW

M

SC

K / R

A1

MIS

O / R

B0

RB

8 / S

CL

®

cP

CB

A

CS

/ RA

0R

B6

/ RX

+3

.3V

+5

V

RS

T / R

B1

5R

B7

/ INT

MO

SI / R

B1

RB

9 / S

DA

t

-IoTPIC

Eb

R

PAC10002

PAC10001 COC100

PAC10102 PAC10101 COC101


PAC10402 PAC10401 COC104

PAC10502 PAC10501 COC105

PAC10602 PAC10601 COC106


PAC20002 PAC20001 COC200

PAC20202 PAC20201 COC202


PAC20502

PAC20501 COC205

PAC20602 PAC20601 COC206

PAC20701

PAC20702 COC207

PAC20801 PAC20802 COC208

PAD10002 PAD10001 COD100

PAD10101 PAD10102 COD101

PAD10201 PAD10202 COD102

PAD20001 PAD20002 COD200 PAD20101 PAD20102 COD201 PAD20201 PAD20202 COD202 PAD20301 PAD20302 COD203

PAJ10001

PAJ10002 COJ100

PAJ10102 PAJ10101 PAJ10100

COJ101

PAJ10206

PAJ10205

PAJ10204

PAJ10203

PAJ10202

PAJ10201 COJ102

PAJ103011

PAJ103010 PAJ10308

PAJ10309 PAJ10307

PAJ10306 PAJ10301

PAJ10302

PAJ10303

PAJ10304

PAJ10305

PAJ10300

COJ103

PAJ10402

PAJ10401 COJ104



COLABEL1 PAQ10001 PAQ10002 PAQ10003 COQ100

PAQ20002 PAQ20003

PAQ20001 COQ200

PAR10002 PAR10001 COR100

PAR10102 PAR10101 COR101

PAR10202 PAR10201 COR102

PAR10302 PAR10301 COR103

PAR10402 PAR10401 COR104

PAR10502 PAR10501 COR105

PAR10601 PAR10602 COR106


PAR10901 PAR10902 COR109

PAR11002 PAR11001 COR110

PAR11102 PAR11101 COR111

PAR11201 PAR11202 COR112

PAR11301 PAR11302 COR113

PAR11402 PAR11401 COR114

PAR11502 PAR11501 COR115

PAR20001 PAR20002 COR200

PAR20102

PAR20101 COR201

PAR20201 PAR20202 COR202 PAR20301 PAR20302 COR203 PAR20401 PAR20402 COR204

PAR20502 PAR20501 COR205

PAR20601 PAR20602 COR206

PAR20702

PAR20701 COR207

PAR20801

PAR20802 COR208

PAR20901 PAR20902 COR209

PAR21001 PAR21002 COR210

PAR21101

PAR21102 COR211


PAR21402 PAR21401 COR214


PAR21702 PAR21701 COR217

PASW20005

PASW20002

PASW20001 PASW20004

PASW20003 COSW200 PASW20105

PASW20102

PASW20101 PASW20104

PASW20103 COSW201

PATP10001 COTP100

PATP20001 COTP200 PATP20101 COTP201 PATP20201 COTP202 PATP20301 COTP203 PATP20401 COTP204 PATP20501 COTP205 PATP20601 COTP206

PATP20701 COTP207 PATP20801 COTP208 PATP20901 COTP209

PAU10009


PAU100010

PAU100011

PAU100012

PAU100013

PAU100014

PAU100015

PAU100016


PAU100026 PAU100027

PAU100028

PAU100029

PAU100030

PAU100031 PAU100032

PAU100033 COU100


PAU10107

PAU10108 PAU10109

PAU101010


PAU101017 PAU101018 PAU101019

PAU101020

PAU101021 COU101

PAU102013

PAU10207

PAU10208

PAU10209 PAU102010

PAU102011 PAU102012

PAU10206

PAU10205

PAU10204 PAU10203

PAU10202 PAU10201

COU102


PAU200020



PAU200010

PAU200029 COU200 PAU20101

PAU20102


PAU20109

PAU201010

PAU201011

PAU201012

PAU201013 PAU201014 PAU201015 PAU201016 PAU201017 PAU201018 PAU201019 PAU201020 PAU201021 PAU201022 PAU201023 PAU201024 PAU201025

PAU201026

PAU201027

PAU201028

PAU201029 PAU201030 PAU201031 PAU201032 PAU201033 PAU201034 PAU201035

PAU201036

PAU201037 PAU201038 PAU201039 PAU201040 PAU201041 PAU201042 PAU201043 PAU201044 PAU201045 PAU201046 PAU201047 PAU201048

PAU201049 PAU20100

COU201 PAU20208

PAU20207

PAU20206 PAU20205 PAU20204

PAU20203

PAU20202

PAU20201

PAU20209 COU202

PAU20309 PAU20301 PAU20302

PAU20304

PAU20303 PAU20306

PAU20305

PAU20307 PAU20308

PAU20300 COU203

8.3 Mechanical DrawingsThe figures below show the board’s mechanical drawing and connector placement.

Figure 8-4. Mechanical Drawing

100mil

1000mil

100mil

600mil

200mil

100mil

800mil

200mil

2500mil

100mil

R 1,20mm x 2R 100mil x 4

16,46mm

R 1,60mm x 4



Figure 8-5. Connector Placement

800mil

500mil

USB

900mil

8,93mm

100mil

LIPOBATTERY



The Microchip WebsiteMicrochip provides online support via our website at http://www.microchip.com/. This website is used to make filesand information easily available to customers. Some of the content available includes:

• Product Support – Data sheets and errata, application notes and sample programs, design resources, user’sguides and hardware support documents, latest software releases and archived software

• General Technical Support – Frequently Asked Questions (FAQs), technical support requests, onlinediscussion groups, Microchip design partner program member listing

• Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing ofseminars and events, listings of Microchip sales offices, distributors and factory representatives

Product Change Notification ServiceMicrochip’s product change notification service helps keep customers current on Microchip products. Subscribers willreceive email notification whenever there are changes, updates, revisions or errata related to a specified productfamily or development tool of interest.

To register, go to http://www.microchip.com/pcn and follow the registration instructions.

Customer SupportUsers of Microchip products can receive assistance through several channels:

• Distributor or Representative• Local Sales Office• Embedded Solutions Engineer (ESE)• Technical Support

Customers should contact their distributor, representative or ESE for support. Local sales offices are also available tohelp customers. A listing of sales offices and locations is included in this document.

Technical support is available through the website at: http://www.microchip.com/support

Microchip Devices Code Protection FeatureNote the following details of the code protection feature on Microchip devices:

• Microchip products meet the specification contained in their particular Microchip Data Sheet.• Microchip believes that its family of products is one of the most secure families of its kind on the market today,

when used in the intended manner and under normal conditions.• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these

methods, to our knowledge, require using the Microchip products in a manner outside the operatingspecifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft ofintellectual property.

• Microchip is willing to work with the customer who is concerned about the integrity of their code.• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code

protection does not mean that we are guaranteeing the product as “unbreakable.”

Code protection is constantly evolving. We at Microchip are committed to continuously improving the code protectionfeatures of our products. Attempts to break Microchip’s code protection feature may be a violation of the DigitalMillennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, youmay have a right to sue for relief under that Act.

Legal NoticeInformation contained in this publication regarding device applications and the like is provided only for yourconvenience and may be superseded by updates. It is your responsibility to ensure that your application meets with



http://www.microchip.com/http://www.microchip.com/pcnhttp://www.microchip.com/support

your specifications. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHEREXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION,INCLUDING BUT NOT LIMITED TO ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY ORFITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. Use of Microchipdevices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend,indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from suchuse. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unlessotherwise stated.

TrademarksThe Microchip name and logo, the Microchip logo, Adaptec, AnyRate, AVR, AVR logo, AVR Freaks, BesTime,BitCloud, chipKIT, chipKIT logo, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, HELDO, IGLOO, JukeBlox,KeeLoq, Kleer, LANCheck, LinkMD, maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo, MOST,MOST logo, MPLAB, OptoLyzer, PackeTime, PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip Designer,QTouch, SAM-BA, SenGenuity, SpyNIC, SST, SST Logo, SuperFlash, Symmetricom, SyncServer, Tachyon,TempTrackr, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip TechnologyIncorporated in the U.S.A. and other countries.

APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, FlashTec, Hyper Speed Control,HyperLight Load, IntelliMOS, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASIC Plus,ProASIC Plus logo, Quiet-Wire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra, TimeProvider,Vite, WinPath, and ZL are registered trademarks of Microchip Technology Incorporated in the U.S.A.

Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, BlueSky, BodyCom,CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController, dsPICDEM,dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, EtherGREEN, In-Circuit Serial Programming, ICSP,INICnet, Inter-Chip Connectivity, JitterBlocker, KleerNet, KleerNet logo, memBrain, Mindi, MiWi, MPASM, MPF,MPLAB Certified logo, MPLIB, MPLINK, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM,PICDEM.net, PICkit, PICtail, PowerSmart, PureSilicon, QMatrix, REAL ICE, Ripple Blocker, SAM-ICE, Serial QuadI/O, SMART-I.S., SQI, SuperSwitcher, SuperSwitcher II, Total Endurance, TSHARC, USBCheck, VariSense,ViewSpan, WiperLock, Wireless DNA, and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A.and other countries.

SQTP is a service mark of Microchip Technology Incorporated in the U.S.A.

The Adaptec logo, Frequency on Demand, Silicon Storage Technology, and Symmcom are registered trademarks ofMicrochip Technology Inc. in other countries.

GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of MicrochipTechnology Inc., in other countries.

All other trademarks mentioned herein are property of their respective companies.© 2020, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved.

ISBN: 978-1-5224-5656-8

Quality Management SystemFor information regarding Microchip’s Quality Management Systems, please visit http://www.microchip.com/quality.



http://www.microchip.com/quality

AMERICAS ASIA/PACIFIC ASIA/PACIFIC EUROPECorporate Office2355 West Chandler Blvd.Chandler, AZ 85224-6199Tel: 480-792-7200Fax: 480-792-7277Technical Support:http://www.microchip.com/supportWeb Address:http://www.microchip.comAtlantaDuluth, GATel: 678-957-9614Fax: 678-957-1455Austin, TXTel: 512-257-3370BostonWestborough, MATel: 774-760-0087Fax: 774-760-0088ChicagoItasca, ILTel: 630-285-0071Fax: 630-285-0075DallasAddison, TXTel: 972-818-7423Fax: 972-818-2924DetroitNovi, MITel: 248-848-4000Houston, TXTel: 281-894-5983IndianapolisNoblesville, INTel: 317-773-8323Fax: 317-773-5453Tel: 317-536-2380Los AngelesMission Viejo, CATel: 949-462-9523Fax: 949-462-9608Tel: 951-273-7800Raleigh, NCTel: 919-844-7510New York, NYTel: 631-435-6000San Jose, CATel: 408-735-9110Tel: 408-436-4270Canada - TorontoTel: 905-695-1980Fax: 905-695-2078

Australia - SydneyTel: 61-2-9868-6733China - BeijingTel: 86-10-8569-7000China - ChengduTel: 86-28-8665-5511China - ChongqingTel: 86-23-8980-9588China - DongguanTel: 86-769-8702-9880China - GuangzhouTel: 86-20-8755-8029China - HangzhouTel: 86-571-8792-8115China - Hong Kong SARTel: 852-2943-5100China - NanjingTel: 86-25-8473-2460China - QingdaoTel: 86-532-8502-7355China - ShanghaiTel: 86-21-3326-8000China - ShenyangTel: 86-24-2334-2829China - ShenzhenTel: 86-755-8864-2200China - SuzhouTel: 86-186-6233-1526China - WuhanTel: 86-27-5980-5300China - XianTel: 86-29-8833-7252China - XiamenTel: 86-592-2388138China - ZhuhaiTel: 86-756-3210040

India - BangaloreTel: 91-80-3090-4444India - New DelhiTel: 91-11-4160-8631India - PuneTel: 91-20-4121-0141Japan - OsakaTel: 81-6-6152-7160Japan - TokyoTel: 81-3-6880- 3770Korea - DaeguTel: 82-53-744-4301Korea - SeoulTel: 82-2-554-7200Malaysia - Kuala LumpurTel: 60-3-7651-7906Malaysia - PenangTel: 60-4-227-8870Philippines - ManilaTel: 63-2-634-9065SingaporeTel: 65-6334-8870Taiwan - Hsin ChuTel: 886-3-577-8366Taiwan - KaohsiungTel: 886-7-213-7830Taiwan - TaipeiTel: 886-2-2508-8600Thailand - BangkokTel: 66-2-694-1351Vietnam - Ho Chi MinhTel: 84-28-5448-2100

Austria - WelsTel: 43-7242-2244-39Fax: 43-7242-2244-393Denmark - CopenhagenTel: 45-4485-5910Fax: 45-4485-2829Finland - EspooTel: 358-9-4520-820France - ParisTel: 33-1-69-53-63-20Fax: 33-1-69-30-90-79Germany - GarchingTel: 49-8931-9700Germany - HaanTel: 49-2129-3766400Germany - HeilbronnTel: 49-7131-72400Germany - KarlsruheTel: 49-721-625370Germany - MunichTel: 49-89-627-144-0Fax: 49-89-627-144-44Germany - RosenheimTel: 49-8031-354-560Israel - Ra’ananaTel: 972-9-744-7705Italy - MilanTel: 39-0331-742611Fax: 39-0331-466781Italy - PadovaTel: 39-049-7625286Netherlands - DrunenTel: 31-416-690399Fax: 31-416-690340Norway - TrondheimTel: 47-72884388Poland - WarsawTel: 48-22-3325737Romania - BucharestTel: 40-21-407-87-50Spain - MadridTel: 34-91-708-08-90Fax: 34-91-708-08-91Sweden - GothenbergTel: 46-31-704-60-40Sweden - StockholmTel: 46-8-5090-4654UK - WokinghamTel: 44-118-921-5800Fax: 44-118-921-5820

Worldwide Sales and Service


http://www.microchip.com/supporthttp://www.microchip.com

PrefaceTable of Contents1. Introduction1.1. Features1.2. Kit Overview

2. Getting Started2.1. Quick Start2.2. Design Documentation and Relevant Links

3. Application User Guide4. Hardware User Guide4.1. On-Board Debugger Overview4.1.1. Debugger4.1.2. Virtual Serial Port (CDC)4.1.2.1. Overview4.1.2.2. Operating System Support4.1.2.3. Limitations4.1.2.4. Signaling4.1.2.5. Advanced Use

4.1.3. Mass Storage Device4.1.3.1. Mass Storage Device Implementation4.1.3.2. Configuration Words4.1.3.3. Special Commands

4.1.4. Data Gateway Interface (DGI)4.1.4.1. Debug GPIO4.1.4.2. Timestamping

4.2. On-Board Debugger Connections4.3. Power4.3.1. Power Source4.3.2. Battery Charger4.3.3. Hardware Modifications

4.4. Peripherals4.4.1. PIC24FJ128GA7054.4.2. mikroBUS™ Socket4.4.3. WINC1510 Wi-Fi Module4.4.4. ATECC608A4.4.5. Temperature Sensor4.4.6. Light Sensor4.4.7. LED4.4.8. Mechanical Buttons

5. Regulatory Approval5.1. United States5.2. Canada5.3. Taiwan5.4. List of Antenna Types

6. Hardware Revision History and Known Issues6.1. Identifying Product ID and Revision6.2. PIC-IoT WG6.2.1. Revision 36.2.2. Revision 2

6.3. PIC-IoT WA6.3.1. Revision 1

7. Document Revision History8. Appendix8.1. Schematic8.2. Assembly Drawing8.3. Mechanica

pic-iot wx hardware user guide · 2020. 3. 6. · pic-iot wx hardware user guide pic-iot wx...

Documents