>Bob Axtell wrote:
> > DIY electronics plans to have its K128 Programmer doing DsPICs within a
> > month.
>
>I plan to have it within a week
>
> > Lord what a programming algorithm...

Olin replied.

>Argh.  Don't get me started.  All the ambiguities and some errors in the
>programming spec don't help either.  It took trial and error to get most
>things working.  The spec can only be considered a hint.
>
>At this point I've got all reading and writing of program and data memory
>working, and have only a few additions to the high level host code left to
>do.  This has taken waaaaay longer than I expected based on experience with
>other PICs.

At least you have the "d" revision to work with.

When I added dsPIC support I had to hand check every opcode in the STDP 
algorithm. There  seemed to be an
op-code error on every page (or is that still the case...)

I cannot believe it took microchip four goes to even get the config bit map 
correct!

Anyway, I don't know if anyone is even using the WARP-13 for dsPIC support. 
I only ever heard from one
person who was having problems and I never got an update from him when I 
enquired for more info.

I know that it worked as far as getting the executive programmed and 
running correctly and it cross check ok
when I tested with a ICD2 .  That is a far as I played with it.

Personally, I think it is all a bit dubious anyway as anyone who is serious 
about developing with the dsPIC really is
going to need a ICD.  Offering someone a programmer so they don't get an 
ICD would be a bit of a disservice
in many cases.

Of course if  the programmer offers some substantial other benefit then 
having both would be a good idea.

Regards,

Jim









subject=Re:[PIC:] DsPIC programmer
source= http://www.piclist.com/piclist/2005/02/16/140626a.txt

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist