From nobody Sun Feb 20 04:29:06 2022 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0E8FE19C6002 for ; Sun, 20 Feb 2022 04:29:31 +0000 (UTC) (envelope-from archimedes.gaviola@gmail.com) Received: from mail-ej1-x62f.google.com (mail-ej1-x62f.google.com [IPv6:2a00:1450:4864:20::62f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4K1XWt2N2Bz3J0G for ; Sun, 20 Feb 2022 04:29:30 +0000 (UTC) (envelope-from archimedes.gaviola@gmail.com) Received: by mail-ej1-x62f.google.com with SMTP id a23so24581779eju.3 for ; Sat, 19 Feb 2022 20:29:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CntG3f0a+k946cyPyAwzCeY9lil5NNJRR/m3RzpjG3Y=; b=KMVH5Tqi/7sw72aSzjUJHIJJUjETPVA5tvcVR2IDfEWZpiUn4ckR7Pp90IPiJXCv5b WxjwkBo9GASZGMiAz+9blv8FkW/TO8dmaOnESMAM3GxHFXnRNL4GEl3FVZ/x5tJ5g8OX xENqbdLKS2DNt7uTDB3TquyYviJ7nsPVlvTRA2hgkYgP6szC+zIfVRUXENN7OGufL3uF rDemRYSNv6akjkfTGG44bIYc41yorQdv9XAn90cQ3YHAZIcMp2DWzGyxYmvalMgn4LFr Z9K0yjm3VCxrAdwfJ8kUPrNDIQ0uViNLoasv0e/MwsiWODpxMY3wUxEuQy3v6TGiZcZ0 aOGw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=CntG3f0a+k946cyPyAwzCeY9lil5NNJRR/m3RzpjG3Y=; b=XLv+qz9EwogmJnInjeLzLBiiIrYaLxF1sa4mECLv86gFJ/+7wC6ClVbKfUfRY2tFem iBlpbUskK8Nv38m8Vib0c5jVTdXEepy9KJrhnDVX+6dqyiMnD4CQKZjND9Tmtbvr2oUZ khDE2AdVN/MB9+rN4eJCvMQn25VQsgqoRLP+dGDsVCz8CpFRTTY3G3wZewMfmKCNTLuS gViuT8HTkPdhMFFnrU4eze/W3yyE/doqSsXPUkhTKBUzIDOhwoN2YL3rr7MHRb/5nacK Y5FCek7lhWj9P2OQ5Ll5eYZZGqOW7eAbpikwqbA5QilDNLC8A+f6CwVOWUj0W+p0LAcd gkwg== X-Gm-Message-State: AOAM530gC6+KdBsWnLRY3Ixyb/4QAxoe5eqK+f01smx7AXxfRunE1lw0 hY99OaO609TFj89cVPG8cdX0aLW0fOX2F31pDPvkx1hpeqw= X-Google-Smtp-Source: ABdhPJz6vrWfBedA3pQwu8r743+PO3Va3CygaEK82R91aoOmCpBD1eCnyFLYsXqDwYVO4UekkNskhZeHJlNGVHW4T3U= X-Received: by 2002:a17:907:9208:b0:6cf:cd92:c1e7 with SMTP id ka8-20020a170907920800b006cfcd92c1e7mr11844410ejb.282.1645331363637; Sat, 19 Feb 2022 20:29:23 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org MIME-Version: 1.0 References: <2DF482A7-FEFC-4833-A16B-A7A01B8713DD@dons.net.au> <94C3A304-B821-4885-A50D-32BD1FBED43D@dons.net.au> In-Reply-To: <94C3A304-B821-4885-A50D-32BD1FBED43D@dons.net.au> From: Archimedes Gaviola Date: Sun, 20 Feb 2022 12:29:06 +0800 Message-ID: Subject: Re: DS3231 RTC module not detected To: "Daniel O'Connor" Cc: freebsd-arm@freebsd.org Content-Type: multipart/alternative; boundary="00000000000077ad0605d86b8f65" X-Rspamd-Queue-Id: 4K1XWt2N2Bz3J0G X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=KMVH5Tqi; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of archimedesgaviola@gmail.com designates 2a00:1450:4864:20::62f as permitted sender) smtp.mailfrom=archimedesgaviola@gmail.com X-Spamd-Result: default: False [-4.00 / 15.00]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-1.00)[-0.999]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62f:from]; MLMMJ_DEST(0.00)[freebsd-arm]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Status: O Content-Length: 3607 Lines: 76 --00000000000077ad0605d86b8f65 Content-Type: text/plain; charset="UTF-8" On Sun, Feb 20, 2022 at 11:51 AM Daniel O'Connor wrote: > > > > On 19 Feb 2022, at 22:49, Archimedes Gaviola < > archimedes.gaviola@gmail.com> wrote: > > Thanks for your feedback Daniel! With the exact DS3231 driver all the > concerns I've mentioned were answered. Once it is set manually via date or > ntpdate, the clock will now continue even if your system is shutdown (with > unplug power cable) or even detaching the module from the RPi4 system for > some time and then attaching it back will now be "real-time". > > > > You can bring your DS1307 with the exact driver as well. Thanks a lot > for your help, it is well appreciated. > > > When you say "with the exact DS3231 driver.." what do you mean? > I mean the appropriate DS3231 driver - ds3231(4) for the module which is a kernel loadable as the dominating driver with 13.0-RELEASE and 14.0-CURRENT which is MAX77620 RTC is the wrong one thus the module will not work properly. The clock stops and goes back to the time when you set it. This behavior is observable when my RPi system is rebooted or shutdown. With the loadable ds3231 driver, this behavior is no longer observed and working as expected. For your DS1307, there's also an equivalent and perhaps the appropriate driver as described in the manual ds1307(4), it can be loaded as well via kldload. Thanks, Archimedes --00000000000077ad0605d86b8f65 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Sun, Feb 20, 2022 at 11:51 AM Dani= el O'Connor <darius@dons.net.a= u> wrote:


> On 19 Feb 2022, at 22:49, Archimedes Gaviola <archimedes.gaviola@gmail.com> wrote:
> Thanks for your feedback Daniel! With the exact DS3231 driver all the = concerns I've mentioned were answered. Once it is set manually via date= or ntpdate, the clock will now continue even if your system is shutdown (w= ith unplug power cable) or even detaching the module from the RPi4 system f= or some time and then attaching it back will now be "real-time".<= br> >
> You can bring your DS1307 with the exact driver as well. Thanks a lot = for your help, it is well appreciated.
>
When you say "with the exact DS3231 driver.." what do you mean?

I mean the appropriate DS3231 driver - ds3231= (4) for the module which is a kernel loadable as the dominating driver with= 13.0-RELEASE and 14.0-CURRENT which is=20 MAX77620 RTC is the wrong one thus the module will not work properly. The clock stops an= d goes back to the time when you set it. This behavior is observable when m= y RPi system is rebooted or shutdown. With the loadable=C2=A0 ds3231 driver, this behavior is no longer observed and working as expected. For y= our DS1307, there's also an equivalent and perhaps the appropriate driv= er as described in the manual ds1307(4), it can be loaded as well via kldlo= ad.

Thanks,
Archimedes
--00000000000077ad0605d86b8f65--