https://devzone.nordicsemi.com/f/nordic-q-a/47683/pc-ble-driver-js-with-custom-board-and-gpio-pinsHi, We have worked with building a raspberry pi system that uses a nRf52832 dev kit board and the pc-ble-driver-js code to scan and connect to our bluetooth devices. This has worked well so we decided to use our custom nRF52832 board. Our board usesen-USTelligent Community 13Fri, 24 May 2019 14:42:16 GMThttps://devzone.nordicsemi.com/thread/189090?ContentTypeID=1Fri, 24 May 2019 14:42:16 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fe348b21-bea4-46e9-a6ce-3b491c758f07Sigurd<p>Hi,</p> [quote userid="77142" url="~/f/nordic-q-a/47683/pc-ble-driver-js-with-custom-board-and-gpio-pins"]The question I have then is if it is possible to recompile the pc-ble-driver and pc-ble-driver-js code to accommodate these different pin settings?[/quote] <p>Yes.</p> <p>The connectivity hex running on the nRF5 is based on the ble_connectivity example in the SDK, found in&nbsp; SDK_folder\examples\connectivity\ble_connectivity ,but with this <a href="https://github.com/NordicSemiconductor/pc-ble-driver/tree/master/hex">nRF5_SDK_15.3.0_connectivity.patch</a>&nbsp;applied. In the patch, we set the pin defines in&nbsp;ser_phy_config_conn.h to&nbsp;RX_PIN_NUMBER,TX_PIN_NUMBER,CTS_PIN_NUMBER and RTS_PIN_NUMBER. If you build the&nbsp;pca10040(nRF52832-DK) project, then these pins are defined in&nbsp;pca10040.h (components\boards). You can apply the patch, set these pins so they match your custom board, build the example,&nbsp;flash the hex file, and you should be good to go.</p><div style="clear:both;"></div>