MPLAB and my WPR3 programmer

Sonnich Jensen <sonnichjensen@gmail.com> wrote:

>On Nov 8, 3:06=A0pm, n...@puntnl.niks (Nico Coesel) wrote:
>> Sonnich Jensen <sonnichjen...@gmail.com> wrote:
>> >Hi all
>>
>> >I got a programmer named WPR3. It offers to program PIC16 and PIC12,
>> >as well as some cards and EEPROMs.
>> >I only need the PIC part.
>>
>> >It is an older type, which is directly controlled by the parallel
>> >port, a type which should have been common at the time. Though I have
>> >not found much on the net.
>>
>> >My basic problem is that my MPLAB will not use/accept it, and I dont
>> >know where to get drivers, which mode to pick ets. MPLAB by default
>> >offers MPLAB ICD2, MPLAB ICD3, PicKit3, AN851 Quick Programmer Beta
>> >and Real Ice.
>>
>> >I use a labtop with a docking station. My LPT is on the docking
>> >station
>>
>> >Any ideas?
>>
>> MPLAB is an attempt to dumb things down :-)
>>
>> The usual way embedded firmware is developed is to compile & link the
>> program to produce a hex file (there are many formats but Intel and
>> Motorola are most common). This hex file is loaded into the software
>> that comes with a programmer. After that all you need to do is insert
>> the chip in the programmer, select the device from the list with
>> devices the programmer supports and click the 'program' button in the
>> programmer's software.
>
>Well, I still need that software.... :)

Did you try contacting the manufacturer? If you don't have or can't
get the software for your programmer you're better of tossing it in
the bin.

I'm going to buy me one of these:
http://www.ebay.com/itm/160378432470

I only need a programmer about once every two years so this seems like
very good value for money.

-- 
Failure does not prove something is impossible, failure simply
indicates you are not using the right tools...
nico@nctdevpuntnl (punt=.)
--------------------------------------------------------------

On Nov 8, 9:19=A0am, Spehro Pefhany <speffS...@interlogDOTyou.knowwhat>
wrote:
> On Tue, 8 Nov 2011 07:46:49 -0800 (PST), linnix
>
>
>
>
>
>
>
>
>
> <m...@linnix.info-for.us> wrote:
> >On Nov 8, 5:06=A0am, n...@puntnl.niks (Nico Coesel) wrote:
> >> Sonnich Jensen <sonnichjen...@gmail.com> wrote:
> >> >Hi all
>
> >> >I got a programmer named WPR3. It offers to program PIC16 and PIC12,
> >> >as well as some cards and EEPROMs.
> >> >I only need the PIC part.
>
> >> >It is an older type, which is directly controlled by the parallel
> >> >port, a type which should have been common at the time. Though I have
> >> >not found much on the net.
>
> >> >My basic problem is that my MPLAB will not use/accept it, and I dont
> >> >know where to get drivers, which mode to pick ets. MPLAB by default
> >> >offers MPLAB ICD2, MPLAB ICD3, PicKit3, AN851 Quick Programmer Beta
> >> >and Real Ice.
>
> >> >I use a labtop with a docking station. My LPT is on the docking
> >> >station
>
> >> >Any ideas?
>
> >> MPLAB is an attempt to dumb things down :-)
>
> >> The usual way embedded firmware is developed is to compile & link the
> >> program to produce a hex file (there are many formats but Intel and
> >> Motorola are most common). This hex file is loaded into the software
> >> that comes with a programmer. After that all you need to do is insert
> >> the chip in the programmer, select the device from the list with
> >> devices the programmer supports and click the 'program' button in the
> >> programmer's software.
>
> >Problem is that MPLAB needs to talk over the parallel bus. =A0If
> >Microchip did not make that programmer, it's unlikely to have any
> >firmware for it. =A0Even if they did, they are likely to migrate away
> >from it. =A0Of course, you can reverse engineering the protocols and
> >DIY, but it might be cheaper (in time) to buy a Microchip supported
> >programmer.
>
> There is no reason (other than perhaps convenience of initial setup)
> to have a Microchip IDE supported programmer. The IDE (or command line
> tools) output a standard Intel hex file.

But the OP is looking for MPLAB support for his programmer.  With
MPLAB supported programmer, it is more convenient for one click
"compile-build-download-run".

>
> The programmer software eats the hex file and sends it to the
> programmer, over parallel, USB, serial, whatever, which programs the
> chips. As it ever was.

Again, the problem is having the software (MPLAB) to talk over
parallel.

>
> Development is another story, and anyone still doing burn and crash
> development needs to move to more modern methods.

Nico Coesel wrote:

> 
> Did you try contacting the manufacturer? If you don't have or can't
> get the software for your programmer you're better of tossing it in
> the bin.


   He could keep an eye out for the same programmer on Ebay and offer
the seller some cash to copy the software.


-- 
You can't have a sense of humor, if you have no sense.

nico@puntnl.niks (Nico Coesel) wrote:

> I'm going to buy me one of these:
> http://www.ebay.com/itm/160378432470
> 
> I only need a programmer about once every two years so this seems like
> very good value for money.

Thanks very much for the link. I have several but they require a parallel 
or serial port which is getting obsolete. Yours is the first I've seen with 
usb that doesn't cost a small fortune. It also has a very impressive list 
of devices it can handle, and the ones I need are on the list.

It's on order. Thanks!

Mike

Spehro Pefhany wrote:

> Development is another story, and anyone still doing burn and crash
> development needs to move to more modern methods.

+1

--Winston

On a sunny day (Tue, 08 Nov 2011 11:23:45 -0800) it happened Winston
<Winston@BigBrother.net> wrote in <j9bvk20n0h@news4.newsguy.com>:

>Spehro Pefhany wrote:
>
>> Development is another story, and anyone still doing burn and crash
>> development needs to move to more modern methods.

Ridiculous, like saying carry a dictionary around because learning to speak
a language becomes soo complicated with all those new words.
That shitty PIC 16 instruction set is minute compared to even a Z80.
:-)

linnix <me@linnix.info-for.us> wrote:

>On Nov 8, 5:06=A0am, n...@puntnl.niks (Nico Coesel) wrote:
>> Sonnich Jensen <sonnichjen...@gmail.com> wrote:
>> >Hi all
>>
>> >I got a programmer named WPR3. It offers to program PIC16 and PIC12,
>> >as well as some cards and EEPROMs.
>> >I only need the PIC part.
>>
>> >It is an older type, which is directly controlled by the parallel
>> >port, a type which should have been common at the time. Though I have
>> >not found much on the net.
>>
>> >My basic problem is that my MPLAB will not use/accept it, and I dont
>> >know where to get drivers, which mode to pick ets. MPLAB by default
>> >offers MPLAB ICD2, MPLAB ICD3, PicKit3, AN851 Quick Programmer Beta
>> >and Real Ice.
>>
>> >I use a labtop with a docking station. My LPT is on the docking
>> >station
>>
>> >Any ideas?
>>
>> MPLAB is an attempt to dumb things down :-)
>>
>> The usual way embedded firmware is developed is to compile & link the
>> program to produce a hex file (there are many formats but Intel and
>> Motorola are most common). This hex file is loaded into the software
>> that comes with a programmer. After that all you need to do is insert
>> the chip in the programmer, select the device from the list with
>> devices the programmer supports and click the 'program' button in the
>> programmer's software.
>
>Problem is that MPLAB needs to talk over the parallel bus.  If
>Microchip did not make that programmer, it's unlikely to have any
>firmware for it.  Even if they did, they are likely to migrate away
>from it.  Of course, you can reverse engineering the protocols and
>DIY, but it might be cheaper (in time) to buy a Microchip supported
>programmer.

Why bother with something vendor specific? If you talk about a waste
of time... :-) Last time I had to write code for PIC I made a little
wrapper around the Hitech compiler to make it behave like GCC so I
could use Eclipse.

-- 
Failure does not prove something is impossible, failure simply
indicates you are not using the right tools...
nico@nctdevpuntnl (punt=.)
--------------------------------------------------------------

On Nov 8, 1:37=A0pm, n...@puntnl.niks (Nico Coesel) wrote:
> linnix <m...@linnix.info-for.us> wrote:
> >On Nov 8, 5:06=3DA0am, n...@puntnl.niks (Nico Coesel) wrote:
> >> Sonnich Jensen <sonnichjen...@gmail.com> wrote:
> >> >Hi all
>
> >> >I got a programmer named WPR3. It offers to program PIC16 and PIC12,
> >> >as well as some cards and EEPROMs.
> >> >I only need the PIC part.
>
> >> >It is an older type, which is directly controlled by the parallel
> >> >port, a type which should have been common at the time. Though I have
> >> >not found much on the net.
>
> >> >My basic problem is that my MPLAB will not use/accept it, and I dont
> >> >know where to get drivers, which mode to pick ets. MPLAB by default
> >> >offers MPLAB ICD2, MPLAB ICD3, PicKit3, AN851 Quick Programmer Beta
> >> >and Real Ice.
>
> >> >I use a labtop with a docking station. My LPT is on the docking
> >> >station
>
> >> >Any ideas?
>
> >> MPLAB is an attempt to dumb things down :-)
>
> >> The usual way embedded firmware is developed is to compile & link the
> >> program to produce a hex file (there are many formats but Intel and
> >> Motorola are most common). This hex file is loaded into the software
> >> that comes with a programmer. After that all you need to do is insert
> >> the chip in the programmer, select the device from the list with
> >> devices the programmer supports and click the 'program' button in the
> >> programmer's software.
>
> >Problem is that MPLAB needs to talk over the parallel bus. =A0If
> >Microchip did not make that programmer, it's unlikely to have any
> >firmware for it. =A0Even if they did, they are likely to migrate away
> >from it. =A0Of course, you can reverse engineering the protocols and
> >DIY, but it might be cheaper (in time) to buy a Microchip supported
> >programmer.
>
> Why bother with something vendor specific? If you talk about a waste
> of time... :-) Last time I had to write code for PIC I made a little
> wrapper around the Hitech compiler to make it behave like GCC so I
> could use Eclipse.
>

I only use PIC24 and PIC32.  The compiler behaves just like GCC, no
wrapper necessary.  I don't see much differences in programming them
vs. TI/LMI or NXP ARMs.

nico@puntnl.niks (Nico Coesel) wrote:

>Sonnich Jensen <sonnichjensen@gmail.com> wrote:
>
>>On Nov 8, 3:06=A0pm, n...@puntnl.niks (Nico Coesel) wrote:
>>> Sonnich Jensen <sonnichjen...@gmail.com> wrote:
>>> >Hi all
>>>
>>> >I got a programmer named WPR3. It offers to program PIC16 and PIC12,
>>> >as well as some cards and EEPROMs.
>>> >I only need the PIC part.
>>>
>>> >It is an older type, which is directly controlled by the parallel
>>> >port, a type which should have been common at the time. Though I have
>>> >not found much on the net.
>>>
>>> >My basic problem is that my MPLAB will not use/accept it, and I dont
>>> >know where to get drivers, which mode to pick ets. MPLAB by default
>>> >offers MPLAB ICD2, MPLAB ICD3, PicKit3, AN851 Quick Programmer Beta
>>> >and Real Ice.
>>>
>>> >I use a labtop with a docking station. My LPT is on the docking
>>> >station
>>>
>>> >Any ideas?
>>>
>>> MPLAB is an attempt to dumb things down :-)
>>>
>>> The usual way embedded firmware is developed is to compile & link the
>>> program to produce a hex file (there are many formats but Intel and
>>> Motorola are most common). This hex file is loaded into the software
>>> that comes with a programmer. After that all you need to do is insert
>>> the chip in the programmer, select the device from the list with
>>> devices the programmer supports and click the 'program' button in the
>>> programmer's software.
>>
>>Well, I still need that software.... :)
>
>Did you try contacting the manufacturer? If you don't have or can't
>get the software for your programmer you're better of tossing it in
>the bin.
>
>I'm going to buy me one of these:
>http://www.ebay.com/itm/160378432470
>

I received it today and it seems to work. The software is not top
notch (but that seems to be the case for any programmer). OTOH the
software supports automatic serial number and date injection which is
nice.

-- 
Failure does not prove something is impossible, failure simply
indicates you are not using the right tools...
nico@nctdevpuntnl (punt=.)
--------------------------------------------------------------