No ping response after opening COM port error

[Prathik]

This is the error I have. Couldn't figure out what causes this error. Tried all the related issues mentioned on this website.
I have made sure the python and latest version pip is installed.
Trying serial update on Windows. I use Adafruit Feather nrf52840 board. I have also read that double clicking reset button enters the DFU mode. When I tried it, I could see led continuously glowing and a drive is visible on my PC. I have tried it several times. But suddenly stopped. Double clicking the reset button doesn't make the led glow and i can't see the drive.  

Please let me know what I can do to make this work. Thank You.

[Vidar Berg]

Hello,

Trying serial update on Windows. I use Adafruit Feather nrf52840 board. I have also read that double clicking reset button enters the DFU mode. When I tried it, I could see led continuously glowing and a drive is visible on my PC. I have tried it several times.

Sounds like the problem is that the board isn't entering DFU mode for some reason. Is there any chance the serial bootloader may have been erased from the board? Also, is the bootloader provided by Adafruit, or have you built it yourself from the nRF5 SDK? The "no ping" error indicates that the bootloader didn't receive the ping request.

 

[Prathik]

Thank you for your response.
I'm not sure whether the bootloader was erased or not. Is there any way to test it?
The bootloader was built from nrf5 SDK. The person who built it has tested using nrfutil. It worked for him.
But I'm facing this issue.

Even the double clicking of Reset button doesn't work.

Please let me know if there's any way to fix this issue. Thank you

[Vidar Berg]

It's bit difficult to say way it won't enter DFU mode. I have not worked with the feather board myself but looks like it comes without an on-board debugger. Do you have an external J-link programmer to re-program the board? Maybe you can recover the board by re-programming the bootloader (assuming you have access to the bootloader .hex file).

[Prathik]

Yes. I have a J-Link programmer. I have deployed the bootloader program and then used the nrfutil command. Still have the same error

[Vidar Berg]

Please try to program the Master boot record (MBR) as well, in case it's not included in your bootloader hex file. This section is needed for the bootup process (bootloader will never start without it)

Bootloader memory layout

MBR hex (from \nRF5_SDK_17.0.2_d674dde\components\softdevice\mbr\hex)

0552.mbr_nrf52_2.4.1_mbr.hex

If it still doesn't work, then you have to try debug the device to find out why it's not entering DFU mode. For example, run 'nrfjprog --readregs' to see if the CPU registers may provide some clues as to what's wrong. The CPU program counter (PC) register will for instance tell what address the CPU is executing code at.

[Prathik]

Hello. Sorry for late reply.
The MBR hex is already present.

C:\Users\nishi>nrfjprog --readregs
R0: 0x00000000
R1: 0x00000000
R2: 0x00000000
R3: 0x00000000
R4: 0x00040003
R5: 0x20001E00
R6: 0x10001000
R7: 0x000FE000
R8: 0x00000000
R9: 0x00000000
R10: 0x00000000
R11: 0x00000000
R12: 0x2003A73D
SP: 0x2003FFD8
LR: 0x0002B6DD
PC: 0x00027720
xPSR: 0x61000000
MSP: 0x2003FFD8
PSP: 0x00000000

I dont know how to check this. Please let me know how I can check whether the device goes to bootloader mode or not.

Thank you.