C64C [PAL]
Ser. No. 771029
Assy 250469
Artwork 252311 (REV 4)
Starting point
From an overall perspective this C64C looks to be in quite good condition. Yes, it is quite dirty, stained and yellowed - but aside from that it appears to be ok. I can not see any damage or cable "burn" marks on the covers.
There are two unoriginal switches; a push button on the right side and a toggle switch on the left side. The push button on the right I assume is a reset switch, but the button is completely stuck. The toggle switch on the left I would guess is a Kernal switcher (toggle between an original Commodore Kernal and a 3rd party ROM). This switch appear to be in mechanical working condition.
As with the push button the power switch is also completely stuck in "OFF" position. It is not possible to move it at all (or more precisely: I do not dare to push it too hard damaging it).
Regarding yellowing the covers are quite yellowed, but it is not completely Gouda cheese. The keycaps on the other hand has yellowed quite a lot.
Two out of the three screws at the bottom are missing.
Below are some pictures of the Commodore 64C before refurbishment.
Refurbishment plan
The refurbishment plan for this C64C (order can vary and some of the tasks will be done in parallell):
- Clean and remove stains from the chassis
- Clean and restore the keyboard
- Refurbish main board (cleaning, checking, repairing, replacing capacitors etc.)
- Replace the RF-modulator with C64 Shortboard RF replacement V2
- Verify operation by testing
The plan can be updated during the refurbishment process. Sometimes I discover areas that needs special attention.
Disassembly
To open the C64C the three... eh... one... screw is removed from the bottom cover. The two missing screws will need to replaced during refurbishment.
The top cover is carefully lifted about 30 degrees and then wiggled back and forth until the rear clips leave the bottom cover. At first glance the interior appear to be in fine condition. Quite some dust, but after 30+ years this is to be expected.
To remove the keyboard the two machine screws (see arrows) are unscrewed and the keyboard lifted away. The keyboard connector underneath is disconnected from the mainboard. Finally the LED connector is disconnected from the mainboard. The top cover, keyboard and bottom cover are now separated. There is very little rust on the RF-/heat shield.
Three out of the seven screws fastening the PCB and shield to the bottom cover are missing. Also, it turns out that the screw at the left bottom corner is longer than the rest (10 mm vs. 8 mm). I am not really sure if this is correct or not (?). I makes sense that the screw at the bottom left and right side should have slightly longer screws due to the additional metal brackets at these places. But due to this slightly oversized (?) screw the plastic standoff beneath the PCB is broken is this place - needs to be glued back as part of the refurbishment.
With the RF/heat shield out of the way the mainboard is exposed. It looks to be in quite condition - but it is quite dirty (the picture does not do justice as it is more dirty in reality). Now I also can see that the toggle switch controls a 3rd party ROM: JiffyDOS! And the push button is a good traditional reset button soldered to the user port. All the old heat paste have completely dried out (which is to be expected).
Exterior casing
In short: dirty, stained and yellowed, and with a broken stand-off. To start the cleaning process the LED is removed first by carefully push the small (brittle) plastic arms away from the LED.
With the LED out of the way the covers are soaked in mild soap water for about 48 hours. This will dissolve most of the old dirt and grease. A perfectly cleaned cover is crucial for a later successful retrobright.
After cleaning the top- and bottom covers are retrobrighted. This is done by applying 12 % hydrogen peroxide cream to the covers and exposing them to UV for about 12 hours. The hydrogen peroxide cream is replenished frequently to avoid drying out - and in addition the covers are wrapped in cling plastic.
The broken stand-off is glued back to the bottom cover. This will probably not last forever, but it should be sufficient for now.
Mainboard
This is a Assy 250469 / Artwork 252311 (Rev 4) mainboard which is one of the common "shortboards". The shortboards have fewer components compared to the old breadbin (and "longboards") as several of the logic ICs are now part of the extended "PLA" IC. The latest revisions of the shortboard even has the color RAM integrated in the "PLA" IC. Shortboards also have the MOS 8500 CPU and MOS 8580 SID chip.
Before the visual inspection the needs to be properly cleaned. All socketed ICs are removed and both the push- and toggle switch are removed before cleaning. Below is a picture of the mainboard before cleaning.
Visual inspection
The mainboard appears to be in good general condition after cleaning. I do not see any major damages, corrosion, leaking capacitors or other oddities. Some other observations:
The power switch is as mentioned previously completely stuck. But there are no external visual damage to the switch that cause this jamming.
The Kernal socket is not very well soldered in place. It would probably work, but some of the solder points are not too good.
The reset push button is also stuck.
Below are some pictures of the Kernal ROM socket (on both sides of the mainboard). There are some poor solder joints here. If it turns out that the machine does work like this it is probably best to just keep it like this to avoid damaging traces or pads. If not ther Kernal socket needs to be replaced.
In the table below the custom ICs are listed. As can be seen from the table below it is likely that this Commodore 64C was manufactured during the summer of 1988 - just in time of the opening of the Summer Olympics in Seoul (?). Whether or not the owner of this Commodore 64C listened to the magnificent album Seventh Son of a Seventh Son from Iron Maiden the same year I leave for the reader to guess.
Repairing the power switch (SW1) and push button
Before initial testing can start the power switch needs to be fixed. Hopefully this can be done by refurbishing the existing switch. If not, a new power switch will be sourced.
Refurbishing the power switch (SW1) is not very complex, but it is a bit fiddly. First the power switch is desoldered from the mainboard. No traces or pads were damaged during the desoldering.
The desoldered power switch has no visual exterior damage which should case it to jam. Quite opposite, it looks to be in good condition. The power switch is used both for the AC and DC rail from the power supply (rated at 9 VAC (3A) and 5VDC (4.5 A)).
Since there are no exterior sign of damage the power switch is opened. This is done by carefully prying it open with a thin flat screwdriver. Make sure not to pry and bent more than absolutely necessary.
The "rocker" and the base is separated by gently dragging the parts away from each other.
All the tiny parts are cleaned individually with a cocktail of contact cleaner and isopropanol. Note that (I think) these switches are lubcrated with some kind of grease originally. But I do not know which kind of grease this is so I do not replenish this. Also, I think that the grease could cause a voltage drop in the Commodore 64 later if the metal plates inside the switch gets dirty. Below is a picture of the all the cleaned parts.
As can be seen from the picture above all the parts appears to be in very good condition (after cleaning). I can not see any obvious reason why the switch should be completely stuck. When the power switch is re-assembled it works fine, but now I notice that it is very stiff. It is possible to turn the switch ON/OFF, but it feels quite hard. Could this be due to some missing lubrication? Maybe, but I do not really think so. I actually think that the problem is that this switch has some marginally larger interior parts making it a quite tight space. This will then require the user to apply some more force to toggle the switch in ON/OFF position. Nevertheless, the switch now works and I will leave it like this for now. If it turns out that the switch jam again during refurbishment it will be replaced.
Repairing the reset push button
The push reset button is also completely stuck. With closer inspection it seems like the top of the button is slightly bent. See picture below (this is perhaps not so easy to see, but pay close attention to the top hat of the button).
To repair the push button the top is gently moved back to original position. This makes the button work again. I will try with this solution first to see if the button now works as it should or if the problem reoccur. Below is a picture taken during the repair prosess (about 75 % complete).
Initial testing
With the repaired power switch soldered back in it is time to do an initial test of the Commodore 64C. Now I feel that the power switch feels very stiff so it probably needs to be replaced, but it will work for now.
Powering on the Commodore 64 results in a: NORMAL BLUE BOOTUP SCREEN (WITH JIFFYDOS OR COMMODORE KERNAL)
Checking the voltages
For the Commodore 64C to work flawlessly all the different voltages need to present and within acceptable tolerances. The 5V at the user port is a bit low, but I think that is due to the power supply or the power switch. A detailed article on the subject can be found in the HOWTO - Checking the C64 voltages. In the table below all the measures voltages are listed (this list will also be updated after refurbishment). All the required voltages are present and within tolerances, so there are nothing obvious wrong in that area. NOTE: for those who follow my refurbish project you may notice that many of the voltages appear lower than seen before. The voltages are completely fine, but I am now using a modified C128 PSU which outputs a bit lower voltages - but it is well within tolerances.
Replacing the RF-modulator
From The Retro Channel:
"The RF modulator in the C64 handles amplification and filtering for all video signals (including the ones on the C64 DIN connector). Unfortunately it does a very poor job and this is even more apparent with modern displays and upscalers, even CRTs with their inherent softening can reveal issues with the original RF modulator. One way to signifcantly improve the video output is to replace the RF modulator with a more modern and finely tuned solution, and why not add a few quality of life features while were at it."
The Retro Channels have designed what is probably the best analog RF-modulator available. And the design is open-source. I order the PCB from PCBWay and components are ordered from Mouser Electronics. Below is a picture of the fully assembled RF-modulator replacement.
NOTE: I managed to purchase the a standing, instead of a flat, 500 Ohm potentiometer from Mouser. Adjusting the fine tuning can still be done with a thin flat screwdriver, but it is a bit awkward. Sorry.
To install the RF-modulator replacement the old RF-modulator needs to be removed obviously. Removing the old RF-modulator is not very complex, but I would recommend following some guidelines to prevent damaging either the old RF-modulator or the mainboard. Since the RF-modulator is a device in itself, and soldered directly to the mainboard, it can easily do damage if not careful. Please see this article on how to desolder the RF-modulator.
The RF-modulator is desoldered, but one of the pads were lifter (pin 4 on top side of mainboard). This does not need any repair though since this pad is not connected to anything on the top side (and the pad on the bottom side of the mainboard is not damaged - and is where the pin is connected). See picture below of the desoldered area, and the arrow mark the missing pad.
Finally, the new RF-modulator replacement is soldered to the mainboard.
Continuing testing - Dead Test Cartrigde
In hindsight I should have done the test with the Dead Test prior to installing the RF-modulator replacement. Well, live and learn I guess. Nevertheless, when running the Dead Test Cartridge I do notice three things:
The CIA #2 (U2) internal Time of Day clock is not being updated
The SID chip produces only a very low sound in one out of the three sound tests
The picture is starting flickering when the mainboard is pressed down (and settles in this way eventually)
See picture below.
Mainboard - Repair
What at first glance seemed like a non-repair refurbished turned into a repair. Nice! Joke aside, these things happens. The Commodore 64 is an old machine and faults occur frequently.
Replacing the power switch
Although the refurbish of the original power switch did improve the situation (it now powers on) I am not satisfied with it. The switch is really hard to toggle. So a spare power switch is taken from another Commodore 64 (Ser. No. 828599). The "new" power switch is soldered in and the machine powers on as normal.
Re-inserting the original RF-modulator
Could the RF-modulator replacement have caused the problem with the flickering picture? An the low audio? I do think that there is a chance that this could be the case, so the original RF-modulator is soldered back in. The result is that the flickering is gone, but the audio is still hardly audible.
Checking the MOS SID 8580 chip
The MOS SID 8580 chip contains analog elements internally which I believe could be causing the very low audible output. The chip is tested in another know working C64C. The result is that this chip does seems to be working just fine in another machine. So apparently there must be something else going on the mainboard.
The analog signal is output on pin 27 on the SID chip, amplified in the Q3 transistor and feed to pin 3 on the RF-modulator as can be seen from the schematics (#252312). Since the SID chip itself appear to be working I would assume that there could be a fault in this amplification network (a bad transistor, capacitor or resistor).
Resistors can fail, but it is not as usual as transistors and capacitors. I will therefore start with these components. There are two components which stand out as possible fault candidates:
C 1815NPN transistor (Q3) which amplifies the signal from pin #27 at the SID chip
10 uF [25 V] electrolytic capacitor (C77) which acts as a filter between the transistor output the RF-modulator input (pin 3)
Checking the NPN C1815 can be done in circuit. By setting the multimeter in diode mode the voltage drop between BASE -> COLLECTOR and BASE -> EMITTER (and vice versa) can be measured. The rule of thumb is that if these measures equal (in each direction) the transistor is fine. As can be seen from the table below these voltages appear to correct, so I do not suspect the transistor to be bad.
Now something odd happens. By chance I test the machine with the Dead Test cartridge - and the audio now works! But ONLY in the first run of the Dead Test procedure. Could this fault be caused by something getting warmed up and stop working?
Checking the 10 uF electrolytic capacitor (C77) in circuit measures about 20 uF. I think this "misreading" is due to being in circuit. These electrolytic capacitors are known for drying out after years, so it is good practice to replace them. A new capacitor is installed.
The result after replacing the C77 capacitor is that audio now works! It needs to be tested further, but so far it works. I will let it run for a few hours and also try to press different areas on the mainboard to see if something could cause the problem.
Note that even if the C77 seems to be ok after desoldering and checking this with a multimeter - it is faulty. As can be seen from the picture below the capacitor reads fine (10 uF), but it still turn out bad? Is it really bad - or did the replacement actually fix something else?
After letting the Dead Test run for 3-4 times something starts to happen. The Dead Test program test the SID chip running sound through the three voices, but after some time running one of these voices seems to be completely gone (or with very low sound)? So I am starting to wonder if the SID chip is marginal. From the Dead Test manual we can read the following:
A step back - what are the faults actually?
Sometimes it is good to take a step back and evaluate the situation. It turns out that even if this machine boots normal, there is something very strange happening when the machine is running for a while. This is not easily detected when the machine is only showing the normal blue screen, but when the Dead Test Cartridge is installed something strange starts to happen...
The symptoms vary from time to time, but this is a typical description of the situation. Please note that the SID chip is removed now, the combined Kernal/BASIC ROM is removed, the MOS 6526 CIA #2 is removed and the original RF-modulator is installed. All this is done to try to reduce the number of chips and modules that could cause faults - but are not required for the Dead Test Cartridge to run.
The situation:
The Dead Test program runs fine for 1-2 rounds. There are of course no audio, and the CIA #2 shows wrong timing, but otherwise everything is ok.
Small thin, flikcering, stripes of disturbance appear on the screen. They look "analog", but I am not really sure what this is.
The whole screens get "darker" and the colors seems wrong. There are colors, but they appear very different.
Some of the characters get wrong colour. Almost like the color RAM is bad.
Test starts to fail: Zero page BAD, Color RAM BAD etc.
The whole screen starts flickering heavily. It is like the whole machine is going down in a major crash - and finally it does
Powering on the machine AFTER such a crash shows only a black screen. When the machine has cooled down the process described above repeats.
In the video shown below you can see an example of how the situation look. Please note that no SID or CIA #2 are installed at this moment and will therefore not show correct results. In this test everything "passes", but the colours are wrong. If I had recorded even longer the tests would have failed also and the machine would have come to a halt.
Things to notice in the video:
0:00 - 00:52: Everything works as it should. All tests pass and colours are ok.
00:52 - 00:53: First signs of flickering on the screen
00:58: The screen is "dimmed" (?) and changes abruptly
1:12 - end: The screen comes back but the colour saturation looks very odd.
What we know so far
Using an oscilloscope has proven valuable. When the situation described above starts, there is obviously something happening on the clock signals:
When measuring on PIN #1 on the CPU (Phi0) the clock is dead steady when everything on the screen is normal (check signal reference here). But when the first "analog looking" faults starts to visualise, the amplitude on the clock signals drops a bit and/or starts to oscillate. As the Dead Test cartridge runs the software this clock signals gets worse and worse. Amplitude oscillates more and more, the signals itself starts to stop/start/jitter and finally the signals goes completely dead - and so does the machine.
The hypothesis
My hypothesis is that there is something wrong with the stability of the clock generating circuit. It could be the ICs related to the clock generation such as the MOS 8565 VIC-II and/or the MOS 8701 clock generator. Also, it could be related to the analog circuits used by these such as the capacitors, crystal and variable resistor.
Troubleshooting
The easiest, and fastest, to check is to see if the MOS 8701 and/or the MOS 8565 are faulty. These are replaced with known good working ICs, but it turns out that the machines behaves the same. The machine seems perfectly normal when it is cold, but after some 5-10 minutes things starts to fall apart.
The next step is to check the passive analog components: the oscillator crystal (Y1) and the variable capacitor (CT1). The crystal has a resonance frequency of 17.734472 MHz and the variable capacitor a range between 7.7 pF - 40 pF. See schematics below (From the C64 Service manual - Schematics 252312).
When desoldering the variable capacitor I accidentally loose a pad, but this not very much of a deal since the pad was not connected to anything. But I also see something I think is a bit strange. When I try to measure the capacitor with a multimeter I get no reading at all - or only some flickering reading. It could be that the multimeter is not capable of such small readings, but I am not sure... Could this be a bad capacitor and cause the fault? See pictures below from the process.
The saga continues - and what a mystery...
Replacing the MOS8701 and crystal oscillator
A TOLB module from Eslapion is ordered from retroleum.co.uk. This little circuit replaces the MOS 8701 (and crystal oscillator) should therefore give a very stable clock - both input to the VIC-II and then further on to the CPU.
With the new TOLB module in place the Dead Test Cartridge is now running fine again! The tests pass time after time - and no analog flickering on the screen!
... until something really weird happens
To make sure the machine is now "back to normal" it is powered on for a while. But now something strange starts to happens! It is not analog flickering, but some digital corruption which is usually caused by RAM failure. See video below.
What is happening here? I feel the machine is falling apart in my hands! Holy moly, hehe!
Nevertheless, a couple of new 41464 RAM chips are put in (and sockets installed).
But we are still not out of the woods yet (!)
With the new RAM ICs installed things looks much better again! Phew! The Dead Test Cartridge is running all tests fine - and everything looks normal.
A known good working CIA is installed - and the Dead Test started again. But now things REALLY start to get crazy! After a couple of runs the AM clock increases slightly faster than the PM clock? Why? And after a few more rounds there is WHITE SMOKE coming from the bottom left corner of the CIA IC! Holy macarony! We have a FIRE!
Ok, that was a bit exaggerated (thanks ChatGPT!), but we definitely have a serious issue here with some kind of short circuit!
Looking for a short circuit
I start to think about it. This repair has been quite challenging - as I feel that more and more problem occur as I repair:
Interim problems with audio
Wrong TOD clock on the CIA #2
Oscillator circuit starting to get flaky before it finally stops working completely
RAM chips starts to suddenly fail
Smoke coming from the CIA #2 (new)
Have I been chasing the wrong fault all the time? Is it so that the "real" fault is causing more and more damage as the repair goes on?
In case you wonder: No, I do not use an old power PSU. I use a modern replacement (which I know is working). But this is kind of the same behaviour you would expect if you had a bad power supply basically "killing" all your ICs as you go.
There is a good spot to check if there is a short circuit on the +5 VDC rail: the USER PORT. In the picture below you can see the user port and where the +5VDC (VCC) and ground (GND) connector can be located.
There is seems to be some kind of short circuit. In the table below the measured resistance between VCC and GND is presented. Note that the CIA#2, VIC-II, 2 x 41464 RAM and TOLB module are all removed when measuring.
After quite some detective work, including removing several of the capacitors, I finally find the short circuit (hopefully). I think I might have caused the short circuit myself (at least partly), but here is what I discovered:
Both pin #19 (TOD) and pin #20 (+5V) are extremely close to the GND plane on the PCB. And I did install a socket for the CIA#2 at some point, but what seems to have happened is that some small area of the GND plane has not been coated. And then some flux residue (?), or tiny amount of solder, from the socket (on pin #20) has reached the GND plane. Note that there was not a dead short between GND and VCC. The short only occured when power-on.
In the picture below you can see where the short circuit was. And also, you can see how close the VCC is to the GND plane on the PCB. Is this really a good PCB design?
After fixing the short circuit the resistance between +5V and GND is back to about 500 Ohms.
The picture above was taken after cleaning. Below is a picture taken after the socket was removed. Notice that the area surround GND, VCC and TOD (pin#19) are all part of the short circuit. Could this also be the reason for the Time of Day (TOD) clock behaving weird?