public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Benson Dong <dongas86.dev@hotmail.com>
To: <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] SDP couldn't discovery any device or service (stlc2500)
Date: Tue, 8 Apr 2008 11:32:12 +0800	[thread overview]
Message-ID: <BLU117-W350837E07CCCAD9D0B092E88F20@phx.gbl> (raw)


The environment i used is BT Module (STLC2500) with bluez 3.26 running on M=
ontavista kernel 2.6.18.

Here is hciconfig output:
# hciconfig -a
hci0: Type: UART
BD Address: 00:80:E1:00:AB:BA ACL MTU: 1021:7 SCO MTU: 0:0
UP RUNNING PSCAN ISCAN
RX bytes:718 acl:0 sco:0 events:23 errors:0
TX bytes:369 acl:0 sco:0 commands:23 errors:0
Features: 0xff 0xeb 0x8d 0xfe 0x9b 0xe9 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: ACCEPT MASTER
Name: 'BlueZ (0)'
Class: 0x080100
Service Classes: Capturing
Device Class: Computer, Uncategorized
HCI Ver: 2.0 (0x3) HCI Rev: 0x402 LMP Ver: 2.0 (0x3) LMP Subver: 0x520
Manufacturer: ST Microelectronics (48)

I wonder only from the output of 'hciconfig -a ',could i make sure that the=
 BT Module i used has really got up?

The following is the output from 'hcidump -x -V &' when trying 'sdptool bro=
wse' and 'hcitool scan':
# hcidump -x -V &
# HCI sniffer - Bluetooth packet analyzer ver 1.41
device: hci0 snap_len: 1028 filter: 0xffffffff
# sdptool browse
Inquiring ...
< HCI Command: Inquiry (0x01|0x0001) plen 5
lap 0x9e8b33 len 10 num 20
> HCI Event: Command Status (0x0f) plen 4
Inquiry (0x01|0x0001) status 0x00 ncmd 1
> HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
> HCI Event: Command Status (0x0f) plen 4
Unknown (0x00|0x0000) status 0x00 ncmd 2
# 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
> HCI Event: Command Status (0x0f) plen 4
Unknown (0x00|0x0000) status 0x00 ncmd 2

It couldn't discovery any services with 'sdptool browse' or 'hcitool scan' =
,although there's a bt headset openned.
It seems that it has a right 'hciconfig -a' output ,but still could not wor=
k.Is it a hardware problem or software problem?

Could someone give me some hints?
Any help would be much appreciated!

Best Regards
Benson


_________________________________________________________________
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 the 2008 JavaOne(SM) Conference =

Register now and save $200. Hurry, offer ends at 11:59 p.m., =

Monday, April 7! Use priority code J8TLD2. =

http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/java=
one
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2008-04-08  3:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-08  3:32 Benson Dong [this message]
2008-04-08  6:37 ` [Bluez-users] SDP couldn't discovery any device or service (stlc2500) David Rehle
2008-04-08  8:00   ` Benson Dong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BLU117-W350837E07CCCAD9D0B092E88F20@phx.gbl \
    --to=dongas86.dev@hotmail.com \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox