Retro/pcjs
Watch
1
0
Fork
You've already forked pcjs
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Moved all the KA10 diagnostics into a ka10 folder

Browse source
This commit is contained in:
Jeff 2017-03-31 16:57:40 -07:00 • committed by Jeff Parsons
commit 6eba847a18
57 changed files with 76 additions and 53 deletions
Download patch file Download diff file Expand all files Collapse all files

10
_posts/2017-03-21-the-macro-10-assembler-50-years-later.md
View file

@ -8,7 +8,7 @@ machines:
type: pdp10
config: /devices/pdp10/machine/ka10/test/debugger/machine.xml
debugger: true
commands: a 30724 /apps/pdp10/diags/klad/dakaa/DAKAA.MAC
commands: a 30724 /apps/pdp10/diags/ka10/dakaa/DAKAA.MAC
---
A few weeks ago, I finished my first cut of the *core* PDP-10 instructions in PDPjs. Most of my remaining work
@ -49,9 +49,9 @@ Any machine that includes the PDPjs Debugger (like the machine below) now includ
{% include machine.html id="testka10" %}
The above machine uses the Debugger's assemble ('a') command to assemble DEC's "DAKAA" diagnostic
[KA10 Basic Instruction Diagnostic](/apps/pdp10/diags/klad/dakaa/) and load the resulting code at address 30724:
[KA10 Basic Instruction Diagnostic](/apps/pdp10/diags/ka10/dakaa/) and load the resulting code at address 30724:
a 30724 /apps/pdp10/diags/klad/dakaa/DAKAA.MAC
a 30724 /apps/pdp10/diags/ka10/dakaa/DAKAA.MAC
The Debugger invokes the MACRO-10 mini-assembler whenever the target address is followed by an argument ending with ".MAC".
@ -206,8 +206,8 @@ now, since I'm holding off on all floating-point support for as long as possible
Much more work is needed to make the MACRO-10 "Mini-Assembler" a general-purpose assembler, but it's already proved itself
useful in assembling the following tests:
- [KA10 Basic Instruction Diagnostic #1](/apps/pdp10/diags/klad/dakaa/)
- [KA10 Basic Instruction Diagnostic #4](/apps/pdp10/diags/klad/dakad/)
- [KA10 Basic Instruction Diagnostic #1](/apps/pdp10/diags/ka10/dakaa/)
- [KA10 Basic Instruction Diagnostic #4](/apps/pdp10/diags/ka10/dakad/)
- [Assorted MACRO-10 Mini-Assembler Tests](/apps/pdp10/tests/macro10/)
However, there's "*assembling*" and then there's "*assembling correctly*". One early problem I had to immediately

16
_posts/2017-03-24-stepping-through-pdp-10-diagnostics.md
View file

@ -8,19 +8,19 @@ machines:
type: pdp10
config: /devices/pdp10/machine/ka10/test/debugger/machine.xml
debugger: true
commands: a 30724 /apps/pdp10/diags/klad/dakaa/DAKAA.MAC
commands: a 30724 /apps/pdp10/diags/ka10/dakaa/DAKAA.MAC
---
Now that the PDPjs MACRO-10 Mini-Assembler is [limping along](/blog/2017/03/21/), it's time to start assembling some
of DEC's PDP-10 "Basic Instruction" diagnostics and loading them into a test machine. The first diagnostic I tried was
[KA10 Basic Instruction Diagnostic #1 (MAINDEC-10-DAKAA)](/apps/pdp10/diags/klad/dakaa/), which has been loaded into
[KA10 Basic Instruction Diagnostic #1 (MAINDEC-10-DAKAA)](/apps/pdp10/diags/ka10/dakaa/), which has been loaded into
the machine below.
{% include machine.html id="testka10" %}
Here were the results of my first run attempt:
>> a 30724 /apps/pdp10/diags/klad/dakaa/DAKAA.MAC
>> a 30724 /apps/pdp10/diags/ka10/dakaa/DAKAA.MAC
starting PCjs MACRO-10 Mini-Assembler...
loading DAKAA.MAC
CPU will not be auto-started (click Run to start)
@ -54,13 +54,13 @@ Here were the results of my first run attempt:
035057: 000000 000000 UUO 0,0 ;history=1
Happily, this was a good outcome, because 035057 is the end of the test. If you look at the diagnostic's
[listing file](/apps/pdp10/diags/klad/dakaa/DAKAA.LST.txt), this is what you would normally see at address 035057:
[listing file](/apps/pdp10/diags/ka10/dakaa/DAKAA.LST.txt), this is what you would normally see at address 035057:
035057 254 00 0 00 030057 ENDXX: JRST BEGEND ;LOOP PROGRAM
I had similar success with [Diagnostic #2 (MAINDEC-10-DAKAB)](/apps/pdp10/diags/klad/dakab/).
I had similar success with [Diagnostic #2 (MAINDEC-10-DAKAB)](/apps/pdp10/diags/ka10/dakab/).
Problems started to crop up in [Diagnostic #3 (MAINDEC-10-DAKAC)](/apps/pdp10/diags/klad/dakac/):
Problems started to crop up in [Diagnostic #3 (MAINDEC-10-DAKAC)](/apps/pdp10/diags/ka10/dakac/):
CAME [0,-1] ;PASS TEST IF C(AC)=0,,-1
@ -68,9 +68,9 @@ Based on the comment, it's clear what they really meant was either "[0,,-1]" or
desired result, which means that even when the assembler parses an mnemonic-less instruction like "0,-1", it must still truncate
the second (address) operand. Once I generated the appropriate value (000000,777777), the test passed.
And I had several failures running [Diagnostic #4 (MAINDEC-10-DAKAD)](/apps/pdp10/diags/klad/dakad/):
And I had several failures running [Diagnostic #4 (MAINDEC-10-DAKAD)](/apps/pdp10/diags/ka10/dakad/):
>> a 30724 /apps/pdp10/diags/klad/dakad/DAKAD.MAC
>> a 30724 /apps/pdp10/diags/ka10/dakad/DAKAD.MAC
starting PCjs MACRO-10 Mini-Assembler...
loading DAKAD.MAC
1986 words loaded at 030724-034625