Re: USB host port 2

Hi,

I m still facing the problem. I have connected the USB cable from GSM to
port 3 of USB HUB which is connected Host port1. This is the debug build of
the OS. Here It is failing at
"failure on DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST".

Could you tell me how to fix this issue?

"KeybdDriverInitializeEx: Layout Manager successfully initialized to 1
0x83f4a604: PM:added for timeout support: switch ONthe display 0x83e1789c:
AddToProcessInputLocaleTable: Added process to ProcessInputLocale table,
hProcess = 0x23F714260x83e1789c: Grow Gdi handle table from 64 to 128
0x83e1789c: calibrating 0 point set 0x83e1789c: calibrating 5 point set
0x83e1789c: Maximum Allowed Error 5: 0x83e1789c: Calibration Results:
0x83e1789c: Screen => Mapped 0x83e1789c: ( 320, 240) => ( 318,
240) 0x83e1789c: ( 128, 96) => ( 130, 96) 0x83e1789c: ( 128, 384) => (
127, 384) 0x83e1789c: ( 512, 384) => ( 514, 384) 0x83e1789c: ( 512, 96)
=> ( 511, 96) 0x83e1789c: Maximum error (square of Euclidean distance in
screen units) = 4 0x83e1789c: Oom Low Pages: 0020 Bytes:
00020000 0x83e1789c: Oom Critical Pages: 0014 Bytes: 00014000
0x83e1789c: Oom Low Block Pages: 0004 Bytes: 00004000 0x83e1789c: Oom
Critical Block Pages: 0002 Bytes: 00002000 0x83e1789c: Oom App Wait 8000
(dec ms) 0x83e1789c: Oom AutoOom 0 0x83e1789c: UpdateIdleTimeoutFromRegistry
0x83fc7024: FILESYS: SignalStarted loop = 2 0x83fc7024: FILESYS: Launching
explorer.exe 0x83d31878: InitSharedHeap: 46300000 0 c 0x83d31878:
InitSharedHeap: return 46300060 0x83d31878: AddToProcessInputLocaleTable:
Added process to ProcessInputLocale table, hProcess = 0xC3D31ABA0x83d31878:
Widgets: bm.bmWidth = 0x80 0x83d31878: Widgets: bm.bmHeight = 0x82
0x83fc7024: FILESYS: Launching services.exe 0x83d31878: Entering InitCapEdit
0x83d31878: CAPEDIT registered(49176) 0x83d31878: InitTTButton: 0x83d28d88:
InitSharedHeap: 46300000 0 c 0x83d28d88: InitSharedHeap: return 46300060
0x83fc7024: FILESYS: Done launching apps 0x83fc7024: UNIMODEM: HayesCompat:
order = 0xffffffff 0x83d28d88: [NOTIFY] Module loaded 0x83d02400: [NOTIFY]
Initializing. 0x83d02400: DB:OpenDB fail: DB DB_notify_queue not found
0x83d02400: [NOTIFY] Initialization completed successfully 0x83fc7024:
-DEVICE!DevloadPostInit 0x83fc7024: This device has booted 1 times !!!
0x83d0b820: AddToProcessInputLocaleTable: Added process to ProcessInputLocale
table, hProcess = 0x63D193EE0x83d0b820: Grow Gdi handle table from 128 to 192
0x83cf1000: [NOTIFY] ProcessDatabase::started at local time 01/01/2003
12:00:16 0x83d28d88: CREDSVC: LoadVProviders: There are no virtual type
providers present 0x83d31878: Console redirected to DEBUG for process
0xC3D31ABA 0x83d31878: Grow Gdi handle table from 192 to 256 0x83d31878:
DB:OpenDB fail: DB RecycleData not found 0x83d02400: [TIMESVC DST] System
Started... 0x83d02400: [NOTIFY] CeRunAppAtEvent - clearing system event
registration for \\.\Notifications\NamedEvents\DSTTzChange 0x83d02400:
[NOTIFY] CeRunAppAtEvent - clearing system event registration for
\\.\Notifications\NamedEvents\DSTTimeChange 0x83d02400: [NOTIFY]
RemoveAppRunAtTime::Starting Database Sweep... 0x83d02400: [NOTIFY]
SetUserNotification (or replacing 00000000) 0x83d02400: [NOTIFY]
SetUserNotification::Registring system watch: event 12 app
\\.\Notifications\NamedEvents\DSTTzChange args AppRunAfterTzChange
0x83d02400: [NOTIFY] SetUserNotification (or replacing 00000000) 0x83d02400:
[NOTIFY] SetUserNotification::Registring system watch: event 1 app
\\.\Notifications\NamedEvents\DSTTimeChange args AppRunAfterTimeChange
0x83d02400: [NOTIFY] RemoveAppRunAtTime::Starting Database Sweep...
0x83d02400: [NOTIFY] SetUserNotification (or replacing 00000000) 0x83d02400:
[NOTIFY] SetUserNotification::Setting event semaphore 0x83d02400: [NOTIFY]
ProcessDatabase::started at local time 01/01/2003 12:00:18 0x83d31878: SIP:
(0,0) - (0,0) 0x83ceb468: AddToProcessInputLocaleTable: Added process to
ProcessInputLocale table, hProcess = 0xE3FC70020x83ceb468: MSIM:
IM_ReadRegistry read KB 5 0x83cae55c: Grow Gdi handle table from 256 to 320
0x83cae55c: Widgets: bm.bmWidth = 0x80 0x83cae55c: Widgets: bm.bmHeight =
0x82 0x83cae55c: Explorer(V2.0) taskbar thread started. 0x83cae55c: [NOTIFY]
CeRunAppAtEvent - clearing system event registration for
\\.\Notifications\NamedEvents\TaskbarTimeChangeEvent 0x83cae55c: [NOTIFY]
SetUserNotification (or replacing 00000000) 0x83cae55c: [NOTIFY]
SetUserNotification::Registring system watch: event 1 app
\\.\Notifications\NamedEvents\TaskbarTimeChangeEvent args
AppRunAfterTimeChange 0x83e26d7c: NdisPower:: Successfully register for
notification! 0x83e54000: CHub(External tier 1)::HubStatusChangeThread - port
3, change = 0x0001, status = 0x0101 0x83e54000: CHub(External tier
1)::HubStatusChangeThread - device attached on port 3 0x83e54000:
+CHub(External tier 1)::AttachDevice - port = 3, fIsLowSpeed = 0 0x83e54000:
CHub(External tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0 0x83e54000:
CHub(External tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0 0x83e54000: CHub(External
tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT,
failures = 0 0x83e54000: CHub(External tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures = 0
0x83e54000: CHub::GetDescriptor - forcing descr type 0x0 to 0x1 0x83e54000:
CHub(External tier 1)::AttachDevice - failure on
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST step 0x83e54000:
CHub(External tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 1 0x83e54000:
CHub(External tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures = 1
0x83e54000: CHub(External tier 1)::AttachDevice - failure on
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST step 0x83e54000:
CHub(External tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 2 0x83e54000:
CHub(External tier 1)::AttachDevice - status =
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures = 2
0x83e54000: CHub(External tier 1)::AttachDevice - failure on
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST step 0x83e54000:
CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_FAILED,
failures = 3"

Pls reply me as soon as posssible. Thanks many in advance.

"Paul G. Tobey [eMVP]" wrote:

That's useless information. We don't care what happens when you don't enter
a driver name.

The driver is not being loaded. I'd have to guess as to what the problem
is, but it could be that the client driver requires some registry entries be
present in order for it to work (it has an install program that makes those
or whatever), and you don't have those entries. It could also be that you
have a driver for some device that isn't the device that you've plugged in.
There is still not enough information for a real diagnosis of the problem.
Talk to Sierra Wireless and see what they suggest. Maybe they can provide
you with a DEBUG version of the driver that will tell you what's actually
going wrong...

Paul T.

"mini" <mini@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:81417603-B7E7-4183-98C0-15DC923F9E02@xxxxxxxxxxxxxxxx
Hello,

I included debug messages in Usbd.cpp and I captured it. After installing
the GSM driver provided by the vendor, I clicked OK in the "Unidentified
USB
device" pop-up message, then "Error installing USB driver" pop-up came. I
clicked OK for this.I didnot give any dll name in the editbox box
provided.

Then the following debug message has come.

"Entered USBD: InstallClientDriver
!USBD:InstallClientDriver, error in LoadLibrary(): 126"


If I give driver dll(SWIVSP.dll) name, then the following message has
come.

"Entered USBD: InstallClientDriver
USBInstallDriver is called for driver SWIVSP.dll
!USBD:InstallClientDriver(SWIVSP.dll), error in client driver install
-SierraWireless CE Driver: DllExit, gMemoryCounter = 0"

Is there problem in installing the driver?
Immediate suggestions pls.....


"Paul G. Tobey [eMVP]" wrote:

Yes, you'll have to remove some of the junk that's in your OS to make the
image small enough to run (Internet Explorer is one thing. .NET Compact
Framework and MFC are also big in DEBUG mode). Keep a list of items that
you remove so you won't forget to put them back later...

Paul T.

<sumathik7@xxxxxxxxx> wrote in message
news:1169719742.948214.237720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I apologise... that the log file which I sent was captured in RELEASE
build of the OS.
I tried with debug mode but the nk.bin size was nearly 60MB. I couldnot
check it.
Presently, I configured *UP2OCR* as *0x03020100* and I connected Active
sync to USB Client.

Could you advice how can I debug this?
Do I need to change register configurations?




On Jan 23, 8:54 pm, "Paul G. Tobey [eMVP]" <p space tobey no spam AT
no instrument no spam DOT com> wrote:
That *can't* be all of the debug messages from a DEBUG build of the
OS...


Paul T.

<sumath...@xxxxxxxxx> wrote in
messagenews:1169529157.979028.153070@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello Paul,

Our GSM module is placed in such a way that it is not a plug-n-play
device. So after downloading the image, it identifies the device as
"Unknown USB device". After installing the .CAB file, "Error in
installing USb driver" pop-up has come. I clicked Ok on WinCE side. I
am sorry for repeating the same steps.

On hyperterminal, the following is captured after following the above
steps.

"Resume Device USBF not supported
SWIUSBPowerControl failed to Set bSuspend = 0 at bInterfaceNumber = 0
SierraWireless USB: SendInitControlRequests 1 [0 = CLR, 1 = SET] DTR
successfully!
SWIUSB: Using Default gdwResumeDetectInterval
SIERRAWIRELESS USB: DeviceAttach: gdwIdleTimeout = 0,
gdwResumeDetectInterval = 500"

For testing purpose,I tapped the USB cable from GSM module externally.
I installed the GSM driver .CAB file and then I plugged-in the USB
cable to one of the ports of USB HUB which is connected tohostport1
of Pxa270 processor. There is no such issue.

On hyperteminal , the same debug has come.If I unplug the USB cable
fromhostport1,the following is captured:

"SWIUSB: Interrupt Thread Exit
SWIUSB: BulkInThread Exit
-SierraWireless CE Driver: DllExit, gMemoryCounter = 0"

Only CAB file is provided by the vendor.No registry settings has been
given for the driver.
Only withhostport2, it affects the speed of the entire system after
installing CAB file.

The module is connected via external transceiver USB1T11AMTCX. The
speed pin (pin 9) of the transceiver is
connected to USB_p2_7 (GPIO<41>) of the processor.

1. Do I need to change any configuration forhostport2?
2. Why does it affects the speed of the entire system? Is there
anything related with transceiver?
3. Is there anything to be changed in default registry settings if I
install any vendor's USB driver?

Pls help me. Very Urgent........

Paul G. Tobey [eMVP] wrote:



If the driver was installed properly, you should not have to enter
the
driver name. I think that you've not got the right registry data or
you're
missing the DLL at the time the system is trying to load it. I'm
afraid
that you've either cut out everything from the log that might have
been
useful (we *don't* need the bootloader stuff or anything from before
the
USB
device is connected, but we do need everything after that)...

Paul T.

<sumath...@xxxxxxxxx> wrote in message
news:1169267889.748871.89170@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,

In PXA270 processor, GSM module is connected to USBhostport2 which
is available in PCI Express Mini Card Form. The module is integrated
in
such a way that once the image has come on WinCE side, it identifies
the USB device. "Unidentified USB device" pop-up has come along with
the editbox in which Driver name has to be entered.

I copied the .CAB file provided by the GSM driver(Sierra Wireless)
using ActiveSync to "MyDevice" and I installed the driver. I am sure
the driver I installed in wince is the right one.

After installing, I entered the name of the .dll in the editbox and
clicked OK. Then the "Error installing USB driver xxx.dll" pop-up has
come and I clicked OK. Then the "DeviceAttach" debug message has
come.

Note: After installing the driver, the entire system has become slow
and if I try to open any folder it is taking much time.

Here is my log file:

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1
Built Jan 5 2007 18:30:50 Microsoft Windows CE Ethernet Bootloader
1.7
for the Intel MainstoneII Development Platform Built Jan 5 2007

Press [ENTER] to launch image stored in flash or [SPACE] to cancel.

Initiating image launch in 3 seconds.

Ethernet Boot Loader Configuration:

0) IP address: 0.0.0.0
1) Subnet mask: 0.0.0.0
2) EtherNet Mac Address 0-E-8C-80-7B-7D
3) Boot delay: 3 seconds
4) DHCP: (Enabled)
5) Reset to factory default configuration
6) Launch existing flash resident image at startup
7) Boot device order: SMSC -> PCMCIA0 -> PCMCIA1
8) Debug serialport: FFUART
D) Download image now
L) Launch existing flash resident image now

Enter your selection: d
INFO: Trying to initialize the built-in SMSC NIC...
LAN91Cxxx: Chip Id 9 Revision 2
INFO: MAC address: E00-808C-7D7B
INFO: SMSC LAN91C111 Ethernet controller initialized.
INFO: MAC address: 0-E-8C-80-7B-7D
System ready!
Preparing for download...
INFO: Using device name: 'MAINSTN31613'
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
Got Response from DHCP server, IP address: 10.100.132.67

ProcessDHCP()::DHCP IP Address Resolved as 10.100.132.67, netmask:
255.255.255.0
Lease time: 10800 seconds
Got Response from DHCP server, IP address: 10.100.132.67 No ARP
response in 2 seconds, assuming ownership of 10.100.132.67
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Locked Down Link 1
Src IP 10.100.132.67Port0800 Dest IP 10.100.132.73Port08DE
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
****** OEMVerifyMemory checking physical range [ 0x80000 ==>
0x1A3ED5F
]...
****** FLASH address ******

ÿINFO: FlashErase: erasing flash BCA80000 to BE43FFFF. Please
wait...

...........................................................................­............................
INFO: FlashWrite: writing to flash...
...........................................................................­...........................INFO:
FlashWrite: verifying the data written to flash...
INFO: FlashWrite: flash programmed successfully!
ROMHDR at Address 9CA80044h
INFO: FlashErase: erasing flash BCA40000 to BCA7FFFF. Please wait...
.
INFO: FlashWrite: writing to flash...
INFO: FlashWrite: verifying the data written to flash...
INFO: FlashWrite: flash programmed successfully!
Download successful! Jumping to image at 0x9CA81000 (physical
0x81000)...
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x0000Windows CE Kernel for ARM (Thumb
Enabled) Built on Jun 24 2004 at 18:25:00
ProcessorType=0411 Revision=7
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable =
9ca85ab4
Sp=ffffc7cc
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
OEMIoControl: Unsupported Code 0x10100d4 - device 0x0101 func 53
OEMIoControl: Unsupported Code 0x10100c4 - device 0x0101 func 49
OEMIoControl: Unsupported Code 0x10100c4 - device 0x0101 func 49
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
[ERROR] "PDD_AudioInitialize() FAILED"
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Drivers\BuiltIn\AFD). Driver cannot be unloaded.
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Drivers\BuiltIn\PPP). Driver cannot be unloaded.
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Drivers\BuiltIn\LPCD). Driver cannot be unloaded.
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions
at (Drivers\BuiltIn\DCOMSSD). Driver cannot be unloaded.
Done getting Registry values:
bpp: 0x8
CxScreen: 0x280
CyScreen: 0x1e0
Display Type: LTM035A776C

Display Driver Initialization Complete
Display Driver Initialization Complete
OEMIoControl: Unsupported Code 0x10100fc - device 0x0101 func 63
Lyg.p: Layout Manager successfully initialized to 1
MSIM: IM_ReadRegistry read KB 5
Explorer(V2.0) taskbar thread started.

Posting WM_NETCONNECT(TRUE) message
AUTORAS:: Dialer notifies: [4] [Dialer Connected]

Resume Device USBF not supported
SWIUSBPowerControl failed to Set bSuspend = 0 at bInterfaceNumber = 0
SierraWireless USB: SendInitControlRequests 1 [0 = CLR, 1 = SET] DTR
successfully!
SWIUSB: Using Default gdwResumeDetectInterval SIERRAWIRELESS USB:
DeviceAttach: gdwIdleTimeout = 0, gdwResumeDetectInterval = 500

Eagerly waiting for ur reply.

Thanks n Regards,
mini

Paul G. Tobey [eMVP] wrote:
We can't answer this question; you've not told us enough to do so.
What
debug messages do you get when you plug the device in? Are you
sure
that
you have the right driver for the device on your processor?
.

Loading