Author: robhamerling
Date: Mon Apr 13 11:25:55 2009
New Revision: 925
Modified:
trunk/TORELEASE
trunk/doc/html/devicefiles.html
Log:
- enhancements in devicefiles.html docs
- added 'new' libs because of refacturing LCD libs (before we forget!)
Modified: trunk/TORELEASE
==============================================================================
--- trunk/TORELEASE (original)
+++ trunk/TORELEASE Mon Apr 13 11:25:55 2009
@@ -142,6 +142,8 @@
include/external/keyboard/keyboard.jal
include/external/lcd/lcd_hd44780_4.jal
include/external/lcd/lcd_hd44780_8.jal
+include/external/lcd/lcd_hd44780_common.jal
+include/external/lcd/lcd_hd44780_serial_sw.jal
include/external/temperature/temperature_tc77.jal
# Jal extension
include/jal/calendar.jal
Modified: trunk/doc/html/devicefiles.html
==============================================================================
--- trunk/doc/html/devicefiles.html (original)
+++ trunk/doc/html/devicefiles.html Mon Apr 13 11:25:55 2009
@@ -19,26 +19,30 @@
<h2>Introduction</h2>
-<p>When I started with JAL it struck me that there were so few JALV2
include
-files, in particular not for some of my favorite PICmicros (e.g. 16F690,
-12F683).
-Unfortunately the output of INC2JAL for these chips caused compile-time
-errors with my programs and I was informed that INC2JAL is not up-to-date
-for JalV2.
-I realized that more people would be in the same position like me.
-Having some experience with scanning MPLAB files (for my Xwisp2 program)
-I decided to make a script to generate the device files not only for the
-desired PICs, but for all PICs supported by the JalV2 compiler!
+<p>When I started programming in JAL it struck me that there were so few
+JALV2 include files, in particular not for some of my favourite PICmicros
+(such as the 16F690 and 12F683).
+The <b>Inc2Jal</b> utility to generate device definition files was designed
+for the original Jal compiler, was not updated for JalV2 and the device
+files it generated for my preferred PICs gave compile errors.
+Possible ways to resolve this issue might have been to update the generated
+device files manually or make Inc2Jal up-to-date for JalV2.
+I didn't like either of these (Inc2Jal is written in Pascal, which I hadn't
+used for many years).
+<br>Since I already had a Rexx script to scan MPlab files for my Xwisp2
+program I decided to take that route for a replacement of Inc2Jal.
+I named the new script <b>Dev2Jal</b> because it uses the .dev files of
+MPlab as base in stead of the .inc files like Inc2Jal.
-<p> The advantages of using a script to generate include files are
-pretty obvious, such as:
+<p>The advantages of automated generation of device files are pretty
+obvious, such as:
<ul>
<li>creation of device files for all PICmicros available in MPLAB
-<li>automatic new device files for new chips in MPLAB
-<li>no manual maintenance
+<li>automatic new device files for new chips
+<li>no manual maintenance of device files
<li>consistent layout
<li>consistent naming convention
-<li>no errors due to typo's with manual editing
+<li>no errors due to typos with manual editing
</ul>
<p>The advantages of a consistent naming convention are also obvious:
@@ -47,10 +51,10 @@
<li>Same for libraries using this naming convention.
</ul>
-<p>This document gives some design information and user instruction
-about these JalV2 device files.
+<p>This document gives some design information and some instructions for
the
+use of these JalV2 device files.
The sources of information are the xxxx.dev files and xxxx.lkr of MPLAB,
-supplemented and corrected with information in the datasheets.
+supplemented and corrected with information from the datasheets.
<hr>
<h1>The Overall Picture</h1>
@@ -74,7 +78,7 @@
<p>These device files are now part of the central JalV2 library
repository <a href="http://jallib.googlecode.com/";>JalLib</a> at
-code.google.com, which uses globally the same structure.
+code.google.com, which uses the same structure.
<h2>Device Files</h2>
@@ -95,6 +99,20 @@
<li>Declaration of symbolic names for configuration bits (fuses).
<li>Procedures to switch the ports to digital I/O.
</ul>
+
+<p>Including a device file doesn't change anything to the PIC.
+For example pins which are input after power-on or reset remain input,
+etc.
+Required changes are the responsibility of the application program or
+function libraries.
+For convenience reasons every device file contains a procedure to
+disable all analog modules of the PIC and to change all pins which are
+analog by default to digital mode: enable_digital_io().
+
+<p>The defaults for the configuration bits may be slightly different
+than their specifications in the datasheet.
+You can find the default configuration bits settings in the top of the
+device file.
<h2>Common Include File 'chipdef_jallib.jal'</h2>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
