Look at the link in /dev/rtc:
ls -al | grep rtc
If you got it to point at /dev/rtc1, I would very much like to know how you
accomplished that!
On Friday, July 28, 2017 at 10:09:19 AM UTC-4, William B wrote:
>
> Greg, it's okay. I was able to make the RTC be recognized as rtc1 in the
> system.
Only /dev/rtc0 is going to be updated automatically. /dev/rtc1 is not
going to be updated automatically, as far as I can determine, with the
Debian distributions as published.
You would have to use the config tools to switch from rtc0 to rtc1 and
compile a new kernel.
So the common scheme you
Greg, it's okay. I was able to make the RTC be recognized as rtc1 in the
system. Just turned off the BBB, disconnected everything that was connected
to the hardware and starts again. I'm sure the RTC module was properly
connected to the BBB, so I believe that there could only be some
Greg,
I'd just like to prevent the RTC from being updated with the system date
and time so that I can even use a script to do this task when I need to.
How do I prevent the RTC from being updated automatically?
Command response "timedatectl"
root@beaglebone:~# timedatectl
Local time: Fri
There is lots of stuff going on, and it is messy. Check out this link:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785445
I tried the configuration via udev, but as reported in the above link, it
doesn't work.
Apparently the only way to get the /dev/rtc link to point to rtc1 instead
of
Actually what is happening is this: when I remove the power from the BBB,
the date and time return to the default setting. Because the RTC is
automatically associated with system time auto-tuning, then its time is
also being changed incorrectly (I had not noticed this in reboot because it
is
Well, rtc0 is most likely the on AM335x on die real time clock, which will
not persist time across reboots.
On Thu, Jul 27, 2017 at 7:54 PM, William B wrote:
> Finally I got ... the last hint from William Hermans indicated me
> something about the device name, which could
William,
Also to save you from future grief. Make sure you load the proper drivers
for your hardware,then if you're going to write your own software to read
from the RTC. Use /dev/rtcx( probably /dev/rtc1 ), and do not try to read
directly from the RTC over I2C. Trust me . . .
On Thu, Jul 27,
On Thu, Jul 27, 2017 at 4:24 PM, William B wrote:
> Is there any other difference in this latest version of Debian? I'm
> following a tutorial below, but the command "hwclock -r -f /dev/rtc1" is
> indicating failure to communicate with the new device:
>
> *TUTORIAL*:
>
Is there any other difference in this latest version of Debian? I'm
following a tutorial below, but the command "hwclock -r -f /dev/rtc1" is
indicating failure to communicate with the new device:
*TUTORIAL*:
https://learn.adafruit.com/adding-a-real-time-clock-to-beaglebone-black/set-rtc-time
On Thu, Jul 27, 2017 at 3:02 PM, William B wrote:
> *Grahan:*
> You're 100% correct. Running "i2cdetect -y -r 2" instead of "1" at the
> end, it detected the RTC at address 0x68, as we can see in the available
> tutorials.
> Answering your question, I'm using the latest
*Grahan:*
You're 100% correct. Running "i2cdetect -y -r 2" instead of "1" at the end,
it detected the RTC at address 0x68, as we can see in the available
tutorials.
Answering your question, I'm using the latest available Debian release
(bone-debian-8.8-iot-armhf-2017-07-01-4gb.img) available
It's not so much the debian version, as it is the kernel. kernel 3.8.x is
different from kernel 4.x. The easiest way to see what is attached it this:
root@wgd:~# i2cdetect -l
i2c-0 i2c OMAP I2C adapterI2C adapter
i2c-1 i2c OMAP I2C adapter
What version of Debian are you running.
On Debian 8, what was in the docs as I2C-1 is now I2C-2.
Hook your translator to pins P9-19 and P9-20 and run "i2cdetect -y -r 2"
I2C-2 is enabled in the device tree by default.
--- Graham
==
--
For more options, visit http://beagleboard.org/discuss
On Thu, Jul 27, 2017 at 1:24 PM, William B wrote:
> Hi!
> I bought the I2C logic converter 3.3V => 5v and I've connected the RTC to
> the BBB, but running "i2cdetect -y -r 1" doesn't find the RTC device. I've
> checked the wiring of the connections and I repeated the process
Hi!
I bought the I2C logic converter 3.3V => 5v and I've connected the RTC to
the BBB, but running "i2cdetect -y -r 1" doesn't find the RTC device. I've
checked the wiring of the connections and I repeated the process a few
times, but it doesn't detect the RTC.
Any suggestion?
--
For
Here is what I used:
https://www.seeedstudio.com/Grove-High-Precision-RTC-p-2741.html
I'm using the Greens so it conveniently plugs in to the Grove connector.
The lithium coin cell was not available at the local stores and I had to
order via Amazon.
This device uses 3.3V battery and it is
John, I get it. But I do not know how it would be possible to do this in my
DS1307 module which is of this type:
http://www.ebay.com/itm/5-PCS-I2C-RTC-DS1307-AT24C32-Real-Time-Clock-Module-For-AVR-ARM-PIC-/172308340060?epid=846722400=item281e609d5c:g:VxcAAOSwawpXsn0J
How would It connect to
18 matches
Mail list logo