I have a problem with time on OrangePi One - it can’t synchronize time without manual date set. Because of that it can’t connect to my OpenBalena instance, because of “future” certificate.
I don’t know why. It shows /dev/rtc0 without rtc connected (fake-hwclock?)
I tried to connect ds3231 rtc clock on OrangePi One pinout, but without success. i2c is not enabled, and i can’t enable it by simple way (no support for raspberry-like overlay environment).
Is there any way to enable it?
I know that one of the solution will be to dive into the Yocto, and prepare it somehow itself, but maybe there is some out of the box way?
If not, do you have some materials/tutorial how to prepare yocto with balena?
SPI Devices also are not supported on OrangePi One, is there any solution to enable it?
Regarding Yocto, if it is related to a balenaOS build then sure, though I would suggest that you create a new thread if it is not directly related to this issue with the clock. Let us know when you have the output of the commands as described above to help us debug this one.
Thanks for the output which I’m looking at now and sorry I misunderstood your last Yocto comment. Regarding an environment, you could try this Docker setup from one of my colleagues, which I’ve used successfully and has all the required dependencies for building balenaOS https://github.com/alexgg/docker-balena
Thanks for the above output. From looking at the logs it seems it is synced and no NTP sources are unreachable. Do you see issues when restarting chrony or just on a system reboot i.e. can you try systemctl restart chronyd.service?
To enable further debugging you could also enable support access for this device and share the UUID and we can take a closer look at it?
Please ignore that comment about gaining access, I missed this was openBalena. Can you just restart chrony and not reboot the device systemctl restart chronyd.service and then provide the full chrony logs via journalctl --no-pager -n 400 -u chronyd.service?
From new orange pi one
root> @a0af15b:~# journalctl --no-pager -n 400 -u chronyd.service
– Logs begin at Thu 1970-01-01 00:00:23 UTC, end at Wed 2020-03-11 09:43:32 UTC. –
Mar 23 12:40:23 localhost systemd: Started NTP client/server.
Mar 23 12:40:23 localhost chronyd: 2019-03-23T12:40:23Z chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP -SCFILTER -SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG)
Jan 01 00:00:24 localhost chronyd: 1970-01-01T00:00:24Z System time set from RTC
Mar 11 09:43:32 a0af15b chronyd: 2020-03-11T09:43:32Z Forward time jump detected!
Mar 11 09:43:32 a0af15b chronyd: 2020-03-11T09:43:32Z chronyd exiting
Mar 11 09:43:32 a0af15b systemd: Stopping NTP client/server…
Mar 11 09:43:32 a0af15b systemd: Stopped NTP client/server.
Mar 11 09:43:32 a0af15b systemd: Started NTP client/server.
Mar 11 09:43:32 a0af15b chronyd: 2020-03-11T09:43:32Z chronyd version 3.2 starting (+CMDMON +NTP +REFCLOCK +RTC -PRIVDROP -SCFILTER -SECHASH -SIGND +ASYNCDNS +IPV6 -DEBUG)
Mar 11 09:43:32 a0af15b chronyd: 2020-03-11T09:43:32Z RTC time before last driftfile modification (ignored)
Mar 11 09:43:32 a0af15b chronyd: 2020-03-11T09:43:32Z Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/drift
It’s available also for support now, cause i connected it to Balena according this:
Hi Adam, thanks it would be good to get access to the device. Could you also mention what version of the OS you are running. It might be worth trying the 2.46.1 OS we have in our staging environment currently to see if it presents with the same problem.
Hi, yes its available for download in our staging environment at https://dashboard.balena-staging.com/login , you will need to create a new account and app there. There you should be able to download the 2.46.1 and then all that you need to do is take your config.json from the production balenaCloud and put it on the SD card in /resin-boot , this will allow that 2.46.1 image to connect to the balenaCloud production servers and you can continue testing as you have before.
Trying to make sense of this thread as it seems that we have a lot of moving parts here. Could you clarify a few points for the sake of anyone reading this far:
So my plan is to build custom orange-pi-one balenaOS image with some additional features like: i2c support…
Did you manage to do this? It seems from the logs you posted that chrony managed to set the time from the RTC and you also mentioned that you had connected it to balena. It would be good to know if you have a working image (self built) and what was required if so.
i2c still doesn’t existsm also spi
I am assuming this is using our stock balenaOS 2.46.1 image?