Bluetooth not coming up

[Shantanu]

My OS came up. But bluetooth is not working. I tried to print some
values where i suspected it should be failing and I got the logs as:


[ 3719.078247] (stk) : timed out waiting for ldisc to be un-installed
[ 3719.085174] Bluetooth: st_register() STATUS: -22
[ 3719.090606] Bluetooth: regcb=0,stgdata=0,newprotot=0,newprotorecv=0
[ 3719.097564] Bluetooth: st_register failed -22
[ 3719.202911] (stc): st_register(2)
[ 3719.206542] (stc): chnl_id list empty :2

Atleast one of the values in regcb, stgdata, newproto, newprotorecv
should be not null for BT to work.
I checked I have uim-sysfs installed and running.

Please help me fix this!!

[Pavan Savoy]

On Tue, Feb 21, 2012 at 12:43 AM, Shantanu <unrea...@gmail.com> wrote:
> My OS came up. But bluetooth is not working. I tried to print some
> values where i suspected it should be failing and I got the logs as:
>
>
> [ 3719.078247] (stk) : timed out waiting for ldisc to be un-installed
> [ 3719.085174] Bluetooth: st_register() STATUS: -22
> [ 3719.090606] Bluetooth: regcb=0,stgdata=0,newprotot=0,newprotorecv=0

Do you happen to have the right version of btwilink driver ?
As in no mix and match - correct ? You use the same btwilink driver
which comes along with the kernel which also has ti-st drivers ?

btwilink is at drivers/bluetooth & ti-st is at drivers/misc/ti-st/

Apart from this the only reason why BT cannot be on is because of uim
- which you say is running.

> [ 3719.097564] Bluetooth: st_register failed -22
> [ 3719.202911] (stc): st_register(2)
> [ 3719.206542] (stc):  chnl_id list empty :2
>
> Atleast one of the values in regcb, stgdata, newproto, newprotorecv
> should be not null for BT to work.
> I checked I have uim-sysfs installed and running.
>
> Please help me fix this!!

--
--Pavan Savoy

[Mircea Gherzan]

Hi,

I've got the same issue: I can't use Bluetooth on a vanilla 3.3-rc3+
kernel.

Here's the relevant part of the kernel log:

[ 9.009338] (stk) :sysfs entries created
[ 9.014007] (stk) : debugfs entries created
[ 9.052581] Bluetooth: Core ver 2.16
[ 9.057189] NET: Registered protocol family 31
[ 9.061981] Bluetooth: HCI device and connection manager initialized
[ 9.068786] Bluetooth: HCI socket layer initialized
[ 9.074676] Bluetooth: L2CAP socket layer initialized
[ 9.080261] Bluetooth: SCO socket layer initialized
[ 9.092254] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
[ 17.311157] Bluetooth: RFCOMM TTY layer initialized
[ 17.316741] Bluetooth: RFCOMM socket layer initialized
[ 17.322479] Bluetooth: RFCOMM ver 1.11
[ 17.330688] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.336517] Bluetooth: BNEP filters: protocol multicast

Am 22.02.2012 17:33, schrieb Pavan Savoy:
> Do you happen to have the right version of btwilink driver ?
> As in no mix and match - correct ? You use the same btwilink driver
> which comes along with the kernel which also has ti-st drivers ?

Yes, they are both in the vanilla kernel.

> btwilink is at drivers/bluetooth & ti-st is at drivers/misc/ti-st/
>
> Apart from this the only reason why BT cannot be on is because of uim
> - which you say is running.

The uim daemon is running. The firmware blob I'm using is the
TIInit_7.2.31.bts

I managed to get it runnig using the tilt-tracking brach of the TI
Landing Team kernel (Linaro) [1].

Any ideas?

Thanks,
Mircea

[1] git://git.linaro.org/landing-teams/working/ti/kernel.git

[Pavan Savoy]

well, are you sure the right uim is running ? as in the same ran with
TI baseline too ?
It is called uim-sysfs I presume.

Also, can you make sure the btwilink platform device exists too ?
In /sys/devices/platform/btwilink ?

>
> I managed to get it runnig using the tilt-tracking brach of the TI
> Landing Team kernel (Linaro) [1].
>
> Any ideas?
>
> Thanks,
> Mircea
>
> [1] git://git.linaro.org/landing-teams/working/ti/kernel.git

--
--Pavan Savoy

[Mircea Gherzan]

Am 22.02.2012 21:04, schrieb Pavan Savoy:
> well, are you sure the right uim is running ? as in the same ran with
> TI baseline too ?
> It is called uim-sysfs I presume.

The uim that I am running is from this tree:

git://gitorious.org/uim/uim.git

Should I use another repo?

> Also, can you make sure the btwilink platform device exists too ?
> In /sys/devices/platform/btwilink ?

You are right: the sysfs entry was missing because the board init
function does not register the btwilink platform device. I patched the
board file (arch/arm/mach-omap2/board-omap4panda.c) and now I get:

[ 8.863464] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
[ 8.870269] hdev eeb0c000
[ 8.872680] HCI device registered (hdev eeb0c000)
[ 8.873596] hci0 eeb0c000
[ 8.873596] (stc): st_register(4)
[ 8.877471] (stc): chnl_id list empty :4
[ 8.881988] (stk) : st_kim_start
[ 8.992736] (stk) :ldisc_install = 1
[ 10.001922] (stk) :ldisc installation timeout
[ 10.006652] (stk) :ldisc_install = 0
[ 11.010162] (stk) : timed out waiting for ldisc to be un-installed
[ 11.122619] (stk) :ldisc_install = 1
[ 12.119567] (stk) :ldisc installation timeout
[ 12.119567] (stk) :ldisc_install = 0
[ 13.119323] (stk) : timed out waiting for ldisc to be un-installed
[ 13.228607] (stk) :ldisc_install = 1
[ 14.220855] (stk) :ldisc installation timeout
[ 14.225402] (stk) :ldisc_install = 0
[ 14.600067] usb 1-1.1: link qh8-0001/ef247d80 start 2 [1/0 us]
[ 15.231140] (stk) : timed out waiting for ldisc to be un-installed
[ 15.344940] (stk) :ldisc_install = 1
[ 16.345855] (stk) :ldisc installation timeout
[ 16.350158] (stk) :ldisc_install = 0
[ 17.205230] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 17.211608] Bluetooth: BNEP filters: protocol multicast
[ 17.211639] Bluetooth: RFCOMM TTY layer initialized
[ 17.211822] Bluetooth: RFCOMM socket layer initialized
[ 17.211822] Bluetooth: RFCOMM ver 1.11
[ 17.353759] (stk) : timed out waiting for ldisc to be un-installed
[ 17.463897] (stk) :ldisc_install = 1
[ 17.739288] NET: Registered protocol family 10
[ 18.463195] (stk) :ldisc installation timeout
[ 18.463195] (stk) :ldisc_install = 0
[ 19.470977] (stk) : timed out waiting for ldisc to be un-installed
[ 19.587982] (stk) :ldisc_install = 1
[ 20.588165] (stk) :ldisc installation timeout
[ 20.588165] (stk) :ldisc_install = 0
[ 21.596038] (stk) : timed out waiting for ldisc to be un-installed
[ 21.596038] Bluetooth: st_register failed -22

Running uim in the foreground I can see that it is blocking in the
poll(2) system call.

Any clues?

Thanks,
Mircea

[Pavan Savoy]

Well there is this problem of UIM not being hosted on 1 place properly
- Have a look at
http://git.omapzoom.org/?p=platform/hardware/ti/wpan.git;a=tree;f=ti_st/uim-sysfs;h=7ad987c750d2bd4f1a258ccba09d4d5cd74e9ad4;hb=refs/heads/ics-mr1

and make sure you have the same code.
On git.omapzoom.org -> project hardware/ti/wpan.git -> any branch GB
or ICS or ICS-release -> then navigate to ti_st/uim/

>
> Any clues?
>
> Thanks,
> Mircea

--
--Pavan Savoy

[Mircea Gherzan]

Am 22.02.2012 22:20, schrieb Pavan Savoy:
> Well there is this problem of UIM not being hosted on 1 place
> properly - Have a look at
> http://git.omapzoom.org/?p=platform/hardware/ti/wpan.git;a=tree;f=ti_st/uim-sysfs;h=7ad987c750d2bd4f1a258ccba09d4d5cd74e9ad4;hb=refs/heads/ics-mr1
>
> and make sure you have the same code. On git.omapzoom.org -> project
> hardware/ti/wpan.git -> any branch GB or ICS or ICS-release -> then
> navigate to ti_st/uim/

First, the code from this repo (master branch) does not compile on a
non-Android Linux. It requires the following patch:

diff --git a/ti_st/uim-sysfs/uim.h b/ti_st/uim-sysfs/uim.h
index b7d981d..bfd6759 100644
--- a/ti_st/uim-sysfs/uim.h
+++ b/ti_st/uim-sysfs/uim.h
@@ -67,6 +67,11 @@
#define UIM_DBG(fmt, arg...)
#define UIM_VER(fmt, arg...)
#endif
+#else /* normal Linux */
+#define UIM_START_FUNC() printf("uim: Inside %s", __FUNCTION__)
+#define UIM_ERR(fmt, arg...) printf("uim:"fmt"\n" , ## arg)
+#define UIM_DBG(fmt, arg...) printf("uim:"fmt"\n" , ## arg)
+#define UIM_VER(fmt, arg...) printf("uim:"fmt"\n" , ## arg)
#endif /* ANDROID */

/*Termios2 structure for setting the Custom baud rate*/

Second, even with the above patch, Bluetooth still does not work.
Running the ti_st/uim-sysfs/uim daemon in the foreground does not
produce any output.

Any clues?

Thanks,
Mircea

PS: The fix for the btwilink platform device issue will is on its way to
mainline: http://www.spinics.net/lists/arm-kernel/msg161204.html

[Pavan Savoy]

On Thu, Feb 23, 2012 at 3:02 PM, Mircea Gherzan <mghe...@gmail.com> wrote:
> Am 22.02.2012 22:20, schrieb Pavan Savoy:
>> Well there is this problem of UIM not being hosted on 1 place
>> properly - Have a look at
>> http://git.omapzoom.org/?p=platform/hardware/ti/wpan.git;a=tree;f=ti_st/uim-sysfs;h=7ad987c750d2bd4f1a258ccba09d4d5cd74e9ad4;hb=refs/heads/ics-mr1
>>
>>  and make sure you have the same code. On git.omapzoom.org -> project
>> hardware/ti/wpan.git -> any branch GB or ICS or ICS-release -> then
>> navigate to ti_st/uim/
>
> First, the code from this repo (master branch) does not compile on a
> non-Android Linux. It requires the following patch:
>
> diff --git a/ti_st/uim-sysfs/uim.h b/ti_st/uim-sysfs/uim.h
> index b7d981d..bfd6759 100644
> --- a/ti_st/uim-sysfs/uim.h
> +++ b/ti_st/uim-sysfs/uim.h
> @@ -67,6 +67,11 @@
>  #define UIM_DBG(fmt, arg...)
>  #define UIM_VER(fmt, arg...)
>  #endif
> +#else /* normal Linux */
> +#define UIM_START_FUNC()      printf("uim: Inside %s", __FUNCTION__)
> +#define UIM_ERR(fmt, arg...)  printf("uim:"fmt"\n" , ## arg)
> +#define UIM_DBG(fmt, arg...)  printf("uim:"fmt"\n" , ## arg)
> +#define UIM_VER(fmt, arg...)  printf("uim:"fmt"\n" , ## arg)
>  #endif  /* ANDROID */

Yes, a similar patch is on its way to git.omapzoom.org as well - along
with other small clean-ups.
However, any logs ? anything at all ? when you do hciconfig hci0 reset
? (up?) on UIM ?

Do you see the poll break -et all ? @ RE_POLL: label under err =
poll(&p, 1, -1); ??
polling on sysfs entries is never a cake-walk - it is as messy as it
can get ....

In any case check if this happens, You can also check the driver is
all good - by verifying the file
cat /sys/devices/platform/kim/install - It should say "1" when you're
at hciconfig hci0 up and "0" when at down.

>  /*Termios2 structure for setting the Custom baud rate*/
>
> Second, even with the above patch, Bluetooth still does not work.
> Running the ti_st/uim-sysfs/uim daemon in the foreground does not
> produce any output.
>
> Any clues?
>
> Thanks,
> Mircea
>
> PS: The fix for the btwilink platform device issue will is on its way to
> mainline: http://www.spinics.net/lists/arm-kernel/msg161204.html

--
--Pavan Savoy

[Mircea Gherzan]

Hi,

It seems that this is the line that fails:

dev_fd = open((const char*) uart_dev_name, O_RDWR);

This is because the /sys/devices/platform/kim/dev_name entry is a quite
unusual "string":

mircea@panda:~$ cat /sys/devices/platform/kim/dev_name > devname.txt
mircea@panda:~$ hexdump -C devname.txt
00000000 ff ff ff ff ff ff ff ff 0a |.........|
00000009

Here's the uim log for "hciconfig hci0 up" (which of course fails):

uim: Inside main
uim: Inside st_uart_config
uim: install set to 1
uim: opening ��������, while already open
uim: cleanup
uim: Can't open ��������
uim: Inside st_uart_config
uim: Un-Installed N_TI_WL Line displine
uim: Inside st_uart_config
uim: install set to 1
uim: Can't open ��������
uim: Inside st_uart_config
uim: Un-Installed N_TI_WL Line displine
uim: Inside st_uart_config
uim: install set to 1
uim: Can't open

[Pavan Savoy]

The string is supposed to say "/dev/ttyO1" - This is populated in
arch/arm/mach-omap2/board-panda
where the btwilink and the wl127x_device platform devices are added.

Can you check that file ? in kernel ?

>
> Here's the uim log for "hciconfig hci0 up" (which of course fails):
>
> uim: Inside main
> uim: Inside st_uart_config
> uim: install set to 1
> uim: opening ��������, while already open
> uim: cleanup
> uim:  Can't open ��������
> uim: Inside st_uart_config
> uim:  Un-Installed N_TI_WL Line displine
> uim: Inside st_uart_config
> uim: install set to 1
> uim:  Can't open ��������
> uim: Inside st_uart_config
> uim:  Un-Installed N_TI_WL Line displine
> uim: Inside st_uart_config
> uim: install set to 1
> uim:  Can't open

--
--Pavan Savoy

[Mircea Gherzan]

I took a look at it and I came to the conclusion that TI people don't
give a damn about the mainline kernel: from the platform_device
perspective, mainline is way behind compared to the Linaro kernels.

I patched the board-omap4panda.c file to get the right content into the
sysfs files and now I get in uim:

uim: Inside main
uim: Inside st_uart_config
uim: install set to 1

uim: opening /dev/ttyO1, while already open
uim: cleanup
uim: Inside set_baud_rate
uim: set_baud_rate() done
uim: Setting speed to 3000000
uim: Inside read_command_complete
uim: Command complete started
uim: Inside read_hci_event
uim: read_hci_event
uim: Invalid response
uim: cleanup

uim: Inside st_uart_config
uim: Un-Installed N_TI_WL Line displine
uim: Inside st_uart_config
uim: install set to 1

uim: Inside set_baud_rate
uim: set_baud_rate() done
uim: Setting speed to 3000000
uim: Inside read_command_complete
uim: Command complete started
uim: Inside read_hci_event
uim: read_hci_event
uim: Invalid response
uim: cleanup

uim: Inside st_uart_config
uim: Un-Installed N_TI_WL Line displine

What should I check next?

Thanks,
Mircea

[Pavan Savoy]

Mircea,
Please be patient, It always takes time for the vanilla kernel to have
patches for all features of panda
consistently in it, the modifications keeps flowing in and out of it.

> I patched the board-omap4panda.c file to get the right content into the
> sysfs files and now I get in uim:
>

good UIM seems to be running alright.

Ok, The invalid response is slightly concerning here, Let's re-visit
the kernel's platform device structure to make
sure the GPIO line mentioned is correct.
To actually know what all these mean, You can refer to wiki
http://omappedia.org/wiki/Device_Driver_Interface_of_WiLink_Solution

> What should I check next?
>
> Thanks,
> Mircea

--
--Pavan Savoy

[Mircea Gherzan]

Am 25.02.2012 04:09, schrieb Pavan Savoy:
> Ok, The invalid response is slightly concerning here, Let's re-visit
> the kernel's platform device structure to make
> sure the GPIO line mentioned is correct.
> To actually know what all these mean, You can refer to wiki
> http://omappedia.org/wiki/Device_Driver_Interface_of_WiLink_Solution

Here are the relevant plaform devices in my current board file:

static struct ti_st_plat_data wilink_platform_data = {
.nshutdown_gpio = 46,
.dev_name = "/dev/ttyO1",
.flow_cntrl = 1,
.baud_rate = 3000000,
.chip_enable = NULL,
.suspend = NULL,
.resume = NULL,
};

static struct platform_device wl1271_device = {
.name = "kim",
.id = -1,
.dev = {
.platform_data = &wilink_platform_data,
},
};

static struct platform_device btwilink_device = {
.name = "btwilink",
.id = -1,
};

static struct platform_device *panda_devices[] __initdata = {
&leds_gpio,
&wl1271_device,
&btwilink_device,
};

[Mircea Gherzan]

Am 25.02.2012 04:09, schrieb Pavan Savoy:

> Ok, The invalid response is slightly concerning here, Let's re-visit
> the kernel's platform device structure to make
> sure the GPIO line mentioned is correct.
> To actually know what all these mean, You can refer to wiki
> http://omappedia.org/wiki/Device_Driver_Interface_of_WiLink_Solution

It seems that the read() from the UART char device is returning EAGAIN:

uim: st_uart_config(): install set to 1
uim: st_uart_config(): opening /dev/ttyO1, while already open
uim: cleanup(): cleanup
uim: set_baud_rate(): set_baud_rate() done
uim: st_uart_config(): Setting speed to 3000000
uim: read_command_complete(): Command complete started
uim: read_hci_event(): read_hci_event
uim: read_hci_event() reading 1st byte: Resource temporarily unavailable
uim: read_hci_event() reading 1st byte: Resource temporarily unavailable
uim: read_hci_event() reading 1st byte: Resource temporarily unavailable
uim: read_hci_event() reading 1st byte: Resource temporarily unavailable
uim: read_command_complete(): Error reading the response: Resource
temporarily unavailable

Mircea

[Pavan Savoy]

Well this is really strange, from ST perspective you pretty much all
what is required to get the BT up and running.
The only other thing I can think of now is to actually probe the chip
to figure out,

1. The nSHUTDOWN (BT_EN) line is being toggled high & low - when you
try and do hciconfig hci0 up/down/reset - This can be a problem if
there is something wrong with gpiolib usage with vanilla kernel
itself.

2. probe the 32khz slow-clock for the chip - to figure out if the UART
would be functional upon enabling the BT_EN.

I Understand that the module is small & probing would be kind of hard,
but I don't see no other options.

>
> Mircea

--
--Pavan Savoy

[Mircea Gherzan]

It seems that one patch [3] was missing to get Bluetooth working.

Bottom line: three patches [1][2][3] are required to functional
Bluetooth with the current mainline kernel (3.3-rc7+).

Mircea

[1] http://www.spinics.net/lists/linux-omap/msg65181.html
[2] http://www.spinics.net/lists/linux-omap/msg65993.html
[3] http://elinux.org/images/8/8d/0001a-omap4-pandaboard-wlan-fix.patch

[Pavan Savoy]

ah, ok understand - the 3rd patch basically enabled the 32k slow clock
for the wilink chip which comes in from TWL.
Makes sense.

> Bottom line: three patches [1][2][3] are required to functional
> Bluetooth with the current mainline kernel (3.3-rc7+).
>
> Mircea
>
> [1] http://www.spinics.net/lists/linux-omap/msg65181.html
> [2] http://www.spinics.net/lists/linux-omap/msg65993.html
> [3] http://elinux.org/images/8/8d/0001a-omap4-pandaboard-wlan-fix.patch

--
--Pavan Savoy

[venky6]

Hi,

I am using Ubuntu-11.10 on Panda-board ES.

inserted  CONFIG_TI_ST=y and

btwink modules.

root@panda:~# hciconfig 

hci0:   Type: BR/EDR  Bus: UART

        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0

        DOWN 

        RX bytes:0 acl:0 sco:0 events:0 errors:0

        TX bytes:0 acl:0 sco:0 commands:0 errors:0

How i need to proceed to get the bluetooth working.

root@panda:~# hciconfig hci0 up

[ 2894.677062] (stk) :line disc installation timed out 

[ 2895.822967] (stk) :line disc installation timed out 

[ 2899.898162] (stk) :line disc installation timed out 

[ 2900.996734] (stk) :line disc installation timed out 

[ 2902.098266] (stk) :line disc installation timed out 

[ 2903.188659] (stk) :line disc installation timed out 

[ 2903.188659] ti_st_open: st_register failed -22

Can't init device hci0: Input/output error (5)

I need to take care of any thing to get bluetooth work.

Thanks in Advance,

venky.

[Pavan Savoy]

This means chip isn't responding. This can mean several things including the lack of proper setup of n shut down gpio line. Or lack of slow clock. Is it a standard panda board? Modified?

Droid sent - Ignore typos

On Jan 7, 2013 8:13 AM, <prasannak...@gmail.com> wrote:

uim is polling for read_hci_event read until 0x04?
So if I keep running it at some time it gets 0X04?
That is why i get bluetooth switched on suddently?
after line discipline installation failed?

[Pavan Savoy]

could be couple of things like muxing of UART or GPIO. This can be done much earlier in kernel init.

If it is because of UIM then try and run it in the earliest possible run-level, May be run it from inittab itself, like getty, It also does what getty does so makes sense to have it there.

On Sun, Jan 27, 2013 at 11:00 PM, <prasannak...@gmail.com> wrote:

Pavan

It is the std pandaboard and tried prebuilt image and was working and when I rebooted It got me the same error and when tried back my image its again showing line disc error

and after a long time it switches on ?
could it be solved ?

Regards
prasanna

--
--Pavan Savoy

[Pavan Savoy]

If it's android and looking at your init. rc the service starts early enough. Must be something wrong with kernel then. Check if there are any conflicts in line usage or try and enable verbose logging you see if UART is losing characters...

Droid sent - Ignore typos

On Jan 27, 2013 11:57 PM, <prasannak...@gmail.com> wrote:

Pavan
Thanks for quick reply
Its working fine for a while and after some time it becomes unstable
root@android:/ # hciconfig hci0 up                                            
Can't init device hci0: I/O error (5)
import init.omap4pandaboard.usb.rc
Am on android  and here is my init script and where can I place the uim daemon?


/*****************************init script original***************************************/
on init
    # mount debugfs
    mount debugfs /sys/kernel/debug /sys/kernel/debug

# power management
# Enable off mode by default
    #write /sys/kernel/debug/pm_debug/enable_off_mode 1

# Enable Smart Reflex in debugfs
    write /sys/kernel/debug/pm_debug/smartreflex/sr_core/autocomp 1
    write /sys/kernel/debug/pm_debug/smartreflex/sr_iva/autocomp 1
    write /sys/kernel/debug/pm_debug/smartreflex/sr_mpu/autocomp 1

on boot
    setprop ro.build.product omap4sdp
    setprop ro.product.device omap4sdp
    setprop wifi.interface wlan0

    # create dhcpcd dir
    mkdir /data/misc/dhcp 0770 dhcp dhcp
    chmod 0770 /data/misc/dhcp
    chmod 0666 /dev/pvrsrvkm

    # switch CPUfreq from performance to hotplug
    #write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor hotplug
    #write /sys/devices/system/cpu/cpufreq/hotplug/down_threshold 30

    #Give system ownership and permission to boost clock for specified timeout
    #Note boost_timeout cannot be changed from application because of dynamic sysfs creation. It will have default value of 3 sec.
    chown system system /sys/devices/system/cpu/cpu0/cpufreq/boost_cpufreq
    chmod 0664  /sys/devices/system/cpu/cpu0/cpufreq/boost_cpufreq

    # Boost the CPU for 60 sec for boot optimization
    #write /sys/devices/system/cpu/cpufreq/hotplug/boost_timeout 60000000
    #write /sys/devices/system/cpu/cpu0/cpufreq/boost_cpufreq 1

    # change permissions for alsa nodes
    chmod 0777  /dev/snd/pcmC0D0c
    chmod 0777 /dev/snd/pcmC0D0p
    chmod 0777  /dev/snd/controlC0
    chmod 0777  /dev/snd/timer

    #change permissions for alsa nodes for audio modem
    chmod 0777 /dev/snd/pcmC0D5c
    chmod 0777 /dev/snd/pcmC0D5p

    #change permissions for alsa nodes for HDMI
    chmod 777  /dev/snd/pcmC0D7p

    # ADXL345 accelerometer on Chipsee Pandaboard Expansion
    chown system system /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/disable
    chown system system /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/rate
    chown system system /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/xinv
    chown system system /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/yinv
    chown system system /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/zinv
    chown system system /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/xyswap
    chmod 0777 /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/disable
    chmod 0777 /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/rate
    chmod 0777 /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/xinv
    chmod 0777 /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/yinv
    chmod 0777 /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/zinv
    chmod 0777 /sys/devices/platform/omap/omap_i2c.4/i2c-4/4-0053/xyswap

    # HMC5843 compass on Chipsee Pandaboard Expansion
    chown system system /sys/bus/i2c/drivers/hmc5843/4-001e/enable
    chown system system /sys/bus/i2c/drivers/hmc5843/4-001e/rate
    chown system system /sys/bus/i2c/drivers/hmc5843/4-001e/xoffset
    chown system system /sys/bus/i2c/drivers/hmc5843/4-001e/yoffset
    chown system system /sys/bus/i2c/drivers/hmc5843/4-001e/zoffset
    chmod 0777 /sys/bus/i2c/drivers/hmc5843/4-001e/enable
    chmod 0777 /sys/bus/i2c/drivers/hmc5843/4-001e/rate
    chmod 0777 /sys/bus/i2c/drivers/hmc5843/4-001e/xoffset
    chmod 0777 /sys/bus/i2c/drivers/hmc5843/4-001e/yoffset
    chmod 0777 /sys/bus/i2c/drivers/hmc5843/4-001e/zoffset

    # Change permissions for compass calibration
    chown system system /data/chipsee_compass/xoffset
    chown system system /data/chipsee_compass/yoffset
    chown system system /data/chipsee_compass/zoffset
    chmod 0777 /data/chipsee_compass/xoffset
    chmod 0777 /data/chipsee_compass/yoffset
    chmod 0777 /data/chipsee_compass/zoffset

    # Change permissions for touchscreen calibration
    chown system system /sys/devices/platform/omap/omap2_mcspi.1/spi1.0/calibrate
    chown system system /data/calibrate
    chmod 0777 /sys/devices/platform/omap/omap2_mcspi.1/spi1.0/calibrate
    chmod 0777 /data/calibrate

    # change permissions for Overlay
    chown system system /dev/video1
    chown system system /dev/video2
    chown system system /dev/video3
    # change permissions for overlay managers and display devices
    chown system system /sys/devices/platform/omapdss/display0/enabled
    chown system system /sys/devices/platform/omapdss/display1/enabled
    chown system system /sys/devices/platform/omapdss/display2/enabled
    chown system system /sys/devices/platform/omapdss/display3/enabled
    chown system system /sys/devices/platform/omapdss/display0/name
    chown system system /sys/devices/platform/omapdss/display1/name
    chown system system /sys/devices/platform/omapdss/display2/name
    chown system system /sys/devices/platform/omapdss/display3/name
    chown system system /sys/devices/platform/omapdss/overlay0/manager
    chown system system /sys/devices/platform/omapdss/overlay1/manager
    chown system system /sys/devices/platform/omapdss/overlay2/manager
    chown system system /sys/devices/platform/omapdss/overlay3/manager
    chown system system /sys/devices/platform/omapdss/overlay0/zorder
    chown system system /sys/devices/platform/omapdss/overlay1/zorder
    chown system system /sys/devices/platform/omapdss/overlay2/zorder
    chown system system /sys/devices/platform/omapdss/overlay3/zorder
    # change permissions for manager tranparency parameters
    chown system system /sys/devices/platform/omapdss/manager0/name
    chown system system /sys/devices/platform/omapdss/manager0/display
    chown system system /sys/devices/platform/omapdss/manager1/name
    chown system system /sys/devices/platform/omapdss/manager1/display
    chown system system /sys/devices/platform/omapdss/manager2/name
    chown system system /sys/devices/platform/omapdss/manager2/display
    chown system system /sys/devices/platform/omapdss/overlay0/enabled
    chown system system /sys/devices/platform/omapdss/overlay1/enabled
    chown system system /sys/devices/platform/omapdss/overlay2/enabled
    chown system system /sys/devices/platform/omapdss/overlay3/enabled
    # change permissions for display timings to get the resolutions
    chown system system /sys/devices/platform/omapdss/display0/timings
    chown system system /sys/devices/platform/omapdss/display1/timings
    chown system system /sys/devices/platform/omapdss/display2/timings
    chown system system /sys/devices/platform/omapdss/display3/timings
    chown system system /sys/devices/platform/omapdss/display2/code
     # change permissions for Tiler driver
    chown media media /dev/tiler
    chmod 0660 /dev/tiler
    chmod 0660 /dev/dmm

    # Revert the boost_timeout to the default value of 3 sec. Note this won't affect the prev boost
    # request for boot time reduction
    # write /sys/devices/system/cpu/cpufreq/hotplug/boost_timeout 3000000

    # Enable hotplug detection for HDMI
    # write /sys/devices/platform/omapdss/display2/hpd_enabled 1

    # wifi related configuration,set the right permissions
    mkdir /system/etc/wifi 0770 wifi wifi
    chmod 0770 /system/etc/wifi
    chmod 0660 /system/etc/wifi/wpa_supplicant.conf
    chown wifi wifi /system/etc/wifi/wpa_supplicant.conf
    mkdir /data/misc/wifi 0770 wifi wifi
    mkdir /data/misc/wifi/sockets 0770 wifi wifi
    chmod 0770 /data/misc/wifi
    chmod 0660 /data/misc/wifi/wpa_supplicant.conf
    chown wifi wifi /data/misc/wifi
    chown wifi wifi /data/misc/wifi/wpa_supplicant.conf
    # wpa_supplicant socket (unix socket mode)
    mkdir /data/system/ 0775 system system

    chown system system /sys/class/graphics/fb0/overlays
    chown system system /sys/class/graphics/fb0/fit_to_screen
    chown system system /sys/class/graphics/fb1/overlays
    chmod 0666 /dev/pvrsrvkm

    insmod /system/modules/st_drv.ko
    insmod /system/modules/bluetooth.ko
    insmod /system/modules/bnep.ko
    insmod /system/modules/hci_uart.ko
    insmod /system/modules/rfcomm.ko
    insmod /system/modules/btwilink.ko

    chown system  system /sys/class/rfkill/rfkill0/type
    chown system  system /sys/class/rfkill/rfkill0/state

    insmod /system/modules/wl1273-core.ko
    insmod /system/modules/wl12xx.ko

# Initialize the SGX driver
service pvrsrvinit /system/bin/pvrsrvinit
    class main
    user root
    oneshot

service wpa_supplicant /system/bin/wpa_supplicant -Dwext -iwlan0  -dd
    socket wpa_wlan0 dgram 660 wifi wifi
    disabled
    oneshot

service dhcpcd_wlan0 /system/bin/dhcpcd -dABKL
    group dhcp
    disabled
    oneshot

#userspace daemon needed for bluetooth
service uim /system/bin/uim
    class main
    user root
    oneshot

# run touchscreen and compass calibration script
service calibrate /system/bin/sh /init.chipsee.sh
    class main
    user root
    oneshot
/***************************************************************************************************/

Regards
prasanna

[Pavan Savoy]

# define VERBOSE as first line in file st_core.c

Droid sent - Ignore typos

On Jan 28, 2013 12:06 AM, <prasannak...@gmail.com> wrote:

It gets me
<6>[  226.270721] (stk) :ldisc_install = 0
<6>[  226.279541] (stc): st_tty_close
<7>[  246.214782] hci0 efbce800
<6>[  246.214782] (stc): st_register(4)
<6>[  246.218627] (stc):  chnl_id list empty :4
<6>[  246.223052] (stk) : st_kim_start
<6>[  246.412780] (stk) :ldisc_install = 1
<6>[  246.469940] (stc): st_tty_open
<6>[  246.473602] (stk) : line discipline installed
<6>[  246.481658] (stk) :TIInit_7.2.31.bts
<4>[  246.493774] (stk) :change remote baud rate command in firmware
<4>[  246.501770] (stk) :skipping the wait event of change remote baud
<6>[  247.220642] (stc): add_channel_to_table: id 4
<6>[  247.220642] (stc): st_register(2)
<6>[  247.229034] (stc): add_channel_to_table: id 2
<6>[  247.233947] (stc): st_register(3)
<6>[  247.233947] (stc): add_channel_to_table: id 3
<7>[  247.242309] hci0: type 1 len 4
<7>[  247.243133] hci0: type 1 len 4
<7>[  247.243896] hci0: type 1 len 4
<7>[  247.244567] hci0: type 1 len 4
<7>[  247.245239] hci0: type 1 len 4
<7>[  247.245758] hci0: type 1 len 4
<7>[  247.246337] hci0: type 1 len 4
<7>[  247.247589] hci0: type 1 len 4
<7>[  247.248138] hci0: type 1 len 5
<7>[  247.248657] hci0: type 1 len 6
<7>[  247.249176] hci0: type 1 len 11
<7>[  247.249786] hci0: type 1 len 12
<7>[  247.250274] hci0: type 1 len 4
<7>[  247.250976] hci0: type 1 len 5
<7>[  247.251495] hci0: type 1 len 5
<7>[  247.252075] hci0: type 1 len 4
<7>[  247.252563] hci0: type 1 len 5
<7>[  247.253173] hci0: type 1 len 6
<7>[  247.302947] hci0: type 1 len 11
<7>[  247.304260] hci0: type 1 len 12
<7>[  247.304870] hci0: type 1 len 5
<7>[  247.305419] hci0: type 1 len 5
<7>[  247.305908] hci0: type 1 len 4
<7>[  247.306518] hci0: type 1 len 6
<7>[  247.307037] hci0: type 1 len 252
<7>[  247.309783] hci0: type 1 len 7
<7>[  247.310882] hci0: type 1 len 5
<7>[  247.311584] hci0: type 1 len 4
<7>[  247.313995] hci0: type 1 len 4
<7>[  247.315460] hci0: type 1 len 4
<7>[  247.315979] hci0: type 1 len 4
<7>[  247.334045] hci0: type 1 len 4
<7>[  247.335083] hci0: type 1 len 245
<7>[  252.329956] hci0: type 1 len 9
<7>[  265.165374] hci0: type 1 len 17
<7>[  265.545959] hci0: type 1 len 6
<7>[  265.569396] hci0: type 1 len 14
<7>[  265.569488] hci0: type 2 len 15
<7>[  265.581604] hci0: type 2 len 17
<7>[  265.595550] hci0: type 2 len 17
<7>[  265.595733] hci0: type 2 len 23
<7>[  265.608154] hci0: type 2 len 29
<7>[  265.634521] hci0: type 2 len 33
<7>[  265.655334] hci0: type 2 len 33
<7>[  265.674957] hci0: type 2 len 17
<7>[  267.724517] hci0: type 1 len 7

--
 
 

[Pavan Savoy]

Hi

It might but then again we would just be delaying the inevitable. So you will have to #define VERBOSE and debug usrt error

On Tuesday, January 29, 2013, wrote:

verbose log

] hci0: type 1 len 5

<7>[  305.920898] <out<32
<7>[  305.953796] >in>33
<7>[  305.953796] <out<01 1a 0c 01 02
<7>[  305.954437] >in>04 0e 04 01 1a 0c 00
<7>[  305.957092] hci0: type 1 len 4
<7>[  305.957092] <out<01 19 0c 00
<7>[  305.957641] >in>04 0e 05 01 19 0c 00 02
<7>[  306.057586] >in>30
<7>[  306.057586] <out<31


On Wednesday, January 30, 2013 12:25:29 PM UTC+5:30, prasannak...@gmail.com wrote:

Does increasing this time solve this issue?

 #define BT_REGISTER_TIMEOUT   6000

On Monday, January 28, 2013 5:05:55 PM UTC+5:30, prasannak...@gmail.com wrote:

Pavan

Now the one which was working earlier isnt working now
I do not want fm driver and wlan and bt should be fine disabling fm would it solve line discipline issue?

Regards
prasanna


On Monday, January 28, 2013 2:23:35 PM UTC+5:30, prasannak...@gmail.com wrote:

When I switch to different sdcard running previous prebuilt it is not turning on which it had some time back

On Monday, January 28, 2013 1:54:08 PM UTC+5:30, prasannak...@gmail.com wrote:

BT address is not shown too with
ine disc installation timed out
<6>[  145.487915] (stk) :ldisc_install = 0
<6>[  147.029876] (stk) :ldisc_install = 1
<3>[  148.050323] (stk) :line disc installation timed out
<6>[  148.050384] (stk) :ldisc_install = 0


On Monday, January 28, 2013 1:48:20 PM UTC+5:30, prasannak...@gmail.com wrote:

when I now switch on it takes so long time and gives
<3>[  125.805999] Bluetooth: hci0 command tx timeout
<7>[  125.811309] hci0: type 1 len 4
<3>[  126.815795] Bluetooth: hci0 command tx timeout
<7>[  126.820648] hci0: type 1 len 4
<3>[  127.845153] Bluetooth: hci0 command tx timeout
<7>[  127.850311] hci0: type 1 len 4
<3>[  128.875854] Bluetooth: hci0 command tx timeout

and when I give service discovery it fails

--
iPhone sent - iGnore typos

[Pavan Savoy]

If this is a problem with registration and not anything to do with hardware not responding in time then try and remove all other modules like fm GPS NFC and just have BT and ST. This should let you know if the problem is with software

On Wednesday, January 30, 2013, wrote:

Hi pavan,

  It seems problem in the registering Btwilink driver with ST layer.
can u suggest me any thing regarding this.
where i missed in modifications required (i have configure all BT , ST modules ).

Thanks,
Venkatesh.

--
You received this message because you are subscribed to the Google Groups "pandaboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandaboard+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Pavan Savoy]

This needs to looked at from hardware perspective prasanna. You'll have to logic analyse on uart or to begin with probe on n shutdown line... Doesn't look like software issue so can't help much

On Sunday, February 3, 2013, wrote:

Well,pavan wifi is switching on(Which is on the same chip as BT) and I also tried removing wlan and fm but still its showing line disc error!
 (stk) :ldisc_install = 1

 (stk) :line disc installation timed out

 (stk) :ldisc_install = 0root@android:/ # uim //gives me this
uim:@ main
uim:install set previously...
uim:@ st_uart_config
uim: signal received, opening /dev/ttyO1
uim:@ set_baud_rate
uim:set_baud_rate() done
uim:Setting speed to 3000000
uim:@ read_command_complete
uim: Command complete started
uim:@ read_hci_event

uim: read_hci_event
uim:Invalid response

uim:begin polling...
uim:poll broke due to event 10(PRI:2/ERR:8)

uim:read 0 from install

uim:@ st_uart_config

uim:Un-Installed N_TI_WL Line displine

uim:begin polling...
uim:poll broke due to event 10(PRI:2/ERR:8)

uim:read 1 from install

uim:@ st_uart_config
uim: signal received, opening /dev/ttyO1
uim:@ set_baud_rate
uim:set_baud_rate() done
uim:Setting speed to 3000000
uim:@ read_command_complete
uim: Command complete started
uim:@ read_hci_event

uim: read_hci_event
uim:Invalid response

uim:begin polling...
uim:poll broke due to event 10(PRI:2/ERR:8)

uim:read 0 from install

[ecev...@gmail.com]

Hi Pavon,

I am trying to bring up Bluez 5.0 on AM335x EVM. Hardware module used is WL1835. I'm using Wilink 8 compat wireless  and compat-bluetooth packages.
I'm able to communicate with the device but scanning doesn't show any device. Logs are given below.

root@am335x-evm:/usr/share/wl1271-demos/bluetooth/scripts# ./BT_Demo.sh
Starting BT Demo .......
[  165.255798] Bluetooth: Core ver 2.16
[  165.259674] NET: Registered protocol family 31
[  165.264343] Bluetooth: HCI device and connection manager initialized
[  165.270996] Bluetooth: HCI socket layer initialized
[  165.276092] Bluetooth: L2CAP socket layer initialized
[  165.281372] Bluetooth: SCO socket layer initialized

/*
 * #################################################
 *                  Cleaning BT
 * #################################################
 */
 
[  165.375976] NET: Unregistered protocol family 31


!!!!!!!!!!! Start from the MAIN MENU !!!!!!!!!!!!!!!!!

/*
 * #################################################
 *                  Initialize BT
 * #################################################
 */
 
[  165.421844] Bluetooth: Core ver 2.16
[  165.425720] NET: Registered protocol family 31
[  165.430358] Bluetooth: HCI device and connection manager initialized
[  165.437011] Bluetooth: HCI socket layer initialized
[  165.442108] Bluetooth: L2CAP socket layer initialized
[  165.447387] Bluetooth: SCO socket layer initialized
[  165.459899] Bluetooth: Bluetooth Driver for TI WiLink - Version 1.0
[  165.469512] (stc): st_register(4)
[  165.472961] (stc):  chnl_id list empty :4
[  165.477233] (stk) : st_kim_start
[  165.597015] (stk) :ldisc_install = 1uim:poll broke due to event 10(PRI:2/ERR:8)

uim:read 1 from install

uim:@ st_uart_config
uim: signal received, opening /dev/ttyO1
uim:@ set_baud_rate
uim:set_baud_rate() done
uim:Setting speed to 3000000
uim:@ read_command_complete
uim: Command complete started
uim:@ read_hci_event
uim: read_hci_event

uim:Command comp
[  165.652862] (stc): st_tty_open lete done
uim:S
[  165.657409] (stk) : line discipline installed peed changing to
[  165.663879] (stk) :TIInit_11.8.32.bts 3000000, 1
uim:@ set_custom_baud_rate
uim:Installed N_TI_WL Line displine
uim:begin polling...

[  165.711212] (stk) :change remote baud rate command in firmware
[  165.717376] (stk) :skipping the wait event of change remote baud
[  166.634033] (stc): add_channel_to_table: id 4
[  166.638763] (stc): st_register(2)
[  166.642150] (stc): add_channel_to_table: id 2
[  166.646881] (stc): st_register(3)
[  166.650268] (stc): add_channel_to_table: id 3
[  174.188293] Bluetooth: RFCOMM TTY layer initialized
[  174.193481] Bluetooth: RFCOMM socket layer initialized
[  174.198852] Bluetooth: RFCOMM ver 1.11

+++++++++++++++++++++++++++++++++++++++++++++++++++++
               MAIN NENU
+++++++++++++++++++++++++++++++++++++++++++++++++++++
    1 - BT Scan Remote Devices
    2 - BT Get capabilities of Remote Device
    3 - OPP  Test
    4 - FTP  Test
    5 - HID  Test
    6 - HSP  Test
    7 - A2DP Test
    8 - AVRCP Test
    9 - Pair Remote Device
    10 - Unpair Remote Device
    11 - Exit Without BT Shut Down
    12 - Exit With BT Shut Down
====> 1

/*
 * ########### BT-Scan #############
 * Scan for the remote BT devices
 * #################################
 */

Scanning ...

+++++++++++++++++++++++++++++++++++++++++++++++++++++
               MAIN NENU
+++++++++++++++++++++++++++++++++++++++++++++++++++++
    1 - BT Scan Remote Devices
    2 - BT Get capabilities of Remote Device
    3 - OPP  Test
    4 - FTP  Test
    5 - HID  Test
    6 - HSP  Test
    7 - A2DP Test
    8 - AVRCP Test
    9 - Pair Remote Device
    10 - Unpair Remote Device
    11 - Exit Without BT Shut Down
    12 - Exit With BT Shut Down
====> 1 

/*
 * ########### BT-Scan #############
 * Scan for the remote BT devices
 * #################################
 */

Scanning ...

+++++++++++++++++++++++++++++++++++++++++++++++++++++
               MAIN NENU
+++++++++++++++++++++++++++++++++++++++++++++++++++++
    1 - BT Scan Remote Devices
    2 - BT Get capabilities of Remote Device
    3 - OPP  Test
    4 - FTP  Test
    5 - HID  Test
    6 - HSP  Test
    7 - A2DP Test
    8 - AVRCP Test
    9 - Pair Remote Device
    10 - Unpair Remote Device
    11 - Exit Without BT Shut Down
    12 - Exit With BT Shut Down
====> 11

ti-st/m335x-evm:/usr/share/wl1271-demos/bluetooth/scripts# cd /sys/kernel/debug/                                                              
root@am335x-evm:/sys/kernel/debug/ti-st# ls
protocols  version
root@am335x-evm:/sys/kernel/debug/ti-st# cat version
AC20 11.8.32
root@am335x-evm:/sys/kernel/debug/ti-st#
root@am335x-evm:/sys/kernel/debug/ti-st# cd protocols
-sh: cd: protocols: Not a directory
root@am335x-evm:/sys/kernel/debug/ti-st# cat protocols
[3]
BT=R
FM=U
GPS=U
root@am335x-evm:/sys/kernel/debug/ti-st#  
root@am335x-evm:/sys/kernel/debug/ti-st# bt-adapter -d

** (bt-adapter:1587): CRITICAL **: Method "GetProperties" with signature "" on interface "org.bluez.Manager" doesn't exist

**
ERROR:lib/bluez/manager.c:201:manager_init: assertion failed: (error == NULL)
Aborted
root@am335x-evm:/sys/kernel/debug/ti-st#

root@am335x-evm:/sys/kernel/debug/bluetooth# cat sco
00:00:00:00:00:00 00:00:00:00:00:00 4
root@am335x-evm:/sys/kernel/debug/bluetooth# cat rfcomm
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 13
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 12
00:00:00:00:00:00 00:00:00:00:00:00 4 10
00:00:00:00:00:00 00:00:00:00:00:00 4 9

root@am335x-evm:/sys/kernel/debug/bluetooth# cat l2cap
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 27 0x0000 0x0000 672 0 2 3
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 23 0x0000 0x0000 672 0 2 0
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 25 0x0000 0x0000 672 0 2 0
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 19 0x0000 0x0000 672 0 1 0
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 17 0x0000 0x0000 672 0 1 0
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 15 0x0000 0x0000 1691 1691 2 0
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 0 0x0004 0x0000 672 0 1 0
84:DD:20:75:D7:7B 00:00:00:00:00:00 4 31 0x0000 0x0000 672 0 1 0
00:00:00:00:00:00 00:00:00:00:00:00 4 1 0x0000 0x0000 672 0 0 0
00:00:00:00:00:00 00:00:00:00:00:00 4 4099 0x0000 0x0000 32767 32767 2 3
00:00:00:00:00:00 00:00:00:00:00:00 4 4097 0x0000 0x0000 32767 32767 1 3
00:00:00:00:00:00 00:00:00:00:00:00 4 3 0x0000 0x0000 1013 0 0 0
root@am335x-evm:/sys/kernel/debug/bluetooth#

root@am335x-evm:/sys/kernel/debug# hciconfig -a

hci0:   Type: BR/EDR  Bus: UART

        BD Address: 84:DD:20:75:D7:7B  ACL MTU: 1021:6  SCO MTU: 180:4
        UP RUNNING PSCAN ISCAN
        RX bytes:843 acl:0 sco:0 events:41 errors:0
        TX bytes:939 acl:0 sco:0 commands:33 errors:0
        Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF
        Link mode: SLAVE ACCEPT
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
    Read Local Name (0x03|0x0014) ncmd 1
    status 0x00 name 'am335x-evm-0'
        Name: 'am335x-evm-0'
< HCI Command: Read Class of Device (0x03|0x0023) plen 0
> HCI Event: Command Complete (0x0e) plen 7
    Read Class of Device (0x03|0x0023) ncmd 1
    status 0x00 class 0x500100
        Class: 0x500100
        Service Classes: Object Transfer, Telephony
        Device Class: Computer, Uncategorized
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
    Read Local Version Information (0x04|0x0001) ncmd 1
    status 0x00
    HCI Version: 4.0 (0x6) HCI Revision: 0x0
    LMP Version: 4.0 (0x6) LMP Subversion: 0xac5f
    Manufacturer: Texas Instruments Inc. (13)
        HCI Version: 4.0 (0x6)  Revision: 0x0
        LMP Version: 4.0 (0x6)  Subversion: 0xac5f
        Manufacturer: Texas Instruments Inc. (13)

root@am335x-evm:/sys/kernel/debug# hcitool scan
Scanning ...
< HCI Command: Inquiry (0x01|0x0001) plen 5
    lap 0x9e8b33 len 8 num 0
> HCI Event: Command Status (0x0f) plen 4
    Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Complete (0x01) plen 1
    status 0x00
root@am335x-evm:/sys/kernel/debug#

What could be the problem??? Am I missing anything? Can you please help?? I'm stuck up in this since long time.

Thanks and Regards
Vaishnavi

[Vaishnavi Raman]

Hi Pavan,

Thank you for the reply. I've attached the two set of scripts that I'm using. Could you please have a look and help me if I'm missing something?

Thanks in Advance.

Regards

Vaishnavi

On Thu, Apr 3, 2014 at 9:01 AM, Pavan Savoy <pavan...@gmail.com> wrote:

Hi, Couldn't reply to your mail earlier.

Generally without hci_tx errors if scanning isn't happening, it is generally a script error.

--

--Pavan Savoy

[LioricZ3 .]

Do you have access to another firmware blob for your Bluetooth IC that you can test with?

When I was setting up Bluetooth for HFP and A2DP on the board (BlueZ 4.11 and 5.0, Alsa and PulseAudio from git, oFono git) I had a similar issue (Bluetooth IC up and running, but no actual radio, no scan or pairing)  when using the 7.2.31 firmware, but the 7.6.15 worked (somewhat) correctly (but I'm on wl1271)

Lioric

--
You received this message because you are subscribed to the Google Groups "pandaboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandaboard+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Pavan Savoy]

Hi, Couldn't reply to your mail earlier.

Generally without hci_tx errors if scanning isn't happening, it is generally a script error.

On Tue, Apr 1, 2014 at 7:33 AM, <ecev...@gmail.com> wrote:

--
--Pavan Savoy

[Pavan Savoy]

Hi,

So, both scripts are similar, in the fact that gpio_script uses a gpio_en.ko which I think is just toggling the BT_EN line and then doing an hciconfig hci0 up - this probably assumes that the hci0 is already available via 

the btwilink driver already built into the kernel.

btwilink_scipt on the other hand probably does the BT_EN via the hciconfig hci0 up - using the hci_up happening on the btwilink.ko - this requires the kernel to have a platform device/driver arch for the BT device with BT_EN line properly assigned.

Again, it is hard to know what is happening until we dive into the kernel...

--
--Pavan Savoy

[ecev...@gmail.com]

Hi Lioric,

Thanks for the reply.

I'm using TIInit_11.8.32.bts firmware. I can't find another firmware blob of this. :(

Thanks and Regards
Vaishnavi

[Vaishnavi Raman]

Hi Pavon,

There are three firmwares available across, in the same name "TIInit_11.8.32.bts" which has caused this problem. There is no description available anywhere to say which firmware should be used for which stack or etc.. I found the right firmware.

Now, It started scanning. Now I'm trying to prove bluez test cases. Pairing, unpairing works. Object Push from Remote-Device to WL1271-Host works.

But, when I try to transfer a file through OPP from host to device, I get the error below.

==== Options for OPP test ====
1 - Object Push from Remote-Device to WL1271-Host
2 - Object push from WL1271-Host to Remote-Device
3 - Goto MAIN MENU
====> 2

/*
 * ############################### BT-OPP ###################################
 * Object Push Profile (OPP) is for sending objects such as pictures,
 * virtual business cards etc. It is called push because the transfers
 * are always instigated by the sender (client), not the  receiver (server).
 * ##########################################################################
 */
 
--- Object push from WL1271-Host to Remote-Device ---
Enter the BD_ADDR of the remote Device for OPP test
====> A8:E0:18:FF:EE:28

Local File Available ...

Document.jpg             Pop.wav                  WLAN_Bluetooth_demo.wmv
 Enter the Local file to be transferred
====> 1
Creating Session
Traceback (most recent call last):
  File "/usr/share/bluetooth/opp-client", line 111, in <module>
    path = client.CreateSession(options.device, { "Target": "OPP" })
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 143, in __call__
    **keywords)
  File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 630, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.bluez.obex.Error.Failed: Unable to request session

Have you faced this problem before? Could you please help? Any problem with package?

Thanks and Regards

Vaishnavi