• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 1502 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

USB Mass Storage problem

Mark Meisner
Prodigy 120 points
Other Parts Discussed in Thread: DM3730

I am trying to connect a USB flash drive to my systems OTG port so I can read/write files.  When I connect it I can use a utility to see that it is a FlashDisk at location sda1 and is 126mb.  The problem is after a few seconds, android crashes and reboots.  I have not been able to capture what causes the crash event so far.

The processor I am using is a DM3730 on a custom board.  I have verified the ID pin is low and Vbus is supplied power.  The port itself works because I can issued adb commands and load .apk's from a computer.  USB OTG, Gadget, and mass storage is enabled in the kernel.

I have seen some forum posts about modifying vold.fstab, but that you cannot have more than two entries in the file. I have no nand so am using my sdcard to host the android system.  Would changing that entry from sdcard to usb affect that, as shown here: http://processors.wiki.ti.com/index.php/TI-Android-ICS-PortingGuide#USB_Mass_storage

I have also tried how to install a usb still in the faq (http://processors.wiki.ti.com/index.php/Android_Developer_FAQs#Q:_How_to_get_USB_stick_installed.C2.A0.3F_How_to_install_apk_residing_on_USB_stick.C2.A0.3F) with no luck.

Thanks

  • 0
    TI__Genius 10210 points

    Could you provide the logcat output when you attach the USB disk to the OTG port

  • 0 in reply to Vishveshwar Bhat
    Prodigy 120 points

    The only way I know how to obtain the logcat output is via ADB in real time to my computer.  The problem is I cannot capture these logs AND plug in the USB stick at the same time, because they both use the same port.  Is there a way to save the logcat to the device and have it retained there after the crash and reboot?  I also have access to the UART to USB port which I use to monitor the boot sequence.  Is it possible to redirect the logcat output to that port?

    Thanks

  • 0 in reply to Mark Meisner
    TI__Genius 10545 points

    Quick comment, see Android_Logging_System in next link,

    http://e2e.ti.com/support/embedded/android/f/509/p/243219/851204.aspx

    other option is to add logcat to init.rc using a logger.

  • 0 in reply to Mark Meisner
    TI__Genius 10210 points

    Mark Meisner said:

    The only way I know how to obtain the logcat output is via ADB in real time to my computer.  The problem is I cannot capture these logs AND plug in the USB stick at the same time, because they both use the same port.  Is there a way to save the logcat to the device and have it retained there after the crash and reboot?  I also have access to the UART to USB port which I use to monitor the boot sequence.  Is it possible to redirect the logcat output to that port?

    Thanks

    You can run logcat on the UART console port. You can also run adb over ethernet.

  • 0 in reply to Vishveshwar Bhat
    Prodigy 120 points

    Got logcat working thanks for the tip. Below is the logcat output when I connect the USB stick.  After this point, the system crashes and reboots.

    usb 2-1: new high speed USB device using musb-hdrc and address 2
    usb 2-1: device v1e3d p2092 is not supported
    usb 2-1: New USB device found, idVendor=1e3d, idProduct=2092
    usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    usb 2-1: Product: FlashDisk
    usb 2-1: Manufacturer: USB2.0
    usb 2-1: SerialNumber: 071729002C47F014
    scsi0 : usb-storage 2-1:1.0
    scsi 0:0:0:0: Direct-Access USB2.0 FlashDisk 5.00 PQ: 0 ANSI: 2
    sd 0:0:0:0: [sda] 258048 512-byte logical blocks: (132 MB/126 MiB)
    sd 0:0:0:0: [sda] Write Protect is off
    sd 0:0:0:0: [sda] Assuming drive cache: write through
    sd 0:0:0:0: [sda] Assuming drive cache: write through
    sda: sda1
    sd 0:0:0:0: [sda] Assuming drive cache: write through
    sd 0:0:0:0: [sda] Attached SCSI removable disk