Physical counter in juno board

Hi,

That's confusing, it's not what I see on my board.

Although you haven't said what the magnitude of the difference is that's concerning you.

A couple of thoughts:

• Although the System Timer count is based on a common timebase, the architecture allows for some flexibility (latency when reading via different observers/mechanisms) as long as time can't be seen to go backwards. So I wouldn't necessarily expect to see the same count in such a test, just similar counts.
• Note the debugger will read the register once on entry to debug state and effectively show a "cached" value. You need to manually refresh the view it to get an updated reading.

Hi,

That's confusing, it's not what I see on my board.

Although you haven't said what the magnitude of the difference is that's concerning you.

A couple of thoughts:

• Although the System Timer count is based on a common timebase, the architecture allows for some flexibility (latency when reading via different observers/mechanisms) as long as time can't be seen to go backwards. So I wouldn't necessarily expect to see the same count in such a test, just similar counts.
• Note the debugger will read the register once on entry to debug state and effectively show a "cached" value. You need to manually refresh the view it to get an updated reading.