nRF52840DK using GPIO P0.18

RE: nRF52840DK using GPIO P0.18

Elfving — Tue, 06 Dec 2022 11:45:16 GMT

Could you open a new support ticket for this?

Regards,

Elfving

RE: nRF52840DK using GPIO P0.18

jtrueb — Mon, 05 Dec 2022 18:54:23 GMT

https://devzone.nordicsemi.com/f/nordic-q-a/84537/enabling-pin-reset-is-still-active-even-with-config_gpio_as_pinreset-n

Is more than 10 months old. It is a workaround for this issue that can "break" a GPIO pin in what is now the only supported IDE.

Using VSCode with the custom board workaround and CONFIG_GPIO_AS_PINRESET=n, using flash action

```

jwtrueb@dhcp-10-101-37-8 app % hexdump uicr.bin
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0001000 0000 0000 0000 0000 0000 0000 0000 0000
*
0100000

```

Using VSCode with only CONFIG_GPIO_AS_PINRESET=n, using flash action

```

jwtrueb@dhcp-10-101-37-8 app % hexdump uicr.bin 0000000 ffff ffff ffff ffff ffff ffff ffff ffff * 0000200 0012 0000 0012 0000 ffff ffff ffff ffff 0000210 ffff ffff ffff ffff ffff ffff ffff ffff * 0001000 0000 0000 0000 0000 0000 0000 0000 0000 * 0100000

```

If I just use `nrfjprog --program zephyr.hex`, then I don't get a surprise like with the workaround. Discussion is locked on the other issue. Is there a new recommended custom board creation process?

RE: nRF52840DK using GPIO P0.18

Elfving — Tue, 08 Feb 2022 13:40:45 GMT

Hello again,

It seems that your understanding of this issue is correct, and I understand that it can be a bit cumbersome to work with.

We are looking into it, and what we can do to make this easier. In the meantime you can also look at what was suggested in this case, especially if you are using a custom board.

Are you using Visual Studio Code btw?

Regards,

Elfving

RE: nRF52840DK using GPIO P0.18

Elfving — Fri, 04 Feb 2022 15:20:22 GMT

Hello,

I am looking into it, but I will have to get back to you over the weekend.

Regards,

Elfving