Re: 11/04 Project

[John Welch via cctalk]

I have it working now.  I had to go into XP settings for the comm port.

@L777

@E

000777 173200 165212 000777

So, next is to hook up to the RL02.  I will start a new thread for that.


On 12/14/2017 7:23 AM, Noel Chiappa wrote:

 > From: William Degnan

 > 1) the console rom does not go in any of the 4 bootstrap slots, these
 > should be empty for now. There is a special console rom slot.

Just to clarify, by "slot", you don't mean 'backplane slot', you mean 'socket
(on the card)', right?

Also, note that the console/diagnostic ROM is a different size (bit-wise; I'm
not sure about the physical package) from the bootstrap ROMs.

 > 6) possibly the only switch to worry about now is the power on auto
 > jump to console switch.

I'd leave that, too, until we get the software console to run when started
manually - at the moment, the ROM's not working, so that switch is irrelevant.

Noel


--
Sincerely,
John Welch
281-353-4706 Home
713-725-7017 Cell
:qw

Re: 11/04 Project

[John Welch via cctalk]

The "@" is on the screen in HyperTerminal.

I have 4 M9312 cards.  Three have W8 jumped, one did not.  I put in the 
M9312 w/o W8 and when I power on I see the "@" on the screen.


Now for the next snag. The bitsavers document suggests L777 ; 
E which should echo some digits.  However nothing pops up.


So I am wondering if I have the handshaking set right?


On 12/14/2017 6:47 AM, Noel Chiappa wrote:

 > From: John Welch

 > CLR
 > 765000
 > LAD
 > EXAM
 > 'Bus Err' light comes on.

Oooh, that's very interesting, and illuminative. The ROM isn't working (so
there's no way for the software console to work - its code is in that ROM).

So look at Section 1.5 of the Technical Manual

   http://bitsavers.org/pdf/dec/unibus/M9312_TechRef.pdf

and make sure all the jumpers on the M9312 are as required. In particular,
jumper W-8 should be _out_.

If it's not, that would explain why the ROM at 765000 isn't resonding. If it's
in, that M9312 board probably has a problem.


Also, while we're at it, it's probably worth making sure the CPU will
run. Do this:

   CLR
   LAD
   777  (This is a 'branch .' instruction)
   DEP
   EXAM (Should display '777')
   CLR  (I think you can dispense with these
   LAD  two, but just to be safe...)
   CTRL-START
   'Run' light should come on
   CTRL-HALT
   'Run' light should go out, should display '0' (or maybe '2', I forget)


 > Do you know which color wire (red, clear, black) goes to which festoon
 > connector (TP1, TP2, TP3, TP4)?

I would leave them all disconnected for the moment; you don't need them. One
is the 'boot' switch on the console, and its ground. The other is the 'boot on
power on enable' (a duplicate of S1-2), and its ground. Since we're trying to
manually start the ROM console from the front console, they aren't needed for
that.

I don't recall offhand which one connects to which - I will have to check.

 > Don't want to blow anything up.

Not sure it will harm anything if you connect things wrongly, but that's
not tested.

Noel


--
Sincerely,
John Welch
281-353-4706 Home
713-725-7017 Cell
:qw

Re: 11/04 Project

[John Welch via cctalk]

On 12/14/2017 6:47 AM, Noel Chiappa wrote:

 > From: John Welch

 > CLR
 > 765000
 > LAD
 > EXAM
 > 'Bus Err' light comes on.

Oooh, that's very interesting, and illuminative. The ROM isn't working (so
there's no way for the software console to work - its code is in that ROM).

So look at Section 1.5 of the Technical Manual

   http://bitsavers.org/pdf/dec/unibus/M9312_TechRef.pdf
Will do.  I have 4 M9312 cards.  One I know I pulled from an 11/04, the 
others from 11/04 or 11/34 (or 11/34a)

[...]

Also, while we're at it, it's probably worth making sure the CPU will
run. Do this:

   CLR
   LAD
   777  (This is a 'branch .' instruction)
   DEP
   EXAM (Should display '777')
   CLR  (I think you can dispense with these
   LAD  two, but just to be safe...)
   CTRL-START
   'Run' light should come on
   CTRL-HALT
   'Run' light should go out, should display '0' (or maybe '2', I forget)

It read 00



 > Do you know which color wire (red, clear, black) goes to which festoon
 > connector (TP1, TP2, TP3, TP4)?

I would leave them all disconnected for the moment; you don't need them. One
is the 'boot' switch on the console, and its ground. The other is the 'boot on
power on enable' (a duplicate of S1-2), and its ground. Since we're trying to
manually start the ROM console from the front console, they aren't needed for
that.

I don't recall offhand which one connects to which - I will have to check.

 > Don't want to blow anything up.

Not sure it will harm anything if you connect things wrongly, but that's
not tested.

Noel


--
Sincerely,
John Welch
281-353-4706 Home
713-725-7017 Cell
:qw

Re: 11/04 Project

[william degnan via cctalk]

On Thu, Dec 14, 2017 at 8:23 AM, Noel Chiappa via cctalk <
cctalk@classiccmp.org> wrote:

> > From: William Degnan
>
> > 1) the console rom does not go in any of the 4 bootstrap slots, these
> > should be empty for now. There is a special console rom slot.
>
> Just to clarify, by "slot", you don't mean 'backplane slot', you mean
> 'socket
> (on the card)', right?
>


Yes of course bad choice of words.  The console ROM socket is separate from
the 4 bootstrap ROM sockets.


>
> Also, note that the console/diagnostic ROM is a different size (bit-wise;
> I'm
> not sure about the physical package) from the bootstrap ROMs.
>
> > 6) possibly the only switch to worry about now is the power on auto
> > jump to console switch.
>
> I'd leave that, too, until we get the software console to run when started
> manually - at the moment, the ROM's not working, so that switch is
> irrelevant.
>
>
>

Yes but if it's on and when you power up the system no @ sign appears at
the terminal that says it's not autostarting the console.  At least knowing
what to expect (off or on) is what's important.

As I said, the 11/04 has specific wire jumper settings.  Such as W8.  These
must be correct for the CPU, the UNIBUS must be in a non DC LO AC LO, etc.
I went through all this with my 11/40 (not 04) and it was a great way to
learn about and diagnose the machine function.

b

Re: 11/04 Project

[Noel Chiappa via cctalk]

> From: William Degnan

> 1) the console rom does not go in any of the 4 bootstrap slots, these
> should be empty for now. There is a special console rom slot.

Just to clarify, by "slot", you don't mean 'backplane slot', you mean 'socket
(on the card)', right?

Also, note that the console/diagnostic ROM is a different size (bit-wise; I'm
not sure about the physical package) from the bootstrap ROMs.

> 6) possibly the only switch to worry about now is the power on auto
> jump to console switch.

I'd leave that, too, until we get the software console to run when started
manually - at the moment, the ROM's not working, so that switch is irrelevant.

Noel

Re: 11/04 Project

[Noel Chiappa via cctalk]

> From: John Welch

> CLR
> 765000
> LAD
> EXAM
> 'Bus Err' light comes on.

Oooh, that's very interesting, and illuminative. The ROM isn't working (so
there's no way for the software console to work - its code is in that ROM).

So look at Section 1.5 of the Technical Manual

  http://bitsavers.org/pdf/dec/unibus/M9312_TechRef.pdf

and make sure all the jumpers on the M9312 are as required. In particular,
jumper W-8 should be _out_.

If it's not, that would explain why the ROM at 765000 isn't resonding. If it's
in, that M9312 board probably has a problem.


Also, while we're at it, it's probably worth making sure the CPU will
run. Do this:

  CLR
  LAD
  777   (This is a 'branch .' instruction)
  DEP
  EXAM  (Should display '777')
  CLR   (I think you can dispense with these
  LAD   two, but just to be safe...)
  CTRL-START
  'Run' light should come on
  CTRL-HALT
  'Run' light should go out, should display '0' (or maybe '2', I forget)


> Do you know which color wire (red, clear, black) goes to which festoon
> connector (TP1, TP2, TP3, TP4)?

I would leave them all disconnected for the moment; you don't need them. One
is the 'boot' switch on the console, and its ground. The other is the 'boot on
power on enable' (a duplicate of S1-2), and its ground. Since we're trying to
manually start the ROM console from the front console, they aren't needed for
that.

I don't recall offhand which one connects to which - I will have to check.

> Don't want to blow anything up.

Not sure it will harm anything if you connect things wrongly, but that's
not tested.

Noel

Re: 11/04 Project

[william degnan via cctalk]

I am confused by the flow of this thread on my phone but.there are
important things to confirm
1) the console rom does not go in any of the 4 bootstrap slots, these
should be empty for now.  There is a special console rom slot. Please
confirm you have it installed.
2) 164020 should bring up the @ prompt or the 11/04 equiv.  Load thus unto
memory and run from there if you want to load manually
3) the 9312 jumpers (not talking about switches) must be set for an 11/04.
They differ for various machines.  Where did this 9312 come from?
4) confirm you don't have a DC LO AC LO failure.
5) the jumper switches more so pertain to the device bootstrap selection
not the console.  It's confusing because they refer to the console being
on/off in relation to the device to be bootstrapped, ignore all that.
6) possibly the only switch to worry about now is the power on auto jump to
console switch. If that's on when the machine powers up it should cause the
machine to  jump to the console and print a @ prompt to the termunal
assuming everything else is right.

Bill Degnan
twitter: billdeg
vintagecomputer.net
On Dec 14, 2017 12:42 AM, "John Welch via cctech" 
wrote:

> On 12/13/2017 10:41 PM, Jerry Weiss wrote:
>
>> What is the configuration of jumpers?
>>
>
> I have tried the following:
> 1   2   3   4   5   6   7   8   9   10
>--- --- --- --- --- --- --- --- --- ---
> S1 Off On  Off Off Off Off Off Off On  Off
> S1 On  On  Off Off Off Off On  Off Off Off
> S1 On  On  Off Off On On  Off Off On  Off
> S1 On  Off Off Off On  On  Off Off On  Off
> Maybe some others, never get anything to the screen.
>
> I have some cards that are marked TP1:Red TP2:Blk TP4:Clr
> and other cards marked TP1:Red TP2:Clr TP4:Blk
> I would really like to hear from someone that has it working rather than
> risking popping something.
>
> On Dec 13, 2017, at 10:34 PM, JCWelch > jcwe...@hal-pc.org>> wrote:
>>>
>>> So far nothing puts ‘@‘, or anything on the screen.
>>>
>>> Sent from my iPad
>>>
>>> On Dec 13, 2017, at 10:05 PM, Jerry Weiss > j...@ieee.org>> wrote:
>>>
>>> According to the documentation EK-M9312-TM-002 M9312
>>> Bootstrap-Terminator Module Technical Manual
>>> there are two addresses to use for the Console Emulator.
>>>
>>> 165020 (765020)  for Console with Diagnostics  SW 1 and 7 on
>>> 165144 (765144)  for Console w/o Diagnostics   SW 1,5,6,9 on
>>>
>>> The switch settings below correspond to xxx004.. which is probably the
>>> first drive for the ROM in position 1 and does
>>> not invoke diagnostics.
>>>
>>> Have you tried 173000 (773000)?
>>>
>>> Jerry
>>>
>>>
>>> On Dec 13, 2017, at 8:37 PM, John Welch via cctech <
 cct...@classiccmp.org > wrote:

 I have bi-directional communication from PC/Hyperterminal.   I forgot
 about having to tell HyperTerminal to echo characters locally. Anyway, 'a'
 comes over as 000141 and 'A' comes over as 000101. So far so good.
 However, I have not gotten "@"
 CNTRL+HLT
 CLR
 LAD
 DEP
 CNTRL+INIT
 CNTRL+START -> reads 02
 CNTRL+BOOT  -> reads 165024

 CLR, 165024 LAD, CTRL/START reads 165024
 773024 LAD, EXAM, reads 165024

 Reconfigured the switches on the M9312

1  2   3   4   5 6   7   8   9   10
  --- --- --- --- --- --- --- --- --- ---
 S1 Off On  Off Off Off Off Off Off On  Off

 CNTRL+HLT
 CLR
 LAD
 DEP
 CNTRL+INIT
 CNTRL+START -> reads 02
 CNTRL+BOOT  -> Run light is on, SR Disp light is on,
 CNTRL+HLT reads 173150


 CLR, 165024 LAD, CTRL/START reads 165024
 773024 LAD, EXAM, reads 165024

 773024 LAD, 773000 DEP, BUS ERR light comes on.

 Any suggestions?  I have other M9312s I could try.

 On 12/13/2017 12:38 PM, Henk Gooijen wrote:
>
> Jumping over the settings. They seem OK, as you get the AB in
> Hyperterm.
>
> That 777564 shows 000200 is also correct (as I remember that): it
> indicates “transmit buffer empty”.
>
> You can also try it the other way:
>
> * type one character in Hyperterm
> * check that 777560 has the receiver buffer full flag set (000200)
> * in 777562 you will see the typed character (in octal)
>
> 773024 showing 165024 rings a bell. IIRC, 165024 is the start address
> of the monitor on the M9312.
>
> That is the PROM “in the middle” on the board.
>
> I think that if you enter CLR, 165024 LAD, CTRL/START you will get the
> “@”.
>
> BTW, there is a second start address. One does some diagnostics, the
> other does not.
>
> My guess that on 773000 and you getting 773002 on the display means
> that you try to boot
>
> from a “device” that is specified in one of the four PROMs, but the
> PROM socket is empty …
>
> 
> 

Re: 11/04 Project

[John Welch via cctalk]

On 12/13/2017 10:41 PM, Jerry Weiss wrote:

What is the configuration of jumpers?


I have tried the following:
    1   2   3   4   5   6   7   8   9   10
   --- --- --- --- --- --- --- --- --- ---
S1 Off On  Off Off Off Off Off Off On  Off
S1 On  On  Off Off Off Off On  Off Off Off
S1 On  On  Off Off On On  Off Off On  Off
S1 On  Off Off Off On  On  Off Off On  Off
Maybe some others, never get anything to the screen.

I have some cards that are marked TP1:Red TP2:Blk TP4:Clr
and other cards marked TP1:Red TP2:Clr TP4:Blk
I would really like to hear from someone that has it working rather than 
risking popping something.


On Dec 13, 2017, at 10:34 PM, JCWelch > wrote:


So far nothing puts ‘@‘, or anything on the screen.

Sent from my iPad

On Dec 13, 2017, at 10:05 PM, Jerry Weiss > wrote:


According to the documentation EK-M9312-TM-002 M9312 
Bootstrap-Terminator Module Technical Manual

there are two addresses to use for the Console Emulator.

165020 (765020)  for Console with Diagnostics  SW 1 and 7 on
165144 (765144)  for Console w/o Diagnostics   SW 1,5,6,9 on

The switch settings below correspond to xxx004.. which is probably 
the first drive for the ROM in position 1 and does

not invoke diagnostics.

Have you tried 173000 (773000)?

Jerry


On Dec 13, 2017, at 8:37 PM, John Welch via cctech 
> wrote:


I have bi-directional communication from PC/Hyperterminal.   I 
forgot about having to tell HyperTerminal to echo characters 
locally. Anyway, 'a' comes over as 000141 and 'A' comes over as 
000101. So far so good.

However, I have not gotten "@"
CNTRL+HLT
CLR
LAD
DEP
CNTRL+INIT
CNTRL+START -> reads 02
CNTRL+BOOT  -> reads 165024

CLR, 165024 LAD, CTRL/START reads 165024
773024 LAD, EXAM, reads 165024

Reconfigured the switches on the M9312

   1  2   3   4   5 6   7   8   9   10
 --- --- --- --- --- --- --- --- --- ---
S1 Off On  Off Off Off Off Off Off On  Off

CNTRL+HLT
CLR
LAD
DEP
CNTRL+INIT
CNTRL+START -> reads 02
CNTRL+BOOT  -> Run light is on, SR Disp light is on,
CNTRL+HLT reads 173150


CLR, 165024 LAD, CTRL/START reads 165024
773024 LAD, EXAM, reads 165024

773024 LAD, 773000 DEP, BUS ERR light comes on.

Any suggestions?  I have other M9312s I could try.


On 12/13/2017 12:38 PM, Henk Gooijen wrote:

Jumping over the settings. They seem OK, as you get the AB in 
Hyperterm.


That 777564 shows 000200 is also correct (as I remember that): it 
indicates “transmit buffer empty”.


You can also try it the other way:

* type one character in Hyperterm
* check that 777560 has the receiver buffer full flag set (000200)
* in 777562 you will see the typed character (in octal)

773024 showing 165024 rings a bell. IIRC, 165024 is the start 
address of the monitor on the M9312.


That is the PROM “in the middle” on the board.

I think that if you enter CLR, 165024 LAD, CTRL/START you will get 
the “@”.


BTW, there is a second start address. One does some diagnostics, 
the other does not.


My guess that on 773000 and you getting 773002 on the display means 
that you try to boot


from a “device” that is specified in one of the four PROMs, but the 
PROM socket is empty …



*Van:* cctech > namens John Welch via 
cctech >

*Verzonden:* Wednesday, December 13, 2017 7:23:01 PM
*Aan:* cct...@classiccmp.org 
*Onderwerp:* 11/04 Project
I am back in front of the machine:

The M7856 is set thusly:
   1  2  3  4  5  6  7  8  9 10
-- -- -- -- -- -- -- -- -- -- --
S5 DN DN DN UP DN DN UP DN DN UP
S3 DN DN UP DN UP UP DN UP DN UP
S1 UP UP DN UP DN DN UP UP DN UP
S4 UP UP DN DN UP UP DN DN DN UP
S2 DN DN UP DN DN UP DN DN -- --

The M9312 is set thusly:

   1  2  3  4  5  6  7  8  9 10
-- -- -- -- -- -- -- -- -- -- --
S1 UP UP DN DN DN DN UP DN DN DN

This should be 300, 8, Odd, 1
I have what I think is null modem between the M7856 cable and a PC
running XP with Hyperterm set to 300, 8,O,1

Troubleshooting from the programmers console:
CNTRL plus HALT, no bus hang.

CLR, 777566, LAD, 101, DEP, Hyperterm shows: A
CLR, 777566, LAD, 102, DEP, Hyperterm shows: AB (the B popped up 
next to

the previous A )


CLR, 777564, LAD, EXAM, display shows: 000200
CLR, 773024, LAD, EXAM, display shows: 165024
CLR, 773024, LAD, EXAM, display shows: 165024
CLR, 773000, LAD, CNTRL plus START, console says: 173002

I am thinking that the Hyperterm should be seeing an "@" and I 
should be

able to boot from there.

Any thoughts?

Sincerely,
John Welch



--
Sincerely,
John Welch
281-353-4706 Home
713-725-7017 Cell
:qw



Jerry Weiss
j...@ieee.org 






Jerry Weiss
j...@ieee.org 





--
Sincerely,
John Welch
281-353-4706 

Re: 11/04 Project

[JCWelch via cctalk]

 CLR
 765000
 LAD
 EXAM
‘Bus Err’ light comes on.

CLR
 765020
 LAD
 CNTRL+START
Display changes to 165020 
Nothing on the terminal.

Do you know which color wire (red, clear, black) goes to which festoon 
connector (TP1, TP2, TP3, TP4)?
Don’t want to blow anything up.


Sent from my iPad

> On Dec 13, 2017, at 9:37 PM, Noel Chiappa  wrote:
> 

> From: John Welch

> Anyway, 'a' comes over as 000141 and 'A' comes over as 000101.

Good, the console is working.


> CLR
> LAD
> DEP

OK, that loads a '0' (halt) in 0.

> CNTRL+INIT
> CNTRL+START -> reads 02

OK, so it reads the HALT at 0 and stops.


> CNTRL+BOOT -> Run light is on, SR Disp light is on
> CNTRL+HLT reads 173150

Sounds like it may be looping in the high bank of ROM? That's not necessarily
wrong.

I finally figured out what the ROMs in the M9312 do; the ROMs at 765000 are
the first-level diagnostic, and the console. The bootstrap code for the
various devices is at 773000.

> 773024 LAD, 773000 DEP, BUS ERR light comes on.

That makes sense; you can't write to the ROM.


> Any suggestions?

i) Check the ROM contents; there are two kinds of M9312 console ROMs, one for
most CPUs, and one for the 11/60 and 11/70, see the tech manual for the
M9312.

So read out the first couple of words:

 CLR
 765000
 LAD
 EXAM
 EXAM
 etc

and let's see what they read.

ii) Try starting the console code directly:

 CLR
 765020
 LAD
 CNTRL+START

> I have other M9312s I could try.

Can't hurt.

   Noel

Re: 11/04 Project

[JCWelch via cctalk]

So far nothing puts ‘@‘, or anything on the screen.

Sent from my iPad

On Dec 13, 2017, at 10:05 PM, Jerry Weiss  wrote:

According to the documentation EK-M9312-TM-002 M9312 Bootstrap-Terminator 
Module Technical Manual
there are two addresses to use for the Console Emulator.

165020 (765020)  for Console with Diagnostics  SW 1 and 7 on
165144 (765144)  for Console w/o Diagnostics   SW 1,5,6,9 on

The switch settings below correspond to xxx004.. which is probably the first 
drive for the ROM in position 1 and does
not invoke diagnostics.

Have you tried 173000 (773000)?

Jerry


> On Dec 13, 2017, at 8:37 PM, John Welch via cctech  
> wrote:
> 
> I have bi-directional communication from PC/Hyperterminal.   I forgot about 
> having to tell HyperTerminal to echo characters locally. Anyway, 'a' comes 
> over as 000141 and 'A' comes over as 000101. So far so good.
> However, I have not gotten "@"
> CNTRL+HLT
> CLR
> LAD
> DEP
> CNTRL+INIT
> CNTRL+START -> reads 02
> CNTRL+BOOT  -> reads 165024
> 
> CLR, 165024 LAD, CTRL/START reads 165024
> 773024 LAD, EXAM, reads 165024
> 
> Reconfigured the switches on the M9312
> 
> 1  2   3   4   5 6   7   8   9   10
>   --- --- --- --- --- --- --- --- --- ---
> S1 Off On  Off Off Off Off Off Off On  Off
> 
> CNTRL+HLT
> CLR
> LAD
> DEP
> CNTRL+INIT
> CNTRL+START -> reads 02
> CNTRL+BOOT  -> Run light is on, SR Disp light is on,
> CNTRL+HLT reads 173150
> 
> 
> CLR, 165024 LAD, CTRL/START reads 165024
> 773024 LAD, EXAM, reads 165024
> 
> 773024 LAD, 773000 DEP, BUS ERR light comes on.
> 
> Any suggestions?  I have other M9312s I could try.
> 
>> On 12/13/2017 12:38 PM, Henk Gooijen wrote:
>> 
>> Jumping over the settings. They seem OK, as you get the AB in Hyperterm.
>> 
>> That 777564 shows 000200 is also correct (as I remember that): it indicates 
>> “transmit buffer empty”.
>> 
>> You can also try it the other way:
>> 
>> * type one character in Hyperterm
>> * check that 777560 has the receiver buffer full flag set (000200)
>> * in 777562 you will see the typed character (in octal)
>> 
>> 773024 showing 165024 rings a bell. IIRC, 165024 is the start address of the 
>> monitor on the M9312.
>> 
>> That is the PROM “in the middle” on the board.
>> 
>> I think that if you enter CLR, 165024 LAD, CTRL/START you will get the “@”.
>> 
>> BTW, there is a second start address. One does some diagnostics, the other 
>> does not.
>> 
>> My guess that on 773000 and you getting 773002 on the display means that you 
>> try to boot
>> 
>> from a “device” that is specified in one of the four PROMs, but the PROM 
>> socket is empty …
>> 
>> 
>> *Van:* cctech  namens John Welch via cctech 
>> 
>> *Verzonden:* Wednesday, December 13, 2017 7:23:01 PM
>> *Aan:* cct...@classiccmp.org
>> *Onderwerp:* 11/04 Project
>> I am back in front of the machine:
>> 
>> The M7856 is set thusly:
>> 1  2  3  4  5  6  7  8  9 10
>> -- -- -- -- -- -- -- -- -- -- --
>> S5 DN DN DN UP DN DN UP DN DN UP
>> S3 DN DN UP DN UP UP DN UP DN UP
>> S1 UP UP DN UP DN DN UP UP DN UP
>> S4 UP UP DN DN UP UP DN DN DN UP
>> S2 DN DN UP DN DN UP DN DN -- --
>> 
>> The M9312 is set thusly:
>> 
>> 1  2  3  4  5  6  7  8  9 10
>> -- -- -- -- -- -- -- -- -- -- --
>> S1 UP UP DN DN DN DN UP DN DN DN
>> 
>> This should be 300, 8, Odd, 1
>> I have what I think is null modem between the M7856 cable and a PC
>> running XP with Hyperterm set to 300, 8,O,1
>> 
>> Troubleshooting from the programmers console:
>> CNTRL plus HALT, no bus hang.
>> 
>> CLR, 777566, LAD, 101, DEP, Hyperterm shows: A
>> CLR, 777566, LAD, 102, DEP, Hyperterm shows: AB (the B popped up next to
>> the previous A )
>> 
>> 
>> CLR, 777564, LAD, EXAM, display shows: 000200
>> CLR, 773024, LAD, EXAM, display shows: 165024
>> CLR, 773024, LAD, EXAM, display shows: 165024
>> CLR, 773000, LAD, CNTRL plus START, console says: 173002
>> 
>> I am thinking that the Hyperterm should be seeing an "@" and I should be
>> able to boot from there.
>> 
>> Any thoughts?
>> 
>> Sincerely,
>> John Welch
>> 
> 
> -- 
> Sincerely,
> John Welch
> 281-353-4706 Home
> 713-725-7017 Cell
> :qw
> 

Jerry Weiss
j...@ieee.org

Re: 11/04 Project

[John Welch via cctalk]

I have bi-directional communication from PC/Hyperterminal.   I forgot 
about having to tell HyperTerminal to echo characters locally. Anyway, 
'a' comes over as 000141 and 'A' comes over as 000101. So far so good.

However, I have not gotten "@"
CNTRL+HLT
CLR
LAD
DEP
CNTRL+INIT
CNTRL+START -> reads 02
CNTRL+BOOT  -> reads 165024

CLR, 165024 LAD, CTRL/START reads 165024
773024 LAD, EXAM, reads 165024

Reconfigured the switches on the M9312

 1  2   3   4   5 6   7   8   9   10
   --- --- --- --- --- --- --- --- --- ---
S1 Off On  Off Off Off Off Off Off On  Off

CNTRL+HLT
CLR
LAD
DEP
CNTRL+INIT
CNTRL+START -> reads 02
CNTRL+BOOT  -> Run light is on, SR Disp light is on,
CNTRL+HLT reads 173150


CLR, 165024 LAD, CTRL/START reads 165024
773024 LAD, EXAM, reads 165024

773024 LAD, 773000 DEP, BUS ERR light comes on.

Any suggestions?  I have other M9312s I could try.

On 12/13/2017 12:38 PM, Henk Gooijen wrote:


Jumping over the settings. They seem OK, as you get the AB in Hyperterm.

That 777564 shows 000200 is also correct (as I remember that): it 
indicates “transmit buffer empty”.


You can also try it the other way:

  * type one character in Hyperterm
  * check that 777560 has the receiver buffer full flag set (000200)
  * in 777562 you will see the typed character (in octal)

773024 showing 165024 rings a bell. IIRC, 165024 is the start address 
of the monitor on the M9312.


That is the PROM “in the middle” on the board.

I think that if you enter CLR, 165024 LAD, CTRL/START you will get the 
“@”.


BTW, there is a second start address. One does some diagnostics, the 
other does not.


My guess that on 773000 and you getting 773002 on the display means 
that you try to boot


from a “device” that is specified in one of the four PROMs, but the 
PROM socket is empty …



*Van:* cctech  namens John Welch via 
cctech 

*Verzonden:* Wednesday, December 13, 2017 7:23:01 PM
*Aan:* cct...@classiccmp.org
*Onderwerp:* 11/04 Project
I am back in front of the machine:

The M7856 is set thusly:
 1  2  3  4  5  6  7  8  9 10
-- -- -- -- -- -- -- -- -- -- --
S5 DN DN DN UP DN DN UP DN DN UP
S3 DN DN UP DN UP UP DN UP DN UP
S1 UP UP DN UP DN DN UP UP DN UP
S4 UP UP DN DN UP UP DN DN DN UP
S2 DN DN UP DN DN UP DN DN -- --

The M9312 is set thusly:

 1  2  3  4  5  6  7  8  9 10
-- -- -- -- -- -- -- -- -- -- --
S1 UP UP DN DN DN DN UP DN DN DN

This should be 300, 8, Odd, 1
I have what I think is null modem between the M7856 cable and a PC
running XP with Hyperterm set to 300, 8,O,1

Troubleshooting from the programmers console:
CNTRL plus HALT, no bus hang.

CLR, 777566, LAD, 101, DEP, Hyperterm shows: A
CLR, 777566, LAD, 102, DEP, Hyperterm shows: AB (the B popped up next to
the previous A )


CLR, 777564, LAD, EXAM, display shows: 000200
CLR, 773024, LAD, EXAM, display shows: 165024
CLR, 773024, LAD, EXAM, display shows: 165024
CLR, 773000, LAD, CNTRL plus START, console says: 173002

I am thinking that the Hyperterm should be seeing an "@" and I should be
able to boot from there.

Any thoughts?

Sincerely,
John Welch



--
Sincerely,
John Welch
281-353-4706 Home
713-725-7017 Cell
:qw

Re: 11/04 Project

[JCWelch via cctalk]

I am much confused as to how to connect TP1, TP2, TP3, & TP4.
there is a wire coming in with spade lugs.  One wire is red, one clear, and one 
black. Just to be share which color goes to which TP lug?

Sent from my iPad

On Dec 13, 2017, at 8:37 PM, John Welch  wrote:

I have bi-directional communication from PC/Hyperterminal.   I forgot about 
having to tell HyperTerminal to echo characters locally.  Anyway, 'a' comes 
over as 000141 and 'A' comes over as 000101. So far so good.
However, I have not gotten "@"
CNTRL+HLT
CLR
LAD
DEP
CNTRL+INIT
CNTRL+START -> reads 02
CNTRL+BOOT  -> reads 165024

CLR, 165024 LAD, CTRL/START reads 165024
773024 LAD, EXAM, reads 165024

Reconfigured the switches on the M9312

 1  2   3   4   5   6   7   8   9   10
   --- --- --- --- --- --- --- --- --- ---
S1 Off On  Off Off Off Off Off Off On  Off

CNTRL+HLT
CLR
LAD
DEP
CNTRL+INIT
CNTRL+START -> reads 02
CNTRL+BOOT  -> Run light is on, SR Disp light is on, 
CNTRL+HLT reads 173150


CLR, 165024 LAD, CTRL/START reads 165024
773024 LAD, EXAM, reads 165024

773024 LAD, 773000 DEP, BUS ERR light comes on.

Any suggestions?  I have other M9312s I could try.

> On 12/13/2017 12:38 PM, Henk Gooijen wrote:
> Jumping over the settings. They seem OK, as you get the AB in Hyperterm.
> That 777564 shows 000200 is also correct (as I remember that): it indicates 
> “transmit buffer empty”.
> You can also try it the other way:
> type one character in Hyperterm
> check that 777560 has the receiver buffer full flag set (000200)
> in 777562 you will see the typed character (in octal)
>  
> 773024 showing 165024 rings a bell. IIRC, 165024 is the start address of the 
> monitor on the M9312.
> That is the PROM “in the middle” on the board.
>  
> I think that if you enter CLR, 165024 LAD, CTRL/START you will get the “@”.
> BTW, there is a second start address. One does some diagnostics, the other 
> does not.
>  
> My guess that on 773000 and you getting 773002 on the display means that you 
> try to boot
> from a “device” that is specified in one of the four PROMs, but the PROM 
> socket is empty …
>  
>  
> Van: cctech  namens John Welch via cctech 
> 
> Verzonden: Wednesday, December 13, 2017 7:23:01 PM
> Aan: cct...@classiccmp.org
> Onderwerp: 11/04 Project
>  
> I am back in front of the machine:
> 
> The M7856 is set thusly:
>  1  2  3  4  5  6  7  8  9 10
> -- -- -- -- -- -- -- -- -- -- --
> S5 DN DN DN UP DN DN UP DN DN UP
> S3 DN DN UP DN UP UP DN UP DN UP
> S1 UP UP DN UP DN DN UP UP DN UP
> S4 UP UP DN DN UP UP DN DN DN UP
> S2 DN DN UP DN DN UP DN DN -- --
> 
> The M9312 is set thusly:
> 
>  1  2  3  4  5  6  7  8  9 10
> -- -- -- -- -- -- -- -- -- -- --
> S1 UP UP DN DN DN DN UP DN DN DN
> 
> This should be 300, 8, Odd, 1
> I have what I think is null modem between the M7856 cable and a PC 
> running XP with Hyperterm set to 300, 8,O,1
> 
> Troubleshooting from the programmers console:
> CNTRL plus HALT, no bus hang.
> 
> CLR, 777566, LAD, 101, DEP, Hyperterm shows: A
> CLR, 777566, LAD, 102, DEP, Hyperterm shows: AB (the B popped up next to 
> the previous A )
> 
> 
> CLR, 777564, LAD, EXAM, display shows: 000200
> CLR, 773024, LAD, EXAM, display shows: 165024
> CLR, 773024, LAD, EXAM, display shows: 165024
> CLR, 773000, LAD, CNTRL plus START, console says: 173002
> 
> I am thinking that the Hyperterm should be seeing an "@" and I should be 
> able to boot from there.
> 
> Any thoughts?
> 
> Sincerely,
> John Welch
> 

-- 
Sincerely,
John Welch
281-353-4706 Home
713-725-7017 Cell
:qw

Re: 11/04 Project

[Noel Chiappa via cctalk]

> From: John Welch

> Anyway, 'a' comes over as 000141 and 'A' comes over as 000101.

Good, the console is working.


> CLR
> LAD
> DEP

OK, that loads a '0' (halt) in 0.

> CNTRL+INIT
> CNTRL+START -> reads 02

OK, so it reads the HALT at 0 and stops.


> CNTRL+BOOT -> Run light is on, SR Disp light is on
> CNTRL+HLT reads 173150

Sounds like it may be looping in the high bank of ROM? That's not necessarily
wrong.

I finally figured out what the ROMs in the M9312 do; the ROMs at 765000 are
the first-level diagnostic, and the console. The bootstrap code for the
various devices is at 773000.

> 773024 LAD, 773000 DEP, BUS ERR light comes on.

That makes sense; you can't write to the ROM.


> Any suggestions?

i) Check the ROM contents; there are two kinds of M9312 console ROMs, one for
most CPUs, and one for the 11/60 and 11/70, see the tech manual for the
M9312.

So read out the first couple of words:

  CLR
  765000
  LAD
  EXAM
  EXAM
  etc

and let's see what they read.

ii) Try starting the console code directly:

  CLR
  765020
  LAD
  CNTRL+START

> I have other M9312s I could try.

Can't hurt.

Noel

Re: 11/04 Project

[Noel Chiappa via cctalk]

> From: John Welch

> Any thoughts?

Concur 100% with Henk's comments.

There is a manual online for the M9312:

  http://bitsavers.org/pdf/dec/unibus/M9312_TechRef.pdf

which will tell you what the other start options are (Appendix C), but see
page 3-1, too. Note especially the bit about how the primary dianostics
are run before it starts the console emulator; I forget what it does if
the primary fails, possibly it halts?

Noel

RE: 11/04 Project

[Henk Gooijen via cctalk]

Jumping over the settings. They seem OK, as you get the AB in Hyperterm.

That 777564 shows 000200 is also correct (as I remember that): it indicates 
“transmit buffer empty”.

You can also try it the other way:

  *   type one character in Hyperterm
  *   check that 777560 has the receiver buffer full flag set (000200)
  *   in 777562 you will see the typed character (in octal)



773024 showing 165024 rings a bell. IIRC, 165024 is the start address of the 
monitor on the M9312.

That is the PROM “in the middle” on the board.



I think that if you enter CLR, 165024 LAD, CTRL/START you will get the “@”.

BTW, there is a second start address. One does some diagnostics, the other does 
not.



My guess that on 773000 and you getting 773002 on the display means that you 
try to boot

from a “device” that is specified in one of the four PROMs, but the PROM socket 
is empty …






Van: cctech  namens John Welch via cctech 

Verzonden: Wednesday, December 13, 2017 7:23:01 PM
Aan: cct...@classiccmp.org
Onderwerp: 11/04 Project

I am back in front of the machine:

The M7856 is set thusly:
 1  2  3  4  5  6  7  8  9 10
-- -- -- -- -- -- -- -- -- -- --
S5 DN DN DN UP DN DN UP DN DN UP
S3 DN DN UP DN UP UP DN UP DN UP
S1 UP UP DN UP DN DN UP UP DN UP
S4 UP UP DN DN UP UP DN DN DN UP
S2 DN DN UP DN DN UP DN DN -- --

The M9312 is set thusly:

 1  2  3  4  5  6  7  8  9 10
-- -- -- -- -- -- -- -- -- -- --
S1 UP UP DN DN DN DN UP DN DN DN

This should be 300, 8, Odd, 1
I have what I think is null modem between the M7856 cable and a PC
running XP with Hyperterm set to 300, 8,O,1

Troubleshooting from the programmers console:
CNTRL plus HALT, no bus hang.

CLR, 777566, LAD, 101, DEP, Hyperterm shows: A
CLR, 777566, LAD, 102, DEP, Hyperterm shows: AB (the B popped up next to
the previous A )


CLR, 777564, LAD, EXAM, display shows: 000200
CLR, 773024, LAD, EXAM, display shows: 165024
CLR, 773024, LAD, EXAM, display shows: 165024
CLR, 773000, LAD, CNTRL plus START, console says: 173002

I am thinking that the Hyperterm should be seeing an "@" and I should be
able to boot from there.

Any thoughts?

Sincerely,
John Welch