jimmyyuyu

完，机制完全不一样，呵呵

我这个BSP是每次UFN_ATTACH之前先UFN_DETACH

18545862

Veabol兄弟你是什么硬件平台？我一直怀疑我的USB Fuction驱动有问题，就是现在不知道从哪里下手改

kxywnljz

CE5.0, S3C2416

xw99

哈，跟s3c2410差别大吗？能否发给我一份你的SD卡驱动和USB Fuction controller驱动的源码还有Platform.reg文件？

我估计咱俩的东西可以通用，拜托兄弟帮个忙吧，分数双手奉上，不够我再去赚，这个问题郁闷我好些天了

yangyong9608@163.com

sgyao

#18楼 问题一 确实每个都是这样的，以前没注意到 CreateFile返回的句柄 跟DeviceIOControl里的参数Handle确实是不同的数值，中间好像经过了某种映射了，但是可以确定这个现象是正确的

问题二 我感觉像是某个其他的驱动把我OpenStore的DSK1给关掉了，因为我这里出现了SD分区出现又消失的过程，从下面的调试信息也可以看到这个现象，似乎又回到了dismount/mount被频繁触发的问题上来了，走进了死胡同

SC2440UsbFn!HandleUSBEvent: UFN_ATTACH
SC2440UsbFn!HandleUSBEvent: Reset
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 1;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 1
SC2440UsbFn!HandleUSBEvent: EP0_OUT_PACKET_RDY
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 1;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SDMemory: +-SMC_Close
SDMemory: +-SMC_Open
SDMemory: +SMC_IOControl Handle 7822816
DISK_IOCTL_GETINFO
SDMemory: -SMC_IOControl returning 1
SDMemory: +SMC_IOControl Handle 7822816
IOCTL_DISK_DEVICE_INFO
SDMemory: -SMC_IOControl returning 1
SDMemory: +SMC_IOControl Handle 7822816
IOCTL_DISK_GET_STORAGEID
SDMemory: -SMC_IOControl returning 0
SDMemory: +SMC_IOControl Handle 7822816
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 1;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 1
SC2440UsbFn!HandleUSBEvent: EP0_OUT_PACKET_RDY
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 1;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 1;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 1;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 1
SC2440UsbFn!HandleUSBEvent: EP0_OUT_PACKET_RDY
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 1;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 1;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 1
SC2440UsbFn!HandleUSBEvent: EP0_OUT_PACKET_RDY
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 11;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: EP0_INT_INTR
SC2440UsbFn!HandleUSBEvent: Status, 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
UsbMsFn!BOT_HandleCBW: Length: 0x0008 Flags: 0x80 CBWLen: 0xa
UsbMsFn!STORE_IsCommandSupported: command 0x25
UsbMsFn!STORE_IsCommandSupported: READ CAPACITY
UsbMsFn!STORE_ExecuteCommand: command 0x25
UsbMsFn!STORE_ExecuteCommand: READ CAPACITY
UsbMsFn!BOT_ExecuteCB: Command : passed
UsbMsFn!BOT_HandleCBW: request length = 8
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 2;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 0;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 2;bUSBBusIrqStat = 0
SC2440UsbFn!HandleUSBEvent: bEpIrqStat = 10;bUSBBusIrqStat = 0
UsbMsFn!BOT_HandleCBW: Length: 0x0200 Flags: 0x80 CBWLen: 0xa
UsbMsFn!STORE_IsCommandSupported: command 0x28
UsbMsFn!STORE_IsCommandSupported: READ (10)
UsbMsFn!STORE_ExecuteCommand: command 0x28
UsbMsFn!STORE_ExecuteCommand: READ (10)
UsbMsFn!ProcessScsiRead10: starting LBA/sector = 0, transfer length = 1 (sectors)
UsbMsFn!ProcessScsiRead10: ===g_hStore = 3485743006
g_fLegacyBlockDriver = 0 DISK_IOCTL_READ = 2 IOCTL_DISK_READ = 482312 dwIoControlCode = 482312
UsbMsFn!ProcessScsiRead10: IOCTL_DISK_READ failed; error = 160
UsbMsFn!STORE_ExecuteCommand: failed to execute command 0x28
UsbMsFn!BOT_ExecuteCB: Command : failed

调试信息显示，红色字体部分好像并非usb mass storage client驱动调用的SDMemory接口函数

这就奇怪了，怎么还会有其他驱动再usb dismount之后自动重新mount SD卡分区呢

sdsongth

不好意思，公司的东西，不方便给的，只能给你提供一些思路。

ggggds

兄弟，两个驱动而已，又不是要整个BSP，不用那么谨慎吧

这些驱动很多人都有的，有些开发板也带了，我就是想省两个钱而已

那我再等等吧，谢谢你

lgj99988

不好意思！最近忙自己事情一直没看到帖子！你这个是什么问题呀？我当时是用u盘做的，不知道你的sd卡友什么区别？还有我想明白你现在是把sd卡插在wince设备中然后在pc段设别做u盘，还是直接拿sd卡在wince设备中作u盘？这个概念必须清楚！