1# BTstack Port for POSIX Systems with Zephyr-based Controller 2 3The main difference to the regular posix-h4 port is that that the Zephyr Controller uses 1000000 as baud rate. 4In addition, the port defaults to use the fixed static address stored during production. 5 6## Prepare Zephyr Controller 7 8Please follow [this](https://devzone.nordicsemi.com/blogs/1059/nrf5x-support-within-the-zephyr-project-rtos/) blog post about how to compile and flash `samples/bluetooth/hci_uart` to a connected nRF5 dev kit. 9 10In 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: 11 12 * Install [J-Link Software and documentation pack](https://www.segger.com/jlink-software.html). 13 * Get nrfjprog as part of the [nRFx-Command-Line-Tools](http://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF52-DK). Click on Downloads tab on the top and look for your OS. 14 * [Checkout Zephyr and install toolchain](https://www.zephyrproject.org/doc/getting_started/getting_started.html). We recommend using the [arm-non-eabi gcc binaries](https://launchpad.net/gcc-arm-embedded) instead of compiling it yourself. At least on OS X, this failed for us. 15 16 * In *samples/bluetooth/hci_uart*, compile the firmware for nRF52 Dev Kit 17 18 $ make BOARD=nrf52_pca10040 19 20 * Upload the firmware 21 22 $ make flash 23 24 * For the nRF51 Dev Kit, use `make BOARD=nrf51_pca10028`. 25 26## Configure serial port 27 28To set the serial port of your Zephyr Controller, you can either update config.device_name in main.c or 29always start the examples with the `-u /path/to/serialport` option. 30 31## Compile Examples 32 33 $ make 34 35## Run example 36 37Just run any of the created binaries, e.g. 38 39 $ ./le_counter 40 41The packet log will be written to /tmp/hci_dump.pklg 42 43