TSC timestamp when nvpps is disabled or ptp is not synching

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.8.1
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.3.10904
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

If instead of programming fsync_start time and ptp synchronization is not working, how do you access the TSC at any given time? If I use the ioctl(m_fd, NVPPS_GETEVENT, &m_ts) - unless ptp is also working, the tsc field is 0 as well as the ptp field, but fsync_triggering is working because I get the expected FPS. How would I get the TSC if the ioctl call does not return it?

Dear @collin.day,

Is it like you want to know TSC value using come command at a given instance?

More like - as an example - is the C++ steady_clock an interface to the TSC?

If not ioctl call, you can check accessing register value to find TSC value. Does that work for you?

That would work - what is the register address of the TSC?

Dear @collin.day ,
high & low TSC tick value store at different register. find them using below registers.

devmem2 0x0c6a0010 —> A
devmem2 0x0c6a0014----> B

Current TSC tick is A + (B << 32) . Each TSC tick is 32ns.