gnupic: Re: [gnupic] PICkit2


Previous by date: 4 Sep 2008 09:50:04 -0000 Re: [gnupic] PICkit2, Xiaofan Chen
Next by date: 4 Sep 2008 09:50:04 -0000 Re: [gnupic] PICkit2, Tom Schouten
Previous in thread: 4 Sep 2008 09:50:04 -0000 Re: [gnupic] PICkit2, Xiaofan Chen
Next in thread: 4 Sep 2008 09:50:04 -0000 Re: [gnupic] PICkit2, Tom Schouten

Subject: Re: [gnupic] PICkit2
From: "Xiaofan Chen" ####@####.####
Date: 4 Sep 2008 09:50:04 -0000
Message-Id: <a276da400809040249k70ea290fu3b58d90ef8c23ff0@mail.gmail.com>

On Thu, Sep 4, 2008 at 6:23 AM, Tom Schouten ####@####.#### wrote:
>> I do not know of any restricts on the hardware side. However, it would
>> be a lot of work to rewrite the firmware and host software.
>
> I didn't look at the scripts in the .dat yet, but if they don't use any
> hard-to-port opcodes (like direct access to the SFRs on the PK2) it should
> not be so incredibly difficult to reuse the scripts and implement just
> what is necessary for a certain range of chips. i'm thinking the USBprog
> AVR here.. and thinking (dreaming) it might be an interesting excercise for
> a portable Staapl application, targeting PIC18 and AVR).

Many scripts are specifically for PIC programming. You can get a
much detailed output of the content of the dat file by running
Jeff's software dat2text which outputs text file with info about
all families, devices, and scripts in Microchip's PK2DeviceFile.dat file.
http://home.pacbell.net/theposts/picmicro/

Xiaofan

Previous by date: 4 Sep 2008 09:50:04 -0000 Re: [gnupic] PICkit2, Xiaofan Chen
Next by date: 4 Sep 2008 09:50:04 -0000 Re: [gnupic] PICkit2, Tom Schouten
Previous in thread: 4 Sep 2008 09:50:04 -0000 Re: [gnupic] PICkit2, Xiaofan Chen
Next in thread: 4 Sep 2008 09:50:04 -0000 Re: [gnupic] PICkit2, Tom Schouten


Powered by ezmlm-browse 0.20.