I've been looking at the "extra" module that is posted together with the PaulMon2 monitor. This has a disassember in it, though it has no line-by-line assembler.

What I'm after is something similar to the MSDOS Debug program, but designed to reside on the 805x family in native mode. I'm also looking at generating a simple pared-down version of the "Wordstar-like" editor used with the Turbo tools from Borland. This syntax is widely understood, and even used to some extent in the MSDOS editor. What I'm after is a totally un-tethered development tool at least capable of allowing a user to run the monitor and maintain the ability to enter mnemonic code manually and assemble it, and subsequently test it in-situ, making change as needed.

The majority of assembler sources I've examined so far have lots of resources used for symbol table and source-file manipulations. Those won't be necessary, since the environment will not have file I/O, per se'.

I expect to be putting code into the system either via the editor or the monitor, depending on whether there will be an editor. SInce I have to write it, and since I have to cope with the various capabilities of a serial terminal, probably an ansi-emulation on a PC, it will probably come in character by character, but be processed a line at a time.

You say, "Another issue is whether you will support the SFRs mnemonically. If you do the resulting disassembler (if implemented) would gain in sophistication."

That's where the PaulMon2 comes in, since it already has the ability to refer to some of the SFR's via its line-by-line disassembler. If I can figure out a good way to use that, then I'll put it together an put it out there.

Right now I still have to decide what, exactly I'm willing to do, in light of what I need. I'm still looking for a relatively easy way, however.

regards,

Dick