I’ve made a couple minor changes to the MINC pages over the last couple days – adding a few more details, crossing some Ts and dotting a couple I. And also, I added the complete sources including all the MINC stuff to the download page. Why now? well, because it now passes the original MNC11 chain of tests.
.C MNC11 R VMNF??/1 MD-11-CVMNF-C MINC-11 OPTION SIZER PROGRAM OPERATOR - PLEASE DO THE FOLLOWING: REMOVE THE CUSTOMER CONNECTIONS FROM EACH "MINC-11" OPTION MNCAD (A/D) SET FRONT PANEL SWITCHES TO THE "TEST" POSITION MNCAG (PREAMP) SET FRONT PANEL SWITCHES TO THE "P" POSITION MNCKW (CLOCK) PULL OUT "ST1" AND "ST2" SWITCHES AND ROTATE FULLY CLOCKWISE MNCDI (DIGITAL IN) SET "DATA" SWITCH TO THE "-" POSITION SLU 0 INSTALL "SLU TEST CONNECTOR" SLU 1 INSTALL "SLU TEST CONNECTOR" SLU 2 INSTALL "SLU TEST CONNECTOR" DEPRESS A KEY ON THE CONSOLE TERMINAL WHEN READY. ;MNCAD AT ADDRESS = 171000 VECTOR = 400 ;MNCKW AT ADDRESS = 171020 VECTOR = 440 ;MNCKW AT ADDRESS = 171024 VECTOR = 450 ;MNCAA AT ADDRESS = 171060 VECTOR = ** DOES NOT EXIST ** ;MNCDI AT ADDRESS = 171160 VECTOR = 130 ;MNCDO AT ADDRESS = 171260 VECTOR = 340 OF ;MNCAD 1 ;MNCKW 2 ;MNCAA 1 ;MNCDI 1 ;MNCDO 1 END PASS # 1 R VMNC??/1 CVMNC-B MNCKW (CLOCK) DIAGNOSTIC PROGRAM DETECTED 2 MNCKW (CLOCK)'S END PASS # 1 R VMNB??/1 CVMNB-B MNCDI (DIGITAL IN) DIAGNOSTIC PROGRAM DETECTED 1 MNCDI (DIGITAL IN)'S MNCDI (DIGITAL IN) UNIT # 0 EXPECTED INTERRUPT AT 120 RECEIVED INTERRUPT AT 130 PLEASE CHECK VECTOR SWITCHES RESTARTING LOGIC TEST END PASS # 1 R VMNE??/1 CVMNE-A MNCDO (DIGIAL OUT) DIAGNOSTIC PROGRAM DETECTED 1 MNCDO (DIGITAL OUT)'S � END PASS # 1 R VMND??/1 CVMND-A MNCAA (D/A) DIAGNOSTIC PROGRAM DETECTED 1 MNCAA (D/A)'S END PASS # 1 R VMNA??/1 CVMNA-C MNCAD (A/D) DIAGNOSTIC PROGRAM DETECTED 1 MNCAD (A/D)'S END PASS # 1 R VMNG??/1 CVMNG-A MINC-11 CHAIN TERMINATOR PROGRAM OPERATOR - THE AUTOMATIC RUNNING OF THE DIAGNOSTICS HAS NOW BEEN COMPLETED
Still not sure about the message from VMNB about the interrupt – and, I should probably add that at this moment in time, MINC support is something that requires a bit of effort and an open mind to research. Still, with the previous posts about building a disk image, and especially if you happen to have a DE0-Nano or DE10-Lite around somewhere…
Oh – shame on those DEC engineers. An apostrophe does not make plural.
And before I forget – there’s also a fix in this release for an issue with Quartus 20 – that causes it not to infer a buffer in the disk controllers, and thus to use a massive amount of logic instead of a single chunck of RAM. So definitely get this version if you want to build for yourself and you’re on the latest and greatest version.