On 05/29/2014 09:31 PM, Joshua Datko wrote:
The RTC uses the ds1307 kernel driver and you're correct, it shows up
as rtc1. It is loaded when the capemgr instantiates the device tree,
since the driver is in the CryptoCape DTS file. So you shouldn't need
any init.d/systemd scripting it should "just work"TM.
Yes, this is nearly identical to the setup I did. Created a dto for the
ds1307, loaded it at boot, all good. The device is there, it has very
good time. The system still needs to be told to *use* that time.
If memory serves Robert updates a time value that gets loaded so if your
on a fairly current image your time is somewhat current.
I'll be more than happy to RTFM, or experiment if pointed in the right
direction. I've not seen any indication that simply adding a battery
backed RTC, loading it via capemgr will cause the system (kernel) to use
that device for obtaining a somewhat sane time value.
Mike
You'll have to set the clock once and then it should hold pretty well.
In testing think I had a bum battery b/c it depleted rather quickly.
Once I changed batteries it seems to be holding steady.
On Thu, May 29, 2014 at 7:28 PM, Mike <bellyac...@gmail.com
<mailto:bellyac...@gmail.com>> wrote:
On 05/29/2014 07:17 PM, Joshua Datko wrote:
The CryptoCape, a collaboration between SparkFun and myself,
is now available for purchase at SparkFun Electronics [1]. In
short, the cape adds some hardware crypto chips, a RTC with
battery, and an ATmega328p which is designed to be flashed
from the Beagle. It will be officially announced on the "new
products Friday" post tomorrow, but I think this group
deserved an early announcement.
Thanks to BeagleBoard.org for making a great platform and
special thanks to Robert Nelson for backporting the TPM driver
to 3.8.
This community is awesome; I've learned so much by following
this list. Thanks to everyone who shares their time and knowledge.
There's only 1 left :)
Happy Hacking!
Josh
[1] https://www.sparkfun.com/products/12773
How is the RTC implemented at the software level? More to the
point perhaps, how early in the boot process does the system time
get set from (presumably) rtc1?
About a month or so ago I setup a battery backed RTC, along with a
fairly current systemd. Systemd have chosen to rewrite hwclock
and last I looked it still only honored/used rtc0. Perhaps I
didn't explain the situation good enough on the systemd mailing
list, but I couldn't seem to get past anyone not understanding why
a board wouldn't have a battery backed RTC on board. Having said
all that I did get it working just using init.d scripts. Just
seems like such an ugly hack when the whole point of systemd is to
essential do away with all the scripts.
The board looks like something very interesting to explore. I'm
sure one will find its' way here when cash flow permits.
Mike
--
For more options, visit http://beagleboard.org/discuss
--- You received this message because you are subscribed to a
topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/beagleboard/NhMSP9ywlzg/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to beagleboard+unsubscr...@googlegroups.com
<mailto:beagleboard%2bunsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google
Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to beagleboard+unsubscr...@googlegroups.com
<mailto:beagleboard+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
