CVS: python README-msp430-dco.txt,1.2,1.3

Chris Liechti <[email protected]> Thu, 15 May 2008 08:56:09 -0700
Newsgroups gmane.comp.hardware.texas-instruments.msp430.gcc.cvs
Message-ID <[email protected]>
Update of /cvsroot/mspgcc/python
In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv32337/python

Modified Files:
	README-msp430-dco.txt 
Log Message:
doc updates

Index: README-msp430-dco.txt
===================================================================
RCS file: /cvsroot/mspgcc/python/README-msp430-dco.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -w -d -r1.2 -r1.3
--- README-msp430-dco.txt	8 Dec 2006 22:05:56 -0000	1.2
+++ README-msp430-dco.txt	15 May 2008 15:56:06 -0000	1.3
@@ -69,7 +69,7 @@
 
     Write clock calibration for 1.5MHz to the information memory at 0x1000::
     
-        msp430-dco 1.5e6 BCSCTL1@0x1000 DCOCTL@0x1000
+        msp430-dco 1.5e6 BCSCTL1@0x1000 DCOCTL@0x1001
 
 Use it at your own risk. No guarantee that the values are correct.
 
@@ -90,7 +90,7 @@
 
 Notes:
 
-- the --output option can be used to redirect the output. Once could also use
+- the --output option can be used to redirect the output. One could also use
   the usual stdout redirection from the shell (``>filename``)
 - --tolerance specifies a window in which the clock has to be to complete the
   calibration.
@@ -187,6 +187,11 @@
     This is only possible for F2xx devices.
 
 
+Known Issues
+------------
+The algorithm does not search for the best match, it stops when the frequency
+iswithin the window. Therefor it's not unlikely that the frequency is at the
+border of the tolerance window and not in the center.
 
 
 History


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/