NSLU2-Linux
view · edit · print · history

Info.RTCChipInfo History

Hide minor edits - Show changes to markup

March 22, 2010, at 09:24 PM by PatrickB -- added link and information to RTC alarm wakeup
Added lines 42-43:

The RTC is capable of waking up the NSLU2, see http://johnarthur.wordpress.com/2008/06/26/a-battery-powered-time-lapse-camera/. According to the comments a Linux kernel from 2.6.26rc-9 on should contain the patch correcting an issue preventing setting the alarm. Hardware-modifications are shown there as well. But it seems to be that you need a special program to set the alarm clock, which you can find on the pade as well.

July 09, 2008, at 02:43 PM by fred --
Added line 41:
July 09, 2008, at 02:42 PM by fred -- ForcePowerAlwaysOn - quetion
Changed lines 40-41 from:

The Chip also has an /INT interrupt pin, which does not seem to be connected to other Hardware on the board. Maybe an alarm time could be set by software so that with hardware modification the slug could be woken up.

to:

The Chip also has an /INT interrupt pin, which does not seem to be connected to other Hardware on the board. Maybe an alarm time could be set by software so that with hardware modification the slug could be woken up. Has anybody tried to connect the /INT pin to the ForcePowerAlwaysOn-hack?

October 07, 2007, at 12:26 PM by marceln -- remove false wiki links
Changed line 20 from:

Error: root@LKG62CC02?:~# date

to:

Error: root@LKG62CC02:~# date

Changed line 22 from:
       root@LKG62CC02?:~# hwclock -lw
to:
       root@LKG62CC02:~# hwclock -lw
Changed line 24 from:
       root@LKG62CC02?:~# hwclock
to:
       root@LKG62CC02:~# hwclock
Changed line 26 from:
       root@LKG62CC02?:~# hwclock
to:
       root@LKG62CC02:~# hwclock
Changed line 30 from:
  root@LKG62CC02?:~# date 011317402006
to:
  root@LKG62CC02:~# date 011317402006
Changed lines 32-33 from:
  root@LKG62CC02?:~# hwclock -lw
  root@LKG62CC02?:~# hwclock
to:
  root@LKG62CC02:~# hwclock -lw
  root@LKG62CC02:~# hwclock
Changed line 35 from:
  root@LKG62CC02?:~# hwclock
to:
  root@LKG62CC02:~# hwclock
October 07, 2007, at 11:17 AM by PatrickB -- Interrupt
Changed line 40 from:

He Chip also has an /INT pin, which does not seem to be connected to other Hardware on the board.

to:

The Chip also has an /INT interrupt pin, which does not seem to be connected to other Hardware on the board. Maybe an alarm time could be set by software so that with hardware modification the slug could be woken up.

May 05, 2007, at 09:08 PM by PatrickB -- INT pin not connected
Added lines 38-40:

He Chip also has an /INT pin, which does not seem to be connected to other Hardware on the board.

January 13, 2006, at 09:56 AM by bbo --
Deleted lines 37-56:

bbo: Error: root@LKG62CC02?:~# date

       Fri Dec 31 00:00:41 UTC 1999
       root@LKG62CC02?:~# hwclock -lw
       hwclock: Could not set the RTC time: Invalid argument
       root@LKG62CC02?:~# hwclock
       Fri Dec 31 00:00:00 1999  0.000000 seconds
       root@LKG62CC02?:~# hwclock
       Fri Dec 31 00:00:00 1999  0.000000 seconds

Solution: set date ! and write to RTC root@LKG62CC02?:~# date 011317402006 Fri Jan 13 17:40:00 UTC 2006 root@LKG62CC02?:~# hwclock -lw root@LKG62CC02?:~# hwclock Fri Jan 13 17:43:45 2006 0.000000 seconds root@LKG62CC02?:~# hwclock Fri Jan 13 17:43:47 2006 0.000000 seconds >>>>>>>

January 13, 2006, at 09:55 AM by bbo -- RTC error
Changed lines 17-18 from:
to:

<<<<<<<

Added lines 30-49:
  root@LKG62CC02?:~# date 011317402006
  Fri Jan 13 17:40:00 UTC 2006
  root@LKG62CC02?:~# hwclock -lw
  root@LKG62CC02?:~# hwclock
  Fri Jan 13 17:43:45 2006  0.000000 seconds
  root@LKG62CC02?:~# hwclock
  Fri Jan 13 17:43:47 2006  0.000000 seconds

=======

bbo: Error: root@LKG62CC02?:~# date

       Fri Dec 31 00:00:41 UTC 1999
       root@LKG62CC02?:~# hwclock -lw
       hwclock: Could not set the RTC time: Invalid argument
       root@LKG62CC02?:~# hwclock
       Fri Dec 31 00:00:00 1999  0.000000 seconds
       root@LKG62CC02?:~# hwclock
       Fri Dec 31 00:00:00 1999  0.000000 seconds

Solution: set date ! and write to RTC

Added line 57:

>>>>>>>

January 13, 2006, at 09:53 AM by bbo -- RTC error
Changed lines 16-35 from:

-VoodooZ

to:

-VoodooZ

bbo: Error: root@LKG62CC02?:~# date

       Fri Dec 31 00:00:41 UTC 1999
       root@LKG62CC02?:~# hwclock -lw
       hwclock: Could not set the RTC time: Invalid argument
       root@LKG62CC02?:~# hwclock
       Fri Dec 31 00:00:00 1999  0.000000 seconds
       root@LKG62CC02?:~# hwclock
       Fri Dec 31 00:00:00 1999  0.000000 seconds

Solution: set date ! and write to RTC root@LKG62CC02?:~# date 011317402006 Fri Jan 13 17:40:00 UTC 2006 root@LKG62CC02?:~# hwclock -lw root@LKG62CC02?:~# hwclock Fri Jan 13 17:43:45 2006 0.000000 seconds root@LKG62CC02?:~# hwclock Fri Jan 13 17:43:47 2006 0.000000 seconds

August 22, 2005, at 02:56 PM by tman --
Changed lines 4-5 from:

There has been an unconfirmed report that the Xicor X1205 RTC chip has been replaced with a ST Microelectronics M41T11? RTC chip.

to:

There has been an unconfirmed report that the Xicor X1205 RTC chip has been replaced with a ST Microelectronics M41T11 RTC chip.

August 22, 2005, at 02:56 PM by tman --
Changed lines 4-5 from:

Kas11 has a working kernel module in AnyU2 CVS.

to:

There has been an unconfirmed report that the Xicor X1205 RTC chip has been replaced with a ST Microelectronics M41T11? RTC chip.

Kas11 has a working kernel module for the Xicor X1205 in the AnyU2 CVS repo.

October 24, 2004, at 12:06 AM by VoodooZ --
Added lines 10-13:

Troubleshooting:

If reading the time via hwclock always returns the same date/time, it's possible your RTC clock is stalled. As suggested by Kas11, removing the battery for a few minutes and reinstalling it fixes the problem in some cases.

October 17, 2004, at 01:08 PM by tman --
Changed line 10 from:
to:

-VoodooZ

October 17, 2004, at 01:08 PM by tman --
Changed line 1 from:

The RTC chip is a Xicor X1205 Real Time Clock/Calendar which is connected externally to the CPU via I2C?.

to:

The RTC chip is a Xicor X1205 Real Time Clock/Calendar which is connected externally to the CPU via I2C.

Changed line 4 from:

Kas11 has a working kernel module in anyu2 cvs.

to:

Kas11 has a working kernel module in AnyU2 CVS.

Changed line 6 from:

The I2C? address of the chip is 0x6F.

to:

The I2C address of the chip is 0x6F.

Changed line 8 from:

The status register is at 0x3f.

to:

The status register is at 0x3F.

October 14, 2004, at 05:51 PM by VoodooZ --
Changed lines 1-10 from:

Describe RTCChipInfo here.

to:

The RTC chip is a Xicor X1205 Real Time Clock/Calendar which is connected externally to the CPU via I2C?. (see LinksToHardwareComponentDocumentation for data sheet)

Kas11 has a working kernel module in anyu2 cvs.

The I2C? address of the chip is 0x6F. The base register is 0x30. The status register is at 0x3f.

-VoodooZ?

view · edit · print · history · Last edited by PatrickB.
Based on work by fred, marceln, PatrickB, bbo, tman, and VoodooZ.
Originally by VoodooZ.
Page last modified on March 22, 2010, at 09:24 PM