USB mass storage automount through vold on sitara

Ashwinee Dhakate said:

       usb mass storage support is not enabled in the kernel and usb configuration switch is not enabled in the kernel.

     For that I enabled the CONFIG_SWITCH and CONFIG_USB_ANDROID_MASS_STORAGE then also it was not showing any change.

This feature is used to make available your android device as USB Mass Storage device when connected to Host PC. You will need to add some additional code to support this feature. Please refer to the following forum post for more information:

http://groups.google.com/group/rowboat/browse_thread/thread/c58ad702419ce1fa

Hi Vishveshwar,

    But the build I am using for SITARA doesn't have the directory framework/base/services/java/com/android/server/usb. This usb folder is not there.

Thanks,

Ashwinee

Hi Ashwinee,

It is not clear to me if you want your Sitara to appear as a mass storage device to a PC or if you just want to access a mass storage device from Sitara. Can you confirm?

Jon

Hi Ashwinee,

To access mass storage device you have to add a entry in vold.fstab file. To use device as a mass storage gadget, please apply patch mentioned in the below link.

http://www.gitorious.org/rowboat/kernel/commit/029c9c05bf913cba036d2d18c57a383a24b11ee4

Regards,

Pankaj Bharadiya

Hi Pankaj,

I don't use rowboat just the standard Android releases for TI OMAP devices, but I can manually mount a mass storage device without modifying vold.fstab file.

Jon

Hi Jon,

I want to access mass storage device(USB) from Sitara without adding entry in vold.fstab.

Thanks,

Ashwinee

Hi Ashwinee,

Is the mass storage device detected when you plug it into the sitara? You should see something like ...

usb 1-1: new high speed USB device using ehci-omap and address 5                                            
usb 1-1: New USB device found, idVendor=08ec, idProduct=0008                                                    
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3                                               
usb 1-1: Product: TD Classic 003C                                                                               
usb 1-1: Manufacturer: Memorex                                                                                  
usb 1-1: SerialNumber: 0E3144614362FB22                                                                         
scsi1 : usb-storage 1-1:1.0                                                                                     
scsi 1:0:0:0: Direct-Access     Memorex  TD Classic 003C  5.00 PQ: 0 ANSI: 0 CCS
sd 1:0:0:0: [sda] 2015232 512-byte logical blocks: (1.03 GB/984 MiB)
sd 1:0:0:0: [sda] Write Protect is off
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1
sd 1:0:0:0: [sda] Assuming drive cache: write through
sd 1:0:0:0: [sda] Attached SCSI removable disk

Then to mount you should be able to do something like (assuming a FAT file-system on the mass storage) ...

# mkdir /data/tmp
# mount -t vfat /dev/block/sda1 /data/tmp

Cheers
Jon

By the way, in the above you will see that I am connecting the mass storage to the EHCI host port on the OMAP. However, I have also tried the USB OTG port and this one is also working. My testing is based upon an OMAP4 device, but I don't see why this would not work on a Sitara based device too. Cheers Jon

Hi Pankaj,

I have already mentioned that I don't want to add an entry in vold.fstab. and the patches you have provided are not for my board as I am using TI8168evm.

Thanks,

Ashwinee

Hi Jon,

I am able to mount the device manually. But I want to make the USB mass storage device automount.

Thanks,

Ashwinee