zephyr/tests/bluetooth/tester
Luiz Augusto von Dentz d7e0294227 Bluetooth: ATT: Add incoming buffer pool
This adds a buffer for incoming prepare writes which can be
tunned using BLUETOOTH_ATT_PREPARE_COUNT, these buffers are then used in
execute write to commit the data thus making flush callback obsolete:

[bt] [DBG] bt_att_recv: (0x001159c0)Received ATT code 0x16 len 50
[bt] [DBG] att_prepare_write_req: (0x001159c0)handle 0x0022 offset 0
[bt] [DBG] prep_write_cb: (0x001159c0)handle 0x0022 offset 0
[bt] [DBG] bt_att_recv: (0x001159c0)Received ATT code 0x16 len 34
[bt] [DBG] att_prepare_write_req: (0x001159c0)handle 0x0022 offset 45
[bt] [DBG] prep_write_cb: (0x001159c0)handle 0x0022 offset 45
[bt] [DBG] bt_att_recv: (0x001159c0)Received ATT code 0x18 len 2
[bt] [DBG] att_exec_write_req: (0x001159c0)flags 0x01
[bt] [DBG] write_cb: (0x001159c0)handle 0x0022 offset 0
[bt] [DBG] write_cb: (0x001159c0)handle 0x0022 offset 45

Change-Id: Iae071d7b4b5b042285952da57e3f7a853cf58afb
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-06-06 12:28:11 +00:00
..
src Bluetooth: Take advantage of net_buf_get_timeout() 2016-06-02 10:32:29 +00:00
Makefile samples: get rid of obsolete usage of ARCH variable 2016-05-12 10:57:28 +00:00
README Bluetooth: tester: Update tester application README 2016-04-19 06:58:55 +00:00
btp_spec.txt Bluetooth: nble: Extend BTP with Identity Resolved event 2016-05-23 13:33:55 +02:00
prj.conf Bluetooth: ATT: Add incoming buffer pool 2016-06-06 12:28:11 +00:00
prj.mdef Bluetooth: Remove unnecessary #ifdef for micro/nano main function 2016-05-17 12:30:41 +03:00
prj_nble.conf drivers: bluetooth: nble: restructures Bluetooth Kconfig options 2016-03-19 00:23:11 +00:00
prj_nimble.conf Bluetooth: ATT: Add incoming buffer pool 2016-06-06 12:28:11 +00:00
testcase.ini sanitycheck: allow for more expressive filtering in testcase.ini 2016-05-04 22:57:39 +00: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.