Announcement

Collapse

Forum Rules and Etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Rule 1: Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Rule 2: Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Rule 3: Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


Rule 4: "PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Rule 5: Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Dallas RTC chip replacement results in video card not found

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Dallas RTC chip replacement results in video card not found

    Hi,

    I have an old Philips 286 laptop that had a dead Dallas RTC chip.
    The CMOS tests failed and I couldn't setup the system (always started with default settings and couldn't persist anything in the BIOS).

    Replacing the Dallas RTC chip was a bit of a botch job ... It was very difficult to remove, and I think I damaged some pads / vias along the way.

    Initially the result was a dead laptop. Knowing really well I screwed up on the Dallas RTC I decided to look at the traces.

    I had put in place an IC socket for the Dallas RTC chip, and I get the same behavior with the original Dallas RTC chip that was in there.

    The Dallas RTC chip is getting power (5V) .

    The PCB is multi-layered so I cannot trace al of the connections, but I did notice that on the Dallas RTC A01 and A03 were not connected.

    where-as I could verify the following connections (continuity check):
    • Dallas RTC A00 was hooked up to Bios EEPROM D0
    • Dallas RTC A02 was hooked up to Bios EEPROM D2
    • Dallas RTC A04 was hooked up to Bios EEPROM D4
    • Dallas RTC A05 was hooked up to Bios EEPROM D5
    • Dallas RTC A06 was hooked up to Bios EEPROM D6
    • Dallas RTC A07 was hooked up to Bios EEPROM D7

    So I hooked up
    • Dallas RTC A01 was hooked up to Bios EEPROM D1
    • Dallas RTC A03 was hooked up to Bios EEPROM D3

    Progress ... When I turn on the laptop now, I get orange lines on the LCD, and

    - 1 long beep, followed by 3 short beeps
    - 1 beep
    - 1 long beep, followed by 2 short beeps

    The BIOS is an Award BIOS. So this seems to suggest an issue with the video card.

    Now most likely there are still some broken traces on the Dallas RTC.

    For example I cannot find the connections for
    • pin 14 AS
    • pin 15 RW
    • pin 16 RESET
    • ping 23 SQW

    I also don't know if hooking up A01 -> D1 and A03 -> D3 is correct (seemed to make sense and I did get something on the screen and some beeps).

    How would I go about debugging this further ? Is there some kind of reference design how these Dallas RTC chips are wired into the BIOS chips, and where the above pins might end up going ?

    Do these beeps give any hint on what the issue might be ? I only touched the pads of the Dallas RTC so I wasn't anywhere near the video card.
    Retro enthousiast. Love everything < 486. Learning and sharing on my little channel

    #2
    Have you seen this post? https://www.vcfed.org/forum/forum/ge...ing-clock-chip

    Comment


      #3
      Originally posted by conradspitfire View Post
      Yes, but I never put it in backwards. I did read about some incompatibilities with the DS12887A chips on older motherboards. My first attempt was with such a DS12887A, but with my DS12887+ and. the original DS1287 chip the computer always does the same thing.

      Don't know that much about how such a Dallas RTC is wired on the board, with what other components it interacts with, or how I could further diagnose this.

      With this multi-layer board there are so many options, and although I did manage to trace down the address lines, the VCC and GND, where are still some pins that I cannot find.

      Got some pictures here (seems to be a 256kb (??) file size limit here for picture) : https://drive.google.com/drive/folde...7C?usp=sharing
      Retro enthousiast. Love everything < 486. Learning and sharing on my little channel

      Comment


        #4
        Without a schematic for your system, it's going to be hard to figure this one out. However, you can at least get a clue from the IBM 5170 schematics here. See sheet 19 for how the MC146818 is hooked in. The Dallas 1287 has the same pinout--it just contains the battery backup under that epoxy.
        Reach me: vcfblackhole _at_ protonmail dot com.

        Comment

        Working...
        X