GPIOTE Library makes my Board Brick?? (J-Link is not Found)

[Daniel T. Lee]

GPIOTE Library makes my Board(nRF51422-QFAC) Brick??

I just build my nRF51422 Board, and It's pretty working well before I've used GPIOTE Library.

Before using GPIOTE Library, I've used GPIOTE Driver, And It works pretty well. (But sometimes, about Running my FW few minutes, it often Hardly resets. [Maybe System-Failure? I couldn't find what was the problem.])

As It works Okay, I was trying to use more than 4-pins(Channel) (I need about 8~9 pins of gpiote). (To my knowledge, GPIOTE Driver only supports 4-pins(Channel) and GPIO Library opens all the 32-pins.)

So I've just followed these instruction.

infocenter.nordicsemi.com/index.jsp

But following instruction, these source codes that I wrote break my Board. I tried 2 PCB boards, all those Two boards not runs at all, and also, J-Link is no more detectable.

These are my source code that I wrote. gist.github.com/.../823882158b455073311bfa1e5816e712

I've never seen like this before. Is it even possible that FW can make Board Brick (+J-Link not detectable)? (and also It's just a simple GPIOTE peripheral ???)

I've used SDK12.2.0, s130, nRF51422-QFAC.

[RK]

no it is not possible that firmware can 'brick' a board. In fact there is almost nothing at all you can do to a simple MCU like the nRF series which makes them unrecoverable. More likely you have a problem with your board design which is not allowing the JLink to access it, or is holding the reset line in reset or something like that.