Author: robhamerling
Date: Sun Jul 12 12:21:55 2009
New Revision: 1102
Modified:
trunk/doc/html/devicefiles.html
Log:
Just some enhancements...
Modified: trunk/doc/html/devicefiles.html
==============================================================================
--- trunk/doc/html/devicefiles.html (original)
+++ trunk/doc/html/devicefiles.html Sun Jul 12 12:21:55 2009
@@ -419,17 +419,23 @@
var volatile bit JANSEL_ANS9 at ANSELH : 1
var volatile bit JANSEL_ANS8 at ANSELH : 0
</pre>
-Another example for the 10F222:
+As you can see the prefix JANSEL is not restricted to bits 0..7 of ANSEL
+but is also used for channel numbers higher than 7, controlled by
+another register.
+The 16F724 and 16F727 have 21 ADC channels spread over 4 ANSELx
+registers, but these can controlled with the names JANSEL_ANS0 through
+JANSEL_ANS20.
+<p>Another example for the 10F222:
<pre>
var volatile byte ADCON0 at { 0x7 }
var volatile bit JANSEL_ANS1 at ADCON0 : 7
var volatile bit JANSEL_ANS0 at ADCON0 : 6
</pre>
-As you can see here the channel selection bits are in register ADCON0
-(the 10Fs have no ANSEL register), but the ADC library doesn't have
-to know!
-<br><i>Note: in reality the channel selection of the 10F220/222 is
-somewhat more complicated!</i>.
+In this case the channel selection bits are in register ADCON0
+(the 10Fs have no ANSEL register), but the ADC library doesn't need
+to know, because it uses the JANSEL alias.
+<br><i>Note: in reality the channel selection of the 10F220/222 is
+somewhat more complicated, but the ADC library takes care of that!</i>.
<h3>Names of other ADC registers and subfields</h3>
@@ -444,10 +450,10 @@
more than 1 subfield.
For example the 16F7x7s have a 3-bits CHS field plus a single CHS3 bit
to be able to support channel 8 and up.
-In this and similar cases a pseudo variable ADCON_CHS has been declared
+In this and similar cases a pseudo variable ADCONx_CHS has been declared
which takes care of the scattering of channel selection bits.
-So an ADC library can always address ADCONx_CFG as multibit 'binary' field,
-regardless if the bits are scattered over the register or not.
+So an ADC library can always address the variable ADCONx_CHS as multibit
+'binary' field, regardless if the bits are scattered over the register or
not.
<h3>Miscellaneous remarks about names</h3>
@@ -459,7 +465,7 @@
PORT_A_direction, etc.
For individual pins the convention 'pin_Ax' is used.
<li>When you hit compile errors related to undefined names, scan the
- device files to search for 'our' name of the register or port.
+ device files to search for the Jallib name of the register.
</ul>
<h2>About Port Shadowing</h2>
@@ -731,7 +737,7 @@
<h2>Compiler requirements</h2>
-<p>The compiler - at the moment of this writing version 2.4j - has a
+<p>The compiler - at the moment of this writing version 2.4k - has a
number of requirements for device specifications.
The most important from a user perspective are the following:
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
