nrf5340-PDK , potentially dead?

[AMarch]

To start, this was a functional unit and I had been installing test firmware into it.

As of a couple of days ago while attempting to read and write to my nrf5340-PDK module, I am receiving the following :

2020-02-10T13:11:21.483Z INFO Application data folder: C:\Users\\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2020-02-10T13:11:21.608Z DEBUG App pc-nrfconnect-programmer v1.3.1 official
2020-02-10T13:11:21.609Z DEBUG App path: C:\Users\\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2020-02-10T13:11:21.609Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.3.0)
2020-02-10T13:11:21.609Z DEBUG nRFConnect path: C:\Users\\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-02-10T13:11:21.609Z DEBUG HomeDir: C:
2020-02-10T13:11:21.609Z DEBUG TmpDir: C:\\Temp
2020-02-10T13:11:21.626Z INFO Using nrfjprog library 10.5.0, pc-nrfjprog-js 1.6.0
2020-02-10T13:11:28.034Z INFO Using nrfjprog to communicate with target
2020-02-10T13:11:28.640Z INFO Using J-Link Software version 6.63
2020-02-10T13:11:29.647Z INFO Segger serial:  960173787
2020-02-10T13:11:29.647Z INFO Segger speed:  2000  kHz
2020-02-10T13:11:29.648Z INFO Segger version:  J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
2020-02-10T13:11:29.656Z INFO Core probed: 960173787.
2020-02-10T13:11:29.656Z INFO Core RAM: 512KiB.
2020-02-10T13:11:29.656Z INFO Core ROM: 1024KiB in pages of 4KiB.
2020-02-10T13:11:30.668Z ERROR Error when closing nrfjprog: Error: Error occured when close opened device. Errorcode: CouldNotResetDevice (0x5)
Lowlevel error: CANNOT_CONNECT (fffffff5)

2020-02-10T13:11:30.669Z INFO Model: NRF5340_xxAA_ENGA.
2020-02-10T13:11:30.672Z ERROR Error when getting device info: Error: Error: Error occured when open device long term. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: INVALID_OPERATION (fffffffe)

2020-02-10T13:11:30.677Z ERROR Error when closing nrfjprog: Error: Error occured when close opened device. Errorcode: CouldNotOpenDevice (0x4)
Lowlevel error: INVALID_OPERATION (fffffffe)

I have tried several times to bring the unit back online, but it just seems to be dead. 

The following is a list of my potential diagnosis points.

1. The chip is dead and there is nothing I can do.

2. I moved a jumper or switch that has rendered the chip unable to communicate

3. I moved firmware onto the chip that is locking the CPU into a state that can't be managed externally.

4. I have somehow bricked the chip by not using its security features correctly.

Assuming it is diagnosis point 3 or 4 , are there any "wake up" points in the PCB that can allow you to bring the nrf5340 to a known default state ready for programming?

Assuming it is diagnosis point 2, are you aware of any jumpers (besides the obvous power switches) that my have accidently been removed? 

I suppose I should examine the board under the microscope to make sure i didn't knock of any components as well.

Tony

[Amanda Hsieh]

Hi,

Please make sure that you do not have more than one program that tries to talk to the PDK through the same port. 

If you are trying to access the PDK on the same port at the same time you could get this error.

Please open the command line and run 'nrfjprog --eraseall'

you could also try 'nrfjprog --recover'

doc

Please post any logs or errors from the testing.

-Amanda H.

[AMarch]

This is great! Your recovery operation did the trick. The board appears to be online.