Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] RFCOMM Connect problem, need help to understand HCIDUMP output
Date: Thu, 14 Apr 2005 10:29:49 +0200	[thread overview]
Message-ID: <1113467389.16014.19.camel@pegasus> (raw)
In-Reply-To: <200504140608.19450.magnus.larsson@callista.se>

Hi Magnus,

> Can someone help me to describe what the HCIDUMP in the end of this message 
> says is wrong?
> 
> Does anyone have a URL to some doc that explain the HCIDUMP output?

install the latest hcidump and use the options "-X -V" which give you a
better hex/ASCII dump and the verbose decoding.

> I think the following part is of interest (see below for the full hcidump - 
> output):
> 
> > ACL data: handle 0x002e flags 0x02 dlen 8
>     L2CAP(d): cid 0x0040 len 4 [psm 3]
>       RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73
> < ACL data: handle 0x002e flags 0x02 dlen 8
>     L2CAP(d): cid 0x0048 len 4 [psm 3]
>       RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd


The more important one is the data packet before it. It tells you for
what command the DM is send:

< ACL data: handle 0x002e flags 0x02 dlen 8
    L2CAP(d): cid 0x004a len 4 [psm 3]
      RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59

This means that you tried to open RFCOMM channel 1 and with the DM the
phone tells you that it won't create it. So you better check your phone
why it is not accepting a connection on this channel.

The DISC is not for channel 1 (DLCI 2). It is for DLCI 0 which is the
signal channel.

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      parent reply	other threads:[~2005-04-14  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-09 22:32 [Bluez-users] RFCOMM Connect problem Magnus Larsson
2005-04-14  4:08 ` [Bluez-users] RFCOMM Connect problem, need help to understand HCIDUMP output Magnus Larsson
2005-04-14  8:18   ` Marco Trudel
2005-04-14  8:29   ` Marcel Holtmann [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=1113467389.16014.19.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