Linux bluetooth development
 help / color / mirror / Atom feed
From: giochi <giochi@telvia.it>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] rfcomm problem
Date: Thu, 22 Apr 2004 23:38:58 +0200	[thread overview]
Message-ID: <20040422233858.1bb6a766@bizio.slackware-italia.com> (raw)

Hello,

this is my first experience with bluetooth. I've followed this link http://www.linuxquestions.org/questions/showthread.php?s=&postid=841157#post
and many others for setup it.
Alls work fine till the rfcomm initialization:

root@bizio:~# rfcomm bind 0 00:0A:28:B1:9C:6E 8
Wrong number of parameters.
root@bizio:~# rfcomm bind 0 00:0A:28:B1:9C:6E 9
Wrong number of parameters.
root@bizio:~# rfcomm bind 0                    
Device USSP not registered: No such device

root@bizio:~# hcitool inq
Inquiring ...
        00:0A:28:B1:9C:6E       clock offset: 0x3ea0    class: 0x000100
root@bizio:~# hcitool scann
Scanning ...
        00:0A:28:B1:9C:6E       Motorola Phone

root@bizio:~# sdptool browse 00:0A:28:B1:9C:6E
Browsing 00:0A:28:B1:9C:6E ...
Service RecHandle: 0x0
Service Class ID List:
  "SDP Server" (0x1000)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "SDP" (0x0001)
Profile Descriptor List:
  "" (0x1000)
    Version: 0x0100

...
Service Name: OBEX Object Push
Service Description: OBEX Object Push
Service Provider: Motorola
Service RecHandle: 0x10008
Service Class ID List:
  "OBEX Object Push" (0x1105)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 8
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
  code_ISO639: 0x6672
  encoding:    0x6a
  base_offset: 0xd800
  code_ISO639: 0x6465
  encoding:    0x6a
  base_offset: 0xd803
  code_ISO639: 0x6974
  encoding:    0x6a
  base_offset: 0xd806
  code_ISO639: 0x6573
  encoding:    0x6a
  base_offset: 0xd809
  code_ISO639: 0x6e6c
  encoding:    0x6a
  base_offset: 0xd80c
  code_ISO639: 0x7472
  encoding:    0x6a
  base_offset: 0xd80f
  code_ISO639: 0x7074Profile Descriptor List:
  "OBEX Object Push" (0x1105)
    Version: 0x0100

Service Name: OBEX file transfer
Service Description: OBEX file transfer
Service Provider: Motorola
Service RecHandle: 0x10009
Service Class ID List:
  "OBEX File Transfer" (0x1106)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 9
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x656e
  encoding:    0x6a
  base_offset: 0x100
  code_ISO639: 0x6672
  encoding:    0x6a
  base_offset: 0xd800
  code_ISO639: 0x6465
  encoding:    0x6a
  base_offset: 0xd803
  code_ISO639: 0x6974
  encoding:    0x6a
  base_offset: 0xd806
  code_ISO639: 0x6573
  encoding:    0x6a
  base_offset: 0xd809
  code_ISO639: 0x6e6c
  encoding:    0x6a
  base_offset: 0xd80c
  code_ISO639: 0x7472
  encoding:    0x6a
  base_offset: 0xd812
  encoding:    0x6a
  base_offset: 0xd80f
  code_ISO639: 0x7074
  encoding:    0x6a
  base_offset: 0xd812
Profile Descriptor List:
  "OBEX File Transfer" (0x1106)
    Version: 0x0100

So, as appears 8 and 9 channels are designed for OBEX.
When I found these channels I type:
sdptool add --channel=9 OPUSH
sdptool add --channel=8 OPUSH

Here's my /etc/bluetooth/rfcomm.conf

#
# RFCOMM configuration file.
#
# $Id: rfcomm.conf,v 1.1 2002/10/07 05:58:18 maxk Exp $
#
#
rfcomm0 {
        # Automatically bind the device at startup
        bind no;

        # Bluetooth address of the device
        device 00:0A:28:B1:9C:6E;

        # RFCOMM channel for the connection
        channel 8;

        # Description of the connection
        comment "ObexBT";
} 

I use a sitecom usb dongle and motorola v525
Any help would be appreciated.
Br,
Fab


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-04-22 21:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 21:38 giochi [this message]
2004-04-23  5:15 ` [Bluez-users] rfcomm problem Marcel Holtmann
2004-04-26 20:55   ` giochi
2004-04-26 23:44     ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2005-03-25  1:37 [Bluez-users] RFCOMM Problem Jin Pu
2005-03-25  6:40 ` Michal Semler
2005-04-08  2:36 [Bluez-users] RFCOMM problem Jin Pu
2005-04-08  4:15 ` Marcel Holtmann
2006-02-26 13:53 [Bluez-users] RFCOMM PROBLEM Zhixiang Deng

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=20040422233858.1bb6a766@bizio.slackware-italia.com \
    --to=giochi@telvia.it \
    --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