BTstack port for Zephyr Controller with HCI UART Firmware Connectected To POSIX System
The main difference to the regular posix-h4 port is that that the Zephyr Contoller uses 1000000 as baud rate. In addition, the port defaults to use the fixed static address stored during production.
Prepare Zephyr Controller
Please follow this blog post about how to compile and flash
samples/bluetooth/hci_uart to a connected nRF5 dev kit.
In short: you need to install an arm-none-eabi gcc toolchain and the nRF5x Command Line Tools incl. the J-Link drivers, checkout the Zephyr project, and flash an example project onto the chipset:
Get nrfjprog as part of the nRFx-Command-Line-Tools. Click on Downloads tab on the top and look for your OS.
In samples/bluetooth/hci_uart, compile the firmware for nRF52 Dev Kit
$ make BOARD=nrf52_pca10040
Upload the firmware
$ make flash
For the nRF51 Dev Kit, use
Configure serial port
To set the serial port of your Zephyr Controller, you can either update config.device_name in main.c or
always start the examples with the
-u /path/to/serialport option.
Just run any of the created binaries, e.g.
The packet log will be written to /tmp/hci_dump.pklg