My goals is to basically have one copy of the assembler in RAM, and be able to run it - in parallel - multiple times.
Ah...that you want to stuff all of Supermon 816’s variables into direct page now makes sense. In effect, you are using the shared-text principle found in UNIX and Linux, starting ...

Hi BDD, thanks for explaining your rationale!

I was just observing, not judging. I know that software is developed with specific intentions in mind and when I come with some different ideas, it sometimes clashes...

My goals is to basically have one copy of the assembler in RAM, and be able to run ...

I have now (I htink) put all runtime variables into direct page.

Also, I have done some changes to improve handling on the Commodore full screen editor:
- you can edit memory dump in place, and it will continue such that you can just move through a full dump with <ret>
- you can edit disassembly in ...

Now the only ,y addressing modes that potentially conflict are auxbuf and ibuffer, IFF I want to move them to directpage.
I did do this for auxbuf, by introducing an "auxbufp" that is set on init and points to the auxbuf.
I'll probably do that with ibuffer too....

The problem with both of them is ...

There is another one on binasc:

3112 T:1950 a2 00 @0000040 ldx #0 ;operand index
3113 T:1952 a0 05 ldy #s_sfac-1 ;workspace index
3114 T:1954 ;
3115 T:1954 b5 19 @0000050 lda faca,x ;copy operand to...
3116 T:1956 99 21 00 sta facb,y ;workspace in...
3117 T:1959 88 dey ;big-endian order
3118 ...

Another find. In monreg you are reading the register values using addr,y addressing, which again conflicts with the direct page location of the list of shadow register.


;
;
; display .C, .X, .Y, SP & DP...
;
.0000030 jsr printspc ;spacing
rep #m_seta
lda reg_ax,y ;get register value
sep ...

Ah no worries. Thanks for standing in as my proverbial rubber duck

Ah yes, that was it. I had commented out the line where X is actually loaded with the length of the workspace *facepalm*

Now I think all commands work, I'll re-check, tag the version and then move over to more deeper changes (pulling the control loop out).

André

After a night of sleep I think the size calculation for the workspace must be wrong in my version. After all it should be only four byte for the MVN/MVP and RTS... will check later

I'm on the Same page with you - on retro feeling and on offloading work. I do have special controllers on my Commodore PET rebuild for USB, I2C. I only do IEC bit banginging because it's the compatible way... (as an extension to be able to use IEC floppies instead of IEEE488 floppy drives. And it ...

P.S. I found this as I was testing a simple "C 0340 0380 0390"... (or was it T - don't remember and not on the PC anymore). The result was it was copying stuff elsewhere, not where it should be ending up.
André

I am not sure if there is not an issue with the copy command when doing the reverse copy.

In this code in moncpy , you add the operand to a register to get the end address - but only after setting up the MVN/MVP "workspace" (if I interprete that right) - which on the other and overwrites the ...

If you only measure time for keyboard idle, how do you know if the 6502 is done finishing its job?
(Besides me wondering , without having read the whole thread, what you then need the 6502 for anyway in this system?)
André

I wonder if 65816 assemblers should issue a warning whenever they encounter a single byte = directpage address that they can only use with an absolut addressing mode opcode... dp and normal addresses should probably be incompatible...

Hm, another interesting catch: in the disassembly code, after dpycod02 the operand is being read using lda operand,y , while it is written before using sta operand,x .

This is unfortunate as the 65816 only as the ",X" versions using the direct page, but not ",Y" - so the store is happening into ...