11/34 failing trap test

[Julian Wolfe]

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 

> -----Original Message-----
> From: cctalk-bounces at classiccmp.org 
> [mailto:cctalk-bounces at classiccmp.org] On Behalf Of Don North
> Sent: Sunday, August 20, 2006 1:10 AM
> To: General Discussion: On-Topic and Off-Topic Posts
> Subject: Re: 11/34 failing trap test
> 
> Pete Turnbull wrote:
> > On Aug 19 2006, 9:38, Wolfe, Julian wrote:
> >
> >> I got the 11/34 up and running, and I loaded XXDP. It 
> fails the trap 
> >> test. The instructions state you should examine the stack pointer
> >> (777706) which shows it to be a value of 000470. This is 
> supposed to 
> >> tell you the address of the Program Counter, right? So I 
> load address 
> >> 470, and the value is 000330. What instruction is failing? Am I 
> >> reading this right?
> >
> > Yes, the stack pointer points to the last address used on 
> the stack, 
> > and that will be the value of the PC when it called the error 
> > subroutine, or to put it another way, the address of the next 
> > instruction to be executed had the JSR not been taken. It's 
> failing at 
> > whatever test was just before location 330 -- which is surprisingly 
> > low. You'd need to look at the listing to see what the test was.
> >
> The trap test typically does a halt-on-failure, so at what 
> address does your CPU halt? After knowing the halt address 
> (and the failed test) the SP and what is on the stack may or 
> may not be useful data.
> 
> BTW the listing of this diagnostic is online at:
> http://www.bitsavers.org/pdf/dec/pdp11/xxdp/listings/AC-8045D-
> MC_CFKABD0-1134-Traps-Tst_Apr77.pdf
> in case you already didn't know this.
> 
> If indeed the CPU did halt at 330 this is in the vector space 
> which is typically populated with .+2/halt word pairs (a 
> 'trapcatcher' in DEC terms).
> 
> Don North
> 
> 
>