Skip to main content
Topic: Difference between PIC code in firmware vs piratePICprog? (Read 2892 times) previous topic - next topic

Difference between PIC code in firmware vs piratePICprog?

Hi all,

I see there is some PIC programming code baked into the Bus Pirate firmware here:

https://code.google.com/p/the-bus-pirat ... urce/pic.c

What is it used for? What is the difference between that and piratePICprog? From what I understand, the PIC adapter is needed to allow the Bus Pirate to program PICs, and piratePICprog is used to send the adapter commands. I don't see any reference of the Bus Pirate being able to program PICs on it's own in the documentation.

Thanks!

Re: Difference between PIC code in firmware vs piratePICprog

Reply #1
As I remember that code is obsolete, we use binwire.c with piratePICprog as I know.

You are right, there is no documentation about PIC programming capability under wiki. That is probably it is still a work in progress, people add their favorite PIC uC's definitions to piratePICprog and then test it. If it works we are able to program one more uC.

The programming adapter is needed for PICs that require a Vpp of about 13V which are 10F, 12F, 16F and 18F series. 24F series and dsPICs need a lower Vpp that the Bus Pirate can supply by itself. More info about using it is in here: http://dangerousprototypes.com/docs/Pir ... Programmer

To understand the operation, try reading binwire.c in Bus Pirate firmware and the codes over here: http://code.google.com/p/dangerous-prot ... 2Fsoftware Most important ones you need are buspirate.c and pic*.c files.

Re: Difference between PIC code in firmware vs piratePICprog

Reply #2
Thanks tayken! I will take a look at binwire.c and the related pic c files.