Re: How to support bluetooth radio (USB interface) in WinCE 5.0
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Thu, 17 Aug 2006 09:44:13 -0700
I'm far from a Bluetooth expert. Which Bluetooth driver are you using? I
had the best luck with the Universal one, rather than the USB one. It
looks, from that, like you're not getting the dongle turned on. Is this is
USB 2.0 port on your main board? If not, does the dongle require 2.0?
This type of error has come up before in two contexts: not all QFEs for the
OS applied, and interrupt problems (interrupt which is supposed to fire
after reset is sent to the Bluetooth device not getting a reply before the
Bluetooth time-out). You might check those two things...
Paul T.
"Aurelie" <Aurelie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:08E0FCA0-8E97-4AF1-A3C8-1C3095A92287@xxxxxxxxxxxxxxxx
Dear Paul,
thank you for your help on this topic. I finally managed to get my usb
dongle recognized by my embedded device (I mean that I do not have the
window
asking for a device driver any more). But when I select "scan device" I
have
the error message : bleutooth controller not present (error 10050).
I can give you more details regarding my investigations.
1- Registry.
Before i plus the device, I have in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\transport\pnp, the device
driver Name : bthusb, flags 2147483648, driver bthusb.dll ....
Once the device is inserted, I have this key reallocated to :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\HCI
I beleive this looks all right.
I also have debug message from platform builder, when I insert the device,
I
got :
4294817862 PID:4347dd02 TID:a32d430e [ERR]
4294817862 PID:4347dd02 TID:a32d430e HCIUSB : ReadPacket failed.
4294817887 PID:4347dd02 TID:23334b5e [ERR]
4294817887 PID:4347dd02 TID:23334b5e hci_connect_transport::
ERROR_OUTOFMEMORY (2)
and the message I got when the system is booting is :
4294775487 PID:4347a70a TID:23322932 [ERR]
4294775488 PID:4347a70a TID:23322932 [HCI] [USB] CheckDevice - device not
active
4294775488 PID:4347a70a TID:23322932 [ERR]
4294775488 PID:4347a70a TID:23322932 hci_connect_transport::
ERROR_MEDIA_UNAVAILABLE
(I guess this one is expected).
I hope this can help
Best regards
Aurélie
"Paul G. Tobey [eMVP]" wrote:
I don't know what to tell you. The DLink adapter worked fine for me.
There
are numerous places where you can have problems if you didn't include the
right components in the OS or didn't set them up correctly for your
hardware, of course. We'll need debug output messages showing where the
failure occurs to proceed any further, I think.
Paul T.
"Aurelie" <Aurelie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D712FD93-90AF-46CE-9D60-B111494D1A77@xxxxxxxxxxxxxxxx
Hello Paul,
yes I read your answer, the thing is that I have already tried with a
Socket
adapter, an iogear and an air cable adapter and none of them is
accepted.
I
will tried the Dlink dongle but I am quite pessimistic...
I am working on a Bsp and platform builder workspace sent by a board
manufacturer. It seems that the BSP was first shipped with ce4.2 that's
why I
beleive there may be a problem with the usb drivers... (Nevertheless,
usb
storage is ok, usb mouse and keyboard are working too...)
Best regards
Aurelie
"Paul G. Tobey [eMVP]" wrote:
I posted one in my last message. Did you read the thread?
Paul T.
"Aurelie" <Aurelie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F8E519F8-3C31-48E5-9499-69361546BDE0@xxxxxxxxxxxxxxxx
Hi,
I am faced with exactly the same problem. Did you find a solution or
a
special USB to bluetooth dongle that works ?
Thanks in advance
Best regards
"fenix" a écrit :
Hi!
We built an WinCE 5.0 OS to support bluetooth radio, but it can not
work.
The WinCE OS can not identify the USB interface Bluetooth radio,
and
it
asked
for the driver name of the unidentified USB device.
We have already added all the catalog items in "Networking -
Persional
Area
Network[PAN]" and in "Personal Area Networking [PAN] devices".
The bluetooth radio is USB interface, and it is OK on Windows XP.
We
have
also tested another type of bluetooth radio, but the result is
same.
By the way, there is something different in WinCE 4.2. We added
"Bluetooth
with integrated USB-Only Driver" and "OHCI", the Bluetooth is OK.
Any help would be appreciated.
Thanks in advance.
Best regards
.
- References:
- Re: How to support bluetooth radio (USB interface) in WinCE 5.0
- From: Paul G. Tobey [eMVP]
- Re: How to support bluetooth radio (USB interface) in WinCE 5.0
- From: Paul G. Tobey [eMVP]
- Re: How to support bluetooth radio (USB interface) in WinCE 5.0
- From: Aurelie
- Re: How to support bluetooth radio (USB interface) in WinCE 5.0
- Prev by Date: Re: How to support bluetooth radio (USB interface) in WinCE 5.0
- Next by Date: Re: CF card detection in WinCE 5.0
- Previous by thread: Re: How to support bluetooth radio (USB interface) in WinCE 5.0
- Next by thread: Re: CF Card Detection in WinCE5.0
- Index(es):
Relevant Pages
|