Ah, thanks - I tried again, and I found that writing a *.65m file gives a correct srecord file, whereas writing a *.s9 file gives a binary memory dump. The latter is the default, at least for me - I had to type in a file extension to override it.


Thanks for the clarification - it seems that at least some programmers will happily accept a binary input file, which doesn't carry spurious load address information.

Cheers
Ed

I usually output the whole thing in binary, then edit out the chunk I want, load it into the programmer then burn it into the ROM. The offsets in Hex are never what I want in the ROM, so this process just makes it quick and easy.

Kinda like BDD suggests.

This way I can make some useful ROMS for some of the bank switched stuff I've made where I can have alternate code loaded into the ROM and select it via dip switch or program control.

_________________
Bill

Hi Bill
As a matter of interest, what tool do you use to edit the binary like that?
Cheers
Ed

I use this:

http://frhed.sourceforge.net/en/

_________________
Bill

Thanks!

[keywords for searching: Frhed / Free hex editor / "Frhed is a binary file editor for Windows"]

BTW, as I haven't had time to finish my UNIX-based 65C816 assembler, I wrote the entire POC BIOS ROM in the Kowalski simulator, using my '816 macros to synthesize the missing instructions. There are nearly 11,000 lines of source code for the ROM, which now includes a SCSI-1 compliant driver, with M/L monitor extensions that allow the disk to be used almost as RAM. I can also read a CD-ROM or a tape drive (tested on a DDS2 drive). The SCSI driver is PIO right now, so performance is not optimum, but I can fetch a disk block into RAM in about 10-12 milliseconds.

I only wish I had the time to dive into the source code for the simulator and make '816 instructions native to it. However, I have far more stuff to work on than time in which to do it (a new business opportunity presented itself today, which may keep me quite busy for the better part of a year), so digging into source code in an unfamiliar environment (Microsoft Visual something-or-other) that is commented entirely in Polish is out of the question.