NCS runs normally in debug mode, but fails to run in normal mode

[zjw2021]

Hello Nordic

     Use NRF52832  、  NCS 1.6 、“zephyr\samples\basic\blinky” sample.

    In hardware, my board doesn't have a low-speed clock, and the reset pin is floating. Therefore, I configured CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y in the kconfig file.

    The program runs normally on the development board, but it doesn't run after being flashed onto my board.

     If I use debugging in VS Code, the program runs normally, but it stops as soon as the debugging session ends.

I have been troubleshooting for a long time but still haven't found the cause. I would greatly appreciate your help.

[Menon]

In hardware, my board doesn't have a low-speed clock, and the reset pin is floating. Therefore, I configured CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y in the kconfig file

That's correct.

I have been troubleshooting for a long time but still haven't found the cause. I would greatly appreciate your help.

Does your custom board come with a DC-DC converter? Please check if disabling this in the prj.config file makes it work:. CONFIG_BOARD_ENABLE_DCDC=n

I am not entirely sure about the SDK version you are using, but if it's NCSv1.6, I recommend switching to a much newer version, as this is quite outdated.

Kind Regards,

Abhijith

[zjw2021]

Thank you very much. Indeed, my circuit doesn't have an inductor, so I need to disable the DC-DC converter.

Additionally, I would like to ask why NCS recommends using the nRF52840 instead of the nRF52832. Besides the smaller flash memory size, are there any other reasons?

[Menon]

Hello,

Glad to hear that it resolved your issue.

I don't think NCS will recommend using nRF52840 over nRF52832. Selecting the chip or development kit depends on the features and the application you are working with. One of the considerations is flash memory, which limits some of the DFU options. I recommend going through the product specification page to compare the two.

Kind regards,

Abhijith