Re: USB Client Driver loading in WCE 5.0
- From: venkatyv <venkatyv@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 24 Dec 2008 22:59:01 -0800
Hi,
I am also working on similar kind of USB to Ethernet adaptor.
I am working on OMAP3530 platform with Windows CE 6.0 in debug version.
Board has USB OTG port and it was connected to D-Link hub. I am trying to
integrate Davicom's DM9601 USB-to-Ethernet adaptor to my system by connecting
it to
hub.OTG port is working perfectly with USB HID devices like keyboard, mouse
and Mass storage device. Board has another ethernet port which also working
perfectly and able to debug with Platform Builder.
I can’t open “Network and Dial-up connections” dialog box. I can’t open the
network setting by clicking on the toolbar icon or even ipconfig command is
not exiting.
Can any one suggest me about the problem i am facing. Here is the log i got
in Platform Builder in debug mode.
**********************------------While loading
DM9USB.dll---------------************************************************************************
PB Debugger Loaded symbols for
'E:\WINCE600\OSDESIGNS\EVM_3530\EVM_3530\RELDIR\TI_EVM_3530_ARMV4I_DEBUG\DM9USB.DLL'
156460 PID:400002 TID:c50002 ==>NdisIMRegisterLayeredMiniport:
NdisWrapperHandle D27DE410
156460 PID:400002 TID:c50002 ==>ndisRegisterMiniportDriver:
NdisWrapperHandle D27DE410
156460 PID:400002 TID:c50002 <==ndisRegisterMiniportDriver: MiniBlock
D27DE490
156460 PID:400002 TID:c50002 <==NdisIMRegisterLayeredMiniport: MiniBlock
D27DE490, Status 0
156460 PID:400002 TID:c50002 OSAXST1: >>> Loading Module 'dm9usb.dll'
(0x892DCEB8) at address 0xC1070000-0xC1080000 in Process 'NK.EXE' (0x872F1AA0)
PB Debugger Loaded symbols for 'SDHC.DLL'
156842 PID:400002 TID:c50002 ==============================================
156842 PID:400002 TID:c50002 Davicom Semiconductor, Inc.
156842 PID:400002 TID:c50002 Based USBDrv Version : 5.0.0.0
156842 PID:400002 TID:c50002 USBDrv Release Date : 2008/03/14
156842 PID:400002 TID:c50002 ==============================================
156842 PID:400002 TID:c50002 ==>NdisInitializeWrapper
156842 PID:400002 TID:c50002 <==NdisInitializeWrapper
156842 PID:400002 TID:c50002 ==>NdisIMRegisterLayeredMiniport:
NdisWrapperHandle D3D003B0
156842 PID:400002 TID:c50002 ==>ndisRegisterMiniportDriver:
NdisWrapperHandle D3D003B0
156842 PID:400002 TID:c50002 <==ndisRegisterMiniportDriver: MiniBlock
D3D00430
156842 PID:400002 TID:c50002 <==NdisIMRegisterLayeredMiniport: MiniBlock
D3D00430, Status 0
**********************------------When i connected the USB-to-Ethernet
adaptor to the system.---------------*************************************
290074 PID:400002 TID:4780002 CExternalHub::: Get Data value 0x2,
fTransferDone 1
290074 PID:400002 TID:4780002 Abort Transfer for Device Address 0x1
290074 PID:400002 TID:4780002 MUSB: CHub(Root tier
1)::HubStatusChangeThread - port 1, change = 0x0001, status = 0x0101
290258 PID:400002 TID:4780002 Abort Transfer for Device Address 0x1
290258 PID:400002 TID:4780002 CHub::ResetAndEnablePort
290512 PID:400002 TID:4780002 CExternalHub::: Get Data value 0x2,
fTransferDone 1
290512 PID:400002 TID:4780002 Abort Transfer for Device Address 0x1
290612 PID:400002 TID:4780002 Abort Transfer for Device Address 0x1
290612 PID:400002 TID:4780002 CHub::HubStatusChangeThread - device attached
on port 1
290612 PID:400002 TID:4780002 MUSB: +CHub(Root tier 1)::AttachDevice - port
= 1, fIsLowSpeed = 0, fIsHighSpeed =0
290612 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0
290612 PID:400002 TID:45a0002 EP 0 has been setup
290612 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0
290612 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0
290645 PID:400002 TID:4780002 CExternalHub::: Get Data value 0x2,
fTransferDone 1
290645 PID:400002 TID:4780002 Abort Transfer for Device Address 0x1
290945 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures = 0
290945 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0
290945 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures = 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures = 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0
290958 PID:400002 TID:4780002 MUSB: CHub(Root tier 1)::AttachDevice -
Select Configuration 0 on DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE step
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY, failures
= 0
290958 PID:400002 TID:4780002 CHub(tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures = 0
290958 PID:400002 TID:45a0002 CSR0 RxStall Error
290958 PID:400002 TID:45a0002 Halt and need to do some data toggle
290958 PID:400002 TID:4780002 MUSB: CFunction::SetOrClearFeature -
recipient = 0, wIndex = 0, set/clear = 0x3, feature = 0x3, FAILED
290958 PID:400002 TID:4780002 SET FEATURE USB_FEATURE_B_HNP_ENABLE is Failed
290958 PID:400002 TID:4780002 USBDAttachProc with address 2
290958 PID:400002 TID:4780002 m_deviceInfo =>
290958 PID:400002 TID:4780002 dwCount = 0x20
290958 PID:400002 TID:4780002 USB_DEVICE_DESCRIPTOR:
290958 PID:400002 TID:4780002 bLength = 0x12
290958 PID:400002 TID:4780002 bDescriptorType = 0x1
290958 PID:400002 TID:4780002 bcdUSB = 0x110
290958 PID:400002 TID:4780002 bDeviceClass = 0x0
290958 PID:400002 TID:4780002 bDeviceSubClass = 0x0
290958 PID:400002 TID:4780002 bDeviceProtocol = 0x0
290958 PID:400002 TID:4780002 bMaxPacketSize0 = 0x8
290958 PID:400002 TID:4780002 idVendor = 0xa46
290958 PID:400002 TID:4780002 idProduct = 0x9601
290958 PID:400002 TID:4780002 bcdDevice = 0x101
290958 PID:400002 TID:4780002 iManufacturer = 0x1
290958 PID:400002 TID:4780002 iProduct = 0x2
290958 PID:400002 TID:4780002 iSerialNumber = 0x3
290958 PID:400002 TID:4780002 bNumConfigurations = 0x1
290958 PID:400002 TID:4780002 ==>NdisIMInitializeDeviceInstanceEx: Driver
D3D00430, Instance C107D284, Context 00000000
290958 PID:400002 TID:4780002 ==>ndisIMInitializeDeviceInstance: Miniport
D3D036D8, Context 00000000
290958 PID:400002 TID:4780002
290958 PID:400002 TID:4780002 ndisMInitializeAdapter: Miniport D3D036D8,
290958 PID:400002 TID:4780002 ==>ndisQueueMiniportOnDriver: Miniport
D3D036D8, MiniBlock D3D00430
290958 PID:400002 TID:4780002 <==ndisQueueMiniportOnDriver: Miniport
D3D036D8, MiniBlock D3D00430, rc 1
290958 PID:400002 TID:4780002 (+)DM9::MiniportIntialize()
290958 PID:400002 TID:4780002 (+)NIC_DRIVER_USB::MiniportInitialize
290958 PID:400002 TID:4780002 === Davicom (_DeviceEntry.)
290958 PID:400002 TID:4780002 +USBD:OpenPipe, EP: 0x81, MaxPkt: 64, Type:
Bulk
290958 PID:400002 TID:45a0002 EP 0 has been setup
290958 PID:400002 TID:4780002 -USBD:OpenPipe success, hPipe = D5265FF0
290958 PID:400002 TID:4780002 +USBD:OpenPipe, EP: 0x2, MaxPkt: 64, Type: Bulk
290958 PID:400002 TID:4780002 MUSBMHDRC issue - BULK OUT pipe need to force
to run at DMA 0
290958 PID:400002 TID:45a0002 EP 0 has been setup
290958 PID:400002 TID:4780002 -USBD:OpenPipe success, hPipe = D5266130
290958 PID:400002 TID:4780002 ==============================================
290958 PID:400002 TID:4780002 Davicom Semiconductor, Inc.
290958 PID:400002 TID:4780002 Package Version : 3.0.0.6
290958 PID:400002 TID:4780002 Driver Version : 1.0.071219.601
290958 PID:400002 TID:4780002 ==============================================
290958 PID:400002 TID:4780002
(+)(-)NIC_DEVICE_OBJECT::InitialConfigurations()
290958 PID:400002 TID:4780002 ==>NdisMSetAttributesEx: Miniport D3D036D8
291290 PID:400002 TID:4780002 SROM:
291290 PID:400002 TID:4780002 00
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002
291290 PID:400002 TID:4780002 08
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002 --
291290 PID:400002 TID:4780002
291290 PID:400002 TID:4780002 DATA:
291290 PID:400002 TID:4780002 00
291290 PID:400002 TID:4780002 60
291290 PID:400002 TID:4780002 6E
291290 PID:400002 TID:4780002 00
291290 PID:400002 TID:4780002 03
291290 PID:400002 TID:4780002 7F
291290 PID:400002 TID:4780002 01
291290 PID:400002 TID:4780002 54
291290 PID:400002 TID:4780002
291290 PID:400002 TID:4780002 46
291290 PID:400002 TID:4780002 0A
291290 PID:400002 TID:4780002 01
291290 PID:400002 TID:4780002 96
291290 PID:400002 TID:4780002 00
291290 PID:400002 TID:4780002 00
291290 PID:400002 TID:4780002 F0
291290 PID:400002 TID:4780002 01
291290 PID:400002 TID:4780002
291290 PID:400002 TID:4780002 (+)3 of 5-
291290 PID:400002 TID:4780002 (-)3 of 5-
291290 PID:400002 TID:4780002 [9USB-]Link=0
291290 PID:400002 TID:4780002 Lnk-Fail-
291290 PID:400002 TID:4780002 [NCNSPHY17:00,00,F010]
291290 PID:400002 TID:4780002 Fail(PHY@ 0, 1) &&
291290 PID:400002 TID:4780002 Fail(NSR@ 0,1,[NEQ:0])
291290 PID:400002 TID:4780002
291290 PID:400002 TID:4780002 (+)5 of 5-
291290 PID:400002 TID:4780002 RegisterConfigurations: DeviceOnSetupFilter(0)
291290 PID:400002 TID:4780002 (-)5 of 5-
291290 PID:400002 TID:4780002 [9USB-]Link=0
291290 PID:400002 TID:4780002 Lnk-Fail-
291290 PID:400002 TID:4780002 [NCNSPHY17:00,00,F010]
291290 PID:400002 TID:4780002 Fail(PHY@ 0, 2) &&
291290 PID:400002 TID:4780002 Fail(NSR@ 0,2,[NEQ:0])
291290 PID:400002 TID:4780002
291290 PID:400002 TID:4780002 @DriverStart@MiniportInitialize.
291290 PID:400002 TID:4780002 (+)DM9USB::DeviceStart()
291290 PID:400002 TID:4780002 DM9USB::DeviceEnableReceive
291290 PID:400002 TID:4780002 [DM9USB: DM9_RXCR=33
291290 PID:400002 TID:4780002 (-)DM9USB::DeviceStart()
291290 PID:400002 TID:4780002 (-)NIC_DRIVER_USB::MiniportInitialize
291290 PID:400002 TID:4780002 (-)DM9::MiniportIntialize()
291290 PID:400002 TID:4780002 MiniportSetInformation:PACKET_FILTER:
DeviceOnSetupFilter(0x0000000B)
291290 PID:1f70002 TID:4780002 [NOTIFY] HandleSystemEvent 5 none
291290 PID:400002 TID:4780002 <==ndisIMInitializeDeviceInstance: Miniport
D3D036D8, Context 00000000, Status 0
291290 PID:400002 TID:4780002 <==NdisIMInitializeDeviceInstanceEx: Driver
D3D00430, Instance C107D284, Context 00000000, Status 0
291290 PID:400002 TID:4780002 MUSB: -CHub(Root tier 1)::AttachDevice - port
= 1, fIsLowSpeed = 0, address = 2
291290 PID:400002 TID:5f0000a NDISPWR:: BIND notification for adapter
[DM9USB1]
293397 PID:400002 TID:28a0002 [9USB-]Link=4
293397 PID:400002 TID:28a0002 Send connection!
293397 PID:400002 TID:28a0002 LnkOn-
293408 PID:400002 TID:28a0002 [NCNSPHY17:08,40,F014]
293408 PID:400002 TID:28a0002 On(PHY@ 1, 2) &&
293408 PID:400002 TID:28a0002 On(NSR@ 1,2,[neq:0])
293408 PID:400002 TID:28a0002
295398 PID:400002 TID:28a0002 [9USB-]Link=4
295398 PID:400002 TID:28a0002 LnkOn-
295398 PID:400002 TID:28a0002 [NCNSPHY17:08,40,8018]
295398 PID:400002 TID:28a0002 On(PHY@ 2, 2) &&
295398 PID:400002 TID:28a0002 On(NSR@ 2,2,[neq:0])
295398 PID:400002 TID:28a0002
300076 PID:400002 TID:23e0006 IPDispatchDeviceControl returned Status 103
Thanks,
Venkat
"tpandey02@xxxxxxxxx" wrote:
On Oct 20, 10:03 pm, "Michel Verhagen (eMVP)" <mic...@xxxxxxxxxx>.
wrote:
This is when USBD loads. What happens when you plug in the device? No
messages then? If you don't get any debug messages from USBD with all
debug zones enabled when you plug in the device, then something is wrong
with your USB driver. Did you try plugging in a mouse (if you have USB
HID in your image) or a USB disk (if you have USB Storage in your
image)? Does that work? If not, fix that first.
Good luck,
Michel Verhagen, eMVP
Check out my blog:http://GuruCE.com/blog
GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.
tpande...@xxxxxxxxx wrote:
On Oct 20, 1:39 pm, "Michel Verhagen (eMVP)" <mic...@xxxxxxxxxx>
wrote:
Those "debug" messages are coming from a retail image. Build a debug
image, download it to your device, enable debug zones for USBD and look
at the output. Without it it'll be hard to tell you what's wrong (with
it it will be very easy).
Good luck,
Michel Verhagen, eMVP
Check out my blog:http://GuruCE.com/blog
GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.
tpande...@xxxxxxxxx wrote:
On Oct 19, 9:54 pm, "Michel Verhagen (eMVP)" <mic...@xxxxxxxxxx>- Show quoted text -
wrote:
Ok, but you are talking about USB function in your first message.Here are the debug messages .I have this USB ethernet adaptor and when
Normally phones don't support USB host, so plugging a device (as in a
mouse or other USB device) into your phone usually doesn't work. Phones
normally "act" like a USB device (like a hard drive, serial port, modem)
when you plug the phone into a PC.
Can you tell us what kind of device you are plugging into your phone?
Also show us debug messages, without it we can't say much.
Please also readhttp://guruce.com/blogpost/howtoaskquestionsonnewsgroups
Good luck,
Michel Verhagen, eMVP
Check out my blog:http://GuruCE.com/blog
GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.
tpande...@xxxxxxxxx wrote:
On Oct 19, 3:30 pm, "Michel Verhagen (eMVP)" <mic...@xxxxxxxxxx>- Show quoted text -
wrote:
Looks like you're confusing USB Function with USB Host.I am sorry about my terminology Michel.I know about the BSP and I
What does "plug this device into my bsp" and "unplug this device from my
bsp" mean?
A BSP is a board support package, it is a set of drivers and low level
kernel code that is used as a layer between the OS and the hardware.
Plugging something in a BSP doesn't make a whole lot of sense.
Tell us a bit more about your system and we may be able to deduct the
correct terminology from your situation.
Good luck,
Michel Verhagen, eMVP
Check out my blog:http://GuruCE.com/blog
GuruCE
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.
tpande...@xxxxxxxxx wrote:
Hi All,
I am working on integrating a 3rd party USB Client driver integration
into our BSP.
I have never worked on USB driver before.I have the registry keys
given to us by third party and that tells like it is a client driver.
I went through the msdn about it but could not get much about it.
I got to know that these drivers should be loaded by USB EHCI driver.
When I plug this device into my bsp I see as USB_FN and RNDISFN driver
unloaded and USB_EHCI and USBD loaded.I am not sure what should happen
next coz I didnt see any other debug messages.
When I unplug this device from my bsp I see as USB_FN and RNDISFN
driver loaded and USB_EHCI and USBD unloaded.
Can anybody help?
T Pandey
should not have used this term for plugging and unplugging.
I meant plugging and unplugging the USB device into my Phone device
that I am working on.
And the rest of the story remains same.I was told that EHCI will read
the registry entries for this driver when it will be plugged into the
phone device and will try loading that but I don't see any other debug
messages except the one I told above.
T Pandey- Hide quoted text -
I plug this into my device I got these debug messages.
Unloaded symbols for 'C:\FW\USBETH\FENWAY\WM\RELEASE
\WPC_QCMSM_RETAIL_FDOAAPAA\WPC\RNDISFN.DLL'
Unloaded symbols for 'C:\FW\USBETH\FENWAY\WM\RELEASE
\WPC_QCMSM_RETAIL_FDOAAPAA\WPC\MSM7X00_USBFN.DLL'
Loaded symbols for 'C:\FW\USBETH\FENWAY\WM\RELEASE
\WPC_QCMSM_RETAIL_FDOAAPAA\WPC\MSM7X00_EHCI.DLL'
Loaded symbols for 'C:\FW\USBETH\FENWAY\WM\RELEASE
\WPC_QCMSM_RETAIL_FDOAAPAA\WPC\USBD.DLL'
and when I unplug I got these messages:
Unloaded symbols for 'C:\FW\USBETH\FENWAY\WM\RELEASE
\WPC_QCMSM_RETAIL_FDOAAPAA\WPC\USBD.DLL'
Unloaded symbols for 'C:\FW\USBETH\FENWAY\WM\RELEASE
\WPC_QCMSM_RETAIL_FDOAAPAA\WPC\MSM7X00_EHCI.DLL'
Loaded symbols for 'C:\FW\USBETH\FENWAY\WM\RELEASE
\WPC_QCMSM_RETAIL_FDOAAPAA\WPC\MSM7X00_USBFN.DLL'
Loaded symbols for 'C:\FW\USBETH\FENWAY\WM\RELEASE
\WPC_QCMSM_RETAIL_FDOAAPAA\WPC\RNDISFN.DLL'
This USB device has a mini B connector and the phone has a mini AB
connector and the phone is working as a host I assume.
Pardon me if I missed something.
T Pandey- Hide quoted text -
Hi Michel,
I enabled the debug zones for USBD and I am getting only two messages.
1380011 PID:855b2266 TID:a4bbe8a6 USBD: DLL attach
1380013 PID:855b2266 TID:a4bbe8a6 +USBD:HcdAttach, hcd: 0x7BCE0
and here is the call stack for this..
USBD!DllMain(void * 0x84b841f8, unsigned long 0x00000001, void *
0x00000000) line 150
USBD!_DllMainCRTStartup() line 33 + 16 bytes
COREDLL!CallEntry() line 61
COREDLL!_CallDllMains() line 71 + 12 bytes
COREDLL!CallDllMains() line 105 + 16 bytes
COREDLL!int_LoadLibraryExW() line 607 + 12 bytes
COREDLL!stub_LoadLibraryExW() line 352
COREDLL!xxx_LoadDriver() line 2201
MSM7X00_EHCI!CDeviceGlobal::Initialize(void * 0x003ba170) line 112 +
8 bytes
MSM7X00_EHCI!CEhcd::DeviceInitialize() line 141 + 12 bytes
MSM7X00_EHCI!HcdMdd_CreateHcdObject(void * 0x003b9f20, void *
0x0007bbc0, const unsigned short * 0x7642f470, unsigned char *
0x483c6100, unsigned long 0x00000036) line 263 + 28 bytes
MSM7X00_EHCI!InitializeEHCI(_SEHCDPdd * 0x003b9f20, const unsigned
short * 0x7642f470) line 316 + 32 bytes
MSM7X00_EHCI!HcdPdd_Init(unsigned long 0x7642f470) line 374 + 12
bytes
MSM7X00_EHCI!HCD_Init(unsigned long 0x7642fa44) line 365 + 8 bytes
DEVMGR!LaunchDevice() line 591 + 20 bytes
DEVMGR!I_ActivateDeviceEx() line 1734 + 36 bytes
DEVMGR!DM_ActivateDeviceEx() line 105
COREDLL!xxx_ActivateDeviceEx() line 50
MSM_OTG!DeviceFolder::LoadDevice() line 163 + 28 bytes
MSM_OTG!USBOTG::LoadUnloadClientDriver() line 392
MSM_OTG!USBOTG::LoadUnloadHCD() line 403 + 16 bytes
MSM_OTG!Cl13611OTG::LoadUnloadHCD(int 0x00000001) line 433 + 12 bytes
MSM_OTG!Cl13611OTG::NewStateAction(USBOTG_STATES USBOTG_a_wait_bcon,
_USBOTG_OUTPUT {...}) line 684 + 44 bytes
MSM_OTG!USBOTG::EnterState() line 520
MSM_OTG!USBOTG::EventNotification() line 716
MSM_OTG!Cl13611OTG::EventNotification() line 698 + 8 bytes
MSM_OTG!Cl13611OTG::ISTProcess() line 778
MSM_OTG!CIST::ThreadRun() line 123
MSM_OTG!CMiniThread::ThreadProc(void * 0x00079ffc) line 156 + 24
bytes
COREDLL!ThreadBaseFunc() line 634
Nothing else.
T Pandey- Hide quoted text -
- Show quoted text -
Michel,
Seems to be something wrong in the USB driver only coz I am getting
the same retail messages even if I am connecting a USB mass storage
driver.I presume I should get something like usbmsc.dll gets loaded/
unloaded.
Please correct me If I am wrong.
As suggested I put breakpoints in USBD where it exactly loads and
unloads the client driver but the break points never got hit I got
straight retails messages.
T Pandey
- Prev by Date: 3rd Party USB-to-Ethernet Adaptor,
- Next by Date: RE: CE6 QFE after M08 breaks D3DM driver?
- Previous by thread: 3rd Party USB-to-Ethernet Adaptor,
- Next by thread: PowerDown question
- Index(es):
Relevant Pages
|
Loading
