From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Cc: Vicky Sweetser <vicky.sweetser@smartsensorsystems.com>,
Jay Johannes <jay.johannes@smartsensorsystems.com>,
Les Hammer <les.hammer@smartsensorsystems.com>
Subject: Re: [Bluez-devel] Question about BlueZ and RFCOMM
Date: Sun, 03 Dec 2006 14:54:06 +0100 [thread overview]
Message-ID: <1165154046.19590.38.camel@localhost> (raw)
In-Reply-To: <001901c71318$6913da00$0600a8c0@PC581820463305>
Hi Dave,
> I have a question about using RFCOMM on BlueZ. Here is our system:
>
>
> Linux system with <-----over the air-------> CSR BC03-MM chip and
> CSR-based USB dongle the STMicroelectronics
> STR710 ARM
> Microprocessor
> ("micro")
>
>
> We want to use the BlueZ RFCOMM library. On the microprocessor side, I'm
> using the serial
> port of the CSR Bluetooth chip so I am able to monitor the serial data
> stream between the
> CSR Bluetooth chip and the microprocessor ("micro").
>
> Most of the RFCOMM communication works fine. On the micro side, I observe
> that the
> parameter negotiation happens OK and the RFCOMM connection is established.
> However,
> the data I try to send from the Linux system is never received by the micro.
> What
> happens instead is that the micro receives these commands from the Bluetooth
> chip
> (these are in CSR's format):
> RFC_CONTROL_IND
> RFC_RELEASE_IND
> RFC_CLOSE_IND
> DM_ACL_CLOSED_IND
>
> I also observe that the Linux system, while connection is being established,
> is sending
> flow control messages (3, in my case) to the micro. These are with a credit
> field of
> 4, 5 and 6 for the 3 flow control messages.
>
> Now to my question: Does the micro need to respond to these flow control
> messages in some
> manner to maintain the RFCOMM connection? Currently the
> micro doesn't
> respond to the flow control messages.
>
> If it is OK for the micro to not respond to the flow control messages, can
> someone help me
> understand what else might be causing the RFCOMM data to not be sent from
> the Linxu system
> and what might be causing the RFCOMM connection to be closed down?
these question should be towards CSR, because you have problems with
their embedded RFCOMM stack. I have not enough insights to answer this
properly.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-12-03 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 18:09 [Bluez-devel] Question about BlueZ and RFCOMM Dave Sweetser
2006-12-03 13: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=1165154046.19590.38.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jay.johannes@smartsensorsystems.com \
--cc=les.hammer@smartsensorsystems.com \
--cc=vicky.sweetser@smartsensorsystems.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.