Thread Viewer Empty - Visual Studio Code

[Doug K]

Hello, 

The thread viewer on VS-Code is empty and not showing the current threads.

nRF52 DK nrf52832
nRF SDK v2.5.2
Toolchain 2.5.2
J-Link updated to Oct 2023 version

Build is set to -Og Optimized for Debugging

I also tried with prj.conf settings:

CONFIG_DEBUG_OPTIMIZATIONS=y

CONFIG_DEBUG_THREAD_INFO=y

I am using the sample for the "Simple Threads", same as the youtube video. Located at: C:\ncs\v2.5.2\zephyr\samples\basic\threads

Something interesting is that I installed Ozone to see if that would work, and thread viewer is working fine on Ozone with the same program running.Its like my visual studio settings are messed up for debugging.

Here is some additional information: 

when typing in debug console -exec info threads

Debug Console info: 

JLinkGDBServerCL: SEGGER J-Link GDB Server V7.96b Command Line Version
JLinkGDBServerCL:
JLinkGDBServerCL: JLinkARM.dll V7.96b (DLL compiled Mar 20 2024 16:56:49)
JLinkGDBServerCL:
JLinkGDBServerCL: -----GDB Server start settings-----
JLinkGDBServerCL: GDBInit file: none
JLinkGDBServerCL: GDB Server Listening port: 56720
JLinkGDBServerCL: SWO raw output listening port: 2332
JLinkGDBServerCL: Terminal I/O port: 2333
JLinkGDBServerCL: Accept remote connection: localhost only
JLinkGDBServerCL: Generate logfile: off
JLinkGDBServerCL: Verify download: off
JLinkGDBServerCL: Init regs on start: off
JLinkGDBServerCL: Silent mode: on
JLinkGDBServerCL: Single run mode: on
JLinkGDBServerCL: Target connection timeout: 0 ms
JLinkGDBServerCL: ------J-Link related settings------
JLinkGDBServerCL: J-Link Host interface: USB
JLinkGDBServerCL: J-Link script: none
JLinkGDBServerCL: J-Link settings file: none
JLinkGDBServerCL: ------Target related settings------
JLinkGDBServerCL: Target device: nRF52832_xxAA
JLinkGDBServerCL: Target device parameters: none
JLinkGDBServerCL: Target interface: SWD
JLinkGDBServerCL: Target interface speed: 12000kHz
JLinkGDBServerCL: Target endian: little
JLinkGDBServerCL:
=thread-group-added,id="i1"
=cmd-param-changed,param="pagination",value="off"
arch_cpu_idle () at C:/ncs/v2.5.2/zephyr/arch/arm/core/aarch32\cpu_idle.S:143
143 cpsie i
Execute debugger commands using "-exec <command>" or "`<command>", for example "-exec info registers" or "`info registers" will list registers in use (when GDB is the debugger)

Breakpoint 3, uart_out () at ../src/main.c:105
105 printk("Toggled led%d; counter=%d\n",

[Doug K]

What J-Link version is everyone using? Also what does your debug printout look like? 

Thanks,

Doug K

[Doug K]

Adding more information. I can get some of the log information to show up if I do the following:

1. Set build to something other than "Optimize for Debugging" and do pristine build

2. Set build back to "Optimize for Debugging" and do a pristine build

3. Click Debug

4. spam the continue/pause until something populates.

Only then will the thread viewer show information but it is still greyed out:

[Menon]

Hello,

Sorry for the delay occurring here. I have poked the team once again now. I will update as soon as I hear from them.

Kind Regards,

Abhijith