Custom programmer

[Andrew Burchill]

Has anybody tried using microchip's pk2cmd as the custom programmer,
this is what I have managed to use successfully,
piklab from cvs, build 2638.
using PK2CMD V1.20 installed standard.

Read "/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -GFtemp.hex"
Erase "/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -E"
Program "/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -M -FtestDAC.hex"
Verify "/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -Y -FtestDAC.hex"
Blank "/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -C"
Run "/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -W -R"
Stop "/usr/local/bin/pk2cmd -B/usr/share/pk2 -P"

The filename for some reason doesn't need any path info.
The only barrier is having to manually change the hex filename for
each
project, I haven't been able to find anything about passing args to
the
command line, having unsuccessfully scoured the src.
I tried the same as used for custom compiler, $file, $(srcpath) but
still
no go. Any Ideas anyone???

having the device autodetect feature with pk2cmd now, makes this much
easier,
a small loss of time maybe, but acceptable.

also posted this on piklab forum.(http://sourceforge.net/forum/
forum.php?forum_id=633023)
Andrew

[Xiaofan Chen]

On Sat, Feb 28, 2009 at 4:36 PM, Andrew Burchill <dust...@gmail.com> wrote:
>
> Has anybody tried using microchip's pk2cmd as the custom programmer,
> this is what I have managed to use successfully,
> piklab from cvs, build 2638.
> using PK2CMD V1.20 installed standard.
>

> also posted this on piklab forum.(http://sourceforge.net/forum/
> forum.php?forum_id=633023)

I did not notice this thread. Are you trying to use PICkit 2 under
piklab with pk2cmd? In that case, you have to send a feature
request to Piklab project.

Nicolas and I were trying to get PICkit 2 V2 firmware to
work under Piklab some time back but it stopped. It is
still in his to-do list.

On the other hand, you can try Pikdev which does integrate
pk2cmd.
http://pikdev.free.fr/

--
Xiaofan http://mcuee.blogspot.com

[Andrew Burchill]

On Apr 22, 3:11 pm, Xiaofan Chen <xiaof...@gmail.com> wrote:
>
> I did not notice this thread. Are you trying to use PICkit 2 under
> piklab with pk2cmd? In that case, you have to send a feature
> request to Piklab project.
>
> Nicolas and I were trying to get PICkit 2 V2 firmware to
> work under Piklab some time back but it stopped. It is
> still in his to-do list.

I had posted on the piklab forum in sourceforge, nobody seem
interested in this subject tho.

I am successfully using PK2CMD and a Pickit2 as the custom programmer
on the piklab toolbar.
The only hitch being that I haven't found a way to pass arg's from
piklab to the 'custom programmer'
each new project I change the line for uploading firmware to a pic.
eg.
'/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -M -FmV-to-BCD.hex'
gets changed to
'/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -M -Fnew-project.hex'
where I would like to think that piklab could do
'/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -M -F$project'
and it would pass the appropriate hex file to the command line.

I'm not really that good at reading cpp, so after having read through
/home/andrew/temp/build/piklab/piklab2638/src/progs/custom ,
I can't see any reference to passing args to the custom programmer.

But I happy with everything currently, all works fine, using up to
date ubuntu.

AndrewB

[Xiaofan Chen]

On Fri, Apr 24, 2009 at 9:53 AM, Andrew Burchill <dust...@gmail.com> wrote:
> I had posted on the piklab forum in sourceforge, nobody seem
> interested in this subject tho.
>
> I am successfully using PK2CMD and a Pickit2 as the custom programmer
> on the piklab toolbar.
> The only hitch being that I haven't found a way to pass arg's from
> piklab to the 'custom programmer'
> each new project I change the line for uploading firmware to a pic.
> eg.
> '/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -M -FmV-to-BCD.hex'
> gets changed to
> '/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -M -Fnew-project.hex'
> where I would like to think that piklab could do
> '/usr/local/bin/pk2cmd -B/usr/share/pk2 -P -M -F$project'
> and it would pass the appropriate hex file to the command line.
>
> I'm not really that good at reading cpp, so after having read through
> /home/andrew/temp/build/piklab/piklab2638/src/progs/custom ,
> I can't see any reference to passing args to the custom programmer.
>
> But I happy with everything currently, all works fine, using up to
> date ubuntu.

You can probably send the procedure to Nicolas directly. Or if you
prefer, you can send it to me and I will contact Nicolas. As far as I
know, Nicolas is still interested in supporting PICKit 2. And I
am certainly want to see that happen as well. But again I am not
a programmer either myself so I would only be able to carry out
tests but not hacking the codes. He is using QT and KDE which
are too complicated to me...

--
Xiaofan http://mcuee.blogspot.com