RTC issue

Hey guys I thought of asking here as I have a strange issue with my RTC on my A4000.

My A4000 mobo has the coin battery mod with the diode from the previous owner and seems the mobo had some sort of repair that is really well performed.
First time I checked the clock was iirc 1978. I thought the battery was dead so I changed it with an new CR2032 one. I checked the voltages with my multimeter under the socket to ensure that the connections were going correctly to the mobo and fired up the Amiga.

For some strange reason the system booted with clock showing:
- January 2005, 12:06pm

When I changed the clock via Prefs:Time, the time changed just fine and everything worked... till next reboot that again showed:
- January 2005, 12:06pm

LOL wtf?

OK I even used "setclock save" command and then a "setclock load" as I remember from the old days, but even then no difference.

It's not such a big deal cause I could sync via NTP once I'll have the miggy connected to the internet permanently but it's getting a bit on my nerves knowing that something isn't working as intended :)

Could it be the RTC chip screwed for some reason?

Cheers

I had an issue with track dammage myself. Burned track underneath.

Check if diode is in right direction, that is plus battery to --->| mobo, meaning the black line is close the mobo plus and the rest of the body is towards the battery-holder.

It is opposite if it stared from minus.

reason: without load my meter gives correct voltage even it is wrong.

i'll check it out when I get home then...
Damn it'll sux having to dismantle all A4000 in case it's not correctly put!
Oh well, one more reason to put an Audio cable under mobo for not having to get the signals from the connectors... :D

Thx my friend

There was a command in WB1.3 "setclock reset" to reset RTC chip because some viruses/cracked games used to save garbage into RTC NVRAM.
Should work in WB3.9 as well

This may be a log shot, but check your start up prefs. IIRC there is a "Set Clock" command that could be in there to force the time to reset to Jan 2005. If I had to take a wild guess, the battery was probably replaced on 2005, at 12:06 PM and the person did a set clock command that saved in the boot script.

Kinda doubt it my friend.
I use an ClassicWB 3.9 installation by Bloodwych and startup doesn't have any SetClock command.
Last night I also made a SetClock reset but nothing changed.

Mario

If you need a new 501 RTC chip, I have one here for you my friend FOC

TC ;)

TC my friend thanks a lot for your offer!!! I'll check it out first and report back!

<3

Quote:

---

Originally Posted by mfilos

TC my friend thanks a lot for your offer!!! I'll check it out first and report back!

<3

---

Just drop me a PM with your addy if you need it mate :thumbsup:


Personally I would suspect the latch chip which is to the left of where the battery used to live, it's quite common for the corrosion to get under the device (mine did).

It's also worth using a multimeter to check the voltage being delivered to the RTC pin directly when the system is powered down, again don't use any 0V or GND but the GND on the RTC pin chip itself, as a poor GND can also drop the voltage.

If the RTC power fails then the system will fall back to the date & time that was captured when the Booted HD was prepared. which is why you are getting the same date again & again.

I forgot to tell ya all that my mobo has some sort of repairing hack near the RTC and chip...

If you check the photos you'll see a diode that connects the Pin1 of the RTC chip to a nearby transistor (i think).

Attachment 16070 Attachment 16071 Attachment 16072 Attachment 16073

Dunno if that is supposed to be right or wrong... but... it was there :unsure:
The mobo must have had some battery leakage problem but someone took care of it very profetionally cause as I see it's a really neat soldering/repair job. Also the cap were changed as well so I guess that it can't be a clueless mod for some reason ;)