diff --git a/MSP430Timers.pdf b/MSP430Timers.pdf
new file mode 100755
index 0000000000000000000000000000000000000000..88e5ef31a3a7b29a73eed61b98bd2bbfdecf1a7e
Binary files /dev/null and b/MSP430Timers.pdf differ
diff --git a/README.md b/README.md
index 7daad53e461be50634e7b8b7a7607d0065554df8..d06eae8cf48be8198958a852d7b2882e7c828d71 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,33 @@
-# Assignment 7: Breathing LED
-
-Here is the example material you were shown in class. Can you get one of the onboard LEDs to "breathe"?
-
-http://coder-tronics.com/msp430-timer-pwm-tutorial/
-
+# Assignment 7: Breathing LED
+
+Here is the example material you were shown in class. Can you get one of the onboard LEDs to "breathe"?
+
+http://coder-tronics.com/msp430-timer-pwm-tutorial/
+
+and here is another useful discussion of timers 
+
+http://web.eng.fiu.edu/watsonh/EEL4709/MSP430/MSP430Timers.pdf
+
+There are many, many such discussions out there. Please DO NOT merely copy code because you will soon be over your head with confusion, and besides that is against the (THE) rules. 
+
+Notice the MSP430 allows you to:
+
+-- cause a light to turn on if the timer uses a pin it is 'tied' to (as in the data sheet you were shown). This is because you have chosen a certain pattern for the Timer (up, up - down ...) 
+
+-- cause a light to blink using an ISR which is triggered by comparing to a CCR register. Colin used the ISR to make the count go even slower in order to achieve 1 blink / second. 
+
+-- cause an ISR to get control for either of two (three ") CCR events 
+
+Your challenge is to manipulate these registers and values so that the frequency and duty cycle of the light have relative relationship so that a) you can see a light as ON and b) it is ON for relatively more or less time so it seems brighter and dimmer and c) vary those values to that brightness seems to change. 
+
+A pdf from the second link above is in this repo as a visual that may help make some sense of the above. 
+
+Per usual, you need to set various attributes of the circuitry: the pattern of the timer, the way the signal is set or reset on a pin as the interrupts occur, how frequently we sample the timer, whether interrupts are enabled etc etc. There are a lot of names, so be sure you can tell the story to yourself (or a friend). 
+
+Thursday's example code is in this repo. Be sure you have at the ready documentation including the slau manual, the data sheet, the header file(s) , all of which provide useful comments in code. 
+
+As usual, send email, check the Slack channel, be in touch. 
+
+Colin, rgt 
+
+