• Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.

Anyone up for some IIcx troubleshooting assistance? We have clocks but no activity...

What @Phipli said. I just scrape the dark parts with the meter probe, and tin over - using an x-acto feels a bit aggro. Wire only goes over confirmed breaks. UV mask is a thing I usually skip as I find it usually just makes things uglier (it's only really needed in certain things).
 
What @Phipli said. I just scrape the dark parts with the meter probe, and tin over - using an x-acto feels a bit aggro. Wire only goes over confirmed breaks. UV mask is a thing I usually skip as I find it usually just makes things uglier (it's only really needed in certain things).
I use the probes too like that. But some are so bad they need careful scraping.
 
Check pin 3 on those same ICs. However something's odd. All address lines generated by NuChip are quiet, but you're telling me those coming from the system side are asserted, or at least something is forcing them on.

Check UDs as well, feel free to check both A and B sides. I have a suspicion this might be close to the issue, especially considering how bad traces around that area look.

1688455806604.png
 
On it. So when I hit reset, the address lines on the roms go high and then back to low. Does this mean the CPU is not “dead” ?
 
Check pin 3 on those same ICs. However something's odd. All address lines generated by NuChip are quiet, but you're telling me those coming from the system side are asserted, or at least something is forcing them on.

Check UDs as well, feel free to check both A and B sides. I have a suspicion this might be close to the issue, especially considering how bad traces around that area look.

View attachment 58924
Uc9 pin 3 - high
Uc13 pin 3 - low
 
On it. So when I hit reset, the address lines on the roms go high and then back to low. Does this mean the CPU is not “dead” ?
No, it doesn't mean anything - somewhere earlier I mentioned broken silicon may still act in ways that seem sensible. While reset is asserted, the system is in undefined state. What reset does is clear the slate and get it all into a known default state the machine can start running from. That would include throwing the CPU at its reset vector, what on the m68kis called an IISR, which makes it go to the bottom of the address space (0x00000000) and then start executing from 0x04. As you can imagine, that location is physically pointed at by an all-low address lines combined.

A broken CPU in an otherwise functioning machine way well jumble the lines upon having reset asserted, and then beautifully clear them once reset deasserts, but never go from there. A broken CPU may have broken address line drivers. Something could short one of those address lines and force them to do weird things. It goes on.
 
Now that the boards been on for a while the uc and UD chips are getting pretty warm/ hot

That red one in the bottom center is uc12. 45 degrees Celsius
 

Attachments

  • IMG_5407.jpeg
    IMG_5407.jpeg
    2.1 MB · Views: 7
Back
Top