| Electronics > Repair |
| ADVANTEST R9211B |
| << < (26/39) > >> |
| m k:
Check POD 12, there seems to be something wrong. If it's clearly connected swap PODs 06 and 12. Tap Run, what you get? POD 12 should be cycling and POD 06 being high. If POD 06, the old 12 remains low we have a problem. It means that _CS1 of RTC is messing its access, but it has not have a problem earlier, so that shouldn't happen. Change Time/Div to 1000ns and do different Patterns again, but leave first and last out. Scroll right and left to see if you can see POD higher than 05 going down, other than 12, 11 or 08. If Pattern generates a picture like Foto 3 or 7 try again. Maybe happening is random enough that Pattern doesn't happen every time before things settle. |
| stfjohn:
photo 1: pod 12 and 06 as before. photo 2: pod 12 and 06 swapped. photo 3: various patterns (always restarting Advantest, otherwise the message "waiting for trigger" appears and the image is blank. |
| m k:
Maybe you should get an extension cord with a power switch for Advantest. R9211 B/C Operating Manual page 3-9 has After Turning the Power ON. There after PROM check is FPU check, few steps before that is Timer check. Timer is not exact but FPU is. One can assume that PROM check is before anything appears on screen, but that's finally just guessing. FPU check then is so exact that finding it can be some kind of a goal, but we don't know exactly when it should happen. Other goal can be finding when CPU's _ILP0 and _ILP1 are going down. But since POD 12 is what it is we must treat it as a cause. POD 05 of foto 3 is also odd, but maybe it's a coincidence. So keep POD 00 to 05. POD 06 68000 25 _ILP0 CPU POD 07 62421 15 _CS1 RTC POD 08 71054 31 _CS U67 timer POD 09 71054 31 _CS U86 timer POD 10 68450 17 _CS DMAC POD 11 62421 2 _CS0 RTC POD 12 71054 31 _CS U52 timer POD 13 32081 21 _SPC FPU POD 14 8279 22 _CS KBC POD 15 9914 3 _CE GPIB Find Patterns xx4x xx5x xx6x xx7x Tap Run and boot Advantest, what you get? If nothing is found continue with Find Patterns from below. All pictures are possibly giving more information, but PODs 06 and 07 are a priority, so you can stop when those are found. Alternatively scroll around and try to find any other than 11 or 08 of POD 06 to 15 going down. Below Find Patterns are based on what has happened earlier. Means that all of those "possible" addresses have been present, but dropping _CS pins are missing, despite POD 08 and 11. xxC1 (5E00xx) xxC5 (5E20xx) xxC9 (5E10xx) xxCD (5E30xx) POD 08 goes down xxCF (5F30xx) xxD3 (5F08xx) POD 11 goes down xxD5 (5E28xx) xxD7 (5F28xx) xxDD (5E38xx) xxE3 (5F04xx) xxE9 (5E14xx) xxED (5E34xx) xxF1 (5E0Cxx) xxF3 (5F0Cxx) xxF5 (5F2Cxx) xxFB (5F1Cxx) |
| stfjohn:
With all the combinations you suggested, I always get a blank image with the words "waiting for trigger". |
| m k:
After booting Advantest also? |
| Navigation |
| Message Index |
| Next page |
| Previous page |