xref: /btstack/port/posix-h4-zephyr/README.md (revision 410be61aeb0ccba1bb545e07233c7c9fddf9ee85)
1*410be61aSMatthias Ringwald# BTstack port for Zephyr Controller with HCI UART Firmware Connectected To POSIX System
26807484cSMatthias Ringwald
3*410be61aSMatthias RingwaldThe main difference to the regular posix-h4 port is that that the Zephyr Contoller uses 1000000 as baud rate.
4*410be61aSMatthias RingwaldIn addition, the port defaults to use the fixed static address stored during production.
56807484cSMatthias Ringwald
6*410be61aSMatthias Ringwald## Prepare Zephyr Controller
7*410be61aSMatthias Ringwald
8*410be61aSMatthias RingwaldPlease 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*410be61aSMatthias Ringwald
10*410be61aSMatthias RingwaldIn 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*410be61aSMatthias Ringwald
12*410be61aSMatthias Ringwald  * Install [J-Link Software and documentation pack](https://www.segger.com/jlink-software.html).
13*410be61aSMatthias Ringwald  * 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*410be61aSMatthias Ringwald  * [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*410be61aSMatthias Ringwald
16*410be61aSMatthias Ringwald  * In *samples/bluetooth/hci_uart*, compile the firmware for nRF52 Dev Kit
17*410be61aSMatthias Ringwald
18*410be61aSMatthias Ringwald      $ make BOARD=nrf52_pca10040
19*410be61aSMatthias Ringwald
20*410be61aSMatthias Ringwald   * Upload the firmware
21*410be61aSMatthias Ringwald
22*410be61aSMatthias Ringwald      $ make flash
23*410be61aSMatthias Ringwald
24*410be61aSMatthias Ringwald   * For the nRF51 Dev Kit, use `make BOARD=nrf51_pca10028`.
25*410be61aSMatthias Ringwald
26*410be61aSMatthias Ringwald## Configure serial port
27*410be61aSMatthias Ringwald
28*410be61aSMatthias RingwaldTo set the serial port of your Zephyr Controller, you can either update config.device_name in main.c or
29*410be61aSMatthias Ringwaldalways start the examples with the `-u /path/to/serialport` option.
30*410be61aSMatthias Ringwald
31*410be61aSMatthias Ringwald## Compile Examples
326807484cSMatthias Ringwald
336807484cSMatthias Ringwald    $ make
346807484cSMatthias Ringwald
35*410be61aSMatthias Ringwald## Run example
366807484cSMatthias Ringwald
37*410be61aSMatthias RingwaldJust run any of the created binaries, e.g.
38*410be61aSMatthias Ringwald
39*410be61aSMatthias Ringwald    $ ./le_counter
40*410be61aSMatthias Ringwald
41*410be61aSMatthias RingwaldThe packet log will be written to /tmp/hci_dump.pklg
42*410be61aSMatthias Ringwald
43