Microchip Technology Curiosity Nano Series Manuel d'installation

PIC16F15276 Curiosity Nano Hardware User Guide

Preface

The PIC16F15276 Curiosity Nano evaluation kit is a hardware platform to evaluate microcontrollers in the

PIC16F152XX family. This board has the PIC16F15276 microcontroller (MCU) mounted.

Supported by MPLAB® X IDE, the board provides easy access to the features of the PIC16F15276 to explore how to

integrate the device into a custom design.

The Curiosity Nano series of evaluation boards include an on-board debugger. No external tools are necessary to

program and debug the PIC16F15276.

•MPLAB® X IDE - Software to discover, configure, develop, program, and debug Microchip microcontrollers.

•Code examples on GitHub - Get started with code examples.

•PIC16F15276 website - Find documentation, data sheets, sample, and purchase microcontrollers.

•PIC16F15276 Curiosity Nano website - Kit information, latest user guide, and design documentation.

Table of Contents

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

1. Introduction............................................................................................................................................. 3

1.1. Features....................................................................................................................................... 3

1.2. Board Overview............................................................................................................................3

2. Getting Started........................................................................................................................................ 4

2.1. Quick Start....................................................................................................................................4

2.2. Design Documentation and Relevant Links................................................................................. 4

3. Curiosity Nano.........................................................................................................................................6

3.1. On-Board Debugger Overview..................................................................................................... 6

3.2. Curiosity Nano Standard Pinout................................................................................................. 12

3.3. Power Supply............................................................................................................................. 13

3.4. Low-Power Measurement.......................................................................................................... 17

3.5. Programming External Microcontrollers..................................................................................... 18

3.6. Connecting External Debuggers................................................................................................ 21

4. Hardware User Guide........................................................................................................................... 23

4.1. Connectors.................................................................................................................................23

4.2. Peripherals................................................................................................................................. 24

5. Hardware Revision History and Known Issues..................................................................................... 26

5.1. Identifying Product ID and Revision........................................................................................... 26

5.2. Revision 1...................................................................................................................................26

6. Document Revision History...................................................................................................................27

7. Appendix............................................................................................................................................... 28

7.1. Schematic...................................................................................................................................28

7.2. Assembly Drawing......................................................................................................................30

7.3. Curiosity Nano Base for Click boards™...................................................................................... 31

7.4. Disconnecting the On-Board Debugger..................................................................................... 32

The Microchip Website.................................................................................................................................34

Product Change Notification Service............................................................................................................34

Customer Support........................................................................................................................................ 34

Microchip Devices Code Protection Feature................................................................................................ 34

Legal Notice................................................................................................................................................. 35

Trademarks.................................................................................................................................................. 35

Quality Management System....................................................................................................................... 36

Worldwide Sales and Service.......................................................................................................................37

1. Introduction

1.1 Features

• PIC16F15276 Microcontroller

• One Yellow User LED

• One Mechanical User Switch

• On-Board Debugger:

– Board identification in Microchip MPLAB® X IDE

– One green power and status LED

– Programming and debugging

– Virtual serial port (CDC)

– One debug GPIO channel (DGI GPIO)

• USB Powered

• Adjustable Target Voltage:

– MIC5353 LDO regulator controlled by the on-board debugger

– 1.8–5.1V output voltage (limited by USB input voltage)

– 500 mA maximum output current (limited by ambient temperature and output voltage)

1.2 Board Overview

The Microchip PIC16F15276 Curiosity Nano evaluation kit is a hardware platform to evaluate the PIC16F15276

microcontroller.

Figure 1-1. PIC16F15276 Curiosity Nano Board Overview

User

Switch

User LED

(LED0)

PIC16F15276

MCU

Debugger

Power/Status

LED

Micro-USB

Connector

Introduction

2. Getting Started

2.1 Quick Start

Steps to start exploring the PIC16F15276 Curiosity Nano board:

1. Download Microchip MPLAB® X IDE.

2. Download MPLAB® XC C Compiler.

3. Launch MPLAB® X IDE.

4. Optional: Use MPLAB® Code Configurator to generate drivers and examples.

5. Write the application code.

6. Connect a USB cable (Standard-A to Micro-B or Micro-AB) between the PC and the debug USB port on the

board.

2.1.1 Driver Installation

When the board connects to the computer for the first time, the operating system will perform a driver software

installation. The driver file supports both 32- and 64-bit versions of Microsoft® Windows® XP, Windows Vista®,

Windows® 7, Windows® 8, and Windows® 10. The drivers for the board are included with MPLAB® X IDE.

2.1.2 Kit Window

When the board is connected to a computer and powered on, the green status LED will be lit, the MPLAB® X IDE

will then auto-detect which boards are connected. The Kit Window in MPLAB® X IDE will present relevant information

like data sheets and board documentation. The PIC16F15276 device on the PIC16F15276 Curiosity Nano board is

programmed and debugged by the on-board debugger and, therefore, no external programmer or debugger tool is

required.

Tip: If closed, the Kit Window in MPLAB® X IDE can be reopened through the menu bar Window > Kit

Window.

2.1.3 MPLAB® X IDE Device Family Packs

Microchip MPLAB® X IDE requires specific information to support devices and tools. This information is contained

in versioned packs. For the PIC16F15276 Curiosity Nano board, MPLAB® X version 5.40 with device family pack

“PIC16F1xxxx_DFP” version 1.7.146 and tool pack “nEDBG_TP” version 1.8.318 or newer are required. For more

information on packs and how to upgrade them, refer to the MPLAB® X IDE User’s guide - Work with Device Packs.

Tip: The latest device family packs are available through Tools > Packs in MPLAB® X IDE or online at

Microchip MPLAB® X Packs Repository.

2.2 Design Documentation and Relevant Links

The following list contains links to the most relevant documents and software for the PIC16F15276 Curiosity Nano

board:

•MPLAB® X IDE - MPLAB X IDE is a software program that runs on a PC (Windows®, Mac OS®, Linux®)

to develop applications for Microchip microcontrollers and digital signal controllers. It is named an Integrated

Getting Started

Development Environment (IDE) because it provides a single integrated “environment” to develop code for

embedded microcontrollers.

•MPLAB® XC Compilers - MPLAB® XC8 C Compiler is available as a free, unrestricted-use download.

Microchips MPLAB® XC8 C Compiler is a comprehensive solution for your project’s software development

on Windows®, macOS® or Linux®. MPLAB® XC8 supports all 8-bit PIC® and AVR® microcontrollers (MCUs).

•MPLAB® Code Configurator - MPLAB Code Configurator (MCC) is a free software plug-in that provides a

graphical interface to configure peripherals and functions specific to your application.

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

•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 Data

Gateway Interface, as found on Curiosity Nano and Xplained Pro boards.

•Microchip PIC® and AVR® Examples - Microchip PIC and AVR Device Examples is a collection of examples

and labs that use Microchip development boards to showcase the use of PIC and AVR device peripherals.

•Microchip PIC® and AVR® Solutions - Microchip PIC and AVR Device Solutions contains complete

applications for use with Microchip development boards, ready to be adapted and extended.

•PIC16F15276 Curiosity Nano website - Kit information, latest user guide, and design documentation.

•PIC16F15276 Curiosity Nano on Microchip Direct - Purchase this kit on Microchip Direct.

Getting Started

3. Curiosity Nano

Curiosity Nano is an evaluation platform of small boards with low pin count microcontroller (MCU) boards with

on-board debuggers and access to most of the microcontrollers I/Os. The Curiosity Nano platform offers easy

integration with MPLAB® X IDE. All boards are identified in the IDE, and when connected a Kit Window is displayed

with links to key documentation, including relevant user guides, application notes, data sheets, and example code.

Everything is easy to find. The on-board debugger features a virtual serial port (CDC) for serial communication to a

host PC and a Data Gateway Interface (DGI) with debug GPIO pin(s).

3.1 On-Board Debugger Overview

PIC16F15276 Curiosity Nano contains an on-board debugger for programming and debugging. The on-board

debugger is a composite USB device consisting of several interfaces:

• A debugger that can program and debug the PIC16F15276 in MPLAB® X IDE

• A mass storage device that allows drag-and-drop programming of the PIC16F15276

• A virtual serial port (CDC) that is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the

PIC16F15276, and provides an easy way to communicate with the target application through terminal software

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

program flow

The on-board debugger controls a Power and Status LED (marked PS) on the PIC16F15276 Curiosity Nano board.

The table below shows how the LED is controlled in different operation modes.

Table 3-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-drop

programming 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.

3.1.1 Debugger

The on-board debugger on the PIC16F15276 Curiosity Nano board appears as a Human Interface Device (HID)

on the host computer’s USB subsystem. The debugger supports full-featured programming and debugging of the

PIC16F15276 using MPLAB® X IDE.

Curiosity Nano

Remember: Keep the debugger’s firmware up-to-date. Firmware upgrades automatically when using

MPLAB® X IDE.

3.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.

3.1.2.1 Overview

The 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

in both directions between the host computer and the target: All characters sent through the virtual serial port on the

host computer will be transmitted as UART on the debugger’s CDC TX pin, and UART characters captured on the

debugger’s CDC RX pin will be returned to the host computer through the virtual serial port.

Figure 3-1. CDC Connection

Target MCU

UART TX

UART RX

Debugger

USB CDC RX

CDC TX

Terminal

Software

Target

Receive

Target

Send

Terminal

Receive

Terminal

Send

Info: As shown in Figure 3-1, the debugger’s CDC TX pin is connected to a UART RX pin on the target

for receiving characters from the host computer. Similarly, the debugger’s CDC RX pin is connected to a

UART TX pin on the target for transmitting characters to the host computer.

3.1.2.2 Operating System Support

On Windows® machines, the CDC will enumerate as Curiosity Virtual COM Port and appear in the Ports section of

the Windows Device Manager. The COM port number can also be found there.

Info: On older Windows systems, the CDC requires a USB driver. This driver is included in installations of

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 of

that group to have permissions to access the CDC.

On Mac® machines, the CDC will enumerate and appear as /dev/tty.usbmodem#. Depending on which terminal

program is used, it will appear in the available list of modems as usbmodem#.

Curiosity Nano

Info: For all operating systems: Be sure to use a terminal emulator that supports DTR signaling. See

3.1.2.4 Signaling.

3.1.2.3 Limitations

Not 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 the

closest 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.

3.1.2.4 Signaling

During USB enumeration, the host OS will start both communication and data pipes of the CDC interface. At this

point, it is possible to set and read back the baud rate and other UART parameters of the CDC, but data sending and

receiving will not be enabled.

When a terminal connects to the host, it must assert the DTR signal. As this is a virtual control signal implemented

on the USB interface, it is not physically present on the board. Asserting the DTR signal from the host will indicate to

the on-board debugger that a CDC session is active. The debugger will then enable its level shifters (if available) and

start the CDC data send and receive mechanisms.

Deasserting DTR in debugger firmware version 1.20 or earlier has the following behavior:

• Debugger UART receiver is disabled, and no further data will be transferred to the host computer

• Debugger UART transmitter will continue to send data that is queued for sending, but no new data is accepted

from the host computer

• Level shifters (if available) are not disabled, and the debugger CDC TX line remains driven

Deasserting DTR in debugger firmware version 1.21 or later has the following behavior:

• Debugger UART receiver is disabled, so no further data will be transferred to the host computer

• Debugger UART transmitter will continue to send data that is queued for sending, but no new data is accepted

from the host computer

• Once the ongoing transmission is complete, level shifters (if available) are disabled, so the debugger CDC TX

line will become high-impedance

Remember: Set up the terminal emulator to assert the DTR signal. Without the signal, the on-board

debugger 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 the

host computer. Also, there are no external pull-up resistors on the CDC lines connecting the debugger and

the target, which means that during power-up, these lines are floating. To avoid any glitches resulting in

unpredictable behavior like framing errors, the target device may enable the internal pull-up resistor on the

pin connected to the debugger’s CDC TX pin.

Curiosity Nano

3.1.2.5 Advanced Use

CDC Override Mode

In normal operation, the on-board debugger is a true UART bridge between the host and the device. However, in

certain use cases, the on-board debugger can override the basic operating mode and use the CDC TX and RX pins

for other purposes.

Dropping a text file into the on-board debugger’s mass storage drive can be used to send characters out of the

debugger’s CDC TX pin. The filename and extension are trivial, but the text file must start with the characters:

CMD:SEND_UART=

Debugger firmware version 1.20 or earlier has the following limitations:

• 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,

the previously used baud rate still applies

Debugger firmware version 1.21 and later has the following limitations/features:

• The maximum message length may vary depending on the MSC/SCSI layer timeouts on the host computer

and/or operating system. A single SCSI frame of 512 bytes (498 characters of payload) is ensured, and files of

up to 4 KB will work on most systems. The transfer will complete on the first NULL character encountered in the

file.

• The baud rate used is always 9600 bps for the default command:

CMD:SEND_UART=

• Do not use the CDC override mode simultaneously with data transfer over the CDC/terminal. If a CDC terminal

session is active at the time a file is received via CDC Override mode, it will be suspended for the duration of the

operation and resumed once complete.

• Additional commands are supported with explicit baud rates:

CMD:SEND_9600=

CMD:SEND_115200=

CMD:SEND_460800=

USB-Level Framing Considerations

Sending data from the host to the CDC can be done byte-wise or in blocks, which will be chunked into 64-byte USB

frames. Each such frame will be queued up for sending to the debugger’s CDC TX pin. Transferring a small amount

of data per frame can be inefficient, particularly at low baud rates, as the on-board debugger buffers frames and not

bytes. A maximum of four 64-byte frames can be active at any time. The on-board debugger will throttle the incoming

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 into

64-byte frames, which are sent to the USB queue for transmission to the host when they are full. Incomplete frames

are also pushed to the USB queue at approximately 100 ms intervals, triggered by USB start-of-frame tokens. Up to

eight 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 data frame will be lost.

To prevent this occurrence, the user must ensure that the CDC data pipe is being read continuously, or the incoming

data rate must be reduced.

3.1.3 Mass Storage Device

The on-board debugger includes a simple Mass Storage Device implementation, which is accessible for read/write

operations via the host operating system to which it is connected.

It provides:

Curiosity Nano

• 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

3.1.3.1 Mass Storage Device Implementation

The 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 Device

that can be found in the disk drives section of the device manager. The CURIOSITY drive appears in the file manager

and claims the next available drive letter in the system.

The CURIOSITY drive contains approximately one MB of free space, and this does not reflect the size of the

target device’s Flash in any way. When programming an Intel® HEX file, the binary data are encoded in ASCII with

metadata providing a large overhead, so 1 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 in

the disk directory listing. This is merely the operating system’s view of the directory, which has not been updated in

reality. It is not possible to read out the file contents. Removing and replugging the board will return the file system to

its original state, but the target will still contain the application that has previously been 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 and

linking to further information:

•AUTORUN.ICO – icon file for the Microchip logo

•AUTORUN.INF – system file required for Windows Explorer to show the icon file

•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

•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 by

the OS and, therefore, do not reflect the correct status.

3.1.3.2 Configuration Words

Configuration Words (PIC® MCU Targets)

Configuration Word settings included in the project being programmed after program Flash is programmed. The

debugger will not mask out any bits in the Configuration Words when writing them, but since it uses Low-Voltage

Programming 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 before

programming) and restore the device to its default settings.

3.1.3.3 Special Commands

Several utility commands are supported by copying text files to the mass storage disk. The filename or extension is

irrelevant – the command handler reacts to content only.

Table 3-2. Special File Commands

Command Content Description

CMD:ERASE Executes a chip erase of the target

Curiosity Nano

Ce manuel convient aux modèles suivants

Table des matières

Autres manuels Microchip Technology Carte mère

Microchip Technology

Microchip Technology MCP251XFD CAN FD Manuel utilisateur

Microchip Technology

Microchip Technology MCP1642B Manuel utilisateur

Microchip Technology

Microchip Technology DM160223 Manuel utilisateur

Microchip Technology

Microchip Technology ATtiny416 Xplained Nano Manuel utilisateur

Microchip Technology

Microchip Technology SOT89-3 Manuel utilisateur

Microchip Technology

Microchip Technology MCP7382X Manuel utilisateur

Microchip Technology

Microchip Technology DIGITAL POWER Manuel utilisateur

Microchip Technology

Microchip Technology ATBTLC1000 Series Manuel utilisateur

Microchip Technology

Microchip Technology ATtiny817 Xplained Pro Manuel utilisateur

Microchip Technology

Microchip Technology UCS1003-1 Manuel utilisateur

Microchip Technology

Microchip Technology Microsemi Silicon Sculptor 4 Manuel technique

Microchip Technology

Microchip Technology SOT23-6 Manuel utilisateur

Microchip Technology

Microchip Technology MCP1012 Manuel utilisateur

Microchip Technology

Microchip Technology PL485-EK Manuel utilisateur

Microchip Technology

Microchip Technology EVK-UTC2000 Manuel utilisateur

Microchip Technology

Microchip Technology EVB-LAN9252-3PORT Manuel utilisateur

Microchip Technology

Microchip Technology PIC32MK Manuel utilisateur

Microchip Technology

Microchip Technology SAMA7G54-EK Manuel utilisateur

Microchip Technology

Microchip Technology MCP2150 Manuel utilisateur

Microchip Technology

Microchip Technology PIC32MX470 Manuel utilisateur

Microchip Technology

Microchip Technology RN-52-EK Manuel utilisateur

Microchip Technology

Microchip Technology PIC16F15244 Curiosity Nano Manuel d'installation

Microchip Technology

Microchip Technology DM160232 Manuel utilisateur

Microchip Technology

Microchip Technology LAN9360 Manuel utilisateur

Manuels Carte mère populaires d'autres marques

DFI

DFI SD170 Manuel utilisateur

ASROCK

ASROCK ROMED8-2T Manuel utilisateur

Asus

Asus P2L97A Manuel utilisateur

Winmate

Winmate IC70 Manuel utilisateur

Asus

Asus MES-B Manuel utilisateur

Grantech

Grantech SYS8F377VGGA-3OMN Manuel utilisateur

Telit Wireless Solutions

Telit Wireless Solutions SL869-3DR Manuel utilisateur

Gigabyte

Gigabyte GA-9IVDT Manuel utilisateur

Texas Instruments

Texas Instruments ADS8372EVM Manuel utilisateur

Commell

Commell MS-C73 Manuel utilisateur

IBT Technologies

IBT Technologies MB860 Manuel utilisateur

Nvidia

Nvidia TEGRA DG-04927-001_V01 Manuel utilisateur

Biostar

Biostar M7VIT Bravo Instructions d'utilisation et d'installation

Intel

Intel D33217CK Manuel utilisateur

Asus

Asus F1A55-M LX PLUS R2.0 Manuel utilisateur

EPC

EPC EPC9147C Manuel utilisateur

Asus

Asus EX-B760M-V5 D4 Manuel utilisateur

EPOX

EPOX MU-8KHA0010 Manuel utilisateur