l2_e1 and l2_e1_sol flash but don´t upload to nRF52 DK

[Luiz Miranda]

Hello,

l2_e1 and l2_e1_sol are generated and built no error.
They flash, but they don't load the program the nRF52 DK.
I used several versions of the toolchain and SDK.
I selected the optimize for debugging option and without the option selected.

I flashed other programs from the nRF Connect SDK Fundamentals course and they all load normally and work.

regards

Luiz

[runsiv]

Hi Luiz

Which versions of NCS did you test?

I tested l2_sol with the 52dk on NCS 3.1 and I don't see any issue. 

Can you try to add a print message to show the status of the LED?

Regards

Runar

[Luiz Miranda]

Hi Runor:

I'll run tests over the weekend and send you the results.

About: Exercise l2_e2 (nRF Connect SDK Intermediate) - 11. See the backtrace of the moments before the crash.
I received the message below from the bt command.
gdb) target remote localhost:1234
Remote debugging using localhost:1234
crash_function (addr=<optimized out>) at C:/myfw/ncs-inter-main/ncs-inter-main/l2/l2_e2/src/main.c:31
31 __asm__ volatile("udf #0" : : : );
(gdb) bt
#0 crash_function (addr=<optimized out>) at C:/myfw/ncs-inter-main/ncs-inter-main/l2/l2_e2/src/main.c:31
#1 0x00002524 in z_arm_fault_init() at C:/ncs/v3.1.0/zephyr/arch/arm/core/cortex_m/fault.c:1121
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Is the result what I should receive?
Is there a command that shows some instructions executed before MSG #0 crash_function?

Regards

Luiz