P0.12 not working with I2C

[TS Gowtham]

Hi,

On the nRF52810, is there any limitation on using P0.12 with I2C? I am using MS50SFA module on a custom PCB.

I've also noticed the same issue on a nrf52 DK while using a pca10040e project.

Thanks,

Gowtham

[Jared]

Hi,

On the nRF52810, is there any limitation on using P0.12 with I2C

 No, there shouldn't be any issues with using pin 12 on the nRF52810. Have you checked that the application doesn't go into the error handler? What happens if you change the pin?

regards

Jared 

[TS Gowtham]

Hi Jared, 

The code did not hit the hardfault handler. The pin was changed to P0.09 and TWI was working as expected.

IIRC, P0.12 was a NFC pin in the nrf52832. Could that be related to this issue somehow?

Thanks

[Jared]

Hi,

P0.12 is marked as a general GPIO on the nRF52810 which you are still using, correct? 

 

I've also noticed the same issue on a nrf52 DK while using a pca10040e project.

 Could you upload an example that reproduces this on the nRF52 DK /PCA10040e

regards

Jared

[TS Gowtham]

Hey Jared,

I don't have an example for the nRF52 DK, I'll try to whip one up ASAP. But wouldn't this issue be expected on the nRF52 DK since P0.12 would be a NFC pin?

Thanks

[Jared]

Hi,

Pin 12 i.e. P0.10 is marked as an NFC pin on the nRF52832, Pin 15 i.e. P0.12 is marked as a GPIO.

The nRF52810 doesn't have an NFC peripheral. 

Either way, emulating the nRF52810 on the nRF52 DK by using the PCA10040e examples will disable the NFC option which will hinder any possible pin conflicts with the NFC.

regards

Jared