Official RTC Shield for Odroid C2

GDPR-1 · October 4, 2016 at 3:26 PM

No. DTS entry was missing. You have to wait for the next release.
[hr]
blackride but you can use that command from a Ubuntu PC and locate the file meson64_odroidc2.dtb on microsd card.

blackride · October 4, 2016 at 4:47 PM

Quote from Raybuntu

No. DTS entry was missing. You have to wait for the next release.
[hr]
blackride but you can use that command from a Ubuntu PC and locate the file meson64_odroidc2.dtb on microsd card.

i tried

Code

wget https://github.com/LibreELEC/linux-amlogic/pull/15/commits/07af642962064d035fdd165074566ef39e51b8b1.diff -O rtc.patch

But

Code

am@G-Mason:~/LibreELEC.tv/projects/Odroid_C2/patches/linux$ wget https://github.com/LibreELEC/linux-amlogic/pull/15/commits/07af642962064d035fdd165074566ef39e51b8b1.diff
--2016-10-04 21:41:45--  https://github.com/LibreELEC/linux-amlogic/pull/15/commits/07af642962064d035fdd165074566ef39e51b8b1.diff
Распознаётся github.com (github.com)... 192.30.253.112
Подключение к github.com (github.com)|192.30.253.112|:443... соединение установлено.
HTTP-запрос отправлен. Ожидание ответа... 404 Not Found
2016-10-04 21:41:47 ОШИБКА 404: Not Found.

GDPR-1 · October 4, 2016 at 4:58 PM

blackride: You seem to have not understand what I meant. Just be patient. Bug has been found and fixed. Wait for the next alpha build.

blackride · October 5, 2016 at 12:39 PM

Quote from Raybuntu

blackride: You seem to have not understand what I meant. Just be patient. Bug has been found and fixed. Wait for the next alpha build.

I'm sorry.
I did not wait, and compile my image LE with your patch and RTC works!
My image here
Thank you Raybuntu, wrxtasy and other developers

GDPR-1 · October 5, 2016 at 1:38 PM

I'm sorry blackride but what you are writing doesn't make sense. The fdtput command is not suppose to be put in boot.ini!? fdtput is part of device-tree-compiler scripts that afaik are neither included in uboot nor LibreELEC!?

blackride · October 6, 2016 at 4:59 AM

Quote from Raybuntu

I'm sorry blackride but what you are writing doesn't make sense.

Please tell me. Thank you.

What is the working principle?
I can not understand.
If my system time eg 10:00.
I request command hwclock -r. The command says 6:00
Then I write to the memory RTC module the command hwclock -w.
And again I am requesting command hwclock -r. The command says 10:00. OK

I reboot. Requesting command hwclock -r. The command says 6:00.
It turns out that every time you boot LE overwrites the memory module the RTC?

GDPR-1 · October 6, 2016 at 6:38 AM

seems like you write utc time and but restore local time or the otherway around.

blackride · January 12, 2022 at 2:41 PM

I would like to return to this topic. I don't quite understand. But I think that the logic of work for the pcf8563 module is not built correctly. Why add this feature to the kernel if it doesn't work?

"If my system time eg 10:00.

I request command hwclock -r. The command says 6:00

Then I write to the memory RTC module the command hwclock -w.

And again I am requesting command hwclock -r. The command says 10:00. OK

I reboot. Requesting command hwclock -r. The command says 6:00."

Can anyone explain how to set the time on the module so that when the system is rebooted, the time in the module remains the same?