aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorMarti Bolivar <mbolivar@leaflabs.com>2011-05-27 20:57:54 -0400
committerMarti Bolivar <mbolivar@leaflabs.com>2011-05-27 20:57:54 -0400
commit55ac899c688ed917ca3c0522f16f8a82919c9d4d (patch)
tree0657c001370f20ccd9a0427091cfc26d0da18d0d /docs
parenteee36ecb65ec8d8e032886468e22d941cc3239c9 (diff)
downloadlibrambutan-55ac899c688ed917ca3c0522f16f8a82919c9d4d.tar.gz
librambutan-55ac899c688ed917ca3c0522f16f8a82919c9d4d.zip
Docs: Updating pinmode.rst
Convert to board-specific values; make the language friendlier.
Diffstat (limited to 'docs')
-rw-r--r--docs/source/lang/api/pinmode.rst47
1 files changed, 25 insertions, 22 deletions
diff --git a/docs/source/lang/api/pinmode.rst b/docs/source/lang/api/pinmode.rst
index 8cee3e5..643e26e 100644
--- a/docs/source/lang/api/pinmode.rst
+++ b/docs/source/lang/api/pinmode.rst
@@ -20,26 +20,29 @@ Library Documentation
Discussion
----------
-``pinMode()`` is usually called within :ref:`lang-setup` in order to
+pinMode() is usually called within :ref:`lang-setup` in order to
configure a pin for a certain usage (although it may be called
anywhere).
Example
-------
-::
+This example uses pinMode() to set up the pin connected to the
+built-in LED as an output. Once this is done,
+:ref:`lang-digitalwrite` can be used to turn the pin ``HIGH`` and
+``LOW``, which turn the LED on and off.
- int ledPin = 13; // LED connected to digital pin 13
+::
void setup() {
- pinMode(ledPin, OUTPUT); // sets the digital pin as output
+ pinMode(BOARD_LED_PIN, OUTPUT); // sets the LED pin as output
}
void loop() {
- digitalWrite(ledPin, HIGH); // sets the LED on
- delay(1000); // waits for a second
- digitalWrite(ledPin, LOW); // sets the LED off
- delay(1000); // waits for a second
+ digitalWrite(BOARD_LED_PIN, HIGH); // sets the LED on
+ delay(1000); // waits for a second
+ digitalWrite(BOARD_LED_PIN, LOW); // sets the LED off
+ delay(1000); // waits for a second
}
Arduino Compatibility
@@ -48,17 +51,16 @@ Arduino Compatibility
.. TODO check out Arduino vs. Maple static discilpline cutoffs to
.. ensure accuracy of following:
-The libmaple implementation of ``pinMode()`` supports the ``INPUT``
-and ``OUTPUT`` modes with semantics identical to that of the Arduino
-function (however, be advised that the Maple, as a 3.3V device, will
-only drive 3.3V to an ``OUTPUT`` pin that has been set ``HIGH``).
+On Maple, pinMode() supports the ``INPUT`` and ``OUTPUT`` modes in the
+same way as Arduino (however, remember that the Maple, as a 3.3V
+device, will only drive 3.3V to an ``OUTPUT`` pin that has been set
+``HIGH``, instead of 5V like on Arduino).
-``INPUT_ANALOG`` and ``PWM`` modes were added because the Maple does
-not distinguish between analog and digital pins the same way the
-Arduino does. Unlike the Arduino, you **must call** ``pinMode()`` to
-set up a pin for these purposes before a call to, e.g.,
-:ref:`lang-analogRead`. In practice, this should only add a few lines
-to your :ref:`lang-setup` function.
+``INPUT_ANALOG`` and ``PWM`` modes were added because the Maple
+doesn't separate the analog and digital pins the same way Arduino
+does. Unlike on Arduino, you **must call** pinMode() to set up a pin
+for these purposes before a call to, e.g., :ref:`lang-analogRead`.
+This should only add a few lines to your :ref:`lang-setup` function.
.. TODO [0.1.0] verify following before putting it in:
@@ -69,9 +71,10 @@ to your :ref:`lang-setup` function.
See Also
--------
-- :ref:`lang-constants`
-- :ref:`lang-digitalwrite`
-- :ref:`lang-digitalread`
-- Maple :ref:`GPIO <gpio>` reference page
+- :ref:`lang-board-values`
+- :ref:`lang-constants`
+- :ref:`lang-digitalwrite`
+- :ref:`lang-digitalread`
+- :ref:`gpio`
.. include:: /arduino-cc-attribution.txt