This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

No ping response after opening COM port error

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.

  • 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.

     

  • 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

  • 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).

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

  • 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.

Related