I use the commands “sudo hwclock --hctosys --utc --rtc /dev/rtc0 --noadjfile” and “sudo hwclock --show --utc --rtc /dev/rtc0 --noadjfile” to set the RTC time to the system time and read the current RTC time respectively. However, every time I power off and then restart the system and run these two commands, an error occurs: “hwclock: select() to /dev/rtc0 to wait for clock tick timed out”. What causes this issue?
*** Please note that this reply is generated by LLM automatically ***
The issue you’re experiencing with the hwclock command on your Jetson Orin Nano system is related to the Generic Timestamp Engine (GTE) and the Real-Time Clock (RTC) synchronization.
The hwclock command is used to set and display the system time, and it relies on the GTE to provide the timestamp functionality. However, the GTE is not enabled by default on the Jetson Orin Nano platform.
When you run the sudo hwclock hctosys utc rtc devrtc0 noadjfile command, it attempts to set the system time to the RTC time, but it fails because the GTE is not enabled, causing the hwclock command to timeout while waiting for the clock tick.
Similarly, when you run the sudo hwclock show utc rtc devrtc0 noadjfile command, it attempts to read the current RTC time, but it also fails due to the same reason.
To resolve this issue, you need to enable the GTE on your Jetson Orin Nano platform. You can do this by loading the GTE kernel device driver (GTE kernel device driver is not explicitly mentioned in the context, but it is assumed to be available) and configuring the GTE to provide the timestamp functionality.
Alternatively, you can use the jetson_clocks utility to max out the SOC clocks and speed up the execution, which may help to alleviate the issue. However, this is not a guaranteed solution and may not work every time.
It’s worth noting that the Jetson Orin NX series and Jetson Orin Nano series modules have different power management characteristics, and the hwclock command may behave differently on these platforms. However, the root cause of the issue is likely related to the GTE and RTC synchronization, which is common to both platforms.
In comparison, the Jetson AGX Orin and Jetson AGX Xavier series modules may have different power management characteristics and may not exhibit the same issue with the hwclock command. However, without further information, it’s difficult to say for certain.
To summarize, the issue you’re experiencing with the hwclock command on your Jetson Orin Nano system is likely related to the GTE and RTC synchronization, and enabling the GTE and configuring it to provide the timestamp functionality should resolve the issue.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
How to confirm that GTE is enabled on the Jetson Orin Nano platform and how to enable GTE
Checking below for GTE.
Thank you for your reply. I’ll go try it first.
The document mentions that “Starting from JP 6.0, the Generic Timestamp Engine (GTE) driver has been marked as deprecated and replaced by the Hardware Timestamp Engine (HTE) from the upstream kernel.” This is the information related to my device. However, I have not been able to find the HTE module. How should I solve this problem? Thank you.
Please check the JP6 document.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.