[Bluez-devel] SCO connection timed out issue

[Bluez-devel] SCO connection timed out issue

[\x11]

[-- Attachment #1: Type: text/plain, Size: 3418 bytes --]


Hi All:

Right now,I'm doing a project aiming to enable the bluez audio feature
on linux 2.6.18 based on a s3c2410 embeded development board.We are
trying to enable the SCO headset and A2DP audio feature.I'm using
bluez-libs-3.20 and bluez-utils-3.20 and ALSA audio drivers.I've also
applied the 2 patches:"sco-flow-control-4.2 patch" and another kernel
patch "patch-2.6.18-mh8" downloaded from bluez.org . I'm using a
bluetooth adapter called "STLC2500C" based on UART interface.It has a
serial-USB converter on it so it would be connected to my board
through USB.In linux, it would be the device:/dev/ttyUSB0.
The trouble is , i've tried many different ways to play audio via SCO
headset(aplay -D headset /1.wav,hstest play /1.wav 00:0D:3C:EB:53:F0
1....etc),it always result in an "Can't connect SCO audio channel:
Connection timed out" failure.The pairing procedure is okey.
Here are some detailed information:

First,these are the commands i put in the /etc/init.d/rcS
initialization procedures:
hciattach ttyUSB0 any
hciconfig hci0 up
rm -f /var/run/messagebus.pid
dbus-daemon --system --fork
hcid -n -d -f /etc/bluetooth/hcid.conf &
sdpd -n &
a2dpd -n &
hcitool scan
hciconfig -a
sdptool add A2SRC
sdptool add A2SNK
sdptool add AVRTG
sdptool add hs
sdptool add hf
headsetd -n &
hciconfig hci0 voice 0x0060

#hciconfig hci0 revision：
hci0: Type: UART
BD Address: 00:80:E1:00:00:00 ACL MTU: 1021:7 SCO MTU: 0:0

STLC2500 R4.2 12102005 12:40:14 ZAV100012
HW Id= V440BAA
(My SCO MTU is 0:0,is this okey?)

#aplay -D headset /1.wav
Can't connect SCO audio channel: Connection timed out

# hstest play /1.wav 00:0D:3C:EB:53:F0 1
Voice setting: 0x0060
RFCOMM channel connected
Can't connect SCO audio channel: Connection timed out

(I've also tried btsco,aplay -D plughw:Headset /1.wav,.....etc. the
failures are the same)

#hcitool con
Connections:
< SCO 00:0D:3C:EB:53:F0 handle 0 state 5 lm SLAVE
< ACL 00:0D:3C:EB:53:F0 handle 1 state 1 lm SLAVE ENCRYPT

(it seems the SCO link is incomplete.state=5,not 1.)

I read the headset profile spec:
http://www.bluetooth.com/NR/rdonlyres/5C0DEE05-84CD-4D79-BD52-7ECA283430A0/981/HSP_SPEC_V11.pdf
and on it says that "
The audio gateway controls the SCO link establishment and release." So
i thought maybe i should pay attention to the "Audio Gateway".

Later i found something.I checked out the website "
http://wiki.bluez.org/wiki/Audio" and found that the
/bluez-utils-3.20/audio/gateway.c implements the
org.bluez.audio.gateway interface.But when i looked into the
gateway.c, there's nothing in there.And /bluez-
utils-3.20/audio-api.txt also says that the audio gateway service is
not yet implemented in the current bluez. Is that true? If it is so
,does this means that there's no way we can enable the SCO/A2DP audio
connection to the headset right now?

I'm really confused cause i read about an
article:http://bluetooth-alsa.sourceforge.net/build.html ,which
teaches the reader how to enable bluez audio without mentioning
anything about the org.bluez.audio.gateway implementation.

So is this "audio gateway " necessary for SCO link establishment? Or
there's anything else going wrong ?




Thanks in advance!


semiyd
_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[Brad Midgley]

semiyd

> Later i found something.I checked out the website "
> http://wiki.bluez.org/wiki/Audio" and found that the
> /bluez-utils-3.20/audio/gateway.c implements the
> org.bluez.audio.gateway interface.But when i looked into the
> gateway.c, there's nothing in there.And /bluez-
> utils-3.20/audio-api.txt also says that the audio gateway service is
> not yet implemented in the current bluez. Is that true? If it is so
> ,does this means that there's no way we can enable the SCO/A2DP audio
> connection to the headset right now?

for now the files there are named backward. gateway.c would contain
code for talking to a gateway device, not for being a gateway. You can
experiment now with sco/a2dp to a headset just fine.

> I'm really confused cause i read about an
> article:http://bluetooth-alsa.sourceforge.net/build.html ,which
> teaches the reader how to enable bluez audio without mentioning
> anything about the org.bluez.audio.gateway implementation.

the bluetooth-alsa stuff is all old. that's why there's a banner
across the top of the page directing people to the new stuff.

brad

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[\x11]

[-- Attachment #1: Type: text/plain, Size: 6108 bytes --]


Brad:

    thanks for the hint!
    According to what u mentioned , i read about the page:http://wiki.bluez.org/wiki/HOWTO/AudioDevices
which says"Note: you will not need bluetooth-alsa, plugz, btsco or the like for audio to work. They are obsolete."
    So it seems i shoud get rid of all the btsco,plugz stuff.
    After i deleted btsco/plugz,then what kind of command should i use?
    i tried "aplay -D bluetooth /1.wav "(which has nothing to do with btsco or plugz)and get this:

\ $ aplay -D bluetooth /1.wav
audio[326]: Accepted new client connection on unix socket (fd=8)
audio[326]: Package PKT_TYPE_CFG_REQ:0
hcid[318]: /org/bluez: org.bluez.Manager.FindAdapter()
audio[326]: Got path /org/bluez/hci0 for adapter with address 00:80:E1:00:00:00
hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles()
hcid[318]: no matching session found. creating a new one
hcid[318]: sdp session added to cache
hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles()
hcid[318]: found matching session, removing from list
hcid[318]: sdp session added to cache
hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles()
hcid[318]: found matching session, removing from list
hcid[318]: sdp session added to cache
hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord()
hcid[318]: found matching session, removing from list
hcid[318]: sdp session added to cache
hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord()
hcid[318]: found matching session, removing from list
hcid[318]: sdp session added to cache
hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord()
hcid[318]: found matching session, removing from list
hcid[318]: sdp session added to cache
hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord()
hcid[318]: found matching session, removing from list
hcid[318]: sdp session added to cache
audio[326]: Audio service discovery completed with success
hcid[318]: /org/bluez/hci0: org.bluez.Adapter.FinishRemoteServiceTransaction()
hcid[318]: found matching session, removing from list
audio[326]: Found Hansfree record
audio[326]: Discovered Headset service on RFCOMM channel 1
audio[326]: Found Headset record
audio[326]: Found Audio Sink
audio[326]: Selecting default device
audio[326]: avdtp_ref(0x3b018): ref=2
audio[326]: a2dp_source_request_stream: selected SEP 0x37250
audio[326]: avdtp_ref(0x3b018): ref=3
hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
audio[326]: AVDTP: connected signaling channel to 00:0D:3C:EB:53:F0
audio[326]: session_cb
audio[326]: DISCOVER request succeeded
audio[326]: seid 1 type 1 media 0 in use 0
audio[326]: seid 2 type 1 media 0 in use 0
audio[326]: session_cb
audio[326]: GET_CAPABILITIES request succeeded
audio[326]: seid 1 type 1 media 0
hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
audio[326]: session_cb
audio[326]: GET_CAPABILITIES request succeeded
audio[326]: seid 2 type 1 media 0
audio[326]: Discovery complete
audio[326]: avdtp_set_configuration(0x3b018): int_seid=1, acp_seid=1
audio[326]: session_cb
audio[326]: SET_CONFIGURATION request succeeded
audio[326]: SBC Source: Set_Configuration_Cfm
audio[326]: avdtp_ref(0x3b018): ref=4
audio[326]: stream state changed: IDLE -> CONFIGURED
audio[326]: session_cb
audio[326]: OPEN request succeeded
audio[326]: stream state changed: CONFIGURED -> OPEN
audio[326]: AVDTP: connected transport channel to 00:0D:3C:EB:53:F0
audio[326]: SBC Source: Open_Cfm
audio[326]: session_cb
audio[326]: START request succeeded
audio[326]: SBC Source: Start_CAlignment trap: bluetoothd-serv (326) PC=0x0001be44 Instr=0xe1c320b0 Address=0xbec85c2d FSR 0x813
fm
audio[326]: SBC Source SEP 0x37250 locked
aplay: main:550: audio open error: Input/output error
hcid[318]: Service owner exited: :1.2
hcid[318]: Audio service (audio) was killed by signal 7
hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)

some kind of Input/output error....   any ideas?




thanks in advance!


semiyd


> Date: Wed, 17 Oct 2007 19:49:57 -0600
> From: bmidgley@gmail.com
> To: bluez-devel@lists.sourceforge.net
> Subject: Re: [Bluez-devel] SCO connection timed out issue
>
> semiyd
>
>> Later i found something.I checked out the website "
>> http://wiki.bluez.org/wiki/Audio" and found that the
>> /bluez-utils-3.20/audio/gateway.c implements the
>> org.bluez.audio.gateway interface.But when i looked into the
>> gateway.c, there's nothing in there.And /bluez-
>> utils-3.20/audio-api.txt also says that the audio gateway service is
>> not yet implemented in the current bluez. Is that true? If it is so
>> ,does this means that there's no way we can enable the SCO/A2DP audio
>> connection to the headset right now?
>
> for now the files there are named backward. gateway.c would contain
> code for talking to a gateway device, not for being a gateway. You can
> experiment now with sco/a2dp to a headset just fine.
>
>> I'm really confused cause i read about an
>> article:http://bluetooth-alsa.sourceforge.net/build.html ,which
>> teaches the reader how to enable bluez audio without mentioning
>> anything about the org.bluez.audio.gateway implementation.
>
> the bluetooth-alsa stuff is all old. that's why there's a banner
> across the top of the page directing people to the new stuff.
>
> brad
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now>> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[\x11]

[-- Attachment #1: Type: text/plain, Size: 6854 bytes --]


PS:  the debug information from "aplay -D bluetooth /1.wav " indicates that the audio service(audio[326], that is /lib/bluetooth/bluetoothd-service-audio) is killed .

don't know why.........



> From: semiyd@hotmail.com
> To: bluez-devel@lists.sourceforge.net
> Date: Thu, 18 Oct 2007 02:46:06 +0000
> Subject: Re: [Bluez-devel] SCO connection timed out issue
>
>
> Brad:
>
> thanks for the hint!
> According to what u mentioned , i read about the page:http://wiki.bluez.org/wiki/HOWTO/AudioDevices
> which says"Note: you will not need bluetooth-alsa, plugz, btsco or the like for audio to work. They are obsolete."
> So it seems i shoud get rid of all the btsco,plugz stuff.
> After i deleted btsco/plugz,then what kind of command should i use?
> i tried "aplay -D bluetooth /1.wav "(which has nothing to do with btsco or plugz)and get this:
>
> \ $ aplay -D bluetooth /1.wav
> audio[326]: Accepted new client connection on unix socket (fd=8)
> audio[326]: Package PKT_TYPE_CFG_REQ:0
> hcid[318]: /org/bluez: org.bluez.Manager.FindAdapter()
> audio[326]: Got path /org/bluez/hci0 for adapter with address 00:80:E1:00:00:00
> hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles()
> hcid[318]: no matching session found. creating a new one
> hcid[318]: sdp session added to cache
> hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles()
> hcid[318]: found matching session, removing from list
> hcid[318]: sdp session added to cache
> hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceHandles()
> hcid[318]: found matching session, removing from list
> hcid[318]: sdp session added to cache
> hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord()
> hcid[318]: found matching session, removing from list
> hcid[318]: sdp session added to cache
> hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord()
> hcid[318]: found matching session, removing from list
> hcid[318]: sdp session added to cache
> hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord()
> hcid[318]: found matching session, removing from list
> hcid[318]: sdp session added to cache
> hcid[318]: /org/bluez/hci0: org.bluez.Adapter.GetRemoteServiceRecord()
> hcid[318]: found matching session, removing from list
> hcid[318]: sdp session added to cache
> audio[326]: Audio service discovery completed with success
> hcid[318]: /org/bluez/hci0: org.bluez.Adapter.FinishRemoteServiceTransaction()
> hcid[318]: found matching session, removing from list
> audio[326]: Found Hansfree record
> audio[326]: Discovered Headset service on RFCOMM channel 1
> audio[326]: Found Headset record
> audio[326]: Found Audio Sink
> audio[326]: Selecting default device
> audio[326]: avdtp_ref(0x3b018): ref=2
> audio[326]: a2dp_source_request_stream: selected SEP 0x37250
> audio[326]: avdtp_ref(0x3b018): ref=3
> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
> audio[326]: AVDTP: connected signaling channel to 00:0D:3C:EB:53:F0
> audio[326]: session_cb
> audio[326]: DISCOVER request succeeded
> audio[326]: seid 1 type 1 media 0 in use 0
> audio[326]: seid 2 type 1 media 0 in use 0
> audio[326]: session_cb
> audio[326]: GET_CAPABILITIES request succeeded
> audio[326]: seid 1 type 1 media 0
> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
> audio[326]: session_cb
> audio[326]: GET_CAPABILITIES request succeeded
> audio[326]: seid 2 type 1 media 0
> audio[326]: Discovery complete
> audio[326]: avdtp_set_configuration(0x3b018): int_seid=1, acp_seid=1
> audio[326]: session_cb
> audio[326]: SET_CONFIGURATION request succeeded
> audio[326]: SBC Source: Set_Configuration_Cfm
> audio[326]: avdtp_ref(0x3b018): ref=4
> audio[326]: stream state changed: IDLE -> CONFIGURED
> audio[326]: session_cb
> audio[326]: OPEN request succeeded
> audio[326]: stream state changed: CONFIGURED -> OPEN
> audio[326]: AVDTP: connected transport channel to 00:0D:3C:EB:53:F0
> audio[326]: SBC Source: Open_Cfm
> audio[326]: session_cb
> audio[326]: START request succeeded
> audio[326]: SBC Source: Start_CAlignment trap: bluetoothd-serv (326) PC=0x0001be44 Instr=0xe1c320b0 Address=0xbec85c2d FSR 0x813
> fm
> audio[326]: SBC Source SEP 0x37250 locked
> aplay: main:550: audio open error: Input/output error
> hcid[318]: Service owner exited: :1.2
> hcid[318]: Audio service (audio) was killed by signal 7
> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
>
> some kind of Input/output error.... any ideas?
>
>
>
>
> thanks in advance!
>
>
> semiyd
>
>
>> Date: Wed, 17 Oct 2007 19:49:57 -0600
>> From: bmidgley@gmail.com
>> To: bluez-devel@lists.sourceforge.net
>> Subject: Re: [Bluez-devel] SCO connection timed out issue
>>
>> semiyd
>>
>>> Later i found something.I checked out the website "
>>> http://wiki.bluez.org/wiki/Audio" and found that the
>>> /bluez-utils-3.20/audio/gateway.c implements the
>>> org.bluez.audio.gateway interface.But when i looked into the
>>> gateway.c, there's nothing in there.And /bluez-
>>> utils-3.20/audio-api.txt also says that the audio gateway service is
>>> not yet implemented in the current bluez. Is that true? If it is so
>>> ,does this means that there's no way we can enable the SCO/A2DP audio
>>> connection to the headset right now?
>>
>> for now the files there are named backward. gateway.c would contain
>> code for talking to a gateway device, not for being a gateway. You can
>> experiment now with sco/a2dp to a headset just fine.
>>
>>> I'm really confused cause i read about an
>>> article:http://bluetooth-alsa.sourceforge.net/build.html ,which
>>> teaches the reader how to enable bluez audio without mentioning
>>> anything about the org.bluez.audio.gateway implementation.
>>
>> the bluetooth-alsa stuff is all old. that's why there's a banner
>> across the top of the page directing people to the new stuff.
>>
>> brad
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now>> http://get.splunk.com/
>> _______________________________________________
>> Bluez-devel mailing list
>> Bluez-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
> _________________________________________________________________
> Explore the seven wonders of the world
> http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
>

_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[Fabien Chevalier]

Hi,

Sorry i have to say you this, but you're basically trying to make sth
work that will never make it ;-)

* STLC2500C does not support sco over hci, so unless your development 
has an audio codec hardwired to the BT chip, you're screwed :-(
* You need latest bluez-utils CVS to have any chance for your chip
to run at decent speed, which is required for a2dp streaming. You should 
then use the follwing syntax to start the chip at max speed: hciattach 
/dev/ttyUSB0 stlc2500 921600

Apart from that this is know to work.

Regards,

Fabien

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[\x11]

[-- Attachment #1: Type: text/plain, Size: 3440 bytes --]


Hi Fabien:
     Thanks a lot for the info!
      * Im confused about what you said about the sco function on STLC2500C.According to the IC datasheet of STLC2500C downloaded from 'www.st.com', it says that this chip supports SCO link. So are you saying that this chip simply can't support SCO under linux?(i have a couple of evaluation software of STLC2500C evaluation board under windowXP.It seems that under windows , its SCO link works.But im not very sure about this.)
      * i followed your hint and used the command "hciattach ttyUSB0 stlc2500" and then got the following information:

Loading file /lib/firmware/STLC2500_R4_02_04.ptc
Loading file /lib/firmware/STLC2500_R4_02_02_WLAN.ssf

 STLC2500 R4.2 12102005 12:40:14 ZAV100012  05
       HW Id= V440BAA

i copied 2 files:
STLC2500_R4_02_02_WLAN.ssf
STLC2500_R4_02_04.ptc
from the bluez-firmware-1.2/st  to the /lib/firmware folder.

i didn't use the "hciattach ttyUSB0 stlc2500 921600" cause this will give the following error:

pl2303 ttyUSB0: pl2303 driver does not support the baudrate requested (fix it)

It seems the pl2303(the serial-USB converter IC on STLC2500C evaluation board) driver does not support the baudrate of 921600.

So up to now , some good improvements have been made thanks to your suggestion. 
Anyway , i got the same err when i tried to connect using the command :aplay -D bluetooth /1.wav

aplay: main:550: audio open error: Input/output error
hcid[318]: Service owner exited: :1.2
hcid[318]: Audio service (audio) was killed by signal 7
hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)

http://wiki.bluez.org/wiki/HOWTO/AudioDevices 
says that i can use bluez only without btsco or plugz.It says using the command "aplay -D bluetooth /1.wav" is just fine.
So i really have no idea if there's any other command i can use in order to connect the headset based on A2DP.
i also don't know whether this "aplay -D bluetooth /1.wav" is aimed to connect the headset with A2DP or SCO.....?



Thank a lot.



semiyd

> Date: Thu, 18 Oct 2007 12:31:40 +0200
> From: fabchevalier@free.fr
> To: bluez-devel@lists.sourceforge.net
> Subject: Re: [Bluez-devel] SCO connection timed out issue
>
> Hi,
>
> Sorry i have to say you this, but you're basically trying to make sth
> work that will never make it ;-)
>
> * STLC2500C does not support sco over hci, so unless your development
> has an audio codec hardwired to the BT chip, you're screwed :-(
> * You need latest bluez-utils CVS to have any chance for your chip
> to run at decent speed, which is required for a2dp streaming. You should
> then use the follwing syntax to start the chip at max speed: hciattach
> /dev/ttyUSB0 stlc2500 921600
>
> Apart from that this is know to work.
>
> Regards,
>
> Fabien
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now>> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

_________________________________________________________________
News, entertainment and everything you care about at Live.com. Get it now!
http://www.live.com/getstarted.aspx


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[\x11]

[-- Attachment #1: Type: text/plain, Size: 3506 bytes --]



Hi Fabien:
      Thanks a lot for the info!

      * Im confused about what you said about the sco function on STLC2500C.According to the IC datasheet of STLC2500C downloaded from 'www.st.com', it says that this chip supports SCO link. So are you saying that this chip simply can't support SCO under linux?(i have a couple of evaluation software of STLC2500C evaluation board under windowXP.It seems that under windows , its SCO link works.But im not very sure about this.)

      * i followed your hint and used the command "hciattach ttyUSB0 stlc2500" and then got the following information: 
Loading file /lib/firmware/STLC2500_R4_02_04.ptc
Loading file /lib/firmware/STLC2500_R4_02_02_WLAN.ssf 
STLC2500 R4.2 12102005 12:40:14 
ZAV100012 05HW Id= V440BAA 

i copied 2 files:
STLC2500_R4_02_02_WLAN.ssf
STLC2500_R4_02_04.ptc
from the bluez-firmware-1.2/st to the /lib/firmware folder. 

i didn't use the "hciattach ttyUSB0 stlc2500 921600" cause this will give the following error:
 pl2303 ttyUSB0: pl2303 driver does not support the baudrate requested (fix it)
 It seems the pl2303(the serial-USB converter IC on STLC2500C evaluation board) driver does not support the baudrate of 921600.

 So up to now , some good improvements have been made thanks to your suggestion. Anyway , i got the same err when i tried to connect using the command :aplay -D bluetooth /1.wav
 aplay: main:550: audio open error: Input/output error
hcid[318]: Service owner exited: :1.2
hcid[318]: Audio service (audio) was killed by signal 7
hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0) 

http://wiki.bluez.org/wiki/HOWTO/AudioDevices says that i can use bluez only without btsco or plugz.It says using the command "aplay -D bluetooth /1.wav" is just fine.So i really have no idea if there's any other command i can use in order to connect the headset based on A2DP.i also don't know whether this "aplay -D bluetooth /1.wav" is aimed to connect the headset with A2DP or SCO.....?   


Thank a lot. 



  semiyd




> Date: Thu, 18 Oct 2007 12:31:40 +0200
> From: fabchevalier@free.fr
> To: bluez-devel@lists.sourceforge.net
> Subject: Re: [Bluez-devel] SCO connection timed out issue
>
> Hi,
>
> Sorry i have to say you this, but you're basically trying to make sth
> work that will never make it ;-)
>
> * STLC2500C does not support sco over hci, so unless your development
> has an audio codec hardwired to the BT chip, you're screwed :-(
> * You need latest bluez-utils CVS to have any chance for your chip
> to run at decent speed, which is required for a2dp streaming. You should
> then use the follwing syntax to start the chip at max speed: hciattach
> /dev/ttyUSB0 stlc2500 921600
>
> Apart from that this is know to work.
>
> Regards,
>
> Fabien
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now>> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[Fabien Chevalier]

Please find some comments below
> 
>       * Im confused about what you said about the sco function on STLC2500C.According to the IC datasheet of STLC2500C downloaded from 'www.st.com', it says that this chip supports SCO link. So are you saying that this chip simply can't support SCO under linux?(i have a couple of evaluation software of STLC2500C evaluation board under windowXP.It seems that under windows , its SCO link works.But im not very sure about this.)

It's basically not in the datasheet, but it is how things are. The chip 
supports SCO but not over hci, only over PCM.
It won't work with windows either :-(

> 
>       * i followed your hint and used the command "hciattach ttyUSB0 stlc2500" and then got the following information: 
> Loading file /lib/firmware/STLC2500_R4_02_04.ptc
> Loading file /lib/firmware/STLC2500_R4_02_02_WLAN.ssf 
> STLC2500 R4.2 12102005 12:40:14 
> ZAV100012 05HW Id= V440BAA 
> 
> i copied 2 files:
> STLC2500_R4_02_02_WLAN.ssf
> STLC2500_R4_02_04.ptc
> from the bluez-firmware-1.2/st to the /lib/firmware folder. 
> 
> i didn't use the "hciattach ttyUSB0 stlc2500 921600" cause this will give the following error:
>  pl2303 ttyUSB0: pl2303 driver does not support the baudrate requested (fix it)
>  It seems the pl2303(the serial-USB converter IC on STLC2500C evaluation board) driver does not support the baudrate of 921600.

Yes that's true, you need a 2.6.23 kernel for this high speed. With 
2.6.18 you should be able to go to 460800 bps though, please retry with 
hciattach ttyUSB0 stlc2500 460800


> 
>  So up to now , some good improvements have been made thanks to your suggestion. Anyway , i got the same err when i tried to connect using the command :aplay -D bluetooth /1.wav
>  aplay: main:550: audio open error: Input/output error
> hcid[318]: Service owner exited: :1.2
> hcid[318]: Audio service (audio) was killed by signal 7
> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0) 

I have no idea of what's going wrong either. If you attach gdb to the 
bluetoothd-service-audio and show me where the program breaks i could 
tell more.

Cheers,

Fabien

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[Brad Midgley]

semiyd

> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)

did you start up a passkey agent? under some setups I have to do this manually:

passkey-agent --default 0000 &

brad

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[\x11]

[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]


Hi Brad:
       No , i didn't start up the passkey agent:)
       In /etc/bluetooth/hcid.conf ,my configuration is "security auto;"
       I manually created a file named 'pincodes' in /var/lib/bluetooth/XX:XX:XX:XX:XX:XX/ and put the linkcode
in it . So that hcid will find the linkcode when requested by the headset.

thanks

semiyd


> Date: Thu, 18 Oct 2007 07:24:58 -0600
> From: bmidgley@gmail.com
> To: bluez-devel@lists.sourceforge.net
> Subject: Re: [Bluez-devel] SCO connection timed out issue
>
> semiyd
>
>> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
>> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
>
> did you start up a passkey agent? under some setups I have to do this manually:
>
> passkey-agent --default 0000 &
>
> brad
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now>> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[Brad Midgley]

semiyd,

fyi you get unpredictable behavior if you change stuff in
/var/lib/bluetooth manually.

brad

On 10/18/07, semiyd@hotmail.com <semiyd@hotmail.com> wrote:
>
> Hi Brad:
>        No , i didn't start up the passkey agent:)
>        In /etc/bluetooth/hcid.conf ,my configuration is "security auto;"
>        I manually created a file named 'pincodes' in /var/lib/bluetooth/XX:XX:XX:XX:XX:XX/ and put the linkcode
> in it . So that hcid will find the linkcode when requested by the headset.
>
> thanks
>
> semiyd

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[dong yan]

Hi Brad:
      You are right.I launched passkey-agent with the command
"passkey-agent --default 8888 &". After that ,i deleted the headset
related linkcode in the /var/lib/bluetooth/XX:XX:XX:XX:XX:XX/pincodes.
Now hcid looks for the linkcode from passkey-agent.
Here:
hcid[306]: link_key_request (sba=00:80:E1:00:AB:BA,
dba=00:0D:3C:EB:53:F0) hcid[306]: pin_code_request
(sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0) hcid[306]: Calling
PasskeyAgent.Request: name=:1.3, path=/org/bluez/passkey_agent_328
Passkey request for device 00:0D:3C:EB:53:F0
hcid[306]: link_key_notify (sba=00:80:E1:00:AB:BA, dba=00:0D:3C:EB:53:F0)
hcid[306]: link_key_request (sba=00:80:E1:00:AB:BA,
dba=00:0D:3C:EB:53:F0) The pairing procedure to the headset is now
handled by passkey-agent. Seems like hcid will search the linkcode
firstly in that 'pincodes' file. If he didn't find one ,he will turn
to the passkey-agent and ask for the code.

thanks

 semiyd

2007/10/19, Brad Midgley <bmidgley@gmail.com>:
> semiyd,
>
> fyi you get unpredictable behavior if you change stuff in
> /var/lib/bluetooth manually.
>
> brad
>
> On 10/18/07, semiyd@hotmail.com <semiyd@hotmail.com> wrote:
> >
> > Hi Brad:
> >        No , i didn't start up the passkey agent:)
> >        In /etc/bluetooth/hcid.conf ,my configuration is "security auto;"
> >        I manually created a file named 'pincodes' in /var/lib/bluetooth/XX:XX:XX:XX:XX:XX/ and put the linkcode
> > in it . So that hcid will find the linkcode when requested by the headset.
> >
> > thanks
> >
> > semiyd
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[\x11]

[-- Attachment #1: Type: text/plain, Size: 4746 bytes --]


Hi Fabien:
     *Firstly, i could only find the 'data brief' datasheet of
STLC2500C,which has very little information.No more detailed datasheet
could be found...

(http://www.st.com/stonline/products/literature/bd/12019/stlc2500c.pdf)
        I also found something.Maybe related to SCO.In the datasheet,it says:
"
Communication interfaces
-PCM interface for voice
"
        I don't know if this is indicating that the chip only supports sco
over pcm,not hci,or something else...Anyway , no further info about SCO can
be found in this datasheet.I also wrote an email to the ST technical
support team to comfirm the stuff.

       *I looked into the source code in the driver of pl2303 in my
linux.It's true that the max baudrate the driver supports is 460800.
       I'm now using the command 'hciattach ttyUSB0 stlc2500 460800 '.

       *About the error:
aplay: main:550: audio open error: Input/output error
 hcid[318]: Service owner exited: :1.2
 hcid[318]: Audio service (audio) was killed by signal 7
        It's like this:I'm developing on an embeded system(S3c2410 EVB).So
i have to mount the root file system(mounted root) through NFS.I tried gdb
before and seems there's something wrong when gdb goes into the content of
NFS(my 'aplay'and some other programmes are in the file system from NFS).I
got the following error from gdb when mounting on NFS:

Program received signal SIGTRAP, Trace/breakpoint trap

This error will force the gdb into a single step mode .That mode begins
when the system just started to mount the root FS from NFS.
But the GDB is okey with ramdisk-based file systems.
So maybe i should create a ramdisk with all the necessary components of
ALSA and bluez and try the GDB again.


thanks


yandong
> Date: Thu, 18 Oct 2007 15:08:29 +0200
> From: fabchevalier@free.fr
> To: bluez-devel@lists.sourceforge.net
> Subject: Re: [Bluez-devel] SCO connection timed out issue
>
> Please find some comments below
>>
>> * Im confused about what you said about the sco function on STLC2500C.According to the IC datasheet of STLC2500C downloaded from 'www.st.com', it says that this chip supports SCO link. So are you saying that this chip simply can't support SCO under linux?(i have a couple of evaluation software of STLC2500C evaluation board under windowXP.It seems that under windows , its SCO link works.But im not very sure about this.)
>
> It's basically not in the datasheet, but it is how things are. The chip
> supports SCO but not over hci, only over PCM.
> It won't work with windows either :-(
>
>>
>> * i followed your hint and used the command "hciattach ttyUSB0 stlc2500" and then got the following information:
>> Loading file /lib/firmware/STLC2500_R4_02_04.ptc
>> Loading file /lib/firmware/STLC2500_R4_02_02_WLAN.ssf
>> STLC2500 R4.2 12102005 12:40:14
>> ZAV100012 05HW Id= V440BAA
>>
>> i copied 2 files:
>> STLC2500_R4_02_02_WLAN.ssf
>> STLC2500_R4_02_04.ptc
>> from the bluez-firmware-1.2/st to the /lib/firmware folder.
>>
>> i didn't use the "hciattach ttyUSB0 stlc2500 921600" cause this will give the following error:
>> pl2303 ttyUSB0: pl2303 driver does not support the baudrate requested (fix it)
>> It seems the pl2303(the serial-USB converter IC on STLC2500C evaluation board) driver does not support the baudrate of 921600.
>
> Yes that's true, you need a 2.6.23 kernel for this high speed. With
> 2.6.18 you should be able to go to 460800 bps though, please retry with
> hciattach ttyUSB0 stlc2500 460800
>
>
>>
>> So up to now , some good improvements have been made thanks to your suggestion. Anyway , i got the same err when i tried to connect using the command :aplay -D bluetooth /1.wav
>> aplay: main:550: audio open error: Input/output error
>> hcid[318]: Service owner exited: :1.2
>> hcid[318]: Audio service (audio) was killed by signal 7
>> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
>
> I have no idea of what's going wrong either. If you attach gdb to the
> bluetoothd-service-audio and show me where the program breaks i could
> tell more.
>
> Cheers,
>
> Fabien
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now>> http://get.splunk.com/
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[\x11]

[-- Attachment #1: Type: text/plain, Size: 5797 bytes --]


Hi Fabien:
       Just got comfirm from ST. No support for sco over hci ;-(     
        They said uncless i buy a mother board with hw-codec and connect it to the STLC2500 adapter .

        About the command "aplay -D bluetooth /1.wav", i have question here:
        Is this command  aimed to connect the headset over A2DP? Or will it automatically adjust the link type between A2DP and SCO accoring to the actual situation? 
        And , is there any command that is aimed to do A2DP with the headset that i can use ?



Thanks!



semiyd



> From: semiyd@hotmail.com
> To: bluez-devel@lists.sourceforge.net
> Date: Fri, 19 Oct 2007 03:16:00 +0000
> Subject: Re: [Bluez-devel] SCO connection timed out issue
>
>
> Hi Fabien:
> *Firstly, i could only find the 'data brief' datasheet of
> STLC2500C,which has very little information.No more detailed datasheet
> could be found...
>
> (http://www.st.com/stonline/products/literature/bd/12019/stlc2500c.pdf)
> I also found something.Maybe related to SCO.In the datasheet,it says:
> "
> Communication interfaces
> -PCM interface for voice
> "
> I don't know if this is indicating that the chip only supports sco
> over pcm,not hci,or something else...Anyway , no further info about SCO can
> be found in this datasheet.I also wrote an email to the ST technical
> support team to comfirm the stuff.
>
> *I looked into the source code in the driver of pl2303 in my
> linux.It's true that the max baudrate the driver supports is 460800.
> I'm now using the command 'hciattach ttyUSB0 stlc2500 460800 '.
>
> *About the error:
> aplay: main:550: audio open error: Input/output error
> hcid[318]: Service owner exited: :1.2
> hcid[318]: Audio service (audio) was killed by signal 7
> It's like this:I'm developing on an embeded system(S3c2410 EVB).So
> i have to mount the root file system(mounted root) through NFS.I tried gdb
> before and seems there's something wrong when gdb goes into the content of
> NFS(my 'aplay'and some other programmes are in the file system from NFS).I
> got the following error from gdb when mounting on NFS:
>
> Program received signal SIGTRAP, Trace/breakpoint trap
>
> This error will force the gdb into a single step mode .That mode begins
> when the system just started to mount the root FS from NFS.
> But the GDB is okey with ramdisk-based file systems.
> So maybe i should create a ramdisk with all the necessary components of
> ALSA and bluez and try the GDB again.
>
>
> thanks
>
>
> yandong
>> Date: Thu, 18 Oct 2007 15:08:29 +0200
>> From: fabchevalier@free.fr
>> To: bluez-devel@lists.sourceforge.net
>> Subject: Re: [Bluez-devel] SCO connection timed out issue
>>
>> Please find some comments below
>>>
>>> * Im confused about what you said about the sco function on STLC2500C.According to the IC datasheet of STLC2500C downloaded from 'www.st.com', it says that this chip supports SCO link. So are you saying that this chip simply can't support SCO under linux?(i have a couple of evaluation software of STLC2500C evaluation board under windowXP.It seems that under windows , its SCO link works.But im not very sure about this.)
>>
>> It's basically not in the datasheet, but it is how things are. The chip
>> supports SCO but not over hci, only over PCM.
>> It won't work with windows either :-(
>>
>>>
>>> * i followed your hint and used the command "hciattach ttyUSB0 stlc2500" and then got the following information:
>>> Loading file /lib/firmware/STLC2500_R4_02_04.ptc
>>> Loading file /lib/firmware/STLC2500_R4_02_02_WLAN.ssf
>>> STLC2500 R4.2 12102005 12:40:14
>>> ZAV100012 05HW Id= V440BAA
>>>
>>> i copied 2 files:
>>> STLC2500_R4_02_02_WLAN.ssf
>>> STLC2500_R4_02_04.ptc
>>> from the bluez-firmware-1.2/st to the /lib/firmware folder.
>>>
>>> i didn't use the "hciattach ttyUSB0 stlc2500 921600" cause this will give the following error:
>>> pl2303 ttyUSB0: pl2303 driver does not support the baudrate requested (fix it)
>>> It seems the pl2303(the serial-USB converter IC on STLC2500C evaluation board) driver does not support the baudrate of 921600.
>>
>> Yes that's true, you need a 2.6.23 kernel for this high speed. With
>> 2.6.18 you should be able to go to 460800 bps though, please retry with
>> hciattach ttyUSB0 stlc2500 460800
>>
>>
>>>
>>> So up to now , some good improvements have been made thanks to your suggestion. Anyway , i got the same err when i tried to connect using the command :aplay -D bluetooth /1.wav
>>> aplay: main:550: audio open error: Input/output error
>>> hcid[318]: Service owner exited: :1.2
>>> hcid[318]: Audio service (audio) was killed by signal 7
>>> hcid[318]: link_key_request (sba=00:80:E1:00:00:00, dba=00:0D:3C:EB:53:F0)
>>
>> I have no idea of what's going wrong either. If you attach gdb to the
>> bluetoothd-service-audio and show me where the program breaks i could
>> tell more.
>>
>> Cheers,
>>
>> Fabien
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems? Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now>> http://get.splunk.com/
>> _______________________________________________
>> Bluez-devel mailing list
>> Bluez-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
> _________________________________________________________________
> Explore the seven wonders of the world
> http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
>

_________________________________________________________________
Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy!
http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us


[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

Re: [Bluez-devel] SCO connection timed out issue

[\x11]

Hi Fabien:
     I got a clue after printf lots of information from the kernel about
my "aplay: main:550: audio open error: Input/output error" after using "apl=
ay -D bluetooth /1.wav".
     In bluez-utils-3.20/audio/pcm_bluetooth.c
           It has a function named:
                 static int bluetooth_cfg(struct bluetooth_data *data,
snd_pcm_stream_t stream,
                       snd_config_t *conf)

                 and the Input/Output error comes from bluetooth_cfg():
***************************************************************************=
************************
     ret =3D send(data->server.fd, pkt, sizeof(*pkt) + pkt->length, 0);
     if (ret < 0)
           return -errno;
     else if (ret =3D=3D 0)
           return -EIO;

     DBG("OK - %d bytes sent. Waiting for response...", ret);

     memset(buf, 0, sizeof(buf));

     ret =3D recv(data->server.fd, buf, sizeof(*pkt) + sizeof(*cfg), 0);
     if (ret < 0)
           return -errno;
     else if (ret =3D=3D 0)
           return -EIO;//This is where Input/Output error come from.
***************************************************************************=
************************
That means after recv(data->server.fd, buf, sizeof(*pkt) + sizeof(*cfg),
0);, it returns a wrong value.

Here's the debug message related to this error:
DEBUG: _snd_pcm_bluetooth_open: Bluetooth PCM plugin (Playback)
DEBUG: bluetooth_init: Connecting to address: /org/bluez/audio
DEBUG: bluetooth_cfg: Sending PKT_TYPE_CFG_REQ...
DEBUG: bluetooth_cfg: OK - 34 bytes sent. Waiting for response...

After Sending PKT_TYPE_CFG_REQ, it seems it didn't
recieve(recv(data->server.fd, buf, sizeof(*pkt) + sizeof(*cfg), 0);) the
proper information.

Can you give me any hints? Is this about PKT_TYPE_CFG_REQ or my .asoundrc
configuration?
***************************************************************************=
***********************************

PS:This is my .asoundrc:
#pcm.a2dpd {
#            type a2dpd
#           }

pcm.bluetooth {
  type bluetooth
     device 00:0D:3C:EB:53:F0
}

#pcm.!default {
#        type hw
#        card 0
#        device 0
#}

pcm.card0 {
   type hw
   card 0
}
ctl.card0 {
   type hw
   card 0
}
***************************************************************************=
************************************



thanks


semiyd




> From: semiyd@hotmail.com
> To: bluez-devel@lists.sourceforge.net
> Date: Fri, 19 Oct 2007 05:55:35 +0000
> Subject: Re: [Bluez-devel] SCO connection timed out issue
>
>
> Hi Fabien:
> Just got comfirm from ST. No support for sco over hci ;-(
> They said uncless i buy a mother board with hw-codec and connect it to th=
e STLC2500 adapter .
>
> About the command "aplay -D bluetooth /1.wav", i have question here:
> Is this command aimed to connect the headset over A2DP? Or will it automa=
tically adjust the link type between A2DP and SCO accoring to the actual si=
tuation?
> And , is there any command that is aimed to do A2DP with the headset that=
 i can use ?
>
>
>
> Thanks!
>
>
>
> semiyd
>
>
>
>> From: semiyd@hotmail.com
>> To: bluez-devel@lists.sourceforge.net
>> Date: Fri, 19 Oct 2007 03:16:00 +0000
>> Subject: Re: [Bluez-devel] SCO connection timed out issue
>>
>>
>> Hi Fabien:
>> *Firstly, i could only find the 'data brief' datasheet of
>> STLC2500C,which has very little information.No more detailed datasheet
>> could be found...
>>
>> (http://www.st.com/stonline/products/literature/bd/12019/stlc2500c.pdf)
>> I also found something.Maybe related to SCO.In the datasheet,it says:
>> "
>> Communication interfaces
>> -PCM interface for voice
>> "
>> I don't know if this is indicating that the chip only supports sco
>> over pcm,not hci,or something else...Anyway , no further info about SCO =
can
>> be found in this datasheet.I also wrote an email to the ST technical
>> support team to comfirm the stuff.
>>
>> *I looked into the source code in the driver of pl2303 in my
>> linux.It's true that the max baudrate the driver supports is 460800.
>> I'm now using the command 'hciattach ttyUSB0 stlc2500 460800 '.
>>
>> *About the error:
>> aplay: main:550: audio open error: Input/output error
>> hcid[318]: Service owner exited: :1.2
>> hcid[318]: Audio service (audio) was killed by signal 7
>> It's like this:I'm developing on an embeded system(S3c2410 EVB).So
>> i have to mount the root file system(mounted root) through NFS.I tried g=
db
>> before and seems there's something wrong when gdb goes into the content =
of
>> NFS(my 'aplay'and some other programmes are in the file system from NFS)=
.I
>> got the following error from gdb when mounting on NFS:
>>
>> Program received signal SIGTRAP, Trace/breakpoint trap
>>
>> This error will force the gdb into a single step mode .That mode begins
>> when the system just started to mount the root FS from NFS.
>> But the GDB is okey with ramdisk-based file systems.
>> So maybe i should create a ramdisk with all the necessary components of
>> ALSA and bluez and try the GDB again.
>>
>>
>> thanks
>>
>>
>> yandong
>>> Date: Thu, 18 Oct 2007 15:08:29 +0200
>>> From: fabchevalier@free.fr
>>> To: bluez-devel@lists.sourceforge.net
>>> Subject: Re: [Bluez-devel] SCO connection timed out issue
>>>
>>> Please find some comments below
>>>>
>>>> * Im confused about what you said about the sco function on STLC2500C.=
According to the IC datasheet of STLC2500C downloaded from 'www.st.com', it=
 says that this chip supports SCO link. So are you saying that this chip si=
mply can't support SCO under linux?(i have a couple of evaluation software =
of STLC2500C evaluation board under windowXP.It seems that under windows , =
its SCO link works.But im not very sure about this.)
>>>
>>> It's basically not in the datasheet, but it is how things are. The chip
>>> supports SCO but not over hci, only over PCM.
>>> It won't work with windows either :-(
>>>
>>>>
>>>> * i followed your hint and used the command "hciattach ttyUSB0 stlc250=
0" and then got the following information:
>>>> Loading file /lib/firmware/STLC2500_R4_02_04.ptc
>>>> Loading file /lib/firmware/STLC2500_R4_02_02_WLAN.ssf
>>>> STLC2500 R4.2 12102005 12:40:14
>>>> ZAV100012 05HW Id=3D V440BAA
>>>>
>>>> i copied 2 files:
>>>> STLC2500_R4_02_02_WLAN.ssf
>>>> STLC2500_R4_02_04.ptc
>>>> from the bluez-firmware-1.2/st to the /lib/firmware folder.
>>>>
>>>> i didn't use the "hciattach ttyUSB0 stlc2500 921600" cause this will g=
ive the following error:
>>>> pl2303 ttyUSB0: pl2303 driver does not support the baudrate requested =
(fix it)
>>>> It seems the pl2303(the serial-USB converter IC on STLC2500C evaluatio=
n board) driver does not support the baudrate of 921600.
>>>
>>> Yes that's true, you need a 2.6.23 kernel for this high speed. With
>>> 2.6.18 you should be able to go to 460800 bps though, please retry with
>>> hciattach ttyUSB0 stlc2500 460800
>>>
>>>
>>>>
>>>> So up to now , some good improvements have been made thanks to your su=
ggestion. Anyway , i got the same err when i tried to connect using the com=
mand :aplay -D bluetooth /1.wav
>>>> aplay: main:550: audio open error: Input/output error
>>>> hcid[318]: Service owner exited: :1.2
>>>> hcid[318]: Audio service (audio) was killed by signal 7
>>>> hcid[318]: link_key_request (sba=3D00:80:E1:00:00:00, dba=3D00:0D:3C:E=
B:53:F0)
>>>
>>> I have no idea of what's going wrong either. If you attach gdb to the
>>> bluetoothd-service-audio and show me where the program breaks i could
>>> tell more.
>>>
>>> Cheers,
>>>
>>> Fabien
>>>
>>> -----------------------------------------------------------------------=
--
>>> This SF.net email is sponsored by: Splunk Inc.
>>> Still grepping through log files to find problems? Stop.
>>> Now Search log events and configuration files using AJAX and a browser.
>>> Download your FREE copy of Splunk now>> http://get.splunk.com/
>>> _______________________________________________
>>> Bluez-devel mailing list
>>> Bluez-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>>
>> _________________________________________________________________
>> Explore the seven wonders of the world
>> http://search.msn.com/results.aspx?q=3D7+wonders+world&mkt=3Den-US&form=
=3DQBRE
>>
>
> _________________________________________________________________
> Invite your mail contacts to join your friends list with Windows Live Spa=
ces. It's easy!
> http://spaces.live.com/spacesapi.aspx?wx_action=3Dcreate&wx_url=3D/friend=
s.aspx&mkt=3Den-us
>

_________________________________________________________________
Connect to the next generation of MSN Messenger=A0
http://imagine-msn.com/messenger/launch80/default.aspx?locale=3Den-us&sourc=
e=3Dwlmailtagline
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel