Post by thread:[PIC] I2C development tool for PC

The ICEs don't do programming do they? On 6/16/05, Olin Lathrop <spam_OUTolin_piclistTakeThisOuTembedinc.com> wrote: > Bill Cornutt wrote: > > I went "whole hog" on PIC development system and got the PicKit1. > > If PicKit1 is "whole hog", then what is ICD2, ICE-2000, or ICE-4000? > > ***************************************************************** > Embed Inc, embedded system specialists in Littleton Massachusetts > (978) 742-9014, http://www.embedinc.com > -

Rochester, 16 juni 2005. Dear all, > Chip selection of PICkit 1 is also not that limited after all. > It will support 10F200/202/204/206, 12F508/509/510, > 12F629/675/635/683, 16F505/54/57/59, 16F630/676/684/636/688, > 16F685/687/689/690, 16F627A/628A/648A (tested) and possibly > 16F785, 16F913/914/916/917 and 16F873A/874A/876A/877A > (not tested). It is also cross platform. Just download > Microchip's latest application (on Windows and MacOS X) > and Mark Rages' hack for Linux and MacOS X. I'm a bit of a beginner still, but so far I have enjoyed the El Cheapo ($35.81 in parts, including cable and ZIF sockets) and the JDM ($12.95 ready made, regular sockets, no cable) programmer, which both are nice (I really appreciate the ZIF sockets, though). I am curious about the more "official" solution from Microchip themselves, though. You list quite a large number of PICmicros here, but their website lists: - PIC12F629, 635, 675, 683 - PIC16F630, 636, 676, 684, 688, 785, 916, 917 - PIC12F508, 509, 510 - PIC16F505 And a few more that "require an adapter". As the website also states the PICkit1 is meant for 8/14-pin devices, and some of the device you list (and especially the 16F628A, which I am most interested in) have 18-pins, I was wondering how I should envision this. I would imagine it has something do do with the "in circuit programming" or the adapter... Could you please explain? Would it involve parts above and beyond the $36 that the kit costs? Is there a reason why the 16F88 would not be in the list? Greetings, Maarten Hofman.

So their websites are updated with new informations. V170 Classic from Microchip supports 16F627A/16F628A /16F648A. I have tested the last two chips with no problem. It is supposed to support 16F913/914/ 16F877A as well. But so fat I have no success with 16F877A yet. Mark Rages' program under Linux does not support the 18pin 16F627/628A/629A now. Both program are open source so one can actually add more supports for more chips within the limitation of the firmware (quite a lot of empty space now but nobody likes to work with the 16C745). Actually no special adapter is necessary since you only need ICSP. What you need is soldering 5 wires (almost zero costs) from J3 and link them to your board or the correct pins of your ZIF sockets. The so-called adpater is just doing this for you. Regards, Xiaofan {Original Message removed}

The following is from XWisp2.cfg file shipped with XWsip2. PICkit 1 firmware V2.02 will not support PIC18. It should support PIC10/16/16B. I am not so sure about PIC16A/PIC16D/PIC16C. Therefore I am not so sure about PIC16F87/88 (PIC16D). The best thing about PICKit 1 is that the firmware and the host software are both open-source and the host software is cross platform (Windows, MacOS X and Linux). So those who are interested can look at them and see if it is possible to extend the list of supported chips. ; - 'Algorithm' is the name of the required method of programming to be ; used by XWisp2 and Wisp628 for the PIC. ; Supported algorithms and main characteristics of each method: ; - PIC10 - (12-bits family '10Fxxx', etc. NOT SUPPORTED yet) ; - PIC16 - Write and read all memory regions word-by-word ; (most older midrange flash PICs). ; This is the default for the 14-bits family (12Fxxx/16Fxxx) ; - PIC16A - Write program memory 2 words at a time, read program ; memory word-by-word, ; write and read other memory regions word-by-word. ; 16F7x, 16F7x7, etc. ; - PIC16B - Write 4 words of program memory at a time, ; read program memory word-by-word ; write and read other memory regions word-by-word ; 16F87xA, etc. ; - PIC16C - Write program memory word-by-word, read program ; memory 4 words at a time, ; write and read other memory regions word-by-word. ; - PIC16D - Write and read 4 words of program memory at a time, ; write and read other memory regions word-by-word ; 16F818/9, 16F87/88, etc. ; - PIC18 - Write and read program memory 8 bytes at a time ; (single panel programming), ; write ID memory 8 bytes at a time, read byte-by-byte, ; write and read other memory regions byte-by-byte. ; All 18Fxxxx. ; -----Original Message----- From: Maarten Hofman [.....cashimorKILLspam@spam@gmail.com] Sent: Friday, June 17, 2005 10:09 AM To: Microcontroller discussion list - Public. Subject: Re: [PIC] I2C development tool for PC Is there a reason why the 16F88 would not be in the list?

The following is the list of commands implemented in PICkit 1 firmware version 2.02. Therefore it may not support PIC16A (16F7x7) and PIC16C (no chips?) and PIC16D (16F818/819 and 16F87/F88). Does it mean that it is able to program PIC16D chips but not be able to read (verify) the chips? Please take note that the new 16F91x chips support 8-word (like PIC18), 4-word (like PIC16D) and 1-word (like PIC16) programming mode according to DS41244B. I think it is possible to implement more commands in the firmware. Right now only 2618 out of 8197 program addresses are used (utilization is 31%). The problem is just that not many people would like to work with 16C745 any more (even with the windowed parts). Regards, Xiaofan ; ASCII commands from sent by GUI #define WRITECONFIG A'C' ; Set Program Counter to 0x2000 (Config Mem) #define CMDTABLE A'c' ; Download command table #define WRITEDATA A'D' ; Write data memory #define ERASEPGM A'E' ; Bulk erase program memory #define ERASEDATA A'e' ; Bulk erase data memory #define RECEIVE A'g' ; Get n bytes from flash device #define INCADDRESS A'I' ; Increment address #define ENTERPROGRAMVDD1ST A'O' ; Enter programming mode #define ENTERPROGRAM A'P' ; Enter programming mode #define EXITPROGRAM A'p' ; Exit programming mode #define READPGM A'R' ; Read program memory #define READDATA A'r' ; Read data memory #define CHECKSUM A'S' ; Calculate checksum #define TRANSFER A't' ; Transfer n bytes to flash device #define POWERCTRL A'V' ; Turn Vdd on/off; Turn 5kHz square wave on/off #define GETVERSION A'v' ; Get firmware version number #define WRITEPGM A'W' ; Write program memory #define WRITEPGMEXT A'w' ; Write 1 word to program memory, externally timed #define ABORT A'x' ; Abort current command #define STUFFBYTE A'Z' ; Stuff byte #define WRITE4WORDS A'4' ; Write 4 words to programm memory

Rochester, 17 juni 2005. Dear Xiaofan, > Actually no special adapter is necessary since you > only need ICSP. What you need is soldering 5 wires > (almost zero costs) from J3 and link them to your > board or the correct pins of your ZIF sockets. The > so-called adpater is just doing this for you. So it would cost me an additional ZIF socket and a board to put it on. I agree that the cost is low ($6 at most, maybe) but it is there. Thank you for all the information! I decided that I'm probably better off building the TLVP from Byron A. Jeff. Greetings, Maarten Hofman.

----- Original Message ----- From: "Maarten Hofman" <cashimorKILLspamgmail.com> Subject: Re: [PIC] I2C development tool for PC > So it would cost me an additional ZIF socket and a board to put it on. > I agree that the cost is low ($6 at most, maybe) but it is there. No, no, no. Design your circuit with ICSP in mind. It makes the socket redundant, but the real point is that it makes the development cycle so much more pleasant. Doesn't matter what programmer you choose, resolve to do your very next project using ICSP. I know it's a little scary at first, but it really is terribly easy, and the huge jump in convenience will mean you will never go back. It will also cause you to loose interest in ZIF sockets. Another big advantage that few people mention is that now you can use the surface mount PICs, which means you can get away from drilling all those annoying holes. SOIC PICs and 1206 passives are plenty easy to deal with using traditional soldering techniques, even for an old fart like me, and its a lot more pleasant without all that drilling. --McD

TLVP only supports a few PICs. I think it is also not so safe to use. People have fried their serial or parallel ports on the motherboard using simple circuit like TLVP when hot plugging. Again a PIC programmer without a PIC on it is not worth considering in the long run. People end up spend more time on debugging the programmers than they spend on their project. Regards, Xiaofan {Original Message removed}