Regarding the bluetooth driver on Wince 6.0

[Vinayakumar C]

Hi CEAssist,



Thanks in advance,

i am porting the thirdparty bluetooth stack onto the WINCE 6.0, I.MX31,

does the wince 6.0 has the bluetooth driverfor establishing the

communication between the host and the controller...i want to have the UART

as the physical transport layer between the host and the controller...



i want to know the driver name used for driving the controller... is it the

uart driver or the hci driver which drives the controller...?



please reply ASAP this is very much required for my work...



With Best Regards,

Vinayakumarc

 

[Paul G. Tobey [eMVP]]

Do you have UART-based Bluetooth support in the OS? If so, you'll have to

tell it which UART to use, how to find it, what its characteristics are, etc.

It seems like you're expecting it to be a case of just turn on the driver,

somehow, and everything works. While that might work with a USB-based

Bluetooth controller, it's not going to be the case with UART-based. Check

the help first. Then read the Bluetooth driver code and see what registry

entries it wants for UART, if the help doesn't tell you. As with any driver

question in CE, start looking in \public\common\oak\drivers.



Paul T.



"Vinayakumar C" wrote:



> Hi CEAssist,

>

> Thanks in advance,

> i am porting the thirdparty bluetooth stack onto the WINCE 6.0, I.MX31,

> does the wince 6.0 has the bluetooth driverfor establishing the

> communication between the host and the controller...i want to have the UART

> as the physical transport layer between the host and the controller...

>

> i want to know the driver name used for driving the controller... is it the

> uart driver or the hci driver which drives the controller...?

>

> please reply ASAP this is very much required for my work...

>

> With Best Regards,

> Vinayakumarc

 

[Vinayakumar C]

Hi Paul

Thanks for your reply.

Yes i do have support for UART.

Before porting the third-party stack, someone asked me to check if the

driver is present for driving the chip, so is it the UART driver (if UART is

selected as the physical bus) or the HCI driver (part of stack) which drives

the IC. please correct my understanding if i am wrong.



With Best Regards,

Vinayakumarc











"Paul G. Tobey [eMVP]" wrote:



> Do you have UART-based Bluetooth support in the OS? If so, you'll have to

> tell it which UART to use, how to find it, what its characteristics are, etc.

> It seems like you're expecting it to be a case of just turn on the driver,

> somehow, and everything works. While that might work with a USB-based

> Bluetooth controller, it's not going to be the case with UART-based. Check

> the help first. Then read the Bluetooth driver code and see what registry

> entries it wants for UART, if the help doesn't tell you. As with any driver

> question in CE, start looking in \public\common\oak\drivers.

>

> Paul T.

>

> "Vinayakumar C" wrote:

>

> > Hi CEAssist,

> >

> > Thanks in advance,

> > i am porting the thirdparty bluetooth stack onto the WINCE 6.0, I.MX31,

> > does the wince 6.0 has the bluetooth driverfor establishing the

> > communication between the host and the controller...i want to have the UART

> > as the physical transport layer between the host and the controller...

> >

> > i want to know the driver name used for driving the controller... is it the

> > uart driver or the hci driver which drives the controller...?

> >

> > please reply ASAP this is very much required for my work...

> >

> > With Best Regards,

> > Vinayakumarc

 

[Paul G. Tobey [eMVP]]

The UART option selects

C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\BLUETOOTH\TRANSPORTS\UART\hciuart.cxx

as the Bluetooth hardware interface. You can see what it does and try to

replicate that in the Bluetooth stack you are porting...



Paul T.



"Vinayakumar C" wrote:



> Hi Paul

> Thanks for your reply.

> Yes i do have support for UART.

> Before porting the third-party stack, someone asked me to check if the

> driver is present for driving the chip, so is it the UART driver (if UART is

> selected as the physical bus) or the HCI driver (part of stack) which drives

> the IC. please correct my understanding if i am wrong.

>

> With Best Regards,

> Vinayakumarc

>

>

>

>

>

> "Paul G. Tobey [eMVP]" wrote:

>

> > Do you have UART-based Bluetooth support in the OS? If so, you'll have to

> > tell it which UART to use, how to find it, what its characteristics are, etc.

> > It seems like you're expecting it to be a case of just turn on the driver,

> > somehow, and everything works. While that might work with a USB-based

> > Bluetooth controller, it's not going to be the case with UART-based. Check

> > the help first. Then read the Bluetooth driver code and see what registry

> > entries it wants for UART, if the help doesn't tell you. As with any driver

> > question in CE, start looking in \public\common\oak\drivers.

> >

> > Paul T.

> >

> > "Vinayakumar C" wrote:

> >

> > > Hi CEAssist,

> > >

> > > Thanks in advance,

> > > i am porting the thirdparty bluetooth stack onto the WINCE 6.0, I.MX31,

> > > does the wince 6.0 has the bluetooth driverfor establishing the

> > > communication between the host and the controller...i want to have the UART

> > > as the physical transport layer between the host and the controller...

> > >

> > > i want to know the driver name used for driving the controller... is it the

> > > uart driver or the hci driver which drives the controller...?

> > >

> > > please reply ASAP this is very much required for my work...

> > >

> > > With Best Regards,

> > > Vinayakumarc

 

[Vinayakumar C]

HI Paul,



Thanks for your reply



with best regards,

vinayakumarc



"Paul G. Tobey [eMVP]" wrote:



> The UART option selects

> C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\BLUETOOTH\TRANSPORTS\UART\hciuart.cxx

> as the Bluetooth hardware interface. You can see what it does and try to

> replicate that in the Bluetooth stack you are porting...

>

> Paul T.

>

> "Vinayakumar C" wrote:

>

> > Hi Paul

> > Thanks for your reply.

> > Yes i do have support for UART.

> > Before porting the third-party stack, someone asked me to check if the

> > driver is present for driving the chip, so is it the UART driver (if UART is

> > selected as the physical bus) or the HCI driver (part of stack) which drives

> > the IC. please correct my understanding if i am wrong.

> >

> > With Best Regards,

> > Vinayakumarc

> >

> >

> >

> >

> >

> > "Paul G. Tobey [eMVP]" wrote:

> >

> > > Do you have UART-based Bluetooth support in the OS? If so, you'll have to

> > > tell it which UART to use, how to find it, what its characteristics are, etc.

> > > It seems like you're expecting it to be a case of just turn on the driver,

> > > somehow, and everything works. While that might work with a USB-based

> > > Bluetooth controller, it's not going to be the case with UART-based. Check

> > > the help first. Then read the Bluetooth driver code and see what registry

> > > entries it wants for UART, if the help doesn't tell you. As with any driver

> > > question in CE, start looking in \public\common\oak\drivers.

> > >

> > > Paul T.

> > >

> > > "Vinayakumar C" wrote:

> > >

> > > > Hi CEAssist,

> > > >

> > > > Thanks in advance,

> > > > i am porting the thirdparty bluetooth stack onto the WINCE 6.0, I.MX31,

> > > > does the wince 6.0 has the bluetooth driverfor establishing the

> > > > communication between the host and the controller...i want to have the UART

> > > > as the physical transport layer between the host and the controller...

> > > >

> > > > i want to know the driver name used for driving the controller... is it the

> > > > uart driver or the hci driver which drives the controller...?

> > > >

> > > > please reply ASAP this is very much required for my work...

> > > >

> > > > With Best Regards,

> > > > Vinayakumarc

 

[Vinayakumar C]

Hi Paul,



I have one more question? does the btd.dll the upper bluetooth protocol

stack runs in kernel mode or user mode?. I have gone through help from msdn,

there they say that all the device drivers are loaded by the Device.exe

module during booting.

They have mentioned all the drivers which would be getting loaded, does

Btd.dll will also be loaded by the Device.exe.



We are adding the Profiles support and bluetooth transport driver through

catalog items which gets added to the OS design, but how does this Btd.dll

gets added to the OSdesign & loaded by which module?



thanks & regards,

vinayakumarc



"Paul G. Tobey [eMVP]" wrote:



> The UART option selects

> C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\BLUETOOTH\TRANSPORTS\UART\hciuart.cxx

> as the Bluetooth hardware interface. You can see what it does and try to

> replicate that in the Bluetooth stack you are porting...

>

> Paul T.

>

> "Vinayakumar C" wrote:

>

> > Hi Paul

> > Thanks for your reply.

> > Yes i do have support for UART.

> > Before porting the third-party stack, someone asked me to check if the

> > driver is present for driving the chip, so is it the UART driver (if UART is

> > selected as the physical bus) or the HCI driver (part of stack) which drives

> > the IC. please correct my understanding if i am wrong.

> >

> > With Best Regards,

> > Vinayakumarc

> >

> >

> >

> >

> >

> > "Paul G. Tobey [eMVP]" wrote:

> >

> > > Do you have UART-based Bluetooth support in the OS? If so, you'll have to

> > > tell it which UART to use, how to find it, what its characteristics are, etc.

> > > It seems like you're expecting it to be a case of just turn on the driver,

> > > somehow, and everything works. While that might work with a USB-based

> > > Bluetooth controller, it's not going to be the case with UART-based. Check

> > > the help first. Then read the Bluetooth driver code and see what registry

> > > entries it wants for UART, if the help doesn't tell you. As with any driver

> > > question in CE, start looking in \public\common\oak\drivers.

> > >

> > > Paul T.

> > >

> > > "Vinayakumar C" wrote:

> > >

> > > > Hi CEAssist,

> > > >

> > > > Thanks in advance,

> > > > i am porting the thirdparty bluetooth stack onto the WINCE 6.0, I.MX31,

> > > > does the wince 6.0 has the bluetooth driverfor establishing the

> > > > communication between the host and the controller...i want to have the UART

> > > > as the physical transport layer between the host and the controller...

> > > >

> > > > i want to know the driver name used for driving the controller... is it the

> > > > uart driver or the hci driver which drives the controller...?

> > > >

> > > > please reply ASAP this is very much required for my work...

> > > >

> > > > With Best Regards,

> > > > Vinayakumarc

 

[Paul G. Tobey [eMVP]]

Search the registry of a built OS (reginit.ini), for btd.dll. That will tell

you where it is called out for enumeration during boot. The flags specified

in its registry entries will tell you how it is to be loaded (including

whether it's a user mode or kernel mode driver). It appears to me that it

will be loaded by device.exe...



Paul T.



"Vinayakumar C" wrote:



> Hi Paul,

>

> I have one more question? does the btd.dll the upper bluetooth protocol

> stack runs in kernel mode or user mode?. I have gone through help from msdn,

> there they say that all the device drivers are loaded by the Device.exe

> module during booting.

> They have mentioned all the drivers which would be getting loaded, does

> Btd.dll will also be loaded by the Device.exe.

>

> We are adding the Profiles support and bluetooth transport driver through

> catalog items which gets added to the OS design, but how does this Btd.dll

> gets added to the OSdesign & loaded by which module?

>

> thanks & regards,

> vinayakumarc

>

> "Paul G. Tobey [eMVP]" wrote:

>

> > The UART option selects

> > C:\WINCE500\PUBLIC\COMMON\OAK\DRIVERS\BLUETOOTH\TRANSPORTS\UART\hciuart.cxx

> > as the Bluetooth hardware interface. You can see what it does and try to

> > replicate that in the Bluetooth stack you are porting...

> >

> > Paul T.

> >

> > "Vinayakumar C" wrote:

> >

> > > Hi Paul

> > > Thanks for your reply.

> > > Yes i do have support for UART.

> > > Before porting the third-party stack, someone asked me to check if the

> > > driver is present for driving the chip, so is it the UART driver (if UART is

> > > selected as the physical bus) or the HCI driver (part of stack) which drives

> > > the IC. please correct my understanding if i am wrong.

> > >

> > > With Best Regards,

> > > Vinayakumarc

> > >

> > >

> > >

> > >

> > >

> > > "Paul G. Tobey [eMVP]" wrote:

> > >

> > > > Do you have UART-based Bluetooth support in the OS? If so, you'll have to

> > > > tell it which UART to use, how to find it, what its characteristics are, etc.

> > > > It seems like you're expecting it to be a case of just turn on the driver,

> > > > somehow, and everything works. While that might work with a USB-based

> > > > Bluetooth controller, it's not going to be the case with UART-based. Check

> > > > the help first. Then read the Bluetooth driver code and see what registry

> > > > entries it wants for UART, if the help doesn't tell you. As with any driver

> > > > question in CE, start looking in \public\common\oak\drivers.

> > > >

> > > > Paul T.

> > > >

> > > > "Vinayakumar C" wrote:

> > > >

> > > > > Hi CEAssist,

> > > > >

> > > > > Thanks in advance,

> > > > > i am porting the thirdparty bluetooth stack onto the WINCE 6.0, I.MX31,

> > > > > does the wince 6.0 has the bluetooth driverfor establishing the

> > > > > communication between the host and the controller...i want to have the UART

> > > > > as the physical transport layer between the host and the controller...

> > > > >

> > > > > i want to know the driver name used for driving the controller... is it the

> > > > > uart driver or the hci driver which drives the controller...?

> > > > >

> > > > > please reply ASAP this is very much required for my work...

> > > > >

> > > > > With Best Regards,

> > > > > Vinayakumarc