https://devzone.nordicsemi.com/f/nordic-q-a/51061/segger-step-debug-jump-unexpected-into-disassembly-codeI use SEGGER step-debug commands F5, F10 and F11. Sometime F10 cause the debugger to step into disassembly code, making continue debugging hard. Restart debugging &#39;cause exactly same behavior, but then later the issue disappear. I cannot see anyen-USTelligent Community 13Tue, 20 Aug 2019 06:16:28 GMThttps://devzone.nordicsemi.com/thread/204901?ContentTypeID=1Tue, 20 Aug 2019 06:16:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8c4e952c-5c07-4823-bb20-f7d5b98fcf2aSusheel Nuguru<p>As far as I know, the segger jumps into disassembly, if it was not able to figure out where the source files for that part of the code section is.&nbsp;</p> <p>In your case if you are stepping one line in the same source file, then it is a bit strange that it jumps into <span>disassembly</span>.</p> <ol> <li>Make sure that there are no unintentional breakpoints set in the disassembly code.</li> <li>Understand what lies at the address of the disassembly code where the execution jumps to.&nbsp;</li> <li>If the assembly instruction does not show any jump to the code section of the disassembly section, then it could be a segger IDE bug, please contact them through <a href="https://forum.segger.com/index.php/Board/9-SEGGER-Embedded-Studio-related/">forum</a> do understand more.</li> </ol><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/204418?ContentTypeID=1Fri, 16 Aug 2019 08:37:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a05388d0-2bf8-44e3-9671-94239e7f549fLennart<p>Actual it looks like it jump into some exception-code, but only when in single step-debug.</p><div style="clear:both;"></div>