On 19/06/2021 10.36, Rob CJ wrote:
A first analysis. The adc_clock.jal library calculates the optimal
converstion time (Tad). It does this only for ADC_ADCS_BITCOUNT with
values 2 and 3 but for the 16f18857 this value is 1 and so the library
generates the error message.
Maybe Rob Hamerling can shine a light on this since he created that
library.
Long time ago! It has always been a primary goal in Jallib to build
libraries which would work for all PICs. We succeeded in most cases, but
for ADC it was by far the most challenging because of the large
variations of ADC implementations between PICs. But that was about 10
years ago. With the availability of newer PICs the variations have only
become larger. But the ADC libraries haven't followed these
developments, complexity being one of the main reasons, 'retirement' of
some of the developers like me another. Today I follow the Jallib
developments passively at considerable distance!
A pragmatic approach for users of JalV2 users might be to forget the
current ADC libraries for PICs which are apparently not supported and
develop code specific for that PIC following the instructions in its
datasheet. I did that myself for the 10F222....
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/29edbe61-8e5d-6266-1c90-651d4670540a%40gmail.com.
