MICROCHIP EV26Q64A User guide

PIC18F16Q41 Curiosity Nano

PIC18F16Q41 Curiosity Nano Hardware User Guide

Preface

The PIC18F16Q41 Curiosity Nano Evaluation Kit is a hardware platform to evaluate microcontrollers in the PIC18‑Q41 Family. This board has the PIC18F16Q41 microcontroller (MCU) mounted.

Supported by MPLAB® X IDE, the board provides easy access to the features of the PIC18F16Q41 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 PIC18F16Q41.

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

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

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

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

User Guide

DS50003048A-page 1

PIC18F16Q41 Curiosity Nano

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

1. Introduction............................................................................................................................................. 4

1.1. Features....................................................................................................................................... 4

1.2. Board Overview............................................................................................................................4

2. Getting Started........................................................................................................................................ 5

2.1. Quick Start....................................................................................................................................5

2.1.1. Driver Installation...........................................................................................................5

2.1.2. Kit Window.....................................................................................................................5

2.1.3. MPLAB® X IDE Device Family Packs............................................................................5

2.2. Design Documentation and Relevant Links................................................................................. 5

3. Preprogrammed Application....................................................................................................................7

4. Curiosity Nano.........................................................................................................................................8

4.1. On-Board Debugger Overview..................................................................................................... 8

4.1.1. Debugger.......................................................................................................................8

4.1.2. Virtual Serial Port (CDC)................................................................................................9

4.1.2.1. Overview..................................................................................................... 9

4.1.2.2. Operating System Support.......................................................................... 9

4.1.2.3. Limitations................................................................................................. 10

4.1.2.4. Signaling....................................................................................................10

4.1.2.5. Advanced Use........................................................................................... 11

4.1.3. Mass Storage Device...................................................................................................11

4.1.3.1. Mass Storage Device Implementation.......................................................12

4.1.3.2. Configuration Words..................................................................................12

4.1.3.3. Special Commands................................................................................... 12

4.1.4. Data Gateway Interface (DGI)..................................................................................... 13

4.1.4.1. Debug GPIO..............................................................................................13

4.1.4.2. Timestamping............................................................................................14

4.2. Curiosity Nano Standard Pinout................................................................................................. 14

4.3. Power Supply............................................................................................................................. 15

4.3.1. Target Regulator.......................................................................................................... 15

4.3.2. External Supply............................................................................................................17

4.3.3. VBUS Output Pin.........................................................................................................17

4.3.4. Power Supply Exceptions............................................................................................18

4.4. Low-Power Measurement.......................................................................................................... 19

4.5. Programming External Microcontrollers..................................................................................... 20

4.5.1. Supported Devices...................................................................................................... 20

4.5.2. Software Configuration................................................................................................ 20

4.5.3. Hardware Modifications............................................................................................... 21

4.5.4. Connecting to External Microcontrollers...................................................................... 22

4.6. Connecting External Debuggers................................................................................................ 23

5. Hardware User Guide........................................................................................................................... 25

5.1. Connectors.................................................................................................................................25

User Guide

DS50003048A-page 2

PIC18F16Q41 Curiosity Nano

5.1.1. PIC18F16Q41 Curiosity Nano Pinout..........................................................................25

5.1.2. Using Pin Headers.......................................................................................................25

5.1.3. Operational Amplifier................................................................................................... 26

5.2. Peripherals................................................................................................................................. 26

5.2.1. LED..............................................................................................................................27

5.2.2. Mechanical Switch.......................................................................................................27

5.2.3. Crystal..........................................................................................................................27

5.2.4. On-Board Debugger Implementation...........................................................................28

5.2.4.1. On-Board Debugger Connections............................................................. 28

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

6.1. Identifying Product ID and Revision........................................................................................... 29

6.2. Revision 3...................................................................................................................................29

6.3. Revision 2...................................................................................................................................29

7. Document Revision History...................................................................................................................30

8. Appendix............................................................................................................................................... 31

8.1. Schematic...................................................................................................................................31

8.2. Assembly Drawing......................................................................................................................33

8.3. Curiosity Nano Base for Click boards™...................................................................................... 34

8.4. Disconnecting the On-Board Debugger..................................................................................... 35

The Microchip Website.................................................................................................................................37

Product Change Notification Service............................................................................................................37

Customer Support........................................................................................................................................ 37

Microchip Devices Code Protection Feature................................................................................................ 37

Legal Notice................................................................................................................................................. 38

Trademarks.................................................................................................................................................. 38

Quality Management System....................................................................................................................... 39

Worldwide Sales and Service.......................................................................................................................40

User Guide

DS50003048A-page 3

1. Introduction

User Switch

(SW0)

User LED

(LED0)

PIC18F16Q41

MCU

32.768 kHz

Crystal Footprint

Debugger

Power/Status

LED

Micro-USB Connector

1.1 Features

• PIC18F16Q41 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)

PIC18F16Q41 Curiosity Nano

Introduction

1.2 Board Overview

The Microchip PIC18F16Q41 Curiosity Nano Evaluation Kit is a hardware platform to evaluate the PIC18F16Q41 microcontroller.

Figure 1-1. PIC18F16Q41 Curiosity Nano Board Overview

User Guide

DS50003048A-page 4

2. Getting Started

2.1 Quick Start

Steps to start exploring the PIC18F16Q41 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 your 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 is connected to your 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.

PIC18F16Q41 Curiosity Nano

Getting Started

2.1.2 Kit Window

Once the board is powered, the green status LED will be lit, 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. The PIC18F16Q41 device on the PIC18F16Q41 Curiosity Nano board is programmed and debugged by the on-board debugger and, therefore, no external programmer or debugger tool is required.

Tip: The Kit Window can be opened in MPLAB® X IDE 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 PIC18F16Q41 Curiosity Nano, board MPLAB® X version 5.40 with device family pack “PIC18F-Q_DP” version 1.8 and tool pack “nEDBG_TP” version 1.4 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 PIC18F16Q41 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 called an Integrated Development Environment (IDE) because it provides a single integrated “environment” to develop code for embedded microcontrollers.

User Guide

DS50003048A-page 5

PIC18F16Q41 Curiosity Nano

Getting Started

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

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

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

User Guide

DS50003048A-page 6

3. Preprogrammed Application

The PIC18F16Q41 mounted on the Curiosity Nano Evaluation Kit is preprogrammed with an application ready to utilize the integrated operational amplifier.

To get started with the application, find the user guide, code, and hex files for this application available online on GitHub.

PIC18F16Q41 Curiosity Nano

Preprogrammed Application

User Guide

DS50003048A-page 7

4. Curiosity Nano

Curiosity Nano is an evaluation platform of small boards with access to most of the microcontrollers I/Os. The platform consists of a series of low pin count microcontroller (MCU) boards with on-board debuggers, which are integrated with MPLAB® X IDE. Each board is identified in the IDE. When plugged in, 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).

4.1 On-Board Debugger Overview

PIC18F16Q41 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 PIC18F16Q41 in MPLAB® X IDE

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

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

PIC18F16Q41, 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 PIC18F16Q41 Curiosity Nano board. The table below shows how the LED is controlled in different operation modes.

Table 4-1. On-Board Debugger LED Control

PIC18F16Q41 Curiosity Nano

Curiosity Nano

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

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.

4.1.1 Debugger

The on-board debugger on the PIC18F16Q41 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 PIC18F16Q41 using MPLAB® X IDE.

Success: The LED blinks slowly for 2 sec

Failure: The LED blinks rapidly for 2 sec

This can occur if the board is externally powered.

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

User Guide

DS50003048A-page 8

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

Target MCU

UART TX

UART RX

Debugger

USB

CDC RX

CDC TX

Terminal

Software

Target

Receive

Target

Send

Terminal

Receive

Terminal

Send

using MPLAB® X IDE.

4.1.2 Virtual Serial Port (CDC)

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

4.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 4-1. CDC Connection

PIC18F16Q41 Curiosity Nano

Curiosity Nano

Info: As shown in Figure 4-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.

4.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, a USB driver is required for CDC. 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#.

User Guide

DS50003048A-page 9

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

4.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 on 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, 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

• Level shifters (if available) are not disabled, so 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

PIC18F16Q41 Curiosity Nano

Curiosity Nano

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

4.1.2.4 Signaling.

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 should enable the internal pull-up resistor on the pin connected to the debugger’s CDC TX pin.

User Guide

DS50003048A-page 10

4.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=

PIC18F16Q41 Curiosity Nano

Curiosity Nano

The CDC Override Mode should not be used 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.

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

User Guide

DS50003048A-page 11

• Write access for programming Intel® HEX formatted files into the target device’s memory

• Write access for simple text files for utility purposes

4.1.3.1 Mass Storage Device 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. 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 one MB is a trivially chosen value for disk size.

It is not possible to format the CURIOSITY drive. When programming a file to the target, the filename may appear in the disk directory listing. This is merely the operating system’s view of the directory, which, 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 application that has been previously programmed.

To erase the target device, copy a text file starting with “CMD:ERASE” onto the disk.

By default, the CURIOSITY drive contains several read-only files for generating icons as well as reporting status 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

PIC18F16Q41 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, do not reflect the correct status.

4.1.3.2 Configuration Words

Configuration Words (PIC® MCU Targets)

Configuration Word settings included in the project being programmed after program Flash is programmed. 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.

4.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 4-2. Special File Commands

Command Content Description

CMD:ERASE

CMD:SEND_UART=

Executes a chip erase of the target

Sends a string of characters to the CDC UART. See “CDC

Override Mode.”

User Guide

DS50003048A-page 12

...........continued

PIC18F16Q41 Curiosity Nano

Curiosity Nano

Command Content Description

CMD:SEND_9600= CMD:SEND_115200= CMD:SEND_460800=

CMD:RESET

CMD:POWERTOGGLE

CMD:0V

CMD:1V8

CMD:3V3

CMD:5V0

Sends a string of characters to the CDC UART at the baud rate specified. Note that only the baud rates explicitly specified here are supported! See “CDC Override Mode” (Debugger firmware v1.21 or newer.)

Resets the target device by entering Programming mode and then exiting Programming mode immediately thereafter. Exact timing can vary according to the programming interface of the target device. (Debugger firmware v1.16 or newer.)

Powers down the target and restores power after a 100 ms delay. If external power is provided, this has no effect. (Debugger firmware v1.16 or newer.)

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

Sets the target voltage to 1.8V. If external power is provided, this has no effect. (Debugger firmware v1.21 or newer.)

Sets the target voltage to 3.3V. If external power is provided, this has no effect. (Debugger firmware v1.16 or newer.)

Sets the target voltage to 5.0V. If external power is provided, this has no effect. (Debugger firmware v1.16 or newer.)

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

4.1.4 Data Gateway Interface (DGI)

Data Gateway Interface (DGI) is a USB interface for transporting raw and timestamped data between on-board debuggers and host computer-based visualization tools. MPLAB Data Visualizer is used on the host computer to display 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 PIC18F16Q41 Curiosity Nano implementation includes logic analyzer channels:

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

4.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 the occurrence of low-frequency events on a time-axis – for example, when certain application state transitions occur.

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

User Guide

DS50003048A-page 13

PIC18F16Q41 Curiosity Nano

Curiosity Nano

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

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

Important: Although bursts of higher-frequency signals can be captured, the useful 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.

4.1.4.2 Timestamping

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

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

Table 4-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

User Guide

DS50003048A-page 14

USB

DEBUGGER

PS LED

CDC RX

CDC TX

DBG1

DBG2

VBUS

VOFF

DBG3

DBG0

GND

VTG

CURIOSITY NANO

USB

Target

MCU

Power source

Cut strap

Power consumer

P3V3

DEBUGGER

Power converter

DEBUGGER

Regulator

VUSB

Target

Regulator

Power Supply

strap

Adjust

Level

shifter

VLVL

VREG

I/O

GPIO

straps

I/O

On/Off

Measure

On/Off

ID system

#VOFF

PTC

Fuse

Power protection

VBUS

Target Power

strap

VTG

PIC18F16Q41 Curiosity Nano

Curiosity Nano

...........continued

Debugger Signal Target MCU Description

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 4-3. Curiosity Nano Standard Pinout

4.3 Power Supply

The board is powered through the USB port and contains two LDO regulators, one to generate 3.3V for the on-board debugger, and an adjustable LDO regulator for the target PIC18F16Q41 microcontroller and its peripherals. The voltage from a USB connector can vary between 4.4V to 5.25V (according to the USB specification) and will limit the maximum voltage to the target. The figure below shows the entire power supply system on PIC18F16Q41 Curiosity Nano.

Figure 4-4. Power Supply Block Diagram

4.3.1 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

User Guide

DS50003048A-page 15

PIC18F16Q41 Curiosity Nano

Curiosity Nano

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 PIC18F16Q41 microcontroller. The voltage limits configured in the on-board debugger on PIC18F16Q41 Curiosity Nano are 1.8–

5.5V.

Info: The target voltage is set to 3.3V when the board is manufactured. 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: Voltage settings that are set up in MPLAB® X IDE are not immediately applied to the board. The new voltage setting is applied to the board when the debugger is accessed in any way, like pushing the Refresh Debug Tool Status button in the project dashboard tab, or programming/reading program memory.

Info: There is a simple option to adjust the target voltage with a drag-and-drop command text file to the board. This supports a set of common target voltages. See section 4.1.3.3 Special Commands for further details.

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

Figure 4-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 turned off. This will detect and handle any short-circuit conditions. It will also detect and handle if an external voltage, which causes VCC_TARGET to move outside of the voltage setting monitoring window of ±100 mV, is suddenly applied to the VTG pin, without setting the VOFF pin low.

User Guide

DS50003048A-page 16

Info: The on-board debugger has a monitoring window of VCC_TARGET±100 mV. If the external voltage

WARNING

is measured under this limit, the on-board debugger status LED will blink rapidly. If the external voltage is measured above this limit, the on-board debugger status LED will continue to shine. If the external voltage is removed, the status LED will start to blink rapidly until the on-board debugger detects the new situation and turns the target voltage regulator back on.

4.3.2 External Supply

PIC18F16Q41 Curiosity Nano can be powered by an external voltage instead of the on-board target regulator. When the Voltage Off (VOFF) pin is shorted to ground (GND), 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. This will be detected by a pin-change interrupt to the on-board debugger, which controls the target voltage regulator accordingly.

Applying an external voltage to the VTG pin without shorting VOFF to GND may cause permanent damage to the board.

PIC18F16Q41 Curiosity Nano

Curiosity Nano

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 PIC18F16Q41 is 1.8–5.5V. Applying a higher voltage may cause permanent damage to the board.

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 is still possible with an external power supply – the debugger and signal level shifters will be powered from the USB cable. 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 PIC18F16Q41 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 in the DEBUG connector on the board. When a USB cable is not plugged in, some current is used to supply the level shifters voltage pins, which have a worst-case current consumption of approximately 5 µA. Typical values may be as low as 100 nA.

4.3.3 VBUS Output Pin

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

User Guide

DS50003048A-page 17

Figure 4-6. VBUS Output Voltage vs. Current

PIC18F16Q41 Curiosity Nano

Curiosity Nano

4.3.4 Power Supply Exceptions

This is a summary of most exceptions that can occur with the power supply.

Target Voltage Shuts Down

This can happen if the target section draws too much current at a given voltage. This will 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 maximum output voltage is limited by the USB input voltage (specified to be 4.4-5.25V), and 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

This can be caused by an externally applied voltage to the VTG pin, without setting the VOFF pin low. If the target voltage differs more than 100 mV over/under the voltage setting, it will be detected by the on-board debugger, and the internal voltage regulator will be 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 be blinking rapidly if the target voltage is below 100 mV of the setting, but will be lit normally when it is higher than 100 mV above the setting.

No, Or Very Low Target Voltage, and PS LED is Blinking Rapidly

This can be caused by a full or partial short-circuit and is a special case of the issue mentioned above. Remove the short-circuit, and the on-board debugger will re-enable the on-board target voltage regulator.

User Guide

DS50003048A-page 18

No Target Voltage and PS LED is Lit 1

Target Power strap (top side)

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

This is most likely caused by 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.

4.4 Low-Power Measurement

Power to the PIC18F16Q41 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 PIC18F16Q41 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:

4.1. Tri-states any I/O connected to the on-board debugger.

4.2. Sets the microcontroller in its lowest power sleep mode.

5. Program the firmware into the PIC18F16Q41.

Figure 4-7. Target Power Strap

PIC18F16Q41 Curiosity Nano

Curiosity Nano

User Guide

DS50003048A-page 19

Tip: A 100-mil pin header can be soldered into the Target Power strap (J101) footprint for easy connection of an ammeter. Once the ammeter is no longer needed, place a jumper cap on the pin header.

Info: The on-board level shifters will draw a small amount of current even when they are not in use. A maximum of 2 µA can be drawn from each I/O pin connected to a level shifter for a total of 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 5.2.4.1 On-Board Debugger Connections. To prevent any leakage to the on-board level shifters, they can be disconnected completely, as described in 8.4 Disconnecting the On-Board

Debugger.

4.5 Programming External Microcontrollers

The on-board debugger on PIC18F16Q41 Curiosity Nano can be used to program and debug microcontrollers on external hardware.

4.5.1 Supported Devices

All external AVR microcontrollers with the UPDI interface can be programmed and debugged with the on-board debugger with Atmel Studio.

External SAM microcontrollers that have a Curiosity Nano Board can be programmed and debugged with the onboard debugger with Atmel Studio.

PIC18F16Q41 Curiosity Nano can program and debug external PIC18F16Q41 microcontrollers with MPLAB X IDE.

PIC18F16Q41 Curiosity Nano

Curiosity Nano

4.5.2 Software Configuration

No software configuration is required to program and debug the same device that is mounted on the board.

To program and debug a different microcontroller than what is mounted on the board, Atmel Studio must be configured to allow free selection of devices and programming interfaces.

1. Navigate to

2. Select the Tools > Tool settings category in the options window.

3. Set the Hide unsupported devices option to False.

Tools > Options through the menu system at the top of the application.

User Guide

DS50003048A-page 20

Figure 4-8. Hide Unsupported Devices

PIC18F16Q41 Curiosity Nano

Curiosity Nano

Info: Atmel Studio allows any microcontroller and interface to be selected when the Hide unsupported devices setting is set to False, also microcontrollers and interfaces which are not supported by the on-

board debugger.

4.5.3 Hardware Modifications

The on-board debugger is connected to the PIC18F16Q41 by default. These connections must be removed 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 PIC18F16Q41 from the on-board debugger.

User Guide

DS50003048A-page 21

GPIO straps (bottom side)

PIC18F16Q41 Curiosity Nano

Figure 4-9. Programming and Debugging Connections to Debugger

Curiosity Nano

Info: Cutting the connections to the debugger will disable programming, debugging, and data streaming

from the PIC18F16Q41 mounted on the board.

Tip: Solder in 0Ω resistors across the footprints or short-circuit them with solder to reconnect the signals between the on-board debugger and the PIC18F16Q41.

4.5.4 Connecting to External Microcontrollers

The figure and table below show where the programming and debugging signals must be connected 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 4.3 Power Supply.

The on-board debugger and level shifters actively drive data and clock signals (DBG0, DBG1, and DBG2) used for programming and debugging, and in most cases, the external resistor on these signals can be ignored. Pull-down resistors are required on the ICSP™ data and clock signals to debug PIC® microcontrollers.

DBG3 is an open-drain connection and requires a pull-up resistor to function.

PIC18F16Q41 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 the 8.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

User Guide

DS50003048A-page 22

Figure 4-10. Curiosity Nano Standard Pinout

USB

DEBUGGER

PS LED

CDC RX

CDC TX

DBG1

DBG2

VBUS

VOFF

DBG3

DBG0

GND

VTG

CURIOSITY NANO

Table 4-4. Programming and Debugging Interfaces

PIC18F16Q41 Curiosity Nano

Curiosity Nano

Curiosity Nano Pin UPDI ICSP

DBG0 UPDI DATA SWDIO

DBG1 — CLK SWCLK

DBG2 — — —

DBG3 — #MCLR #RESET

4.6 Connecting External Debuggers

Even though there is an on-board debugger, external debuggers can be connected directly to the PIC18F16Q41 Curiosity Nano to program/debug the PIC18F16Q41. The on-board debugger keeps all the pins connected to the PIC18F16Q41 and board edge in tri-state when not actively used. Therefore, the on-board debugger will not interfere with any external debug tools.

™

SWD

User Guide

DS50003048A-page 23

678

MCLR VDD Ground DATA

CLOCK

3 = Ground

4 = PGD

5 = PGC

6 = Unused

7 = Unused

8 = Unused

2 = VDD

1 = MCLR

MPLAB® PICkit™ 4

USB

DEBUGGER

PS LED

CDC RX

CDC TX

DBG1

DBG2

VBUS

VOFF

DBG3

DBG0

GND

VTG

CURIOSITY NANO

CAUTION

PIC18F16Q41 Curiosity Nano

Curiosity Nano

Figure 4-11. Connecting the MPLAB® PICkit™ 4 In-Circuit Debugger/Programmer to PIC18F16Q41 Curiosity Nano

The MPLAB PICkit 4 In-circuit Debugger/Programmer is capable of delivering high voltage on the MCLR pin. R110 can be permanently damaged by the high voltage. If R110 is broken, the on-board debugger can not enter Programming mode of the PIC18F16Q41, 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.

User Guide

DS50003048A-page 24

5. Hardware User Guide

USB

DEBUGGER

PIC18F16Q41

SW0

LED0

PS LED

CDC RX

CDCRX

UART[n] TXRB7

CDC TX

CDCTX

UART[n] RXRB5

DBG1

RA1ICSPCLK

DBG2

RC0SW0

RB7

UART[n] TXCDC RX

RB5

UART[n] RXCDC TX

RB4

I2C1 SDA

RB6

I2C1 SCL

RC5

SPI[n] MOSI

RC4

SPI[n] MISO

RC6

SPI[n] SCK

RC7

SPI[n] SS

GND

VBUS

VOFF

DBG3

RA3 MCLR

DBG0

RA0 ICSPDAT

GND

VTG

RA5

ANA5 (SOSCI)

RA4

ANA4 (SOSCO)

RC0

ANC0 PWM[n] SW0

RA0

ANA0 PWM[n]

RC1

ANC1 PWM[n] LED0

RC2

ANC2 OPA1 OUT

RA2

ANA2 OPA1 IN2 DAC1

RC3

ANC3 OPA1 IN1

GND

DEBUGGER

PIC18F16Q41

Analog

Debug

I2C

SPI

UART

Peripheral

Port

PWM

Power

Ground

OPAMP

Shared pin

PIC18F16Q41

Curiosity Nano

5.1 Connectors

5.1.1 PIC18F16Q41 Curiosity Nano Pinout

All the PIC18F16Q41 I/O pins are accessible at the edge connectors on the board. The image below shows the board pinout.

Figure 5-1. PIC18F16Q41 Curiosity Nano Pinout

PIC18F16Q41 Curiosity Nano

Hardware User Guide

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

5.1.2 Using Pin Headers

The edge connector footprint on PIC18F16Q41 Curiosity Nano has a staggered design where each hole is shifted 8 mil (~0.2 mm) off-center. The hole shift allows the use of regular 100 mil pin headers on the board without soldering. Once the pin headers are firmly in place, they can be used in normal applications like pin sockets and prototyping boards without any issues.

User Guide

DS50003048A-page 25

PIC18F16Q41 Curiosity Nano

Figure 5-2. Attaching Pin-Headers to the Curiostiy Nano Board

Hardware User Guide

Figure 5-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.

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.

™

5.1.3 Operational Amplifier

PIC18F16Q41 features an internal operational amplifier (OPA) with a flexible connection scheme using multiple inputs, inverting and non-inverting. This allows a large number of analog signal conditioning configurations, many requiring no external components.

For information about operational amplifier on the edge connector and any shared functionality see 5.1.1

PIC18F16Q41 Curiosity Nano Pinout.

5.2 Peripherals

User Guide

DS50003048A-page 26

5.2.1 LED

There is one yellow user LED available on the PIC18F16Q41 Curiosity Nano board that can be controlled by either GPIO or PWM. The LED can be activated by driving the connected I/O line to GND.

Table 5-1. LED Connection

PIC18F16Q41 Pin Function Shared Functionality

RC1 Yellow LED0 Edge connector

5.2.2 Mechanical Switch

The PIC18F16Q41 Curiosity Nano board has one mechanical switch. This is a generic user-configurable switch. When the switch is pressed, it will drive the I/O line to ground (GND).

Tip: There is no externally connected pull-up resistor on the switch. To use the switch, make sure that an internal pull-up resistor is enabled on pin RC0.

Table 5-2. Mechanical Switch

PIC18F16Q41 Pin Description Shared Functionality

PIC18F16Q41 Curiosity Nano

Hardware User Guide

RC0 User switch (SW0) Edge connector, On-board debugger

5.2.3 Crystal

The PIC18F16Q41 Curiosity Nano Board has a 32.768 kHz crystal footprint made for standard 3.2 mm by 1.5 mm surface mount crystals with two terminals.

The crystal footprint is not connected to the PIC18F16Q41 by default, as the GPIOs are routed out to the edge connector. To use the crystal, some hardware modifications are required.

• The two I/O lines routed to the edge connector must be disconnected to reduce the chance of contention to the crystal, and to remove excessive capacitance on the lines.

• Disconnect the edge connector by cutting the two cut-straps on the bottom side of the board, marked RA4 and RA5.

• Connect the crystal by soldering on a solder blob on each of the circular solder points next to the crystal on the top side of the board, J210 and J211.

The crystal has a cut-strap next (J209) to it, which 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 5-4.

Table 5-3. Crystal Connections

RA4 SOSCO (Crystal output) Edge connector

RA5 SOSCI (Crystal input) Edge connector

PIC18F16Q41 Pin Function Shared Functionality

User Guide

DS50003048A-page 27

Figure 5-4. Crystal Connection and Cut Straps

Top side

Bo�om side

J208

J207

J211

J210

32.768 kHz

Crystal footprint

J209

5.2.4 On-Board Debugger Implementation

PIC18F16Q41 Curiosity Nano features an on-board debugger that can be used to program and debug the PIC18F16Q41 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.

PIC18F16Q41 Curiosity Nano

Hardware User Guide

5.2.4.1 On-Board Debugger Connections

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

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

Overview.

Table 5-4. On-Board Debugger Connections

PIC18F16Q41 Pin

RB5 CDC TX UART RX (PIC18F16Q41 RX line) Edge connector

RB7 CDC RX UART TX (PIC18F16Q41 TX line) Edge connector

RA0 DBG0 ICSPDAT Edge connector

RA1 DBG1 ICSPCLK Edge connector

RC0 DBG2 SW0/GPIO Edge connector

RA3 DBG3 MCLR Edge connector

Debugger Pin Function Shared Functionality

User Guide

DS50003048A-page 28

PIC18F16Q41 Curiosity Nano

Hardware Revision History and Known Issues

6. Hardware Revision History and Known Issues

This user guide is written to provide 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.

6.1 Identifying Product ID and Revision

The revision and product identifier of the PIC18F16Q41 Curiosity Nano board can be found in two ways: Either by utilizing the MPLAB® X IDE Kit Window or by looking at the sticker on the bottom side of the PCB.

By connecting PIC18F16Q41 Curiosity Nano to a computer with MPLAB® X IDE running, the Kit Window will pop up. The first six digits of the serial number, which is listed under kit information, contain the product identifier and revision.

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

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

The serial number string has the following format:

"nnnnrrssssssssss"

n = product identifier

r = revision

s = serial number

The product identifier for PIC18F16Q41 Curiosity Nano is A09‑3378.

6.2 Revision 3

PIC18F16Q41 silicon revision A5 or later is mounted on this revision of the board.

6.3 Revision 2

Revision 2 is the initially released board revision.

PIC18F16Q41 silicon revision A4 is mounted on this revision of the board.

User Guide

DS50003048A-page 29

7. Document Revision History

Revision Date Description

A 09/2020 Initial document release

PIC18F16Q41 Curiosity Nano

Document Revision History

User Guide

DS50003048A-page 30

D D

C C

B B

A A

2 of 4

PIC18F 16Q40 Curiosity Nan o

8/13/2020

PIC18F16Q40_Curiosity_Nano_Target_MCU.SchDoc

Project Title

PCB Assembly Number: PCBA Revision:

File:

PCB Number: PCB Revision:

Designed with

Drawn By:

Sheet Title

Target MCU

Engineer:

A08-3084 2

Size

A09-3373 2

Page:

Date:

Altium.com

3.9p

C203

N.M

3.9p

C204

N.M

GND

100n

C200

GND

32KHz C rystal

DBG0

R203

USER LE D

VCC_TARGET

GND

USER BUTT ON

R202

YELLOW LED

SML-D12Y1WT86

D200

TS604VM1-035CR

1 3

SW200

CDC_TX

CDC_RX

DBG2

GND VCC_EDGE

GNDGND

DBG1

DBG3

DBG2

DEBUGG ER CONNE CTIO NS

DBG1

DBG3

J209

DBG0

PIC18F 16Q40

ICSPDAT

ICSPCLK

GPIO0

MCLR

DBG0

DBG1

DBG2

DBG3

Debugger

CDC TX

CDC RX

UART[n] RX

UART[n] TX

PIC18F16Q40

RA3_MCLR

RA1_ANA1_ICSPCLK

J210

J211XOUT

XIN

GND

2.2uF

C205

VCC_EDGE

GND

RA0_ANA0_ICSPDAT

RC0_ANC0_SW0

RC1_ANC1_LED0

RC2_ANC2RC3_ANC3

RC4_SPI_MISO

RC5_SPI_MOSI

RC6_SPI_SCK

RC7_SPI_SS

RA2_ANA2

RA4_ANA4_SOSCO

RA5_ANA5_SOSCI

RB4_I2C1_SDA

RB5_UART_RX

RB6_I2C1_SCLRB7_UART_TX

RA4_ANA4_SOSCO

RA5_ANA5_SOSCI

RB7_UART_TX

RB5_UART_RX

RB4_I2C1_SDA

RB6_I2C1_SCL

RC4_SPI_MISO

RC5_SPI_MOSI

RC6_SPI_SCK

RC7_SPI_SS RC3_ANC3

RA2_ANA2

RC2_ANC2

RC1_ANC1_LED0

RA0_ANA0_ICSPDAT

RC0_ANC0_SW0

RA4_ANA4_SOSCO

RA5_ANA5_SOSCI

RA1_ANA1_ICSPCLK

RA0_ANA0_ICSPDAT

RA3_MCLR

RC0_ANC0_SW0

RB7_UART_TX

RB5_UART_RX

TARGET BULK

PRO G/DEBUG Pu ll

47k

R204

47k

R205

GND

VTG 1.8V - 5.5V

VOFF

ID_SYS

VOFF

DBG0

DBG1

CDC RX3CDC TX4DBG15DBG260 TX71 RX82 SDA93 SCL104 MOSI115 MISO126 SCK137 SS14GND

DBG3

DBG0

GND

VCC

PWM 3

ADC 2

ADC 1

ADC 0

GND

ADC 724ADC 6

ADC 5

PWM 4

DEBUGGER

TARGET

VOFF

RESERVED

VBUS

CNANO30-pin edge connector

J200

VBUS

J201

J203

J205

J206

J202

J204

RA1

RC0

RA3

RA0

RB7

RB5

Name Pin

RC0_ANC0_SW0

RC1_ANC1_LED0

RA4

RA5

32.768kHz

VMK3-9001-32K7680000TR

XC200

N.M

J207

J208

47k

R200

CDC_TX

CDC_RX

CDC_TX

CDC_RX

DBG2

DBG1

DBG3

DBG0

VOFF

ID_SYS

VCC_TARGET

RA3/MCLR/VPP4RC55RC46RC37RC68RC79RB7

RB611RB5

RB413RC214RC115RC016RA2

ICSPCLK/RA118ICSPDAT/RA0

VSS

VDD1SOSCI/RA52SOSCO/RA4

PIC18F16Q40-I/SS

U200

Crystal datasheet:

Ccrystal = 7pF

max ESR = 70kOhm

Accuracy ±20ppm

Estimated parameters

Cxin = 5pF

Cxout = 5pF

Cpcb = 2.5pF

Estimated load

C = 2 (Ccrystal- Cpara - Cpcb)

C = 2 (7pF - 2.5pF - 2.5pF)

C = 4pF

Selected in design

C = 3.9pF

RX/TX on the header denotes the

input/output direction of the signal

respective to it's source.

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.

mounted close to slave device(s).

PIC18F16Q41 Curiosity Nano

Appendix

8. Appendix

8.1 Schematic

Figure 8-1. PIC18F16Q41 Curiosity Nano Schematic

User Guide

DS50003048A-page 31

D D

C C

B B

A A

3 of 4

PIC18F 16Q41 Curiosity Nan o

4/6/2020

PIC18F16Q41_Curiosity_Nano_Debugger.SchDoc

Project Title

PCB Assembly Number: PCBA Revision:

File:

PCB Number: PCB Revision:

Designed with

Drawn By:

Sheet Title

Debugger

Engineer:

A08-3086 2

Size

A09-3378 2

Page:

Date:

Altium.com

DEBUGG ER USB MIC RO-B CONNE CTOR

GND

USBD_P

USBD_N

100n

C107

100n

C108

R107

VCC_P3V3

SRST

STATUS_LED

SHIELD

VBUS

VCC_P3V3

GND

TP100

Testpoint Array

1 2

3 4

5 6

7 8

9 10

TCK

TDO

TMS

Vsup

TDI GND

TRST

SRST

VTref

GND

J102

GND

4.7uF

C100

DBG0

GREEN LED

SML-P12MTT86R

D100

VBUS1D-2D+3GND5SHIELD16SHIELD27ID4SHIELD38SHIELD4

MU-MB0142AB2-269

J105

PAD

PA001PA012PA023PA03

GND

VDDANA

PA045PA056PA067PA07

PA08

PA09

PA10

PA11

PA14

PA15

PA16

PA17

PA18

PA19

PA22

USB_SOF/PA23

USB_DM/PA24

USB_DP/PA25

PA27

RESETN

PA28

GND

VDDCORE

VDDIN

SWDCLK/PA30

SWDIO/PA31

SAMD21E18A-MUT

U100

VOUT1VOUT

GND

EN4VIN

MIC5528-3.3YMTU101 VCC_P3V3

GND

USBD_P

USBD_N

GND

C106

VCC_MCU_CORE

VCC_P3V3

2.2uF

C101

GND

74LVC1T45FW4-7

VCCA

VCCB

GND

DIR5B

U103

VCC_P3V3

GND

74LVC1T45FW4-7

VCCA

VCCB

GND

DIR5B

U104

VCC_P3V3

GND

74LVC1T45FW4-7

VCCA

VCCB

GND

DIR5B

U105

VCC_P3V3

GND

VCC_EDGE

GND

74LVC1T45FW4-7

VCCA

VCCB

GND

DIR5B

U107

VCC_P3V3

GND

DBG2

DBG3_CTRL

S1_0_TX

S1_1_RX

S0_2_TX

DAC

VTG_ADC

RESERVED

S0_3_CLK

DBG0_CTRL

CDC_TX_CTRL

BOOT

DEBUGGE R POWE R/STATUS LED

EN1BYP

VOUT

GND

VIN

NC/ADJ

GND

MIC5353U102

100n

C102

GND

47k

R101

27k

R104

GND

33k

R106

2.2uF

C103

GND

R108

J100

VCC_LEVELVCC_REGULATOR

74LVC1T45FW4-7

VCCA

VCCB

GND

DIR5B

U106

VCC_P3V3

GND

DBG1

CDC_RX

CDC_TX

DBG3

DBG1_CTRL

DEBUGG ER REGUL ATOR

REG_ENABLE

47k

R103

VCC_LEVEL

47k

R102

47k

R105

SWCLK

GND

47k

R100

GND

DBG2

S0_0_RX

DBG1_CTRL

DBG0_CTRL

DBG3 OP EN DRAIN

TARGET ADJUST ABLE REGUL ATOR

SRST

DEBUGG ER TEST POINT

DBG2_CTRL

VOFF

CDC_RX_CTRL

47k

R109

DBG1

CDC_TX_CTRL

CDC_RX_CTRL

SWCLK

REG_ADJUST

DBG2_GPIO

DBG3_CTRL

DBG2_CTRL

DBG3

R110

VBUS_ADC

2 3

DMN65D8LFB

Q101

ID_SYS

VOFF

R112

VCC_P3V3

VTG_ADC

DAC

MIC94163

VIN

VOUT

VINA2EN

GND

VOUT

U108

GND

ID_SYS

VTG_EN

VBUS_ADC

SWDIO

ID_SYS

TP101

GND

SWDIO

VOFF

47k

R111

GND

ID PI N

VCC_VBUS

MC36213

F100

VCC_VBUS

J101

VCC_TARGET

47k

R113

DEBUGGER

UPDI

GPIO

RESET

Signal

DBG0

DBG1

DBG2

DBG3

ICSP

Interface

DAT

CLK

GPIO

MCLR

CDC TX

CDC RX

UART RX

UART TX

UART RX

UART TX

TARGET TARGET

VCC - -

SWD

SWDAT

SWCLK

SWO/GPIO

RESET

UART RX

UART TX

TARGET

CDC_TX

CDC_RX

AVR programming

connector for factory

programming of

DEBUGGER.

MIC5528:

Vin: 2.5V to 5.5V

Vout: Fixed 3.3V

Imax: 500mA

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

Maximum output voltage is limited by the input voltage and the dropout voltage in the regulator.

(Vmax = Vin - dropout)

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.

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

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.

PTC Resettable fuse:

Hold current: 500mA

Trip current: 1000mA

R113:

Pull down to prevent

DBG3_CTRL from

floating when debugger is

not powered.

PIC18F16Q41 Curiosity Nano

Appendix

User Guide

DS50003048A-page 32

8.2 Assembly Drawing

PAC10002

PAC10001

COC100

PAC10102

PAC10101

COC101

PAC10201

PAC10202

COC102

PAC10301

PAC10302

COC103

PAC10602

PAC10601

COC106

PAC10702

PAC10701

COC107

PAC10802

PAC10801

COC108

PAC20001

PAC20002

COC200

PAC20301

PAC20302

COC203

PAC20401

PAC20402

COC204

PAC20502

PAC20501

COC205

PAD10001

PAD10002

COD100

PAD20002

PAD20001

COD200

PAF10001 PAF10002

COF100

PAJ10001

PAJ10002

COJ100

PAJ10101

PAJ10102

COJ101

PAJ10201 PAJ10202

PAJ10203 PAJ10204

PAJ10205 PAJ10206

COJ102

PAJ105011

PAJ105010

PAJ10508

PAJ10509

PAJ10507

PAJ10506

PAJ10501 PAJ10502 PAJ10503 PAJ10504 PAJ10505

PAJ10500

COJ105

PAJ200027

PAJ200028

PAJ200030

PAJ200029

PAJ200014

PAJ200017

PAJ200016

PAJ200026

PAJ200025

PAJ200024

PAJ200023

PAJ200022

PAJ200021

PAJ200020

PAJ200019

PAJ200018

PAJ20001

PAJ20002

PAJ20003

PAJ20004

PAJ20005

PAJ20006

PAJ20007

PAJ20008

PAJ20009

PAJ200010

PAJ200011

PAJ200012

PAJ200013

PAJ200015

PAJ20000

COJ200

PAJ20102

PAJ20101

COJ201

PAJ20202

PAJ20201

COJ202

PAJ20302

PAJ20301

COJ203

PAJ20402

PAJ20401

COJ204

PAJ20502

PAJ20501

COJ205

PAJ20602

PAJ20601

COJ206

PAJ20702

PAJ20701

COJ207

PAJ20802

PAJ20801

COJ208

PAJ20902

PAJ20901

COJ209

PAJ21002

PAJ21001

PAJ21005

COJ210

PAJ21102

PAJ21101

PAJ21105

COJ211

COLABEL1

PAQ10103

PAQ10102 PAQ10101

COQ101

PAR10001

PAR10002

COR100

PAR10102 PAR10101

COR101

PAR10201

PAR10202

COR102

PAR10301

PAR10302

COR103

PAR10402 PAR10401

COR104

PAR10501

PAR10502

COR105

PAR10602

PAR10601

COR106

PAR10701

PAR10702

COR107

PAR10802 PAR10801

COR108

PAR10902

PAR10901

COR109

PAR11002

PAR11001

COR110

PAR11102

PAR11101

COR111

PAR11202

PAR11201

COR112

PAR11301

PAR11302

COR113

PAR20001

PAR20002

COR200

PAR20202

PAR20201

COR202

PAR20302

PAR20301

COR203

PAR20402

PAR20401

COR204

PAR20502

PAR20501

COR205

PASW20004

PASW20002

PASW20003

PASW20001

COSW200

PATP10001

COTP100

PATP10101

COTP101

PAU10009

PAU10008

PAU10007 PAU10006

PAU10005

PAU10004 PAU10003

PAU10002 PAU10001

PAU100010

PAU100011

PAU100012

PAU100013

PAU100014

PAU100015

PAU100016

PAU100017

PAU100018 PAU100019

PAU100020

PAU100021 PAU100022

PAU100023 PAU100024

PAU100025

PAU100026

PAU100027

PAU100028

PAU100029

PAU100030

PAU100031

PAU100032

PAU100033

COU100

PAU10101

PAU10102

PAU10103

PAU10106

PAU10105

PAU10104

PAU10107

PAU10100

COU101

PAU10201 PAU10202

PAU10203

PAU10206 PAU10205

PAU10204

PAU10207

COU102

PAU10301

PAU10302 PAU10303

PAU10304

PAU10305

PAU10306

PAU10300

COU103

PAU10401

PAU10402

PAU10403

PAU10404

PAU10405

PAU10406

PAU10400

COU104

PAU10501

PAU10502 PAU10503

PAU10504

PAU10505

PAU10506

PAU10500

COU105

PAU10601

PAU10602 PAU10603

PAU10604

PAU10605

PAU10606

PAU10600

COU106

PAU10701

PAU10702 PAU10703

PAU10704

PAU10705

PAU10706

PAU10700

COU107

PAU1080C2

PAU1080C1

PAU1080B2

PAU1080B1

PAU1080A2

PAU1080A1

COU108

PAU20001

PAU20002

PAU20003

PAU20004

PAU20005

PAU20006

PAU20007

PAU20008

PAU20009

PAU200010

PAU200020

PAU200019

PAU200018

PAU200017

PAU200016

PAU200015

PAU200014

PAU200013

PAU200012

PAU200011

COU200

PAXC20002

PAXC20001

COXC200

PAC10002

PAC10001

COC100

PAC10102

PAC10101

COC101

PAC10201

PAC10202

COC102

PAC10301

PAC10302

COC103

PAC10602

PAC10601

COC106

PAC10702

PAC10701

COC107

PAC10802

PAC10801

COC108

PAC20001

PAC20002

COC200

PAC20301

PAC20302

COC203

PAC20401

PAC20402

COC204

PAC20502

PAC20501

COC205

PAD10001

PAD10002

COD100

PAD20002

PAD20001

COD200

PAF10001 PAF10002

COF100

PAJ10001

PAJ10002

COJ100

PAJ10101

PAJ10102

COJ101

PAJ10201 PAJ10202

PAJ10203 PAJ10204

PAJ10205 PAJ10206

COJ102

PAJ105011

PAJ105010

PAJ10508

PAJ10509

PAJ10507

PAJ10506

PAJ10501 PAJ10502 PAJ10503 PAJ10504 PAJ10505

PAJ10500

COJ105

PAJ200027

PAJ200028

PAJ200030

PAJ200029

PAJ200014

PAJ200017

PAJ200016

PAJ200026

PAJ200025

PAJ200024

PAJ200023

PAJ200022

PAJ200021

PAJ200020

PAJ200019

PAJ200018

PAJ20001

PAJ20002

PAJ20003

PAJ20004

PAJ20005

PAJ20006

PAJ20007

PAJ20008

PAJ20009

PAJ200010

PAJ200011

PAJ200012

PAJ200013

PAJ200015

PAJ20000

COJ200

PAJ20102

PAJ20101

COJ201

PAJ20202

PAJ20201

COJ202

PAJ20302

PAJ20301

COJ203

PAJ20402

PAJ20401

COJ204

PAJ20502

PAJ20501

COJ205

PAJ20602

PAJ20601

COJ206

PAJ20702

PAJ20701

COJ207

PAJ20802

PAJ20801

COJ208

PAJ20902

PAJ20901

COJ209

PAJ21002

PAJ21001

PAJ21005

COJ210

PAJ21102

PAJ21101

PAJ21105

COJ211

COLABEL1

PAQ10103

PAQ10102 PAQ10101

COQ101

PAR10001

PAR10002

COR100

PAR10102 PAR10101

COR101

PAR10201

PAR10202

COR102

PAR10301

PAR10302

COR103

PAR10402 PAR10401

COR104

PAR10501

PAR10502

COR105

PAR10602

PAR10601

COR106

PAR10701

PAR10702

COR107

PAR10802 PAR10801

COR108

PAR10902

PAR10901

COR109

PAR11002

PAR11001

COR110

PAR11102

PAR11101

COR111

PAR11202

PAR11201

COR112

PAR11301

PAR11302

COR113

PAR20001

PAR20002

COR200

PAR20202

PAR20201

COR202

PAR20302

PAR20301

COR203

PAR20402

PAR20401

COR204

PAR20502

PAR20501

COR205

PASW20004

PASW20002

PASW20003

PASW20001

COSW200

PATP10001

COTP100

PATP10101

COTP101

PAU10009

PAU10008

PAU10007 PAU10006

PAU10005

PAU10004 PAU10003

PAU10002 PAU10001

PAU100010

PAU100011

PAU100012

PAU100013

PAU100014

PAU100015

PAU100016

PAU100017

PAU100018 PAU100019

PAU100020

PAU100021 PAU100022

PAU100023 PAU100024

PAU100025

PAU100026

PAU100027

PAU100028

PAU100029

PAU100030

PAU100031

PAU100032

PAU100033

COU100

PAU10101

PAU10102

PAU10103

PAU10106

PAU10105

PAU10104

PAU10107

PAU10100

COU101

PAU10201 PAU10202

PAU10203

PAU10206 PAU10205

PAU10204

PAU10207

COU102

PAU10301

PAU10302 PAU10303

PAU10304

PAU10305

PAU10306

PAU10300

COU103

PAU10401

PAU10402

PAU10403

PAU10404

PAU10405

PAU10406

PAU10400

COU104

PAU10501

PAU10502 PAU10503

PAU10504

PAU10505

PAU10506

PAU10500

COU105

PAU10601

PAU10602 PAU10603

PAU10604

PAU10605

PAU10606

PAU10600

COU106

PAU10701

PAU10702 PAU10703

PAU10704

PAU10705

PAU10706

PAU10700

COU107

PAU1080C2

PAU1080C1

PAU1080B2

PAU1080B1

PAU1080A2

PAU1080A1

COU108

PAU20001

PAU20002

PAU20003

PAU20004

PAU20005

PAU20006

PAU20007

PAU20008

PAU20009

PAU200010

PAU200020

PAU200019

PAU200018

PAU200017

PAU200016

PAU200015

PAU200014

PAU200013

PAU200012

PAU200011

COU200

PAXC20002

PAXC20001

COXC200

Figure 8-2. PIC18F16Q41 Curiosity Nano Assembly Drawing Top

Figure 8-3. PIC18F16Q41 Curiosity Nano Assembly Drawing Bottom

PIC18F16Q41 Curiosity Nano

Appendix

User Guide

DS50003048A-page 33

USB

DEBUGGER

PIC18F16Q41

SW0

LED0

PS LED

NCNCID

CDC RX

CDCRX

UART[n] TXRB7

CDC TX

CDCTX

UART[n] RXRB5

DBG1

RA1ICSPCLK

DBG2

RC0SW0

RB7

UART[n] TXCDC RX

RB5

UART[n] RXCDC TX

RB4

I2C1 SDA

RB6

I2C1 SCL

RC5

SPI[n] MOSI

RC4

SPI[n] MISO

RC6

SPI[n] SCK

RC7

SPI[n] SS

GND

VBUS

VOFF

DBG3

RA3 MCLR

DBG0

RA0 ICSPDAT

GND

VTG

RA5

ANA5 (SOSCI)

RA4

ANA4 (SOSCO)

RC0

ANC0 PWM[n] SW0

RA0

ANA0 PWM[n]

RC1

ANC1 PWM[n] LED0

RC2

ANC2 OPA1 OUT

RA2

ANA2 OPA1 IN2 DAC1

RC3

ANC3 OPA1 IN1

GND

DEBUGGER

PIC18F16Q41

Analog

Debug

I2C

SPI

UART

Peripheral

Port

PWM

Power

Ground

OPAMP

Shared pin

PIC18F16Q41

Curiosity Nano

AN PWM

RST INT

CS RX

SCK TX

MISO SCL

MOSI SDA

+3.3V +5V

GND GND

AN PWM

RST INT

CS RX

SCK TX

MISO SCL

MOSI SDA

+3.3V +5V

GND GND

AN PWM

RST INT

CS RX

SCK TX

MISO SCL

MOSI SDA

+3.3V +5V

GND GND

Xplained Pro Extension

EXT1

1 2

19 20

Curiosity Nano Base

for click boards

RC3 RC1

RA5 RA4

RC7 RB5

RC6 RB7

RC4 RB6

RC5 RB4

+3.3V +5V

GND GND

RA2 RA0

RC6

RC4 RB6

RC5 RB4

+3.3V +5V

GND GND

RC2 RC0

RB5

RC6 RB7

RC4 RB6

RC5 RB4

+3.3V +5V

GND GND

ID GND

RA2 RC2

RA0 RC0

RB4 RB6

RC5

RC4 RC6

GND +3.3V

PIC18F16Q41 Curiosity Nano

Appendix

8.3 Curiosity Nano Base for Click boards

Figure 8-4. PIC18F16Q41 Curiosity Nano Pinout Mapping

™

User Guide

DS50003048A-page 34

8.4 Disconnecting the On-Board Debugger

DEBUGGER

TARGET

Level-Shift

PA04/PA06 PA07 PA08 PA16 PA00 PA01

USB

DIR x 5

VCC_P3V3

VBUS

VCC_LEVEL

VCC_TARGET

DBG0 DBG1 DBG2 DBG3 CDC TX CDC RX

CDC RX CDC TX

DBG3

DBG2

DBG1

DBG0

GPIO straps

LDO

VOFF

LDO

VBUS VTG

VCC_EDGE

Power Supply strap Target Power strap

UART RX UART TX

The on-board debugger and level shifters can be completely disconnected from the PIC18F16Q41.

The block diagram below shows all connections between the debugger and the PIC18F16Q41. 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 8-6.

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: Any connection that is cut can be reconnected using solder. Alternatively, a 0Ω 0402 resistor can be mounted.

Tip: When the debugger is disconnected, an external debugger can be connected to holes shown in

Figure 8-6. Details about connecting an external debugger are described in 4.6 Connecting External Debuggers.

PIC18F16Q41 Curiosity Nano

Appendix

Figure 8-5. On-Board Debugger Connections Block Diagram

User Guide

DS50003048A-page 35

Figure 8-6. On-Board Debugger Connection Cut Straps

GPIO straps (bottom side) Power Supply strap (top side)

PIC18F16Q41 Curiosity Nano

Appendix

User Guide

DS50003048A-page 36

PIC18F16Q41 Curiosity Nano

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 devices:

• 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 and under normal conditions.

• There are dishonest and possibly illegal methods being used in attempts to breach the code protection features of the Microchip devices. We believe that these methods require using the Microchip products in a manner outside the operating specifications contained in Microchip’s Data Sheets. Attempts to breach these code protection features, most likely, cannot be accomplished without violating Microchip’s intellectual property rights.

• Microchip is willing to work with any customer who is concerned about the integrity of its code.

• 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. We at Microchip are committed to continuously improving the code protection features of our products. Attempts to break Microchip’s code protection feature may be a violation of the Digital Millennium Copyright Act. If such acts allow unauthorized access to your software or other copyrighted work, you may have a right to sue for relief under that Act.

User Guide

DS50003048A-page 37

PIC18F16Q41 Curiosity Nano

Legal Notice

Information contained in this publication is provided for the sole purpose of designing with and using Microchip products. Information regarding device applications and the like is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications.

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

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

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

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

The Adaptec logo, Frequency on Demand, Silicon Storage Technology, and Symmcom are registered trademarks 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.

ISBN: 978-1-5224-6863-9

User Guide

DS50003048A-page 38

PIC18F16Q41 Curiosity Nano

Quality Management System

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

User Guide

DS50003048A-page 39

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

User Guide

DS50003048A-page 40

MICROCHIP EV26Q64A User guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Preface

Table of Contents

1. Introduction

1.1 Features

1.2 Board Overview

2. Getting Started

2.1 Quick Start

2.1.1 Driver Installation

2.1.2 Kit Window

2.1.3 MPLAB® X IDE Device Family Packs

2.2 Design Documentation and Relevant Links

3. Preprogrammed Application

4. Curiosity Nano

4.1 On-Board Debugger Overview

4.1.1 Debugger

4.1.2 Virtual Serial Port (CDC)

4.1.2.1 Overview

4.1.2.2 Operating System Support

4.1.2.3 Limitations

4.1.2.4 Signaling.

4.1.2.5 Advanced Use

4.1.3 Mass Storage Device

4.1.3.1 Mass Storage Device Implementation

4.1.3.2 Configuration Words

4.1.3.3 Special Commands

4.1.4 Data Gateway Interface (DGI)

4.1.4.1 Debug GPIO

4.1.4.2 Timestamping

4.2 Curiosity Nano Standard Pinout

Power Supply

4.3.1 Target Regulator

4.3.2 External Supply

4.3.3 VBUS Output Pin

4.3.4 Power Supply Exceptions

4.4 Low-Power Measurement

4.5 Programming External Microcontrollers

4.5.1 Supported Devices

4.5.2 Software Configuration

4.5.3 Hardware Modifications

4.5.4 Connecting to External Microcontrollers

4.6 Connecting External Debuggers

5. Hardware User Guide

5.1 Connectors

5.1.1 PIC18F16Q41 Curiosity Nano Pinout

5.1.2 Using Pin Headers

5.1.3 Operational Amplifier

5.2 Peripherals

5.2.1 LED

5.2.2 Mechanical Switch

5.2.3 Crystal

5.2.4 On-Board Debugger Implementation

5.2.4.1 On-Board Debugger Connections

6. Hardware Revision History and Known Issues

6.1 Identifying Product ID and Revision

6.2 Revision 3

6.3 Revision 2

7. Document Revision History

8. Appendix

8.1 Schematic

8.2 Assembly Drawing

8.4 Disconnecting the On-Board Debugger

The Microchip Website

Product Change Notification Service

Customer Support

Microchip Devices Code Protection Feature

Legal Notice

Trademarks

Quality Management System

Worldwide Sales and Service