Udisk connected with OTG Host is not able to access.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Udisk connected with OTG Host is not able to access.

2,379 Views
lisztkao
Contributor II

Hi

     I'v a customed board with MX6DQ,we need to access flash disk plugged in otg-host port. However, it's freeze/hangs on while type ls command in console. Any suggestions will be appreciated.

My customed board info:

1).Android 4.4.2

2).Usb OTG ID pin has been pulled down to ground by hardware.

3).There are two of usb ports, usb1 is otg-usg port and usb2 is normal usb port.

mount command info:

/dev/fuse /mnt/media_rw/udisk fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

init.rc

service fuse_udisk /system/bin/sdcard -u 1023 -g 1023 -w 1023 -d /mnt/media_rw/udisk /storage/udisk

  class late_start

  disabled

fstab.freescale

/devices/platform/fsl-ehci.0/usb1 /mnt/media_rw/udisk vfat defaults voldmanaged=udisk:auto

/devices/platform/fsl-ehci.1/usb2/2-1/2-1.1 /mnt/media_rw/udisk1 vfat defaults voldmanaged=udisk1:auto

/devices/platform/fsl-ehci.1/usb2/2-1/2-1.2 /mnt/media_rw/udisk2 vfat defaults voldmanaged=udisk2:auto

/devices/platform/fsl-ehci.1/usb2/2-1/2-1.3 /mnt/media_rw/udisk3 vfat defaults voldmanaged=udisk3:auto

/devices/platform/fsl-ehci.1/usb2/2-1/2-1.4 /mnt/media_rw/udisk4 vfat defaults voldmanaged=udisk4:auto

Labels (3)
4 Replies

1,521 Views
CarlosCasillas
NXP Employee
NXP Employee

Hi,

I have tested Android 4.4.2 on Sabre-SD board (iMX6Q based) which has OTG port, and the USB stick is mounted properly. Could you please test the OTG port in Host mode with a different supported USB Device (for example, a Mouse)?

Hope this will be useful for you.

Best regards!

/Carlos

0 Kudos
Reply

1,521 Views
lisztkao
Contributor II

Hi Carlos

The destination /devices/platform/fsl-ehci.0/usb1 was mounted to /mnt/media_rw/udisk. (Please refer to following log)

I found there are two of symlink /mnt/media_rw/udisk point to different target path.

The first one is in the ~/imx6/etc/init.rc.

mkdir /mnt/media_rw/udisk 0755 system system

symlink /mnt/media_rw/udisk /storage/udisk

The second is in the ~/device/fsl/PROJECT/init.rc

mkdir /storage/udisk 0000 system system

mkdir /mnt/media_rw/udisk 0666 system system

symlink /mnt/media_rw/udisk /udisk

If two of line in first file be commented, this error will be fixed.

It just different "SYMBOL" path point at the same source path, doesn't it?

Why? Any idea?

log

-----------------------------------------------------------------------------------------------------------------------------------------------

usb 1-1: new high speed USB device number 6 using fsl-ehci

usb 1-1: device v1307 p0163 is not supported

scsi7 : usb-storage 1-1:1.0

scsi 7:0:0:0: Direct-Access Ut163 USB2FlashStorage 0.00 PQ: 0 ANSI: 2

sd 7:0:0:0: [sdc] 1007616 512-byte logical blocks: (515 MB/492 MiB)

sd 7:0:0:0: [sdc] Write Protect is off

sd 7:0:0:0: [sdc] Mode Sense: 00 00 00 00

sd 7:0:0:0: [sdc] Asking for cache data failed

sd 7:0:0:0: [sdc] Assuming drive cache: write through

sd 7:0:0:0: [sdc] Asking for cache data failed

sd 7:0:0:0: [sdc] Assuming drive cache: write through

sdc:

D/Vold ( 2261): Volume udisk state changing 0 (No-Media) -> 1 sd 7:0:0:0: [sdc] Asking for cache data failed

(Idle-Unmounted)

D/MountService(sd 7:0:0:0: [sdc] Assuming drive cache: write through

2629): volume state changed for sd 7:0:0:0: [sdc] Attached SCSI removable disk

/storage/udisk (removed -> unmounted)

D/MountService( 2629): sendStorageIntent Intent { act=android.intent.action.MEDIA_UNMOUNTED dat=file:///storage/udisk (has extras) } to UserHandle{-1}

W/Vold ( 2261): Volume is idle but appears to be mounted - fixing

D/Vold ( 2261): Volume udisk state changing 1 (Idle-Unmounted) -> 4 (Mounted)

D/MountService( 2629): volume state changed for /storage/udisk (unmounted -> mounted)

D/MountService( 2629): sendStorageIntent Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///storage/udisk (has extras) } to UserHandle{-1}

0 Kudos
Reply

1,521 Views
CarlosCasillas
NXP Employee
NXP Employee

Hi,

"It just different "SYMBOL" path point at the same source path, doesn't it"

It should not exist this case in default BSP.  When system.img is compiled and packaged, there is only one init.rc in system. You can check your run-time init.rc.


Hope this will be useful for you.
Best regards!
/Carlos

1,521 Views
CarlosCasillas
NXP Employee
NXP Employee

Hi,

We are internally reviewing your case. We will post an update as soon as getting news.

Best regards!

/Carlos

0 Kudos
Reply