summaryrefslogtreecommitdiff
path: root/nuttx/configs/stm32f4discovery
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2013-05-29 10:26:00 -0600
committerGregory Nutt <gnutt@nuttx.org>2013-05-29 10:26:00 -0600
commit26346bebfa749b55d1dd983c478d14c913eb9619 (patch)
treed8c42f6585bfb31af497f7100b09b3b2f9274bf8 /nuttx/configs/stm32f4discovery
parentc2f92bd1abeb2cab6b1dffb6f88f10b6c8b596e1 (diff)
downloadpx4-nuttx-26346bebfa749b55d1dd983c478d14c913eb9619.tar.gz
px4-nuttx-26346bebfa749b55d1dd983c478d14c913eb9619.tar.bz2
px4-nuttx-26346bebfa749b55d1dd983c478d14c913eb9619.zip
Fix STM32F1 and F3 USB device driver. It was not handling NULL packets correctly and it prevent use of the driver with the CDC/ACM class
Diffstat (limited to 'nuttx/configs/stm32f4discovery')
-rw-r--r--nuttx/configs/stm32f4discovery/README.txt6
1 files changed, 6 insertions, 0 deletions
diff --git a/nuttx/configs/stm32f4discovery/README.txt b/nuttx/configs/stm32f4discovery/README.txt
index 684c916f5..e94bd466b 100644
--- a/nuttx/configs/stm32f4discovery/README.txt
+++ b/nuttx/configs/stm32f4discovery/README.txt
@@ -1641,6 +1641,12 @@ Where <subdir> is one of the following:
configuration so nothing should appear on UART2 unless you enable
some debug output or enable the USB monitor.
+ NOTE: Using the SYSLOG to get debug output has limitations. Among
+ those are that you cannot get debug output from interrupt handlers.
+ So, in particularly, debug output is not a useful way to debug the
+ USB device controller driver. Instead, use the USB monitor with
+ USB debug off and USB trance on (see below).
+
4. Enabling USB monitor SYSLOG output. If tracing is enabled, the USB
device will save encoded trace output in in-memory buffer; if the
USB monitor is enabled, that trace buffer will be periodically