Steve Toner
Experienced Member
Continuing the saga...
Haven't reprogrammed the ATMEGA. But if I create a couple of RL02 partitions on the 2GB card and copy ZERORL.DSK to them, it does activate those partitions and shows them as DL0 and DL1. Copying a different disk image file, xxdp25.rl02, to one of the partitions causes automount to fail. This image file is a full 20480 records in length (=512 tracks * 40 sectors/track), while the ZERORL file is only 20450 records, but it appears to be overwriting the start of the next partition. Truncating the xxdp image to 20450 sectors before copying it results in automount working once again. But it won't boot. This does not appear to be related to the truncation, but a DMA failure. BOOT DL1 (the XXDP drive) reports an E.10 controller error.
The RLV12 registers contain:
17774400/120615 (CSR)
17774402/000000 (Bus address)
17774404/000000 (Disk address)
17774406/000000
17774410/000000
17774412/000000
17774414/000000
17774416/000000
Decoding the CSR, the following bits are set: ERR, E3, DS0, CRDY, F2, F1, DRDY
Controller and drive ready, operation=READ DATA, selected drive=1
Bus address and Disk address=0, as you expect from a boot
Indicated error = Non-Existent Memory
So at this point there are 3 possible failure points:
1. The RLV12 emulator (either the ATMEGA code or one of the CPLDs)
2. The KDJ11-D/S CPU module (Qbus interface)
3. The backplane
More investigation required...
Haven't reprogrammed the ATMEGA. But if I create a couple of RL02 partitions on the 2GB card and copy ZERORL.DSK to them, it does activate those partitions and shows them as DL0 and DL1. Copying a different disk image file, xxdp25.rl02, to one of the partitions causes automount to fail. This image file is a full 20480 records in length (=512 tracks * 40 sectors/track), while the ZERORL file is only 20450 records, but it appears to be overwriting the start of the next partition. Truncating the xxdp image to 20450 sectors before copying it results in automount working once again. But it won't boot. This does not appear to be related to the truncation, but a DMA failure. BOOT DL1 (the XXDP drive) reports an E.10 controller error.
The RLV12 registers contain:
17774400/120615 (CSR)
17774402/000000 (Bus address)
17774404/000000 (Disk address)
17774406/000000
17774410/000000
17774412/000000
17774414/000000
17774416/000000
Decoding the CSR, the following bits are set: ERR, E3, DS0, CRDY, F2, F1, DRDY
Controller and drive ready, operation=READ DATA, selected drive=1
Bus address and Disk address=0, as you expect from a boot
Indicated error = Non-Existent Memory
So at this point there are 3 possible failure points:
1. The RLV12 emulator (either the ATMEGA code or one of the CPLDs)
2. The KDJ11-D/S CPU module (Qbus interface)
3. The backplane
More investigation required...