Revision 17:91fb934a2166, committed 2013-03-01

Comitter:

DavidEGrayson

Date:

Fri Mar 01 05:13:23 2013 +0000

Parent:

16:eaed541b08b0

Child:

18:34ba573573df

Commit message:

Not sure.

Changed in this revision

--- a/PololuLedStrip.cpp	Fri Mar 01 05:09:55 2013 +0000
+++ b/PololuLedStrip.cpp	Fri Mar 01 05:13:23 2013 +0000
@@ -21,7 +21,9 @@
         // Try to generally compute what the delays should be for a ide range of clock frequencies.
         
         // The fudge factors below were experimentally chosen so that we would have
-        // 700/1300 ns pulses and a ~2500 ns period on the mbed NXP LPC1768 (96 MHz Cortex-M3).
+        // ~700/1300 ns pulses and a ~2500 ns period on the mbed NXP LPC1768 (96 MHz Cortex-M3).
+        // There seem to be some ~100 ns inconsistencies in the timing depending on which example program is
+        // running; the most likely explanation is some kind of flash caching that affects the timing.
         // If you ever change these numbers, it is important to check the the subtractions below
         // will not overflow in the worst case, which is f_mhz = 49.
         led_strip_write_delays[0] = 700*f_mhz/1000 - 23;