<div dir="ltr"><div>I too found this error.</div><div>in my opinion the setting:</div><div>set rom nodelay</div><div>causes a lot more of them</div><div>probably some test checks timed istruction sequences <br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2018-06-24 18:00 GMT+02:00 <span dir="ltr"><<a href="mailto:simh-request@trailing-edge.com" target="_blank">simh-request@trailing-edge.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Simh mailing list submissions to<br>
<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:simh-request@trailing-edge.com">simh-request@trailing-edge.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:simh-owner@trailing-edge.com">simh-owner@trailing-edge.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Simh digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: MicroVAX 3900 simulator fails BIST sometimes?<br>
(Mark Pizzolato)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Sat, 23 Jun 2018 14:11:46 -0700<br>
From: Mark Pizzolato <<a href="mailto:Mark@infocomm.com">Mark@infocomm.com</a>><br>
To: "<a href="mailto:bob@jfcl.com">bob@jfcl.com</a>" <<a href="mailto:bob@jfcl.com">bob@jfcl.com</a>>, "<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>"<br>
<<a href="mailto:simh@trailing-edge.com">simh@trailing-edge.com</a>><br>
Cc: Mark Pizzolato <<a href="mailto:Mark@infocomm.com">Mark@infocomm.com</a>><br>
Subject: Re: [Simh] MicroVAX 3900 simulator fails BIST sometimes?<br>
Message-ID:<br>
<<a href="mailto:03006E3FC39B5A48AB9DBCCC101090A8343CCCF72F@REDROOF2.alohasunset.com">03006E3FC39B5A48AB9DBCCC10109<wbr>0A8343CCCF72F@REDROOF2.<wbr>alohasunset.com</a>><br>
Content-Type: text/plain; charset="us-ascii"<br>
<br>
On Saturday, June 23, 2018 at 12:41 PM, Robert Armstrong wrote:<br>
> > Mark Pizzolato <<a href="mailto:Mark@infocomm.com">Mark@infocomm.com</a>> wrote:<br>
> >Heisenberg effects mean that the problem is never seen<br>
> <br>
> Yep, the uncertainty principle applies to software as well...<br>
> <br>
> I'm just curious - do we (well, I don't, but somebody) have source listings for<br>
> the KA655 EPROM? Supposedly one of the other hex numbers in the "?53 2 0A<br>
> FF 00 0000" message identifies the exact subtest that's failing. It might be<br>
> interesting to know that.<br>
<br>
The listings we have are for a close, but not precise, version that the ROM <br>
is built from. Without regard to precise listings, the listings don't actually <br>
have a mapping of the test numbers (and sub test numbers) to specific <br>
tests. The assignment of tests is magically built by small macros that briefly<br>
define PSECTs that each tests contributes a little content towards. There <br>
must be some nice tool that can decode the resulting collection of test <br>
numbers and map them back to particular tests. Maybe a special <br>
interpretation of data in the link map might help get there, but how it is <br>
done isn't particularly obvious.<br>
<br>
ROM debugging is a very tedious process. You poke around in the<br>
ROM binary and disassemble a section. Then you locate particular instruction <br>
Sequences in the listing. Or you do the opposite (start from the listing and<br>
look for instruction patterns in the ROM). You then put simh breakpoints in <br>
some ROM locations that you want to stop at. The presence of breakpoints<br>
adds to Heisenberg variances since simh breakpoints are implemented by <br>
checking instruction fetch addresses rather than modifying the target code to <br>
insert actual breakpoint instructions (which are architecturally meaningful <br>
within the VAX simulation). For most things Heisenberg doesn't come into <br>
play, but timing calibration stuff is the exception.<br>
<br>
Anyway, this problem is benign enough, and the lack of solid debug data <br>
has it sitting there unsolved.<br>
<br>
- Mark<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
______________________________<wbr>_________________<br>
Simh mailing list<br>
<a href="mailto:Simh@trailing-edge.com">Simh@trailing-edge.com</a><br>
<a href="http://mailman.trailing-edge.com/mailman/listinfo/simh" rel="noreferrer" target="_blank">http://mailman.trailing-edge.<wbr>com/mailman/listinfo/simh</a><br>
<br>
------------------------------<br>
<br>
End of Simh Digest, Vol 173, Issue 5<br>
******************************<wbr>******<br>
</blockquote></div><br></div>