aboutsummaryrefslogtreecommitdiffstats
path: root/source/hardware/maple.rst
diff options
context:
space:
mode:
authorMarti Bolivar <mbolivar@leaflabs.com>2011-05-13 17:44:46 -0400
committerMarti Bolivar <mbolivar@leaflabs.com>2011-05-13 20:10:37 -0400
commit3bf30c706c1a5a266dbe55af0d206385887882fa (patch)
tree86db5ddc7dd6c0e2e5f37335a0b58777a8349c93 /source/hardware/maple.rst
parent0cfeed3fe453118be00ec6965a3de6dda7853852 (diff)
downloadlibrambutan-3bf30c706c1a5a266dbe55af0d206385887882fa.tar.gz
librambutan-3bf30c706c1a5a266dbe55af0d206385887882fa.zip
Docs: Removing note about cutting the Maple's NJTRST<->NRST trace.
Worried about the possibility of an attractive nuisance.
Diffstat (limited to 'source/hardware/maple.rst')
-rw-r--r--source/hardware/maple.rst10
1 files changed, 4 insertions, 6 deletions
diff --git a/source/hardware/maple.rst b/source/hardware/maple.rst
index 2ae1c30..d0434ab 100644
--- a/source/hardware/maple.rst
+++ b/source/hardware/maple.rst
@@ -322,12 +322,10 @@ Rev 5
from its silkscreen. This mistake was fixed in later manufacturing
runs.
-* **Reset and NJTRST tied together**: The MCU's reset pin is tied to
- PB4, the NJTRST pin, which is pin 43. Thus, attempting to use pin
- 43 as a GPIO will reset your board (and also prevents the JTAG
- "reset halt") command from working properly. It's possible to cut
- the trace, but doing so will damage your board, so we *do not
- recommend it* unless you're very sure about what you're doing.
+* **Reset and NJTRST tied together**: The MCU's reset pin is connected
+ to PB4, the NJTRST pin, which is pin 43. Thus, attempting to use
+ pin 43 as a GPIO will reset your board (and also prevents the JTAG
+ "reset halt") command from working properly.
Rev 3
~~~~~