William Chops Westfield wrote :

> 1) i would sort of think that learning about "quirks" would be an
> important part of a 'serious' "intro to embedded programming"

Yes, if they was general in nature (common to any MCU family, not
only PICs).

No, if you mean design flaws in *some* PICs specificaly.

There is no reason to start with showing all the things that
make people switch to *other* MCU families, are there ?

> 2) Once you decide to go to a new, non-quirky 28 or 40 pin
> chip without
> all the hobbyist history of the 16F series, are you still sure
> you want to use a PIC?  I mean, there are LOTS of $10 40pin
> flash microcontrollers.  (hmm.  Aside from the expense of
> tools, I wonder if a 'comparative religionxxxxx I mean
> microcontroller" class where you implement the same project
> on several different chips would be more beneficial than an
> in-depth study of one particular chip...)

It's not going to be in-depth, even if *only* using PICs.

It's ment as an introduction and to show that there are
other things "out there" then HTML, JavaScript and PHP...

(I'm also discussion on setting up an OpenVMS environment there
to show that there actualy exists *good* operating systems, not
only those comming from Microsoft... But that's another story
for another mail-list... :-) )

Jan-Erik.

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics