PIC16F18076 Curiosity Nano
PIC16F18076 Curiosity Nano Hardware User Guide
Preface
The PIC16F18076 Curiosity Nano evaluation kit is a hardware platform to evaluate microcontrollers in the
PIC16F18076 family. This board has the PIC16F18076 microcontroller (MCU) mounted.
Supported by MPLAB® X IDE, the board provides easy access to the features of the PIC16F18076 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 PIC16F18076.
•
•
•
•
MPLAB® X IDE - Software to discover, configure, develop, program, and debug Microchip microcontrollers.
Code examples on GitHub - Get started with code examples.
PIC16F18076 website - Find documentation, data sheets, sample, and purchase microcontrollers.
PIC16F18076 Curiosity Nano website - Kit information, latest user guide and design documentation.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 1
PIC16F18076 Curiosity Nano
Table of Contents
Preface........................................................................................................................................................... 1
1.
Introduction............................................................................................................................................. 4
1.1.
1.2.
2.
Getting Started........................................................................................................................................ 5
2.1.
2.2.
2.3.
3.
Curiosity Nano Quick Start MPLAB® Xpress............................................................................... 5
Quick Start....................................................................................................................................5
2.2.1.
Driver Installation........................................................................................................... 5
2.2.2.
Kit Window.....................................................................................................................5
2.2.3.
MPLAB® X IDE Device Family Packs............................................................................6
Design Documentation and Relevant Links................................................................................. 6
Curiosity Nano.........................................................................................................................................7
3.1.
3.2.
3.3.
3.4.
3.5.
3.6.
4.
Features....................................................................................................................................... 4
Board Overview............................................................................................................................4
On-Board Debugger Overview..................................................................................................... 7
3.1.1.
Debugger....................................................................................................................... 7
3.1.2.
Virtual Serial Port (CDC)................................................................................................8
3.1.2.1.
Overview..................................................................................................... 8
3.1.2.2.
Operating System Support.......................................................................... 8
3.1.2.3.
Limitations................................................................................................... 9
3.1.2.4.
Signaling......................................................................................................9
3.1.2.5.
Advanced Use........................................................................................... 10
3.1.3.
Mass Storage Device...................................................................................................11
3.1.3.1.
Mass Storage Device Implementation.......................................................11
3.1.3.2.
Configuration Words..................................................................................12
3.1.3.3.
Special Commands................................................................................... 12
3.1.4.
Data Gateway Interface (DGI)..................................................................................... 13
3.1.4.1.
Debug GPIO..............................................................................................13
3.1.4.2.
Timestamping............................................................................................ 13
Curiosity Nano Standard Pinout................................................................................................. 13
Power Supply............................................................................................................................. 14
3.3.1.
Target Regulator.......................................................................................................... 15
3.3.2.
External Supply............................................................................................................16
3.3.3.
VBUS Output Pin......................................................................................................... 17
3.3.4.
Power Supply Exceptions............................................................................................ 17
Low-Power Measurement.......................................................................................................... 18
Programming External Microcontrollers..................................................................................... 19
3.5.1.
Supported Devices...................................................................................................... 19
3.5.2.
Software Configuration................................................................................................ 19
3.5.3.
Hardware Modifications............................................................................................... 20
3.5.4.
Connecting to External Microcontrollers...................................................................... 21
Connecting External Debuggers................................................................................................ 22
Hardware Description............................................................................................................................24
4.1.
Connectors................................................................................................................................. 24
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 2
PIC16F18076 Curiosity Nano
4.2.
5.
4.1.1.
PIC16F18076 Curiosity Nano Pinout...........................................................................24
4.1.2.
Using Pin-Headers.......................................................................................................25
Peripherals................................................................................................................................. 26
4.2.1.
LED..............................................................................................................................26
4.2.2.
Mechanical Switch....................................................................................................... 26
4.2.3.
Crystal..........................................................................................................................26
4.2.4.
On-Board Debugger Implementation...........................................................................27
4.2.4.1.
On-Board Debugger Connections............................................................. 27
Hardware Revision History and Known Issues..................................................................................... 28
5.1.
5.2.
Identifying Product ID and Revision........................................................................................... 28
Revision 3...................................................................................................................................28
6.
Document Revision History...................................................................................................................29
7.
Appendix............................................................................................................................................... 30
7.1.
7.2.
7.3.
7.4.
Schematic.................................................................................................................................0
Assembly Drawing......................................................................................................................33
™
Curiosity Nano Base for Click boards ...................................................................................... 35
Disconnecting the On-Board Debugger..................................................................................... 36
Microchip Information................................................................................................................................... 38
The Microchip Website..........................................................................................................................38
Product Change Notification Service.................................................................................................... 38
Customer Support................................................................................................................................. 38
Microchip Devices Code Protection Feature.........................................................................................38
Legal Notice.......................................................................................................................................... 38
Trademarks........................................................................................................................................... 39
Quality Management System................................................................................................................ 40
Worldwide Sales and Service................................................................................................................41
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 3
PIC16F18076 Curiosity Nano
Introduction
1.
Introduction
1.1
Features
•
•
•
•
•
•
•
1.2
PIC16F18076 Microcontroller
One Yellow User LED
One Mechanical User Switch
Footprint for 32.768 kHz Crystal
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)
Board Overview
The Microchip PIC16F18076 Curiosity Nano evaluation kit is a hardware platform to evaluate the PIC16F18076
microcontroller.
Figure 1-1. PIC16F18076 Curiosity Nano Board Overview
Micro-USB
Connector
32.768 kHz
Debugger
Power/
Status LED
© 2022 Microchip Technology Inc.
and its subsidiaries
Crystal Footprint
PIC16F18076
MCU
User Guide
User LED
(LED0)
User
Switch
DS50003399A-page 4
PIC16F18076 Curiosity Nano
Getting Started
2.
Getting Started
2.1
Curiosity Nano Quick Start MPLAB® Xpress
MPLAB Xpress Cloud-Based IDE is an online development environment that contains the most popular features of
our award-winning MPLAB X IDE.
Steps to start exploring the Curiosity Nano platform with MPLAB Xpress:
1. Go to mplabxpress.microchip.com to open MPLAB Xpress.
2. Create a new stand-alone project for PIC16F18076.
3. Use the MPLAB Xpress Code Configurator, or write your code.
4. Compile and download the application HEX file (Both can be achieved by "Run Project")
5. Connect a USB cable (Standard-A to Micro-B or Micro-AB) between the PC and the debug USB port on the
kit.
6. Copy the application HEX file into the CURIOSITY mass storage drive to program the application into the
PIC16F18076.
To use advanced debug features of the Curiosity Nano kit, package the MPLAB Xpress project for MPLAB X
IDE, and follow the quick start guide in the next section.
2.2
Quick Start
Steps to start exploring the PIC16F18076 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\Develop 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.
7. Program your application onto the device.
The PIC16F18076 device on the PIC16F18076 Curiosity Nano board is programmed and debugged by the
on-board debugger. Therefore, no external programmer or debugger tool is required.
2.2.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.2.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
auto-detect which boards are connected. The Kit Window in MPLAB® X IDE will present relevant information like data
sheets and board documentation.
Tip: If closed, reopen the Kit Window in MPLAB® X IDE through the menu bar Window > Kit Window.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 5
PIC16F18076 Curiosity Nano
Getting Started
2.2.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 PIC16F18076 Curiosity Nano board, MPLAB® X version 6.0 or later with device family
pack “PIC16F1xxxx_DFP” version 1.14.187 or later and tool pack “nEDBG_TP” version 1.10.488 or later or newer is
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.3
Design Documentation and Relevant Links
The following list contains links to the most relevant documents and software for the PIC16F18076 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
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 the project’s software development on
Windows®, macOS® or Linux®. MPLAB® XC8 supports all 8-bit PIC® and AVR® microcontrollers (MCUs).
MPLAB® Xpress Cloud-Based IDE - MPLAB Xpress Cloud-Based IDE is an online development environment
containing the most popular features of our award-winning MPLAB X IDE. This simplified and distilled
application is a faithful reproduction of our desktop-based program, allowing users an easy transition between
the two environments.
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 one 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 the on-board debugger’s Data
Gateway Interface, as found on Curiosity Nano and Xplained Pro boards.
MPLAB Discover - MPLAB Discover is a tool to help you find Microchip example projects and collateral for
Microchip devices.
PIC16F18076 Curiosity Nano website - Kit information, latest user guide and design documentation.
PIC16F18076 Curiosity Nano on Microchip Direct - Purchase this kit on Microchip Direct.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 6
PIC16F18076 Curiosity Nano
Curiosity Nano
3.
Curiosity Nano
Curiosity Nano is an evaluation platform of small boards with low pin count microcontroller (MCU) boards with onboard 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. When connected, a Kit Window appears 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
PIC16F18076 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 PIC16F18076 in MPLAB® X IDE
• A mass storage device that allows drag-and-drop programming of the PIC16F18076
• A virtual serial port (CDC) that is connected to a Universal Asynchronous Receiver/Transmitter (UART) on the
PIC16F18076 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 PIC16F18076 Curiosity Nano board.
The table below shows how the different operation modes control the LED.
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 about 5 Hz.
3.1.1
Debugger
The on-board debugger on the PIC16F18076 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
PIC16F18076 using MPLAB® X IDE.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 7
PIC16F18076 Curiosity Nano
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 with a standard Communications Device Class (CDC)
interface, which appears on the host as a virtual serial port. Use the CDC to stream arbitrary data between the host
computer and the target in both directions: All characters sent through the virtual serial port on the host computer will
be transmitted as UART on the debugger’s CDC TX pin. The 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
PC
Terminal
Software
Terminal
Send
Debugger
USB
Terminal
Receive
CDC TX
CDC RX
Target
Receive
Target
Send
Target MCU
UART RX
UART TX
Info: The debugger’s CDC TX pin is connected to a UART RX pin on the target for receiving characters
from the host computer, as shown in the figure above. 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. The MPLAB® X IDE installation
Includes this driver.
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 permission to access the CDC.
On Mac® machines, the CDC will enumerate and appear as /dev/tty.usbmodem#. Depending on the terminal
program used, it will appear in the available list of modems as usbmodem#.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 8
PIC16F18076 Curiosity Nano
Curiosity Nano
Info: For all operating systems, 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:
•
•
•
•
•
3.1.2.4
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.
Signaling
During USB enumeration, the host OS will start both the 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.
The terminal must assert the DTR signal when it connects to the host. 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 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 queued data ready for transfer, 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, and no further data will be transferred to the host computer
• Debugger UART transmitter will continue to send queued data ready for transfer, but no new data is accepted
from the host computer
• Once the ongoing transmission is complete, level shifters (if available) are disabled, and 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 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 the lines are floating during power-up.The target device may enable the
internal pull-up resistor on the pin connected to the debugger’s CDC TX pin to avoid glitches resulting in
unpredictable behavior like framing errors.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 9
PIC16F18076 Curiosity Nano
Curiosity Nano
3.1.2.5
Advanced Use
CDC Override Mode
In ordinary 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 will 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 configured, the
previously used baud rate still applies
Debugger firmware version 1.21 and later has the following limitations/features:
• The maximum message length will 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 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 when receiving a file via the 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, chunked into 64-byte USB frames. Each
such frame will be queued for transfer to the debugger’s CDC TX pin. Sending a small amount of data per frame can
be inefficient, particularly at low baud rates, as the on-board debugger buffers frames but 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.
An overrun will occur if the host (or the software running on it) fails to receive data fast enough. When this happens,
the last-filled buffer frame recycles instead of being sent to the USB queue, and a complete data frame will be lost. To
prevent this occurrence, the user will ensure that the CDC data pipe is continuously read, or the incoming data rate
will be reduced.
Sending Break Characters
The host can send a UART break character to the device using the CDC. This can be useful for resetting a receiver
state-machine or signalling an exception condition from the host to the application running on the device.
A break character is defined as a sequence of at least 11 zero bits transmitted from the host to the device.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 10
PIC16F18076 Curiosity Nano
Curiosity Nano
Not all UART receivers have support for detecting a break, but a correctly-formed break character usually triggers a
framing error on the receiver.
Sending a break character using the debugger's CDC has the following limitations:
• Sending a break must NOT be done at the same time as using the CDC Override mode (drag-and-drop). Both
these functions are temporary states, so they must be used independently.
• Sending a break will cause data currently being sent to be lost. Be sure to wait a sufficient amount of time to
allow all characters in the transmission buffer to be sent (see above section) before sending the break. This is
also in line with expected break character usage: For example, reset a receiver state-machine after a timeout
occurs waiting for data to be returned to the host.
• The CDC specification allows for debugger-timed breaks of up to 65534ms in duration to be requested. For
simplicity, the debugger will limit the break duration to a maximum of 11 bit-durations at its minimum supported
baud rate.
• The CDC specification allows for indefinite host-timed breaks. It is the responsibility of the terminal application/
user to release the break state in this case.
Note: Sending break characters is available in debugger firmware version 1.24 and later.
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:
• 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 having 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
found in the disk drives section of the device manager. The CURIOSITY drive appears in the file manager and claims
the following available drive letter in the system.
The CURIOSITY drive contains approximately one MB of free space and does not reflect the target device’s Flash
size. 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. The filename may appear in the disk directory listing when
programming a file to the target, which is merely the operating system’s view of the directory that, in reality, has not
been updated. 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 previously programmed application.
Copy a text file starting with “CMD:ERASE” onto the disk to erase the target device.
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
•
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 11
PIC16F18076 Curiosity Nano
Curiosity Nano
Info: STATUS.TXT is dynamically updated by the on-board debugger. The contents may be cached by the
OS and, therefore, not reflecting 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 can't 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
CMD:SEND_UART=
Sends a string of characters to the CDC UART. See “CDC
Override Mode.”
CMD:SEND_9600=
CMD:SEND_115200=
CMD:SEND_460800=
Sends a string of characters to the CDC UART at the specified
baud rate. Note that only the baud rates explicitly specified here
are supported! See “CDC Override Mode”. (Debugger firmware
v1.21 or newer.)
CMD:RESET
Resets the target device by entering Programming mode and
exiting Programming mode immediately afterward. The exact
timing can vary according to the programming interface of the
target device. (Debugger firmware v1.16 or newer.)
CMD:POWERTOGGLE
Powers down the target and restores it after a 100 ms delay.
If external power is provided, this has no effect. (Debugger
firmware v1.16 or newer.)
CMD:0V
Powers down the target device by disabling the target supply
regulator. If external power is provided, this has no effect.
(Debugger firmware v1.16 or newer.)
CMD:1V8
Sets the target voltage to 1.8V. If external power is provided,
this has no effect. (Debugger firmware v1.21 or newer.)
CMD:3V3
Sets the target voltage to 3.3V. If external power is provided,
this has no effect. (Debugger firmware v1.16 or newer.)
CMD:5V0
Sets the target voltage to 5.0V. If external power is provided,
this has no effect. (Debugger firmware v1.16 or newer.)
Info: The content sent to the mass storage emulated disk triggers the commands listed here and provides
no feedback in the case of either success or failure.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 12
PIC16F18076 Curiosity Nano
Curiosity Nano
3.1.4
Data Gateway Interface (DGI)
Data Gateway Interface (DGI) is a USB interface for transporting raw and timestamped data between on-board
debuggers and host computer-based visualization tools. MPLAB Data Visualizer is used on the host computer to
display any debug GPIO data. It is available as a plug-in for MPLAB® X IDE or a stand-alone application that can be
used in parallel with MPLAB® X IDE.
Although DGI encompasses several physical data interfaces, the PIC16F18076 Curiosity Nano implementation
includes logic analyzer channels:
• One debug GPIO channel (also known as DGI GPIO)
3.1.4.1
Debug GPIO
Debug GPIO channels are timestamped digital signal lines connecting the target application to a host computer
visualization application. They are typically used to plot low-frequency events on a time axis – for example, when
given Application state transitions occur.
The figure below shows the monitoring of the Digital state of a mechanical switch connected to a debug GPIO in
MPLAB Data Visualizer.
Figure 3-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 the
DGI Timestamp module.
Important: Although signal bursts of higher frequency can be captured, the frequency range of signals
for which debug GPIO can be used is up to about 2 kHz. Attempting to capture signals above this
frequency will result in data saturation and overflow, which may cause the DGI session to be aborted.
3.1.4.2
Timestamping
DGI sources are timestamped when they are captured by the debugger. The timestamp counter implemented in the
Curiosity Nano debugger increments at a 2 MHz frequency, providing a timestamp resolution of a half microsecond.
3.2
Curiosity Nano Standard Pinout
The 12 edge connections closest to the USB connector on Curiosity Nano boards have a standardized pinout. The
program/debug pins have different functions depending on the target programming interface, as shown in the table
and figure below.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 13
PIC16F18076 Curiosity Nano
Curiosity Nano
Table 3-3. Curiosity Nano Standard Pinout
Debugger Signal
Target MCU
Description
ID
—
ID line for extensions
CDC TX
UART RX
USB CDC TX line
CDC RX
UART TX
USB CDC RX line
DBG0
ICSPDAT
Debug data line
DBG1
ICSPCLK
Debug clock line
DBG2
GPIO0
debug GPIO0
DBG3
MCLR
Reset line
NC
—
No connect
VBUS
—
VBUS voltage for external use
VOFF
—
Voltage Off input. Disables the target regulator and
target voltage when pulled low.
VTG
—
Target voltage
GND
—
Common ground
Figure 3-3. Curiosity Nano Standard Pinout
USB
NC
PS LED
ID
CDC RX
VOFF
DEBUGGER
DBG3
CDC TX
DBG0
DBG1
GND
DBG2
3.3
VBUS
CURIOSITY NANO
VTG
Power Supply
The USB port powers the board. It contains two LDO regulators, one to generate 3.3V for the on-board debugger and
an adjustable LDO regulator for the target PIC16F18076 microcontroller and its peripherals. The voltage from a USB
connector can vary between 4.4V and 5.25V (according to the USB specification) and will limit the maximum voltage
supplied to the target. The figure below shows the entire power supply system on PIC16F18076 Curiosity Nano.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 14
PIC16F18076 Curiosity Nano
Curiosity Nano
Figure 3-4. Power Supply Block Diagram
VTG
VREG
Target
Regulator
VLVL
Measure
USB
On/Off
Adjust
VUSB
Power consumer
Power converter
Power protection
DEBUGGER
PTC
Fuse
Regulator
P3V3
Power
Supply
strap
Target
Power
strap
On/Off
DEBUGGER
I/O
Target
MCU
Level
shifter
I/O
GPIO
straps
I/O
Power source
Cut strap
3.3.1
VBUS
#VOFF
ID system
Target Regulator
The target voltage regulator is a MIC5353 variable output LDO. The on-board debugger can adjust the voltage output
supplied to the board target section by manipulating the MIC5353’s feedback voltage. The hardware implementation
is limited to an approximate voltage range from 1.7V to 5.1V. Additional output voltage limits are configured in
the debugger firmware to ensure that the output voltage never exceeds the hardware limits of the PIC16F18076
microcontroller. The voltage limits configured in the on-board debugger on PIC16F18076 Curiosity Nano are 1.8–
5.5V.
Info: The factory default target voltage is 3.3V. It can be changed through the MPLAB® X IDE project
properties. Any change to the target voltage is persistent, even after a power toggle. The resolution is less
than 5 mV but may be limited to 10 mV by the adjustment program.
Info: The voltage settings setup in MPLAB® X IDE is not applied immediately to the board. The new
voltage setting is applied to the board when accessing the debugger, like pushing the Refresh Debug Tool
Status button in the project dashboard tab or programming/reading program memory.
Info: There is an easy option to adjust the target voltage with a drag-and-drop command text file to the
board, which supports a set of common target voltages. See section 3.1.3.3. Special Commands for
further details.
MIC5353 supports a maximum current load of 500 mA. It is an LDO regulator in a small package, placed on a
small printed circuit board (PCB), and the thermal shutdown condition can be reached at lower loads than 500 mA.
The maximum current load depends on the input voltage, the selected output voltage, and the ambient temperature.
The figure below shows the safe operating area for the regulator, with an input voltage of 5.1V and an ambient
temperature of 23°C.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 15
PIC16F18076 Curiosity Nano
Curiosity Nano
Figure 3-5. Target Regulator Safe Operation Area
The voltage output of the target regulator is continuously monitored (measured) by the on-board debugger. If it is
more than 100 mV over/under the set device voltage, an error condition will be flagged, and the target voltage
regulator will be switched off, detecting and handling any short-circuit conditions. It will also detect and handle if an
external voltage, which causes VCC_TARGET to move outside the voltage setting monitoring window of ±100 mV, is
suddenly applied to the VTG pin without setting the VOFF pin low.
Info: The on-board debugger has a monitoring window of VCC_TARGET±100 mV. The on-board debugger
status LED will blink rapidly if the external voltage is under this limit. The on-board debugger status LED
will continue to shine if the external voltage is above this limit. When removing the external voltage, the
status LED will start blinking rapidly until the on-board debugger detects the new situation and turns the
target voltage regulator back on.
3.3.2
External Supply
Instead of the on-board target regulator, an external voltage can power the PIC16F18076 Curiosity Nano. When
shorting the Voltage Off (VOFF) pin to the ground (GND) pin, the on-board debugger firmware disables the target
regulator, and it is safe to apply an external voltage to the VTG pin.
It is also safe to apply an external voltage to the VTG pin when no USB cable is plugged into the DEBUG connector
on the board.
The VOFF pin can be tied low/let go at any time, which will be detected by a pin-change interrupt to the on-board
debugger, which controls the target voltage regulator accordingly.
WARNING
WARNING
WARNING
Applying an external voltage to the VTG pin without shorting VOFF to GND may cause permanent damage
to the board.
Do not apply any voltage to the VOFF pin. Let the pin float to enable the power supply.
The absolute maximum external voltage is 5.5V for the on-board level shifters, and the standard operating
condition of the PIC16F18076 is 1.8–5.5V. Applying a higher voltage may cause permanent damage to the
board.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 16
PIC16F18076 Curiosity Nano
Curiosity Nano
Info: If an external voltage is applied without pulling the VOFF pin low and an external supply pulls the
voltage lower than the monitoring window’s lower limit (target voltage setting – 100 mV), the on-board
debugger status LED will blink rapidly and shut the on-board regulator off. If an external voltage is
suddenly removed when the VOFF pin is not pulled low, the status LED will start to blink rapidly until the
on-board debugger detects the new situation and switches the target voltage regulator back on.
Programming, debugging, and data streaming are still possible with an external power supply. The USB cable will
power the debugger and signal level shifters. Both regulators, the debugger, and the level shifters are powered down
when the USB cable is removed.
Info: In addition to the power consumed by the PIC16F18076 and its peripherals, approximately 100 µA
will be drawn from any external power source to power the on-board level shifters and voltage monitor
circuitry when a USB cable is plugged into the DEBUG connector on the board. When a USB cable is not
plugged in, some current is used to supply the level shifter’s voltage pins, which have a worst-case current
consumption of approximately 5 µA. Typical values may be as low as 100 nA.
3.3.3
VBUS Output Pin
PIC16F18076 Curiosity Nano has a VBUS output pin that can be used to power external components that need a 5V
supply. The VBUS output pin has a PTC fuse to protect the USB against short circuits. A side effect of the PTC fuse
is a voltage drop on the VBUS output with higher current loads. The chart below shows the voltage versus the current
load of the VBUS output.
Figure 3-6. VBUS Output Voltage vs. Current
3.3.4
Power Supply Exceptions
This chapter sums up most exceptions that can occur with the power supply.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 17
PIC16F18076 Curiosity Nano
Curiosity Nano
Target Voltage Shuts Down
Not reaching the target voltage setting can happen if the target section draws too much current at a given voltage and
cause the thermal shutdown safety feature of the MIC5353 regulator to kick in. To avoid this, reduce the current load
of the target section.
Target Voltage Setting is Not Reached
The USB input voltage (4.4-5.25V) limits the maximum output voltage, the voltage drop over the MIC5353 regulator
at a given voltage setting, and current consumption. If a higher output voltage is needed, use a USB power source
that can provide a higher input voltage or use an external voltage supply on the VTG pin.
Target Voltage is Different From Setting
An externally applied voltage to the VTG pin without setting the VOFF pin low can cause this. If the target voltage
differs more than 100 mV over/under the voltage setting, the on-board debugger will detect it, and the internal voltage
regulator will shut down. To fix this issue, remove the applied voltage from the VTG pin, and the on-board debugger
will enable the on-board voltage regulator when the new condition is detected. Note that the PS LED will blink rapidly
if the target voltage is below 100 mV of the setting but will ordinarily turn on when higher than 100 mV above the
setting.
No, Or Very Low Target Voltage, and PS LED is Blinking Rapidly
A full or partial short circuit can cause this and is a particular case of the issue mentioned above. Remove it, and the
on-board debugger will re-enable the on-board target voltage regulator.
No Target Voltage and PS LED is Lit 1
This occurs if the target voltage is set to 0.0V. To fix this, set the target voltage to a value within the specified voltage
range for the target device.
No Target Voltage and PS LED is Lit 2
This can be the issue if power jumper J100 and/or J101 is cut, and the target voltage regulator is set to a value within
the specified voltage range for the target device. To fix this, solder a wire/bridge between the pads for J100/J101, or
add a jumper on J101 if a pin-header is mounted.
VBUS Output Voltage is Low or Not Present
If the VBUS output voltage is low or missing, the reason is probably a high-current drain on VBUS, and the protection
fuse (PTC) will reduce the current or cut off completely. Reduce the current consumption on the VBUS pin to fix this
issue.
3.4
Low-Power Measurement
Power to the PIC16F18076 is connected from the on-board power supply and VTG pin through a 100 mil pin-header
marked with “POWER” in silkscreen (J101). To measure the power consumption of the PIC16F18076 and other
peripherals connected to the board, cut the Target Power strap and connect an ammeter over the strap.
To measure the lowest possible power consumption, follow these steps:
1. Cut the POWER strap with a sharp tool.
2. Solder a 1x2 100 mil pin-header in the footprint.
3. Connect an ammeter to the pin header.
4. Write firmware that:
a. Tri-states any I/O connected to the on-board debugger.
b. Sets the microcontroller in its lowest Power sleep mode.
5. Program the firmware into the PIC16F18076.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 18
PIC16F18076 Curiosity Nano
Curiosity Nano
Figure 3-7. Target Power Strap
Target Power strap (top side)
Tip: A 100-mil pin-header can be soldered into the Target Power strap (J101) footprint for a simple
connection of an ammeter. Place a jumper cap on the pin-header once the ammeter is no longer needed.
Info: The on-board level shifters will draw a small amount of current even when not used. Maximum
2 µA can be drawn from each I/O pin connected to a level shifter, the worst case maximum for the 5
on-board level shifters is therefore 10 µA. Keep any I/O pin connected to a level shifter in tri-state to
prevent leakage. All I/Os connected to the on-board debugger are listed in 4.2.4.1. On-Board Debugger
Connections. The on-board level shifters can be completely disconnected to prevent leakage, as described
in 7.4. Disconnecting the On-Board Debugger.
3.5
Programming External Microcontrollers
The on-board debugger on PIC16F18076 Curiosity Nano can be used to program and debug microcontrollers on
external hardware.
3.5.1
Supported Devices
All external AVR microcontrollers with the UPDI interface can be programmed and debugged with the on-board
debugger with Microchip Studio.
External SAM microcontrollers having a Curiosity Nano Board can be programmed and debugged with the on-board
debugger with Microchip Studio.
PIC16F18076 Curiosity Nano can program and debug external PIC16F18076 microcontrollers with MPLAB X IDE.
3.5.2
Software Configuration
No software configuration is required to program and debug the same device mounted on the board.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 19
PIC16F18076 Curiosity Nano
Curiosity Nano
To program and debug a different microcontroller than the one mounted on the board, configure Microchip Studio to
allow an independent selection of devices and programming interfaces.
1.
2.
3.
Navigate to Tools > Options through the menu system at the top of the application.
Select the Tools > Tool settings category in the options window.
Set the Hide unsupported devices option to False.
Figure 3-8. Hide Unsupported Devices
Info: Microchip Studio allows any microcontroller and interface to be selected when the Hide
unsupported devices setting is set to False - also microcontrollers and interfaces not supported by
the on-board debugger.
3.5.3
Hardware Modifications
The on-board debugger is connected to the PIC16F18076 by default. Remove these connections before any external
microcontroller can be programmed or debugged. Cut the GPIO straps shown in the figure below with a sharp tool to
disconnect the PIC16F18076 from the on-board debugger.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 20
PIC16F18076 Curiosity Nano
Curiosity Nano
Figure 3-9. Programming and Debugging Connections to Debugger
GPIO straps(bottom side)
Info: Cutting the connections to the debugger will disable programming, debugging, and data streaming
from the PIC16F18076 mounted on the board.
Tip: Solder 0Ω resistors across the footprints or short circuit them with solder to reconnect the signals
between the on-board debugger and the PIC16F18076.
3.5.4
Connecting to External Microcontrollers
The figure and table below show where to connect the programming and debugging signals to program and debug
external microcontrollers. The on-board debugger can supply power to the external hardware or use an external
voltage as a reference for its level shifters. Read more about the power supply in 3.3. Power Supply.
The on-board debugger and level shifters actively drive data and clock signals used for programming and debugging
(DBG0, DBG1, and DBG2). Pull-down resistors are required on the ICSP™ data and clock signals to debug PIC®
microcontrollers. All other interfaces are functional with or without pull-up or pull-down resistors.
DBG3 is an open-drain connection and requires a pull-up resistor to function.
PIC16F18076 Curiosity Nano has pull-down resistors R204 and R205 connected to the ICSP data and clock signal
(DBG0 and DBG1). There is also a pull-up resistor R200 connected to the MCLR signal (DBG3). The location of pull
resistors is shown in 7.2. Assembly Drawing in the appendix.
Remember:
• Connect GND and VTG to the external microcontroller
• Tie the VOFF pin to GND if the external hardware has a power supply
• Make sure there are pull-down resistors on the ICSP data and clock signals (DBG0 and DBG1) to
support the debugging of PIC microcontrollers
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 21
PIC16F18076 Curiosity Nano
Curiosity Nano
Figure 3-10. Curiosity Nano Standard Pinout
USB
PS LED
NC
VBUS
ID
VOFF
CDC RX
DBG3
DEBUGGER
CDC TX
DBG0
DBG1
GND
DBG2
VTG
CURIOSITY NANO
Table 3-4. Programming and Debugging Interfaces
Curiosity Nano Pin
3.6
ICSP™
UPDI
SWD
DBG0
UPDI
DATA
SWDIO
DBG1
—
CLK
SWCLK
DBG2
—
—
—
DBG3
—
MCLR
RESET
Connecting External Debuggers
Even though there is an on-board debugger, external debuggers can be connected directly to the PIC16F18076
Curiosity Nano to program/debug the PIC16F18076. When not actively used, the on-board debugger keeps all the
pins connected to the PIC16F18076 and board edge in tri-state. Therefore, the on-board debugger will not interfere
with any external debug tools.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 22
PIC16F18076 Curiosity Nano
Curiosity Nano
™
Figure 3-11. Connecting the MPLAB® PICkit 4 In-Circuit Debugger/Programmer to PIC16F18076 Curiosity
Nano
1 = MCLR
MPLAB® PICkit™ 4
2 = VDD
3 = Ground
4 = PGD
5 = PGC
6 = Unused
7 = Unused
8 = Unused
8 7 6 5 4 3 2 1
MCLR
VDD
Ground
DATA
CLOCK
USB
NC
PS LED
VBUS
ID
CDC RX
CAUTION
DBG3
DEBUGGER
CDC TX
DBG0
DBG1
GND
DBG2
CAUTION
VOFF
CURIOSITY NANO
VTG
The MPLAB® PICkit™ 4 In-circuit Debugger/Programmer can deliver high voltage on the MCLR pin. High
voltage can permanently damage R110. If R110 is broken, the on-board debugger cannot enter the
programming mode of the PIC16F18076 and will typically fail at reading the device ID.
To avoid contention between the external debugger and the on-board debugger, do not start any
programming/debug operation with the on-board debugger through MPLAB® X IDE or mass storage
programming while the external tool is active.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 23
PIC16F18076 Curiosity Nano
Hardware Description
4.
Hardware Description
4.1
Connectors
4.1.1
PIC16F18076 Curiosity Nano Pinout
All the PIC16F18076 I/O pins are accessible at the edge connectors on the board. The image below shows the board
pinout.
Figure 4-1. PIC16F18076 Curiosity Nano Pinout
PIC16F18076
Curiosity Nano
USB
EUSART TX1
RC6
CDC TX
DBG2
CDC RX
DBG1
RC6
EUSART RX1
RC7
RC7
SDA1
RC4
SCL1
RC3
MOSI2
RB0
MISO2
RB1
SCK2
RB2
SS2
RB3
RD4
RD3
RD2
RD1
RD0
GND
RC5
RA7
RA6
RA5
RA4
RA3
RE2
RA2
(RC0)
LED0
GND
GND
SW0
RA1
(RC1)
GND
RE1
(RC1)
RE0
SOSCI
RC2
(RC0)
PIC16F18076
RB5
SOSCO
RB4
RE2
GND
RE1
RB3
RE0
RB2
RC2
RB1
RB5
RB0
RB4
EUSART RX2
RC3
EUSART TX2
CDC TX
DEBUGGER
PIC16F18076
RD5
DBG2
RD6
DBG1
RA0
RD7
RB6
SW0
VTG
ICSPCLK
GND
CDC TX
DBG0
EUSART RX2
DEBUGGER
DBG3
RB5
CDC RX
VOFF
CDC RX
Port
Debug
PWM
I2C
Power
SPI
Ground
UART
Shared pin
Peripheral
VBUS
EUSART TX2
RC4
RB4
GND
PS LED
ID
ID
NC
NC
Analog
VBUS
VOFF
DBG3
RE3
MCLR
DBG0
RB7
ICSPDAT
GND
VTG
RD7
AND7
RD6
AND6
RD5
AND5
RD4
AND4
PWM[3/4]
RD3
AND3
PWM[3/4]
RD2
AND2
RD1
AND1
RD0
AND0
GND
RC5
RA7
RA6
RA5
RA4
RA3
RA2
RA1
LED0
GND
Info: Peripheral signals shown in the image above, such as UART, I2C, SPI, ADC, PWM, and others, are
shown at specific pins to comply with the Curiosity Nano Board standard. These signals can usually be
routed to alternate pins using the Peripheral Pin Select (PPS) feature in the PIC16F18076.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 24
PIC16F18076 Curiosity Nano
Hardware Description
4.1.2
Using Pin-Headers
The edge connector footprint on PIC16F18076 Curiosity Nano has a staggered design where each hole is shifted 8
mil (~0.2 mm) off-center. The hole shift allows regular 100 mil pin-headers to be used without soldering on the board.
The pin-headers can be used in applications like pin sockets and prototyping boards without issues once they are
firmly in place.
Figure 4-2. Attaching Pin-Headers to the Curiostiy Nano Board
Figure 4-3. Connecting to Curiosity Nano Base for Click boards
™
Tip: Start at one end of the pin header and gradually insert the header along the length of the board.
Once all the pins are in place, use a flat surface to push them in.
Tip: For applications where the pin-headers will be used permanently, it is still recommended to solder
them in place.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 25
PIC16F18076 Curiosity Nano
Hardware Description
Important: Once the pin-headers are in place, they are hard to remove by hand. Use a set of pliers and
carefully remove the pin-headers to avoid damage to the pin-headers and PCB.
4.2
Peripherals
4.2.1
LED
One yellow user LED is available on the PIC16F18076 Curiosity Nano board. It can be controlled by either GPIO or
PWM. Driving the connected I/O line to GND can also activate the LED.
Table 4-1. LED Connection
PIC16F18076 Pin
RA1
4.2.2
Function
Yellow LED0
Shared Functionality
Edge connector
Mechanical Switch
The PIC16F18076 Curiosity Nano board has one mechanical switch - a generic user-configurable switch. Pressing it
will connect the I/O pin to ground (GND).
Tip: There is no externally connected pull-up resistor on the switch. The internal pull-up resistor on pin
RA0 must be enabled to use the switch.
Table 4-2. Mechanical Switch
PIC16F18076 Pin
RA0
4.2.3
Description
User switch (SW0)
Shared Functionality
Edge connector, On-board debugger
Crystal
The PIC16F18076 Curiosity Nano board has a footprint for a 3.2 mm by 1.5 mm surface mount crystal with two
terminals.
The crystal footprint has a cut-strap (J211) next to it that can be used to measure the oscillator safety factor. This
is done by cutting the strap and adding a 0402 SMD resistor across the strap. More information about oscillator
allowance and safety factor can be found in the AN2648 application note from Microchip.
The cut straps and solder points can be seen in Figure 4-4.
Table 4-3. Crystal Connections
PIC16F18076 Pin
Function
Shared Functionality
RC0
SOSCO (Crystal output)
Edge connector
RC1
SOSCI (Crystal input)
Edge connector
Some hardware modifications are required to use RC0 and RC1 as GPIO.
WARNING
Before performing any hardware modifications, ensure that the board is disconnected from the USB or
external power.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 26
PIC16F18076 Curiosity Nano
Hardware Description
•
•
Disconnect the crystal footprint by cutting the two straps on the top side of the board next to the crystal (J209,
J210). The footprint must be disconnected if a crystal is mounted to prevent damage to the crystal.
Connect the I/O lines to the edge connector by placing solder blobs on the circular solder points marked RC0
and RC1 on the bottom side of the board (J207, J208)
Figure 4-4. Crystal Connection and Cut Straps
Crystal
Footprint
J208
J209
J207
J210
J211
Top Side
4.2.4
Bottom Side
On-Board Debugger Implementation
PIC16F18076 Curiosity Nano features an on-board debugger that can be used to program and debug the
PIC16F18076 using ICSP. The on-board debugger also includes a virtual serial port (CDC) interface over UART
and debug GPIO. MPLAB® X IDE can be used as a front-end for the on-board debugger for programming and
debugging. MPLAB Data Visualizer can be used as a front-end for the CDC and debug GPIO.
4.2.4.1
On-Board Debugger Connections
The table below shows the connections between the target and the debugger section. All the connections between
the target and the debugger are tri-stated when the debugger is not using the interface. Hence, there are few
contaminations of the signals, e.g., 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 3.1. On-Board Debugger
Overview.
Table 4-4. On-Board Debugger Connections
PIC16F18076
Pin
Debugger Pin
Function
Shared Functionality
RB5
CDC TX
EUSART[1/2] RX (PIC16F18076 RX
line)
Edge connector
RB4
CDC RX
EUSART[1/2] TX (PIC16F18076 TX
line)
Edge connector
RB7
DBG0
ICSPDAT
Edge connector
RB6
DBG1
ICSPCLK
Edge connector
RA0
DBG2
SW0/GPIO
Edge connector
RE3
DBG3
MCLR
Edge connector
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 27
PIC16F18076 Curiosity Nano
Hardware Revision History and Known Issues
5.
Hardware Revision History and Known Issues
This user guide provides information about the latest available revision of the board. The following sections contain
information about known issues, a revision history of older revisions, and how older revisions differ from the latest
revision.
5.1
Identifying Product ID and Revision
There are two ways to find the revision and product identifier of the PIC16F18076 Curiosity Nano: Either by utilizing
the MPLAB® X IDE Kit Window or by looking at the sticker on the bottom of the PCB.
The Kit Window will pop up when connecting PIC16F18076 Curiosity Nano to a computer with MPLAB® X IDE
running. The first six digits of the serial number, listed under kit information, contain the product identifier and
revision.
Tip: If closed, the Kit Window can be opened in MPLAB® X IDE through the menu bar Window > Kit
Window.
The same information is found on the sticker on the bottom side of the PCB. Most boards will have the identifier and
revision printed in plain text as A09-nnnn\rr, where “nnnn” is the identifier, and “rr” is the revision.
The serial number string has the following format:
"nnnnrrssssssssss"
n = product identifier
r = revision
s = serial number
The product identifier for PIC16F18076 Curiosity Nano is A09-3454.
5.2
Revision 3
Revision 3 is the initially released board revision.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 28
PIC16F18076 Curiosity Nano
Document Revision History
6.
Document Revision History
Doc. Rev.
Date
Comments
A
09/2022
Initial document release
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 29
PIC16F18076 Curiosity Nano
Appendix
7.
Appendix
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 30
rotatethispage90
3
4
5
PIC16F18076
GND
B
C202
100n
RB0_MOSI2
RB1_MISO2
RB2_SCK2
1
2
3
4
5
6
7
8
9
10
40
39
38
37
36
35
34
33
32
31
Name
Pin
CDC TX
EUSART2 RX
RB5
CDC RX
EUSART2 TX
RB4
DBG0
ICSPDAT
RB7
DBG1
ICSPCLK
RB6
DBG2
GPIO0
RA0
DBG3
MCLR
RE3
CDC_RX
CDC_TX
DBG0
DBG3
DBG1
DBG2
VOFF
ID_SYS
CDC_RX
CDC_TX
DBG0
DBG3
DBG1
DBG2
VOFF
ID_SYS
A
PROG/DEBUG PULL
DBG0
DBG1
1.8V - 5.5V
R204
47k
R205
47k
VTG
GND
U200
PIC16F18076T-I/MP
RC6
RC5
RC4
RD3
RD2
RD1
RD0
RC3
RC2
RC1
EP
8
GND
RC0_SOSCO
RA6
RA7
30
29
28
27
26
25
24
23
22
21
C200
100n
RE2
RE1
RE0
RA5
RA4
VCC_TARGET
RB4_EUSART2_TX
RB5_EUSART2_RX
RC2
RE0
RE1
RE2
RC0_SOSCO
RC1_SOSCI
MCLR PULL-UP
11
12
13
14
15
16
17
18
19
20
RC0
RA6
RA7
VSS
VDD
RE2
RE1
RE0
RA5
RA4
RB4_EUSART2_TX
RB5_EUSART2_RX
RB6_ICSPCLK
RA0_SW0
RC6_EUSART1_TX
RC7_EUSART1_RX
RC4_SDA1
RC3_SCL1
RB0_MOSI2
RB1_MISO2
RB2_SCK2
RB3_SS2
R200
100k
RB3_SS2
RB4_EUSART2_TX
RB5_EUSART2_RX
RB6_ICSPCLK
RB7_ICSPDAT
RE3_MCLR
RA0_SW0
RA1_LED0
RA2
RA3
VCC_TARGET
J201
J203
J205
J206
GND
J207
J208
RC0
RC1
GND
VBUS
J200
DEBUGGER
NC 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
RESERVED VBUS
ID
VOFF
CDC RX
DBG3
CDC TX
DBG0
DBG1
GND
DBG2
VCC
0 TX
ADC 7
1 RX
ADC 6
2 SDA
ADC 5
3 SCL
PWM 4
4 MOSI
PWM 3
5 MISO
ADC 2
6 SCK
ADC 1
7 SS
ADC 0
GND
GND
0 (TX)
7
1 (RX)
6
2
5
3
4
0
7
1
6
2
5
3
4
GND
GND
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
J202
J204
GND
VCC_EDGE
GND
RE3_MCLR
RB7_ICSPDAT
RD7_AND7
RD6_AND6
RD5_AND5
RD4_AND4_PWM
RD3_AND3_PWM
RD2_AND2
RD1_AND1
RD0_AND0
B
RC5
RA7
RA6
RA5
RA4
RA3
RA2
RA1_LED0
GND
TARGET
CNANO48-pin edge connector
RE3_MCLR
C
RC1_SOSCI
TARGET BULK
2
D200
1
XOUT
XIN
XC200
NOTE on I2C:
No pull-ups on board. Pull-ups should be
mounted close to client device(s).
J211
N.M
C205
2.2uF
32.768kHz
N.M C206
GND
R203
1k
D
CDC TX is output from the DEBUGGER.
CDC RX is input to the DEBUGGER.
TX is output from the TARGET device.
RX is input to the TARGET device.
C207 N.M
GND
Drawn By:
D
ST
GND
Engineer:
ST
GND
Project Title
Designed with
PIC16F 18076 Curiosity Nano
Sheet Title
Target MCU
Assembly Number: A09-3454
A3 PCB
PCB Number:
A08-3140
File: PIC16F18076_Curiosity_Nano_Target_MCU.SchDoc
Size
1
2
3
4
5
6
7
Altium.com
PCBA Revision: 3
PCB Revision: 2
Date: 8/23/2022
Page: 2 of 4
8
Appendix
DS50003399A-page 31
SW200
VCC_EDGE
YELLOW LED
SML-D12Y1WT86
R202
1k
VCC_TARGET
RX/TX on the header denotes the
input/output direction of the signal
respective to it's source.
32KHz Cr ystal
J209
USER LED
NOTE on UART/CDC:
J210
RA1_LED0
RA0_SW0
USER BUTTON
RC0_SOSCO
C
PIC16F18076 Curiosity Nano
User Guide
VCC_TARGET
RC7
RD4
RD5
RD6
RD7
VSS
VDD
RB0
RB1
RB2
RB3
RB4
RB5
RB6/ICSPCLK
RB7/ICSPDAT
RE3/MCLR
RA0
RA1
RA2
RA3
41
RC6_EUSART1_TX
RC5
RC4_SDA1
RD3_AND3_PWM
RD2_AND2
RD1_AND1
RD0_AND0
RC3_SCL1
RC2
RC1_SOSCI
A
RC7_EUSART1_RX
RD4_AND4_PWM
RD5_AND5
RD6_AND6
RD7_AND7
7
DEBUGGER CONNECTIONS
PIC16F18076
Debugger
GND
6
VOFF
DBG3
DBG0
2
DBG2
DBG1
CDC_TX
CDC_RX
ID_SYS
1
TS604VM1-035CR
1
3
2
4
and its subsidiaries
© 2022 Microchip Technology Inc.
Figure 7-1. PIC16F18076 Curiosity Nano MCU Schematic
2
rotatethispage90
3
4
5
6
7
Interface
TARGET ADJUSTABLE REGULATOR
GND
2
GND
GND
GND
GND
C103
2.2uF
VTG_EN
GND
GND
VOUT
VOUT
GND
J100
A1
B1
C1
J101
MIC94163
GND
VCC_TARGET
R111
47k
GND
R105
47k
BYP
R101
47k
6
C102
100n
5
VIN
VIN
EN
GND
GND
VTG_ADC
DAC
R106
33k
UPDI
TARGET
SWD
TARGET
UART RX
UART RX
UART RX
CDC RX
UART TX
UART TX
J101:
This is footprint for a 1x2 100mil pitch pin-header that can be used for easy current measurement
to the target microcontroller and the LED / Button. To use the footprint:
- Cut the track between the holes, and mount a pin-header
UART TX
DBG0
DAT
UPDI
SWDAT
DBG1
CLK
GPIO
SWCLK
DBG2
GPIO
GPIO
SWO/GPIO
MIC5353:
Vin: 2.6V to 6V
Vout: 1.25V to 5.1V
Imax: 500mA
Dropout (typical): 50mV@150mA, 160mV @ 500mA
Accuracy: 2% initial
Thermal shutdown and current limit
DBG3
MCLR
RESET
RESET
VCC
-
-
-
DEBUGGER TESTPOINT
Adjustable output and limitations:
- The DEBUGGER can adjust the output voltage of the regulator between 1.25V and 5.1V to the target.
- The voltage output is limited by the input (USB), which can vary between 4.40V to 5.25V
- The level shifters have a minimal voltage level of 1.65V and will limit the minimum operating voltage allowed for the
target to still allow communication.
- The MIC94163 has a minimal volatege level of 1.70V and will limit the minimum voltage delivered to the target.
- Firmware configuration will limit the voltage range to be within the the target specification.
DEBUGGER REGULATOR
VCC_VBUS
R114
18R
J102
SWCLK
1
3
5
7
9
SWDIO
Programming connector
for factory programming
of DEBUGGER.
B
TCK
TDO
TMS
Vsup
TDI
2
4
6
8
10
GND
VTref
SRST
TRST
GND
GND
VCC_P3V3
SRST
VDBG_IN 6
4
C104
2.2uF
A
MIC5528:
Vin: 2.5V to 5.5V
Vout: Fixed 3.3V
Imax: 500mA
Dropout: 260mV @ 500mA
Maximum output voltage is limited by the input voltage and the dropout voltage in the regulator.
(Vmax = Vin - dropout)
U101 MIC5528-3.3YMT
1
VIN
VOUT
EN
VOUT
Testpoint Array
GND
NC
EP
NC/ADJ
REG_ADJUST
R104
27k
R100
47k
C100
4.7uF
R103
47k
A
1
7
R109
47k
REG_ENABLE
U108
A2
B2
C2
ICSP
TARGET
CDC TX
Signal
J100:
Cut-strap used for full separation of target power from the level shifters and on-board regulators.
- For current measurements using an external power supply, this strap could be cut for more
accurate measurements. Leakage back through the switch is in the micro ampere range.
VCC_EDGE
GND
EN
U102
VCC_LEVEL
3
VIN
VCC_REGULATOR
MIC5353
4
VOUT
R102
47k
VCC_VBUS
3
8
VCC_P3V3
2
C101
2.2uF
5
7
1
VBUS_ADC
GND
B
GND
DEBUGGER
DEBUGGER POWER/STATUS LED
VCC_MCU_CORE
GND
C106
1u
GND
R107
1k
STATUS_LED
VCC_LEVEL
CDC_RX
CDC_RX
6
5
4
VCCB
DIR
B
74LVC1T45FW4-7
1
VCCA
2 VCC_P3V3
GND
3 GND
A
U105
DBG0_CTRL
VCC_LEVEL
DBG0
DBG0
6
5
4
74LVC1T45FW4-7
1
VCCB
VCCA
2 VCC_P3V3
DIR
GND
3 GND
B
A
R108
1k
C
DBG1
DBG1
6
5
4
VCCB
DIR
B
S1_0_TX
S1_1_RX
DAC
VTG_ADC
S0_0_RX
RESERVED
S0_2_TX
S0_3_CLK
74LVC1T45FW4-7
1
VCCA
2 VCC_P3V3
GND
3 GND
A
1
2
3
4
5
6
7
8
PA00
PA01
PA02
PA03
PA04
PA05
PA06
PA07
U107
DBG2_CTRL
VCC_LEVEL
DBG2
DBG2
6
5
4
74LVC1T45FW4-7
1
VCCB
VCCA
2 VCC_P3V3
DIR
GND
3 GND
B
A
VCC_P3V3
GND
3
Q101
DMN65D8LFB
1
VCC_VBUS
F100
U100
SAMD21E18A-MUT
MC36213
C108
100n
USBD_P
USBD_N
ID_SYS
CDC_TX_CTRL
VOFF
CDC_RX_CTRL
VTG_EN
DBG3_CTRL
GND
SHIELD
PAD
GND
ID PIN
C
MU-MB0142AB2-269
ID_SYS
D
ST
Engineer:
ST
DBG3_CTRL
Project Title
R113
47k
Designed with
PIC16F 18076 Curiosity Nano
Sheet Title
Debugger
Assembly Number: A09-3454
A3 PCB
PCB Number:
A08-3140
File: PIC16F18076_Curiosity_Nano_Debugger.SchDoc
3
VBUS
DD+
ID
GND
SHIELD1
SHIELD2
SHIELD3
SHIELD4
Drawn By:
Size
2
1
2
3
4
5
6
7
8
9
VCC_P3V3
ID_SYS
VOFF
1
USBD_N
USBD_P
33
GND
VOFF
PTC Resettable fuse:
Hold current: 500mA
Trip current: 1000mA
J105
24
23
22
21
20
19
18
17
R113:
Pull down to prevent
DBG3_CTRL from
floating when debugger is
not powered.
R110
1k
D
VBUS
GND
4
5
6
7
Altium.com
PCBA Revision: 3
PCB Revision: 2
Date: 8/23/2022
Page: 3 of 4
8
Appendix
DS50003399A-page 32
DBG3 OPEN DRAIN
DBG3
DBG3
DEBUGGER USB MICRO-B CONNECTOR
TP100 TP101
USB_DP/PA25
USB_DM/PA24
USB_SOF/PA23
PA22
PA19
PA18
PA17
PA16
VDDANA
GND
PA08
PA09
PA10
PA11
PA14
PA15
VCC_LEVEL
BOOT
9
10
11
12
13
14
15
16
U106
DBG1_CTRL
SRST
SWCLK
SWDIO
VCC_P3V3
R112
1k
U104
CDC_RX_CTRL
74LVC1T45FW4-7
1
VCCA
2 VCC_P3V3
GND
3 GND
A
32
31
30
29
28
27
26
25
CDC_TX
VCCB
DIR
B
SWDIO/PA31
SWDCLK/PA30
VDDIN
VDDCORE
GND
PA28
RESETN
PA27
CDC_TX
6
5
4
2
GREEN LED
SML-P12MTT86R
DBG2_CTRL
DBG2_GPIO
REG_ENABLE
VBUS_ADC
DBG0_CTRL
DBG1_CTRL
VCC_LEVEL
D100
PIC16F18076 Curiosity Nano
User Guide
U103
CDC_TX_CTRL
1
VCC_P3V3
C107
100n
2
and its subsidiaries
© 2022 Microchip Technology Inc.
Figure 7-2. PIC16F18076 Curiosity Nano Debugger Schematic
PIC16F18076 Curiosity Nano
Appendix
7.2
Assembly Drawing
Figure 7-3. PIC16F18076 Curiosity Nano Assembly Drawing Top
PIC
MCU
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 33
PIC16F18076 Curiosity Nano
Appendix
Figure 7-4. PIC16F18076 Curiosity Nano Assembly Drawing Bottom
4
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 34
PIC16F18076 Curiosity Nano
Appendix
7.3
Curiosity Nano Base for Click boards™
Figure 7-5. PIC16F18076 Curiosity Nano Pinout Mapping
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 35
PIC16F18076 Curiosity Nano
Appendix
Disconnecting the On-Board Debugger
The on-board debugger and level shifters can be completely disconnected from the PIC16F18076.
The block diagram below shows all connections between the debugger and the PIC16F18076. The rounded boxes
represent connections to the board edge. The signal names shown are also printed in silkscreen on the bottom side
of the board.
To disconnect the debugger, cut the straps shown in Figure 7-7.
Attention: Cutting the GPIO straps to the on-board debugger will disable the virtual serial port,
programming, debugging, and data streaming. Cutting the power supply strap will disconnect the on-board
power supply.
Tip: Reconnect any cut connection by using solder. Alternatively, mount a 0Ω 0402 resistor.
Tip: When the debugger is disconnected, an external debugger can be connected to holes, as shown
in Figure 7-7. Details about connecting an external debugger are described in 3.6. Connecting External
Debuggers.
Figure 7-6. On-Board Debugger Connections Block Diagram
VTG
Power Supply strap
VBUS
LDO
LDO
VCC_P3V3
PA04/PA06
PA07
PA08
PA16
PA00
PA01
DIR x 5
VCC_EDGE
DBG0
DBG1
DBG2
Level-Shift DBG3
CDC TX
CDC RX
CDC RX
CDC TX
© 2022 Microchip Technology Inc.
and its subsidiaries
Target Power strap
VCC_LEVEL
USB
VOFF
VCC_TARGET
VBUS
DEBUGGER
7.4
GPIO straps
TARGET
UART RX
UART TX
DBG0
DBG1
DBG2
DBG3
User Guide
DS50003399A-page 36
PIC16F18076 Curiosity Nano
Appendix
Figure 7-7. On-Board Debugger Connection Cut Straps
GPIO straps (bottom side)
© 2022 Microchip Technology Inc.
and its subsidiaries
Power Supply strap (top side)
User Guide
DS50003399A-page 37
PIC16F18076 Curiosity Nano
Microchip Information
The Microchip Website
Microchip provides online support via our website at www.microchip.com/. This website is used to make files and
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’s
guides and hardware support documents, latest software releases and archived software
General Technical Support – Frequently Asked Questions (FAQs), technical support requests, online
discussion groups, Microchip design partner program member listing
Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of
seminars and events, listings of Microchip sales offices, distributors and factory representatives
Product Change Notification Service
Microchip’s product change notification service helps keep customers current on Microchip products. Subscribers will
receive email notification whenever there are changes, updates, revisions or errata related to a specified product
family or development tool of interest.
To register, go to www.microchip.com/pcn and follow the registration instructions.
Customer Support
Users 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 to
help customers. A listing of sales offices and locations is included in this document.
Technical support is available through the website at: www.microchip.com/support
Microchip Devices Code Protection Feature
Note the following details of the code protection feature on Microchip products:
•
•
•
•
Microchip products meet the specifications contained in their particular Microchip Data Sheet.
Microchip believes that its family of products is secure when used in the intended manner, within operating
specifications, and under normal conditions.
Microchip values and aggressively protects its intellectual property rights. Attempts to breach the code
protection features of Microchip product is strictly prohibited and may violate the Digital Millennium Copyright
Act.
Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code
protection does not mean that we are guaranteeing the product is “unbreakable”. Code protection is constantly
evolving. Microchip is committed to continuously improving the code protection features of our products.
Legal Notice
This publication and the information herein may be used only with Microchip products, including to design, test,
and integrate Microchip products with your application. Use of this information in any other manner violates these
terms. Information regarding device applications is provided only for your convenience and may be superseded
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 38
PIC16F18076 Curiosity Nano
by updates. It is your responsibility to ensure that your application meets with your specifications. Contact your
local Microchip sales office for additional support or, obtain additional support at www.microchip.com/en-us/support/
design-help/client-support-services.
THIS INFORMATION IS PROVIDED BY MICROCHIP "AS IS". MICROCHIP MAKES NO REPRESENTATIONS
OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY
OR OTHERWISE, RELATED TO THE INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE,
OR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE.
IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR
CONSEQUENTIAL LOSS, DAMAGE, COST, OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE
INFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE
POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW,
MICROCHIP'S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION OR ITS USE
WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR
THE INFORMATION.
Use of Microchip devices 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 such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights
unless otherwise stated.
Trademarks
The Microchip name and logo, the Microchip logo, Adaptec, AVR, AVR logo, AVR Freaks, BesTime, BitCloud,
CryptoMemory, CryptoRF, dsPIC, flexPWR, HELDO, IGLOO, JukeBlox, KeeLoq, Kleer, LANCheck, LinkMD,
maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo, MOST, MOST logo, MPLAB, OptoLyzer,
PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip Designer, QTouch, SAM-BA, SenGenuity, SpyNIC, SST,
SST Logo, SuperFlash, Symmetricom, SyncServer, Tachyon, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are
registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
AgileSwitch, APT, ClockWorks, The Embedded Control Solutions Company, EtherSynch, Flashtec, Hyper Speed
Control, HyperLight Load, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASIC Plus,
ProASIC Plus logo, Quiet- Wire, SmartFusion, SyncWorld, Temux, TimeCesium, TimeHub, TimePictra, TimeProvider,
TrueTime, 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, Augmented Switching,
BlueSky, BodyCom, Clockstudio, CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion,
CryptoController, dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, Espresso T1S,
EtherGREEN, GridTime, IdealBridge, In-Circuit Serial Programming, ICSP, INICnet, Intelligent Paralleling, IntelliMOS,
Inter-Chip Connectivity, JitterBlocker, Knob-on-Display, KoD, maxCrypto, maxView, 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, RTAX, RTG4, SAMICE, Serial Quad I/O, simpleMAP, SimpliPHY, SmartBuffer, SmartHLS, SMART-I.S., storClad, SQI, SuperSwitcher,
SuperSwitcher II, Switchtec, SynchroPHY, Total Endurance, Trusted Time, TSHARC, USBCheck, VariSense,
VectorBlox, VeriPHY, ViewSpan, WiperLock, XpressConnect, 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 of
Microchip Technology Inc. in other countries.
GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip
Technology Inc., in other countries.
All other trademarks mentioned herein are property of their respective companies.
©
2022, Microchip Technology Incorporated and its subsidiaries. All Rights Reserved.
ISBN: 978-1-6683-1162-2
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 39
PIC16F18076 Curiosity Nano
Quality Management System
For information regarding Microchip’s Quality Management Systems, please visit www.microchip.com/quality.
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 40
Worldwide Sales and Service
AMERICAS
ASIA/PACIFIC
ASIA/PACIFIC
EUROPE
Corporate Office
2355 West Chandler Blvd.
Chandler, AZ 85224-6199
Tel: 480-792-7200
Fax: 480-792-7277
Technical Support:
www.microchip.com/support
Web Address:
www.microchip.com
Atlanta
Duluth, GA
Tel: 678-957-9614
Fax: 678-957-1455
Austin, TX
Tel: 512-257-3370
Boston
Westborough, MA
Tel: 774-760-0087
Fax: 774-760-0088
Chicago
Itasca, IL
Tel: 630-285-0071
Fax: 630-285-0075
Dallas
Addison, TX
Tel: 972-818-7423
Fax: 972-818-2924
Detroit
Novi, MI
Tel: 248-848-4000
Houston, TX
Tel: 281-894-5983
Indianapolis
Noblesville, IN
Tel: 317-773-8323
Fax: 317-773-5453
Tel: 317-536-2380
Los Angeles
Mission Viejo, CA
Tel: 949-462-9523
Fax: 949-462-9608
Tel: 951-273-7800
Raleigh, NC
Tel: 919-844-7510
New York, NY
Tel: 631-435-6000
San Jose, CA
Tel: 408-735-9110
Tel: 408-436-4270
Canada - Toronto
Tel: 905-695-1980
Fax: 905-695-2078
Australia - Sydney
Tel: 61-2-9868-6733
China - Beijing
Tel: 86-10-8569-7000
China - Chengdu
Tel: 86-28-8665-5511
China - Chongqing
Tel: 86-23-8980-9588
China - Dongguan
Tel: 86-769-8702-9880
China - Guangzhou
Tel: 86-20-8755-8029
China - Hangzhou
Tel: 86-571-8792-8115
China - Hong Kong SAR
Tel: 852-2943-5100
China - Nanjing
Tel: 86-25-8473-2460
China - Qingdao
Tel: 86-532-8502-7355
China - Shanghai
Tel: 86-21-3326-8000
China - Shenyang
Tel: 86-24-2334-2829
China - Shenzhen
Tel: 86-755-8864-2200
China - Suzhou
Tel: 86-186-6233-1526
China - Wuhan
Tel: 86-27-5980-5300
China - Xian
Tel: 86-29-8833-7252
China - Xiamen
Tel: 86-592-2388138
China - Zhuhai
Tel: 86-756-3210040
India - Bangalore
Tel: 91-80-3090-4444
India - New Delhi
Tel: 91-11-4160-8631
India - Pune
Tel: 91-20-4121-0141
Japan - Osaka
Tel: 81-6-6152-7160
Japan - Tokyo
Tel: 81-3-6880- 3770
Korea - Daegu
Tel: 82-53-744-4301
Korea - Seoul
Tel: 82-2-554-7200
Malaysia - Kuala Lumpur
Tel: 60-3-7651-7906
Malaysia - Penang
Tel: 60-4-227-8870
Philippines - Manila
Tel: 63-2-634-9065
Singapore
Tel: 65-6334-8870
Taiwan - Hsin Chu
Tel: 886-3-577-8366
Taiwan - Kaohsiung
Tel: 886-7-213-7830
Taiwan - Taipei
Tel: 886-2-2508-8600
Thailand - Bangkok
Tel: 66-2-694-1351
Vietnam - Ho Chi Minh
Tel: 84-28-5448-2100
Austria - Wels
Tel: 43-7242-2244-39
Fax: 43-7242-2244-393
Denmark - Copenhagen
Tel: 45-4485-5910
Fax: 45-4485-2829
Finland - Espoo
Tel: 358-9-4520-820
France - Paris
Tel: 33-1-69-53-63-20
Fax: 33-1-69-30-90-79
Germany - Garching
Tel: 49-8931-9700
Germany - Haan
Tel: 49-2129-3766400
Germany - Heilbronn
Tel: 49-7131-72400
Germany - Karlsruhe
Tel: 49-721-625370
Germany - Munich
Tel: 49-89-627-144-0
Fax: 49-89-627-144-44
Germany - Rosenheim
Tel: 49-8031-354-560
Israel - Ra’anana
Tel: 972-9-744-7705
Italy - Milan
Tel: 39-0331-742611
Fax: 39-0331-466781
Italy - Padova
Tel: 39-049-7625286
Netherlands - Drunen
Tel: 31-416-690399
Fax: 31-416-690340
Norway - Trondheim
Tel: 47-72884388
Poland - Warsaw
Tel: 48-22-3325737
Romania - Bucharest
Tel: 40-21-407-87-50
Spain - Madrid
Tel: 34-91-708-08-90
Fax: 34-91-708-08-91
Sweden - Gothenberg
Tel: 46-31-704-60-40
Sweden - Stockholm
Tel: 46-8-5090-4654
UK - Wokingham
Tel: 44-118-921-5800
Fax: 44-118-921-5820
© 2022 Microchip Technology Inc.
and its subsidiaries
User Guide
DS50003399A-page 41
工商网监
湘ICP备2023018690号
