Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Something strange with minicom
Date: Fri, 29 Apr 2005 19:16:15 +0200	[thread overview]
Message-ID: <1114794975.8836.106.camel@pegasus> (raw)
In-Reply-To: <200504291833.26111@ByZsA>

Hi Attila,

> I'm trying to connect to my new mobile phone via a usb bluetooth 
> dongle. I solved many problems (and learned a lot) but I'm 
> stuck. I downloaded and installed the latest bluez stuff. 
> (Version 2.16 at this time) It seems to work but I still can not 
> comminicate with my phone. I can start everything and could pair 
> my phone with my PC. When I start minicom to test the 
> connection, I can type anything but phone answers with "error". 
> I tried it with hyperterminal under windows and it works. So we 
> shouldn't talk about hardware problems.
> 
> Here is my hciconfig -a output:
> hci0:   Type: USB
>         BD Address: 00:09:DD:10:6D:32 ACL MTU: 192:8 SCO MTU: 
> 64:8
>         UP RUNNING PSCAN ISCAN AUTH ENCRYPT
>         RX bytes:1990 acl:51 sco:0 events:91 errors:0
>         TX bytes:1174 acl:49 sco:0 commands:28 errors:0
>         Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: RSWITCH HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT
>         Name: 'Cornflower'
>         Class: 0x3e0100
>         Service Classes: Networking, Rendering, Capturing
>         Device Class: Computer, Uncategorized
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x460 LMP Ver: 1.1 (0x1) LMP 
> Subver: 0x460
>         Manufacturer: Cambridge Silicon Radio (10)

are you sure that you wanna be in security mode 3. Using auth and
encrypt is not advisable.

> And here is the "hcidump -x" result when I enter an "atz" modem 
> command in minicom:
> HCI sniffer - Bluetooth packet analyzer ver 1.20
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < ACL data: handle 41 flags 0x02 dlen 9
>     L2CAP(d): cid 0x0041 len 5 [psm 0]
>       0B EF 03 61 9A

Make sure that you grep the initial HCI and L2CAP connection setup,
because otherwise hcidump is not able to decode RFCOMM. Or specific the
--psm=3 option on the command line.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-04-29 17:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-29 16:33 [Bluez-users] Something strange with minicom Attila Zsigmond
2005-04-29 17:16 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-29 22:03 Attila Zsigmond
2005-04-29 23:56 ` Marcel Holtmann
2005-04-30 18:29   ` Attila Zsigmond
2005-04-30 19:38     ` Marcel Holtmann
2005-05-02 10:22       ` Attila Zsigmond
2005-05-02 10:37         ` Marcel Holtmann
2005-05-02 12:02           ` Attila Zsigmond
2005-06-28 16:16           ` Attila Zsigmond

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=1114794975.8836.106.camel@pegasus \
    --to=marcel@holtmann.org \
    --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