summaryrefslogtreecommitdiff
path: root/nuttx/configs/lpc4330-xplorer/README.txt
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-07-17 03:58:11 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-07-17 03:58:11 +0000
commit5da90b889758aac235acf8c1dff93e90ddfbfe7d (patch)
treed73fe9581f45296f026a24f991bc80cab5cd479d /nuttx/configs/lpc4330-xplorer/README.txt
parentaa7d9710dc9c125685b30dbc3c9ac33dd0e5567f (diff)
downloadpx4-nuttx-5da90b889758aac235acf8c1dff93e90ddfbfe7d.tar.gz
px4-nuttx-5da90b889758aac235acf8c1dff93e90ddfbfe7d.tar.bz2
px4-nuttx-5da90b889758aac235acf8c1dff93e90ddfbfe7d.zip
Header file clean-up
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4948 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/configs/lpc4330-xplorer/README.txt')
-rw-r--r--nuttx/configs/lpc4330-xplorer/README.txt36
1 files changed, 34 insertions, 2 deletions
diff --git a/nuttx/configs/lpc4330-xplorer/README.txt b/nuttx/configs/lpc4330-xplorer/README.txt
index e3697f6e7..13805c0b1 100644
--- a/nuttx/configs/lpc4330-xplorer/README.txt
+++ b/nuttx/configs/lpc4330-xplorer/README.txt
@@ -381,8 +381,35 @@ Code Red IDE
CONFIG_DEBUG=y
CONFIG_DEBUG_SYMBOLS=y
- Troubleshooting. This page provides some troubleshooting information that
- you can use to verify that the LPCLink is working correctly:
+ NOTE 4: Every time that you control-C out of the command line GDB, you
+ leave a copy of the Code Red debugger (crt_emu_lpc18_43_nxp) running. I
+ have found that if you have these old copies of the debugger running,
+ hen strange things can happen when start yet another copy of the
+ debugger (I suspect that GDB may be talking with the wrong debugger).
+
+ If you exit GDB with quit (not control-C), it seems to clean-up okay.
+ But I have taken to keeping a Process Explorer window open all of the
+ time to keep track of how many of these bad processes have been created.
+
+ NOTE 5: There is also a certain function that is causing some problems.
+ The very first thing that the start-up logic does is call a function
+ called lpc43_softreset() which resets most of the peripherals. But it
+ also causes some crashes... I think because the resets are causing some
+ interrupts.
+
+ I put a big delay in the soft reset logic between resetting and clearing
+ pending interrupts and that seems to help some but I am not confident
+ that that is a fix. I think that the real fix might be to just eliminated
+ this lpc43_softreset() function if we determine that it is not needed.
+
+ If you step over lpc43_softreset() after loading the coding (using the 'n'
+ command), then everything seems work okay.
+
+ Troubleshooting
+ ---------------
+
+ This page provides some troubleshooting information that you can use to
+ verify that the LPCLink is working correctly:
http://support.code-red-tech.com/CodeRedWiki/LPCLinkDiagnostics
@@ -394,6 +421,11 @@ Code Red IDE
found in the configs/lpc4330-xplorer/scripts directory can do that with
a single command line command.
+ USB DFU Booting
+ ---------------
+
+ To be provided.
+
NuttX buildroot Toolchain
=========================