Re: Bus Pirate PIC 24F Programmer Dev Thread
Reply #38 –
The logic behind using the rawwire binary mode and a PC application for the PIC programmer is that each PIC has quirks, undocumented protocol requirements, etc. Integrating these into a single PIC firmware would take a lot of the space we need for other stuff, especially when v5 is released.
For a long time I swore never to add PIC programming at all, but just a few chips can't hurt, right
We'll get it as fast as we can, but the Bus Pirate PIC programmer will probably end up like the JTAG support - good in a pinch, but pretty slow. And for me, I need a debugger for any real development anyways.
Hopefully, after we stabilize the code a little, someone will port it to a more multi-platform console-app situation.
For new protocols, we've found the best way is to implement the protocol as shown in the documentation, then capture the signals from an ICD2 working with the chip and figure out which parts are undocumented :p