Curiosity PIC32MZ EF 2.0 Development Board Users Guide
Introduction
The Microchip Technology Curiosity PIC32MZ EF 2.0 Development Board (DM320209) includes an integrated
programmer and debugger, which requires no additional hardware to get started. Users can expand functionality
through MikroElectronika mikroBUS™ Click™ adapter boards, add Ethernet connectivity with the Microchip PHY
Daughter Board, add Wi-Fi® connectivity capability using the Microchip expansions boards, and add audio input and
output capability with Microchip audio daughter boards.
With or without expansion boards, the Curiosity PIC32MZ EF 2.0 Development Board provides the freedom to
develop a variety of applications, including Bluetooth Audio, CAN, Graphics/UI, Internet of Things (IoT), robotics
development, and proof-of-concept designs.
Curiosity PIC32MZ EF 2.0 Development Board Features
The Curiosity PIC32MZ EF 2.0 Development Board has the following features:
• On-Board debugger (PKoB4)
– Real time Programming & Debugging
– Virtual COM port (VCOM)
– Data Gateway Interface (DGI)
• Two mikroBUS interfaces
• Two X32 Audio interfaces supporting Bluetooth® and Audio
• Ethernet interface
• Graphics interface
• Xplained pro extension compatible interface
• CAN interface
• User buttons
• User LEDs
• 8 MB QSPI memory
• Arduino Uno R3 compatible interface
Kit Contents
The kit contains one Curiosity PIC32MZ EF 2.0 Development Board (DM320209).
Note: If any part is missing from the kit, contact a Microchip sales office for assistance. A list of Microchip offices for
sales and service is provided on the last page of this document.
Curiosity PIC32MZ EF 2.0 Development Board
The Curiosity PIC32MZ EF 2.0 Development Board (DM320209) is shown in the following figure:
The Microchip Web Site............................................................................................................................... 39
15USB to PKoB4 for debugging, power, virtual COM port
1.2 System Block Diagram
The following high-level block diagram that shows the major data bus routing.
Figure 1-2. System Block Diagram
Development Board Functionality and Features
1.3 Power Block Diagram
The following figure shows a block diagram of the power system on the Curiosity PIC32MZ EF 2.0 Development
Board. The Curiosity PIC32MZ EF 2.0 Development Board has several power sub systems that allow it to accept up
to 16V. The barrel jack is a 2.1 mm center positive connector. The power in can also be connected through the
Arduino header, this input is before the reverse voltage protection.
The MPLAB® PICkit™ On-Board 4 (PKoB4) is a new generation of In-Circuit Debugger. The MPLAB PKoB4
programs faster than its predecessor, and is designed to use a high-speed 2.0 USB interface and provide a feature
rich debugging experience through one USB cable. The PKoB4 is intended to support programming debugging and a
Data Gateway interface.
The MPLAB PKoB4 In-Circuit Debugger is compatible with any of these platforms:
• Microsoft Windows® 7 or later
®
™
download at https://www.microchip.com/mplabx/)
• Linux
• macOS
The MPLAB PKoB4 In-Circuit Debugger system provides the following advantages:
Features and Capabilities:
• Connects to computer through high-speed USB 2.0 (480 Mbits/s) cable
• Programs devices using MPLAB X IDE or MPLAB IPE
• Supports multiple hardware and software breakpoints, stopwatch, and source
• code file debugging
• Debugs your application in real time
• Sets breakpoints based on internal events
• Monitors internal file registers
• Debugs at full speed
• Configures pin drivers
• Field-upgradeable through an MPLAB X IDE firmware download
• Adds new device support and features by installing the latest version of MPLAB X IDE (available as a free
3.Click on Debug > Hardware Tool Emergency Boot Firmware Recovery.
Figure 1-5. Debugging Window
4.Follow the directions on the screen. This will bring the tool back to the factory conditions.
For additional information on the PKoB4, refer to the “MPLAB® PICkit™ 4 In-Circuit Debugger User’s Guide”
(DS50000251), which is available for download at http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB
The I2C voltage is defaulted to 3.3-volt pull ups. A 5.0-volt option is possible. In order to do this the trace must be cut
and a resistor of 0 ohm or a bus bar must be installed. A 0805 SMD footprint has been provided. This is located on
the back side of the board. The following figure shows the I2C jumper in the trace:
The X32 is a 32-pin interface to the board to support audio codec, DACs, and Bluetooth radios. This interface has
audio supply I2S and other control lines, and data interfaces.
1.6.1 Block Diagram
The Curiosity PIC32MZ EF 2.0 Development Board has two X32 interfaces that share two I2S signals. The following
figure shows the relation between the I2S signals and the X32 daughter board interface.
The following table shows the pinout and description for the X32 Audio interface. Refer to the Schematics for
additional information.
Table 1-2. X32 Audio Interface Pinout
Pin NumberNameDescriptionInterface
1GNDGroundPower
2GNDGroundPower
3UART RXUART RX, receive to MCU from DBUART
4UART CTSUART Clear to sendUART
5UART TXUART TX, transmit from MCU to DBUART
DS70005400A-page 10
Page 11
Development Board Functionality and Features
...........continued
Pin NumberNameDescriptionInterface
6UART RTSUART Ready to sendUART
7I2C SCLClock line for I2C interface.I2C
8STBY/RSTStandby/Reset controlGPIO
9I2C SDAData line for I2C interface.I2C
10Audio WS/LRCLKAudio Word Select/Left Right ClockI2S
11Audio InAudio into MCU, out from CODECI2S
12Audio CLKAudio clockI2S
13Audio outAudio out of MCU, in to CODEC/DACI2S
14REFCLK/MCKReference clock #1REFCLK
15GNDGroundPower
16GNDGroundPower
17NCLegacy hold over-
18+3.3vVDDPower
19NCLegacy hold over-
20+5.0vVDDPower
21 (1)Audio WS/ Audio LRCLKAudio Word Select/Left Right ClockI2S
22 (2)Card ID pinCommunication line to the daughter card and
23 (3)Audio CLKAudio ClockI2S
24 (4)NC
25 (5)Audio INAudio into MCU, out from CODECI2S
26 (6)NC
27 (7)Audio OUTAudio out of MCU, in to CODEC/DACI2S
28 (8)NC
29 (9)REFCLK2/MCK2Reference clock #2REFCLK
30 (10)NC
31 (11)GNDGroundPower
32 (12)GNDGroundPower
1.6.3 Port Connections
The following table provides the port and connections to the X32 Audio interface. The I2S signals listed are the main
signals, and both of these signals are available at each interface, refer to the X32 Interface Block Diagram for
additional information.
The mikroBUS interface allows for the use of additional click™ boards. For additional information and to see the
boards which can be used with this development board, refer to: https://www.mikroe.com/.
Table 1-4. mikroBUS™ Pinout
Development Board Functionality and Features
InterfaceX32#1X32#2
UART RTSRPE8RPF5
UART CTSRPF12RPD10
I2C SDARA3RA3
I2C SCLRA2RA2
ResetRJ12RJ10
REFCLKRPD15RPD15
I2S ClockRPD1RPG6
I2S Audio Out (MOSI)RPD7RPG8
I2S Audio In (MISO)RPD14RPG7
I2S LRCLKRPD9RPC2
Pin NumberNameFunction
1GNDGround
2+5V+5.0V
3SDAI2C SDA
4SCLI2C SCL
5TXUART TX
6RXUART RX
7INTInterrupt request line
8PWMPulse width modulation
9GNDGround
10+3.3VGround
11MOSIMaster Out Slave In line of serial peripheral interface.
12MISOMaster In Slave Out line of serial peripheral interface.
13SCKClock for serial peripheral interface
14CSChip Select for serial peripheral interface. (Active low)
15RSTReset
16ANAnalog-to-digital converter.
1.7.1 Port Connections
The following table provides the port connections to the mikroBUS interface. The mikroBUS is nested inside of the
X32 Audio interface. Due to mechanical interference, either a mikroBUS or Audio interface can be used in the same
socket. The mikroBUS interface shares signals with the X32 Audio interface, refer to Pinout for additional information
on pinout or signal probing.
Table 1-5. Port Connections for the mikroBUS Interface
InterfacemikroBUS™ #1mikroBUS™ #2
UART RXRPC4RPE9
UART TXRPC1RPG9
INT/IRQRPF12RPD10
I2C SDARA3RA3
I2C SCLRA2RA2
ResetRJ12RJ10
PWMRPD15RPD15
SPI ClockRPD1RPG6
SPI MOSIRPD7RPG8
SPI MISORPD14RPG7
SPI SSRPD9RPC2
ADCAN5AN6
1.8 Control Area Network (CAN) Bus Interface
The Curiosity PIC32MZ EF 2.0 Development Board provides access to a CAN interface that is post transceiver. The
on-board CAN transceiver is an ATA6561, which allows the application to be used directly with any CAN bus
compliant interface.
Table 1-6. CAN Bus Interface
Pin NumberNameDescriptionPort
1CAN_HCAN High Signal-
2GNDGround-
3CAN_LCAN Low Signal-
-CAN2_TXCAN TransmitRPD5
-CAN2_RXCAN ReceiveRPF5
1.9 Ethernet
The Curiosity PIC32MZ EF 2.0 Development Board has a modular Ethernet PHY system that enables different PHYs
to be plugged into the board. This interface is set up to use a Reduced Media-Independent Interface (RMII interface)
and a SPI bus interface with GPIO.
23 (11)CSChip Select for serial peripheral interfaceRH3
24 (12)SCKClock for serial peripheral interfaceRB14
25 -30EGNDShield Ground-
1.10 Xplained Pro Extension Standard Header
The Curiosity PIC32MZ EF 2.0 Development Board has an Xplained Pro extension compatible interface that enables
using the existing extension boards. This interface consists of a dual row, 20-pin, 100 mil, 90 degree extension male
header. Xplained Pro extensions have their female counterparts. The extension headers can be used to connect a
variety of Xplained Pro extension boards or to access the pins of the target MCU directly. All connected pins follow
the defined pinout description as shown in the following table.
Note: All pins are not always connected.
Table 1-8. Interface Pinout
Pin
number
1IDCommunication line to the ID chip on an extension
2GNDGround-
3ADC(+)Analog-to-digital converter, alternatively positive part of
4ADC(-)Analog-to-digital converter, alternatively negative part of
5GPIO1General purpose I/ORK4
6GPIO2General purpose I/ORK5
7PWM(+)Pulse width modulation, alternatively positive part of
8PWM(-)Pulse width modulation, alternatively negative part of
9IRQ/INT/GPIOInterrupt request line and/or general purpose I/ORK0
10SPI SS B/GPIOSPI Slave Select or General purpose I/ORK6
11I2C SDAData line for I2C interface. Always implemented, bus
12I2C SCLClock line for I2C interface. Always implemented, bus
14UART TXTransmitter line of target device UART.RPF4
15SPI SS A/GPIOSPI Slave Select or General purpose I/ORPB15
NameDescriptionPort
16SPI MOSIMaster Out Slave In line of serial peripheral interface.
Always implemented, bus type.
17SPI MISOMaster In Slave Out line of serial peripheral interface.
Always implemented, bus type.
18SPI SCKClock for serial peripheral interface. Always
implemented, bus type
19GNDGround-
20VCCPower for extension boards (3.3V)-
Figure 1-10. Pinout Schematic
RPB3
RPB5
RPB14
1.11 Graphics Connector/GFX Card Interface
The Curiosity PIC32MZ EF 2.0 Development Board has a new graphics interface that enables using different
graphics cards to support different graphics models.
Table 1-9. Graphics Pinout
Pin NumberNameDescriptionPort
1GNDGround-
2GNDGround-
3MCLRMaster Clear, controlled by the debuggers. allows
for a complete system reboot
4IRQ1 (LCD Touch)Interrupt request line for cap touch deviceRD0
55.0V VCC5.0V-
6IRQ2 (Q Touch)Interrupt request line for Q touch devicesRH9
The Curiosity PIC32MZ EF 2.0 Development Board offers several user buttons and LEDs. Some of the LEDs can be
used with PWM (Output Compare). The following table shows the function, description and the port on the MCU.
Table 1-10. Functions for Buttons and LEDs
FunctionDescriptionTypePort
SW1Users switchInputRJ4
SW2Users switchInputRJ5
SW3Users switchInputRJ6
SW4Users switchInputRC15
RESETHard reset of the PIC32Input-
LED1User programmable LED. Single colorGPIO OutputRJ7
LED2User programmable LED. Single colorGPIO OutputRK7
LED3User programmable LED. Single colorGPIO OutputRJ3
LED4 (Red)RGB LED Red channelGPIO or PWMRPB7 or OC8
Development Board Functionality and Features
LED4 (Green) RGB LED Green ChannelGPIO or PWMRPB8 or OC5
LED4 (Blue)REB LED Blue ChannelGPIO or PWMRPB9 or OC3
1.13 USB
The Curiosity PIC32MZ EF 2.0 Development Board has a high-speed USB 2.0 connection for user application. This
port can act as either a device class or host class.
For Device class, use the USB cable which can be plugged into the target USB. Refer to 1.1 Board Feature Location
for additional information.
For host device class operation, a USB OTG cable is needed. To enable power from the Curiosity PIC32MZ EF 2.0
Development Board, the user must control the VBUS Enable pin. The Curiosity PIC32MZ EF 2.0 Development Board
must be powered through an external source, Vin, PKoB4, or barrel jack.
Table 1-11. VBUS Enable Pin Description
FunctionDescriptionPort
VBUS EnableEnable power control to USB devices attached to the Curiosity PIC32MZ EF
Microchip provides online support via our web site at http://www.microchip.com/. This web site is used as a means to
make files and information easily available to customers. Accessible by using your favorite Internet browser, the web
site contains the following information:
• 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 (FAQ), technical support requests, online discussion
groups, Microchip consultant 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
Customer Change Notification Service
Microchip’s customer notification service helps keep customers current on Microchip products. Subscribers will
receive e-mail notification whenever there are changes, updates, revisions or errata related to a specified product
family or development tool of interest.
To register, access the Microchip web site at http://www.microchip.com/. Under “Support”, click on “Customer Change
Notification” and follow the registration instructions.
Customer Support
Users of Microchip products can receive assistance through several channels:
• Distributor or Representative
• Local Sales Office
• Field Application Engineer (FAE)
• Technical Support
Customers should contact their distributor, representative or Field Application Engineer (FAE) for support. Local sales
offices are also available to help customers. A listing of sales offices and locations is included in the back of this
document.
Technical support is available through the web site at: http://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 specification contained in their particular Microchip Data Sheet.
• Microchip believes that its family of products is one of the most secure families of its kind on the market today,
when used in the intended manner and under normal conditions.
• There are dishonest and possibly illegal methods used to breach the code protection feature. All of these
methods, to our knowledge, require using the Microchip products in a manner outside the operating
specifications contained in Microchip’s Data Sheets. Most likely, the person doing so is engaged in theft of
intellectual property.
• Microchip is willing to work with the customer who is concerned about the integrity of their code.
• Neither Microchip nor any other semiconductor manufacturer can guarantee the security of their code. Code
protection does not mean that we are guaranteeing the product as “unbreakable.”
Code protection is constantly evolving. We at Microchip are committed to continuously improving the code 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.
Information contained in this publication 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. 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 ITS CONDITION, QUALITY, PERFORMANCE, MERCHANTABILITY OR
FITNESS FOR PURPOSE. Microchip disclaims all liability arising from this information and its use. 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, AnyRate, AVR, AVR logo, AVR Freaks, BitCloud, chipKIT, chipKIT
logo, CryptoMemory, CryptoRF, dsPIC, FlashFlex, flexPWR, Heldo, JukeBlox, KeeLoq, Kleer, LANCheck, LINK MD,
maXStylus, maXTouch, MediaLB, megaAVR, MOST, MOST logo, MPLAB, OptoLyzer, PIC, picoPower, PICSTART,
PIC32 logo, Prochip Designer, QTouch, SAM-BA, SpyNIC, SST, SST Logo, SuperFlash, tinyAVR, UNI/O, and
XMEGA are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
ClockWorks, The Embedded Control Solutions Company, EtherSynch, Hyper Speed Control, HyperLight Load,
IntelliMOS, mTouch, Precision Edge, and Quiet-Wire 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, 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, motorBench, 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.
Silicon Storage Technology is a registered trademark 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.
2019, Microchip Technology Incorporated, Printed in the U.S.A., All Rights Reserved.
ISBN: 978-1-5224-4834-1
Quality Management System Certified by DNV
ISO/TS 16949
Microchip received ISO/TS-16949:2009 certification for its worldwide headquarters, design and wafer fabrication
facilities in Chandler and Tempe, Arizona; Gresham, Oregon and design centers in California and India. The
Company’s quality system processes and procedures are for its PIC® MCUs and dsPIC® DSCs, KEELOQ® code
hopping devices, Serial EEPROMs, microperipherals, nonvolatile memory and analog products. In addition,
Microchip’s quality system for the design and manufacture of development systems is ISO 9001:2000 certified.
2355 West Chandler Blvd.
Chandler, AZ 85224-6199
Tel: 480-792-7200
Fax: 480-792-7277
Technical Support:
http://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