Full CP/M IDE?

[Robb Bates]

Is there a good free CP/M IDE that had an editor, assembler, emulator that can step through and over instructions, deal with BDOS calls and show a CP/M environment with a terminal?

I've been playing with ASM80.com which is decent, but I can't figure out how to add my .com file into the CP/M drive it emulates.

Can someone either tell me how to do that or suggest a Windows APP that will do the same thing?

Robb

[Ed Silky]

I'm not saying that there isn't one, but I certainly never used an 'IDE' in the CP/M days. I don't think I encountered an 'IDE' until Visual Studio in the late '80s and then Eclipse in the '90s. Neither of which was for a Z80 or CP/M.

-Ed

--
You received this message because you are subscribed to the Google Groups "RC2014-Z80" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rc2014-z80+...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/rc2014-z80/bbe2884b-e5b9-493c-b4b5-ee0057af293bn%40googlegroups.com.

[Peter Onion]

Just to be clear, are you looking for something to run native on CP/M on a real Z80, or something to run  CP/M on an emulated Z80 on a modern PC ?

PeterO

[Richard Deane]

This paragraph confuses me: I've been playing with ASM80.com which is decent, but I can't figure out how to add my .com file into the CP/M drive it emulates.

Could you clarify this for me?

Try Z80pack on a pc, with the config tweak before build to activate Mostek ICE debugger.

However that won't resolve by itself your understanding of cp/m and com files. When you use asm80 or similar to create an object file , you then link the object to create hex or com files. If hex then hexload or hexcom will create the com files. Some assemblers eg z80asm can create the com directly on the disk.

To view this discussion, visit https://groups.google.com/d/msgid/rc2014-z80/261832b7-873b-44ec-ad02-306c77f65ef9n%40googlegroups.com.

[Peter Onion]

Seems the "bit rot" has set in on this old software :-(

petero@pi-nvme:~/RC2014/Z80pack/z80pack-1.10/cpmsim/srcsim $ make

test -f ../auxin || mknod ../auxin p
test -f ../auxout || mknod ../auxout p
lnsrc
make: lnsrc: No such file or directory
make: *** [Makefile:31: sim0.c] Error 127

Seems that the author may have had "." in their $PATH !   You need to add "./" infrornt of  lnsrc and ulnsrc in the Makefile.

   

PeterO

[Peter Onion]

OPSE, accidentally downloaded z80pack-1.10 rather than z80pack-1.17 .   However....  version 17 has it's onw problems ;-)

gcc sim0.o sim1.o sim2.o sim3.o sim4.o sim5.o sim6.o sim7.o simctl.o simint.o iosim.o simfun.o simglb.o unix_terminal.o -s -o ../cpmsim
/usr/bin/ld: unix_terminal.o:(.bss+0x48): multiple definition of `new_term'; simctl.o:(.bss+0x0): first defined here
/usr/bin/ld: unix_terminal.o:(.bss+0x8): multiple definition of `old_term'; simctl.o:(.bss+0x40): first defined here
collect2: error: ld returned 1 exit status
make: *** [Makefile:43: ../cpmsim] Error 1
 

This is caused by current versions of gcc defaulting to -fno-common , so you need to add "-f-common"  to the CFLAGS in the makefile 

PeterO

[Peter Onion]

Success !

#######  #####    ###            #####    ###   #     #

     #  #     #  #   #          #     #    #    ##   ##
    #   #     # #     #         #          #    # # # #
   #     #####  #     #  #####   #####     #    #  #  #
  #     #     # #     #               #    #    #     #
 #      #     #  #   #          #     #    #    #     #
#######  #####    ###            #####    ###   #     #

Release 1.17, Copyright (C) 1987-2008 by Udo Munk

CPU speed is unlimited

Booting...

64K CP/M Vers. 2.2 (Z80 CBIOS V1.2 for Z80SIM, Copyright 1988-2007 by Udo Munk)

A>dir
A: DUMP     COM : SDIR     COM : SUBMIT   COM : ED       COM
A: STAT     COM : BYE      COM : RMAC     COM : CREF80   COM
A: DDTZ     COM : L80      COM : M80      COM : SID      COM
A: WM       COM : WM       HLP : ZSID     COM : MAC      COM
A: TRACE    UTL : HIST     UTL : RESET    COM : LIB80    COM
A: M        SUB : ZAP      COM : DDT      COM : Z80ASM   COM
A: CLS      COM : MOVCPM   COM : ASM      COM : LOAD     COM
A: XSUB     COM : PIP      COM : SYSGEN   COM
A>bye

HALT Op-Code reached at 0101

[Richard Deane]

Use Z80pack from github udo munk. You probably have an old version.

To view this discussion, visit https://groups.google.com/d/msgid/rc2014-z80/b6453160-3bbb-48aa-a89a-812934abaa57n%40googlegroups.com.

[Peter Onion]

On Fri, 2025-10-31 at 12:10 +0000, Richard Deane wrote:
> Use Z80pack from github udo munk. You probably have an old version.
>

That'll teach me not to trust google results !

PeterO

[Robb Bates]

Richard,

My ASM80.COM, I meant the website, not a program if that what you're asking.

It's a pretty neat setup.  I wish I had something pretty equivalent to that in a windows program.  The interface on the website is a bit clunky.

Robb

[Dirk Prins]

Maybe this can be of use to step through your assembler code:

https://github.com/ForNextSoftwareDevelopment/Z80_RC2014

I wrote this to debug my programs for the Z80.

Now using the MPF-1 version more for this.

Best regards,

Dirk.

[Michelle Lawson]

Just my $0.02 worth.... I have used zDev Studio ( https://sourceforge.net/projects/zdevstudio/ ) for all of my Z-80 coding. Granted it only does the writing and assembling of the code, but it has worked flawlessly for me. I run it on my Windoz10 system, then upload it to my target system and run whatever I wrote.

[Robb Bates]

Plenty of options out there!  Thanks for all the recommendations.  I'll check them out.  The asm80.com website works, but it's far from ideal.

For what it's worth, I've figured out how to get your project on the b: disk using the asm80.com website.

In the assembler, name your source code file  PROJECT.COM even though it would seem  to make more sense to name it PROJECT.ASM or  PROJECT.Z80.

Then in the source code include these directives:

.cpu z80
.pragma com
.engine cpm

They have to be in lower case.

I've writing everything in Visual Studio Code and then copy pasting the source code.

Then when you're ready to test, just click COMPILE [F9].

It will create:

PROJECT.COM.com

PROJECT.COM.hex

PROJECT.COM.lst

Then click EMULATOR [F10]. It will launch a CP/M emulator with your PROJECT.COM  .com file in the B: drive.  Just change to the B: drive and run it.  I've named mine B.COM to make it quick and easy.  The edit, compile, execute, debug cycle is really super quick.  The built debugger is itself a bit buggy.  But it's worked for me.  And I'm learning how very useful the .LST file can be.

I'm just about done with the project I'm working on.  Expect to see it here soon.  This weekend if I can get it all wrapped up.

Robb