changed the getting started markdown files to rflect Pi board revision autodetection

Romilly Cocking · Romilly Cocking · commit fe84c7b986aa · 2012-12-06T15:41:57.000Z
diff --git a/doc/getting-started-with-gpio.md b/doc/getting-started-with-gpio.md
@@ -32,7 +32,7 @@ the header pin number and whether the pin is to be used for input or
 output.
 
     out_pin = Pin(12, Pin.Out)
-    in_pin = Pin(16, Pin.In)
+    in_pin = Pin(11, Pin.In)
 
 When you have a Pin instance you can read or write its value.  A value
 of 1 is high, a value of 0 is low.
@@ -50,7 +50,7 @@ Putting it all together into a single program:
     from quick2wire.gpio import Pin
     
     out_pin = Pin(12, Pin.Out)
-    in_pin = Pin(16, Pin.In)
+    in_pin = Pin(11, Pin.In)
     
     out_pin.value = 1
     print(in_pin.value)
@@ -64,34 +64,20 @@ as part of a [with](http://docs.python.org/reference/compound_stmts.html#with) s
 
     from quick2wire.gpio import Pin, exported
 
-    with exported(Pin(12, Pin.Out)) as out_pin, exported(Pin(16, Pin.In)) as in_pin:
+    with exported(Pin(12, Pin.Out)) as out_pin, exported(Pin(11, Pin.In)) as in_pin:
         out_pin.value = 1
     	print(in_pin.value)
 
 This will unexport the pins when the program leaves the `with` statement, even 
 if the user kills the program or a bad piece of code throws an exception.
 
-Here's a slightly more complicated example that blinks an LED attached to pin 8. This will 
+Here's a slightly more complicated example that blinks an LED attached to pin 12. This will
 loop forever until the user stops it with a Control-C.
 
     from time import sleep
     from quick2wire.gpio import Pin, exported
     
-    with exported(Pin(8, Pin.Out)) as pin:
+    with exported(Pin(12, Pin.Out)) as pin:
         while True:
             pin.value = 1 - pin.value
             sleep(1)
-
-
-Connecting Pins
----------------
-
-To make this blink program work, you'll need to know which physical pins to connect. The 
-`quick2wire.gpio` library sorts out the confusion of pin numbering schemes so that you can
-just specify the physical pin on the device. [This page](http://elinux.org/Rpi_Low-level_peripherals) 
-currently seems to be the best summary of the pins and the I/O roles they fulfill. The library
-will allow you to allocate only those pins which support GPIO. Lower numbered
-pins are at the top end of the Pi with the SD Card and power connector. Pins 1 and 2 (at the top of 
-the columns) are the 3.3 and 5 volt outputs. Here's a Pi wired up for the blink program 
-
-<img src="http://github.com/quick2wire/quick2wire-python-api/raw/master/doc/getting-started-with-gpio-setup.png" alt="GPIO wiring example" width="250"/>
diff --git a/doc/getting-started-with-i2c.md b/doc/getting-started-with-i2c.md
@@ -10,16 +10,8 @@ Warning:
 With a revision 2.0 board, if you connect an I2C device to the appropriate header,
 you will see it when you run `i2cdetect 1` instead of `i2cdetect 0`.
 
-Also **in the example below, and in the I2C examples in the examples directory,
-you need to change the line**
-
-    with i2c.I2CBus() as bus:
-
-to read
-
-    with i2c.I2CBus(1) as bus:
-
-We will automate the detection of the default bus as soon as we get our hands on a rev 2.0 board.
+The library now auto-detects whether you are running version 1.0 or 2.0 of the board, so the same code will work on
+either.
 
 The example:
 ------------
@@ -46,7 +38,7 @@ group membership.
 
 Check the MCP23008 is connected to your I2C bus and its address is
 configured as expected.  We can see the device on the bus by running
-the `i2cdetect` command:
+the `i2cdetect` command. Remember to replace 0 with 1 if you hav a revision 2 board.
 
     $ i2cdetect 0
     WARNING! This program can confuse your I2C bus, cause data loss and worse!
