Re: DS3231 RTC module not detected

Archimedes Gaviola <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <CAJFbk7FVOjg0zP-WKhKP3ANeGrOiUsEt_9YqGQX2V2inQ16tdg@mail.gmail.com>
On Mon, Feb 21, 2022 at 7:29 PM Daniel O'Connor <[email protected]> wrote:

>
>
> > On 21 Feb 2022, at 21:50, Archimedes Gaviola <
> [email protected]> wrote:
> > Did you re-compile your kernel? Brian has shared his resolution on
> customizing the GENERIC kernel here
>
> No I didn't realise it was necessary :)
>

Yes it is :-)


>
> > https://lists.freebsd.org/archives/freebsd-arm/2022-February/001024.html
> which allows to free-up the i2c address 0x68 which by default is being used
> by the MAX77620 RTC driver from the SOC_NVIDIA_TEGRA210. So, you need to
> add these lines in your kernel (I assume it's still the GENERIC otherwise
> use your existing config),
> >
> > include         GENERIC
> > ident             GENERIC-PI
> > nooptions     SOC_NVIDIA_TEGRA210
> >
> > and then recompile. Keep your /boot/msdos/config.txt and
> /boot/msdos/overlays/ds1307.dtbo files intact. After recompiling and
> rebooting, you can check the dmesg if the ds1307 driver is loaded,
> otherwise invoke "kldload ds1307" and see if it's detected. Add a line into
> your /boot/loader.conf with ds1307_enable="YES" if necessary. Lastly,
> kindly backup your data before recompiling for safety.
> >
> > This is the way I do it with my ds3231 driver, hope you will get the
> same result.
>
> Thanks.
>


You're welcome.


>
> I chatted to some people on IRC and I think it's fixed in a later version
> anyway with these commits:
>
> https://cgit.freebsd.org/src/commit/?id=1bd3e8ba696633ccd7525030d951b58ade167814
>
> https://cgit.freebsd.org/src/commit/?id=a534b50e245d801af887d91b5d48ebcf120aa039
>
>
Wow, this is good news...


> Although I have not been brave enough to update to HEAD and try it yet :)
>

Yeah, better to wait than meet a lot of surprises with HEAD :-)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.