nRF52840 custom board won't boot without debugger "kick" start

RE: nRF52840 custom board won't boot without debugger "kick" start

Sigurd — Fri, 25 Nov 2022 16:25:18 GMT

[quote user="laurentc"]

I try

CONFIG_BOARD_ENABLE_DCDC=n

...

and it works...

What a relief.

[/quote]

Great to hear it's now working!

RE: nRF52840 custom board won't boot without debugger "kick" start

laurentc — Fri, 25 Nov 2022 14:42:20 GMT

Hum, I see that in the default dk conf, the DCDC is enabled...
I try

CONFIG_BOARD_ENABLE_DCDC=n

...

and it works...

What a relief.

I would recommend that the default prj.conf has the line CONFIG_BOARD_ENABLE_DCDC=y

even if it is the default value.

RE: nRF52840 custom board won't boot without debugger "kick" start

laurentc — Fri, 25 Nov 2022 14:32:42 GMT

I am OK to provide all the information needed in a private thread. with schematics, and full project.

4) Yes I do. I just tried with a radio_test without mcuboot. (still compiled in the same dev env)

See below only differences.

Again, I have tried. Exactly the same behavior. Will start only with the debugger and then can be reset by my CPU and will restart.

I have been given some example hex, not compiled with nrfconnect that do start correctly on our target.

1) Yes.
2) No. We have no external LC filter. DCC left not connected. Note : Do not enable the DC/DC regulator without an external LC filter being connected as this will inhibit device operation, including debug access, until an LC filter is connected.

3) As I said, I modified the DK_1 in order to look quite like our design.

Practically,

I target the nrf52840dk_nrf52840

For radio_test without mcuboot all changes are :

prj.conf modified with

# No 32.768Khz Quartz

CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=n

AND with added overlay file

/ {

buttons {

compatible = "gpio-keys";

button4: button_4 {

gpios = <&gpio1 15 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>;

label = "Nordic_CONN";

};

aliases {

sw4 = &button4;

};

&pinctrl {

uart0_default: uart0_default {

group1 {

psels = <NRF_PSEL(UART_TX, 0, 0)>;

};

group2 {

psels = <NRF_PSEL(UART_RX, 0, 1)>;

bias-pull-up;

};

uart0_sleep: uart0_sleep {

group1 {

psels = <NRF_PSEL(UART_TX, 0, 0)>,

<NRF_PSEL(UART_RX, 0, 1)>;

low-power-enable;

bias-pull-up;

};

&uart0 {

status = "okay";

current-speed = <115200>;

};

nota : same problem without the bias-pull-up in the uart0_sleep section

RE: nRF52840 custom board won't boot without debugger "kick" start

laurentc — Fri, 25 Nov 2022 13:40:53 GMT

Yes to both of your questions. To be even more precise, after having compiled and run the FW on the DK_1. I close nRFConnect. Switch off DK_1. Connect the target and flash it with the generated merged.hex through the DK_2.

This way, I am sure that it is exacly the same binary.

RE: nRF52840 custom board won't boot without debugger "kick" start

Sigurd — Fri, 25 Nov 2022 13:24:08 GMT

Hi,

1) You are running the exact same FW on the custom board and the DK, and you are only having this issue on the custom board? Correct?

2) Are you using DCDC?

3) In nRF Connect SDK, what board target are you building for? Did you create your own board files for the custom board?

4) Do you see the same issue with samples that don't use mcuboot?