Sat, 2007-01-06 11:08 Hi,
Wrap boards are know not to store data/time settings because of missing backup battery. Here is a section of their manual:
-----------------------
Real-Time Clock
WRAP does not include a battery backup for the real-time clock (RTC).
The A3 stepping of the SC1100 CPU had a problem with the 32768 Hz oscillator, leading to
potential RTC inaccuracy. This version also was sensitive to ESD on the battery voltage pin.
A backup battery can be connected as follows:
WRAP.1C / .1D: Add a 100 ohm, 0603 resistor in location R5, replace the 0 ohm resistor in location
C105 (bottom side) with a 0.1uF 0603 capacitor, install a 2 pin header in location J1. Connect 3V
Lithium battery to J1, observing the polarity marks.
WRAP.2B / .2C: Connect 3V battery to J7 pin 7 (positive) and pin 8 (negative).
SC1100 is specified for a battery voltage of 2.4 to 3.6V, drain current 7 to 30 UA. At 30UA, a
CR2032 Lithium coin cell will last only about a year – please consider a larger CR123 Lithium (often
used in cameras).
-------------------------
PCEngines guys, that produce wrap boards give 4 reasons for this:
- One more thing to break...
- tinyBIOS doesn't use CMOS RAM to store setup (safely stored in flash)
- time servers...
- limited shelf life / recycling hassles"
Please try our 4.0 release and start ntp with -s switch to setup you date/time at boot time.
Joined: 2006-12-18
Hi,
I have tested the free cf-image of embedded Linux in actual version (2.7.3-i586-wrap) on the WRAP.1E-1 (2 LAN) Board. I don't have installed any extensions. I have configured the name server and ntp daemon. After some minutes (the ntp server have contact to some peers) the ntp daemon fails without any error message. The Message in ntpq is: "ntpq: read: connection refused". In process list then there isn't a ntp process. I think, that the ntp writes the time information to the boards time controller and the daemon fails because there is a write problem.
With the "date" command I can set the system date and time, but not the board time. After reboot (init 6) in every case the system have date of "Jan 1 00:00:00 PST 2000".
Any ideas?
regards Torsten