From: Richard Neill <rn214@richardneill.org>
To: linux-bluetooth@vger.kernel.org
Subject: Re: How to test/debug bluetooth advertising [with hciconfig]?
Date: Wed, 28 Aug 2013 15:35:22 +0100 [thread overview]
Message-ID: <521E0AAA.10309@richardneill.org> (raw)
In-Reply-To: <20130828115343.GE15469@aemeltch-MOBL1>
Dear Andrei,
Thanks for your help.
>>
>> However, before I delve into this in great detail, I wonder whether
>> I am about to "re-invent the wheel". For example, if I wanted to
>> use "ping" in a shell-script, I wouldn't normally begin by poking
>> registers in the ethernet card.
>
> Then you should not use "hcitool cmd". Better use high level API.
I'd love to use a high level API. But where can I find it? There doesn't
seem to be any documentation, or any example code for Bluetooth Low
Energy on Linux.
BTLE documentation only seem to be documented for Windows, iOS, or
Android. I'm sorry if I seem to be being dense, but while I can find
lots of references to 2007-era bluetooth tutorials, lots of information
on how wonderful BTLE is, and a lot of questions on eg stackexchange
asking *how* to do this, there doesn't seem to be any starting point for
actually doing it.
hciconfig looks to be the natural place to start (it has the commands to
enable and disable LE advertising, but appears to have omit the command
to set the advertising data itself).
Regards,
Richard
next prev parent reply other threads:[~2013-08-28 14:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 10:22 How to test/debug bluetooth advertising [with hciconfig]? Richard Neill
2013-08-28 10:39 ` Andrei Emeltchenko
2013-08-28 11:09 ` Richard Neill
2013-08-28 11:10 ` Richard Neill
2013-08-28 11:54 ` Andrei Emeltchenko
2013-08-28 14:35 ` Richard Neill [this message]
2013-08-28 12:12 ` Andrei Emeltchenko
2013-08-28 14:10 ` Claudio Takahasi
2013-08-28 14:45 ` Richard Neill
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=521E0AAA.10309@richardneill.org \
--to=rn214@richardneill.org \
--cc=linux-bluetooth@vger.kernel.org \
/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