Thank you Juggler.
Yup the only reason I was thinking of the RTC device pictured is that I used that one for a microrouter openwrt project doing a bit of bit banging and soldered a 1-wire temperature sensor to the RTC board.
and I have done similiar with the RPi2 (well two of them now).
With the NIC rom and the RTC then the Joggler will be much closer to a regular computer. I am currently using many of them as touch interfaces to my automation mothership.
I do manage them via name, MAC and IP via the mothership today.
I am trying to short cut this a bit and making many assumptions.
There is a little lithium battery on the Openpeak 2 devices and I have no ideal if there is a charging circuit and where the battery goes to. It does work though as when I read the hardware clock I see the actual time with no network connection configured.
I see some stuff with stock build. Guessing if I just add the RTC clock I may see something using i2cdetect without doing much; then from there and the addresses just go to the bit banging part of it.
I have not really ever played with a logic analyzer but did get in to ham radio stuff in the 1960's and building stuff back then. Getting 5VDC from the board shouldn't be an issue and the 1-wire temperature sensor would just be an add. The Openframe device uses a massive metal heatsink in it so I really don't need to watch the temperatures.
root@ICS-Ubuntu-Buzz:~# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
Code: Select all
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- 34 -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
If the hardware works well together, it will still be necessary to read the time from the RTC module at boot time and at specific intervals to update and keep the Joggler's infamously drifting clock, more or less accurate.
Well here I was going to just do some bit banging at boot if it works similiar to what I did with my openwrt microrouter. There just tapped a couple of free GPIO ports though.
Here is how I am starting the openwrt microrouter to read the RTC clock.
root@ICS-GLiNet:~# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
Code: Select all
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
root@ICS-GLiNet:~#
UU is at 0X68
echo ds1307 0x68 > /sys/bus/i2c/devices/i2c-0/new_device
if hwclock | grep 'Jan' | grep -q 2000 ; then
logger "RTC appears to have a flat battery..."
else
logger "RTC set hwclock"
hwclock -s
So it looks like you are using a radio receiver for your time sync eh?
Here all of the clocks on the walls in the house use radio to sync time. They work OK though not great as here in Chicago I am getting time sync from Colorado. I do have a GPS with PPS connected to my PFSense Firewall and that works pretty good.