The EJTAGproxyproject brings GDB interface for MIPS processors, including PIC32.
However, it currently supports Microchip PICkit2 and PICkit3, but not the chipKIT™ PGM programmer.
I asked the developer about . His answer is the chipKIT PGMprogrammer relies on a proprietary protocol.
Quote
The chipKIT-PGM is basically an OEM version of picKIT3 programmer. Unfortunately, it uses a proprietary protocol, which is pretty complicated, and Microchip has no intention to disclose the details.
Obviously, there is the command-line Microchip Debugger (MDB), but it requires the installation of the full MPLABX and it is not compatible with the standard GDB.
Could the Digilent and chipKIT teams work together on adding the chipKIT PGMprogrammer to the JTAGproxy project?
Question
ReiVilo
The EJTAGproxy project brings GDB interface for MIPS processors, including PIC32.
However, it currently supports Microchip PICkit2 and PICkit3, but not the chipKIT™ PGM programmer.
I asked the developer about . His answer is the chipKIT PGM programmer relies on a proprietary protocol.
Obviously, there is the command-line Microchip Debugger (MDB), but it requires the installation of the full MPLABX and it is not compatible with the standard GDB.
Could the Digilent and chipKIT teams work together on adding the chipKIT PGM programmer to the JTAGproxy project?
Also posted at http://chipkit.net/forum/viewtopic.php?f=17&t=3841
1 answer to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.