Revision: 1297 Author: robhamerling Date: Sun Sep 6 02:28:51 2009 Log: Some corrections and improvements of devicefiles.html Added simple table style to jallib.css
http://code.google.com/p/jallib/source/detail?r=1297 Modified: /trunk/doc/html/devicefiles.html /trunk/doc/html/jallib.css ======================================= --- /trunk/doc/html/devicefiles.html Sat Sep 5 12:13:38 2009 +++ /trunk/doc/html/devicefiles.html Sun Sep 6 02:28:51 2009 @@ -428,39 +428,51 @@ difference in register naming is not issue, on the contrary: a compiler message will inform you when you included the wrong library. -<- -------- -> <h3>Names for registers and subfields of CCP modules</h3> -<p>There are CCP modules and enhanced CCP modules. -The first is also called 'legacy' CPP modules in this document. +<p>There are CCP modules and Enhanced CCP modules. +The first is also called 'legacy' CPP modules in this document and elsewhere. Most legacy CCP modules have registers names starting with CCP, most registers of enhanced CCP modules start with ECCP. The same is true for subfields of these registers. -<p>However there are many deviations from these rules and contradictions +However there are many deviations from these rules and contradictions between PMPLAB .dev files and the datasheets! <p>Enhanced CCP modules can be used as legacy CCP modules, in particular for PWM operations. -For this purpose a number aliases are declared which allow a PWM library -to access the CCP registers and subfields with legacy names. -<ul> -<li>ECCPxCON has alias CCPxCON (x in range 1..10). -<li>ECCPxCON subfield EDCxB has alias DCxB -<li>EXXPxCON subfield ECCPxM has alias CCPxM -<li>ECCPRx has alias CCPRx, -ECCPRxH and ECCPRxL have aliases CCPRxH and CCPRxL. -</ul> -Exception: for PICs with both an CCP1CON and a ECCP1CON register -ECCP1CON has alias CCP2CON, EDC1B subfiled has alias DC2B, -ECCPxM has alias CCP2xM -(18f448,4480,458,4580,4585,4680,4682,4685). -With these aliases the enhanced CCP module can be accessed as second -(legacy) CCP module. - -<p>Some PICs have the CCPxCON 2-bits subfield DCxB defined -as 2 separate bits CCPxX and CCPxY. -For compatibility with other PICs a 2 bits field DCxB has been added. -(16F91x,946,18F2321,2480,2580,4321,4480,4580). +For this purpose a number aliases are added to the device files which +allow access of enhanced CCP registers and subfields with legacy names. +An example of this is the pwm_hardware library. +<p>The following legacy aliases for enhance CCP modules are declared: +<table> +<tr><th>field <th>alias <th>remarks </tr> +<tr><td>ECCPxCON <td>CCPxCON <td>x in range 1..10 </tr> +<tr><td>ECCPxCON_EDCxB <td>CCPxCON_DCxB <td>bits*2 </tr> +<tr><td>ECCPxCON_ECCPxM <td>CCPxCON_CCPxM <td>bits*4 </tr> +<tr><td>ECCPRx <td>CCPRx <td> </tr> +<tr><td>ECCPRxH <td>CCPRxH <td> </tr> +<tr><td>ECCPRxL <td>CCPRxL <td> </tr> +</table> +<p>Exception: for PICs with both an CCP1CON and a ECCP1CON register +(18f448,4480,458,4580,4585,4680,4682,4685), +and to allow the enhanced CCP module to be used as second legacy CCP module, +the following aliases are declared: +<table> +<tr><th>field <th>alias <th>remarks </tr> +<tr><td>ECCP1CON <td>CCP2CON <td> </tr> +<tr><td>ECCP1CON_EDC1B <td>CCP2CON_DC2B <td> </tr> +<tr><td>ECCP1CON_ECCP1M <td>CCP2CON_CCP2M <td> </tr> +<tr><td>ECCPR1 <td>CCPR2 <td> </tr> +<tr><td>ECCPR1H <td>CCPR2H <td> </tr> +<tr><td>ECCPR1L <td>CCPR2L <td> </tr> +</table> + +<p>Some PICs (16F91x,946, 18F2321,2480,2580,4321,4480,4580) have the +CCPxCON 2-bits subfield DCxB defined as 2 separate bits CCPxX and CCPxY, +other PICs (16F88x) have this field enumerated and defined as +DCxB1 and DCxB0. +For compatibility with most other PICs a 2 bits field CCPxCON_DCxB has +been added in the device files for these cases. <h3>Names of ANSEL bits</h3> ======================================= --- /trunk/doc/html/jallib.css Wed Jan 28 23:51:47 2009 +++ /trunk/doc/html/jallib.css Sun Sep 6 02:28:51 2009 @@ -57,6 +57,21 @@ margin: 2em 1em 1em 1em; } + table { + border: solid navy 3px; + border-collapse: collapse; + margin: 1em 0 0 1em; + padding: 2em; + } + th { + padding: 0 1em 0 1em; + font-weight: bold; + border: solid navy 2px; + } + td { + padding: 0 1em 0 1em; + border: solid navy 1px; + } /* end of stylesheet for Jallib */ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
