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