From: Marcel Holtmann <marcel@holtmann.org>
To: lucky Dimas <lucky_d80@hotmail.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Packet Order \ L2CAP Connection
Date: Wed, 31 Mar 2004 00:54:18 +0200 [thread overview]
Message-ID: <1080687258.2773.35.camel@pegasus> (raw)
In-Reply-To: <Sea2-F399C1opccV19X00042b44@hotmail.com>
Hi Lucky,
> First I have to apologize if this message is not directly BlueZ related. I
> am using my own stack on an embedded platform, but the BlueZ stack was one
> of its models.
> Anyway, I am trying to connect to my Nokia 6310i over my Embedded platform
> and so far I have managed to make an inquiry, and find my cell
> phone(Allthough I had to use the max Page timeout!! Is there something wrong
> with the Nokia Bluetooth implementation, or is it what I fear: EM problems
> with my PCB?!)
> Now I am trying to create a RFCOMM connection which needs an L2CAP Channel
> to run over it. Well here is where the troubles starts. Following a log of
> the packets after the BB_Connection:
>
> Baseband Connection Table:
> nr, handle, numOfChan, state, bd_addr
> 0, 0x 28, 0, 4, [00:60:57:23:3b:e0].OPEN
> Sending Connect Request:
> ***T:2
> ** T: 28 **
> ** T: 20 **
> ** T: c **
> ** T: 0 **
> ** T: 8 **
> ** T: 0 **
> ** T: 1 **
> ** T: 0 **
> ** T: 2 **
> ** T: 2 **
> ** T: 4 **
> ** T: 0 **
> ** T: 3 **
> ** T: 0 **
> ** T: 40 **
> ** T: 0 **max chang
>
> ** R: 4[1]**
> ** R: 13
> ** R: 5
> ** R: 1
> ** R: 28
> ** R: 0
> ** R: 1
> ** R: 0
> # compl.
>
> ** R: 4[1]**
> ** R: d
> ** R: 15
> ** R: 0
> ** R: 28
> ** R: 0
> ** R: 0
> ** R: 1
> ** R: 0
> ** R: 0
> ** R: 0
> ** R: 0
> ** R: 0
> ** R: 0
> ** R: 0
> ** R: 0
> ** R: ff
> ** R: ff
> ** R: ff
> ** R: ff
> ** R: ff
> ** R: ff
> ** R: ff
> ** R: ff
>
> ** R: 2
> ** R: 28
> ** R: 20
> ** R: 10
> ** R: 0
> ** R: c
> ** R: 0
> ** R: 1
> ** R: 0
> ** R: 3
> ** R: 2
> ** R: 8
> ** R: 0
> ** R: 40
> ** R: 0
> ** R: 40
> ** R: 0
> ** R: 0
> ** R: 0
> ** R: 0
> ** R: 0
> QOS Compl.
> W4_ACL_HDR
>
>
> While I Do realize that my UART (Duart to be exact)implementation might
> contain bugs, I am not quite sure how to interpret this packet order, or
> what to await. Has someone a Packet sequence for a succesfull RFCOMM
> connection available? What is my stack supposed to sent after the QOS Setup,
> is there some kind of diagram available? I checked the specs, looked in
> "Connect without Cables", and "Das Bluetooth handbuch", but I couldn't find
> anything...
I don't even understand your log output and it will take me too much
time to think about it. If you want a sample packet sequence you can use
hcidump in raw mode to see what is going on. But this will be HCI layer
and not baseband.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-03-30 22:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 19:13 [Bluez-users] Packet Order \ L2CAP Connection lucky Dimas
2004-03-30 22:54 ` 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=1080687258.2773.35.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=lucky_d80@hotmail.com \
/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