We welcome retro users & hardware gurus alike! Come and join the party :)
https://www.exxosforum.co.uk/forum/
Ah, makes sense. I'll give that a try. Thanks.Maximilian wrote: 09 Nov 2023 18:26 You cab use a no so sharp needle and just try to ever so lightly try to move a pin, if the pin moves with the needle, it is loose.
No need to continuity check if there is no apparent damage, and it can give you a false hope of security because if the pin isn't soldered correctly if will give problems when the machine heats up or cools down..
@Maximilian, there was indeed one pin not solidly connected (pin 15), although I don't think it's connected to anything anyway (according to schematic). Thanks for the suggestion. Unfortunately, still no video output. I'm going to go through the Phantom mod documentation and see what might need reversing.Maximilian wrote: 09 Nov 2023 18:26 You cab use a no so sharp needle and just try to ever so lightly try to move a pin, if the pin moves with the needle, it is loose.
No need to continuity check if there is no apparent damage, and it can give you a false hope of security because if the pin isn't soldered correctly if will give problems when the machine heats up or cools down..
I have to agree with Stephen here, if you chase everything you end up with nothing.stephen_usher wrote: 10 Nov 2023 15:12 You may not have video output but do you have bus activity?
You may be fighting multiple faults so concentrate upon one thing at a time.
If you see data on all the address lines and all the data lines around the board and you see the correct type of signal on the CPU control lines then you can move on from the CPU to other parts of the system. Trying to diagnose everything at once is a hiding to nothing.
Thanks @stephen_usher and @rubber_jonnie. That's next.rubber_jonnie wrote: 10 Nov 2023 15:14I have to agree with Stephen here, if you chase everything you end up with nothing.stephen_usher wrote: 10 Nov 2023 15:12 You may not have video output but do you have bus activity?
You may be fighting multiple faults so concentrate upon one thing at a time.
If you see data on all the address lines and all the data lines around the board and you see the correct type of signal on the CPU control lines then you can move on from the CPU to other parts of the system. Trying to diagnose everything at once is a hiding to nothing.
Well, no clock = bad juju, so definitely a good place to start :)Steve wrote: 10 Nov 2023 15:47 @stephen_usher @rubber_jonnie but we do know he doesn't have his 32mhz clock line due to L132 being removed. So I'd start there.
Also, no clock == no nothing.rubber_jonnie wrote: 10 Nov 2023 16:23Well, no clock = bad juju, so definitely a good place to start :)Steve wrote: 10 Nov 2023 15:47 @stephen_usher @rubber_jonnie but we do know he doesn't have his 32mhz clock line due to L132 being removed. So I'd start there.
So far, all of the address lines I tested are high, but yes, L102 is missing. I probed on the oscillator side and it's coming out 32MHz, so I'll either bridge it as suggested or get a replacement. The I can't make out the value for L102 in the schematic I have (see pic). Does anyone know the proper value?stephen_usher wrote: 10 Nov 2023 16:31Also, no clock == no nothing.rubber_jonnie wrote: 10 Nov 2023 16:23
Well, no clock = bad juju, so definitely a good place to start :)