Linux bluetooth development
 help / color / mirror / Atom feed
From: Erwin Authried <eauth@softsys.co.at>
To: "bluez-users@lists.sourceforge.net" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ on ETRAX 100LX devboard 82+
Date: Mon, 13 Jun 2005 10:32:35 +0200	[thread overview]
Message-ID: <1118651555.25847.19.camel@justakiss> (raw)
In-Reply-To: <20050610050635.82925.qmail@web52804.mail.yahoo.com>

Am Fre, den 10.06.2005 schrieb Naved Aziz um 7:06:
> Hi,
> 
> Basically, these are the steps that I am taking to set
> up an SP connection between the Axis board and the
> Nokia 6600:
> 
> (1) hcid
> (2) sdpd
> (3) hciconfig hci0 up #set up the bluetooth dongle
> (4) hcitool scan  #spot the phone, get the BD address
> (5) sdptool browse <BD address> #see services and 
>     their corrresponding channels
> (6) rfcomm connect /dev/rfcomm0 <BD address> <channel>
>     #where, if channel 2 is the one on nokia 6600    
>     providing serial port service, I put 2 for
> channel.   
>     The /dev/rfcomm0 is already created prior to 
>     flashing the image onto the board as follows:
>     mknod -m 0666 /dev/rfcomm0 c 216 0 
> 
> At this point, the phone gives a prompt, asking for a
> pin number.  The value in /etc/bluetooth/pin is 1234,
> and I have changed the pin_helper in hcid.conf to
> refer to a script file called qpin that looks like
> this:
> 
> #!/bin/sh
> #echo "PIN:1234"
> 
> This script file that I have created to work with the
> pin_helper is stored in the /tmp directory, since this
> is the only place where I am allowed to create any
> files, etc once an image has been downloaded onto the
> board. 
> 
> After I type in the pin on the Nokia 6600, there is a
> moment of wait, and then, the phone says "unable to
> connect", and the board says "can't create socket:
> resource temporarily unavailable".
> 
> You mentioned that the rfcomm utility creates a device
> that causes problems on some systems; how to get
> around this?
> 
> Thanks in advance for your help.
> 
> Naved
> 
are you sure that your board is able to save the link key? It is
normally stored in /etc/bluetooth/link_key. If your /etc is r/o, you
must make a symlink into a writeable directory.

Regards,
Erwin




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      parent reply	other threads:[~2005-06-13  8:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 11:12 [Bluez-users] BlueZ on ETRAX 100LX devboard 82+ Naved Aziz
2005-06-09 11:43 ` Marco Trudel
2005-06-09 13:57   ` Naved Aziz
2005-06-09 15:26     ` Marco Trudel
2005-06-10  5:06       ` Naved Aziz
2005-06-12  9:51         ` Marco Trudel
2005-06-14 14:04           ` Naved Aziz
2005-06-14 18:26             ` Marco Trudel
2005-06-26 10:40               ` Naved Aziz
2005-06-26 13:36                 ` Naved Aziz
2005-06-13  8:32         ` Erwin Authried [this message]

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=1118651555.25847.19.camel@justakiss \
    --to=eauth@softsys.co.at \
    --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