• State Verified Answer
  • Replies 16 replies
  • Subscribers 75 subscribers
  • Views 4554 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 273993
Options
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

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.

Parents
  • 0

    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.

     

  • 0 in reply to Vidar Berg

    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

  • 0 in reply to Vidar Berg

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

  • 0 in reply to Prathik

    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.

  • 0 in reply to Vidar Berg

    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.

  • 0 in reply to Prathik

    Hello,

    The Program counter (PC) shows that the CPU is executing code inside your main application and xPSR shows that it's not running in any interrupt context. Unfortunately, it doesn't help explain why your board is not entering/staying in the bootloader DFU mode on startup.

    Could you try to view the memory layout if your device with the nRF connect for desktop app just to make sure everything looks to be as expected?

    Also, check the if the bootloader address stored at the following 2 addresses matches the actual bootloader address displayed in the nRF connect app:

  • 0 in reply to Vidar Berg



    The bootloader file is a zip file that I have to use for updating by Serial using nrfutil. It contains bin and dat file. So I cant drag and drop that file.


Reply Children
Related
Terms of service