diff options
| author | Gregory Nutt <gnutt@nuttx.org> | 2013-05-29 10:26:00 -0600 |
|---|---|---|
| committer | Gregory Nutt <gnutt@nuttx.org> | 2013-05-29 10:26:00 -0600 |
| commit | 26346bebfa749b55d1dd983c478d14c913eb9619 (patch) | |
| tree | d8c42f6585bfb31af497f7100b09b3b2f9274bf8 /nuttx/TODO | |
| parent | c2f92bd1abeb2cab6b1dffb6f88f10b6c8b596e1 (diff) | |
| download | nuttx-26346bebfa749b55d1dd983c478d14c913eb9619.tar.gz nuttx-26346bebfa749b55d1dd983c478d14c913eb9619.tar.bz2 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/TODO')
| -rw-r--r-- | nuttx/TODO | 19 |
1 files changed, 2 insertions, 17 deletions
diff --git a/nuttx/TODO b/nuttx/TODO index 74bf4e78c..e1c57dfe1 100644 --- a/nuttx/TODO +++ b/nuttx/TODO @@ -1,4 +1,4 @@ -NuttX TODO List (Last updated April 10, 2013) +NuttX TODO List (Last updated May 29, 2013) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This file summarizes known NuttX bugs, limitations, inconsistencies with @@ -32,7 +32,7 @@ nuttx/ (0) ARM/LPC43x (arch/arm/src/lpc43xx/) (3) ARM/STR71x (arch/arm/src/str71x/) (3) ARM/LM3S6918 (arch/arm/src/lm/) - (6) ARM/STM32 (arch/arm/src/stm32/) + (5) ARM/STM32 (arch/arm/src/stm32/) (3) AVR (arch/avr) (0) Intel x86 (arch/x86) (5) 8051 / MCS51 (arch/8051/) @@ -1608,21 +1608,6 @@ o ARM/STM32 (arch/arm/src/stm32/) Status: Open Priority: Low - Title: USB DRIVER IN STM32F3DISCVORY usbnsh CONFIGURATION - Description: The USB device driver is not reliable in the - configs/stm32f3discovery/upnsh configuration. When a large - volume of serial data is sent (for example, by entering - 'help' from the NSH command line), the driver hangs. This - looks like an improperly handled output data overrun problem. - - This is a surprising since this same driver has worked with - the STM32 F1 for some time using the Mass Storage driver - which has considerably higher data rates. So this seems to - be some particular issue with the way that the CDC/ACM driver - sends data through the driver. - Status: Open - Priority: Medium High - o AVR (arch/avr) ^^^^^^^^^^^^^^ |