That's one thing you can rule out. So it's something.
If the CPU is stuck somewhere, there should be one particular address decode/chip select
that's getting hammered.
I'm sure you scoped the reset to make sure it's not glitching into the active state, right?
Sounds like a tough one...
If the CPU is stuck somewhere, there should be one particular address decode/chip select
that's getting hammered.
I'm sure you scoped the reset to make sure it's not glitching into the active state, right?
Sounds like a tough one...