User:RHansen: Difference between revisions
mNo edit summary |
No edit summary |
||
Line 16: | Line 16: | ||
| | | | ||
|} | |} | ||
A long time | A long time ago, in another universe it seems, I was using SINTRAN on an ND-100 at our electronics/computer school. | ||
We configured and ran the machine after we inherited it. | We configured and ran the machine after we inherited it. | ||
Line 25: | Line 25: | ||
(I have to admit I have ''borrowed'' some of the complex opcodes from the existing nd100em emulator ) | (I have to admit I have ''borrowed'' some of the complex opcodes from the existing nd100em emulator ) | ||
The emulator contains a debugger, | The emulator contains a debugger, disassembler and code tracer in addition to logic to mount different floppy-image, read/write hardddrive, loading BPUN and PROG files directly into memory. | ||
I have successfully dumped and booted SINTRAN version H in ND-100 mode, although there are still some bugs to iron out. | I have successfully dumped and booted SINTRAN version H in ND-100 mode, although there are still some bugs to iron out. | ||
Line 61: | Line 61: | ||
== What's NOT working in the emulator == | == What's NOT working in the emulator == | ||
* SINTRAN K,L and M doesn't boot fully yet.. | * SINTRAN K,L and M doesn't boot fully yet.. There are some page-table mappings that fail with memory exception, and SINTRAN ends up looping. I am guessing the bug is related to memory access or interrupt handling, but so far, I haven't been able to track down the bug. Hopefully implementing the same logic in the ND-110 cpu emulator may | ||
* MON 131 ABSTR behaves "buggy" in SINTRAN H | * MON 131 ABSTR behaves "buggy" in SINTRAN H | ||
** Something odd happens with zero-pointers for some logical devices sending the CPU into a loop at P=0 | ** Something odd happens with zero-pointers for some logical devices sending the CPU into a loop at P=0 | ||
* Odd | * Odd behavior in CONFIGURATION on interrupt detection (see picture on the right) | ||
* Copying file from papertape driver to SINTRAN disk with "COPY 'FILE:BPUN' PT1' fails after 129 bytes. It just stops, and I have to cancel the copy with ESC key. | * Copying file from papertape driver to SINTRAN disk with "COPY 'FILE:BPUN' PT1' fails after 129 bytes. It just stops, and I have to cancel the copy with ESC key. | ||
Line 71: | Line 71: | ||
* Documentation on the ND-100 register ACTL (Active Level). It looks like it's 3 bits, and its not PIL. | * Documentation on the ND-100 register ACTL (Active Level). It looks like it's 3 bits, and its not PIL. | ||
* Images of SINTRAN J floppies. The source code that has been scanned is SINTRAN J, but since I now have access to source code for version L this is less important now. | * Images of SINTRAN J floppies. The source code that has been scanned is SINTRAN J, but since I now have access to source code for version L this is less important now. | ||
* Information on what REALLY happens in the | * Information on what REALLY happens in the Registes that are "locked" (Like IIC, PEA, PES) Documentation says its "locked" when there is an error, and "unlocked" during an TRA IIC <= Starting to get an understanding while implementing ND-110 CPU :-) | ||
* Other binary images (Tape, PaperTape, HDD, Floppy,+++) All SINTRAN III versions are of interrest. | * Other binary images (Tape, PaperTape, HDD, Floppy,+++) All SINTRAN III versions are of interrest. | ||
* ROM's with Microcode for ND-10, ND-100, ND-110 | * ROM's with Microcode for ND-10, ND-100, ND-110 | ||
Line 96: | Line 96: | ||
*** Everything is written in C#/.NET7 | *** Everything is written in C#/.NET7 | ||
*** MicroCode compiler works | *** MicroCode compiler works | ||
*** MicroCode retrieved from PDF document using OCR techniques mixed with some "text washing" gives me a file with 16600 lines of microcode I manually | *** MicroCode retrieved from PDF document using OCR techniques mixed with some "text washing" gives me a file with 16600 lines of microcode I manually have validate against the PDF. The whole file is manually compared and does compile without errors. However, I know there are bugs because of the OCR, like details that has not been identified is now missing in the file. I need to do a full re-read with focus on identifying missing microcode elements. | ||
*** MicroCode CPU somewhat working. Decoding of macro-instructions to micro-instructions and dekoding of the 64 bit microcode partially working. Still a lot to implement, but before I can implement every detail, I need to understand the ND-110 CPU HW better. | **** I wish I had a ROM export or the original microcode in a file. | ||
*** MicroCode CPU somewhat working. I have implemented registers, ALU (really 4x Am2901 chips) and interrupts (Am2914 chip) | |||
**** Decoding of macro-instructions to micro-instructions and dekoding of the 64 bit microcode partially working. Still a lot to implement, but before I can implement every detail, I need to understand the ND-110 CPU HW better. | |||
*** This CPU will definitively be slower than the ND-100 emulator, but hopefully behave 100% like the original. This way I can verify behavior differences between the ND-100 opcodes and the ND-110 opcodes. | *** This CPU will definitively be slower than the ND-100 emulator, but hopefully behave 100% like the original. This way I can verify behavior differences between the ND-100 opcodes and the ND-110 opcodes. | ||
Revision as of 15:33, 2 January 2023
Real name: | Ronny Hansen |
Role: | Developer, Architect, Geek |
Interrested in: | Everything between Embedded and Cloud |
A long time ago, in another universe it seems, I was using SINTRAN on an ND-100 at our electronics/computer school. We configured and ran the machine after we inherited it.
These days I am a Cloud Architect, Developer and Geek - and the last years I have been spending an unhealthy amount of time writing emulators. You can read how this crazy journey started here [1]
ND-100 Emulator
I have successfully (with some help) created an ND-100 emulator in .NET/C# with peripherals such as TeleType, Floppy and HardDrive. (I have to admit I have borrowed some of the complex opcodes from the existing nd100em emulator )
The emulator contains a debugger, disassembler and code tracer in addition to logic to mount different floppy-image, read/write hardddrive, loading BPUN and PROG files directly into memory.
I have successfully dumped and booted SINTRAN version H in ND-100 mode, although there are still some bugs to iron out.
I have tried booting SINTRAN K, L and M. Dumping to HDD works great, but I haven't successfully managed to boot SINTRAN from HD with 22! If using DISK-75MB-1, I am actually able to make SINTRAN start. However it fails after a while with a
What's working in the emulator
- SINTRAN H boots and runs (with a minor hardcode in the emulator to fix ABSTR bug (?))
- Test programs that validates the opcodes so far
- ONE—CHECK, TWO—CHECK, THREE—CHECK
- FOUR—CHECK (a few bugs still)
- INSTRUCTION-B.BPUN (PROGRAM NUMBER: 204384B DATE ISSUED : 83.11.01)
- PAGING-B.BPUN (PROGRAM NUMBER: 203098B 1982)
- FLOPPY-FU-1986F (All tests work except Test 2 "Format Decoder Test" on my PIO floppy driver)
- Test programs on floppy "210523E00-XX-01D"
- INSTRUCTION - Version: C00 - 1986-10-30
- "48 BITS FLOATING INSTRUCTIONS" - not working as I am only emulating 32 bits FPU
- PAGING - Version: C00 - 1986-10-16
- All tests report success in MMS-1 and MMS-2 mode.
- INSTRUCTION - Version: C00 - 1986-10-30
What's NOT working in the emulator
- SINTRAN K,L and M doesn't boot fully yet.. There are some page-table mappings that fail with memory exception, and SINTRAN ends up looping. I am guessing the bug is related to memory access or interrupt handling, but so far, I haven't been able to track down the bug. Hopefully implementing the same logic in the ND-110 cpu emulator may
- MON 131 ABSTR behaves "buggy" in SINTRAN H
- Something odd happens with zero-pointers for some logical devices sending the CPU into a loop at P=0
- Odd behavior in CONFIGURATION on interrupt detection (see picture on the right)
- Copying file from papertape driver to SINTRAN disk with "COPY 'FILE:BPUN' PT1' fails after 129 bytes. It just stops, and I have to cancel the copy with ESC key.
I am looking for the following
- Documentation on the ND-100 register ACTL (Active Level). It looks like it's 3 bits, and its not PIL.
- Images of SINTRAN J floppies. The source code that has been scanned is SINTRAN J, but since I now have access to source code for version L this is less important now.
- Information on what REALLY happens in the Registes that are "locked" (Like IIC, PEA, PES) Documentation says its "locked" when there is an error, and "unlocked" during an TRA IIC <= Starting to get an understanding while implementing ND-110 CPU :-)
- Other binary images (Tape, PaperTape, HDD, Floppy,+++) All SINTRAN III versions are of interrest.
- ROM's with Microcode for ND-10, ND-100, ND-110
- Documentation on device and IOX register usage for all peripherals, especially Ethernet
- Access to a REAL ND-100/ND-110 to run som test programs to compare with my emulator.
- Source Code. Any source code. Especially test programs and IO drivers.
- Documentation on Date/Time format/calculation for file/timestamps
- Hard Disk boot sector information - currently I must boot from via "boot floppies" and I would like to be able to boot directly from the HDD.
Things I am working on
- After getting the source code for SINTRAN L, I am now focusing on getting version L to boot to login prompt.
- Dumping to DISK-75MB-1 works great. Boot startes and runs 2.5 million instructions before it hangs.
- Currently stuck on a page-fault in a none-demand segment after SINTRAN starts the RT system. SINTRAN Segment Administration on Level 3 tries to give it a PageTable setting, but can't. It then restarts the process, and we have a never-ending loop.
- JMP 042314 = ESCER => Page Fault! PT=9 VPN=17 PTe=00000000 Accessmode=FETCH PGS=141121
- Getting the I/O devices to work flawlessly. Normal read/write works in my drivers, but test-programs are not working 100% as they are enabling "test mode" which I havent implemented (yet).
- I am focusing on getting the ND-10/ND-100 opcodes working 100%. (I do believe that the ones that are implemented are "almost" bugfree)
- Implementing the missing opcodes
- «Commercial Extended» (CE) option (BCD)
- CX opcodes (Stack, Segment,)
- ND-110 Specific opcodes
- Focusing on getting SINTRAN H work 100% flawlessly (could be opcodes, but at the moment all my trouble is inside MON 131 ABSTR)
- ND-110 MicroCode CPU
- Creating a new CPU emulator at the MicroCode level to teach me more about the internals of the opcodes, but also to (hopefully) help me identify "features" in my ND-100 Emulator
- Everything is written in C#/.NET7
- MicroCode compiler works
- MicroCode retrieved from PDF document using OCR techniques mixed with some "text washing" gives me a file with 16600 lines of microcode I manually have validate against the PDF. The whole file is manually compared and does compile without errors. However, I know there are bugs because of the OCR, like details that has not been identified is now missing in the file. I need to do a full re-read with focus on identifying missing microcode elements.
- I wish I had a ROM export or the original microcode in a file.
- MicroCode CPU somewhat working. I have implemented registers, ALU (really 4x Am2901 chips) and interrupts (Am2914 chip)
- Decoding of macro-instructions to micro-instructions and dekoding of the 64 bit microcode partially working. Still a lot to implement, but before I can implement every detail, I need to understand the ND-110 CPU HW better.
- This CPU will definitively be slower than the ND-100 emulator, but hopefully behave 100% like the original. This way I can verify behavior differences between the ND-100 opcodes and the ND-110 opcodes.
- Creating a new CPU emulator at the MicroCode level to teach me more about the internals of the opcodes, but also to (hopefully) help me identify "features" in my ND-100 Emulator
Open Source
- When I have a stable working version, I am planning to put the source code on GitHub under a BSD License. Then everyone can look at the code, modify it or just run it.
- I have been playing with the idea on porting my C# code to C - when its stable. And integrate it in the SIMH projects [2]. For this I may need help :)