Command Line Interface
The Command Line Interface
The MSCP emulator provides a command line interface. You connect to the command line interface via the USB port on the controller. This provides a asynchronuous serial connection to the microcontroller. The parameters of the serial line are
- 115'200baud
- 8 data bits
- no parity
- one start bit
- one stop bit
Commands can be abbreviated, e.g. sh or sho for show. However you must provide enough characters to make the keywords unique.
Important note
The command line interface may access the same data structures as the MSCP emulation itself. Currently there is only very little protection. In other words, many commands may conflict with a running operating system. This will be improved in the near future and locks and mutex will be added to make sure that there are no conflicts anymore. So for the time being don’t use the command line interface extensively when an PDP-11 operation system is activ.
Disk Emulator Commands
There are a set of basic commands that control the disk emulation. We suppose that you have a MBR formatted SD-Card inserted with a FAT-16/FAT-32 formatted partition
dir
Shows the content of the directory. Without any directory name it shows the content of the current working directory
cd
Changes the directory. The dot and dotdot work as within MS-DOS or Unix systems. After changing the directory all commands which use file or directory names refer to this directory
pwd
Shows the current working directory. No parameters allowed.
show
There are several show commands, there are a lot more show commands for debugging purpses which will be documented in the future.
show version
Prints information about the microcontroller and the firmware
]show version
Universal Disk Emulator V2 Vers 1.0.0 Jun 26 2026 11:18:54 CPLD Interface active
CPLD Interface ...: 40
System Uptime ....: 0 Days 00:00:03
]
show units
Shows that status of the currently four units. It shows if the unit is attached, whether it is attached to a partition or a file and prints some information about the attached partition or file.
]show units
Unit 0 (0x4D90) is attached to file (0x6A56) /diskimages/rt11v57du4.dsk
Fragments of file
Start:002F0F34 Length:00000180
Start:002F10F4 Length:00021C40
Drive has 0x00021DB0 blocks, 0x11 sectors/track, 0x08 tracks/cylinder and 0x0400 cylinders
Drive type/flags and name 0x00/0x00 RD53
Unit is ONLINE
Unit 1 (0x4DA0) is not attached
Unit 2 (0x4DB0) is not attached
Unit 3 (0x4DC0) is not attached
]
show partitions
When you insert a MBR formatted SD-Card the MSCP emulator reads all partitions and keeps them in an internal list of available partitions.
]show partitions
Partition 01 (pcb:0x6FE2) starting at sector 0x00000800 MBR at 0x00000000 is not attached
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 02 (pcb:0x6FC2) starting at sector 0x00006000 MBR at 0x00000000 is not attached
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 03 (pcb:0x6FA2) starting at sector 0x0000B800 MBR at 0x00000000 is idle offset 0x01DE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 04 (pcb:0x6F82) starting at sector 0x00011000 MBR at 0x00010800 is idle offset 0x01BE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 05 (pcb:0x6F62) starting at sector 0x00016800 MBR at 0x00016000 is idle offset 0x01BE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 06 (pcb:0x6F42) starting at sector 0x0001C000 MBR at 0x0001B800 is idle offset 0x01BE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 07 (pcb:0x6F22) starting at sector 0x00021800 MBR at 0x00021000 is not attached
Drive has 0x0004BFA0 blocks, 0x11 sectors/track, 0x0F tracks/cylinder and 0x0001 cylinders
Drive type/flags and name 0x00/0x01 RD54
Partition 08 (pcb:0x6F02) starting at sector 0x0006E000 MBR at 0x0006D808 is not attached
Drive has 0x0004BFA0 blocks, 0x11 sectors/track, 0x0F tracks/cylinder and 0x0001 cylinders
Drive type/flags and name 0x00/0x01 RD54
Partition 43 (pcb:0x6EE2) starting at sector 0x000BA800 MBR at 0x000BA008 is volume C:
Label:"FILES " Volume Size: 14'759'936 Sectors
]
show logging
The MSCP emulator constantly performs logging in a circular memory buffer. You can display the content of the logging and after that the logging buffer is reset. The logging buffer is divided into an initial buffer that collects the first entries and a circular buffer that catches the last entries. This is mainly for debugging purposes but it gives an view into the disk IOs a working operating system does.
]show logg
Logging 768 start entries starting at 0x7000
0x7000 INIT (3D) Input 0x70, INTFLAGS 0x00
0x7004 INIT (42) Input 0x78, INTFLAGS 0x00
0x7008 Trace ID 0x1E, Bytes 0x02 0x13 Word 011402
0x700C Trace ID 0x10, Bytes 0x01 0x00 Word 000001
0x7010 Trace ID 0x11, Bytes 0x00 0x00 Word 000000
0x7014 Trace ID 0x12, Bytes 0x01 0x00 Word 000001
0x7018 Trace ID 0x13, Bytes 0x00 0x00 Word 000000
0x701C Trace ID 0x1E, Bytes 0x02 0x13 Word 011402
0x7020 Trace ID 0x1E, Bytes 0x02 0x13 Word 011402
0x7024 Trace ID 0x14, Bytes 0x00 0x05 Word 002400
0x7028 Trace ID 0x15, Bytes 0x00 0x00 Word 000000
0x702C Trace ID 0x18, Bytes 0x00 0x00 Word 000000
0x7030 Trace ID 0x16, Bytes 0x01 0x00 Word 000001
0x7034 Trace ID 0x18, Bytes 0x00 0x80 Word 100000
0x7038 Trace ID 0x17, Bytes 0x01 0x00 Word 000001
0x703C Trace ID 0x18, Bytes 0x00 0x00 Word 000000
0x7040 Trace ID 0x1E, Bytes 0x02 0x13 Word 011402
0x7044 Poll DMA Get Descriptor ......: 00002410
0x7048 Trace ID 0x73, Bytes 0x00 0x00 Word 000000
0x704C Trace ID 0x1E, Bytes 0x01 0x13 Word 011401
0x7050 Poll DMA Get Descriptor ......: 00002410
0x7054 Poll DMA Get Packet ..........: 00001064
0x7058 Poll DMA Put Descriptor ......: 00002412
0x705C Trace ID 0x71, Bytes 0x09 0x00 Word 000011
0x7060 Trace ID 0x7F, Bytes 0x00 0x00 Word 000000
...
0x7BD4 Trace ID 0x50, Bytes 0x00 0x04 Word 002000
0x7BD8 Trace ID 0x5F, Bytes 0x00 0x00 Word 000000
0x7BDC LBN: 53'979./ 0x0000D2DB
0x7BE0 PBN: 2'784'527./ 0x002A7D0F
0x7BE4 Trace ID 0x7E, Bytes 0x00 0x00 Word 000000
0x7BE8 Poll DMA Get Descriptor ......: 00002226
0x7BEC Poll DMA Put Packet ..........: 00001042
0x7BF0 Poll DMA Put Descriptor ......: 00002230
0x7BF4 Poll DMA Write Flag ..........: 00002224
0x7BF8 Poll DMA Get Descriptor ......: 00002232
0x7BFC Trace ID 0x73, Bytes 0x00 0x00 Word 000000
Logging 256 circular entries. Logging Pointer 0x7C4C
0x7C4C Trace ID 0x7F, Bytes 0x00 0x00 Word 000000
...
...
0x7C2C Trace ID 0x7E, Bytes 0x00 0x00 Word 000000
0x7C30 Poll DMA Get Descriptor ......: 00165026
0x7C34 Poll DMA Put Packet ..........: 00165260
0x7C38 Poll DMA Put Descriptor ......: 00165030
0x7C3C Poll DMA Write Flag ..........: 00165024
0x7C40 IACK (1E) Vector 000154
0x7C44 Poll DMA Get Descriptor ......: 00165032
0x7C48 Trace ID 0x73, Bytes 0x00 0x00 Word 000000
]
activate
As not all operating systems can create partition of type Linux the activate command allows to change the partition type of a HFS+ or FAT-12 partition to be overwritten with the partition type Linux.
After a partition has been activated it can be attached to a unit.
Partitions that are recognised as valid, i.e. of type HFS+ or MS-DOS,
are marked as idle. Only idle partitions can be activated.
In the following we have a MBR formatted SD-Card with a total of nine partitions. Tha last being the FAT-32 formatted partitions that can hold disk image files. Partitions 3, 4, 5, 6 are idle and we activate Partition 4.
]show partitions
Partition 01 (pcb:0x6FE2) starting at sector 0x00000800 MBR at 0x00000000 is not attached
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 02 (pcb:0x6FC2) starting at sector 0x00006000 MBR at 0x00000000 is not attached
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 03 (pcb:0x6FA2) starting at sector 0x0000B800 MBR at 0x00000000 is idle offset 0x01DE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 04 (pcb:0x6F82) starting at sector 0x00011000 MBR at 0x00010800 is idle offset 0x01BE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 05 (pcb:0x6F62) starting at sector 0x00016800 MBR at 0x00016000 is idle offset 0x01BE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 06 (pcb:0x6F42) starting at sector 0x0001C000 MBR at 0x0001B800 is idle offset 0x01BE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 07 (pcb:0x6F22) starting at sector 0x00021800 MBR at 0x00021000 is not attached
Drive has 0x0004BFA0 blocks, 0x11 sectors/track, 0x0F tracks/cylinder and 0x0001 cylinders
Drive type/flags and name 0x00/0x01 RD54
Partition 08 (pcb:0x6F02) starting at sector 0x0006E000 MBR at 0x0006D808 is not attached
Drive has 0x0004BFA0 blocks, 0x11 sectors/track, 0x0F tracks/cylinder and 0x0001 cylinders
Drive type/flags and name 0x00/0x01 RD54
Partition 43 (pcb:0x6EE2) starting at sector 0x000BA800 MBR at 0x000BA008 is volume C:
Label:"FILES " Volume Size: 14'759'936 Sectors
]activate partition4
]show partitions
Partition 01 (pcb:0x6FE2) starting at sector 0x00000800 MBR at 0x00000000 is not attached
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 02 (pcb:0x6FC2) starting at sector 0x00006000 MBR at 0x00000000 is not attached
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 03 (pcb:0x6FA2) starting at sector 0x0000B800 MBR at 0x00000000 is idle offset 0x01DE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 04 (pcb:0x6F82) starting at sector 0x00011000 MBR at 0x00010800 is not attached
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 05 (pcb:0x6F62) starting at sector 0x00016800 MBR at 0x00016000 is idle offset 0x01BE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 06 (pcb:0x6F42) starting at sector 0x0001C000 MBR at 0x0001B800 is idle offset 0x01BE
Drive has 0x00005000 blocks, 0x28 sectors/track, 0x02 tracks/cylinder and 0x0200 cylinders
Drive type/flags and name 0x01/0x00 RL02
Partition 07 (pcb:0x6F22) starting at sector 0x00021800 MBR at 0x00021000 is not attached
Drive has 0x0004BFA0 blocks, 0x11 sectors/track, 0x0F tracks/cylinder and 0x0001 cylinders
Drive type/flags and name 0x00/0x01 RD54
Partition 08 (pcb:0x6F02) starting at sector 0x0006E000 MBR at 0x0006D808 is not attached
Drive has 0x0004BFA0 blocks, 0x11 sectors/track, 0x0F tracks/cylinder and 0x0001 cylinders
Drive type/flags and name 0x00/0x01 RD54
Partition 43 (pcb:0x6EE2) starting at sector 0x000BA800 MBR at 0x000BA008 is volume C:
Label:"FILES " Volume Size: 14'759'936 Sectors
]
logging
Various logging types are defined. With the logging command you can display the current settings
]logging
Logging device register access .: off
Logging Interrupts .............: on
Logging LBN/PBN ................: on
Logging Trace ..................: on
Logging poll DMA Addresses ....: on
Logging unit 0 .................: on
Logging unit 1 .................: on
Logging unit 2 .................: off
Logging unit 3 .................: off
]
You can individually switch certain logging off or on using the logging
and no logging command with one of the parameters
- device
- interrupts
- pbn
- trace
- poll
- unit
For example
]log reg
]logg
Logging device register access .: on
Logging Interrupts .............: on
Logging LBN/PBN ................: on
Logging Trace ..................: on
Logging poll DMA Addresses ....: on
Logging unit 0 .................: on
Logging unit 1 .................: on
Logging unit 2 .................: off
Logging unit 3 .................: off
]no log reg
]logg
Logging device register access .: off
Logging Interrupts .............: on
Logging LBN/PBN ................: on
Logging Trace ..................: on
Logging poll DMA Addresses ....: on
Logging unit 0 .................: on
Logging unit 1 .................: on
Logging unit 2 .................: off
Logging unit 3 .................: off
]
load
You can load bootstrap loaders to the PDP-11 memory. For MSCP emulation you can load the duboot bootstrap ROM image
]load 0100000 duboot
Writing 64 Words of DUBOOT to 00100000, use 100004g
]
Note that this is a 1-to-1 copy of the DU bootstrap ROM of Dan Norths collection of bootstrap ROMs found at M9312 PROM Files.
Therefore you need to use the load address +4 to start the code in ODT
@100004g
RT-11XM V05.07
.TYPE V5USER.TXT
RT-11 V5.7
Installation of RT-11 Version 5.7 is complete and you are now running
RT-11 from your system volume.
Your system volume is your working volume if you have used the Automatic
Installation (AI) procedure. If you have installed RT-11 using that
procedure, Mentec recommends you verify the correct operation of your
system's software using the VERIFY verification procedure. You can only
perform VERIFY on the valid target (output) media you used for the AI
procedure. Run VERIFY before you run CONFIG. To run VERIFY, enter the
command:
IND VERIFY
Mentec recommends you read the file V5NOTE.TXT, which you can TYPE or
PRINT. Also, read the Introduction to RT-11, rewritten for V5.7, which
contains much of the information you need to use RT-11 Version 5.7.
.R MSCPCK
.
help
Displays some information about commands. Not very extensive for the moment.
DMA Test Commands
These commands are for debugging purpose only. Don’t use them if a PDP-11 operating system is running.
dmaaddr
Sets the DMA address for subsequent DMA write or read test commands. Note that the DMA address must be set before switching from read to write or vice versa, else the read or write will fail
dmawrite
Write to the PDP-11 memory using DMA. Subsequent writes will use the DMA address autoincrement feature of the CPLD and will write to the next memory locations
]dmaaddress 0100000
]dmawrite 0
DMA - Set Address 00100000
DMA - write Data 000000
]
]dmawrite 0377
DMA - write Data 000377
]
]dmawrite 0177400
DMA - write Data 177400
]dmawrite 0177777
DMA - write Data 177777
]
dmaread
Reads back from PDP-11 memory using DMA. Note you need to set the address when you have written data via DMA previously as in our example
]dmaad 0100000
]dmar
DMA - Set Address 00100000
DMA - Read Data 000000
]
]dmar
DMA - Read Data 000377
]
]dmar
DMA - Read Data 177400
]
]dmar
DMA - Read Data 177777
]
dmadata
Writes to the DMA data register and reads back the DMA data register. This does not perform a DMA on the PDP-11 memory but is rather used to check the CPLD interface and of course should read back the same value as written.
]dmadata 0x00ff
DMA Register read back 0x00FF
]
dmatest
Caution this command overwrites the internal AVR memory if not used correctly. The MSCP Emulator has set aside the memory from 0x5000 to 0x5FFF for testing and debugging purposes often used in conjunction with the set of built in Apple II Monitor commands. It is safe to write to this memory range, however it most likely has catastrophic results if you write to any other address in the AVR memory.
This command will write 512. bytes from the AVR memory address given with
the command to the PDP-11 memory address previously set with the dmaaddress
command. It will then read back the PDP-11 memory and place it to the
next 512. bytes in AVR memory.
First you can prepare the AVR memory with some data, here I use the pattern command
]$5000.51ffp
]$5000.51ff
5000 - 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
5010 - 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
5020 - 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
5030 - 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
5040 - 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F
5050 - 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F
5060 - 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F
5070 - 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F
5080 - 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F
5090 - 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F
50A0 - A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF
50B0 - B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF
50C0 - C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF
50D0 - D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF
50E0 - E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF
50F0 - F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF
5100 - 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
5110 - 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
5120 - 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
5130 - 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
5140 - 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F
5150 - 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F
5160 - 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F
5170 - 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F
5180 - 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F
5190 - 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F
51A0 - A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF
51B0 - B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF
51C0 - C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF
51D0 - D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF
51E0 - E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF
51F0 - F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF
]
Next you set the DMA address
]dmaaddress 0100000
]
And then I execute the test command with address 0x5000
]dmatest 0x5000
DMA - Set Address 00100000
]
Now the AVR memory from 0x5200 to 0x53FF should have the same content as the memory from 0x5000 to 0x51ff which was set with the pattern command
]$5200.53ff
5200 - 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
5210 - 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
5220 - 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
5230 - 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
5240 - 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F
5250 - 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F
5260 - 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F
5270 - 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F
5280 - 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F
5290 - 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F
52A0 - A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF
52B0 - B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF
52C0 - C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF
52D0 - D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF
52E0 - E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF
52F0 - F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF
5300 - 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
5310 - 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
5320 - 20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F
5330 - 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F
5340 - 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F
5350 - 50 51 52 53 54 55 56 57 58 59 5A 5B 5C 5D 5E 5F
5360 - 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F
5370 - 70 71 72 73 74 75 76 77 78 79 7A 7B 7C 7D 7E 7F
5380 - 80 81 82 83 84 85 86 87 88 89 8A 8B 8C 8D 8E 8F
5390 - 90 91 92 93 94 95 96 97 98 99 9A 9B 9C 9D 9E 9F
53A0 - A0 A1 A2 A3 A4 A5 A6 A7 A8 A9 AA AB AC AD AE AF
53B0 - B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 BA BB BC BD BE BF
53C0 - C0 C1 C2 C3 C4 C5 C6 C7 C8 C9 CA CB CC CD CE CF
53D0 - D0 D1 D2 D3 D4 D5 D6 D7 D8 D9 DA DB DC DD DE DF
53E0 - E0 E1 E2 E3 E4 E5 E6 E7 E8 E9 EA EB EC ED EE EF
53F0 - F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 FA FB FC FD FE FF
]
This could also be checked using the Apple II Monitor command verify
]$5000<5200.53ffv
]
If there is no output then the two memory ranges 0x5000 to 0x51ff and 0x5200 to x053ff have the identical content
You can also check on the PDP-11 side
@100000/000400
00100002/001402
00100004/002404
00100006/003406
00100010/004410
00100012/005412
00100014/006414
00100016/007416
00100020/010420
00100022/011422
@