Montaigne, Mike - NRC wrote:
>Tks Dan,
>
>As mentioned, I went and 'bought' my "Complete" running example programs,
>for the 84 series, because that was the quickest and perhaps only way I
>could find to 'jump in'.
>
>The problem is not lack of information, it's just that it's not accessible.
>
>It would be great if the piclist community could respond....If Microchip
>responded (ant they have already with demo boards, application notes etc.,
>they just haven't taken it far enough) it would be very smart marketing.
>

Hi Mike,

I am re-posting your original msg here. There has been a definite
lack of response on piclist - regarding the "merits" of what I
suggested, but who knows .......

- dan
=================

MIKE'S ORIGINAL MSG:

   I have some limited experience with the 16F84 but need to do a project with
   the 12C67X chip and I am trying to find some simple examples of code to help
   me get started.  I have searched Microchip and the web and last years
   messages from this news group but have not learned the secret of finding
   programs relating to a specific processor line yet.  If anyone can help me
   get started, it would be greatly appreciated.  I have started trying to
   write a program to read pin 7 (A-D value between 0-5V) and output either the
   upper 4 or lower 4 bits on pins 2, 3, 5, & 6 using pin 4 as an upper/lower
   selection input.  I thought this would give me a good start learning how to
   set up I/O with the chip.  I'll worry about interrupts, timers, EPROM etc..
   later.


>
>> ----------
>> From:        Dan Michaels[SMTP:oricom@USWEST.NET]
>> Reply To:    pic microcontroller discussion list
>> Sent:        Thursday July 05, 2001 9:07 AM
>> To:  PICLIST@MITVMA.MIT.EDU
>> Subject:     Re: 'hole' in PIC information available
>>
>> Montaigne, Mike - NRC wrote:
>> >I posted a basic question recently re: request for sample programs for
>> the
>> >12CE67X processor.  Getting no sample programs from the newsgroup, I
>> asked
>> >Microchip for some help and got some excellent assistance to get me
>> started
>> >from support person Brent Walters.
>> >
>> >> I would like to make a comment.  With the 'tons' of information
>> available
>> >> on the PIC, it is very frustrating to me to be unable to get what I
>> think
>> >> should be simple information without having to do what I did - go and
>> >> bother Bret Walters with a question I should have been able to find out
>> >> for myself.
>> ...........
>>
>>
>> Mike, you make a very good point. It is partly in response to your
>> observations that I recently posted the suggestions that I did
>> - repeated below.
>>
>> best regards,
>> - dan michaels
>> www.oricomtech.com
>> =========================
>>
>> PART OF ORIGINAL FOLLOWS:
>>
>> .............
>> 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.
>> ........

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu