27 Apr
2015
27 Apr
'15
1:47 a.m.
The 11/34 seems to be pretty healthy, I've punched in some code to do
some basic testing and the CPU seems to be capable of running simple
programs and the RAM seems capable of holding data. So that's good.
I've also verified that the console SLU is at the right address and
vector (it wasn't initially, due to a pair of bad DIP switch blocks),
and I can read/write characters from/to it. Huzzah.
The bootstrap ROM doesn't seem to be executing properly, however. After
power-on or a BOOT/CTRL It'll run for a fraction of a second and then
halt, leaving me at address 0 with 161721 displayed. ROM Data appears
at the expected addresses (773000-773777, 765000-765777) but I don't
know if it's at all correct.
I need to scare up a second SLU so I can get an emulated TU-58 hooked up
to try booting XXDP, but in the meantime I thought I'd see if I could
verify the ROM contents manually (it's only 512 bytes long). I can't
find a listing, however -- the operator / maintenance manual doesn't
contain it and I haven't found it anywhere else. I've found a reference
to a microfiche, "EP-M9301-RL-A" that supposedly contains these
listings, but it doesn't appear to be archived anywhere. Anyone have
this, or have dumps of the M9301-YB PROMs?
Thanks,
Josh
27 Apr
27 Apr
2:01 a.m.
Josh,
here some resources which may be helpful:
- can you run the console emulator?
To boot: Set all switches on the M9301 to ON and power on
OR enter 165020 LAD CTRL-START
- if the console emulator runs, you can load any paper tape image
diagnostic with my PDP11GUI
http://www.retrocmp.com/tools/pdp11gui
- I organized all known PDP11 diagnostics material into a database
http://www.retrocmp.com/tools/pdp-11-diagnostic-database/202-pdp-11-diagnos…
There you can download paper tape images, and also the *.BIN and *.BIC
from XXDP disks. These are in papertape format too.
- I found that the "-YA/B/C../F.." label on M9301's doesn't
necessarily
match the ROM content.
- I have dumps of M9301-YA and -YF
- I can burn M9301 ROMs
- and I also have a spare DL11-W to offer
Joerg
Am 27.04.2015 um 07:47 schrieb Josh Dersch:
The 11/34 seems to be pretty healthy, I've punched
in some code to do
some basic testing and the CPU seems to be capable of running simple
programs and the RAM seems capable of holding data. So that's good.
I've also verified that the console SLU is at the right address and
vector (it wasn't initially, due to a pair of bad DIP switch blocks),
and I can read/write characters from/to it. Huzzah.
The bootstrap ROM doesn't seem to be executing properly, however. After
power-on or a BOOT/CTRL It'll run for a fraction of a second and then
halt, leaving me at address 0 with 161721 displayed. ROM Data appears
at the expected addresses (773000-773777, 765000-765777) but I don't
know if it's at all correct.
I need to scare up a second SLU so I can get an emulated TU-58 hooked up
to try booting XXDP, but in the meantime I thought I'd see if I could
verify the ROM contents manually (it's only 512 bytes long). I can't
find a listing, however -- the operator / maintenance manual doesn't
contain it and I haven't found it anywhere else. I've found a reference
to a microfiche, "EP-M9301-RL-A" that supposedly contains these
listings, but it doesn't appear to be archived anywhere. Anyone have
this, or have dumps of the M9301-YB PROMs?
Thanks,
Josh
3:05 a.m.
On 4/26/15 11:01 PM, J?rg Hoppe wrote:
Josh,
here some resources which may be helpful:
- can you run the console emulator?
To boot: Set all switches on the M9301 to ON and power on
OR enter 165020 LAD CTRL-START
I should have clarified, I've been running
with all switches set to ON
(and after the fiasco with the SLU's address DIP switches, I confirmed
that they're all actually closed :)). The console emulator does not
run, either at power-on or manually (I wasn't aware it could be started
from that address -- I didn't see it in the
documentation but I'm sure I
just skimmed over it...).
At 165000-165776 there's just RAM (I have 128KW installed); At 765000-
765776 the ROM code appears. Should the ROM be getting mapped into the
first 64K of the address space at power-up?
- if the console emulator runs, you can load any paper tape image
diagnostic with my PDP11GUI
http://www.retrocmp.com/tools/pdp11gui
- I organized all known PDP11 diagnostics material into a database
http://www.retrocmp.com/tools/pdp-11-diagnostic-database/202-pdp-11-diagnos…
There you can download paper tape images, and also the *.BIN and *.BIC
from XXDP disks. These are in papertape format too.
Very cool! Once I get things running a bit better I'll have to give
that a shot. Thanks for putting that together!
- I found that the "-YA/B/C../F.." label on
M9301's doesn't
necessarily match the ROM content.
- I have dumps of M9301-YA and -YF
- I can burn M9301 ROMs
- and I also have a spare DL11-W to offer
Thanks, I may have to take you up on some
of that, we'll see...
- Josh
Joerg
Am 27.04.2015 um 07:47 schrieb Josh Dersch:
The 11/34 seems to be pretty healthy, I've
punched in some code to do
some basic testing and the CPU seems to be capable of running simple
programs and the RAM seems capable of holding data. So that's good.
I've also verified that the console SLU is at the right address and
vector (it wasn't initially, due to a pair of bad DIP switch blocks),
and I can read/write characters from/to it. Huzzah.
The bootstrap ROM doesn't seem to be executing properly, however. After
power-on or a BOOT/CTRL It'll run for a fraction of a second and then
halt, leaving me at address 0 with 161721 displayed. ROM Data appears
at the expected addresses (773000-773777, 765000-765777) but I don't
know if it's at all correct.
I need to scare up a second SLU so I can get an emulated TU-58 hooked up
to try booting XXDP, but in the meantime I thought I'd see if I could
verify the ROM contents manually (it's only 512 bytes long). I can't
find a listing, however -- the operator / maintenance manual doesn't
contain it and I haven't found it anywhere else. I've found a reference
to a microfiche, "EP-M9301-RL-A" that supposedly contains these
listings, but it doesn't appear to be archived anywhere. Anyone have
this, or have dumps of the M9301-YB PROMs?
Thanks,
Josh
3:19 a.m.
I could be wrong, but ISTR that in the first few words of a ROM
are the two capitals of the boot device that the PROM supports.
Proms are of course present on the board ...
I never had an M9301, always M9312.
- Henk
-----Oorspronkelijk bericht-----
From: Josh Dersch
Sent: Monday, April 27, 2015 9:05 AM
To: J?rg Hoppe ; cctalk at classiccmp.org
Subject: Re: M9301-YB Bootstrap/Terminator ROM dumps / listings?
On 4/26/15 11:01 PM, J?rg Hoppe wrote:
Josh,
here some resources which may be helpful:
- can you run the console emulator?
To boot: Set all switches on the M9301 to ON and power on
OR enter 165020 LAD CTRL-START
I should have clarified, I've been running
with all switches set to ON
(and after the fiasco with the SLU's address DIP switches, I confirmed
that they're all actually closed :)). The console emulator does not
run, either at power-on or manually (I wasn't aware it could be started
from that address -- I didn't see it in the
documentation but I'm sure I
just skimmed over it...).
At 165000-165776 there's just RAM (I have 128KW installed); At 765000-
765776 the ROM code appears. Should the ROM be getting mapped into the
first 64K of the address space at power-up?
- if the console emulator runs, you can load any paper tape image
diagnostic with my PDP11GUI
http://www.retrocmp.com/tools/pdp11gui
- I organized all known PDP11 diagnostics material into a database
http://www.retrocmp.com/tools/pdp-11-diagnostic-database/202-pdp-11-diagnos…
There you can download paper tape images, and also the *.BIN and *.BIC
from XXDP disks. These are in papertape format too.
Very cool! Once I get things running a bit better I'll have to give
that a shot. Thanks for putting that together!
- I found that the "-YA/B/C../F.." label on
M9301's doesn't necessarily
match the ROM content.
- I have dumps of M9301-YA and -YF
- I can burn M9301 ROMs
- and I also have a spare DL11-W to offer
Thanks, I may have to take you up on some
of that, we'll see...
- Josh
Joerg
Am 27.04.2015 um 07:47 schrieb Josh Dersch:
The 11/34 seems to be pretty healthy, I've
punched in some code to do
some basic testing and the CPU seems to be capable of running simple
programs and the RAM seems capable of holding data. So that's good.
I've also verified that the console SLU is at the right address and
vector (it wasn't initially, due to a pair of bad DIP switch blocks),
and I can read/write characters from/to it. Huzzah.
The bootstrap ROM doesn't seem to be executing properly, however. After
power-on or a BOOT/CTRL It'll run for a fraction of a second and then
halt, leaving me at address 0 with 161721 displayed. ROM Data appears
at the expected addresses (773000-773777, 765000-765777) but I don't
know if it's at all correct.
I need to scare up a second SLU so I can get an emulated TU-58 hooked up
to try booting XXDP, but in the meantime I thought I'd see if I could
verify the ROM contents manually (it's only 512 bytes long). I can't
find a listing, however -- the operator / maintenance manual doesn't
contain it and I haven't found it anywhere else. I've found a reference
to a microfiche, "EP-M9301-RL-A" that supposedly contains these
listings, but it doesn't appear to be archived anywhere. Anyone have
this, or have dumps of the M9301-YB PROMs?
Thanks,
Josh
4:03 a.m.
On 4/27/15 12:05 AM, Josh Dersch wrote:
On 4/26/15 11:01 PM, J?rg Hoppe wrote:
Answering my own question (I wasn't thinking w/the above) -- the front
panel will let me see whatever memory I want as a flat 18-bit address
space from 000000-777776 but the CPU only has a 16-bit address range,
and with memory mapping turned off the I/O page appears at the top of
the 16-bit address space. So when I peek at 160000-177777 from the
front panel I see RAM, but when the CPU is executing it's addressing ROM
in the I/O page.
I'm going to do a bit of disassembly tomorrow to see what the CPU's
executing from ROM and why it's halting. It's clearly time for me to
get to bed now, however :).
Thanks,
Josh
Josh,
here some resources which may be helpful:
- can you run the console emulator?
To boot: Set all switches on the M9301 to ON and power on
OR enter 165020 LAD CTRL-START
I should have clarified, I've been running
with all switches set to ON
(and after the fiasco with the SLU's address DIP switches, I confirmed
that they're all actually closed :)). The console emulator does not
run, either at power-on or manually (I wasn't aware it could be
started from that address -- I didn't see it in the documentation but
I'm sure I just skimmed over it...).
At 165000-165776 there's just RAM (I have 128KW installed); At 765000-
765776 the ROM code appears. Should the ROM be getting mapped into
the first 64K of the address space at power-up?
5:11 p.m.
You can find a dump and partial disassembly of PROMs 034A9, 035A9, 036A9,
and 037A9 here
http://www.chdickman.com/pdp11/Notes/M9301.shtml
-chuck
3:54 a.m.
Josh,
I read your post again, couldn't stop my thoughts spinning.
The bootstrap ROM doesn't seem to be executing
properly, however. After
power-on or a BOOT/CTRL It'll run for a fraction of a second and then
halt, leaving me at address 0 with 161721 displayed. ROM Data appears
at the expected addresses (773000-773777, 765000-765777) but I don't
know if it's at all correct.
Display of 161721 looks evil to me: it could be a
"165721" (a valid ROM
address) with a failing bit 4000 = bit #11.
Theory: the CPU has a defective data or address line. (The bus drivers
are the usual suspects).
To test you have to read the ROM with CPU code, not over the KY11
console. You'll have to write a short assember program which copies
165000 etc to RAM 1000 or so. Then verify the copy with KY11.
If RAM == ROM, my theory is wrong.
Of course it may happen that your copy loop will not run at all because
of a cpu defect.
So best you develop and test this program with PDP11GUI and an attached
SimH before, see PDP11GUI tutorial. But keep in mind that the SimH
machines do not have 165000 implemented.
Joerg
3374
days inactive
3374
days old
6 comments
4 participants
participants (4)
-
chd＠chdickman.com -
derschjo＠gmail.com -
henk.gooijen＠hotmail.com -
j_hoppe＠t-online.de