dev academy - nrf connect sdk intermediate - lesson 2 excercise 1 : Memory explorer - not possible to select data

[toto cho]

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.

[toto cho]

No.
1) Nothing appeared on the top when I search test_var with "go to symbol"
2) I also tried "go to address", but it has the same problem.

By the way, 

I tested my personal nRF5340.at home first.
I was wondering if it is my DK's issue, so I also tried nRF52DK-nRF52832 in the office (with different laptop, but I believe the VSCode should have the same setting).
And I got the same result, so I wonder if there is any option that I should select on VS Code or nRF Connect Extension?
Or could it be APProtect issue? I don't think my nRF52DK has the SoC with APProtect as it's quite old version. (PCA10040 3.0.0, 2022.12)

[dheadrick]

I am having the same issue, although using an nRF9151DK. I have tried all the mentioned possible solutions and nothing has resolved the memory explorer unable to show anything but the 'rom' - bug.

[oscargomezf]

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.

[toto cho]

Hello Amanda,

Can you check my reply and other people's opinion, and let us know if it is a bug that Nordic should fix or we should change any settings on VS Code or nRF Connect extension?

[Mark Szente]

Here's a workaround: click the + button next to "data", enter something like 0, 1, 1. It will create a new tab. Then, close that tab. You're now on "data". Unfortunately, you cannot go back to "rom", unless you close the nRF debug UI. Similarly, "text" and "rodata" are inaccessible.