I have built a standard Cyclone II c version of Multicomp and having good fun with it (mostly using mc-2g-1024 build) and have identified one application which is incompatible but runs on other CP/M builds (e.g. RC2014 - tested on Z80 and Z280 flavours))
Debugz v1.2 from Microcode Consulting (https://www.microcodeconsulting.com/z80/debugz.htm) is regarded as one of the best debuggers under CP/M (Z80) and is the only program I have found so far that won't work properly on Multicomp. It would be good if someone could confirm that. I've tried it on CP/M 2.2 and CP/M 3, same error on both.
The symptoms I get are that the program loads and then runs in a loop displaying BP error (As shown below), but on other CP/M hardware systems (CP/M 2.2 and CP/M 3) it just loads and runs normally (j command will give full screen debugging)
DEBUGZ v1.2 (C) 1988,1989 MICROCode Consulting
Terminal: Digital VT-100
Free: 0100-C2D5
DebugZ: C2D6-E804
#
*Unknown BP at F738
--EFZ- A=02 B=0023 D=0006 H=F609 S=E5A5 P=F738 ADD A,B
#
*UNKNOWN BP AT F738
--EFZ- A=02 B=0023 D=0006 H=F609 S=E5A5 P=F738 ADD A,B
#
*UNKNOWN BP AT F738
--EFZ- A=02 B=0023 D=0006 H=F609 S=E5A5 P=F738 ADD A,B
#
*UNKNOWN BP AT F73A
--EFZ- A=02 B=0023 D=0006 H=F609 S=E5A5 P=F73A LD B,A
#
Note that debugz needs to be configured for the screen type with dbginst.com, after terminal type set by SETQTERM.COM, if one wishes to use full screen debugging. The above error was verified with virgin program from MICROCode, and after patching to different terminal type, so the error on Multicomp is unrelated to my patching.
I found that the dbginst program doesn't work for me so I had to use ddt to read debugz.com, then read qterm.dat (as previously configured through setqterm.com) at 0006 (which overlays it at 106), ctrl-c out of ddt, then SAVE 44 DEBUGZ.COM
Can anyone verify this problem with running debug on Multicomp CP/M?
Richard
Debugz v1.2 from Microcode Consulting (https://www.microcodeconsulting.com/z80/debugz.htm) is regarded as one of the best debuggers under CP/M (Z80) and is the only program I have found so far that won't work properly on Multicomp. It would be good if someone could confirm that. I've tried it on CP/M 2.2 and CP/M 3, same error on both.
The symptoms I get are that the program loads and then runs in a loop displaying BP error (As shown below), but on other CP/M hardware systems (CP/M 2.2 and CP/M 3) it just loads and runs normally (j command will give full screen debugging)
DEBUGZ v1.2 (C) 1988,1989 MICROCode Consulting
Terminal: Digital VT-100
Free: 0100-C2D5
DebugZ: C2D6-E804
#
*Unknown BP at F738
--EFZ- A=02 B=0023 D=0006 H=F609 S=E5A5 P=F738 ADD A,B
#
*UNKNOWN BP AT F738
--EFZ- A=02 B=0023 D=0006 H=F609 S=E5A5 P=F738 ADD A,B
#
*UNKNOWN BP AT F738
--EFZ- A=02 B=0023 D=0006 H=F609 S=E5A5 P=F738 ADD A,B
#
*UNKNOWN BP AT F73A
--EFZ- A=02 B=0023 D=0006 H=F609 S=E5A5 P=F73A LD B,A
#
Note that debugz needs to be configured for the screen type with dbginst.com, after terminal type set by SETQTERM.COM, if one wishes to use full screen debugging. The above error was verified with virgin program from MICROCode, and after patching to different terminal type, so the error on Multicomp is unrelated to my patching.
I found that the dbginst program doesn't work for me so I had to use ddt to read debugz.com, then read qterm.dat (as previously configured through setqterm.com) at 0006 (which overlays it at 106), ctrl-c out of ddt, then SAVE 44 DEBUGZ.COM
Can anyone verify this problem with running debug on Multicomp CP/M?
Richard