11/34 failing trap test

[Julian Wolfe]

Okay, it halts with 20 in the octal display.  Is that the address?

I guess I need to take this one step at a time.

On Sep 20, 2006, at 1:39 AM, Don North wrote:

> Julian Wolfe wrote:
>> Okay, I had a look at the instruction listing and to be honest,  
>> have no idea
>> what I'm looking at.  How do I figure out what test was running  
>> when it
>> failed, and how do I decipher what that means?  Is 330 the number  
>> on the
>> very left of the page?
>>
>> If so, it says to scope the problem, replace halt with 240 (is  
>> this JMP?)
>> and replace the next instruction with 703 (what's that? Where I'm  
>> jumping
>> to?)
>>
>> Anyway, of course, any help would be much appreciated.
>>
>> Thanks!
>> Julian
>
> You need to run the trap test and when it halts (meaning a failure)  
> then
> observe the halt address in the lights on the console display. Forget
> about the stack pointer and all that stuff until you know where in the
> diagnostic the failure is located.
>
> THEN if it is relevant you can examine the registers and/or memory to
> get more info. But you need to know what to look for first, and the
> starting point is the halt address in the console lights.
>
> Don