Physical counter in juno board

Curiosity forced me to try this in DS-5, with Linux booted on a Juno board. [All cores are halted in debug state at EL1 Non Secure, AArch64].

When I refresh debugger's register view I can see CNTPCT_EL0 reflecting the incrementing System Timer. I see the same values reflected in all core's registers (or at least as close to the same as the delay in refreshing one view after another) will allow.

So reassuringly this test matches the expected behaviour.

Curiosity forced me to try this in DS-5, with Linux booted on a Juno board. [All cores are halted in debug state at EL1 Non Secure, AArch64].

When I refresh debugger's register view I can see CNTPCT_EL0 reflecting the incrementing System Timer. I see the same values reflected in all core's registers (or at least as close to the same as the delay in refreshing one view after another) will allow.

So reassuringly this test matches the expected behaviour.

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 Mark,

I tried reading the values in DS-5.

Reading CNTPCT_EL0 register in EL2 (Hypervisor mode) in AArch64 state results in this value. Also, I observed a similar behaviour when I read the memory mapped CNTCV value (0x2a800000).

Secondary core reports a lower value than the primary core as time goes by.

Thanks,

Gowthami