>Date: Sat, 28 Dec 1996 23:06:35 -0600 >To: uttl@ols.net >From: Jim Robertson >Subject: Re: Picstart 16B1 Firmware Replacment > >At 08:00 PM 12/27/96 -0800, you wrote: >>I hadn't seen any reviews on this yet so I thought I'd comment on this >> >>for anybody interested. >> >> >> >>I downloaded and installed the Phoenix firmware that replaces the >>Microchip firmware on the PicStart 16B1 programmer. While it is still >>in a beta release, I'm impressed with the cabability that Jim and his >>organazation has done with it. While it's still rough around the edges >>as far as the user interface, it goes far beyond what the original >>firmware did. I've tried most of the 16C6X and 16C7X family on it as >>well as the 16C84.. Whoops, I guess that's the 16F84 now... and all >>parts appears to program and verify fine. >> >> >> >>Give it a look if you need everything a 16B1 and 16C1 wanted to be for >>Christmas.... >> >>and didn't want to shell out for a PicStart Plus. >> >> >>http://www.labyrinth.net.au/~newfound/ > > Jim and his organization??? Oh, that must be me and my Dog! :-) Thanks for the feedback. This is exactly what I want. I need to know that it works as far as the serial communications go. If I know the serial stuff is ok, then I can proceed and tidy up the package. One person so far said he couldn't get it communicating properly. I have had a few good reports in private email but until the communication is proven, there is no point in passing on these comments. Oh, while I'm here, let me remind people _again_ that the 28-pin "skinny DIP" parts (16C62/63/72/73 etc) are NOT to be placed in the picstart 16B on-board ZIF socket. Sure they fit, sure the upgrade will program them BUT THEY STILL DON'T GO IN THAT SOCKET! A few people have over looked this and reported it as a problem to me. I'm more concerned with those who haven't and have abandoned the upgrade believing it to be at fault. Please wire up the adapter as described on my web page. See the phoenix mailing list letter #1. Jim (and his dog) :-)