diff options
author | patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679> | 2012-03-19 17:56:15 +0000 |
---|---|---|
committer | patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679> | 2012-03-19 17:56:15 +0000 |
commit | aa37eeaa03f819cb3cf591b63dc2ee463fc78047 (patch) | |
tree | 5d423851b7062520785d7624c9a1d0b3a09ce33b /nuttx/TODO | |
parent | 199e9314622731714c0331264a52e8b1d00a1d4e (diff) | |
download | px4-firmware-aa37eeaa03f819cb3cf591b63dc2ee463fc78047.tar.gz px4-firmware-aa37eeaa03f819cb3cf591b63dc2ee463fc78047.tar.bz2 px4-firmware-aa37eeaa03f819cb3cf591b63dc2ee463fc78047.zip |
Minor updates for PIC32 USB device driver bugs
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4497 7fd9a85b-ad96-42d3-883c-3090e2eb8679
Diffstat (limited to 'nuttx/TODO')
-rw-r--r-- | nuttx/TODO | 37 |
1 files changed, 33 insertions, 4 deletions
diff --git a/nuttx/TODO b/nuttx/TODO index d20309ae1..0baac17ab 100644 --- a/nuttx/TODO +++ b/nuttx/TODO @@ -1,4 +1,4 @@ -NuttX TODO List (Last updated February 21, 2012) +NuttX TODO List (Last updated March 19, 2012) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This file summarizes known NuttX bugs, limitations, inconsistencies with @@ -35,7 +35,7 @@ nuttx/ (3) AVR (arch/avr) (0) Intel x86 (arch/x86) (4) 8051 / MCS51 (arch/8051/) - (0) MIPS/PIC32 (arch/mips) + (1) MIPS/PIC32 (arch/mips) (1) Hitachi/Renesas SH-1 (arch/sh/src/sh1) (4) Renesas M16C/26 (arch/sh/src/m16c) (10) z80/z8/ez80 (arch/z80/) @@ -1253,8 +1253,37 @@ o 8051 / MCS51 (arch/8051/) Status: Open Priority: Low -- only because there as so many other issues with 8051 -o MIPS (arch/mips) - ^^^^^^^^^^^^^^^^ +o MIPS/PIC32(arch/mips) + ^^^^^^^^^^^^^^^^^^^^^ + + Title: PIC32 USB DRIVER DOES NOT WORK WITH MASS STORAGE CLASS + Description: The PIC32 USB driver either crashes or hangs when used with + the mass storage class when trying to write files to the target + storage device. This usually works with debug on, but does not + work with debug OFF (implying some race condition?) + + Here are some details of what I see in debugging: + + 1. The USB MSC device completes processing of a read request + and returns the read request to the driver. + 2. Before the MSC device can even begin the wait for the next + driver, many packets come in at interrupt level. The MSC + device goes to sleep (on pthread_cond_wait) with all of the + read buffers ready (16 in my test case). + 3. The pthread_cond_wait() does not wake up. This implies + a problem with pthread_con_wait(?). But in other cases, + the MSC device does wake up, but then immediately crashes + because its stack is bad. + 4. If I force the pthread_cond_wait to wake up (by using + pthread_cond_timedwait instead), then the thread wakes + up and crashes with a bad stack. + + So far, I have no clue why this is failing. + Status: Open + Priority: High + + + o Hitachi/Renesas SH-1 (arch/sh/src/sh1) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |