Third-Party Module cannot run and debug examples in ncs

SDK: NCS v2.6.0

Program Software: v2.6.0\nrf\samples\openthread\cli

Hardware:nrf52840dk_nrf52840 and third-party module(nrf52840 soc)

The program runs normally on nrf52840dk_nrf52840, but it cannot run and debug after flashing to the third-party module. In addition, the third-party module cannot be flashed a second time after the first successful flash. The device needs to be restarted to erase the flash.The program runs normally on nrf52840dk_nrf52840, but it cannot run and debug after flashing to the third-party module. In addition, the third-party module cannot be flashed a second time after the first successful flash. The device needs to be restarted to erase the flash.

Screenshot below:

How should I deal with this?

sincere regards,

Parents
  • Hello,

    The typical issue that leads to this behavior is the lack of the condencator required for the DCDC converter to work.

    The fix is to disable the DCDC in your prj.conf by adding:

    CONFIG_BOARD_ENABLE_DCDC=n

    However, the board(s) that you already programmed with an application that is enabling the DCDC when it is not possible to use it is probably stuck in some reset loop.

    What you can try is to save this snippet into a .bat file on your computer, and name it recover_script.bat (or whatever you like to call it):

    :loop
    nrfjprog --recover -f NRF52
    goto loop

    Then run this script from a command line, while you power cycle the board. Let it run for a few minutes, while power cycling the board every couple of seconds. Then the goal is that the script is able to hook onto the debugger before the chip browns out. 

    Best of luck, and best regards,

    Edvin

Reply
  • Hello,

    The typical issue that leads to this behavior is the lack of the condencator required for the DCDC converter to work.

    The fix is to disable the DCDC in your prj.conf by adding:

    CONFIG_BOARD_ENABLE_DCDC=n

    However, the board(s) that you already programmed with an application that is enabling the DCDC when it is not possible to use it is probably stuck in some reset loop.

    What you can try is to save this snippet into a .bat file on your computer, and name it recover_script.bat (or whatever you like to call it):

    :loop
    nrfjprog --recover -f NRF52
    goto loop

    Then run this script from a command line, while you power cycle the board. Let it run for a few minutes, while power cycling the board every couple of seconds. Then the goal is that the script is able to hook onto the debugger before the chip browns out. 

    Best of luck, and best regards,

    Edvin

Children
No Data
Related