mirror/btstack
1
0
Fork 0
mirror of https://github.com/bluekitchen/btstack.git synced 2025-03-30 07:21:20 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: move parts from quick start into port readme file for pic32 and windows-winusb

Browse Source
This commit is contained in:
Matthias Ringwald 2017-12-22 23:54:37 +01:00
parent b379648ac7
commit a1a1af7129
2 changed files with 36 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
port/pic32-harmony/README.md
View File

@ -2,6 +2,17 @@
Status: All examples working, polling UART driver. Tested on Bluetooth Audio Development Kit only. Created with Harmony v1.07, does not compile with new v2.x versions.
## Hardware
The PIC32 Bluetooth Audio Development Kit comes with the CSR8811-based
BTM805 Bluetooth module. In the port, the UART on the DAC daughter board
was used for the debug output. Please remove the DAC board and connect a
3.3V USB-2-UART converter to GND and TX to get the debug output.
## Software
Microchip MPLAB X IDE and the MPLAB XC32 compiler needs to be installed.
## Setup
- Place BTstack tree into harmony/framework folder.
@ -9,8 +20,14 @@ Status: All examples working, polling UART driver. Tested on Bluetooth Audio Dev
## Usage
The examples can be opened and compiled in Microchip MPLABX.
The examples can be opened and compiled in Microchip MPLAB X IDE or from the command line using the Makefile generated by it.
### Modifications to the GATT Database
After changing the GATT definition in $example.gatt, please run ./update_gatt_db.h to regenerate $example.h in the $example folder.
After changing the GATT definition in $example.gatt, please run ./update_gatt_db.h to regenerate example.h in the $example folder.
### Compiler Warnings:
The project is set to use -Os optimization which will cause warnings if you
only have the Free version. It will still compile a working example.

17
port/windows-winusb/README.md Normal file
View File

@ -0,0 +1,17 @@
# BTstack Port for Windows Systems using the WinUSB Driver
Although libusb basically works with the POSIX Run Loop on Windows, we recommend to use the Windows-WinUSB port that uses the native run loop and WinUSB API to access a USB Bluetooth dongle.
To allow libusb or WinUSB to access an USB Bluetooth dongle, you need to install a special device driver to make it accessible to user space processes.
It works like this:
- Start [Zadig](http://zadig.akeo.ie)
- Select Options -> “List all devices”
- Select USB Bluetooth dongle in the big pull down list
- Select WinUSB (libusb) in the right pull pull down list
- Select “Replace Driver”
When running the examples in the MSYS2 shell, the console input (via btstack_stdin_support) doesn't work. It works in the older MSYS and also the regular CMD.exe environment. Another option is to install WinPTY and then start the example via WinPTY like this:
$ winpty ./hfp_hf_demo.exe