Access Official Technical PDF

Share Summary:LinkedInEmail

For engineers developing embedded control hardware, a development board can make it easier to test firmware and circuit behavior before integrating a design into a larger system. The Curiosity Development Board is a PIC MCU development board for Microchip 8-, 14- and 20-pin 8-bit microcontrollers. Used with MPLAB X IDE, it supports programming and in-circuit debugging while providing access to common inputs, indicators and expansion connections.

Its value lies in combining a socketed MCU, flexible pin access and several power options on one platform. Understanding how those elements are configured—and how programming depends on the MCU’s configuration bits—helps teams move from an initial firmware build to reliable bench testing.

Curiosity Development Board features for PIC MCU prototyping

The board’s MCU socket accommodates supported PIC devices in 8-, 14- and 20-pin packages. Dual-row expansion headers provide connections to MCU pins, while an application header includes ground and supply connections. This arrangement gives developers a way to connect external circuitry and observe how firmware interacts with hardware.

For basic application testing, the board includes indicator LEDs, push-button switches, an mTouch button and a variable potentiometer. These components can support simple input and output tests without requiring a separate circuit for every early-stage experiment. The board also includes a mikroBUS footprint for compatible Click boards and a footprint for an RN4020 Bluetooth Low Energy module.

Connections are designed with flexibility in mind. Zero-ohm resistors are placed in series with connections such as the mikroBUS interface, touch input and LEDs. Where the circuit design allows, these resistors can be removed to change routing without cutting PCB traces. Check the board schematic and relevant module documentation before making a modification, and confirm that the chosen pin assignments do not conflict.

Power options and jumper configuration

The board can be powered in three ways. The correct choice depends on the setup, and the J12 jumper arrangement matters when using the board’s standard USB or 9V input paths.

  • USB through J2: USB power can supply the board. A shunt jumper on J12 selects the board’s 5V or 3.3V supply connection, according to the jumper position.
  • 9V external supply through J15: The on-board regulator circuitry provides the supply rails. J12 is used to select the appropriate voltage connection.
  • Variable external supply through TP3 and TP4: An external supply can be applied directly to VDD. In this configuration, the guide states that a shunt jumper on J12 is not required.

Before powering the board, confirm the selected supply, jumper position and target MCU’s voltage requirements. When troubleshooting a board that does not start, the status LEDs can help narrow down the issue: the guide recommends checking USB host power if D1 is off, and checking J12’s connection to the intended device voltage if D2 is off.

Programming and debugging with MPLAB X IDE

The Curiosity Development Board connects to a computer through its USB connector and works with MPLAB X IDE. In the IDE, the on-board PICkit On-Board (PKOB) interface provides programming and low-voltage in-circuit debugging for supported devices. Debugging allows a developer to run, stop and single-step through firmware, use breakpoints, reset the processor, and examine or modify register contents when execution is stopped.

The setup process begins by connecting the board over USB and opening or creating a project in MPLAB X. In the project properties, select the Curiosity entry under “Starter Kits (PKOB),” then choose the target device and the XC8 compiler version being used. Under the Starter Kit (PKOB) program options, enable Low-Voltage Programming if it is not already selected. After applying the settings, use the IDE’s Make and Program Device command to build and program the project.

Why the LVP configuration bit matters

PKOB programming relies on low-voltage programming. The target PIC’s configuration words must therefore have the Low-Voltage Programming bit enabled (LVP = ON, or 1). If custom firmware clears this bit, the on-board programmer may not be able to program the device. A PIC previously programmed with high-voltage programming and LVP disabled may likewise not be recognized by PKOB.

In that situation, the guide describes two recovery paths: use a PICkit 3 programmer with the appropriate MPLAB configuration and set LVP to 1 in the configuration word, or use a blank device configured for low-voltage programming. If a PICkit 3 will not program the MCU, check that the J12 3.3/5V jumper has been removed.

Expansion modules and practical limitations

The RN4020 BLE module requires configuration before use. The guide describes configuring it through a UART-to-USB bridge and terminal program, or through custom firmware running on the PIC MCU. It also notes that the RN4020’s Wake_HW line must be connected for proper BLE functionality; consult the module’s command reference for configuration details.

The RN4020 and a Click module cannot both use the shared UART TX and RX lines to communicate with the PIC at the same time. This is an important integration constraint when planning an application that combines wireless communication with a UART-based expansion module. During debug mode, LED D5 is unavailable to the user because of the board’s debugging arrangement; the associated series resistor can be removed if a different connection is needed.

Putting the board to work

The Curiosity Development Board is most useful when treated as a configurable firmware and hardware test platform rather than a finished application circuit. Its socket, headers, basic input and output components, expansion footprints and multiple power paths give teams options for evaluating supported PIC MCUs and connected circuitry. Successful use depends on matching the power arrangement to the setup, selecting the correct device and tool settings in MPLAB X, and keeping the LVP configuration consistent with the programming method.

For industrial automation engineers and system integrators, these checks provide a practical foundation for early embedded-control development. Confirm supply and pin routing before connecting external hardware, account for shared interfaces when selecting modules, and verify configuration bits when programming fails. These habits help make bench testing more systematic before firmware and circuitry move into a larger control design.

Access Official Technical PDF

About The Author