Thanks
I did a tweak. I soldered to Pin3 (left side 3rd from top) on the microcontroller , after looking at the pin diagram.
DS3231 RTC module for Raspberry Pi (HCRASP0009)
-
- Posts: 7
- Joined: Sat Aug 08, 2020 11:09 pm
Re: DS3231 RTC module for Raspberry Pi (HCRASP0009)
Can someone please help with a pin diagram for this module? I am trying to use it with Raspberry Pi Pico. All help is appreciated.
Re: DS3231 RTC module for Raspberry Pi (HCRASP0009)
I've added an image showing the pinout of the module to the first post. Hope this helps.
Comments made by this poster do not necessarily reflect the views of Hobby Components Ltd.
Re: DS3231 RTC module for Raspberry Pi (HCRASP0009)
It's probably your browser cashing the old page. If it's still doing it and assuming your using a computer try doing a CTRL-SHFT-R to refresh the page, that usually fixes it. Failing that try looking at the page in private view/incognito mode.
Comments made by this poster do not necessarily reflect the views of Hobby Components Ltd.
Re: DS3231 RTC module for Raspberry Pi (HCRASP0009)
Rpi4/Buster - RTC supplied by Hobby Components - DS3231 RTC module for Raspberry Pi (HCRASP0009)
Install as per instruction here - part way through - get to "Reading the current time from the module:"
but i get an apparently bad response from the commend
sudo hwclock --verbose -r
hwclock from util-linux 2.33.1
System Time: 1640618062.955225
Trying to open: /dev/rtc0
Trying to open: /dev/rtc
Trying to open: /dev/misc/rtc
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.
Can't find any info to resolve - before proceeding regardless using the instructions - should I continue ? or turn back ? if the latter how to recover ?
Noting that /dev/modules only has i2c-dev
and that i2cdetect -y 1 shows 68 only
And /boot/config.txt appears to have nothing in there for rtc or i2c
ls -l on /dev shows i2c-1 but no rtc devices
I know I made a typo with the echo statement to make the /sys/class so that ds1307 became ds3107 but I cant find any impact of that - unfortunately I cant find a way to remove that /sys/class/i2c-adapter/i2c-1 entry.
rmmod says its not loaded
.
This is a pi with a lot of stuff loaded so I dont want to scrub restart if at all possible.
Thanks Gray
Install as per instruction here - part way through - get to "Reading the current time from the module:"
but i get an apparently bad response from the commend
sudo hwclock --verbose -r
hwclock from util-linux 2.33.1
System Time: 1640618062.955225
Trying to open: /dev/rtc0
Trying to open: /dev/rtc
Trying to open: /dev/misc/rtc
No usable clock interface found.
hwclock: Cannot access the Hardware Clock via any known method.
Can't find any info to resolve - before proceeding regardless using the instructions - should I continue ? or turn back ? if the latter how to recover ?
Noting that /dev/modules only has i2c-dev
and that i2cdetect -y 1 shows 68 only
And /boot/config.txt appears to have nothing in there for rtc or i2c
ls -l on /dev shows i2c-1 but no rtc devices
I know I made a typo with the echo statement to make the /sys/class so that ds1307 became ds3107 but I cant find any impact of that - unfortunately I cant find a way to remove that /sys/class/i2c-adapter/i2c-1 entry.
rmmod says its not loaded
.
This is a pi with a lot of stuff loaded so I dont want to scrub restart if at all possible.
Thanks Gray
Re: DS3231 RTC module for Raspberry Pi (HCRASP0009)
The device name in the echo command will matter and so that's what's probably causing the problem. But the first thing to do is confirm that everything before the ‘Configuring the module’ section worked ok. Run the following command again to check that it is seeing the RTC on I2C address 68:
If it’s reporting the I2C address of the module correctly you can move on to the next step:
The echo step in the ‘Configuring the module’ section should not be permanent so simply rebooting your pi should undo it. So if you haven’t already, reboot your pi and you should be able to repeat that section with the correct device name. If that fixes the error you can then continue the guide from there.
Code: Select all
sudo i2cdetect -y 1
If it’s reporting the I2C address of the module correctly you can move on to the next step:
The echo step in the ‘Configuring the module’ section should not be permanent so simply rebooting your pi should undo it. So if you haven’t already, reboot your pi and you should be able to repeat that section with the correct device name. If that fixes the error you can then continue the guide from there.
Comments made by this poster do not necessarily reflect the views of Hobby Components Ltd.