Reusing WM2003SE Widcomm BT stack extracted from dumped ROM image - anyone tried?

Just a thought:
I've just remembered OzVGA 192dpi dlls didn't work at the begining. It was because they weren't digitally signed and we needed a new signed version. Maybe we have the same problem with widcomm drivers. The dlls we have aren't signed. Maybe they are not loading for this reason. What do you think?

It could be the reason. I'll try to investigate this. But the people from XDA developers have managed to install these versions on XDAs with WM5.

[Li0rE]

Yes, a $10000 award was given to the first person who got XP to run on Mac successfully with instructions. This is far easier than that though it isnt easy. That is why the goal for the reward is $500-$1000

[mikelspikel]

C'mon guys! Only thinking in the money?

Some interesting news here:

It seems BtCeIf.dll (and friends) don't load at boot time. I still think it's because they are not signed. I've developed a little C++ program that calls several times to ActivateDeviceEx API. With this, drivers.exe loads BtCeIf.dll, BtCeProfiles.dll and BtCeStack.dll using the settings stored in the registry.

Well, using version 1.6, Beemer's .reg file for this version and another .reg file built taking some keys from the full x50 WM2003 registry dump, I've managed to switch bluetooth on (blue led flashing) without the driver memory error. I can run bluetooth manager too. Anyway, there's still something not working because I cannot "see" other devices.

I'll post the files tomorrow morning (football match on TV this evening, sorry).

It'll be interesting if someone with Visual Studio 2005 and WM5 SDK could try to sign the dlls with SDK Certificate in order to test if they load at boot time this way.

[kpc1]

That sounds promising, mikelspikel, well done. Enjoy your football match, you deserve it!

how do you sign it?

Good job, Mikelspikel.

Now what I've found:
1-Comunication path
X51, as nearly all BT devices, are based on Cambridge Silicon Radio (CSR) chipsets http://www.csr.com, and probably on Bluecore2
This chipset can be accesed in three ways: USB, syncronous serial port (usually called BCSP protocol or UART serial port. The last is the case on X51.
This Serial port is controlled by BTUartDMA.dll driver that is called from device.exe reading the registry key HKLM\Drivers\Builtin\BTTart and load it as COM5:
Opening COM5: from a program (Telnet program) and sending several CRs BT chip turns on (Blue LED start blinking).
It seems that if under HKLM\software\Widcom\btconfig\general\TransportLib rary we use BTCESerialTrans.dll (an inexistent dll) BTTrayCE.exe tries to activate BT by means of COM5: (defined in HKLM\software\Widcom\btconfig\SerialTransport), but if we put BTCeBCSPTrans.dll it tries it by means of the syncronous BCSP serial protocol that is not the case on the Axim.
Then I think BTUart registry entry must be maintained.

2-Error Log
When BTTRayCE.exe tries to load the stack and tuen on BT, it writes a small error log under HKLM\software\Widcom\BtConfig\Debug\Log One line each error and rewrites it each 5 lines.
In this error log I've found that the only TIBinaryParser.dll that does not causes an error is the one in 1.5.200 but if we remove it's entry there are not error also.
The error that is persistent and I associate with BTCEif.dll not loaded (as MikelSpikel does) is "BTStack (MAGICNUMBER) load failed" or something like that.

3-CPL
Using BTcplCe and BTTrayCE from1.5.200 is the only way that allow to clik advanced buttons on BT control panel and see things like the version of each file. With others the program hangs.

4-HKLM\Microsoft\Bluetooth\Transports\BuiltIn\1
This key is the main transport for the Microsoft Stack. On X50 it load USB comunications Transport ¿¿¿??? but on X51 it load somecing called BTHCI.dll that as said in
http://msdn.microsoft.com/library/de...chitecture.asp
seems to be the HCI part from Microsoft (the part from CSR is in firmware) and I'm pretty sure that it must be removed from the registry and that BTCEif.dll is the equivalent from Widcomm.

5-BTCeif.dll
I don't know whi it doesn't load. MikelSpikes sais that the problem is that this driver is not signed: I've tried with and without WM5 security activated (using setsecurity.exe from Ctitanic) and had no results. Also, the guys from XDA-developers.com have maneged to run Widcomm stack on HTC based machines with WM5 and MS BT Stack (but always based on BCSP protocol) without the need of sign any driver. Remember that X51 is the only WM5 device that has MS security enabled by default, but it can be easily disabled.
I'll try to sign this driver, but I have heard that it cannot be done without buying a digital sign....

And this is all up to this moment...

[mikelspikel]

Quite a lot of new information! Good work beemer!

Reading your post, I think maybe I wasn't in the right way, as I was using BtCeBCSPTrans.dll.

I've attached ActivateBTDrivers.zip. It has the little c++ program mentioned above used to make devices.exe load BtCeIf.dll. It has to be run after soft reset and before BtTrayCe is loaded.

The following drivers must exist in the registry for the program to work:

BtCeStack
BtCeProfiles
BTC1
BTC2
BTC4
Serial7
Serial8

The drivers are loaded in this order. If anyone of them fails to load, you'll get an error message with the name of the driver that failed and an error code (1610 when the driver is not in the registry or 2404 when it's already loaded). If everything works ok you'll get a success message.

Regarding signatures, I've read there is a test purpose certificate available with WM5 SDK. I don't know anything more about this as I don't have VS2005 available.

I have as well security prompt disabled with setsecurity but if I try to use the 192 dpi dlls available in OzVGA website (not signed) and switch to true VGA, the Axim freezes while booting (-> hard reset). With the signed ones it works great. That's why I still believe the signature has something to do about this. Maybe dlls can only be loaded at boot time if they are signed.

[itpsp]

Quite a lot of new information! Good work beemer!

Reading your post, I think maybe I wasn't in the right way, as I was using BtCeBCSPTrans.dll.

I've attached ActivateBTDrivers.zip. It has the little c++ program mentioned above used to make devices.exe load BtCeIf.dll. It has to be run after soft reset and before BtTrayCe is loaded.

The following drivers must exist in the registry for the program to work:

BtCeStack
BtCeProfiles
BTC1
BTC2
BTC4
Serial7
Serial8

The drivers are loaded in this order. If anyone of them fails to load, you'll get an error message with the name of the driver that failed and an error code (1610 when the driver is not in the registry or 2404 when it's already loaded). If everything works ok you'll get a success message.

Regarding signatures, I've read there is a test purpose certificate available with WM5 SDK. I don't know anything more about this as I don't have VS2005 available.

I have as well security prompt disabled with setsecurity but if I try to use the 192 dpi dlls available in OzVGA website (not signed) and switch to true VGA, the Axim freezes while booting (-> hard reset). With the signed ones it works great. That's why I still believe the signature has something to do about this. Maybe dlls can only be loaded at boot time if they are signed.

:approve: keep up the good work

[coolbre304]

A bit over my head, but I understood bits and pieces. Amazing, keep up the good work.

[Patrick Y.]

Good work guys. We're counting on you. BTW, don't forget the big prize!!;)

[Li0rE]

yea the prize is almost $500! Listen, beemer. Setsecurity just disables the security prompt, but I'm not sure if that means you still don't need signed drivers. Someone PM mrp04 and ask him to sign the drivers, because I think he has VStudio WM5 SDK.

[Kazkin]

HP rolled out WM5 upgrade for the 4700 the last couple days ... wondered if they did their homework this time ... since their WM5 upgrade for their other models also suffered the MS BT woes ...

if they did their homework ... posibilities are just at the horizon :p

http://www.pdastreet.com/articles/20...0-Windows.html


~~~~~

[Li0rE]

how is this related to bluetooth? It would only be related if hx4700 has widcomm and used a CSR bt radio.

[Kazkin]

how is this related to bluetooth? It would only be related if hx4700 has widcomm and used a CSR bt radio.

as their other models also suffered from the lack of BT services ...

I was thinking in the line of ... they did their homework this time with the 4700 ...

if they can make their device operating properly using WM5 OS and have BT profiles ...etc..etc ... that we could learn something from them ( being optimistic of the talents we have on this site :p )

ofcourse ... it could just been wishful thinking :p

[Li0rE]

You are right. WOW! I think for the first time in a while, PDA consumers can learn something from PDA manufacturers. Anyway, lets get back on topic now. I don't want to hijack a thread this important. But guys, keep your eyes on the prize!