You complained about the quality of code available at piclist.com, and specified what you would rather see. I explained why the code on the site is as it is and put out a plea for you and others to improve and expand it (hopefully as you had suggested). How, exactly, is that missing the point? You are correct that concentrating on basic, complete, debugged, tool like code would be ideal. I am trying to make it possible for anyone who has or takes the time to do that to share the result. Please post your improved code to the list and to the site. James Newton, PICList Admin #3 mailto:jamesnewton@piclist.com 1-619-652-0593 phone http://www.piclist.com ----- Original Message ----- From: Dan Michaels To: Sent: Wednesday, July 04, 2001 09:17 Subject: Re: [PIC]: [WANTED]: I2C Open-Source Tool James, you missed the entire point of my argument. At 09:09 AM 7/4/01 -0700, you wrote: >Beggars can't be chooses Dan. I (we) don't have the money to pay for donated >code and I (we) don't always have time to write new code just for fun. I do >make the time to post to the site what code I write or find that may be of >use. It only take a few seconds to go to >http://www.piclist.com/techref/microchip/routines.htm >login, browse to a good page, then use the form to select "Add a [public] >[link], enter a short description and "optional link to" pagename.htm (where >pagename is the file name of your program. e.g. snipp.htm) then press the >Add button. This creates a new page which you can now go to, and using the >same form select "Add a [public] [program listing]" paste your code into the >text box (leave "optional link" blank) and press the Add button. > >SHAZAM! new code on its own page at piclist.com with credit to you. > >I do anything I can to add to the available code base at piclist.com. I >agree that more complete, better tested programs would be great. I just now >(literally) got on my knees and I am begging you (or anyone) to expand on >Tony's snipp.asm to make it a complete (and tested) program. > >It doesn't grow without help. > >--- >James Newton (PICList Admin #3) >mailto:jamesnewton@piclist.com 1-619-652-0593 >PIC/PICList FAQ: http://www.piclist.com or .org > >-----Original Message----- >From: pic microcontroller discussion list >[mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Dan Michaels >Sent: Wednesday, July 04, 2001 08:53 >To: PICLIST@MITVMA.MIT.EDU >Subject: Re: [PIC]: [WANTED]: I2C Open-Source Tool > > >Simon-Thijs de Feber wrote: >>Look at this : >> >>http://www.lancos.com/prog.html >> > > >Simon, thanks for the pointer. This is a very nice full-featured >commercial programmer, but not quite what I was after, which was >just a little "free" tool that I could download into a PIC in 2 >minutes and use immediately one time. > >I checked the snipp.asm code on piclist.com from Tony Kubek. It >is clearly professionally written code and very nice, but also >not what I need. It accesses internal EEPROM rather than external, >has empty RS232 routines, and there is no indication is has ever >been verified independently. Basically it is a code fragment >and not a "tool". I was hoping no to have to build my own tool, >rather to find something working and already proven. > >You know, in retrospect, I wonder whether the piclist community >hasn't totally gone off in the wrong direction here. Instead of >offering disembodied code segments and pushing for open-source >universal programmers which entail months and months of work, >maybe we would be better served if we concentrated on the >following: > >1 - "Complete" running example programs for ALL the standard PIC > controllers that would contain a good mix of the common operations > - interrupts, RS232, A/D, I2C, timer fcns, command processing, > etc. This would really make it easy for newbies to get into > any PIC of their choice. Download a completely working source > file, assemble, program and go - rather than grab a bunch of > disembodied code fragments written in several different dialects. > >2 - "Tools" - small, complete, and verified utility programs that > perform certain targeted functions, like I2C and SPI EEPROM > read/write, RS232 comms at all baud rates to test links, > programs to exercise/test proto h.w., etc. These tools could > be offered as both source and/or hex, and people could download > them and program into a PIC and have them running in a matter > of minutes. They would only need be available for about 3 cpus > - '84, '873/876, '877 - covering major pinouts. They would have > already been verified by others, and known to work properly. > >We seem to have both ends of the spectrum discussed a lot on >piclist, but where is the middle ground? Maybe it's here somewhere >and I haven't found it. > >[still looking for an I2C tool]. > >best regards, >- dan michaels >www.oricomtech.com >======================== > >-- >http://www.piclist.com#nomail Going offline? Don't AutoReply us! >email listserv@mitvma.mit.edu with SET PICList DIGEST in the body > >-- >http://www.piclist.com#nomail Going offline? Don't AutoReply us! >email listserv@mitvma.mit.edu with SET PICList DIGEST in the body > > > > -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body