# Unable to read hardware Clock **URL:** \ **Category:** NXP i.MX8M Plus\ **Tags:** iMX8M-plus\ **Created:** [March 21, 2022, 1:17pm UTC](https://community.solid-run.com/t/unable-to-read-hardware-clock/268 "2022-03-21T13:17:38Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![j-licht](https://avatars.discourse-cdn.com/v4/letter/j/bcef8e/32.png) [@j-licht](https://community.solid-run.com/u/j-licht)\ **Post date:** [March 21, 2022, 1:17pm UTC](https://community.solid-run.com/t/unable-to-read-hardware-clock/268/1 "2022-03-21T13:17:38Z")
Hi, I’m unable to read the hardware clock on my HummingBoard Pulse & i.MX8M Plus. I’m using your hardknott yocto release. Dmesg output: ```auto dmesg | grep rtc-a [5.323718] rtc-abx80x 2-0069: model 1805, revision 2.3, lot 373, wafer 3, uid 53f0 [5.335351] rtc-abx80x 2-0069: Enabling trickle charger: 05 [5.379611] rtc-abx80x 2-0069: Oscillator failure, data is invalid. [5.379998] rtc-abx80x 2-0069: registered as rtc0 [5.391270] rtc-abx80x 2-0069: Oscillator failure, data is invalid. [5.398571] rtc-abx80x 2-0069: hctosys: unable to read the hardware clock [68.654207] rtc-abx80x 2-0069: Oscillator failure, data is invalid. [139.181129] rtc-abx80x 2-0069: Oscillator failure, data is invalid. root@:~# hwclock [180.550011] rtc-abx80x 2-0069: Oscillator failure, data is invalid. hwclock: RTC_RD_TIME: Invalid argument ``` Do you have any hints? Best regards, Jonas ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [March 21, 2022, 1:27pm UTC](https://community.solid-run.com/t/unable-to-read-hardware-clock/268/2 "2022-03-21T13:27:50Z")
These errors will occur until the RTC is programmed with a valid time. This is generally done by the kernel or systemd depending on the configuration. You can do this manually by running the command `sudo hwclock -w`