Hello,

Thank you for your inquiry.
The reported issue should be fixed with the latest Ozone V2.56n.

Quote from release notes: "The refresh rates of watched expressions were erroneously reset to "off" when the program was resumed. Fixed."

Best regards,
Nino

Hi, there is still a bug remaining in v2.56n.

If an expression is added to the Watch Window, all expressions are set to a refresh rate of "Off".

Additionally, in this state when all expressions are "Off", we cannot edit the Expression name in the "Expression" column. Normally, we can double-click the name of the expression to edit it. But if all expressions have a refresh of "Off", then none of the expressions can be edited. Only when right-clicking and setting one expression to "1Hz" or more, then we can edit the name of an expression.

-Dan

Hi Dan,

During run time expression names can't be edited if refresh rate is Off. This behaviour is intended.
The other reported issues were not reproducible with an example project.
Could you provide a step by step reproduction scenario?
What data types are you watching?
Could you attach the Ozone Console log of such a session?

Best regards,
Nino

To reproduce the bug:

I found that right-clicking in the Watch window and selecting "Watch..." and then typing the variable name does not produce the bug. It seems to work OK if you use the pop-up window to enter the expression name.

However, double-clicking on the small blue arrow on the empty line in the Watch window allows me to type a new expression name. When I press enter after typing the name, all the expressions in the watch window are set to Refresh=Off. Changing the Refresh value is very cumbersome (right-click sub-menu) so changing all the values back is tedious.

The types I am testing are uint32_t ("ulong" in the Watch window). The type doesn't matter, I also tested with enum, struct, and char. All types behave the same. Arrays, single elements, everything behaves the same.
It also does not matter if the program is running, or paused. Either way, if I double click the blue arrow, type an expression (whether valid or invalid expression, it does not matter), then press Enter, all Refresh settings are set to Off. In fact, I can't find an example where double-clicking the blue arrow does *not* set the Refresh value to Off for all expressions in the Watch window.

Do you see the same behavior?

I am using the MacOS version 2.56n, debugging a project for the STM32F765. Trace is disabled.

Does anyone else see this behavior?

Here is a screen recording of it happening:

Video of SEGGER Ozone Bug in Watch Window

In the Watch Window, the Refresh Rate for all expressions is set to Off whenever a new expression is added by double-clicking the blank line.

Additionally, I've found that the Refresh Rate for all expressions is reset to Off whenever an expression is removed. The removal can be by clicking the expression line and pressing the Delete key, or by right-clicking and selecting "Remove". Either way, all expressions have their Refresh setting reset to Off.

I don't know if this matters, but I'm using the J-Trace PRO Cortex-M.

I hope you can schedule this bug to be fixed. Thanks
Dan

Hi Dan,

Thank you for your further descriptions.
With them we were able to reproduce the issue and are working on a fix.
It should be available with the next Ozone release planned this week.

Best regards,
Nino

Thanks, version 2.56p seems to have corrected it!

Dan

Hi Dan,

Great to hear that you are up and running again.
This thread will now be marked as solved.

Best regards,
Nino