zephyr/tests/bluetooth/tester
Johan Hedberg 900fbc20ba boards: x86: Don't default to 'y' with NRF51_PM and WAIT_NOP
These options were only needed for a MyNewt-based nRF51 firmware on
these boards (the MyNewt BLE stack is called Nimble, hence the
prj_nimble.conf sample config files). With a Zephyr-based nRF51
firmware these options are no-longer needed, so it's not appropriate
to have them default to enabled. Instead, if they are needed, require
the app-specific configuration to enable them.

Change-Id: Iefbee4d97590af4e11bcedea05fe61f32a147b83
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-11-01 19:37:26 +00:00
..
src Bluetooth: GATT: Pass CCC attribute to changed callback 2016-10-21 07:47:31 +03:00
Makefile Bluetooth: Use unified kernel build for tests and samples 2016-10-28 08:30:57 +02:00
README
btp_spec.txt Bluetooth: tester: Rework discovery procedure 2016-10-16 09:01:28 +03:00
prj.conf Bluetooth: tester: Add L2CAP init method 2016-09-07 09:08:47 +00:00
prj_nble.conf Bluetooth: samples: Remove redundant CONFIG_ARC_INIT=n 2016-10-28 08:09:08 +03:00
prj_nimble.conf boards: x86: Don't default to 'y' with NRF51_PM and WAIT_NOP 2016-11-01 19:37:26 +00:00
testcase.ini Bluetooth: Use unified kernel build for tests and samples 2016-10-28 08:30:57 +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 qemu

'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 chip, thus nble
driver has to be build.
For building tester application for Arduino 101 board with Nordic Bluetooth Low
Energy stack (NBLE) use prj_nble.conf:

$ make pristine && make CONF_FILE=prj_nble.conf BOARD=arduino_101 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.