Hi Matt, Kiste,
On 12.03.14 01:14, mattschinkel wrote:
How about for any PIC that has a different sample type?
On 12.03.14 09:04, Oliver Seitz wrote:
Well, I can't be more specific than this: I hardly ever use anything
else than the internal oscillator. I could do without all of the _hs
samples, replacing them by _intosc.
Two 2 blink samples per PIC would mean more than 1000 samples, and my
concern is 'not see the wood for the trees'.
In my view the main purposes of the blink-a-led samples are:
- Show how to setup a program with Jallib device files,
especially how to specify fuse_defs
(and oscillator-related registers in case of INTOSC).
- Prove that you can obtain a working program with the
provided device files (and the whole Jallib package).
I use the blink samples to validate the device files, so
I need at least 1 sample per PIC, but it is not absolutely
necessary to publish each sample!
It seems overdone to me to provide both a HS and an INTOSC blink sample
for every PIC. I think that 1 pair of samples for each group of PICs (=
PICs in the same datasheet) is sufficient, since the samples of other
PICs of that group will be (almost) identical.
The only difficulty I see with this grouping is that a (new) user might
have difficulty to find a proper blink sample for 'his' specific PIC
when he is not aware of the population of the groups. (which might be
solved with a list or a pointer to the datasheet wikis which show the
groups).
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/d/optout.
