Olimex Low-cost programmer / debugger PIC-KIT3 PIC-KIT3 User Manual
Product codes
PIC-KIT3
OLIMEX© 2013
PIC-KIT3 user's manual
CHAPTER 4: FREQUENTLY ASKED QUESTIONS
Q: What USB cable do I need?
A: You should have a USB type A-B cable to connect to PC, all PC USB hosts have USB-A
connector while PIC-KIT3 has USB-B connector so the cable should be USB A-to-B type. Note that
such a cable is not included in the package.
A: You should have a USB type A-B cable to connect to PC, all PC USB hosts have USB-A
connector while PIC-KIT3 has USB-B connector so the cable should be USB A-to-B type. Note that
such a cable is not included in the package.
Q: Does your ICSP connector layout differ from the ICSP connector layout of the original PIC-
KIT3?
A: Yes. This can be easily adjusted by proper mirrored cable. Pay attention to the mirroring of the
cables that the Olimex PIC-KIT3 comes with. Note the layout at the connector also.
KIT3?
A: Yes. This can be easily adjusted by proper mirrored cable. Pay attention to the mirroring of the
cables that the Olimex PIC-KIT3 comes with. Note the layout at the connector also.
Q: What should I know when I connect PIC-KIT3 to a target board?
A: It's very important that your target PIC MCLR is not connected directly to VCC! During the
programming/debugging MCLR goes as high as 13VDC and if your target MCLR is connected
directly to the target's VCC you will blow either the PIC-KIT3 or your target board. Always use
10K pull-up resistor from MCLR to VCC.
A: It's very important that your target PIC MCLR is not connected directly to VCC! During the
programming/debugging MCLR goes as high as 13VDC and if your target MCLR is connected
directly to the target's VCC you will blow either the PIC-KIT3 or your target board. Always use
10K pull-up resistor from MCLR to VCC.
Q: What are the LEDs for?
A: There are two LEDs – one yellow LED named ACTIVE and one double-color (red/green) LED
named STAT . The yellow LED shows USB activity, e.g. when the device is connected to the USB
properly; when you are powering the board from external source via the power jack this LED would
blink. The STAT LED shows RED color when you are connected to MPLAB or the image inside the
flash memory is ready for operation. When there is programming data transferred the double LED
should blink in orange color (red and green).
A: There are two LEDs – one yellow LED named ACTIVE and one double-color (red/green) LED
named STAT . The yellow LED shows USB activity, e.g. when the device is connected to the USB
properly; when you are powering the board from external source via the power jack this LED would
blink. The STAT LED shows RED color when you are connected to MPLAB or the image inside the
flash memory is ready for operation. When there is programming data transferred the double LED
should blink in orange color (red and green).
Q: What voltage should I provide to the power jack for “programmer-to-go” stand alone mode?
A: (6-12) V DC; the inner pin of the connector is the DC
A: (6-12) V DC; the inner pin of the connector is the DC
Q: Hello, I pressed the "programmer-to-go" button and my PIC32 died. What burned my chip?
A: Do not use "programmer-to-go" button when there is no image in the OLIMEX PIC-KIT3 or
MICROCHIP PIC-KIT3 or that might put your microcontroller in an inrecoverable state. We have
tested the mentioned scenario and we can confirm it destroys PIC32 chips (using both our and the
original Microchip PICKIT3). We don't take responsibility if you brick your chip that way.
A: Do not use "programmer-to-go" button when there is no image in the OLIMEX PIC-KIT3 or
MICROCHIP PIC-KIT3 or that might put your microcontroller in an inrecoverable state. We have
tested the mentioned scenario and we can confirm it destroys PIC32 chips (using both our and the
original Microchip PICKIT3). We don't take responsibility if you brick your chip that way.
Q: My PIC16 can not be debugged. Why?
A: Some PIC MCUs might require additional headers to be able to debug them. Always check the
chip's datasheet for hardware requirements.
A: Some PIC MCUs might require additional headers to be able to debug them. Always check the
chip's datasheet for hardware requirements.
Page 12 of 14