Line-by-line debug broken between uVision 5.36 and 5.41

Hello,

I run a college microprocessor lab and my students were having trouble with line-by-line debugging only working in the disassembly window. I was running uVision 5.36 and had never seen this issue. I made a second installation with version 5.41, and this has replicated the issue.

This is while using the software simulator to debug.

In version 5.36, the correct behavior when entering debug mode:

The cursor is brought to the first executable line in the editor window, and highlights the line to be executed. When stepping the program with F11:

The cursor, line highlight, and yellow arrow in the editor box have moved to the next line to be executed, and the executed code line has the green executed box on the left.

When running the same file with the same debug settings in version 5.41:

Breakpoints fail despite being on executable lines.

No yellow arrow is present on the editor screen, only in the disassembly window. Students have difficulty telling what is being executed.

When stepping forward with F11:

The editor window is not refocused, but updates the green squares when clicked into or interacted with. The disassembly window functions as expected, but no yellow arrow exists on the editor window with the source code. In addition, the "Show Next Statement" yellow arrow button does nothing.

The program functions normally, though, with all register and memory values matching what is expected.

Here are the details on both installations:

The target is TI TM4C123GH6PM.

When using the board and debugging with Stellaris ICDI, the same issue occurs, but the green "executed" boxes do not appear in either the disassembly or the source editor window.

Is there a way to fix this error, or should I just have my students install an older version?

Thanks for your help!

  • We will analyze this issue to find out if the newer Arm compiler causes this issue or any change in the µVision debugger.

    When using the board and debugging with Stellaris ICDI, the same issue occurs, but the green "executed" boxes do not appear in either the disassembly or the source editor window.

    The green 'executed' boxes come from code coverage information. This information is only available in the simulator and when the target and the debug interface support the collection of code coverage information. This is currently only possible with ULINKpro and targets that support an ETM interface.