This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

pc-ble-driver UART pins

We're targetting the nRF51822 and use the pc-ble-driver (via connectivity_1.1.0_115k2_with_s130_2.0.1)

Currently I'm using the dev board and the virtual COM port connection works. But ideally I would like to flash this same .hex file for production, just connecting the UART for coms instead.

So questions:

  • Does anyone know if the UART is enabled on that hex and what on which pins?
  • If the answer to above is "not available, you have to recompile", can anyone point me to the source (or header) file where to setup that?

I found questions like this LINK but it seems to ask to change the UART pins, I don't want to change them, I want to simply know which ones are already configured, so we can plan our hardware using the same ones.

Parents
  • 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.

  • "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 !

Reply
  • "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 !

Children
No Data
Related