[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
picp improvements
From: Andrew Pines ####@####.#### Date: 14 Apr 2000 16:59:40 -0000 Message-Id: <38F74C2E.E74E1B0D@cosmodog.com> Hi, all, I've been receiving word of a number of issues with picp (for programming PICs using the PicStart Plus). I'm going to try to address as many of them as I can but I'd like to get a little feedback from anyone I haven't already heard from first. I never use it for anything other than 16c505's so I don't get a good sense of what works and what doesn't other than through user feedback (I only found out yesterday that flash erase of data space may not work as advertised). Things I'd like to know about: 1) parts that are listed as supported but don't seem to work properly 2) parts that are not listed as supported but should be (e.g., new parts that MPLAB now supports) 3) parts that DO work as expected, so I can maintain a list of known working parts 4) specific features that don't work as expected 5) bad experiences building on a particular platform (please provide details) Thanks. -Andrew -- Andrew Pines ####@####.#### http://www.cosmodog.com | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |