From: Andrew Kohlsmith <aklists@mixdown.ca>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BlueZ protocol stack on microcontroller
Date: Fri, 7 Dec 2007 09:37:20 -0500 [thread overview]
Message-ID: <200712070937.20497.aklists@mixdown.ca> (raw)
In-Reply-To: <20071207092240.jtm1je3tcc4cwo40@www.nexusmail.uwaterloo.ca>
On Friday 07 December 2007 09:22:40 gpolack@engmail.uwaterloo.ca wrote:
> I'm new to using Bluetooth modules and would appreciate some guidance.
> I'm connecting a Bluetooth module that has a UART interface to a
> microcontroller, and I wish to use the BlueZ protocol stack to talk to
> the module but I know nothing about how the protocol works. Can it be
> configured to talk via UART to the module? Also, what is the minimal
> set of functions one would need for simple data transfer between two
> Bluetooth modules, no stereo audio, or other fancy stuff? My questions
> will get more specific as I start understanding how this all works.
You want to use the hciattach. I have used this on one of my MCF5282 designs
when talking to A7eng's bluetooth modules.
hciattach creates an hci device and brokers all requests over the UART to the
bluetooth module. From that point on you use everyday standard utilities to
manipulate the hci device that was created.
-A.
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-12-07 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 14:22 [Bluez-devel] BlueZ protocol stack on microcontroller gpolack
2007-12-07 14:37 ` Andrew Kohlsmith [this message]
2007-12-07 14:40 ` Peter Wippich
2007-12-08 12:40 ` 迎宾 高
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=200712070937.20497.aklists@mixdown.ca \
--to=aklists@mixdown.ca \
--cc=bluez-devel@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