Maybe I am a bit biased but I think JDM type of programmer
(or any programmer without a PIC on it) may be not a
good enough programmer.

To me it may be worth more effort to extend Wisp628/EasyProg
to program more chips (including dsPIC). Even though Wouter 
and Olin may not want to do it for good reasons, the protocol
and the firmware are both open. They tend to be more stable
than JDM type across different computers.

I also quite doubt the assertion that you can port a Windows
console app within one day when dealing with hardware access
but I am not a PC programmer.

Xiaofan

-----Original Message-----
From: Byron A Jeff [mailto:byron@cc.gatech.edu]
Sent: Tuesday, May 31, 2005 12:58 AM
To: Microcontroller discussion list - Public.
Subject: Re: [PIC] Programming the dsPIC (newbie)

...
The programmer isn't the issue. It seems to be the same serial programming
interface, just in a different spot on the chip. So if you do ICSP it should
be no problem from the hardware side.
...
Another tool you'll need is port access. A DLL that's helpful in this
regard is the inpout32.dll for Windows. You can find it here:
http://www.logix4u.net/inpout32.htm
It loads a kernel driver to interface to I/O ports.

Between the two it's probably less than a day's work to get a working
windows console app that will drive your JDM.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist