diff options
| author | patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679> | 2012-06-03 20:05:44 +0000 |
|---|---|---|
| committer | patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679> | 2012-06-03 20:05:44 +0000 |
| commit | 2d80d4285eb7805b7dc7b5fba590a9a5fb766651 (patch) | |
| tree | b8f7b119b13d5243084377e2e596ee43a2178843 /nuttx/TODO | |
| parent | df97ce92a49aafeeba1a9e51240d3b1ad33698e1 (diff) | |
| download | px4-firmware-2d80d4285eb7805b7dc7b5fba590a9a5fb766651.tar.gz px4-firmware-2d80d4285eb7805b7dc7b5fba590a9a5fb766651.tar.bz2 px4-firmware-2d80d4285eb7805b7dc7b5fba590a9a5fb766651.zip | |
PIC32 USB mass storage device works; USB and MSC are now enabled by default in the PIC32MX7 MMB configuration
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4801 7fd9a85b-ad96-42d3-883c-3090e2eb8679
Diffstat (limited to 'nuttx/TODO')
| -rw-r--r-- | nuttx/TODO | 24 |
1 files changed, 22 insertions, 2 deletions
diff --git a/nuttx/TODO b/nuttx/TODO index b75691420..5c2be8d81 100644 --- a/nuttx/TODO +++ b/nuttx/TODO @@ -35,7 +35,7 @@ nuttx/ (3) AVR (arch/avr) (0) Intel x86 (arch/x86) (4) 8051 / MCS51 (arch/8051/) - (1) MIPS/PIC32 (arch/mips) + (2) 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/) @@ -1442,6 +1442,7 @@ o MIPS/PIC32(arch/mips) ^^^^^^^^^^^^^^^^^^^^^ Title: PIC32 USB DRIVER DOES NOT WORK WITH MASS STORAGE CLASS + UPDATE: ** ONLY USING RAM DISK FOR EXPORTED VOLUME *** 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 @@ -1464,8 +1465,27 @@ o MIPS/PIC32(arch/mips) up and crashes with a bad stack. So far, I have no clue why this is failing. + UPDATE: This bug was recorded using the PIC32 Ethernet + Starter kit with a RAM disk (that board has no SD card slot). + Howevever, using the USB mass storage device with the + Mikroelektronika using a real SD card, there is no such + problem -- the mass storage device is quite stable. + Status: Open + Priority: Originally, High BUT reduced to very Low based on the + UPDATED comments. + + Title: PIC32 USB MASS STORAGE DEVICE FAILS TO RE-CONNECT + Description: Found using configuration configs/pic32mx7mmb/nsh. + In this configuratin, the NSH 'msconn' command will connect the + mass storage device to the host; the 'msdis' command will + disconnect the device. The first 'msconn' works perfectly. + However, when attempting to re-connect, the second 'msconn' + command does not command properly: Windows reports an + unrecognized device. Apparently, some state is being properly + reset when the mass storage device is disconnected. Shouldn't + be hard to fix. Status: Open - Priority: High + Priority: Medium o Hitachi/Renesas SH-1 (arch/sh/src/sh1) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |