1# BTstack port for Zephyr Controller with HCI UART Firmware Connectected To POSIX System 2 3The main difference to the regular posix-h4 port is that that the Zephyr Contoller 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 correct `-u COMx` option. 30 31## Toolchain 32 33The port requires a Unix-like toolchain. We successfully used [mingw-w64](https://mingw-w64.org/doku.php) to compile and run the examples. mingw64-w64 is based on [MinGW](https://en.wikipedia.org/wiki/MinGW), which '...provides a complete Open Source programming tool set which is suitable for the development of native MS-Windows applications, and which do not depend on any 3rd-party C-Runtime DLLs.' 34 35We've used the Msys2 package available from the [downloads page](https://mingw-w64.org/doku.php/download) on Windows 10, 64-bit and use the MSYS2 MinGW 64-bit start menu item to compile 64-bit binaries. 36 37In the MSYS2 shell, you can install everything with pacman: 38 39 $ pacman -S git 40 $ pacman -S make 41 $ pacman -S mingw-w64-x86_64-toolchain 42 $ pacman -S python 43 $ pacman -S winpty 44 45## Compile Examples 46 47 $ make 48 49Note: When compiling with msys2-32 bit and/or the 32-bit toolchain, compilation fails 50as `conio.h` seems to be mission. Please use msys2-64 bit with the 64-bit toolchain for now. 51 52## Run example 53 54Just run any of the created binaries, e.g. 55 56 $ ./le_counter 57 58The packet log will be written to /tmp/hci_dump.pklg 59 60