(2) log meesage : When usb in platform, system boot up.Ĭi_hdrc ci_hdrc.1: doesn't support gadgetĬi_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 1Ĭi_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00 Sd 2:0:0:0: Assuming drive cache: write through Scsi 2:0:0:0: Direct-Access SanDisk Cruzer Micro 0.1 PQ: 0 ANSI: 2 Usb-storage 1-1.2:1.0: USB Mass Storage device detected Usb 1-1.2: Manufacturer: SanDisk Corporation Usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Usb 1-1.2: New USB device found, idVendor=0781, idProduct=5151 (1) log message : After system boot up, the usb disk plug in # usb 1-1.2: new high-speed USB device number 7 using ci_hdrc It's can not show SanDisk USB drive information in Android 6.0.1 (Setting/ Storage&USB/). The USB drive information will be show in Andorid 6.0.1 (Setting/ Storage&USB/). I try again the Android 6.0.1 Demo image on an SABRE-SD demo board. Note: If this post answers your question, please click the Correct Answer button. So, the recommendation is getting familiar with the 'sm' command in Android as it seems to provide several function for storage devices. the packaged explorer does not have the ability to adopt or change permissions. Then in a debug session do "sm set-force-adoptable true"Īt this point you need an application that can set permissions. Settings -> Developer Options -> Select USB Configuration -> Settings -> About phone (or tablet) -> Touch 5 times on Build Number to enable Developer optionsĢ. You can enable developer options and enable USB features by following below stepsġ. So don't expect the OTG port to be enumerated until the DT is changed. It was found that on our prebuilt binaries set it to MTP mode.īut then it seems that USB OTG support is not supported by the device tree. It seems by default (in MM) Android sets USB to Charge only mode. The original configuration of fstab may just used for OTG/USB0 on demo board, as USB1 are not used on sabresd-im圆dq board? We just need to update it according to our HW change in projects.Īccording with AE team, any USB device has to be "adopted" in order to appear as a storage device on MM.Īdditional tests were performed in order to see if they have any deviation from defaults.
The data'0x2184200' has been defined for USB1 in the 'im圆qdl.dtsi(?)' file of Kernel4.1.5. Firstly, we cound not use FIle Explore to access any U-disk. In our project, we use sabresd-im圆dq as base. "The root cause if that if you need host1, you need change eescale to host1 then android vold can know this.Ĭhange /devices/soc0/soc.0/2100000.aips-bus/b/ci_hdrc.0* to Jim.LIN, NXP's guy, gave the correct answer. How to setting or modify parameter for mount USB in host USB port?
0 kommentar(er)
