Kowalski Simulator Macro Anomalies

[Klaus2m5]

You can run any intel hex object code on the simulator! Just assemble with your favourite assembler (with the macros you want) and load the object code into the simulator.

[BigDumbDinosaur]

Klaus2m5 wrote:

You can run any intel hex object code on the simulator! Just assemble with your favourite assembler (with the macros you want) and load the object code into the simulator.

Also, Motorola S-record or raw binary. I use S-record to transfer object code from the Kowalski assembler to my POC units for testing. I use the raw binary output for burning EPROMs.

[BigDumbDinosaur]

8BIT wrote:

I've been searching through the forum for bugs/feature requests/etc with the Kowalski Simulator and found this. Can you describe the purpose and use of the .PARAMTYPE feature?

I will post a consolidated list of bugs and feature requests once its completed.

I almost forgot about one "bug" (whether or not it is a real bug is probably more a matter of opinion than anything else) but was reminded of it by a post by Klaus on loading code into the simulator.

The Kowalski assembler's Motorola S-record output only generates S1 and S9 records. While those two record types are sufficient to transfer object code to another system, some applications may require S0 and S5 records. For example, the software for the well-known TOPS programmers will accept an S-record file, but not the Kowalski version, as it lacks the S0 and S5 records.

Dunno how much a task it would be to add those two records.

motorola_s_record.pdf

Motorola S-Record Format

(28.82 KiB) Downloaded 188 times

[Druzyek]

Klaus2m5 wrote:

You can run any intel hex object code on the simulator!

Right. That works pretty well but you lose all your label and macro names. It's not the end of the world but it does make it a bit hard to follow. Maybe I'm spoiled from my old setup where I ran CA65 list files through a program that ran them on a real 6502 over USB