zephyr

History

Anas Nashif 10bb38c186 Use SoC instead of platform. Change terminology and use SoC instead of platform. An SoC provides features and default configurations available with an SoC. A board implements the SoC and adds more features and IP block specific to the board to extend the SoC functionality such as sensors and debugging features. Change-Id: I15e8d78a6d4ecd5cfb3bc25ced9ba77e5ea1122f Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2016-02-05 20:25:11 -05:00
..
beacon	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
central	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
central_hr	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
init	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
init_h5	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
ipsp	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
peripheral	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
peripheral_dis	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
peripheral_sc_only	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
shell	Use SoC instead of platform.	2016-02-05 20:25:11 -05:00
test_bluetooth	Bluetooth: Convert driver header info to hidden Kconfig options	2016-02-05 20:24:45 -05:00
tester	rename basic_atom with minnowboard	2016-02-05 20:25:11 -05:00
README	Bluetooth: Fix HCI driver Kconfig references in samples	2016-02-05 20:25:03 -05:00

README

Bluetooth subsystem

= Building =

Build samples

$ make -C samples/bluetooth/<app>

= Bluetooth Sample application =

Host Bluetooth controller is connected to the second qemu serial line
through a UNIX socket (qemu option -serial unix:/tmp/bt-server-bredr).
This option is already added to qemu through QEMU_EXTRA_FLAGS in Makefile.

On the host side BlueZ allows to "connect" Bluetooth controller through
a so-called user channel. Use the btproxy tool for that:

$ sudo tools/btproxy -u
Listening on /tmp/bt-server-bredr

Note that before calling btproxy make sure that Bluetooth controller is down.

Now running qemu result connecting second serial line to 'bt-server-bredr'
UNIX socket. When Bluetooth (CONFIG_BLUETOOTH) and Bluetooth HCI UART driver
(CONFIG_BLUETOOTH_H4) are enabled, Bluetooth driver registers to the system.
From now on Bluetooth might be used by the application. To run application in
the qemu run:

$ make qemu

== Bluetooth IPSP application ==

To test IPSP please take a look at samples/net/README, in addition to running
echo-client it is necessary to enable 6LowPAN module in Linux with the
following commands:

$ modprobe bluetooth_6lowpan
$ echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable

Then to connect:

echo "connect <bdaddr> <type>" > /sys/kernel/debug/bluetooth/6lowpan_control

Once connected a dedicated interface will be created, usually bt0, which can
then be used as following:

$ echo-client -i bt0 <ip>

= Bluetooth sanity check =

There is smoke test application in nanokernel and microkernel test
directories which gets run in sanity check script:

$ scripts/sanity_chk/sanity_chk [-P <platform>]

For quick regression test use bt_regression, it only check Bluetooth test

$ samples/bluetooth/bt_regression.sh