It's too bad one has to jump through these various work around hoops
in order to get the job done.

One suggestion to the keyboard/mouse/monitor switch is to use MS
remote desktop (if you have windows XP pro on one machine) or VLC. 
Then you can treat the extra computer as an application on the primary
computer.  Somewhat like using virtual PC, but with two real
computers.

-Adam

On 3/30/06, Bob Axtell <engineer@cotse.net> wrote:
> The ICD2 is so incredibly cranky to make use of.  The
> problem is not so much the hardware as the firmware,
> which provides such cryptic error messages that it is
> almost useless.
>
> Why doesn't Microchip release the debug code for
> the chips so that a USEFUL piece of equipment
> can be designed and sold? There needs to be a
> product priced somewhere in the middle of the range
> ($250-300) that will work properly. The jump from
> ICD2 to the ICE4000 is a jump from $150 to $4000.
>
> Here are my specific complaints:
>
> 1. ONE ICD2 per Host PC is really not enough. I
> am frequently involved in development where more
> than one PIC needs to be developed AT THE SAME
> TIME. Yes, I now use two PC's, and use a switch to
> switch the mouse, keyboard, and video. But there is
> no need to, in fact.
>
> 2. The GROUND system between the ICD2 and the
> unit being developed is too weak. The convenience
> of the RJ12 is overshadowed by its poor ground. At
> the very least, the unused 6th pin should have been
> a second ground pin. A better method is simply a more
> solid connector with more contact surface area.
>
> 3. The error messages are useless. Its ridiculous that
> the ICD2 can't realize that it's device has no clock, for
> example. Or that the error "Can't Enter Debug Mode"
> can't simply say that the debug firmware was never installed
> into the chip... disgraceful.
>
> 4.  The round shape of the ICD2 has no advantage whatever.
> It simply falls off the bench easier.
>
> 5. The USB interface, either the driver, the chip used, or both,
> seems to be inordinately finicky. At least once a day, I have to
> reboot the system to get the USB driver to start working
> again. It might be $MS problems, haven't discussed this with
> anybody using Linux.
>
> 6. Using the DB9, a top speed of 57.6Kb with the FIFO buffer
> disabled is just poor design. It should be able to accept 115kb
> at the very least and make use of the FIFO buffers; this would
> effectively triple the thruput when not using USB. In fact, a
> custom speed of 250Kb should be realistic, although the
> PIC16F877A  will probably have to be replaced with a 40Mhz
> PIC.
>
> Open for flames.
>
> --Bob
>
> --
> Note: To protect our network,
> attachments must be sent to
> attach@engineer.cotse.net .
> 1-520-850-1673 USA/Canada
> http://beam.to/azengineer
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

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