From: Vinicius Costa Gomes <vcgomes@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Vinicius Costa Gomes <vcgomes@gmail.com>
Subject: [PATCH BlueZ v1 13/15] soletta: Add a sample flow using the heartrate node
Date: Tue, 21 Jul 2015 20:16:46 -0300 [thread overview]
Message-ID: <1437520608-22444-14-git-send-email-vcgomes@gmail.com> (raw)
In-Reply-To: <1437520608-22444-1-git-send-email-vcgomes@gmail.com>
The flow and associated conffile, defines a very simple flow using the
heartrate node.
With soletta already installed you just run it, something like this:
$ sol-fbp-runner heartrate.fbp
It will look for the sol-flow.conf (which would define options for the
nodes) in the current directory.
---
peripheral/soletta/heartrate.fbp | 1 +
peripheral/soletta/sol-flow.json | 8 ++++++++
2 files changed, 9 insertions(+)
create mode 100644 peripheral/soletta/heartrate.fbp
create mode 100644 peripheral/soletta/sol-flow.json
diff --git a/peripheral/soletta/heartrate.fbp b/peripheral/soletta/heartrate.fbp
new file mode 100644
index 0000000..63185c4
--- /dev/null
+++ b/peripheral/soletta/heartrate.fbp
@@ -0,0 +1 @@
+Timer(timer:interval=1000) OUT -> IN Heartrate(heartrate)
diff --git a/peripheral/soletta/sol-flow.json b/peripheral/soletta/sol-flow.json
new file mode 100644
index 0000000..c1f8fca
--- /dev/null
+++ b/peripheral/soletta/sol-flow.json
@@ -0,0 +1,8 @@
+{
+ "nodetypes": [
+ {
+ "name": "Heartrate",
+ "type": "heartrate"
+ }
+ ]
+}
--
2.4.6
next prev parent reply other threads:[~2015-07-21 23:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 23:16 [PATCH BlueZ v1 00/15] Introducing Soletta peripheral node-type Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 01/15] build: Add configure-time checks for soletta Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 02/15] shared: Add a mainloop implementation using soletta Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 03/15] peripheral/gatt: Fix usage of mainloop_ functions Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 04/15] peripheral/gatt: Add a way to external services to register services Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 05/15] peripheral/gap: Fix missing includes Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 06/15] peripheral/gap: Init the gatt_server Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 07/15] peripheral: Disable support for static random addresses Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 08/15] peripheral/gap: Set the discoverable flag in the advertising Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 09/15] peripheral/gatt: Use LOW security level Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 10/15] soletta/heartrate: Add a node-type for the Heartrate profile Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 11/15] .gitignore: Ignore soletta generated files Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 12/15] build: Add heartrate soletta node type to the build system Vinicius Costa Gomes
2015-07-21 23:16 ` Vinicius Costa Gomes [this message]
2015-07-21 23:16 ` [PATCH BlueZ v1 14/15] peripheral: Add a README for the Soletta support Vinicius Costa Gomes
2015-07-21 23:16 ` [PATCH BlueZ v1 15/15] peripheral: Add a Makefile for building a binary using soletta Vinicius Costa Gomes
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=1437520608-22444-14-git-send-email-vcgomes@gmail.com \
--to=vcgomes@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).