Hi Seb,
On 03/25/10 12:35 pm, Sebastien Lelong wrote:
If user says "set_analog_pin(5), then
it should act on pin AN5 (not RA5 for instance). The question now is:
what if there's no AN5 pin?
Due to an little error in the Dev2Jal script some of the latest device
files have JANSEL_ANSx declarations for non-existing ADC channels. That
is not too bad, unless you check on defined(JANSEL_ANSx) and not on
defined(pin_ANx). BTW my error was in this check!
While testing my fix I noticed a 'peculiarity'. The device file of the
16F913 has a JANSEL_ANS4, but when looking in the datasheet, I saw no
AN4 in Table2! So I thought it was an eeror in pinmap.py.
Looking a little further I saw that the QFN package (Table 3) does have
an AN4! This is strange, since all are 28 pins packages. However on the
Pin Diagram all packages have an AN4 pin! So I assume this is an error
in Table2 of the datasheet.
It seems unlikely to me that the different packages have different
electronics (for example more active ADC channels). But it could be that
44-pin QFN packages have more active pins than their 40 PDIP
counterparts. Or am I seeing ghosts?
Can anybody say more about this hardware issue (and preferrrably assure
me that different packages have the same electronics)?
Regards, Rob
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
