Date: Sat, 20 Jul 2019 05:24:04 +0300 From: Stefan Parvu <sparvu@kronometrix.org> To: freebsd-arm@freebsd.org Subject: Re: Rasclock (PCF2127 ) Hardware Clock FreeBSD 12.0 Message-ID: <218CD5DF-9484-4FD7-9F7E-ADDB297185BE@kronometrix.org> In-Reply-To: <3C0049D3-5998-49F1-9B1E-A877A85A9268@kronometrix.org> References: <41A4CA5C-B487-490F-8A19-2D51F43E1004@kronometrix.org> <95616620-bbaf-dbc3-49eb-3e2562638d49@bunyatech.com.au> <AB510253-52D9-469C-B06E-5EC73C5F188E@kronometrix.org> <fd9991c4e6aaccb812a59ff86c9c8564ebd1d767.camel@freebsd.org> <74E3E782-8481-4B5B-A0AF-A04590C27D6D@kronometrix.org> <790afcb5f0809a89b45982958a85f1539fec05c7.camel@freebsd.org> <36088812-2135-4433-BC49-0BC433EC6767@kronometrix.org> <c52f9d9ab358ac0dc09af411bf97625945579b4e.camel@freebsd.org> <86CC4711-47AC-45C6-B6D3-71C9FFDD4A91@kronometrix.org> <BE321299-8569-4B2E-98FD-FD5210E1B6AF@kronometrix.org> <A9FD7D2B-9382-4EAE-B245-5F4DE643DBB7@gromit.dlib.vt.edu> <C93E2C64-6280-464D-AB5F-B1E968690CEF@kronometrix.org> <2ec7d7f63de31065b9cab396c662fe24f0107078.camel@freebsd.org> <BD0BE075-9E69-4CB0-826A-5DF2D160E9B1@kronometrix.org> <d71fc4e3db26242ffa817814d6cd92b8899fc2ab.camel@freebsd.org> <EF94BC84-4B8D-455C-952F-4FD1CC5557CE@kronometrix.org> <2AC05799-7D11-4200-8D16-38E3718470BB@kronometrix.org> <91E26684-07A0-4F03-92BC-8D49359B1358@kronometrix.org> <5F33E59B-7EA5-4B8B-A95A-CD1FB569ACDC@kronometrix.org> <6a39f74088d2984b5426e8585b5f7e864a6766f8.camel@freebsd.org> <571EABD9-364C-4D91-9177-CC25CB382D76@kronometrix.org> <A53C9BE4-B3A7-4F15-808F-AB9846674625@kronometrix.org> <2dd107308cb7fc21bab793218d8e37039dbc108e.camel@freebsd.org> <C32068F6-862A-4863-B055-52621209F7D9@kronometrix.org> <F4FB90D0-9777-41EE-9005-9BA441D721A6@kronometrix.org> <b4970b3cf77a854dba71a3319d0ada8619efbd7c.camel@freebsd.org> <77885EA9-6AA4-4106-B447-3A83FB6033BA@kronometrix.org> <B596A43F-6985-4639-9AB3-652CEE8C1387@kronometrix.org> <E6E790AC-D301-4F8E-AA7D-8147B6C9F292@kronometrix.org> <CD36FD00-0EAA-40AF-B05F-43DC51F4A514@kronometrix.org> <C8307F48-6107-43C5-9A40-BB5D1DFAA392@kronometrix.org> <7aafd9f1f1cc072081a14c41a0253e72cd449811.camel@freebsd.org> <89879D9D-9432-44FA-B4E0-A6D3EE969E7A@kronometrix.org> <5F7CD5C3-5107-48BE-B301-3193B4E7A4A2@kronometrix.org> <fa7e500dceb465da76f7160562f4177917f6b55e.camel@freebsd.org> <3C0049D3-5998-49F1-9B1E-A877A85A9268@kronometrix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>=20 > Hmm. I could test first this one. I could set and fix the time. The = power off > the thing for coupld of hours or until morning and then plug it back = to my > board and check if there is any difference. thats a good point. >=20 RTC disconnect / re-connect after 5hrs - the RTC has been unplugged from = the board for 5hrs+. After I reconnect the RTC to the board, power on the system I = can see that the time is correctly retrieved from the RTC.=20 $ dmesg | grep nxp nxprtc0: <NXP PCF2129 RTC> at addr 0xa2 on iicbus0 nxprtc0: registered as a time-of-day clock, resolution 0.015625s So, I can repeat this test to real make sure this is consistent. But = something is making the RTC device to lose time when is installed on the board. Stefan=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?218CD5DF-9484-4FD7-9F7E-ADDB297185BE>