In some cases, the Expressions view can display invalid values for variables. This has been observed on targets with real-time memory access support. It does not impact all variables.

The issue was first obersrved (and locally reproduced) on an F280049C LaunchPad, which has real-time debug support.

Some obervations when running a provided test case:

1. If I simply run the target and view the variable in the expressions view with continuous refresh enabled (like you have in your video), The issue is reproduced.
2. If I continuously step over the source lines in the while loop, the issue is not reproduced (only the expected values for the variable appear)
3. If I set a breakpoint somewhere in the while loop (for example on line 28) and run the target and let it halt on the breakpoint and then run again and repeat, the issue is not reproduced.
4. If I disable continuous refresh and run the target without any breakpoints, the variable will change to an invalid value and remain so until the target is manually halted (then which a valid value will appear).
5. If I enable the debugger option to always halt the target before target access, then the issue goes away even with continuous refresh enabled and the target is left running (though halting under the hood when memory is read).