I discovered that wanting to code a absolute long address mode with a variable that was word-sized resulted in the instruction getting coded as absolute. it seems that the backslash is the only special character not used, so I tried it as an experiment.



Its not really elegant but its functional. It works with BYTE sizes values as well and even works when numbers are used in the operands. I get a "value exceeds 16 bits" error once in while but its pointing to the *= line. Pressing Assemble again and the error goes away. I need to trace the source of that issue down. Still more work before its ready for release.

Daryl

_________________
Please visit my website -> https://sbc.rictor.org/

I have updated this a little to increase flexibility. I've added a numeric after the \ to indicate the number of bytes to use. This allows for specific modes when needed, such as forcing Absolute long in bank zero, or using absolute vs. direct page addressing for addresses < 256.

The format looks like this:
\1 byte sized - takes least significant byte of the operand
\2 word sized - takes least significant 2 bytes of the operand
\3 long sized - takes full 24 bit value of the operand



My next task is to expand the memory coverage to the full 16MB space, and address any issue that get found along the way.

Daryl

_________________
Please visit my website -> https://sbc.rictor.org/

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

As soon as I get done testing it, I'll post it.

Daryl

_________________
Please visit my website -> https://sbc.rictor.org/

*** EDIT *** I have updated the zip file with the corrected program. The Missing ORG error is fixed.

Here is the latest version - 1.3.2

It includes the \x overrides I mentioned previously, a few fixes, some added features, and updated help.

Features added:



I also added all of the 65816 opcodes to the help file along with the new 65816 mode chart. There is a new page on overriding the operand sizes as well, which covers immediate '!#' and '\1', '\2', and '\3'.

The assembler makes an assumption that any undeclared variable will be 16 bits by default. If it later is found to fix in 8 bits or 24 bits, it will adjust the output accordingly. However, if an address label value changes between the first and second pass, a "Phase Error" will be generated. This is not new, but may be encountered more often with the increased possibility of operand size changes. This can be hard to troubleshoot as the error will tell you where the label is, but not where the variable size change happened. It would require a major rewrite to allow better error reporting. I am investigating other options.

Please give this a try - try to use the new features, and let me know if you find any issues.

thanks!

Daryl

_________________
Please visit my website -> https://sbc.rictor.org/

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

Let me start by saying its awesome to see the Michal Kowalski Simulator continue to be developed.
In fact i personally found it pretty hard to a *latest copy, that i created a latest github repository just to store a copy of it.

I "wrote" a monitor with code borrowed/inspired from San Bergmans (with permission) two pass assembler, KRUSADER (MOS) disassembler, code tracer, and usual commands (is for a 65c02 only that i built in 1992 - this CONVID-19 stuff hashed out some old projects and wanted it to be "polished" as i can afford the extra space in the ROM. I've also added LCD 16x2 code..

Anyway when i run it on version 1.3.2 i get "ERROR E032: Missing .ORG directive-..." yet when i run it in 1.2.15 i have no issues. Full source is here:

https://github.com/jdimeglio/6502-Monitor

_________________
_________________________________________________________________________
Checkout my 2pass assembler/monitor https://github.com/jdimeglio/6502-Monitor

Hello and thank you for posting. I created a bug while trying to expand the memory beyond 64k. The last line of your code is causing the error because after the .WORD directive writes the Interrupt vector, it advances the internal program counter to $10000. I am working to reverse the bug I created.

If you comment out that last statement, it will assemble without error.

I'll post the revised v1.3.2 sometime today.

thanks!

Daryl

_________________
Please visit my website -> https://sbc.rictor.org/

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

(we all have preferences... I like to see projects hosted somewhere convenient, and I find github convenient. Let's not suppose any one person's preferences are ideal. That said, I think there is consensus on images: best to attach them to a post. Too many times externally hosted images have vanished.)

Well, emphasis on some other forum members. While I feel an equal amount of annoyance to BDD in this case, it's aimed in the opposite direction: I find GitHub a lot more convenient than downloading a file and viewing it, and especially more convenient than dowloading multiple files or dealing with unarchivers. Clicking a link or two and having the code pop up immediately in that same web browser window is (for me, anyway) invariably much faster. When I do want a set of files locally, a simple `git pull` is much faster and easier for me than dealing with manual downloads and unarchivers and the like.

Probably the best solution (and the one I use) is to give a link to the repo, but also attach here any specific files that are particularly relevant, even if they don't include the build and test system that some of us would consider de rigueur for any close examination of code.

This has been discussed (or "discussed" :-)) before; I wonder if it's worth spending the effort to build a little document describing the opinions and options so that one could just link to it.

_________________
Curt J. Sampson - github.com/0cjs

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

In case anyone misses my edited post above, here is the fixed version 1.3.2.

Daryl

_________________
Please visit my website -> https://sbc.rictor.org/

Sorry still got bugs.

So when i run up my polished monitor it assembles (f7), it debugs (f6) and Run is highlighted (f5). Hitting Run does nothing other then grey out all the options.
I've tried to step in rather than run, even place a breakpoint on RESET.

Is this worth fixing? Are there any more 65C02 die-hards out there? or am i just better off using an older version..

PS:@BigDumbDinosaur i added .OPT proc65C02,swapbin (and removed it and all the @<->% in troubleshooting this issue)

_________________
_________________________________________________________________________
Checkout my 2pass assembler/monitor https://github.com/jdimeglio/6502-Monitor

Everything appears to be copacetic with it. It successfully assembled the POC V1.2 firmware.

Good job!

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!