Raytac Corporation, A Bluetooth Module Maker based on Nordic nRF52840 & nRF52832 & nRF51822 & nRF52810 Solution. Bluetooth Specification Version: BT5 & BT4.2 & BT4.1 & BT4.0
Wednesday, December 5, 2018
BLE Module Firmware Development Q&A: NFC pins creates “Error 404 – signal not found” (technically)
When you start developing your firmware for your Nordic nRF52832 solution-based Raytac BLE module, you will (like on most other projects) bump into some difficulties.
The other day, we had yet another case where a simple thing caused major difficulties for even some of the brightest people – a customer couldn’t get their GPIO direction bit to work.
Although not too difficult to solve, it’s a common error that most customers end up having on our modules and that is because Pin 0.09 & 0.10 are set to NFC per Nordic’s default settings. In order to be able to use these pins as normal GPIOs, you will have to change those settings.
The two pins I am talking about are the ones linked to the NFC-part to the far left in the circuit example below:
So, to convert these two pins to normal GPIOs, here’s what you need to do:
In SES, you’ll need to add CONFIG_NFCT_PINS_AS_GPIOS.
Check out the link below for a reference example on Nordic’s DevZone.