---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id ADB6138E01FA; Sun, 01 Feb 2004 16:45:42 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <18.00CC81C0@cherry.ease.lsoft.com>; 1 Feb 2004 19:45:34 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 6062 for PICLIST@MITVMA.MIT.EDU; Sun, 1 Feb 2004 19:45:25 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 8495; Sun, 1 Feb 2004 19:44:57 -0500 Received: from ALPHA6.ITS.MONASH.EDU.AU [130.194.1.25] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Sun, 01 Feb 2004 19:44:56 EST X-Comment: mitvma.mit.edu: Mail was sent by ALPHA6.ITS.MONASH.EDU.AU Received: from localhost ([130.194.13.84]) by vaxc.its.monash.edu.au (PMDF V6.1 #39306) with ESMTP id <01L64E1GAYEK9356OY@vaxc.its.monash.edu.au> for PICLIST@MITVMA.MIT.EDU; Mon, 02 Feb 2004 09:34:05 +1100 Received: from blammo.its.monash.edu.au (localhost.its.monash.edu.au [127.0.0.1]) by localhost (Postfix) with ESMTP id 4EA3139C004 for ; Mon, 02 Feb 2004 09:34:05 +1100 (EST) Received: from eng.monash.edu.au (civ-tnixon.eng.monash.edu.au [130.194.129.127]) by blammo.its.monash.edu.au (Postfix) with ESMTP id 1892A2DC014 for ; Mon, 02 Feb 2004 09:34:05 +1100 (EST) MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en, en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 References: <401B4B02.4050009@yahoo.com> <401B6405.52A61AB@3mtmp.com> <401BD4F5.6040401@yahoo.com> <401BF795.9182021E@3mtmp.com> <401C8548.7010203@yahoo.com> Message-ID: <401D7EDD.1020501@eng.monash.edu.au> Date: Mon, 2 Feb 2004 09:34:05 +1100 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Tony Nixon Organization: Dept of Civil Engineering - Monash University Subject: Re: [PIC:] K128 USB Programmer. What's wrong? GOT IT To: PICLIST@MITVMA.MIT.EDU In-Reply-To: <401C8548.7010203@yahoo.com> Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856791 Bob Axtell wrote: > Thanks Josh, and to everyone who has helped me. The K128 is really cute, > rugged, and well-designed. Its now working properly. > Hi Bob, Glad you got it working. The major problem has been that some vendors were unknowingly giving out kits with early versions of the firmware. These chips, unfortunately, did not match the later version of the PC program. As I understand it, all previous software packages are available from the KitsRus web site, so I have proposed that firmware chips be marked after programming with the matching PC version. This should make it easy to get a kit going and upgrade to the latest. The kit protocols changed slightly because of the growing differences in programing algorithms from all the new PIC chips coming out. Programmers were quite easy to maintain in times not long past, as most algorithms were the same. Nowadays, with ever increasing chip functionality, there are more and more changes to the programming specs, some very minor in similar families and difficult to spot. Even the LVP pin positions vary across the new 18 pin chips, which is making a reasonably simple and useful single socket programmer impossible to build without multiplexing the pins as in the Picstart+ approach. I guess, and to quote Ned Kelly's famous words, "Such is life". The FTDI driver information changes from time to time so it becomes a large task to monitor this and maintain any upgraded docs in the kits. It seemed wiser just to point out that the latest install info is available from the FTDI site. best regards Tony -- http://www.piclist.com hint: PICList Posts must start with ONE topic: [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads .