Hello,
I am following the instruction on dev academy - nrf connect sdk intermediate lesson 2 excercise 1, but I can't select data tab on memory explorer.
I can select only rom area.
I wonder if I missed any settings in the VS Code or nRF Connect extension.
I am using
1. nRF5340DK
2. nRF Connect SDK 2.9.1
I also created the build with ns or without ns.
I wanted to find if any others have the same issues before, but I couldn't find.
1. I followed the lesson, and I faced the problem before I added any additional codes. I have the issue on section 6.7.
If you check the lesson's details, you can see that the solution code will be made after section 7.
2. Anyhow, I tried to run l2_e1_sol, but I have the same issue. When the debug is stopped at the first breakpoint which is at the main(), I tried to select any other tabs in Memory explorer, but only ROM is selected and cannot move to other tabs.
3. When I continue the debugging by pressing F5 button, the error occurred.
/__w/_temp/workspace/build/.build/HOST-x86_64-w64-mingw32/arm-zephyr-eabi/src/gdb/gdb/infrun.c:5825: internal-error: finish_step_over: Assertion `ecs->event_thread->control.trap_expected' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal
/__w/_temp/workspace/build/.build/HOST-x86_64-w64-mingw32/arm-zephyreabi/src/gdb/gdb/infrun.c:5825: internal-error: finish_step_over:
Assertion `ecs->event_thread->control.trap_expected' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal]
ERROR: GDB exited unexpectedly with exit code 3 (0x3). Debugging will now abort.
The program 'c:/ncs/MyWorkSpace/ncsinter/l2_e1_sol_1/build/l2_e1_sol_1/zephyr/zephyr.elf' has exited with code -1 (0xffffffff).
My SDK is v2.9.1.
nRF Connect for VS Code version is 2025.4.106
I am testing with nRF5340DK (I tried ns and normal, but both have the same result)
We cannot reproduce the issue in your first post.
Could you try 2025.4.186 of nRF Connect for VS Code?
The second issue seems like a debugger issue, it very much sounds like the gdb issues discussed in this forum.
Hello, the nRF Connect for VS Code has been automatically updated to 2025.4.186 today.
But I still face the issue.
I also tried SDK 2.7.0, but the result is the same.
I also checked my VS Code is not updated, but it's already the latest one.
I also checked the memory area, and it looks like data area is properly reserved.
In the worst case, I am thinking to uninstall the VS Code and re-install it. But in that case, I need to set up everything, so I would like to avoid that situation.
Is there any other thing that I can try?
Are you able to click the Go to Symbol icon in the upper right-hand corner in the memory explorer window, and Type in the global variable test_var? Will it show up as Step 6.5 in the lesson 2 exercise 1?
Are you able to click the Go to Symbol icon in the upper right-hand corner in the memory explorer window, and Type in the global variable test_var? Will it show up as Step 6.5 in the lesson 2 exercise 1?
I am using the nRF9151DK with the nRF Connect for VS Code Extension Pack, version 2025.4.4, and I am experiencing a similar bug. However, I can only access the data tab:
I am clicking on the ROM, text, and rodata tabs, but they do not change.
