WinCE6.0 Bluetooth via UART

[Microsoft]

Hi,

I'm using WinCE6.0 and adding Bluetooth module into our platform via
UART1, but it always fails and shows: “Bluetooth hardware error 10050
(controller not present)” , details as following:
1, H/W: Samsung S3C6410 + Bluetooth Module, Interface: UART1.
2, S/W: WinCE6.0 R2, last updated: 090131.
3, The driver we are using is the one included in Microsoft's
WindowsCE6.0 package: bthuart.dll.
4, Catalog Items I selected for Bluetooth ares: SYSGEN_BTH_AG,
SYSGEN_BTH_UART_ONLY and SYSGEN_BTH.
5, In addition, I added an environment variable:
"BSP_BLUETOOTH_BUILTIN_UART=1".
6, CPU frequency of S3C6410: 667MHz; UART baud rate: 115200bps.
7, When the OS bootup and we launch:Control Panel/Bluetooth device
property/Scan Device, the system will popup: “Bluetooth hardware error
10050 (controller not present)”.

No matter how hard I try to debug it, it always shows this damn
message:"Bluetooth hardware error 10050 (Controller not present)", very
confusing...

So I want to know:
1, Can WinCE6.0 support the UART connected Bluetooth?
2, Can I use Microsoft's driver for this case? then need I modify it to
suit our platform? and where?
3, I know that the registry keys are playing very important roles in
WinCE system, but what modification should I make to let it work correctly?
4, I'm not sure whether should I add the environment variable
"BSP_BLUETOOTH_BUILTIN_UART=1" or not, could anyone tell me patiently?
5, I don't know the handshaking mechanism between the host and the
Bluetooth device, can anyone tell me about that?
6, Can anyone tell me how should I debug it? or any other good idea on
this issue?

Any helpful suggestion is very appreciated!

Best regards,
Jack Zhao

[Luca Calligaris]

I suppose you know the difference between UART and CSR serial transports and
that UART is the right choice for your device.
'Controller not present' is probably due to a failure in HCI driver
intialization: the driver will use serial API (CreateFile, ReadFile,
SetupComm,...) to talk
to the BT controller and you should see clearly the error message when it
fails if you run a debug build.
I remember I experienced a failure in HCI loading since it expects the
serial driver to handle a certain amount of bytes in his SW queue.
The standard MDD layer didn't handle it correctly so I had the fault. Sorry
but I don't remember other details.
Check the code
%_WINCEROOT%\PUBLIC\COMMON\OAK\DRIVERS\BLUETOOTH\TRANSPORTS\UART
%_WINCEROOT%\PUBLIC\COMMON\OAK\DRIVERS\SERIAL\COM_MDD2
to have more info
--

Luca Calligaris (MVP-Windows Embedded)
http://geekswithblogs.net/WindowsEmbeddedAnnotations
l.calliga...@eurotech.it.nospam
www.eurotech.it

"Microsoft" <Jack...@yeah.net> ha scritto nel messaggio
news:%23ecePXe...@TK2MSFTNGP03.phx.gbl...