BSP and nRF52 custom board - P0.9/P0.10 GPIO LED issue

RE: BSP and nRF52 custom board - P0.9/P0.10 GPIO LED issue

hmolesworth — Fri, 09 Mar 2018 04:00:50 GMT

We all got caught by these at some time or other .. and the rest:

// Important Heardware Pin Options - used in system_nrf52.c, typically added to project options
// ===============================
// ENABLE_SWO activates SWO pin, otherwise SWO pin is available as GPIO
// ENABLE_TRACE activates TRACE pins, otherwise TRACE pins are available as GPIOs
// CONFIG_NFCT_PINS_AS_GPIOS bypasses NFC input circuitry and enables 2 GPIO pins, otherwise 2 pins are NFC only
// CONFIG_GPIO_AS_PINRESET activates pin reset, otherwise pin nRESET is available as GPIO

RE: BSP and nRF52 custom board - P0.9/P0.10 GPIO LED issue

Cy — Fri, 09 Mar 2018 01:25:36 GMT

Using command line development relying on the makefile, this preprocessor needed to be added in the makefile. Using a custom board within the blinky project I added line 144 CFLAGS += -DCONFIG_NFCT_PINS_AS_GPIOS within the makefile. It would not work placed inside the pca10056.h file.

RE: BSP and nRF52 custom board - P0.9/P0.10 GPIO LED issue

RichieJH — Mon, 06 Jun 2016 14:18:10 GMT

I edited the heading because as more and more nRF52 custom boards are built this could keep coming up.

RE: BSP and nRF52 custom board - P0.9/P0.10 GPIO LED issue

RichieJH — Mon, 06 Jun 2016 14:16:03 GMT

Ok, solved this and thankfully don't feel so silly.

It appears pins 0.9 and 0.10 for the nRF52 are set for use with the NFC antenna out of the box. So in the preprocessor you need to set CONFIG_NFCT_PINS_AS_GPIOS to turn them into GPIOs.