Hi Rob,
On 13/02/2021 12.29, [email protected] wrote:
The blink-a-led-py script generates this samples but will initially
generate a crystal version since that is what it checks as first item
and then it stops. It can also generate the version with the internal
oscillator but that is not done when a HS version is created.
I didn't check the current blink-a-led script, but as far as I remember
after initially generating an HS version for a certain PIC, the script
checks if this PIC is member of a list of PICs for which ALSO a blink
sample with INTOSC and/or a sample for USB must be generated. So all
variants would be generated in one run.
If I change the order to first check for the internal oscillator, a
lot of new blink samples using the internal oscillator are created. It
will then not create the HS version (crystal version).
My questions are:
1) Should we move the priority from HS before internal oscillator to
internal oscillator before HS?
2) Do we still want to keep the HS version if an internal oscillator
version is available or should we remove them? Currently the script
generates one of the two but I could change it to create both.
I would like to suggest to have all possible types of blink-a-led
samples for all PICs and improve the directory structure: a subdirectory
for HS, INTOSC and USB variants of the blink samples and a separate
directory for the other samples (thus 4 sample directories).
Regards, Rob.
--
*Rob H*amerling, Vianen, 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 view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/ca2f7c50-cac1-769b-4553-63f22e79028c%40gmail.com.
