Revision: 1164
Author: robhamerling
Date: Wed Aug  5 12:47:32 2009
Log:
  Update for dev2jal script version 0.0.77 (and JalV2 compiler version 2.4l)


http://code.google.com/p/jallib/source/detail?r=1164

Modified:
  /trunk/doc/html/devicefiles.html

=======================================
--- /trunk/doc/html/devicefiles.html    Mon Jul 20 08:38:26 2009
+++ /trunk/doc/html/devicefiles.html    Wed Aug  5 12:47:32 2009
@@ -9,7 +9,7 @@
    <meta name="project" content="This file is part of jallib   
http://jallib.googlecode.com";>
    <meta name="license" content="Released under the BSD license"
                               
"http://www.opensource.org/licenses/bsd-license.php";>
-  <meta name="compiler" content="2.4">
+  <meta name="compiler" content="2.4l">
    <link rel="stylesheet" href="jallib.css" type="text/css">
  </head>
  <body LANG="en-US" DIR="LTR">
@@ -461,6 +461,21 @@
  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>Names of Timer fields</h3>
+<p>For the timers the following naming has been chosen:
+<ul>
+<li>'bit*4 PS' of T0CON splitted into 'bit PSA' and 'bit*3 PS'
+(this is a correction of the MPLAB .dev files).
+<li>Bit TxSYNC in TxCON register normalized to NTxSYNC for:
+  <ul>
+  <li>T1CON of baseline and midrange
+  <li>T1CON, T3CON, T5CON and T7CON of 18F series.
+  </ul>
+<li>TxCON_TOUTPS is normalized to TxCON_TxOUTPS (x = timer number) for
+the 18Fs.
+Since the baseline PICs have only 1 timer with TOUTPS bit this name has
+been maintained.
+</ul>

  <h3>Miscellaneous remarks about names</h3>
  <p>When you have used JAL before with other device files or libraries
@@ -578,18 +593,24 @@
     LP                 -- Low Power crystal on OSC1,OSC2
     XT                 -- Crystal or Resonator on OSC1,OSC2
     HS                 -- High Speed Crystal or Resonator on OSC1,OSC2
-   HS_PLL             -- HS with PLL active
+   HS_PLL             -- HS with (hardware) PLL active
     EC_CLKOUT          -- External Clock (TTL) signal on OSC1, ClockOut on  
OSC2
     EC_NOCLKOUT        -- External Clock (TTL) signal on OSC1, OSC2 is I/O
     EC_CLKOUT_PLL      -- EC_CLKOUT with PLL active
     EC_NOCLKOUT_PLL    -- EC_NOCLKOUT with PLL active
-   RC_CLKOUT          -- (external) RC oscillator on OSC1, ClockOut on OSC2
-   RC_NOCLKOUT        -- (external) RC oscillator on OSC1, OSC2 is I/O
+   RC_CLKOUT          -- (external) Resistor/Capacitor oscillator on OSC1,  
ClockOut on OSC2
+   RC_NOCLKOUT        -- (external) Resistor/Capacitor oscillator on OSC1,  
OSC2 is I/O
     INTOSC_CLKOUT      -- Internal oscillator, OSC1 is I/O, ClockOut on OSC2
     INTOSC_NOCLKOUT    -- Internal oscillator, OSC1 and OSC2 are I/O
-   <i>(other keywords may be used as well,
-       esp. for PICs with USB, PLL or dual oscillator sources)</i>
  </pre>
+Several other keywords could be possible, for example for PICs:
+<ul compact>
+<li>with USB
+<li>with dual oscillator sources
+<li>low, medium, and high power oscillators
+</ul>
+The datasheet will specify the possibilities, scan the device files for
+the keyword which applies.

  <h3>Fuse_Def WDT  (watchdog)</h3>
  <pre>
@@ -678,9 +699,9 @@
  usually 'On' and 'Off' are used.
  </ol>

-<p>When a fuse_def statement causes compile-time error messages you may
-simply delete it and specify the fuse-word(s) or -byte(s) explicitly with
-bit patterns in stead of using fuse option pragma statements.
+<p>When a fuse_def statement causes compile-time error messages you
+probably should use an alternative method to specify the configuration-
+word(s) or -byte(s) explicitly with bit patterns.
  For example for the PIC16F690 the following group of statements:
  <pre>
     pragma target OSC       HS
@@ -746,7 +767,7 @@

  <h2>Compiler requirements</h2>

-<p>The compiler - at the moment of this writing version 2.4k - has a
+<p>The compiler - at the moment of this writing version 2.4l - 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to