Re: USB not detected - help

Hi,

Scenario 1:

If the OS can't load a driver for a connected USB device, the only data that
will pass over the USB bus is the device identification data. After that,
the communication with the device will stop. The data transfer of the device
identificaton will be a very short burst, so there is a big change you miss
it. You might try measuring it with a memory scope set to a one shot trigger
mode. A better indication of the proper identification of the USB device
should be the debug info when the OS get's loaded. If you enable the correct
debugzones in your usb host driver, you should see some information about
the USB device detection during startup, indicating that your GSM is
properly identified.

Scenario 2:

When the driver is loaded, there is communication to and from the device.
That are the spikes you are seeing.

Scenario 3:

Could you be a bit more specific?
Did you copy the driver dll back from the device or did you got it from the
CAB file?
Could you post the lines you added to the bib file and the lines you added
to the registry file.
If you don't connect the device during bootup, does the device boot normally
in that case?
What happens if you connect the device after the OS is loaded?
Try saving the whole registry "with" and "without" the GSM driver installed.
Check for other registry keys besides the one I mentioned.
Try to open the CAB file on your PC. There are special tools on the market
for that. Even a tool like Winzip or Winrar can be used. They give you a
rough idea of the files in the CAB and their size. One of the files is plain
ascii and contains the registry keys that are added to the device registry.

Try to only add the driver file to your OS image. verify on the target
platform if it really is there. Connect your GSM and fill in the driver name
when you get the "Unidentified device popup". See what happens in that case.

regards,

Luc


"mini" <mini@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B53880A2-865E-4F2C-AD0E-8C3BDCCC2E84@xxxxxxxxxxxxxxxx
Hi Luc,

Scenario 1: The GSM module is connected on booting.
I checked with D+ & D- pins of the USB HUB chip: TUSB2046BIVFR. When I
connect the mouse, in D+ and D- pins of the corresponding ports, some
signals
like spikes are coming. But the port in which GSM module is connected, the
D+
pin always stay HIGH, no spikes came.

Scenario 2: GsM module connected after bootup.
D+ and D- pins of the port in which GSM module is connected, spikes are
coming. Without installing the driver, when I plug-out and plug-in again,
the
D+ pin goes to high .

What is the reason for this behaviour? Please explain me as I am not much
aware of hardware.

Scenario 3:
I included the Registry settings in platform.reg and dll path in
platform.bib and I
copied the driver dll to the MainstoneII/Files folder. But I download that
image I got
"Data Abort: Thread=83ce6848 Proc=801263f0 'gwes.exe'
AKY=00000009 PC=01ba7838(pxa27x_lcd.dll+0x00007838)
RA=01ba7878(pxa27x_lcd.dll+0x00007878) BVA=08000010 FSR=00000007
Data Abort: Thread=83ce6848 Proc=801263f0 'gwes.exe'
AKY=00000009 PC=0004c33c(gwes.exe+0x0003c33c)
RA=00054138(gwes.exe+0x00044138) BVA=08000008 FSR=00000007"

I don't know whether am I missing anything?
Pls reply me soon.....

mini

"Luc Cool" wrote:

Hi,

You should look at the things that change when you install the cab file.
As
I told before, most CAB installs do 2 things:

1. Copy the dll driver file(s) to the platform windows map. Some might
copy
control panel applet's to that destination as well. (If so, you will
have
additional icon's in your control panel)

2. Add some registry keys so that the USB host knows which driver it
should
install when the device is connected.

So, if you wan't the device to be recognised by the OS, you will have to
include those step's yourself.

If you connect your platform to a PC (I like active sync to do this) you
can
use the remote registry editor to check your device registry. You can
copy
the keys you need and insert them in the platform.reg of your platform.

check the HKLM\USB\LoadClients\xxx

There you should find under \default\default\xxxx the " DLL REG_SZ
xxxx.dll" registry key. This is the name of the driver. The first xxx
after
the loadclients refer to the VID and PID of the device. This should be
the
unique numbers each USB device uses to identify itself to the host.

You can copy the dll back to your development pc. You can include it in
your
OS by adding it to the platform.bib file section.

Your new created image (with the registry setting and the driver dll
included) should recognise the device without user intervention or
driver
installation.

Hope this helps.

regards,

Luc

<sumathik7@xxxxxxxxx> wrote in message
news:1170410937.154128.41120@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Yes. You are absolutely right. I followed the sequence:
1) Download the image.
2) Copy the CAB file using Activesync.
3) Insert the USB cable into the HUB
4) Double tap it.

If I insert the device after installing the cab file, it identifies
the device.

But in real time scenario, I'll connect the gsm module inbuilt. So
while downloading image I want the device to be identified.
How can I do that?

Give me some apt solution. I have done so many work arounds, all but
in vain.
Thanks in advance...




On Feb 2, 1:48 pm, "Luc Cool" <luc__c...@xxxxxxxxxxx> wrote:
Hi,

Did you install the driver on your platform?

What do you mean with "The device isnotdetectedif it is inserted
while
booting?"
How do you know that it isnotdetected?

Is your problem that you can only use the device if you plug it in
after
powerup, or can't you use it at all?

You say you will install the driver once the device is identified.
You
should do things the other way around. You have to install the
driver so
that the OS can identify theUSBdevice. Without driver, it will show
you
the unidentifiedUSBdevice and allow you to manually tell it which
driver
to use. If the driver is ok for theUSBdevice, the OS will create the
necessary registry keys, so that theusbdevice driver will load
automatically, the next time the device isdetected.

regards,

Luc

"mini" <m...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:D534DB02-722C-4535-8960-200B6BD4095F@xxxxxxxxxxxxxxxx



Thanks forthe reply.

If I insertUSBcable from GSM module after bootup, it gives the
pop-up
from
that I understand that it identifies the device. The driver for
GSM
module
is
available in the form of .CAB file and once if it identifies, I'll
install
it.

What I want is on power-up, if my module is inserted, it should
identify
the
device.

How can I do for that?
Could you clarify do I include any uhci/ehci from catalogue items?

Already I included OHCI in my image.

Thanks very much in advance.

"vinoth" wrote:

Windows CE 5.0 doesn't have the GSM Module support. and Windows
CE
6.0
having
the GSM Module Support (Cellcore) . i don't think it will
support
for
GSM
overUSBand it will support GSM over serial port.
--
vinoth.R
software Engineer

"mini" wrote:

I inserted the (GSM modem)USBdevice to one of the ports of
myUSBHUB
which
is connected to host port 1 of pxa270 processor.
I also insertedUSBmouse, pen drive to this hub. These devices
are
detected. But the GSM device isnotdetectedif theUSBcable is
plugged-in
while booting.

After bootup, once the image has comeup, if I plug-in the
GSMUSB
device,
then the "UnidentifiedUSBdevice" pop-up has come.

Actually where is the problem? I couldnot get it?
Immediate help needed.....- Hide quoted text -

- Show quoted text -







.

Relevant Pages

  • Re: USB not detected - help
    ... did you check for the presence of the driver dll in your windows map? ... USB device popup *didnot* come. ... Scenario 1: ... Did you copy the driver dll back from the device or did you got it from ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Same OS;wifi works on one,not on other
    ... of the cab file contents might be slightly different. ... There are quite a few USB ... that Windoze 98SE did not include a USB driver. ... Drive into add-remove and remove any USB device drivers that don't ...
    (alt.internet.wireless)
  • Re: Question about different ways of calling a driver
    ... But in my dll, I ... I also don't know why my NandFlash driver calls "OALPaToVa"(The driver ... Because I am forced to use scenario B to call a driver. ... In scenario B you aren't calling a driver. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: IRP_MJ_READ/IRP_MJ_WRITE
    ... I hope you did not put the scenario in a production driver. ... Don Burn (MVP, Windows DDK) ... Neither IO means that you touch user mode memory from kernel ...
    (microsoft.public.development.device.drivers)
  • Re: PCI and DSP bandwidth
    ... interrupt at a time for all the channels. ... and the driver was written by that company - however I've ... There's no other cards hooked to the PCI, graphics uses PCIe, and the same ... the system is able to cope with the worst case scenario. ...
    (comp.dsp)