nRF52832 wlcsp pin assignment from nRF51822 QFN

RE: nRF52832 wlcsp pin assignment from nRF51822 QFN

Jørgen Holmefjord — Fri, 06 Jan 2017 11:36:15 GMT

Just use 23. A good practice is to create a define that say something about the pin function and use that define in your code. For instance if P0.23 is connected to LED1:

#define LED1 23
nrf_gpio_cfg_ouput(LED1);
nrf_gpio_pin_set(LED1);

RE: nRF52832 wlcsp pin assignment from nRF51822 QFN

K.O. — Fri, 06 Jan 2017 09:33:51 GMT

Thanks for the hints and the hack, Jørgen. I learned that I shouldn't have to change nRF5 SDK.

Please let me confirm if I got it. In the case of MDBT42, nRF52832's P0.23 assigned to MDBT's P2. I should have to called it 『p23』 or 『P0_23』 in my program, right?

Best Regards.

K.O.

RE: nRF52832 wlcsp pin assignment from nRF51822 QFN

Jørgen Holmefjord — Fri, 06 Jan 2017 08:27:24 GMT

Hi,

The nRF52832 WLCSP ball assignments is documented in the nRF52832 product specification at the infocenter. You should not have to do any changes in the SDK, as the pin numbers used in the SDK correcponds to the Px.xx name of the pins, not the physical pin/ball number.

Best regards,

Jørgen