Skip to the content
2 layersPicArd, the printed circuit board in 3D

An Ultra Low Cost PIC programmer with Arduino Uno/Nano (hardware + software)

Copper layers
2
Thickness
1.6 mm
Parts
31
Nets
44
Pads
101
Tracks, vias
147, 0
Pours
1
Routed
Yes
KiCad
KiCad 9.0 (file 20241229)
Created
20 Dec 2023
Updated
29 Oct 2026

Overview

PicArd is an open-source printed circuit board by NelsonBittencourt, from the NelsonBittencourt/PicArd repository on GitHub, published under the MIT licence. It is a 2-layer board with 31 parts on 44 nets, routed with 147 tracks and 0 vias.

Its parts include 14 resistors, 7 transistors, 4 capacitors, 3 diodes and 1 connector. It belongs with the interfaces and adapters boards and the AVR (ATmega, ATtiny) and PIC boards of this library.

README

README.md

PicArd - Ultra-Low Cost PIC Programmer

Table of Contents

A) Intro

As my projects became increasingly complex (and required more discrete components), I decided to migrate several of them from "discrete" electronics to microcontrollers.

During this transition, I evaluated various microcontroller families available and I selected PICs because they are easy to find, cost-effective and meet my requirements.

To keep my projects as low-cost as possible (and also as a personal challenge), I made two decisions: a) to purchase some PIC12F675s (the cheapest here in Brazil) and some PIC16F819s and b) to build my own PIC programmer!

Thus, the PicArd (PIC + Arduino) Project was born!

PicArd IS:

  • a full USB programmer for PIC microcontrollers;
  • composed by PC software, Arduino software and extremely simple and cheap hardware;
  • able to run in Windows and Linux;
  • able to use High Voltage Programming (HVP) and Low Voltage Programming (LVP);
  • script oriented (and based on PICkit 2 Interface Guide from Microchip);
  • capable of select between three voltages (5.0V, 3.3V and 2.7V) and
  • PicKit independent (you don't need to have one of them to extract firmware).

PicArd ISN'T:

  • a debugger for PIC microcontrollers;
  • able of performing all PicKit's functions;
  • capable of handle PIC32, EEPROM and KEELOQ families and
  • able to program device via ENHANCED ICSP (programming executive).
Important note:

As reported by wocard2, the voltage on ICSP pins of current hardware is 5 V. This voltage is not suitable for PICs whose maximum operating voltage is below 5 V

$\color{red}{\textbf{Carefully check the operating voltage of your PIC to avoid potential damage!}}$

A new hardware revison with level shifters is under development and will resolve the mismatch between 5 V and lower voltages.

B) PicArd Hardware

The PicArd Hardware consists of:

  1. Arduino UNO R3 (with ATMEGA328PU 32-lead TQFP);
  2. DC-DC step-up (boost) converter;
  3. Programming voltage (VPP) control and
  4. Microcontroller power supply voltage (VDD) control.

Don't be intimidated by this list! It looks very complex (except for the Arduino, perhaps), but to assemble everything, I only used seven bipolar junction transistors (BC547s and BC557s) and few passive components. Check out the breadboard:



Figure 1a. PicArd Breadboard


If you prefer, you can assemble the PicArd Programmer as a shield. Figure 1b shows a rendered image of the Arduino Uno Shield that I created.



Figure 1b. PicArd Arduino Uno Shield


Important: For new projects, always use PicArd Programmer Hardware Revision 2 and the latest software versions (>= 0.45).

Gerber files for the fabrication of this shield are available in Uno Shield folder.

B.1) Arduino Uno R3

The following figure shows Arduino Uno R3 connections to PicArd:



Figure 2. Arduino UNO R3 Connections


My Arduino R3 clone board has a ATMEGA328PU in a TQFP package. The pin numbers above refer to this package. If your Arduino has another package, consider making connections using identifications into the brackets (PCB silk screen) or the full pin name (e.g. PORT0).

The connections between Arduino R3 and PicArd are:

Table 1. Labels Descriptions

LabelDescription
5VPositive 5 V (remember, Arduino needs to be connected to PC USB)
3V3Positive 3.3 V (from Arduino Uno)
PWMPWM signal for DC/DC boost converter
PWM_FBPWM voltage feedback
VDD_ONOFFTurns on/off VDD to device
VPP_ONOFFTurns on/off VPP to device
VDD_5.0VSelect/Unselect 5.0 V as VDD
VDD_3.3VSelect/Unselect 3.3 V as VDD
VDD_2.7VSelect/Unselect 2.7 V as VDD
ICSP_DATAIn-circuit serial programming (ICSP) data pin
ICSP_CLOCKICSP clock pin
ICSP_AUXICSP for Low Voltage Programming (LVP)
VDDSelected VDD
VDD_DEVICEDevice VDD Pin
VPPProgramming voltage
VPP_DEVICEDevice VPP Pin
GNDGround

B.2) DC-DC Boost Converter

DC-DC boost converter is responsible for raising voltage from 5 V to programming voltage (VPP) required by PICs. This module is optional if you intend to use only PICs that support LVP.

I designed this circuit to operate with VPPs between 2 V and 13 V.



Figure 3. DC/DC booster


PWM signal from Arduino controls Q4 through R1 and C2 (capacitor added to improve switching speed). L1, D2 and C1 completes basic DC/DC boost circuitry. A voltage divider (R2 and R3) is used apply a secure voltage (<=5.0V) to PWM_FB pin. As an additional precaution, I added D1 (5.1V zener diode).

B.3) Voltages Control

The PICs' supply voltages (VDD) can range from 2.7 V to 5.0 V. Since the Arduino Uno has voltage regulators for 3.3 V and 5.0 V, I used the circuit below to allow the selection of the correct voltage. By controlling pins D02 (VDD_5.0V), D03 (VDD_3.3V), and D04 (VDD_2.7V), we can obtain 5.0 V, 3.3 V, and approximately 2.7V, which covers almost all devices.

This approach eliminates the necessity of a Low Dropout Regulator (LDO), reducing the project cost.



Figure 4. VDD Selection Control


VPP (from DC/DC converter) and VDD (from above circuit) must be applied to PIC at specific times. Therefore, Arduino needs to send VPP_ONOFF and VDD_ONOFF signals to control when PIC will receive this voltages.

The circuit below shows my solution:



Figure 5. Voltages Control


VPP_DEVICE and VDD_DEVICE must be applied to PIC's correspondent pins.

B.4) Connection Examples

Connecting PicArd to PIC microcontrollers is pretty simple, just follow Microchip's programming specifications.

The figures below show two connection examples:

B.4.1) PicArd to PIC12F675


Figure 6. PicArd connected to PIC12F675


Each PIC microcontroller family has its own programming specifications. For PIC12F675 in the example above, see: PIC12F629/675 Memory Programming Specification

B.4.2) PicArd to PIC16F819


Figure 7. PicArd connected to PIC16F819


This example follows PIC16F818/819 Memory Programming Specification.

B.5) Full Schematics

The link below contains all the schematic diagrams we have seen so far (I also included a page with typical voltage and signal values):

Full schematic PDF


C) PicArd Software

PicArd requires two sets of code:

C.1) Arduino software (firmware) main functions:

  • Control and monitor PicArd's hardware voltages (voltages on/off, PWM, etc);
  • Send/receive serial data to/from the connected PIC and
  • Send/receive information to/from PC via USB port.

Arduino software must be uploaded to Arduino Uno R3. Download it from Release section

C.2) PC Software:

PicArd PC software has two flavors: GUI or console. Both have been compiled for Windows and Linux, and their functions are:

  • Parse device database;
  • Parse '.hex' files provided by user;
  • Backup OSCCAL, bandgap and configuration words to avoid data loss and
  • Send/receive information to/from Arduino via USB port.

As of version 0.45, PC applications also handle Calibration Words. Because I had previously created two additional record types to the Intel HEX standard (06 for BandGaps and 07 for OSCCALs), I decided to call the input file format as Picard Hex Files (.pchx).

For further details and examples regarding this format, refer to pchx format.

Warning 1: Database file (pic_devices.dat) must be in the same folder that PicArd executable.

Warning 2: From version 0.45 onwards, the picard.ini file must be provided. See further details about this file in C.2.1 or C.2.2.

Warning 3: In Linux, ensure that your user has read and write access to USB devices.

Download PicArd's PC software in Releases section.

C.2.1) GUI

GUI version consists of a single main window, as shown in Figure 8.It is self-explanatory.



Figure 8. PicArd GUI Main Window


This version generates two log files (in the executable directory):

First one is osccals_bandgaps.txt, which will save the OSCCALs, BandGaps and Calibration Words values every time a device is read. This information is useful to avoid losing factory calibration data for certain PICs.

The second file, picard.log, logs the steps executed by the application to help identify potential errors.

Some features have not yet been implemented, such as "Save PCHx file".

PicArd GUI files are named picard_gui_<version_number>_windows.zip and picard_gui_<version_number>_linux.zip.

From version 0.45 onwards, the picard.ini file must be provided. Although this file is included in every package in the release folder, it must be modified by the user before launching the application.

The picard.ini sintax is:

text
last_usb:none
last_device:none
voltage_divider_top_resistor:0
voltage_divider_bottom_resistor:0
programming_voltage_stability_check:0

last_usb and last_device (GUI only) can be left as "none".

voltage_divider_top_resistor and voltage_divider_bottom_resistor represent the values of resistors R2 and R3 in the boost converter feedback voltage divider (Figure 3). Measure the actual values of your circuit and enter them as integers in this file.

For example, my prototype had R2 = 4074.9 ohms and R3 = 2675.1 ohms. The picard.ini is:

text
last_usb:none
last_device:none
voltage_divider_top_resistor:4705
voltage_divider_bottom_resistor:2675
programming_voltage_stability_check:0

When programming_voltage_stability_check is enabled (value 1), the Picard Hardware waits for the boost converter's output voltage to stabilize. This feature worked well in my experiments, but some people did not achieve good results (see Issue #1 ,Portuguese only).

C.2.2) Console Application:

Starting with version 0.45, I decided to simplify the commands for PicArd console version.

If, for some reason, you continue using the old versions, simply type picard.exe or ./picard to see the syntax.

The picard.ini file must also be used for the console version. Here a example for this file in console application directory:

text
voltage_divider_top_resistor:4705
voltage_divider_bottom_resistor:2675
programming_voltage_stability_check:0

Replace the values above with your measured values.

Command line sintax:
text
picard -c <serial port> -d <device name> [-r output_file] [-w hex_file]

where:

text
Usage examples

Example 1: Verify if PIC12F675 exist in database (pic_device.dat):

text
picard -d PIC12F675

PicArd 0.45 - PIC Programmer using Arduino UNO
Nelson Rossi Bittencourt - https://github.com/nelsonbittencourt/picard

Device found
Device name : PIC12F675
Device ID   : 4032 (fc0)
Family name : Midrange/Standard
LVP support : No
Nothing to do!

Example 2: Read a PIC12F675 (Arduino on COM3) to file pic_output.pchx

text
picard -c COM3 -d PIC12F675 -r pic_output.pchx

PicArd 0.45 - PIC Programmer using Arduino UNO
Nelson Rossi Bittencourt - https://github.com/nelsonbittencourt/picard

Device found
Name        : PIC12F675
ID          : 4032 (fc0)
Family      : Midrange/Standard
LVP support : No

Programmer booted.
VDD setted to: 5V
Programming entry mode: HVP
Setting VPP to : 12V

Reading device configuration:
Reading Device ID: Ok [fc0]
Reading User IDs: Ok
To avoid errors or calibration lost, PicArd will save OSCCAL, BandGap and Calibration Word(s) into osccals_bandgaps.txt.
Feel free to write down values to reduce data loss probability.
Reading OSCCAL : Ok [3460]
Reading Configuration Word(s): Ok
Reading Program Memory: Ok

For PIC read operations, the console version of PicArd will save the read data in .pchx format.

Example 3: Send hex data (program.hex) from PC to PIC12F675:

text
picard -c COM3 -d PIC12F675 -w program.hex

Will send all necessary data (program data, EEPROM data, configuration words, etc) to device.

PicArd Console files are named picard_console_<version_number>_windows.zip and picard_console_<version_number>_linux.zip.

C.3) Script based (PC and Arduino software):

PicArd is based on the same scripts and code used in the PicKit2. These scripts, as well as the device information, are stored in the pic_devices.dat file. I have utilized the file bravely maintained and updated by Jaka and Anobium.

If you want to support Anobium's efforts in device file, consider buying PICkitPlus software.

My goal was to implement all the script codes contained in the "PICkit 2 Interface Guide" to allow the programming of largest number of devices possible. Studying the scripts and datasheets, I decided to leave out PIC32, KEELOQ, and EEPROM models. Furthermore, I was unable to read all the datasheets and could not test all devices.

If your device utilizes a script whose code is implemented in PicArd, there is a good chance that it can be read/programmed by the application. However, this is not guaranteed...

Below are the codes that I have already implemented and those that still need to be implemented:

C.3.1) Implemented script commands

Table 2. Implemented script codes

CodeFunction/MnemonicArduino Uno Label / Comments
0xFFVDD ONVDD_ONOFF / Turns on PNP transistor (Q3); Device VDD = VDD
0xFEVDD OFFVDD_ONOFF / Turns off PNP transistor (Q3); Device VDD = 0V
0xFDVDD GND ONVDD_ONOFF / Implemented as 0xFE
0xFCVDD GND OFFVDD_ONFF / Implemented as 0xFF
0xFBVPP ONVPP_ONOFF / Turns on NPN/PNP pair (Q1 and Q2); Device VPP = VPP
0xFAVPP OFFVPP_ONOFF / Turns off NPN/PNP pair (Q1 and Q2); Device VPP = VPP
0xF9VPP PWM ONMapped only. Not necessary (PWM always on in HVP mode)
0xF8VPP PWM OFFMapped only. Not necessary (PWM always on in HVP mode)
0xF7MCLR GND ONMapped only. (VPP pull-down resistor)
0xF6MCLR GND OFFMapped only. (VPP pull-down resistor)
0xF5Busy led onArduino built-in LED turns on
0xF4Busy led offArduino built-in LED turns off
0xF3Set ICSP PinsICSP_DATA (D05) and ICSP_CLOCK (D06)
0xF2Write byte literal-
0xF1Write byte buffer-
0xF0Read byte buffer-
0xEFRead byte-
0xEEWrite bits literal-
0xEDWrite bits buffer-
0xECRead bits buffer-
0xEBRead bits-
0xE9Loop-
0xE8Delay long-
0xE7Delay short-
0xE6If equal gotoImplemented, not tested
0xE5If greater gotoImplemented, not tested
0xE4Goto index-
0xE3Exit scriptMapped only. Not used
0xDDLoop buffer-
0xDBPop download-
0xDACOREINST18-
0xD9COREINST24Not tested
0xD8NOP24Not tested
0xD7VISI24Not tested
0xD6RD2_BYTE_BUFFERImplemented as 0xF0. Not tested
0xD5RD2_BITs_BUFFERImplemented as 0xEC. Not tested
0xD4WRITE_BUFWORD_WNot tested
0xD3WRITE_BUFBYTE_WNot tested
0xD2WRITE_BUFBYTE_WNot tested
0xD1CONST_WRITE_DLNot tested
0xCFSet AuxICSP_AUX (D07)
C.3.2) Not implemented script commands

Table 3. Not implemented script codes

CodeFunction/MnemonicComments
0xEASet ICSP speedPC-Arduino Uno communication at constant speed (19200 bauds)
0xE2Peek SFRNot found in pic_devices.dat file
0xE1Poke SFRNot found in pic_devices.dat file
0xE0ICDSLAVE_RXOnly for debug scripts
0xDFICDSLAVE_TX_LITOnly for debug scripts
0xDEICDSLAVE_TX_BUFOnly for debug scripts
0xDCICSP_STATES_BUFFEROnly for debug scripts
0xD1WRITE_BITS_LIT_HLD33CK_ChpErasePrep only
0XD0WRITE_BITS_BUF_HLDHCS only
0xCEAux State BufferNot found in pic_devices.dat file
0xC8 to 0xCDI2C commandsNot used in PicArd
0xC3 to 0xC7SPI commandsNot used in PicArd
0xC0 to 0xC2ICDSLAVE debug commandsOnly for debug scripts
0xB3 to 0xBCJT2 commandsNot used in PicArd
0xBFMEASURE_PULSENot used in PicArd
0xBEUNIO_TXEEPROMs only
0xBDUNIO_TX_RXEEPROMs only

D) Tested Devices

Table 4. Tested Devices

DeviceTestersNotes
PIC10F322@wocard2
PIC12F1572@wocard2 and @lalo-uy
PIC12F1822@wocard2
PIC12F1840@wocard2
PIC12F508@wocard2Device without ID. Read ID skipped by software
PIC12F629@girardim
PIC12F675@NelsonBittencourt
PIC16C84@lalo-uy
PIC16F13145@wocard2
PIC16F1454@wocard2
PIC16F18324@wocard2HVP only. Internal VPP pull-up too strong
PIC16F19156@wocard2
PIC16F1938@girardim
PIC16F819@NelsonBittencourt
PIC16F886@girardim and @lalo-uy
PIC18F14K50@wocard2HVP only. Internal VPP pull-up too strong

E) Contact

Personal site:

https://nrbenergia.azurewebsites.net/

or

http://www.nrbenergia.somee.com/

LinkedIn:

https://www.linkedin.com/in/nelsonrossibittencourt/

Parts

31
QtyValueFootprintReferences
52N5401Package_TO_SOT_THT:TO-92_Inline_WideQ2, Q3, Q4, Q6, Q7
310kResistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P10.16mm_HorizontalR10, R12, R13
32k2Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P10.16mm_HorizontalR5, R6, R7
34k7Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P10.16mm_HorizontalR3, R9, R14
2100kResistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P10.16mm_HorizontalR8, R11
22N5551Package_TO_SOT_THT:TO-92_Inline_WideQ1, Q5
1100nCapacitor_THT:C_Axial_L3.8mm_D2.6mm_P7.50mm_HorizontalC2
11N4148Diode_THT:D_DO-35_SOD27_P7.62mm_HorizontalD3
11N5231Diode_THT:D_DO-201_P15.24mm_HorizontalD2
11N5817Diode_THT:D_DO-41_SOD81_P10.16mm_HorizontalD1
11k2Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P10.16mm_HorizontalR2
11nCapacitor_THT:C_Axial_L3.8mm_D2.6mm_P7.50mm_HorizontalC3
12k8Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P10.16mm_HorizontalR4
12m2Inductor_THT:L_Axial_L5.0mm_D3.6mm_P10.00mm_Horizontal_Murata_BL01RN1A2A2L1
1470uCapacitor_THT:CP_Radial_D10.0mm_P5.00mmC1
147uCapacitor_THT:CP_Radial_D5.0mm_P2.50mmC4
156Resistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P10.16mm_HorizontalR1
1Arduino_Nano_v3.xModule:Arduino_NanoA1
1Conn_01x06_PinConnector_PinHeader_2.54mm:PinHeader_1x06_P2.54mm_VerticalJ1

Similar boards

  • 2 layers44.5 × 46.9 mmOSO SWAT B1-jig, the printed circuit board in 3D

    OSO SWAT B1-jig

    joeycastillo/Sensor-Watch

    A board replacement for the classic Casio F-91W wristwatch

    31 parts2.1k
  • 2 layers65 × 30 mmRgb to hdmi, the printed circuit board in 3D

    Rgb to hdmi

    hoglet67/RGBtoHDMI

    Bare-metal Raspberry Pi project that provides pixel-perfect sampling of Retro Computer RGB/YUV video and conversion to HDMI

    31 parts1kGPL-3.0
  • 2 layers191 × 98.5 mmMacroKeypad, the printed circuit board in 3D

    MacroKeypad

    hackclub/OnBoard

    💡 Join 1,000 teenagers and make your first PCB with a $100 grant!

    31 parts915
  • 2 layers39 × 45.2 mmCH32V003F4P6-R0-1v1, the printed circuit board in 3D

    CH32V003F4P6-R0-1v1

    openwch/ch32v003

    CH32V003 is an ultra-cheap RISC-V MCU with 2KB SRAM, 16KB flash, and up to 18 GPIOs that sells for under $0.10

    31 parts599
  • 2 layers26.7 × 27.9 mmBreakout board, the printed circuit board in 3D

    Breakout board

    Luos-io/luos_engine

    Open-source and real-time orchestrator for cyber-physical-systems, to easily design, test and deploy embedded applications and digital twins.

    31 parts546MIT
  • 2 layers100 × 50 mmPixelix, the printed circuit board in 3D

    Pixelix

    BlueAndi/Pixelix

    Full RGB LED matrix, based on an ESP32 and WS2812B LEDs or emulated LEDs on TFT.

    31 parts447MIT
  • 2 layers77.2 × 69.8 mmCubesatsim solar, the printed circuit board in 3D

    Cubesatsim solar

    alanbjohnston/CubeSatSim

    CubeSatSim, the AMSAT CubeSat Simulator

    31 parts419GPL-3.0
  • 2 layers103 × 55 mmTd neck-294, the printed circuit board in 3D

    Td neck-294

    tdaede/td-crt

    tubes

    31 parts373

Questions

What parts does the PicArd use?

31 parts. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the PicArd KiCad files?

From the NelsonBittencourt/PicArd repository on GitHub, at the commit this page was made from: the board is third_party/lalo_uy/Nano_HW/Picard.kicad_pcb and its schematic third_party/lalo_uy/Nano_HW/Picard.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the PicArd design in my own project?

Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).