I tried to moddify EhBasic by adding my own routines and some variables (including few located in zero page). But something strange happens, when I try to "burn" an EPRM. MiniProg informas me, that bin or hes file is outside programmed memory space. My program bagins at 0xC000 and ends at 0xFFFF (vectors). How to generate proper hex (or bin) file, containing only this fragment of memory space?

Working with such limited information it can be hard to give you an answer. Attaching the file you generated would be very helpful, as would describing in detail the changes you made and how you generated the file.

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

How big is the HEX/binary file and what size is your EPROM? You may have produced an output file that represents the entire 64K of memory space.

Likely you will have to edit the HEX/Binary file to remove leading 0s so it fits into your EPROM from the top down. Or re-define how to build the output file in your assembler.

Another vote for posting the file here so we can have a look, and letting us know what you used to create it.

_________________
Bill

As the most basic point, remember that there's a difference between the address range you design your code to appear in to the CPU, and the offset within the ROM that you need to burn it.

The assembler may be producing files (IHEX or SREC) which indicate the correct addresses, but your burning program doesn't know how to map those to offsets. Or you may be producing a raw hex or binary file without addresses, in which case all bets are off.

Ok, I already found the cause. I had been using ORG statement to define variables, so assembler put them into bin file, with a lot of 0x00s between data and program. Then I've noticed that original EhBasic code uses EQ labels to define addresses of variables. Now generated hexes contain only a code, without variables.

You don't mention what assembler you were using or what pseudo-ops you were using to reserve space in the `ORG` sections, but with some assemblers, so long as you use reservation pseudo-ops such as DS rather than definition pseudo-ops such as DB, output will not be generated. Others may generate output (typically zeros) for that area, though they ought not.

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