given you can refresh watched data at up to a few Hz in the background on MPUs that don't support the full high speed sampling mechanism over JTAG, why does the Timeline / data sampling?

using J-Trace with Cortex A5D27 which doesn't support the full high speed background refresh

this appears in the console


Hardware setup does not support data sampling.
Current setup does not support background memory access mode
Error (84): Failed to start high speed sampling (HSS).

i don't see why the mechanism for flushing the data from the processor should matter to being able to graph / do stats on a variable ( which does appear in the data sampling window but obviously doesn't update ) given that as the user we know and understand the sampling restrictions of the hardware platform

you can't graph watched variables when using the emulated background JTAG refreshing [ Cortex A5D27 doesn't support high speed live watches according to ozone so is starting and stopping the MPU to read the values ]

they do happily slowly update which is fine given you only get 5Hz updating

but you can't graph the vatiables

VAR_ALLOW_BMA_EMULATION is on and has been - hence i said I have seen and understood the massive difference in update rates for this mode of operation being limited to 5Hz but sample rate is no issue for this

this is what happens when i try and use this

"tick" is added as a watch, set to refresh at 1Hz and it does indeed update in the watch window at 1Hz

when then try to graph "tick" then you just spit out a bunch of error messages in the console

which contradicts what the manual / you say

that looks enough to show the isuse

you can see that in the image of the project file startup script