733 commits

Author	SHA1	Message	Date
Folkert van Heusden	640643cb65	fixes vor ADC/SBC & added byte-ode for ADC/SBC	2025-04-06 18:33:58 +02:00
Folkert van Heusden	97aafc5815	fix for emit_bit_instructions	2025-04-06 18:09:46 +02:00
Folkert van Heusden	4b60b47a60	BIC/BIS: also (R1) target	2025-04-06 17:53:24 +02:00
Folkert van Heusden	dd67a2a276	code clean-up	2025-04-06 17:40:51 +02:00
Folkert van Heusden	e8333f3468	JMP/JSR/RTS fix, BPT removed	2025-04-05 15:34:19 +02:00
Folkert van Heusden	4ef5404ee3	bits to ignore	2025-04-05 15:17:27 +02:00
Folkert van Heusden	ec07c5ca38	different PSW values for RTI/BPT/RTT tests	2025-04-05 12:03:19 +02:00
Folkert van Heusden	e61cbf4c6a	test generation fix & misc	2025-04-05 01:32:58 +02:00
Folkert van Heusden	204e6e435c	todo	2025-04-04 23:57:13 +02:00
Folkert van Heusden	bfff919fcc	a single operand instruction has a single operand	2025-04-04 23:51:34 +02:00
Folkert van Heusden	4b508f81ca	todo	2025-04-04 23:17:02 +02:00
Folkert van Heusden	bef06aef86	Using R1 as base register for ASHC is problematic	2025-04-04 23:10:16 +02:00
Folkert van Heusden	854e2e67ce	more tests	2025-04-04 20:45:45 +02:00
Folkert van Heusden	65b3baa73b	would emit more memory than set	2025-04-04 09:42:08 +02:00
Folkert van Heusden	9635fdda03	do not (re-)generate if file exists	2025-04-04 09:08:48 +02:00
Folkert van Heusden	ae0c503054	emit_add_sub also test the two carry values	2025-04-04 09:02:18 +02:00
Folkert van Heusden	524d540a2a	file per set	2025-04-04 08:33:56 +02:00
Folkert van Heusden	732c66eceb	sim_interval would make tests fail	2025-04-04 08:22:22 +02:00
Folkert van Heusden	818e74f3d3	more tests, faster	2025-04-04 08:11:05 +02:00
Folkert van Heusden	5c38023e5e	reduced test count for add/sub	2025-04-04 07:47:09 +02:00
Folkert van Heusden	53b600a39a	branch instructions tweaks	2025-04-04 01:02:24 +02:00
Folkert van Heusden	d8b99a1199	more test sets	2025-04-04 00:42:21 +02:00
Folkert van Heusden	2283367549	test sets	2025-04-04 00:20:11 +02:00
Folkert van Heusden	ed4e54939b	use static rand() seed for reproducability	2025-04-03 23:38:43 +02:00
Folkert van Heusden	c8348bc8fe	make sure to reset everything	2025-04-03 23:37:47 +02:00
Folkert van Heusden	2796bf9e22	work arounds to prevent access to odd addresses or i/o	2025-04-03 23:20:00 +02:00
Folkert van Heusden	9999fd9ea1	skip HALT/WAIT/RESET	2025-04-03 20:46:09 +02:00
Folkert van Heusden	40f2ca866c	memory init fix	2025-04-03 09:28:51 +02:00
Folkert van Heusden	51b18a7956	skip invalid instructions	2025-04-03 09:24:13 +02:00
Folkert van Heusden	1fecfed1f2	after-memory	2025-04-03 09:16:48 +02:00
Folkert van Heusden	bc233e9a5a	include stack	2025-04-03 08:58:31 +02:00
Folkert van Heusden	3671049405	Generate testset using simh	2025-04-03 08:50:59 +02:00
Tony Lawrence	c093bcdcf6	PDP11: RP11: Implement original RP11 controller flavor ... Studying RSX11M source code I found out that the original RP11 controller (vs. -C and -E later versions) was still supported in the software, and notably UMD (User Mode Diagnostics) was still capable of handing it and dealing with its testing, even in much later OS versions (compared to when the original RP11 was phased out). The change in this commit basically implements that flavor (which only supported the RP02 drives), and also makes a few minor fixes / cleanups for the device code, here and there. The default mode for the RP11 controller remains the more widely used -C/-E version, but if so desired, it can be downgraded to support its predecessor with the "SET RR <type>" command now.	2024-09-04 13:39:47 -04:00
Tony Lawrence	c831460ecb	PDP11: Fix to fix disassembly #331 ... As discussed in PR#331, the fix needed more fix with the proper masks array. This patch completes the fix.	2024-07-23 14:25:19 -04:00
Tony Lawrence	100f351575	PDP11: RP11: Interrupt on IE+RESET+GO ... Recent analysis of the 2.9BSD kernel revealed that RP11 was expected to interrupt on control RESET function if IE bit was also set. Documentation was not very clear of the fact, saying in one place that RESET+GO does not interrupt (which is not contradictory with the above because it does not mention IE). In other place, however, it says that IE always causes interrupt when DONE is asserted. Thus, since RESET does assert DONE, an interrupt should be posted if IE is set. The autoconfig binary from 2.9BSD uses this feature of RP11 to check the presence of the controller. Formerly RESET was always clearing RPCS with DONE unconditionally, and that reset IE as well. This patch makes sure that the IE bit is preserved, and if set, it posts an interrupt when RESET asserts DONE.	2024-06-13 21:42:44 -04:00
Tony Lawrence	6a1b5685fd	PDP11: RP11: Make sure to advance DA after every I/O ... It looks like disk controllers, which automatically update disk address (DA) after completion of I/O, are expected to do so even if there was no data transfer because of I/O errors. I was studying RSX-11's Error Logger documentation and examples are clearly offsetting disk addresses backwards by one when I/O errors are reported by the controller. Since once the controller has found the DA-specified sector, the I/O begins regardless of the condition of the sector (bad or good data) or ability to transfer the contents between the disk and the memory. If an error occurs (NXM, for instance) the operation would stop (with the error reported) at the end of the sector. So if, for example, the bus address register had a bad address from the get-go, no data would be able to transfer at all, yet DA should still be updated with DA + 1 once the controller asserts the DONE bit. This patch makes sure that DA is always advanced when I/O has actually been commenced.	2024-02-01 12:56:04 -05:00
B. Scott Michel	d9d0e8bd74	CMake: Updates ... Issue #294: "apple silicon build problem(s?)": If the "--flavor/-f" flag is not specified on the command line, then complain loudly, print help and exit. The script used to default to "Unix Makefiles". Updates: - Add missing "-DHAVE_LIBPNG" compiler command line define when the PNG library is detected/present for screen capture support. - Add "clang64" to the list of MinGW64 platforms for which the .travis/deps.sh script can install build dependencies. - Add PThread4W_FOUND to the condition that sets async I/O for Win32 when using vcpkg for build dependencies. - Add vs2022-x64, vs2019-x64 and vs2017-x64 build environments to build 64-bit Windows executables. - Use simulator AIO only where needed by the simulator (i.e., the simulator calls/uses AIO_CHECK_EVENT in sim_instr()) - Add "USES_AIO" flag to add_simulator() to mark a simulator that acutally uses asynchronous I/O. - Build "_aio" SIMH core library variants that have AIO turned on, link with the "_aio" variant when a simulator sets USES_AIO. - Emit a warning message when WITH_ASYNC is False (CMake configuration option) to notify the user/developer that some functionality will be crippled. Affected simulator builds: 3b2 family, PDP-6, PDP-11, VAX family, IMLAC and TT2500. The makefile and cmake/generate.py also updated to remain in sync with CMake. N.B.: Simulators still link with the underlying platform's threading library. SEL32 requires pthreads or equivalent threading library, independent of AIO. - cmake/cmake-builder.sh - New "--no-aio" flag: Build simulators without async I/O. - New "--no-aio-intrinsics" flag: Don't build async I/O using compiler compare-exchange, atomic load intrinsics. - cmake/cmake-builder.ps1 - New "-noaio" flag: Build simulators without async I/O. - New "-noaiointrinsics" flag: Don't build async I/O using compiler compare-exchange, atomic load intrinsics. CMake 3.28.1 INTERFACE_LINK_LIBRARIES behavior change: The file name must now be an absolute path. Relative paths no longer accepted. Internally, SIMH enforces this if CMAKE_VERSION >= 3.19, when REAL_PATH was first implemented.	2024-02-01 12:51:13 -05:00
Paul Koning	c077c22d24	PDP11: fix disassembly of reg,src instructions ... This corrects the disassembly of MUL, DIV, ASH, and ASHC so it works correctly when the register is not R0.	2023-12-18 14:33:06 -05:00
Tony Lawrence	dd49f851a4	PDP11: RP11: Remove duplicate checks (now only done in svc routine)	2023-11-28 09:51:01 -05:00
Lars Brinkhoff	7797344bf9	PDP11, VAX, KS10: Speed up Chaosnet polling when there is traffic.	2023-11-28 09:49:35 -05:00
Lars Brinkhoff	1ed26cfb0e	KS10: Make Chaosnet work.	2023-11-28 09:49:35 -05:00
Tony Lawrence	47cf74ac4b	PDP11: TA11/TU60 fix identification	2023-11-28 09:48:36 -05:00
Christian Gauger-Cosgrove	2396fd0349	PDP-11, VAX: Expand DTYPE mask size, fix RF35, add new devices to RQ sim ... The disk type mask width (UNIT_W_DTYPE) was increased to six (6) bits, doubling the possible number of disk types definable to sixty-four (64). The RF35 was not entered in either the drv_tab or drv_types tables, causing any set command issued for the drive type defined after the RF35 -- the RF71 through RF73, as well as any disk defined after the RF73 -- to act incorrectly. The ESE20 solid state disk and ESE50 series of solid state disks are added based on simple drive geometry and size information without any parameters for bad block management (not that it is used in the simulation anyways). The ESE50 series drives are labelled as they are in the MSCP specification document, the Ultrix-32 v4.5 disktab, and the Media Type noted in the "ESE50 SDI Solid State Disk User Guide" (EK-ESE50-UG.B01): * ESE50-A: ESE52 * ESE50-B: ESE56 * ESE50-D: ESE58 The RD33 is added based on the geometry of the Microscience HH-1090 hard disk drive, with the bad block management information calculated from the bad block information for the other RDxx series drives. The RX18 is added based on the geometry of the RX180 floppies in the VT-180 "Robin" CP/M system, which are noted in the MSCP specification document as a possible device. Specific information is taken from the "VT-180 Series Technical Manual" (EK-VT18X-TM-001).	2023-11-21 16:26:52 -05:00
Tony Lawrence	eeebbed273	PDP11: RP11: Implement delayed CS_DONE for "initiation" commands (SEEK/HOME) ... Running earlier XXDP tests revealed that a technique of concurrent command initiation and continued housekeeping for the command completion was used in the old code. For example, code could initiate a SEEK command for a drive, and knowing that CS_DONE (and thus, an interrupt) is coming in about 16us, it would then go ahead and clear a flag, which registers that the interrupt has occurred (expected to be set to 1 by the ISR). If CS_DONE is set by the implementation at the function initiation immediately, that would mean that the interrupt could be triggered before the next instruction, and the flag would be set by the ISR right away. The main code, however, would proceed with the the flag clear as the following instruction, thus, never detecting the interrupt down the road. Since this technique was in existence, it is better to introduce a delay for setting CS_DONE in the "fast" initiation commands like SEEK and HOME, to accommodate the software that was relying on it. So far, however, no issues were encountered in testing (except one), where this delay mattered, but it's hard to tell if it would not be needed at all. All I/O commands always delay CS_DONE already because they were never supposed to be immediate. Since the time for CS_DONE in initiation commands was documented at 16us, the introduced delay is set to 10 instructions, which usually took more than that to execute. But the interrupt flag clear case would be covered, as well as the counted waits, which used some 25+-iteration tight loops for "drive ready", before flagging a time-out (so the delay cannot be longer, either). It also looks like more modern code never used any such tricks, so for it, it should not matter if CS_DONE was slightly delayed or not.	2023-10-24 12:45:59 -04:00
Tony Lawrence	f75592c5b8	PDP11: 11/70 read-only registers must not return NXM on write ... 17 777 740 - 17 777 742, read-only error address registers, and 17 777 764, a read-only System ID register, and are not handled in the CPU70_wr() routine, which means for these addresses the routine returns NXM, which then translates to "bus timeout" (no response to address), and then, as a result, trap to vector 4. That is incorrect, IMO. These locations are read-only yet the address gets decoded, and even though writing does not have any effect, the write routine for these addresses should return SCPE_OK.	2023-10-10 19:52:41 -04:00
Tony Lawrence	090ed215de	PDP11: RP11: Major update after XXDP ... Having run the device code thru XXDP and some other OS's and scenarios rigorously, a bunch of discrepancies were found, which need to be addressed by this rather extensive patch. 1. Each unit must implement its own "drive status" register, to be able to track per-drive errors / conditions correctly; 2. Fixed INT_SET() / INT_CLR() in RPCS write function (wrong order of the "if" conditions); 3. Some behavior was implemented not exactly how it was expected from the real hardware, such as: a. Post-I/O register values in RPDA and RPCA (including the corner case of pack overflow); b. I/O stacking, which wasn't mentioned in any available documentation, but only XXDP listings; c. RESET/IDLE function must be accepted for a "busy" controller; d. HOME function must always execute, even when "device ready" is not set (e.g. when SEEK error detected); e. SEEK incomplete should not respond with "device ready" (however, the condition can be cleared by HOME, d.); f. WLOA-induced write-lock violation wasn't reflected in "device status". 4. Some timing was off so that the device worked "too fast" -- this was fixed (except for the pathological cases when the races are in the actual test code, and cannot be logically fixed); 5. WLOA setup command bug was fixed; 6. Added more code comments found per the above peculiarities.	2023-10-10 14:10:50 -04:00
Tony Lawrence	5fba1e75e7	PDP11: TS11: Fix help output for BOOT command	2023-10-10 13:02:02 -04:00
Tony Lawrence	dc69862bc8	PDP11: RF11: Fix DAE computation in service routine	2023-10-09 20:16:01 -04:00
Tony Lawrence	5407544728	PDP11: RP11-C (RP02/03) disk implementation	2023-09-23 23:42:26 -04:00
Tony Lawrence	a8c5f7c88b	PDP11: RP11-C (RP02/03) disk implementation	2023-09-22 19:41:33 -04:00