pc-ble-driver UART pins

RE: pc-ble-driver UART pins

FormerMember — Fri, 21 Apr 2017 11:46:42 GMT

On the nRF51-DK, UART uses pin P0.08, P0.09, P0.10, and P0.11.

RE: pc-ble-driver UART pins

Ronaldo Pace — Thu, 13 Apr 2017 11:06:57 GMT

"about the pins that are configured on the supplied .hex file" I've been trying this for a couple of days but I always get error 13 on driver.open(), reason why I came to ask here. That is both true for on my Linux PC and on the raspberry PI that will be the controller on production. I've even sniffed the Tx out of the rPI and I can see a binary data being sent to the board. The DK simply never replies. Interesting enough I've tried the board with a host connected USB (led is solid green), with a power only USB(led blinks like crazy) and with direct external 3.3V supply (led is off). There's no change there, still 13 !

RE: pc-ble-driver UART pins

Carles — Thu, 13 Apr 2017 10:47:04 GMT

Hi there,

Yes, the UART is enabled of course since that is how the host communicates with the board.

The way to build the .hex is described here:

github.com/.../Installation.md

If you look at the patch you need to apply to the SDK, you'll see that it uses these macros to map the UART pins:

github.com/.../sdk110_connectivity.patch

Those macros are defined somewhere on the SDK based on the board you select, just search for those in the SDK (version 11 in your case) once you've downloaded it.

EDIT: about the pins that are configured on the supplied .hex file, just check the pins in a normal nRF51 DK (they are in the back of the PCB) and those would be it, since the .hex files are for our DKs.