Hi to all,
please consider assisting me.
I am using Jlink to program my DUT with a low-power FW. Yet, it seems that, when the programming is over and I try to close GDBserver (by killing the task through windows) something remains connected and my DUT cannot enter the lower power mode, it stays in high-power debug mode.
My tests are as follows:
Going through the active processes there is nothing related that seems to be running after either window close or cmd taskkill.
Apparently, when manually closing GDBserver by hitting the 'close' button there are other operations as well taking place (disconnect? power off?)
Does anybody have any insight on this? How can I, properly, close GDBserver via CL?
Thank you in advance
BR,
Thanos
please consider assisting me.
I am using Jlink to program my DUT with a low-power FW. Yet, it seems that, when the programming is over and I try to close GDBserver (by killing the task through windows) something remains connected and my DUT cannot enter the lower power mode, it stays in high-power debug mode.
My tests are as follows:
- Case 1
- Manually open GDBserver
- Program board
- Check processes, there are
- linkGDBserver
- linkGUIserver running
- linkGDBserver
- Close GDBserver window manually
- Both processes disappear, consumption drops to uA
- Manually open GDBserver
- Case 2
- Manually run GDBserver
- Program board
- Check processes, there are
- linkGDBserver, and
- linkGUIserver running
- linkGDBserver, and
- Kill GDBserver via CMD (C:\Windows\System32\TASKKILL.exe /F /PID 19996 , PID changes for each run of course)
- Both processes disappear, consumption STAYS HIGH
- Altering the kill operation (first kill GDBserver then kill GUIserver or vice versa) does not change things
- Manually run GDBserver
- Case 3
- Open GDBserver via "C:\Program Files\SEGGER\JLink_V794\JLinkGDBServerCL.exe" -device Cortex-M33 -select USB=1100007809 -if swd -speed 1000 -port 2331 -ir
- Program board
- Check processes, there are
- JLinkGDBServerCL, and
- JLinkGUIServer running
- JLinkGDBServerCL, and
- Kill GDBserverCL via CMD (C:\Windows\System32\TASKKILL.exe /F /PID 19996 , PID changes for each run of course)
- Both processes disappear, consumption STAYS HIGH
- Altering the kill operation (first kill GDBserverCL then kill GUIserver or vice versa) does not change things
- Open GDBserver via "C:\Program Files\SEGGER\JLink_V794\JLinkGDBServerCL.exe" -device Cortex-M33 -select USB=1100007809 -if swd -speed 1000 -port 2331 -ir
Going through the active processes there is nothing related that seems to be running after either window close or cmd taskkill.
Apparently, when manually closing GDBserver by hitting the 'close' button there are other operations as well taking place (disconnect? power off?)
Does anybody have any insight on this? How can I, properly, close GDBserver via CL?
Thank you in advance
BR,
Thanos