Re: [pandaboard] Enabling Bluetooth LE

[Pavan Savoy]

On Mon, Aug 6, 2012 at 5:44 PM, John Tobias <john.to...@gmail.com> wrote:
> Hello All,
>
> Is there anyone here successfully enabled the Bluetooth in Pandaboard ES in
> low energy mode?. I tried the "hcitool lescan" but I was getting an
> input/output error.

Do you have basic BT working ? hcitool scan ?
Can you also try and enable hcidump -X before running the command ?

If there is a command not allowed error which is happening then you
might need a new fw .bts file.
Also, what is the chip ID that you get ? TIInit_7.x.x ?

> Regards,
>
> John



--
--Pavan Savoy

[John Tobias]

hcitool scan is working. I haveTIInit_7.6.15.bts file. May I know the latest version of .bts file and where can I get a copy?.

Regards,

John

[Pavan Savoy]

On Tue, Aug 7, 2012 at 11:15 AM, John Tobias <john.to...@gmail.com> wrote:
> hcitool scan is working. I haveTIInit_7.6.15.bts file. May I know the latest
> version of .bts file and where can I get a copy?.

Well we need to determine if the existing fw already supports LE or not.
So, enable hcidump -X & then perform a hciconfig hci0 lestates - and
then let's see what the output says ??

> Regards,
>
> John
>
>
> On Tue, Aug 7, 2012 at 8:42 AM, Pavan Savoy <pavan...@gmail.com> wrote:
>>
>> On Mon, Aug 6, 2012 at 5:44 PM, John Tobias <john.to...@gmail.com>
>> wrote:
>> > Hello All,
>> >
>> > Is there anyone here successfully enabled the Bluetooth in Pandaboard ES
>> > in
>> > low energy mode?. I tried the "hcitool lescan" but I was getting an
>> > input/output error.
>>
>> Do you have basic BT working ? hcitool scan ?
>> Can you also try and enable hcidump -X before running the command ?
>>
>> If there is a command not allowed error which is happening then you
>> might need a new fw .bts file.
>> Also, what is the chip ID that you get ? TIInit_7.x.x ?
>>
>> > Regards,
>> >
>> > John
>>
>>
>>
>> --
>> --Pavan Savoy
>
>

--
--Pavan Savoy

[John Tobias]

Here are the output of the two commands:

#hcidump -X

HCI sniffer - Bluetooth packet analyzer ver 2.2

device: hci0 snap_len: 1028 filter: 0xffffffff

< HCI Command: LE Read Supported States (0x08|0x001c) plen 0

> HCI Event: Command Complete (0x0e) plen 8

    LE Read Supported States (0x08|0x001c) ncmd 1

    0000: 0c 60 47 bc 53                                    .`G.S

#hciconfig hci0 lestates

Read LE supported states on hci0 returned status 12

john

[Pavan Savoy]

On Tue, Aug 7, 2012 at 1:31 PM, John Tobias <john.to...@gmail.com> wrote:
> Here are the output of the two commands:
>
> #hcidump -X
> HCI sniffer - Bluetooth packet analyzer ver 2.2
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: LE Read Supported States (0x08|0x001c) plen 0
>> HCI Event: Command Complete (0x0e) plen 8
> LE Read Supported States (0x08|0x001c) ncmd 1
> 0000: 0c 60 47 bc 53 .`G.S
>
> #hciconfig hci0 lestates
> Read LE supported states on hci0 returned status 12

Yep, 0x0c or 12 is for unsupported command. So the fw doesn't seem to
have support for LE.
Let me get back to you on this, need to check up what fw is upon the repository.

--
--Pavan Savoy

[John Tobias]

thanks for the info.

Are you referring to the .bts file?

[Pavan Savoy]

On Tue, Aug 7, 2012 at 2:44 PM, John Tobias <john.to...@gmail.com> wrote:
> thanks for the info.
> Are you referring to the .bts file?

Yes, a BLE enabling BTS file.
In the mean-time, just for trial purposes, can you try
hcitool cmd 0x3f 0x015B 0x1 0x0 & hcitool cmd 0x3f 0x01DD 0x1 ?
& then try hciconfig hci0 lestates ?

& then hcitool cmd 0x3f 0x015B 0x1 0x0 + hciconfig hci0 lestates ?

--
--Pavan Savoy

[John Tobias]

Here are the output:

< HCI Command: ogf 0x3f, ocf 0x015b, plen 2

  01 00 

> HCI Event: 0x0e plen 4

  01 5B FD 1F 

< HCI Command: ogf 0x3f, ocf 0x01dd, plen 1

  01 

> HCI Event: 0x0e plen 4

  01 DD FD 00 

Supported link layer states:

        YES Non-connectable Advertising State

        YES Scannable Advertising State

        YES Connectable Advertising State

        YES Directed Advertising State

        YES Passive Scanning State

        YES Active Scanning State

        YES Initiating State/Connection State in Master Role

        YES Connection State in the Slave Role

        YES Non-connectable Advertising State and Passive Scanning State combination

        YES Scannable Advertising State and Passive Scanning State combination

        YES Connectable Advertising State and Passive Scanning State combination

        YES Directed Advertising State and Passive Scanning State combination

        NO  Non-connectable Advertising State and Active Scanning State combination

        NO  Scannable Advertising State and Active Scanning State combination

        NO  Connectable Advertising State and Active Scanning State combination

        NO  Directed Advertising State and Active Scanning State combination

        NO  Non-connectable Advertising State and Initiating State combination

        NO  Scannable Advertising State and Initiating State combination

        NO  Non-connectable Advertising State and Master Role combination

        NO  Scannable Advertising State and Master Role combination

        NO  Non-connectable Advertising State and Slave Role combination

        NO  Scannable Advertising State and Slave Role combination

        NO  Passive Scanning State and Initiating State combination

        NO  Active Scanning State and Initiating State combination

        NO  Passive Scanning State and Master Role combination

        NO  Active Scanning State and Master Role combination

        NO  Passive Scanning State and Slave Role combination

        NO  Active Scanning State and Slave Role combination

        NO  Initiating State and Master Role combination/Master Role and Master Role combination

< HCI Command: ogf 0x3f, ocf 0x015b, plen 2

  01 00 

> HCI Event: 0x0e plen 4

  01 5B FD 1F 

Supported link layer states:

        YES Non-connectable Advertising State

        YES Scannable Advertising State

        YES Connectable Advertising State

        YES Directed Advertising State

        YES Passive Scanning State

        YES Active Scanning State

        YES Initiating State/Connection State in Master Role

        YES Connection State in the Slave Role

        YES Non-connectable Advertising State and Passive Scanning State combination

        YES Scannable Advertising State and Passive Scanning State combination

        YES Connectable Advertising State and Passive Scanning State combination

        YES Directed Advertising State and Passive Scanning State combination

        NO  Non-connectable Advertising State and Active Scanning State combination

        NO  Scannable Advertising State and Active Scanning State combination

        NO  Connectable Advertising State and Active Scanning State combination

        NO  Directed Advertising State and Active Scanning State combination

        NO  Non-connectable Advertising State and Initiating State combination

        NO  Scannable Advertising State and Initiating State combination

        NO  Non-connectable Advertising State and Master Role combination

        NO  Scannable Advertising State and Master Role combination

        NO  Non-connectable Advertising State and Slave Role combination

        NO  Scannable Advertising State and Slave Role combination

        NO  Passive Scanning State and Initiating State combination

        NO  Active Scanning State and Initiating State combination

        NO  Passive Scanning State and Master Role combination

        NO  Active Scanning State and Master Role combination

        NO  Passive Scanning State and Slave Role combination

        NO  Active Scanning State and Slave Role combination

        NO  Initiating State and Master Role combination/Master Role and Master Role combination

[Pavan Savoy]

On Tue, Aug 7, 2012 at 3:15 PM, John Tobias <john.to...@gmail.com> wrote:
> Here are the output:

oh good then.
with these you can at-least start advertising to begin with and scan
from another LE device...

--
--Pavan Savoy

[John Tobias]

Pavan,

Do you know what is the up-to-date .bts file and where should I get it?.

Thanks,

John

[Pavan Savoy]

On Tue, Aug 7, 2012 at 4:40 PM, John Tobias <john.to...@gmail.com> wrote:
> Pavan,
>
> Do you know what is the up-to-date .bts file and where should I get it?.

Well I am looking into the option of having them released, Not sure
how and when ...
However, till that time, you can certainly go ahead with the commands
that I sent out to begin LE stuff.

Basic LE command now should not be blocked, any other LE command that
would come via the fw would be pretty much bug-fixes.

--
--Pavan Savoy

[Martin Maurer]

Hello Pavan,

 

is there a description of the commands / events you sent to the module?

Are the vendor specific command / events and  normal BT LE commands / events included somewhere in a datasheet

of the Bluetooth chip?

 

Best regards,

 

Martin

[Pavan Savoy]

On Wed, Aug 8, 2012 at 12:39 AM, Martin Maurer
<meinemai...@online.de> wrote:
> Hello Pavan,
>
> is there a description of the commands / events you sent to the module?
> Are the vendor specific command / events and normal BT LE commands / events
> included somewhere in a datasheet
> of the Bluetooth chip?

Yes, they are vendor specific commands, They seem to be only
applicable to WL1273L, don't have either a device or data-sheet at end
- right away to refer to them.
But those are related to LE reset and LE enable.

--
--Pavan Savoy

[John Tobias]

Hi Pavan,

I have a follow up question, I got the latest kernel being used by ubuntu (3.2.24), I did cross compile, the wifi is working but when I do the hcitool dev, it did not detect the hcixx.

I am just wondering if there's a step to follow to detect the hcix. I loaded the bluetooth driver, hci_uart.

Regards,

John

[Pavan Savoy]

Hi,

On Fri, Aug 10, 2012 at 6:05 PM, John Tobias <john.to...@gmail.com> wrote:
> Hi Pavan,
>
> I have a follow up question, I got the latest kernel being used by ubuntu
> (3.2.24), I did cross compile, the wifi is working but when I do the hcitool
> dev, it did not detect the hcixx.

Do you happen to have btwilink.ko built in ? lsmod would show if it
exists, try and execute a modprobe btwilink.ko if not.
Also, can you check up on the following sysfs entries ?

/sys/devices/platform/kim ? & /sys/devices/platform/btwilink.

--
--Pavan Savoy

[John Tobias]

I searched the sys directory and I got the following:

(But now /sys/devices/platform/btwilink exist on sys directory)

./bus/platform/drivers/btwilink

./module/st_drv/holders/btwilink

./module/btwilink

./devices/platform/kim

./bus/platform/devices/kim

./bus/platform/drivers/kim

./bus/platform/drivers/kim/kim

Also, I posted my kernel messages;

[    0.877746] driver: 'omap_timer.6': driver_bound: bound to device 'omap_timer'

[    0.877746] bus: 'platform': really_probe: bound device omap_timer.6 to driver omap_timer

[    0.877807] bus: 'platform': driver_probe_device: matched device omap_timer.7 with driver omap_timer

[    0.877838] bus: 'platform': really_probe: probing driver omap_timer with device omap_timer.7

[    0.877929] driver: 'omap_timer.7': driver_bound: bound to device 'omap_timer'

[    0.877929] bus: 'platform': really_probe: bound device omap_timer.7 to driver omap_timer

[    0.877990] bus: 'platform': driver_probe_device: matched device omap_timer.8 with driver omap_timer

[    0.877990] bus: 'platform': really_probe: probing driver omap_timer with device omap_timer.8

[    0.878082] driver: 'omap_timer.8': driver_bound: bound to device 'omap_timer'

[    0.878112] bus: 'platform': really_probe: bound device omap_timer.8 to driver omap_timer

[    0.878143] bus: 'platform': driver_probe_device: matched device omap_timer.9 with driver omap_timer

[    0.878173] bus: 'platform': really_probe: probing driver omap_timer with device omap_timer.9

[    0.878265] driver: 'omap_timer.9': driver_bound: bound to device 'omap_timer'

[    0.878265] bus: 'platform': really_probe: bound device omap_timer.9 to driver omap_timer

[    0.878326] bus: 'platform': driver_probe_device: matched device omap_timer.10 with driver omap_timer

[    0.878326] bus: 'platform': really_probe: probing driver omap_timer with device omap_timer.10

[    0.878417] driver: 'omap_timer.10': driver_bound: bound to device 'omap_timer'

[    0.878417] bus: 'platform': really_probe: bound device omap_timer.10 to driver omap_timer

[    0.878479] bus: 'platform': driver_probe_device: matched device omap_timer.11 with driver omap_timer

[    0.878479] bus: 'platform': really_probe: probing driver omap_timer with device omap_timer.11

[    0.878570] driver: 'omap_timer.11': driver_bound: bound to device 'omap_timer'

[    0.878601] bus: 'platform': really_probe: bound device omap_timer.11 to driver omap_timer

[    0.879180] Registering sysdev class 'clocksource'

[    0.879455] Registering sys device of class 'clocksource'

[    0.879486] Registering sys device 'clocksource0'

[    0.879852] bus: 'platform': add driver alarmtimer

[    0.880279] Registering platform device 'alarmtimer'. Parent at platform

[    0.880279] device: 'alarmtimer': device_add

[    0.880310] bus: 'platform': add device alarmtimer

[    0.880401] PM: Adding info for platform:alarmtimer

[    0.880706] bus: 'platform': driver_probe_device: matched device alarmtimer with driver alarmtimer

[    0.880737] bus: 'platform': really_probe: probing driver alarmtimer with device alarmtimer

[    0.880798] driver: 'alarmtimer': driver_bound: bound to device 'alarmtimer'

[    0.880798] bus: 'platform': really_probe: bound device alarmtimer to driver alarmtimer

[    1.016540] bus: 'event_source': registered

[    1.016601] device: 'breakpoint': device_add

[    1.016632] bus: 'event_source': add device breakpoint

[    1.016754] PM: Adding info for event_source:breakpoint

[    1.017089] device: 'tracepoint': device_add

[    1.017181] bus: 'event_source': add device tracepoint

[    1.017272] PM: Adding info for event_source:tracepoint

[    1.017547] device: 'software': device_add

[    1.017608] bus: 'event_source': add device software

[    1.017791] PM: Adding info for event_source:software

[    1.029754] VFS: Disk quotas dquot_6.5.2

[    1.029998] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

[    1.032592] JFFS2 version 2.2. (NAND) (SUMMARY)  \xffffffc2\xffffffa9\xffffffa9 2001-2006 Red Hat, Inc.

[    1.033447] msgmni has been set to 1463

[    1.035949] io scheduler noop registered

[    1.035980] io scheduler deadline registered

[    1.036163] io scheduler cfq registered (default)

[    1.036224] device: 'fbcon': device_add

[    1.036346] PM: Adding info for No Bus:fbcon

[    1.036773] bus: 'platform': add driver platform-lcd

[    1.037200] bus: 'platform': add driver generic-bl

[    1.037567] device class 'display': registering

[    1.037902] device: 'ptmx': device_add

[    1.038024] PM: Adding info for No Bus:ptmx

[    1.038299] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

[    1.038482] Registering platform device 'serial8250'. Parent at platform

[    1.038513] device: 'serial8250': device_add

[    1.038543] bus: 'platform': add device serial8250

[    1.038635] PM: Adding info for platform:serial8250

[    1.039123] device: 'ttyS0': device_add

[    1.039398] PM: Adding info for No Bus:ttyS0

[    1.056365] device: 'ttyS1': device_add

[    1.056549] PM: Adding info for No Bus:ttyS1

[    1.087493] device: 'ttyS2': device_add

[    1.087677] PM: Adding info for No Bus:ttyS2

[    1.110961] device: 'ttyS3': device_add

[    1.111114] PM: Adding info for No Bus:ttyS3

[    1.142181] bus: 'platform': add driver serial8250

[    1.142303] bus: 'platform': driver_probe_device: matched device serial8250 with driver serial8250

[    1.142333] bus: 'platform': really_probe: probing driver serial8250 with device serial8250

[    1.142364] driver: 'serial8250': driver_bound: bound to device 'serial8250'

[    1.142395] bus: 'platform': really_probe: bound device serial8250 to driver serial8250

[    1.142730] bus: 'platform': add driver omap_uart

[    1.142791] bus: 'platform': driver_probe_device: matched device omap_uart.0 with driver omap_uart

[    1.142822] bus: 'platform': really_probe: probing driver omap_uart with device omap_uart.0

[    1.142944] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 104) is a OMAP UART0

[    1.143127] device: 'ttyO0': device_add

[    1.143371] PM: Adding info for No Bus:ttyO0

[    1.157806] driver: 'omap_uart.0': driver_bound: bound to device 'omap_uart'

[    1.157836] bus: 'platform': really_probe: bound device omap_uart.0 to driver omap_uart

[    1.157867] bus: 'platform': driver_probe_device: matched device omap_uart.1 with driver omap_uart

[    1.157867] bus: 'platform': really_probe: probing driver omap_uart with device omap_uart.1

[    1.157928] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 105) is a OMAP UART1

[    1.158020] device: 'ttyO1': device_add

[    1.158203] PM: Adding info for No Bus:ttyO1

[    1.189056] driver: 'omap_uart.1': driver_bound: bound to device 'omap_uart'

[    1.189056] bus: 'platform': really_probe: bound device omap_uart.1 to driver omap_uart

[    1.189086] bus: 'platform': driver_probe_device: matched device omap_uart.2 with driver omap_uart

[    1.189117] bus: 'platform': really_probe: probing driver omap_uart with device omap_uart.2

[    1.189178] omap_uart.2: ttyO2 at MMIO 0x48020000 (irq = 106) is a OMAP UART2

[    2.058685] console [ttyO2] enabled

[    2.062408] device: 'ttyO2': device_add

[    2.062622] PM: Adding info for No Bus:ttyO2

[    2.071868] driver: 'omap_uart.2': driver_bound: bound to device 'omap_uart'

[    2.071868] bus: 'platform': really_probe: bound device omap_uart.2 to driver omap_uart

[    2.071899] bus: 'platform': driver_probe_device: matched device omap_uart.3 with driver omap_uart

[    2.071929] bus: 'platform': really_probe: probing driver omap_uart with device omap_uart.3

[    2.071990] omap_uart.3: ttyO3 at MMIO 0x4806e000 (irq = 102) is a OMAP UART3

[    2.079620] device: 'ttyO3': device_add

[    2.079803] PM: Adding info for No Bus:ttyO3

[    2.126556] driver: 'omap_uart.3': driver_bound: bound to device 'omap_uart'

[    2.126556] bus: 'platform': really_probe: bound device omap_uart.3 to driver omap_uart

[    2.129302] device: '1:0': device_add

[    2.129425] PM: Adding info for No Bus:1:0

[    2.129760] device: 'ram0': device_add

[    2.129974] PM: Adding info for No Bus:ram0

[    2.130554] device: '1:1': device_add

[    2.130676] PM: Adding info for No Bus:1:1

[    2.131011] device: 'ram1': device_add

[    2.131195] PM: Adding info for No Bus:ram1

[    2.131683] device: '1:2': device_add

[    2.131774] PM: Adding info for No Bus:1:2

[    2.132110] device: 'ram2': device_add

[    2.132293] PM: Adding info for No Bus:ram2

[    2.132781] device: '1:3': device_add

[    2.132904] PM: Adding info for No Bus:1:3

[    2.133239] device: 'ram3': device_add

[    2.133422] PM: Adding info for No Bus:ram3

[    2.133911] device: '1:4': device_add

[    2.134002] PM: Adding info for No Bus:1:4

[    2.134399] device: 'ram4': device_add

[    2.134582] PM: Adding info for No Bus:ram4

[    2.135070] device: '1:5': device_add

[    2.135192] PM: Adding info for No Bus:1:5

[    2.135498] device: 'ram5': device_add

[    2.135681] PM: Adding info for No Bus:ram5

[    2.136169] device: '1:6': device_add

[    2.136291] PM: Adding info for No Bus:1:6

[    2.136627] device: 'ram6': device_add

[    2.136810] PM: Adding info for No Bus:ram6

[    2.137298] device: '1:7': device_add

[    2.137420] PM: Adding info for No Bus:1:7

[    2.137725] device: 'ram7': device_add

[    2.137908] PM: Adding info for No Bus:ram7

[    2.138397] device: '1:8': device_add

[    2.138519] PM: Adding info for No Bus:1:8

[    2.138854] device: 'ram8': device_add

[    2.139068] PM: Adding info for No Bus:ram8

[    2.139556] device: '1:9': device_add

[    2.139678] PM: Adding info for No Bus:1:9

[    2.139984] device: 'ram9': device_add

[    2.140197] PM: Adding info for No Bus:ram9

[    2.140686] device: '1:10': device_add

[    2.140777] PM: Adding info for No Bus:1:10

[    2.141113] device: 'ram10': device_add

[    2.141296] PM: Adding info for No Bus:ram10

[    2.141815] device: '1:11': device_add

[    2.141937] PM: Adding info for No Bus:1:11

[    2.142333] device: 'ram11': device_add

[    2.142517] PM: Adding info for No Bus:ram11

[    2.143066] device: '1:12': device_add

[    2.143188] PM: Adding info for No Bus:1:12

[    2.143524] device: 'ram12': device_add

[    2.143707] PM: Adding info for No Bus:ram12

[    2.144165] device: '1:13': device_add

[    2.144287] PM: Adding info for No Bus:1:13

[    2.144592] device: 'ram13': device_add

[    2.144775] PM: Adding info for No Bus:ram13

[    2.145263] device: '1:14': device_add

[    2.145385] PM: Adding info for No Bus:1:14

[    2.145690] device: 'ram14': device_add

[    2.145874] PM: Adding info for No Bus:ram14

[    2.146362] device: '1:15': device_add

[    2.146484] PM: Adding info for No Bus:1:15

[    2.146850] device: 'ram15': device_add

[    2.147033] PM: Adding info for No Bus:ram15

[    2.147491] brd: module loaded

[    2.150878] device: 'loop-control': device_add

[    2.151153] PM: Adding info for No Bus:loop-control

[    2.152099] device: '7:0': device_add

[    2.152313] PM: Adding info for No Bus:7:0

[    2.152984] device: 'loop0': device_add

[    2.153167] PM: Adding info for No Bus:loop0

[    2.153961] device: '7:1': device_add

[    2.154083] PM: Adding info for No Bus:7:1

[    2.154449] device: 'loop1': device_add

[    2.154632] PM: Adding info for No Bus:loop1

[    2.155334] device: '7:2': device_add

[    2.155456] PM: Adding info for No Bus:7:2

[    2.155822] device: 'loop2': device_add

[    2.156036] PM: Adding info for No Bus:loop2

[    2.156707] device: '7:3': device_add

[    2.156860] PM: Adding info for No Bus:7:3

[    2.157196] device: 'loop3': device_add

[    2.157409] PM: Adding info for No Bus:loop3

[    2.158142] device: '7:4': device_add

[    2.158264] PM: Adding info for No Bus:7:4

[    2.158630] device: 'loop4': device_add

[    2.158843] PM: Adding info for No Bus:loop4

[    2.159515] device: '7:5': device_add

[    2.159667] PM: Adding info for No Bus:7:5

[    2.160003] device: 'loop5': device_add

[    2.160186] PM: Adding info for No Bus:loop5

[    2.160888] device: '7:6': device_add

[    2.161010] PM: Adding info for No Bus:7:6

[    2.161376] device: 'loop6': device_add

[    2.161590] PM: Adding info for No Bus:loop6

[    2.162292] device: '7:7': device_add

[    2.162414] PM: Adding info for No Bus:7:7

[    2.162780] device: 'loop7': device_add

[    2.162963] PM: Adding info for No Bus:loop7

[    2.163482] loop: module loaded

[    2.166839] bus: 'i2c': add driver menelaus

[    2.167205] bus: 'platform': add driver twl4030-audio

[    2.167694] device class 'scsi_disk': registering

[    2.167968] bus: 'scsi': add driver sd

[    2.168365] device class 'mtd': registering

[    2.168762] device: 'mtd-unmap': device_add

[    2.168884] PM: Adding info for No Bus:mtd-unmap

[    2.169342] device: 'mtd-romap': device_add

[    2.169464] PM: Adding info for No Bus:mtd-romap

[    2.169952] device: 'mtd-rwmap': device_add

[    2.170043] PM: Adding info for No Bus:mtd-rwmap

[    2.170989] mtdoops: mtd device (mtddev=name/number) must be supplied

[    2.177886] omap2-nand driver initializing

[    2.182250] bus: 'platform': add driver omap2-nand

[    2.182678] OneNAND driver initializing

[    2.186737] bus: 'platform': add driver omap2-onenand

[    2.187133] device class 'ubi': registering

[    2.187438] device: 'ubi_ctrl': device_add

[    2.187591] PM: Adding info for No Bus:ubi_ctrl

[    2.187957] bus: 'mdio_bus': add driver SMSC LAN83C185

[    2.188262] bus: 'mdio_bus': add driver SMSC LAN8187

[    2.188537] bus: 'mdio_bus': add driver SMSC LAN8700

[    2.188842] bus: 'mdio_bus': add driver SMSC LAN911x Internal PHY

[    2.189178] bus: 'mdio_bus': add driver SMSC LAN8710/LAN8720

[    2.189453] bus: 'spi': add driver ks8851

[    2.189758] bus: 'platform': add driver ks8851_mll

[    2.190155] bus: 'platform': add driver smc91x

[    2.190551] bus: 'platform': add driver smsc911x

[    2.190948] bus: 'usb': add driver asix

[    2.191314] usbcore: registered new interface driver asix

[    2.197052] bus: 'usb': add driver cdc_ether

[    2.197387] usbcore: registered new interface driver cdc_ether

[    2.203552] bus: 'usb': add driver smsc95xx

[    2.203887] usbcore: registered new interface driver smsc95xx

[    2.209991] bus: 'usb': add driver net1080

[    2.210327] usbcore: registered new interface driver net1080

[    2.216339] bus: 'usb': add driver cdc_subset

[    2.216644] usbcore: registered new interface driver cdc_subset

[    2.222930] bus: 'usb': add driver zaurus

[    2.223266] usbcore: registered new interface driver zaurus

[    2.229217] cdc_ncm: 04-Aug-2011

[    2.232635] bus: 'usb': add driver cdc_ncm

[    2.232940] usbcore: registered new interface driver cdc_ncm

[    2.238983] device class 'usbmon': registering

[    2.239349] device: 'usbmon0': device_add

[    2.239471] PM: Adding info for No Bus:usbmon0

[    2.239898] bus: 'usb': add driver cdc_wdm

[    2.240234] usbcore: registered new interface driver cdc_wdm

[    2.246246] Initializing USB Mass Storage driver...

[    2.251403] bus: 'usb': add driver usb-storage

[    2.251770] usbcore: registered new interface driver usb-storage

[    2.258148] USB Mass Storage support registered.

[    2.263153] bus: 'usb': add driver libusual

[    2.263854] usbcore: registered new interface driver libusual

[    2.269958] bus: 'usb': add driver usbtest

[    2.270324] usbcore: registered new interface driver usbtest

[    2.276397] device: 'mice': device_add

[    2.276519] PM: Adding info for No Bus:mice

[    2.276916] device: 'psaux': device_add

[    2.277038] PM: Adding info for No Bus:psaux

[    2.277313] mousedev: PS/2 mouse device common for all mice

[    2.283264] bus: 'serio': add driver atkbd

[    2.283721] bus: 'platform': add driver twl4030_keypad

[    2.284454] bus: 'serio': add driver psmouse

[    2.284881] bus: 'spi': add driver ads7846

[    2.285217] bus: 'platform': add driver twl4030_pwrbutton

[    2.285614] bus: 'platform': remove driver twl4030_pwrbutton

[    2.285888] driver: 'twl4030_pwrbutton': driver_release

[    2.285919] bus: 'platform': add driver twl_rtc

[    2.286010] bus: 'platform': driver_probe_device: matched device twl_rtc with driver twl_rtc

[    2.286041] bus: 'platform': really_probe: probing driver twl_rtc with device twl_rtc

[    2.286529] twl_rtc twl_rtc: Power up reset detected.

[    2.292938] twl_rtc twl_rtc: Enabling TWL-RTC.

[    2.299530] device: 'rtc0': device_add

[    2.299743] PM: Adding info for No Bus:rtc0

[    2.300201] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0

[    2.307006] driver: 'twl_rtc': driver_bound: bound to device 'twl_rtc'

[    2.307006] bus: 'platform': really_probe: bound device twl_rtc to driver twl_rtc

[    2.307342] i2c /dev entries driver

[    2.311035] device class 'i2c-dev': registering

[    2.311462] device: 'i2c-1': device_add

[    2.311737] PM: Adding info for No Bus:i2c-1

[    2.312408] device: 'i2c-2': device_add

[    2.312561] PM: Adding info for No Bus:i2c-2

[    2.312896] device: 'i2c-3': device_add

[    2.313049] PM: Adding info for No Bus:i2c-3

[    2.313354] device: 'i2c-4': device_add

[    2.313476] PM: Adding info for No Bus:i2c-4

[    2.313781] Driver for 1-wire Dallas network protocol.

[    2.319549] bus: 'w1': registered

[    2.319580] bus: 'w1': add driver w1_master_driver

[    2.319885] bus: 'w1': add driver w1_slave_driver

[    2.320190] bus: 'platform': add driver omap_wdt

[    2.320312] bus: 'platform': driver_probe_device: matched device omap_wdt with driver omap_wdt

[    2.320343] bus: 'platform': really_probe: probing driver omap_wdt with device omap_wdt

[    2.320922] device: 'watchdog': device_add

[    2.321166] PM: Adding info for No Bus:watchdog

[    2.321655] OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec

[    2.328033] driver: 'omap_wdt': driver_bound: bound to device 'omap_wdt'

[    2.328063] bus: 'platform': really_probe: bound device omap_wdt to driver omap_wdt

[    2.328399] bus: 'platform': add driver twl4030_wdt

[    2.328796] Bluetooth: HCI UART driver ver 2.2

[    2.333526] Bluetooth: HCI H4 protocol initialized

[    2.338623] Bluetooth: HCI BCSP protocol initialized

[    2.343841] Bluetooth: HCILL protocol initialized

[    2.348846] Bluetooth: Broadcom Blutonium firmware driver ver 1.2

[    2.355316] bus: 'usb': add driver bcm203x

[    2.355651] usbcore: registered new interface driver bcm203x

[    2.361663] Bluetooth: Digianswer Bluetooth USB driver ver 0.10

[    2.367919] bus: 'usb': add driver bpa10x

[    2.368286] usbcore: registered new interface driver bpa10x

[    2.374206] Bluetooth: Generic Bluetooth USB driver ver 0.6

[    2.380096] bus: 'usb': add driver btusb

[    2.380462] usbcore: registered new interface driver btusb

[    2.386291] Bluetooth: Generic Bluetooth SDIO driver ver 0.1

[    2.392272] bus: 'sdio': add driver btsdio

[    2.392578] bus: 'mmc': add driver mmcblk

[    2.392913] bus: 'sdio': add driver sdio_uart

[    2.393218] bus: 'platform': add driver mmci-omap

[    2.393615] bus: 'platform': remove driver mmci-omap

[    2.393890] driver: 'mmci-omap': driver_release

[    2.394134] bus: 'platform': add driver omap_hsmmc

[    2.394195] bus: 'platform': driver_probe_device: matched device omap_hsmmc.0 with driver omap_hsmmc

[    2.394226] bus: 'platform': really_probe: probing driver omap_hsmmc with device omap_hsmmc.0

[    2.398864] device: 'mmc0': device_add

[    2.398986] PM: Adding info for No Bus:mmc0

[    2.400695] driver: 'omap_hsmmc.0': driver_bound: bound to device 'omap_hsmmc'

[    2.400726] bus: 'platform': really_probe: bound device omap_hsmmc.0 to driver omap_hsmmc

[    2.400787] bus: 'platform': driver_probe_device: matched device omap_hsmmc.4 with driver omap_hsmmc

[    2.400817] bus: 'platform': really_probe: probing driver omap_hsmmc with device omap_hsmmc.4

[    2.401153] device: 'mmc1': device_add

[    2.401275] PM: Adding info for No Bus:mmc1

[    2.403533] driver: 'omap_hsmmc.4': driver_bound: bound to device 'omap_hsmmc'

[    2.403564] bus: 'platform': really_probe: bound device omap_hsmmc.4 to driver omap_hsmmc

[    2.404479] bus: 'hid': registered

[    2.404541] bus: 'hid': add driver generic-usb

[    2.404937] bus: 'usb': add driver usbhid

[    2.405273] usbcore: registered new interface driver usbhid

[    2.411224] usbhid: USB HID core driver

[    2.415252] oprofile: hardware counters not available

[    2.420715] oprofile: using timer interrupt.

[    2.425659] TCP cubic registered

[    2.429077] Initializing XFRM netlink socket

[    2.433685] NET: Registered protocol family 17

[    2.438446] NET: Registered protocol family 15

[    2.443420] Bluetooth: RFCOMM socket layer initialized

[    2.448944] Bluetooth: RFCOMM ver 1.11

[    2.452880] Bluetooth: BNEP (Ethernet Emulation) ver 1.3

[    2.458526] Bluetooth: HIDP (Human Interface Emulation) ver 1.2

[    2.464813] bus: 'hid': add driver generic-bluetooth

[    2.465423] lib80211: common routines for IEEE802.11 drivers

[    2.471496] lib80211_crypt: registered algorithm 'NULL'

[    2.471527] Registering the dns_resolver key type

[    2.476867] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

[    2.485015] ThumbEE CPU extension supported.

[    2.495544] omap_vc_i2c_init: I2C config for all channels must match.

[    2.502227] omap_vc_i2c_init: I2C config for all channels must match.

[    2.509918] Power Management for TI OMAP4.

[    2.536773] clock: disabling unused clocks to save power

[    2.542724] device: 'cpu_dma_latency': device_add

[    2.542846] PM: Adding info for No Bus:cpu_dma_latency

[    2.543273] device: 'network_latency': device_add

[    2.543426] PM: Adding info for No Bus:network_latency

[    2.543731] device: 'network_throughput': device_add

[    2.543884] PM: Adding info for No Bus:network_throughput

[    2.545318] regulator_init_complete: VANA: incomplete constraints, leaving on

[    2.553283] regulator_init_complete: CLK32KG: incomplete constraints, leaving on

[    2.562225] regulator_init_complete: VDAC: incomplete constraints, leaving on

[    2.570343] bus: 'platform': add driver gpio-keys

[    2.571807] twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)

[    2.581756] Freeing init memory: 312K

[    2.871765] mmc0: host does not support reading read-only switch. assuming write-enable.

[    2.926239] mmc0: new high speed SDHC card at address 0007

[    2.932373] device: 'mmc0:0007': device_add

[    2.932647] bus: 'mmc': add device mmc0:0007

[    2.932830] PM: Adding info for mmc:mmc0:0007

[    2.933105] bus: 'mmc': driver_probe_device: matched device mmc0:0007 with driver mmcblk

[    2.933105] bus: 'mmc': really_probe: probing driver mmcblk with device mmc0:0007

[    2.984100] mmcblk0: mmc0:0007 SD16G 14.9 GiB 

[    2.989074] device: '179:0': device_add

[    2.989288] PM: Adding info for No Bus:179:0

[    2.989746] device: 'mmcblk0': device_add

[    2.990417] PM: Adding info for No Bus:mmcblk0

[    2.994750]  mmcblk0: p1 p2

[    2.997894] device: 'mmcblk0p1': device_add

[    2.998260] PM: Adding info for No Bus:mmcblk0p1

[    2.998474] device: 'mmcblk0p2': device_add

[    2.998687] PM: Adding info for No Bus:mmcblk0p2

[    2.999420] driver: 'mmc0:0007': driver_bound: bound to device 'mmcblk'

[    2.999450] bus: 'mmc': really_probe: bound device mmc0:0007 to driver mmcblk

[    3.118164] mmc1: card claims to support voltages below the defined range. These will be ignored.

[    3.196044] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)

[    3.213165] mmc1: new SDIO card at address 0001

[    3.218048] device: 'mmc1:0001': device_add

[    3.218231] bus: 'mmc': add device mmc1:0001

[    3.218383] PM: Adding info for mmc:mmc1:0001

[    3.218444] bus: 'mmc': driver_probe_device: matched device mmc1:0001 with driver mmcblk

[    3.218475] bus: 'mmc': really_probe: probing driver mmcblk with device mmc1:0001

[    3.218536] mmcblk: probe of mmc1:0001 rejects match -19

[    3.219970] device: 'mmc1:0001:1': device_add

[    3.220031] bus: 'sdio': add device mmc1:0001:1

[    3.220184] PM: Adding info for sdio:mmc1:0001:1

[    3.220397] device: 'mmc1:0001:2': device_add

[    3.220428] bus: 'sdio': add device mmc1:0001:2

[    3.220550] PM: Adding info for sdio:mmc1:0001:2

[    3.635711] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem

[    3.643524] EXT4-fs (mmcblk0p2): write access will be enabled during recovery

[    7.417083] EXT4-fs (mmcblk0p2): recovery complete

[    7.450622] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)

[    8.573547] device: 'vcs7': device_add

[    8.573883] PM: Adding info for No Bus:vcs7

[    8.574127] device: 'vcsa7': device_add

[    8.574279] PM: Adding info for No Bus:vcsa7

[   21.097686] udevd[3195]: starting version 175

[   21.334411] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro

[   22.135772] bus: 'platform': add driver kim

[   22.135864] bus: 'platform': driver_probe_device: matched device kim with driver kim

[   22.135894] bus: 'platform': really_probe: probing driver kim with device kim

[   22.136077] (stk) :sysfs entries created

[   22.136199] (stk) : debugfs entries created 

[   22.136199] driver: 'kim': driver_bound: bound to device 'kim'

[   22.136230] bus: 'platform': really_probe: bound device kim to driver kim

[   22.177917] bus: 'i2c': add driver bma150

[   22.177978] bus: 'i2c': driver_probe_device: matched device 4-0038 with driver bma150

[   22.177978] bus: 'i2c': really_probe: probing driver bma150 with device 4-0038

[   22.178741] bma150 4-0038: BMA150 chip id error: -121

[   22.184295] bma150: probe of 4-0038 failed with error -22

[   22.206054] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0

[   22.206085] bus: 'platform': add driver btwilink

[   22.467651] device: 'vcs2': device_add

[   22.467834] PM: Adding info for No Bus:vcs2

[   22.468109] device: 'vcsa2': device_add

[   22.468231] PM: Adding info for No Bus:vcsa2

[   22.523498] device: 'vcs3': device_add

[   22.523651] PM: Adding info for No Bus:vcs3

[   22.524017] device: 'vcsa3': device_add

[   22.524200] PM: Adding info for No Bus:vcsa3

[   22.568725] device: 'vcs4': device_add

[   22.568969] PM: Adding info for No Bus:vcs4

[   22.569091] device: 'vcsa4': device_add

[   22.569274] PM: Adding info for No Bus:vcsa4

[   22.611572] device: 'vcs5': device_add

[   22.611724] PM: Adding info for No Bus:vcs5

[   22.611846] device: 'vcsa5': device_add

[   22.612182] PM: Adding info for No Bus:vcsa5

[   22.655059] device: 'vcs6': device_add

[   22.658660] PM: Adding info for No Bus:vcs6

[   22.658782] device: 'vcsa6': device_add

[   22.658935] PM: Adding info for No Bus:vcsa6

[   23.272979] bus: 'sdio': add driver wl1271_sdio

[   23.273040] bus: 'sdio': driver_probe_device: matched device mmc1:0001:1 with driver wl1271_sdio

[   23.273071] bus: 'sdio': really_probe: probing driver wl1271_sdio with device mmc1:0001:1

[   23.411376] wl1271_sdio: probe of mmc1:0001:1 rejects match -19

[   23.411437] bus: 'sdio': driver_probe_device: matched device mmc1:0001:2 with driver wl1271_sdio

[   23.411468] bus: 'sdio': really_probe: probing driver wl1271_sdio with device mmc1:0001:2

[   23.423614] Registering platform device 'wl1271'. Parent at platform

[   23.423645] device: 'wl1271': device_add

[   23.423675] bus: 'platform': add device wl1271

[   23.423797] PM: Adding info for platform:wl1271

[   23.424835] wl1271_sdio mmc1:0001:2: firmware: requesting ti-connectivity/wl1271-nvs.bin

[   23.424865] device: 'mmc1:0001:2': device_add

[   23.425018] PM: Adding info for No Bus:mmc1:0001:2

[   23.527252] device: 'mmc1:0001:2': device_unregister

[   23.527252] PM: Removing info for No Bus:mmc1:0001:2

[   23.527801] device: 'phy0': device_add

[   23.528198] PM: Adding info for No Bus:phy0

[   23.529266] device: 'wlan0': device_add

[   23.530029] PM: Adding info for No Bus:wlan0

[   23.534576] wl1271: loaded

[   23.534576] driver: 'mmc1:0001:2': driver_bound: bound to device 'wl1271_sdio'

[   23.534606] bus: 'sdio': really_probe: bound device mmc1:0001:2 to driver wl1271_sdio

[   23.908355] init: udev-fallback-graphics main process (3485) terminated with status 1

[   24.174133] wl1271_sdio mmc1:0001:2: firmware: requesting ti-connectivity/wl127x-fw-3.bin

[   24.174163] device: 'mmc1:0001:2': device_add

[   24.174530] PM: Adding info for No Bus:mmc1:0001:2

[   24.236267] device: 'mmc1:0001:2': device_unregister

[   24.236297] PM: Removing info for No Bus:mmc1:0001:2

[   24.630584] wl1271: firmware booted (Rev 6.3.0.0.77)

[  144.371612] init: alsa-restore main process (3613) terminated with status 19

[  144.858551] init: plymouth-upstart-bridge main process (3509) killed by TERM signal

[  144.872467] init: lightdm main process (3639) terminated with status 1

[  145.428863] init: plymouth-stop pre-start process (3841) terminated with status 1

[  275.520446] bus: 'platform': remove driver btwilink

[  275.520538] driver: 'btwilink': driver_release

[  301.856811] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0

[  301.856842] bus: 'platform': add driver btwilink

[  381.320312] bus: 'platform': remove driver btwilink

[  381.320404] driver: 'btwilink': driver_release

[  416.043853] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0

[  416.043914] bus: 'platform': add driver btwilink

[  564.258239] bus: 'platform': remove driver btwilink

[  564.258331] driver: 'btwilink': driver_release

[  566.044036] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0

[  566.044067] bus: 'platform': add driver btwilink

[Pavan Savoy]

Well then you should now be able to see the hciX interface atleast.
As in hciconfig -a should throw up hci0 DOWN.

Try and do a hciconfig hci0 up. You might need this binary running too.
Run it in back-ground (uim-sysfs) & then try hciconfig hci0 up.

--
--Pavan Savoy

[John Tobias]

Still no success.

hciconfig hci0 up

Can't get device info: No such device

I compared my kernel messages against to the working version and I've noticed that on the working version has the following:

[   10.850372] hdev ef09c000

[   10.854919] HCI device registered (hdev ef09c000)

[   10.857116] hci0 ef09c000

[   10.857116] (stc): st_register(4) 

[   10.857116] (stc):  chnl_id list empty :4 

[   10.857147] (stk) : st_kim_start

[   10.959899] (stk) :ldisc_install = 1

[   11.012634] (stc): st_tty_open 

[   11.012664] (stk) : line discipline installed 

[   11.013183] (stk) :ti-connectivity/TIInit_7.6.15.bts

Any idea?.

Also, can you tell me what version of the kernel are you using and can you share to me the .config file?.

Thanks,

john

[Erik Andresen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Do you have uim running?
See
http://omappedia.org/wiki/Device_Driver_Interface_of_WiLink_Solution#User_Space_components

greetings,
Erik

On 11.08.2012 01:05, John Tobias wrote:
> Hi Pavan,
>
> I have a follow up question, I got the latest kernel being used by
> ubuntu (3.2.24), I did cross compile, the wifi is working but when
> I do the hcitool dev, it did not detect the hcixx. I am just
> wondering if there's a step to follow to detect the hcix. I loaded
> the bluetooth driver, hci_uart.
>
>
> Regards,
>
> John

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAlwDIACgkQ8NqlQQxmej5f1ACfS7jTNTiK09eaE0GMglKM8Hhb
HToAnjMDGt8a8PuDKDmf/cfaRwXOcvNf
=r1p9
-----END PGP SIGNATURE-----

[John Tobias]

Hi Erik,

After using the latest kernel from http://git.kernel.org/?p=linux/kernel/git/luca/wl12xx.git;a=summary, I was able to find the hci0 interface.

Regards,

john

[John Tobias]

Hi,

I got a working kernel where the Bluetooth is detected correctly. I have a bluegia BLDE112, where it broadcast an advertisement (I was able to scan it using my iPhone). I was assuming that I can scan the said service in linux after executing the commands you sent to me (below), but I did not get any result.

hcitool cmd 0x3f 0x015B 0x1 0x0

hcitool cmd 0x3f 0x01DD 0x1

hciconfig hci0 lestates

hcitool cmd 0x3f 0x015B 0x1 0x0

hciconfig hci0 lestates

The follow questions after executing the said commands above:

1. What command should I use to scan the le devices?

2. What command should I use to advertise, create connection to le device?.

Regards,

John

[Pavan Savoy]

On Sun, Aug 12, 2012 at 12:27 PM, John Tobias <john.to...@gmail.com> wrote:
> Hi,
>
> I got a working kernel where the Bluetooth is detected correctly. I have a
> bluegia BLDE112, where it broadcast an advertisement (I was able to scan it
> using my iPhone). I was assuming that I can scan the said service in linux
> after executing the commands you sent to me (below), but I did not get any
> result.
>
> hcitool cmd 0x3f 0x015B 0x1 0x0
> hcitool cmd 0x3f 0x01DD 0x1
> hciconfig hci0 lestates
> hcitool cmd 0x3f 0x015B 0x1 0x0
> hciconfig hci0 lestates
>
> The follow questions after executing the said commands above:

hciconfig hci0 lestates -> returning a few states as TRUE suggests LE
can be enabled on the device.

> 1. What command should I use to scan the le devices?

hcitool lescan - scans for devices that are advertising.

> 2. What command should I use to advertise, create connection to le device?.

hciconfig hci0 leadv -> Is to enable advertisement, that can be
scanned by other devices.

hcidump -X in both the above cases will show you what is being
advertised by remote device and what you would advertise too.

--
--Pavan Savoy

[John Tobias]

Hi Pavan,

I executed the 'hciconfig hci0 leadv' and the hcidump was running in the background. Then, found out the "Error: Command Disallowed".

Any idea how to fix it?.

< HCI Command: LE Set Advertise Enable (0x08|0x000a) plen 1

  0000: 01                                                .

LE set advertise enable on hci0 returned status 12

> HCI Event: Command Complete (0x0e) plen 4

    LE Set Advertise Enable (0x08|0x000a) ncmd 1

    status 0x0c

    Error: Command Disallowed

Regards,

John

[Pavan Savoy]

On Mon, Aug 13, 2012 at 12:56 PM, John Tobias <john.to...@gmail.com> wrote:
> Hi Pavan,
>

> I executed the 'hciconfig hci0 leadv' and the hcidump was running in the
> background. Then, found out the "Error: Command Disallowed".
> Any idea how to fix it?.

Did you make sure you ran the VS commands that I sent out earlier ?
You'd want to run it everytime hci0 is reset.
i.e make sure hciconfig hci0 lestates - says few states to be TRUE
before running any of these LE commands.

--
--Pavan Savoy

[John Tobias]

Hi Pavan,

I think I am getting closer for my first goal which is to make an advertisement on my first Pandaboard ES and to scan it to my 2nd pandaboard ES.

On my first board, here's what I did:

1. Executed the commands you sent me

2. hciconfig hci0 leadv

and I got the following messages, it seems OK:

< HCI Command: LE Set Advertise Enable (0x08|0x000a) plen 1

  0000: 01                                                .

> HCI Event: Command Complete (0x0e) plen 4

    LE Set Advertise Enable (0x08|0x000a) ncmd 1

    status 0x00

On my 2nd board:

1. Executed the same commands you sent me

2. hcitool -i hci0 lescan

and I got the following messages:

< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7

    type 0x01 (active)

    interval 10.000ms window 10.000ms

    own address: 0x00 (Public) policy: All

> HCI Event: Command Complete (0x0e) plen 4

    LE Set Scan Parameters (0x08|0x000b) ncmd 1

    status 0x00

< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 2

    value 0x01 (scanning enabled)

    filter duplicates 0x01 (enabled)

> HCI Event: Command Complete (0x0e) plen 4

    LE Set Scan Enable (0x08|0x000c) ncmd 1

    status 0x00

LE Scan ...

The only problem right now, after executing the 'hcitool -i hci0 lescan', the said command did not return any output and it looks it keep scanning.

My follow up question is, am I missing something?.

Regards,

John

[Pavan Savoy]

On Mon, Aug 13, 2012 at 2:20 PM, John Tobias <john.to...@gmail.com> wrote:
> Hi Pavan,
>

No, Things seem to be in place. Can you make sure the device is like
basic discover-able and all ?
To sort of eliminate the antenna/range issues ?

hciconfig hci0 leadv - is supposed to enable ...

3] : <Rx> - 04:34:57.903
-Type : 0x04 (Event)
-EventCode : 0xFF (HCI_LE_ExtEvent)
-Data Length : 0x0C (12) bytes(s)
Event : 0x0601
Status : 0x00 (Success)
NumDevs : 0x01 (1)
Device #0
EventType : 0x00 (Connectable Undirected Advertisement)
AddrType : 0x00 (Public)
Addr : 50:56:63:CA:2C:4E
Dump(Rx):
04 FF 0C 01 06 00 01 00 00 4E 2C CA 63 56 50

connectable un-directed advertisement of the bd-address.

--
--Pavan Savoy

[John Tobias]

I'm not sure how to do it, may be you can tell me the command should I execute?

 

hciconfig hci0 leadv - is supposed to enable ...

What command did you execute to get the output below? 

[Pavan Savoy]

I had a BLE development kit at hand, quite a good development tool if
you are working on BLE,
http://www.ti.com/tool/cc2540dk-mini

However, you should be able to see most of it - via hcidump -X too, right away
- until you order and get this one :)

--
--Pavan Savoy

[John Tobias]

Is this dev kit and the usb dongle working perfectly in linux?.

May I know what Linux distro, kernel version and the bts file you are using?.

Thanks,

John

[Pavan Savoy]

On Mon, Aug 13, 2012 at 5:59 PM, John Tobias <john.to...@gmail.com> wrote:
> Is this dev kit and the usb dongle working perfectly in linux?.
> May I know what Linux distro, kernel version and the bts file you are
> using?.

oh, good that you asked, I'll ask around.
As of now, there are only windows tools available for the dongle, the
keyfob however is a nice little device by itself, where plenty of
example GATT services are flashed
- But after you mentioned this - I plugged in the device to linux PC,
since it does enumerate as a tty device under windows too. It is
asking for a ...
sudo hciattach /dev/ttyACM0 texas 57600
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_0.2.16.bts

So, I can try and get hold of this & let you know...

--
--Pavan Savoy

[John Tobias]

thanks for your help. BLE is one of my priority :)

Regards,

john

[John Tobias]

btw, do you know other usb bluetooth le where it works in linux?. I really need a working device for my development and I'm stuck at this time.

thanks,

john

[John Tobias]

Hi Pavan,

I would like to know if your usb dongle works in linux (advertise, scan, etc). Am I going to buy the devkit now or not yet? :)

Regards,

John

On Mon, Aug 13, 2012 at 4:17 PM, Pavan Savoy <pavan...@gmail.com> wrote:

On Mon, Aug 13, 2012 at 5:59 PM, John Tobias <john.to...@gmail.com> wrote:
> Is this dev kit and the usb dongle working perfectly in linux?.
> May I know what Linux distro, kernel version and the bts file you are
> using?.

oh, good that you asked, I'll ask around.
As of now, there are only windows tools available for the dongle, the
keyfob however is a nice little device by itself, where plenty of
example GATT services are flashed
- But after you mentioned this - I plugged in the device to linux PC,
since it does enumerate as a tty device under windows too. It is
asking for a ...
sudo hciattach /dev/ttyACM0 texas 57600
Found a Texas Instruments' chip!
Firmware file : /lib/firmware/TIInit_0.2.16.bts

So, I can try and get hold of this & let you know...

Hi Pavan

[Pavan Savoy]

On Tue, Aug 14, 2012 at 11:27 AM, John Tobias <john.to...@gmail.com> wrote:
> Hi Pavan,
>
> I would like to know if your usb dongle works in linux (advertise, scan,
> etc). Am I going to buy the devkit now or not yet? :)

John,
I've asked the same on the e2e forums from TI - where the device is
sold and supported.
But from personal experience of using it on windows, quite satisfied
with it to test GATT stuff.

Provided you have an IAR - It is also very good for development.
There is support for linux - however it is with blestack from the
manufacturer and not bluez - So hopefully we do have a way .. but not
sure as of yet.

--
--Pavan Savoy

[John Tobias]

Pavan,

When you connect your usb dongle, (sudo hciattach /dev/ttyACM0 texas 57600)

are you able to advertise and scan using the dongle?.

john

[John Tobias]

Hi Pavan,

I got the TI BLE Vendor Specific HCI Guide. I used "hcitool cmd 0x8 0xc 0x200c" to enable the LE scan and found out the command is returning error.

< HCI Command: ogf 0x08, ocf 0x000c, plen 1

  0C 

< HCI Command: LE Set Scan Enable (0x08|0x000c) plen 1

    value 0x0c (scanning enabled)

    filter duplicates 0x20 (enabled)

> HCI Event: Command Complete (0x0e) plen 4

    LE Set Scan Enable (0x08|0x000c) ncmd 1

    status 0x11

    Error: Unsupported Feature or Parameter Value

> HCI Event: 0x0e plen 4

  01 0C 20 11 

Regards,

John

[John Tobias]

Same with the le advertise enable:

hcitool cmd 0x8 0xa 0x200a

< HCI Command: ogf 0x08, ocf 0x000a, plen 1

  0A 

< HCI Command: LE Set Advertise Enable (0x08|0x000a) plen 1

  0000: 0a                                                .

> HCI Event: Command Complete (0x0e) plen 4

    LE Set Advertise Enable (0x08|0x000a) ncmd 1

    status 0x11

    Error: Unsupported Feature or Parameter Value

> HCI Event: 0x0e plen 4

  01 0A 20 11

[Pavan Savoy]

Vendor specific commands have ogf of 0x3f. Can you point which document you are referring to?

Droid sent - Ignore typos

...

[John Tobias]

TI BLE Vendor Specific HCI Reference Guide Version 1.2.1

Page 13 of 143

[Pavan Savoy]

On Wed, Aug 15, 2012 at 7:09 PM, John Tobias <john.to...@gmail.com> wrote:
> TI BLE Vendor Specific HCI Reference Guide Version 1.2.1
> Page 13 of 143

John,

Please do not confuse the CC254 with WL127x on Pandaboard.
The BT chip on panda board is a dual mode WL127xL which supports BLE.

CC2540 is a LE stand-alone chip set which is available for purchase as
a catalog product by TI.
The document you are referring to is w.r.t CC2540.

--
--Pavan Savoy

[John Tobias]

Ohh ok.. May I know where I can download the HCI Reference Guide for WL127x?.

Thanks,

john

[John Tobias]

I ended up buying a usb bluetooth le dongle to use for development and
I'll wait from TI to fully support the WL127x functionality.

john

On Tue, Aug 28, 2012 at 2:20 PM, <freto...@gmail.com> wrote:
> I'm in the same boat, I followed all the steps and I was able to execute
> hcitool lecc, however when I tried to establish a connection I got the
> following error
>
>>> hcitool lecc
>>> Could not create connection: I/O error
>
> Looking at the hcidump :
>
> HCI Event: Command Status (0x0f) plen 4
> LE Create Connection (0x08|0x000d) status 0x0c ncmd 1
> Error: Command Disallowed
>
> Can anyone provide a way to enable these commands? or at least the
> documentation to the vendor specific command for the WL127x.?

[John Tobias]

Still no update. I am hoping TI will provide some support anytime
soon. But, we don't know when it's gonna happen...

On Thu, Sep 27, 2012 at 3:59 PM, Kyle Manna <2bl...@gmail.com> wrote:
> Hey all, any updates or success with this? I'm now in the same boat as a
> few others.
>
> I posted @ http://e2e.ti.com/support/low_power_rf/f/307/t/217059.aspx hoping
> to get some visibility from TI.
>
> - Kyle

[Pavan Savoy]

On Thu, Sep 27, 2012 at 5:59 PM, Kyle Manna <2bl...@gmail.com> wrote:
> Hey all, any updates or success with this? I'm now in the same boat as a
> few others.
>
> I posted @ http://e2e.ti.com/support/low_power_rf/f/307/t/217059.aspx hoping
> to get some visibility from TI.

Kyle, There is certainly visibility from TI. We also want our fellow
developers to have BLE on pandaboards.
Just clearing through few legalities of releasing firmware.

Xavier, Nipuna, Can we host the firmware on panda-board wiki somewhere ?
There need not be a PPA release specifically for this I suppose?

> - Kyle
>
> On Wednesday, August 29, 2012 4:34:26 PM UTC-5, John Tobias wrote:
>>

>> I ended up buying a usb bluetooth le dongle to use for development and
>> I'll wait from TI to fully support the WL127x functionality.
>>
>> john

--
--Pavan Savoy

[John Tobias]

Hi Pavan,

Good to hear that... Please inform me once the firmware is available
to public...
Do you know the estimated date for the release (weeks/months)?

Regards,

john

[Pavan Savoy]

People who were waiting on panda-board having LE enabled firmware -
Can now pick fw up from
http://processors.wiki.ti.com/index.php/BTS_with_BTLE_enabled_for_WL1271L

ENJOY !!!

Disclaimer :
This fw is NOT for panda-board as such - Ideally you should still have
whatever comes from PPA updates.
But the module for which the fw is published and the one on
panda-board are the same.

--
--Pavan Savoy

[Nipuna Gunasekera]

Thanks Pavan!!