zephyr

History

Anas Nashif a9e879e273 logging: move sys_log to subsys/logging Move logging out of misc/ to its own subsystem. Anything related to logging and any new logging features or backends could be added here instead of the generic location in misc/ which is overcrowded with options that are not related to eachother. Jira: ZEP-1467 Change-Id: If6a3ea625c3a3562a7a61a0ba5fd7e6ca75518ba Signed-off-by: Anas Nashif <anas.nashif@intel.com>		2016-12-19 19:58:39 +00:00
..
src	logging: move sys_log to subsys/logging	2016-12-19 19:58:39 +00:00
Makefile	Bluetooth: tests: Fix Makefiles comments	2016-11-18 07:47:50 +02:00
README	Bluetooth: tester: Set Zephyr-based BLE configuration as default	2016-11-04 22:06:31 +02:00
btp_spec.txt	Bluetooth: tester: Rework discovery procedure	2016-10-16 09:01:28 +03:00
default.conf	Bluetooth: Kconfig: Restructure for a more logical hierarchy	2016-11-11 07:59:15 +02:00
nble.conf	Bluetooth: Kconfig: Restructure for a more logical hierarchy	2016-11-11 07:59:15 +02:00
nimble.conf	Bluetooth: Kconfig: Restructure for a more logical hierarchy	2016-11-11 07:59:15 +02:00
qemu.conf	Bluetooth: Kconfig: Restructure for a more logical hierarchy	2016-11-11 07:59:15 +02:00
testcase.ini	Bluetooth: tester: Fix configuration file name	2016-11-04 22:06:31 +02:00

README

Title: Bluetooth tester application

Description:

Tester application uses binary protocol to control Zephyr stack and is aimed at
automated testing. It requires two serial ports to operate.
The first serial is used by Bluetooth Testing Protocol (BTP) to drive Bluetooth
stack. BTP commands and events are received and buffered for further processing
over the same serial.

--------------------------------------------------------------------------------

Supported Profiles:

GAP, GATT, SM
--------------------------------------------------------------------------------

Building and running on QEMU:

QEMU should have connection with the external host Bluetooth hardware.
The btproxy tool from BlueZ can be used to give access to a Bluetooth controller
attached to the Linux host OS:

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

/tmp/bt-server-bredr option is already set in Makefile through QEMU_EXTRA_FLAGS.

To build tester application for QEMU:

$ make pristine && make BOARD=qemu_cortex_m3 CONF_FILE=qemu.conf qemu

Note: Target board have to support enough UARTs for BTP and controller.
We recommend using qemu_cortex_m3.

'bt-stack-tester' UNIX socket (previously set in Makefile) can be used for now
to control tester application.
--------------------------------------------------------------------------------

Building and running on Arduino 101:

Arduino 101 is equipped with Nordic nRF51 Bluetooth LE controller.
Please refer to the Zephyr Project wikis [1] to see how to build and flash the
controller with the HCI Bluetooth LE firmware.

Next, build and flash tester application:

$ make pristine && make flash

While running tester application on Arduino 101, serial converter, typically
UART <-> USB is required by BTP to operate. Connect Arduino 101 Tx and Rx lines
(0 and 1 ports on Arduino 101 board) through the UART converter to the host
USB port.

Use serial client, e.g. PUTTY to communicate over the serial port
(typically /dev/ttyUSBx) with the tester using BTP.

[1] https://wiki.zephyrproject.org/view/Arduino_101#Bluetooth_firmware_for_the_Arduino_101