Passion Mission Action
News & Blog
Dec.06.2018
BLE Module Firmware Development Q&A: NFC pins creates “Error 404 – signal not found” (technically)
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.
Reference link:Nordic DevZone - NFC pins into GPIOs
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.
Reference link:Nordic DevZone - NFC pins into GPIOs
Other News
-
Essential Tips for Verifying HEX Files to flash into Raytac nRF54L15 modules
Aug.06.2025UPDATE. -
MCUboot DFU Guide For Raytac MDBT50Q-DB-40 (Using NCS V2.9.1)
May.29.2025UPDATE.

