This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SEGGER step-debug jump unexpected into Disassembly code

I 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 'cause exactly same behavior, but then later the issue disappear. 

I cannot see any reason since the code is not strange at all. No code-optimizing is configured.

Just one Example:

void CBtCmd::Advert(char *adv)
{
if(Port == 1)  // Here F10 result in jump to disassembly while previous code work fine in C++ 
{
memcpy(TxBuf(), adv, ADV_LEN);
SCmd.BtTx(TxBuf() ,ADV_LEN);
}
}

QUESTION: Is there any way to prevent SEGGER unexpected jump into Disassembly ?

Parents Reply Children
No Data
Related