Boot Loader Hardware Config

May 13, 2007 at 5:06 AM
Hi All,
Well I have finally installed the we-boot and have window ce up also. I went to the bluetooth properties and it couldn't find the device. I read up alittle and it seems that I need to enable bluetooth in the hardware config.

How can I do this?

0x00011299 is for a Connec-XM 400mz (as in the docs) but I need it for a Basix gumstix w/ bluetooth. How can I can derive this 0x00???? special numbe?.

Thx!

Coordinator
May 13, 2007 at 1:53 PM
Which version are you using CE 5.0 or 6.0?
Also you need to know which Bluetooth module is on your Gumstix board.
Gumstix has used three different modules.
May 13, 2007 at 3:32 PM
We-boot 3.02, Window CE 5.0

Now looking at my gumstix I see a white sticker with PBA31308 ES3 060630 on it.
Coordinator
May 13, 2007 at 11:04 PM
we don't have support for 308 module yet but there is a simple hack you can use.
I posted the fix in the gotdotnet message thread: http://www.gotdotnet.com/workspaces/messageboard/thread.aspx?id=df0ed5bb-f1b0-437b-b8cf-0fd690d3a547&threadid=d7cde0e6-091a-449b-9617-8e1b2032ae26

I'll copy it here:
PBA31307 vs PBA31308 Bluetooth module Posted on: 01/17/2007 20:20:25


Gumstix recently changed the Bluetooth module (again!!) from a PBA31307 to PBA31308. Early indications are the 0.7 BSP release does not work with this module. We are looking into supporting the new module in the next release.

DV
Post edited by dvescovi on 01/17/2007 20:21:05

dvescovi

User Posts:
54
PBA31307 vs PBA31308 Bluetooth module Posted on: 01/29/2007 15:21:55


A simple hack to make the BSP work with the PBA31308 Bluetooth module would be to change dwStartBaud in the HCI_OpenConnection routine to 921600. Make sure you have booted the Linux OS at least once before flashing we-boot. The Linux boot set the default baudrate from 115200 (factory) to 921600 and stores the setting persistently in the module.
Upon CE boot, the Gumstix BT UART will be set to 921600 (dwStartBaud) and will not send any module specific HCI commands. This seems to work.
Thanks to Nicholus Chen for testing this out.
A better, more robust, change would be to sense the module and set accordingly.

I will add this in the next release.

Coordinator
May 13, 2007 at 11:07 PM
I forgot to mention .. set the hardware word to support the 307 module to use the 308 hack.
DV
May 14, 2007 at 2:22 AM
Is the dwStartBaud setting can only be edited in Platform Builder? I am running the generic gumstix2 ce image and am not using Platform Builder. I have poked around in the registry and have not found anything there.

Also just curious do you have a date on your next release?

Thx


dvescovi wrote:
we don't have support for 308 module yet but there is a simple hack you can use.
I posted the fix in the gotdotnet message thread: http://www.gotdotnet.com/workspaces/messageboard/thread.aspx?id=df0ed5bb-f1b0-437b-b8cf-0fd690d3a547&threadid=d7cde0e6-091a-449b-9617-8e1b2032ae26

I'll copy it here:
PBA31307 vs PBA31308 Bluetooth module Posted on: 01/17/2007 20:20:25


Gumstix recently changed the Bluetooth module (again!!) from a PBA31307 to PBA31308. Early indications are the 0.7 BSP release does not work with this module. We are looking into supporting the new module in the next release.

DV
Post edited by dvescovi on 01/17/2007 20:21:05

dvescovi

User Posts:
54
PBA31307 vs PBA31308 Bluetooth module Posted on: 01/29/2007 15:21:55


A simple hack to make the BSP work with the PBA31308 Bluetooth module would be to change dwStartBaud in the HCI_OpenConnection routine to 921600. Make sure you have booted the Linux OS at least once before flashing we-boot. The Linux boot set the default baudrate from 115200 (factory) to 921600 and stores the setting persistently in the module.
Upon CE boot, the Gumstix BT UART will be set to 921600 (dwStartBaud) and will not send any module specific HCI commands. This seems to work.
Thanks to Nicholus Chen for testing this out.
A better, more robust, change would be to sense the module and set accordingly.

I will add this in the next release.



Coordinator
May 14, 2007 at 5:50 AM
Pretty much stuck if you don't have Platform Builder 5.0. You need to rebuild to get the hack. You use to be able to download an eval version of PB from the MS web site. Don't know if they still have it available now that CE 6.0 is out.
If you get PB 5.0 its a simple matter to rebuild if you use my prebuilt OSDesigns project.

I will probably be posting some prebuilt CE 6.0 images in the comming weeks along with additional hardware support and bug fixes.

DV
May 14, 2007 at 3:00 PM
Well the only thing I can find is the eval for PB 6.0 and updates for PB 5.0.

Would it be too much to ask you to post a new image on codeplex with the 308 hack?
May 16, 2007 at 2:29 AM
For any lone reader reading this post this is what I have found if you have to rebuild the os image with Platform Builder 5.0

I finally found PB 5.0 and it's not simply called Platform Build 5.0. The download for PB 5.0 can be found here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=486e8250-d311-4f67-9fb3-23e8b8944f3e&DisplayLang=en

Here is all the updates except for November 2006 can be found here:
http://msdn2.microsoft.com/en-us/embedded/aa731256.aspx

The November 2006 PB 5.0 update can be downloaded by this direct link:
http://download.microsoft.com/download/7/1/b/71bcdfdc-b6c6-4eef-a49b-6f9cf2590830/WinCEPB50-061130-2006M11-Armv4I.msi

Make sure all the updates are installed. I am still having problems compiling the image but hopefully through time will have figured it all out.

dvescovi I thank you for your help and will be looking foward to your new release that will support the PBA31308 bluetooh module. Keep up the good work.