PDA

View Full Version : Cheap programmer with modern low voltage PIC support?



CuriousOne
- 4th August 2014, 16:31
Hello.

I have DIY K-149 USB programmer, which is great, but can't support low voltage PICs, such as 16F887 or 16F1503. I need a cheap programmer that can support these chips and allow fuse config (pickit 3 does not allow).

Any ideas?

towlerg
- 4th August 2014, 20:41
Pickit2 clone or the real thing. The clone is considerable cheaper.

CuriousOne
- 5th August 2014, 09:55
I have genuine Pickit 2. It does not allows to set fuses in the meaningful way.

Pista1
- 5th August 2014, 11:25
Hello CuriousOne:

I would like to clarify the question: Low voltage chips, meaning LF version(3.3V max Vdd) or low voltage programmable chips which do not use the usual 14V reset on MCLR to go into programming mode? Although I always include the __config setup into the program, I recall that I did config setup changes with PICkit2 standalone programmer just before the program was loaded. This even works when you use the MPLAB just to load the HEX file into the chip, quite a few clicks though. I use PICkit3 in case of 12LF1840 which my PICkit 2 does not support. By the way does anyone know where the upgrade for extended chip list can be downloaded for standalone PICkit 2 like the PIC LF chips? There are references that this exists but I cannot seem to find it.
Steve

CuriousOne
- 5th August 2014, 12:14
Thanks.

I meant the newer chips, like 16F1507.

For the Pickit 2, you can change the config, but it is in the way like address, byte, you have to remember that say at 93H is TRISIO config stored and so on. While the MicroBRN (The software that comes with K-149 programmer, has the direct checkboxes, so you can config MCLR, OSC, etc, etc in direct way).

towlerg
- 5th August 2014, 14:07
I have genuine Pickit 2. It does not allows to set fuses in the meaningful way.

Why use a programmer to set fuses? Life is much easier if you set the fuses in the source of your program. Thus avoiding mistakes and making it much easier to revisit a project without having to remember what fuses you set.

George

towlerg
- 5th August 2014, 15:26
You don't have to use the command line tool. I leave the GUI version running in the background and either select the .HEX file manually or rely on the automatic detect and compile function.

The GUI version supports the PIC you want to use.

Given the utility of the PicKit2 (logic analyzer, UART tool and debugger) and the price, it's not a purchase you are likely to regret.

If you google around you will find tools to add devices to both versions and example device files again for both versions.

George

CuriousOne
- 5th August 2014, 15:50
I use programmer to set fuses because this is way I've used to do and I prefer to less waste time on changing knowledge, and focus more on tasks to be solved.