gnupic: Re: [gnupic] RE: [PIC] gputils-mplab
Subject:
Re: [gnupic] RE: [PIC] gputils-mplab
From:
Craig Franklin ####@####.####
Date:
3 Oct 2005 01:28:26 +0100
Message-Id: <43407BB4.9000606@users.sourceforge.net>
Chen Xiao Fan wrote:
>Thanks for the clarification. I guess Microchip will
>probably not answer my question regarding the plug-in. ;-(
>
>
>
They have always been helpful when I asked them in the past.
>Actually I am quite curious about how you write
>gputils-mplab. The specifications of the .mtc and .ini
>file inside the plug-in directory are not published to the
>public by Microchip. I assume it is only given to some
>leading third party tool vendors. I could be wrong though.
>
>C:\Program Files\Microchip\MPLAB IDE\Core\MTC Suites
>
>
>
Send them a request, they will send the documents. I have them, but I
wasn't given permission to redistribute.
>The latest plug-ins from Hi-Tech is in dll format.
>For example, the following is the batch file from
>HiTech PICC18.
>
>@echo off
>regsvr32 "C:\HTSOFT\PIC18\Suite_HITECH18.dll"
>
>I again assume that the format of the dll file is missing
>from Microchip.
>
>
>
Actually we are using the wrong terminology. Microchip provides two
interfaces for third party tools. The MTC/INI is really simple. Create
a couple of text files and make some registry entries and it works. The
other Microchip calls their "plugin" interface. You sign an NDA and
they provide documentation about internal interfaces. The plugin is
contained in dlls. It gives you the most flexibility, but requires more
work.
I wasn't willing to sign an NDA, so I created the MTC/INI based
gputils-mplab.
>Anyway the tool suite plug-in is not really that important
>for the use of gpasm. It is nice to have but not
>essential. A simple makefile and a nice text editor
>can do the job.
>
>The more important plug-in is to let third-party programmers
>(or debuggers if there is any cheaper ones) to be plugged into
>MPLAB, for example, let xwisp2 be used inside MPLAB as an
>alternative programmer.
>
>C:\Program Files\Microchip\MPLAB IDE\PICkit\MPPICkit.dll
>is an example of such a plug-in (for PICkit 1). Again the
>specification of such dll is missing from Microchip.
>
>All in all, the above plug-ins are not so important than
>the on-chip debug specifications and the communication protocol
>(programming and debugging) of ICD2 to the public.
>
>With gputils/gpsim/sdcc getting better and better and
>open source programmers like JDM/WISP628/PICkit2, the only
>missing tool is an open source hardware debugger which
>support PIC16/18/dsPIC ...
>
>Regards,
>Xiaofan
>
>---------------------------
>welcome to pickit-devel project
>Linux program to work with PICkit 1/2
>http://groups.google.com/group/pickit-devel/
>---------------------------
>
>-----Original Message-----
>From: Craig Franklin
>Sent: Thursday, September 29, 2005 1:13 PM
>To: ####@####.####
>Subject: Re: [gnupic] RE: [PIC] gputils-mplab
>
>That behavior is completely controlled by MPLAB. It is not a
>gputils-mplab bug. Ask Microchip, if you figure out the answer,
>please post it to this list.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: ####@####.####
>For additional commands, e-mail: ####@####.####
>
>
>
>
