aboutsummaryrefslogtreecommitdiffstats
path: root/docs/source/troubleshooting.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/source/troubleshooting.rst')
-rw-r--r--docs/source/troubleshooting.rst62
1 files changed, 0 insertions, 62 deletions
diff --git a/docs/source/troubleshooting.rst b/docs/source/troubleshooting.rst
index 181c3d4..0e9e13d 100644
--- a/docs/source/troubleshooting.rst
+++ b/docs/source/troubleshooting.rst
@@ -10,68 +10,6 @@ This page documents common problems and their solutions.
.. contents:: Contents
:local:
-===================
- Hardware problems
-===================
-
-.. _troubleshooting-throb:
-
-The LED is throbbing and my program is stopped!
------------------------------------------------
-
-The LED throbs when there has been a failed software :ref:`ASSERT()
-<lang-assert>` or some other error.
-
-In the case of a failed assertion, a first debugging step you can take
-is to find out the file and line where the failed assertion took place
-(for instructions on this, see the ``ASSERT()`` documentation linked
-to above). This may give you some clue about the source of the error.
-
-:ref:`libmaple` often uses ``ASSERT()`` to halt immediately when it
-detects that something has gone wrong, so if you're not using
-assertions, then what's probably happening is that some bug is causing
-the failed ``ASSERT()`` lower down.
-
-If it's not a failed assertion, then you're likely looking at
-something like a `hard fault
-<http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0337e/ch05s12s01.html>`_.
-
-There are a few issues with the bootloader which mean you might not be
-able to upload your program when this happens. You can still
-reprogram by using :ref:`perpetual bootloader mode
-<troubleshooting-perpetual-bootloader>`.
-
-My board is bricked! I can't upload via the bootloader no matter what!
-----------------------------------------------------------------------
-
-Don't panic. First, make sure that the board is plugged in correctly
-for program upload. If that doesn't work,
-try using :ref:`perpetual bootloader mode
-<troubleshooting-perpetual-bootloader>`.
-
-If that doesn't work, then you've got a problem. All is not lost,
-however! You can always try to :ref:`re-flash the bootloader
-<bootloader-reflashing>` over serial (or :ref:`JTAG <jtag>`).
-
-If your board really is bricked, and you think it's our fault,
-`contact us <http://leaflabs.com/contact>`_\ !
-
-My 5v peripheral doesn't work! (I2C, SPI, USART, etc)
------------------------------------------------------
-
-Yup, the Maple is a 3.3v board. You may need to use a level
-converter. See the :ref:`Arduino Compatibility
-<arduino-compatibility>`, :ref:`GPIO <gpio>`, or other :ref:`hardware
-specific documentation <index-hardware>` for more information.
-
-The reset and D38/serial buttons don't seem to work reliably!
--------------------------------------------------------------
-
-A few Maple Rev3 boards shipped in May-June 2010 may have had
-unreliable buttons; see the :ref:`Maple Errata
-<maple-rev3-bad-buttons>` for details. `We're happy to replace these
-for you <http://leaflabs.com/contact>`_\ !
-
.. _troubleshooting-ide-install:
=======================