<div dir="ltr"><div><br></div><br><div><div class="gmail_extra"><br><div class="gmail_quote">2015-12-30 18:57 GMT+01:00 Bob Supnik <span dir="ltr"><<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">It's the MMU.<br>
<br>
After adding the BEVENT disable logic, I noticed that the MMU option cannot be disabled in any model, although it was in fact optional in the KDF11A module (but not the 11/23 system). So I hacked the configuration table to make the MMU optional and tried an 11/23 with no MMU. It hangs just like the 11/03, 04, 05, and 20.<br></blockquote><div><br></div><div>Great that we have a solution for BEVENT!<div><br></div><div>According to the manual XXDP shall resort to the small monitor if the MMU is non present or faulty. (page 2-2 indicate so as far as I read it)</div><div><br></div><div>I tested the images at <a href="http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/xxdp/">http://www.ibiblio.org/pub/academic/computer-science/history/pdp-11/xxdp/</a></div><div>I can boot the two XXDP RL02 images attached to rl0 on 11/04, 11/05 and 11/20.<br></div><div><br></div><div><div>PDP-11 simulator V4.0-0 Beta git commit id: ea4d9a16</div><div>sim> set 11/04</div><div>Disabling XQ</div><div>sim> attach rl0 ./xxdp22.rl02.img </div><div>sim> b rl0</div><div><br></div><div><br></div><div>CHMDLD0 XXDP+ DL MONITOR</div><div>BOOTED VIA UNIT 0</div><div>28K UNIBUS SYSTEM</div><div><br></div><div>ENTER DATE (DD-MMM-YY): </div><div>Simulation stopped, PC: 150574 (BPL 150652)</div><div>sim> attach rl0 ./xxdp25.rl02.img</div><div>sim> b rl0</div><div><br></div><div><br></div><div>CPU NOT SUPPORTED BY XXDP-XM</div><div><br></div><div><br></div><div><br></div><div>BOOTING UP XXDP-SM SMALL MONITOR</div><div><br></div><div><br></div><div>XXDP-SM SMALL MONITOR - XXDP V2.4</div><div>REVISION: D0</div><div>BOOTED FROM DL0</div><div>28KW OF MEMORY</div><div>UNIBUS SYSTEM</div><div><br></div><div>RESTART ADDRESS: 152010</div><div>TYPE "H" FOR HELP </div><div><br></div><div>.</div><div>Simulation stopped, PC: 151006 (TST R0)</div><div>sim> set 11/05</div><div>sim> b rl0</div><div><br></div><div><br></div><div>CPU NOT SUPPORTED BY XXDP-XM</div><div><br></div><div><br></div><div><br></div><div>BOOTING UP XXDP-SM SMALL MONITOR</div><div><br></div><div><br></div><div>XXDP-SM SMALL MONITOR - XXDP V2.4</div><div>REVISION: D0</div><div>BOOTED FROM DL0</div><div>28KW OF MEMORY</div><div>UNIBUS SYSTEM</div><div><br></div><div>RESTART ADDRESS: 152010</div><div>TYPE "H" FOR HELP </div><div><br></div><div>.</div><div>Simulation stopped, PC: 151002 (JSR PC,150664)</div><div>sim> set 11/20</div><div>sim> b rl0</div><div><br></div><div><br></div><div>CPU NOT SUPPORTED BY XXDP-XM</div><div><br></div><div><br></div><div><br></div><div>BOOTING UP XXDP-SM SMALL MONITOR</div><div><br></div><div><br></div><div>XXDP-SM SMALL MONITOR - XXDP V2.4</div><div>REVISION: D0</div><div>BOOTED FROM DL0</div><div>28KW OF MEMORY</div><div>UNIBUS SYSTEM</div><div><br></div><div>RESTART ADDRESS: 152010</div><div>TYPE "H" FOR HELP </div><div><br></div><div>.</div><div>Simulation stopped, PC: 150674 (BPL 150750)</div><div><br></div><div>So it cannot be the MMU (not alone at least). It has to be a combination with device driver. </div></div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
Why it fails is unknown. Mattis' real 11/04 gets further than the simulator, although it ultimately fails.<br></blockquote><div><br></div><div>I am not sure if this is a co-incidence but the real 11/03 behaves very similar to the emulated 11/04 in that sense that the address it stops at when halted are very similar. The emulated 11/04 seems to be in some kind of loop testing for console input.</div><div><br></div><div>I did some further testing creating DU-device images (RD51) for XXDP+, XXDP V2.5 (2.4?) from the RL02-images mentioned above. They both boot on a 11/04 (and all the others) in SimH.</div><div><br></div><div><a href="https://dl.dropboxusercontent.com/u/96935524/xxdp-plus-du.dsk.gz">https://dl.dropboxusercontent.com/u/96935524/xxdp-plus-du.dsk.gz</a><br></div><div><a href="https://dl.dropboxusercontent.com/u/96935524/xxdp-v25-du.dsk.gz">https://dl.dropboxusercontent.com/u/96935524/xxdp-v25-du.dsk.gz</a><br></div><div><br></div><div>Then I used the V2.2 XXDP image I posted earlier and made a small RD51 image out of it.</div><div><br></div><div><a href="https://dl.dropboxusercontent.com/u/96935524/xxdp-v22-du.dsk.gz">https://dl.dropboxusercontent.com/u/96935524/xxdp-v22-du.dsk.gz</a><br></div><div><br></div><div>In SimH it boots on 11/73 but not the 11/04. </div><div><br></div><div>I have not been able to test real systems yet.</div><div><br></div><div>I don't think this is such a big issue since SimH can in fact run both XXDP+ and XXDP V2.5 (V2.6) and the real machine also had problems with XXDP V2.2. It can also be bugs in XXDP V2.2 that behaves slightly different?</div><div><br></div><div>/Mattis</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<br>
/Bob<br>
<br>
On 12/30/2015 12:00 PM, <a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-edge.com</a> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Message: 1<br>
Date: Wed, 30 Dec 2015 11:28:35 -0500<br>
From: Bob Supnik <<a href="mailto:bob@supnik.org" target="_blank">bob@supnik.org</a>><br>
To: "<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a>" <<a href="mailto:simh@trailing-edge.com" target="_blank">simh@trailing-edge.com</a>><br>
Subject: Re: [Simh] XXDP v2<br>
Message-ID: <<a href="mailto:56840633.5080505@supnik.org" target="_blank">56840633.5080505@supnik.org</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<span><br>
<br>
I did a quick hack and removed the clock from the device list,<br>
effectively disabling it. With that done, the 11/23 runs XXDP V2<br>
correctly, with 64KB of memory. I'll add BEVENT DISABLE to formalize this.<br>
<br>
So the failing systems are the 03, 04, 05, and 20. Possible common factors:<br>
<br>
- no memory management<br>
- no EIS<br>
<br>
I tried an 11/03 with EIS and no clock, and it fails, so EIS does not<br>
appear to be the problem.<br>
<br>
I'm now looking for XXDP monitor sources. The failure happens before<br>
anything is printed, but a listing would still be of great help.<br>
<br>
/Bob<br>
<br>
<br></span>
------------------------------<br>
<br>
Subject: Digest Footer<span><br>
<br>
_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a><br>
<br></span>
------------------------------<br>
<br>
End of Simh Digest, Vol 143, Issue 27<br>
*************************************<br>
</blockquote><div><div>
<br>
_______________________________________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com" target="_blank">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.com/mailman/listinfo/simh</a></div></div></blockquote></div><br></div></div></div>