I have an LE enabled BT controller, and I happened to send across a
simple "leadv" from the recently updated hciconfig
I got back the following data
"4 e 5 1 a 20 c 3a" and hence
"Can't set advertise mode on hci0: Success (0)"
and 0xC I guess by the BT spec means the command is disallowed (for
reasons unknown?....)
So I'm just wondering, am I supposed to run some HCI-VS commands to
enable LE? I mean I should ask my vendor I agree, but anyone who has
got it working.. do they run some VS commands before enabling LE
advertising?
On Fri, Sep 10, 2010 at 11:35:50PM +0200, ext Mike Tsai wrote:
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Claudio Takahasi
> Sent: Friday, September 10, 2010 2:03 PM
> To: Anderson Lizardo
> Cc: Pavan Savoy; Anderson Briglia; [email protected]
> Subject: Re: set LE advertise not working...
>
> On Fri, Sep 10, 2010 at 5:35 PM, Anderson Lizardo
> <[email protected]> wrote:
> > On Fri, Sep 10, 2010 at 3:01 PM, Pavan Savoy <[email protected]> wrote:
> >> No, I don't suppose my controller was in a advertising state.. even if
> >> it was why the return 0x0c? (command disallowed ..)
> >>
> >> I wanted to know whether you have some HCI-VS commands which sort of
> >> enable the LE (AMP/radio/controller) ?
> >> Is it only then the leadv command works? Or does it just works right-away.
> >> I have one of those all in 1 chips.. bt/fm-rx-tx/gps so I am wondering
> >> should I do something to enable BLE and is it some sort of un-spoken
> >> standard?
> >
> > Does LE scan work for this same hardware?
> >
> > Do you have some windows software to test this hardware ? if so, you
> > can try putting one device in advertise mode there , then attempt
> > lescan on the other (from linux)... If it works, most probably the
> > hardware might require some initialization...
> >
> > At least some hardware requires firmware upload and vendor specific
> > one-time initialization which (I think) is out of scope for hciconfig.
> >
> > Regards,
> > --
> > Anderson Lizardo
> > OpenBossa Labs - INdT
> > Manaus - Brazil
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> > the body of a message to [email protected]
> > More majordomo info at ?http://vger.kernel.org/majordomo-info.html
> >
>
> > Hi All,
>
> > I noticed that some LE hardwares don't allow to enable scanning or
> > advertising when inquiry scan and/or page scan are enabled.
> > Try to disable it using hciconfig or the D-Bus method before to start
> > LE operations.
>
> > Regards,
> > Claudio.
>
> Hello,
>
> Now I remember, dual mode devices (BR/EDR/LE) are not allowed to work as peripheral (or slave) device. The default advertising mode is "connectable indirect advertising mode". When you try to enable the advertising, you are trying to make this dual mode device as a potential slave to other LE masters and that's why the controller rejects the command.
>
Where is this stated?
> Scan should work though.
>
> I don't think you can ever connect 2 dual mode devices together, you need a single mode device (LE only) as the slave,
Well my two dual mode controllers connect fine with eachother.
--
Ville
So do these (my) dual mode device has some command where I can put it
in BLE (slave) mode only ?
Is that not part of spec?
PS:
Still trying to get around the spec and its uses.. so please excuse
naive questions...
On Fri, Sep 10, 2010 at 4:35 PM, Mike Tsai <[email protected]> wrote:
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Claudio Takahasi
> Sent: Friday, September 10, 2010 2:03 PM
> To: Anderson Lizardo
> Cc: Pavan Savoy; Anderson Briglia; [email protected]
> Subject: Re: set LE advertise not working...
>
> On Fri, Sep 10, 2010 at 5:35 PM, Anderson Lizardo
> <[email protected]> wrote:
>> On Fri, Sep 10, 2010 at 3:01 PM, Pavan Savoy <[email protected]> wrote:
>>> No, I don't suppose my controller was in a advertising state.. even if
>>> it was why the return 0x0c? (command disallowed ..)
>>>
>>> I wanted to know whether you have some HCI-VS commands which sort of
>>> enable the LE (AMP/radio/controller) ?
>>> Is it only then the leadv command works? Or does it just works right-away.
>>> I have one of those all in 1 chips.. bt/fm-rx-tx/gps so I am wondering
>>> should I do something to enable BLE and is it some sort of un-spoken
>>> standard?
>>
>> Does LE scan work for this same hardware?
>>
>> Do you have some windows software to test this hardware ? if so, you
>> can try putting one device in advertise mode there , then attempt
>> lescan on the other (from linux)... If it works, most probably the
>> hardware might require some initialization...
>>
>> At least some hardware requires firmware upload and vendor specific
>> one-time initialization which (I think) is out of scope for hciconfig.
>>
>> Regards,
>> --
>> Anderson Lizardo
>> OpenBossa Labs - INdT
>> Manaus - Brazil
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>> Hi All,
>
>> I noticed that some LE hardwares don't allow to enable scanning or
>> advertising when inquiry scan and/or page scan are enabled.
>> Try to disable it using hciconfig or the D-Bus method before to start
>> LE operations.
>
>> Regards,
>> Claudio.
>
> Hello,
>
> Now I remember, dual mode devices (BR/EDR/LE) are not allowed to work as peripheral (or slave) device. The default advertising mode is "connectable indirect advertising mode". When you try to enable the advertising, you are trying to make this dual mode device as a potential slave to other LE masters and that's why the controller rejects the command.
>
> Scan should work though.
>
> I don't think you can ever connect 2 dual mode devices together, you need a single mode device (LE only) as the slave,
>
> Cheers,
>
> Mike
>
>
>
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Claudio Takahasi
Sent: Friday, September 10, 2010 2:03 PM
To: Anderson Lizardo
Cc: Pavan Savoy; Anderson Briglia; [email protected]
Subject: Re: set LE advertise not working...
On Fri, Sep 10, 2010 at 5:35 PM, Anderson Lizardo
<[email protected]> wrote:
> On Fri, Sep 10, 2010 at 3:01 PM, Pavan Savoy <[email protected]> wrote:
>> No, I don't suppose my controller was in a advertising state.. even if
>> it was why the return 0x0c? (command disallowed ..)
>>
>> I wanted to know whether you have some HCI-VS commands which sort of
>> enable the LE (AMP/radio/controller) ?
>> Is it only then the leadv command works? Or does it just works right-away.
>> I have one of those all in 1 chips.. bt/fm-rx-tx/gps so I am wondering
>> should I do something to enable BLE and is it some sort of un-spoken
>> standard?
>
> Does LE scan work for this same hardware?
>
> Do you have some windows software to test this hardware ? if so, you
> can try putting one device in advertise mode there , then attempt
> lescan on the other (from linux)... If it works, most probably the
> hardware might require some initialization...
>
> At least some hardware requires firmware upload and vendor specific
> one-time initialization which (I think) is out of scope for hciconfig.
>
> Regards,
> --
> Anderson Lizardo
> OpenBossa Labs - INdT
> Manaus - Brazil
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
> Hi All,
> I noticed that some LE hardwares don't allow to enable scanning or
> advertising when inquiry scan and/or page scan are enabled.
> Try to disable it using hciconfig or the D-Bus method before to start
> LE operations.
> Regards,
> Claudio.
Hello,
Now I remember, dual mode devices (BR/EDR/LE) are not allowed to work as peripheral (or slave) device. The default advertising mode is "connectable indirect advertising mode". When you try to enable the advertising, you are trying to make this dual mode device as a potential slave to other LE masters and that's why the controller rejects the command.
Scan should work though.
I don't think you can ever connect 2 dual mode devices together, you need a single mode device (LE only) as the slave,
Cheers,
Mike
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Sep 10, 2010 at 5:35 PM, Anderson Lizardo
<[email protected]> wrote:
> On Fri, Sep 10, 2010 at 3:01 PM, Pavan Savoy <[email protected]> wrote:
>> No, I don't suppose my controller was in a advertising state.. even if
>> it was why the return 0x0c? (command disallowed ..)
>>
>> I wanted to know whether you have some HCI-VS commands which sort of
>> enable the LE (AMP/radio/controller) ?
>> Is it only then the leadv command works? Or does it just works right-away.
>> I have one of those all in 1 chips.. bt/fm-rx-tx/gps so I am wondering
>> should I do something to enable BLE and is it some sort of un-spoken
>> standard?
>
> Does LE scan work for this same hardware?
>
> Do you have some windows software to test this hardware ? if so, you
> can try putting one device in advertise mode there , then attempt
> lescan on the other (from linux)... If it works, most probably the
> hardware might require some initialization...
>
> At least some hardware requires firmware upload and vendor specific
> one-time initialization which (I think) is out of scope for hciconfig.
>
> Regards,
> --
> Anderson Lizardo
> OpenBossa Labs - INdT
> Manaus - Brazil
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Hi All,
I noticed that some LE hardwares don't allow to enable scanning or
advertising when inquiry scan and/or page scan are enabled.
Try to disable it using hciconfig or the D-Bus method before to start
LE operations.
Regards,
Claudio.
On Fri, Sep 10, 2010 at 3:01 PM, Pavan Savoy <[email protected]> wrote:
> No, I don't suppose my controller was in a advertising state.. even if
> it was why the return 0x0c? (command disallowed ..)
>
> I wanted to know whether you have some HCI-VS commands which sort of
> enable the LE (AMP/radio/controller) ?
> Is it only then the leadv command works? Or does it just works right-away.
> I have one of those all in 1 chips.. bt/fm-rx-tx/gps so I am wondering
> should I do something to enable BLE and is it some sort of un-spoken
> standard?
Does LE scan work for this same hardware?
Do you have some windows software to test this hardware ? if so, you
can try putting one device in advertise mode there , then attempt
lescan on the other (from linux)... If it works, most probably the
hardware might require some initialization...
At least some hardware requires firmware upload and vendor specific
one-time initialization which (I think) is out of scope for hciconfig.
Regards,
--
Anderson Lizardo
OpenBossa Labs - INdT
Manaus - Brazil
No, I don't suppose my controller was in a advertising state.. even if
it was why the return 0x0c? (command disallowed ..)
I wanted to know whether you have some HCI-VS commands which sort of
enable the LE (AMP/radio/controller) ?
Is it only then the leadv command works? Or does it just works right-away.
I have one of those all in 1 chips.. bt/fm-rx-tx/gps so I am wondering
should I do something to enable BLE and is it some sort of un-spoken
standard?
On Fri, Sep 10, 2010 at 1:14 PM, Anderson Briglia
<[email protected]> wrote:
> On 09/10/2010 12:53 PM, Pavan Savoy wrote:
>>
>> Nope, I haven't applied the kernel patches...
>> But my kernel diff to the latest kernel is only regarding the "block"
>> and "unblock" to black list devices....
>>
>> do I need some patches in kernel for enabling/disabling BLE too ?
>> I thought it just sends out the commands to controller...
>>
>
> You are right. You don't need to have the kernel patches.
> I did some tests here and everything goes ok.
> Check the hcidump output below:
>
> 2010-09-10 14:13:19.032099 < HCI Command: Unknown (0x08|0x000a) plen 1
> 0000: 01 .
> 2010-09-10 14:13:19.070320 > HCI Event: Command Complete (0x0e) plen 4
> Unknown (0x08|0x000a) ncmd 2
> 0000: 00
>
> I just did a hciconfig hci0 leadv
>
> Regards,
>
> Anderson Briglia
>>
>> On Fri, Sep 10, 2010 at 8:40 AM, Anderson Briglia
>> <[email protected]> wrote:
>>
>>>
>>> Hi Pavan,
>>>
>>> Try to make a hciconfig reset before setting leadv.
>>> Are you using that kernel patches I send before, right?
>>>
>>> Regards,
>>>
>>> Anderson Briglia
>>>
>>> On 09/09/2010 03:58 PM, Pavan Savoy wrote:
>>>
>>>>
>>>> I have an LE enabled BT controller, and I happened to send across a
>>>> simple "leadv" from the recently updated hciconfig
>>>> I got back the following data
>>>> "4 e 5 1 a 20 c 3a" and hence
>>>> "Can't set advertise mode on hci0: Success (0)"
>>>> and 0xC I guess by the BT spec means the command is disallowed (for
>>>> reasons unknown?....)
>>>>
>>>> So I'm just wondering, am I supposed to run some HCI-VS commands to
>>>> enable LE? I mean I should ask my vendor I agree, but anyone who has
>>>> got it working.. do they run some VS commands before enabling LE
>>>> advertising?
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe
>>>> linux-bluetooth"
>>>> in
>>>> the body of a message to [email protected]
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>
>>>>
>>>
>>>
>
>
On 09/10/2010 12:53 PM, Pavan Savoy wrote:
> Nope, I haven't applied the kernel patches...
> But my kernel diff to the latest kernel is only regarding the "block"
> and "unblock" to black list devices....
>
> do I need some patches in kernel for enabling/disabling BLE too ?
> I thought it just sends out the commands to controller...
>
You are right. You don't need to have the kernel patches.
I did some tests here and everything goes ok.
Check the hcidump output below:
2010-09-10 14:13:19.032099 < HCI Command: Unknown (0x08|0x000a) plen 1
0000: 01 .
2010-09-10 14:13:19.070320 > HCI Event: Command Complete (0x0e) plen 4
Unknown (0x08|0x000a) ncmd 2
0000: 00
I just did a hciconfig hci0 leadv
Regards,
Anderson Briglia
> On Fri, Sep 10, 2010 at 8:40 AM, Anderson Briglia
> <[email protected]> wrote:
>
>> Hi Pavan,
>>
>> Try to make a hciconfig reset before setting leadv.
>> Are you using that kernel patches I send before, right?
>>
>> Regards,
>>
>> Anderson Briglia
>>
>> On 09/09/2010 03:58 PM, Pavan Savoy wrote:
>>
>>> I have an LE enabled BT controller, and I happened to send across a
>>> simple "leadv" from the recently updated hciconfig
>>> I got back the following data
>>> "4 e 5 1 a 20 c 3a" and hence
>>> "Can't set advertise mode on hci0: Success (0)"
>>> and 0xC I guess by the BT spec means the command is disallowed (for
>>> reasons unknown?....)
>>>
>>> So I'm just wondering, am I supposed to run some HCI-VS commands to
>>> enable LE? I mean I should ask my vendor I agree, but anyone who has
>>> got it working.. do they run some VS commands before enabling LE
>>> advertising?
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
>>> in
>>> the body of a message to [email protected]
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>>
>>
>>
Is it possible that BT controller is not in standby state. i.e. it could be already in scanning or advertising sate by default?
Mike
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Pavan Savoy
Sent: Friday, September 10, 2010 9:53 AM
To: Anderson Briglia
Cc: [email protected]
Subject: Re: set LE advertise not working...
Nope, I haven't applied the kernel patches...
But my kernel diff to the latest kernel is only regarding the "block"
and "unblock" to black list devices....
do I need some patches in kernel for enabling/disabling BLE too ?
I thought it just sends out the commands to controller...
On Fri, Sep 10, 2010 at 8:40 AM, Anderson Briglia
<[email protected]> wrote:
> Hi Pavan,
>
> Try to make a hciconfig reset before setting leadv.
> Are you using that kernel patches I send before, right?
>
> Regards,
>
> Anderson Briglia
>
> On 09/09/2010 03:58 PM, Pavan Savoy wrote:
>>
>> I have an LE enabled BT controller, and I happened to send across a
>> simple "leadv" from the recently updated hciconfig
>> I got back the following data
>> "4 e 5 1 a 20 c 3a" and hence
>> "Can't set advertise mode on hci0: Success (0)"
>> and 0xC I guess by the BT spec means the command is disallowed (for
>> reasons unknown?....)
>>
>> So I'm just wondering, am I supposed to run some HCI-VS commands to
>> enable LE? I mean I should ask my vendor I agree, but anyone who has
>> got it working.. do they run some VS commands before enabling LE
>> advertising?
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
>> in
>> the body of a message to [email protected]
>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>>
>
>
Nope, I haven't applied the kernel patches...
But my kernel diff to the latest kernel is only regarding the "block"
and "unblock" to black list devices....
do I need some patches in kernel for enabling/disabling BLE too ?
I thought it just sends out the commands to controller...
On Fri, Sep 10, 2010 at 8:40 AM, Anderson Briglia
<[email protected]> wrote:
> Hi Pavan,
>
> Try to make a hciconfig reset before setting leadv.
> Are you using that kernel patches I send before, right?
>
> Regards,
>
> Anderson Briglia
>
> On 09/09/2010 03:58 PM, Pavan Savoy wrote:
>>
>> I have an LE enabled BT controller, and I happened to send across a
>> simple "leadv" from the recently updated hciconfig
>> I got back the following data
>> "4 e 5 1 a 20 c 3a" and hence
>> "Can't set advertise mode on hci0: Success (0)"
>> and 0xC I guess by the BT spec means the command is disallowed (for
>> reasons unknown?....)
>>
>> So I'm just wondering, am I supposed to run some HCI-VS commands to
>> enable LE? I mean I should ask my vendor I agree, but anyone who has
>> got it working.. do they run some VS commands before enabling LE
>> advertising?
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth"
>> in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
Hi Pavan,
Try to make a hciconfig reset before setting leadv.
Are you using that kernel patches I send before, right?
Regards,
Anderson Briglia
On 09/09/2010 03:58 PM, Pavan Savoy wrote:
> I have an LE enabled BT controller, and I happened to send across a
> simple "leadv" from the recently updated hciconfig
> I got back the following data
> "4 e 5 1 a 20 c 3a" and hence
> "Can't set advertise mode on hci0: Success (0)"
> and 0xC I guess by the BT spec means the command is disallowed (for
> reasons unknown?....)
>
> So I'm just wondering, am I supposed to run some HCI-VS commands to
> enable LE? I mean I should ask my vendor I agree, but anyone who has
> got it working.. do they run some VS commands before enabling LE
> advertising?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>