Customasm seems to always prefill leading blanks (zero data) for Banks (with the Intel Hex output).
Ex Definition:
Customasm is defined as:
bankdef data
{
addr 0x8000
#size 0x8000
#outp 8 * 0x8000
}
bank data
d "cm"
The Intel Hex output is as below:
(many records of prefill zeros)
.
.
:207FC0000000000000000000000000000000000000000000000000000000000000000000A1
:207FE000000000000000000000000000000000000000000000000000000000000000000081
:02800000636DAE
:00000001FF
The Hex files should only have the last two records (all the proceeding records are blank fill), where the data begins at 0x8000.
:02800000636DAE
:00000001FF
My RAM begins at address 0x8000 and that is where the bank data/code should begin/get loaded. Programs loading an Intel Hex file do not need the prefill blank/zero data. There should be a way to suppress the blank prefill and just start the load at 0x8000 in this example.
Customasm seems to always prefill leading blanks (zero data) for Banks (with the Intel Hex output).
Ex Definition:
Customasm is defined as:
bankdef data
{
addr 0x8000
}
bank data
d "cm"
The Intel Hex output is as below: (many records of prefill zeros) . . :207FC0000000000000000000000000000000000000000000000000000000000000000000A1 :207FE000000000000000000000000000000000000000000000000000000000000000000081 :02800000636DAE :00000001FF
The Hex files should only have the last two records (all the proceeding records are blank fill), where the data begins at 0x8000.
:02800000636DAE :00000001FF
My RAM begins at address 0x8000 and that is where the bank data/code should begin/get loaded. Programs loading an Intel Hex file do not need the prefill blank/zero data. There should be a way to suppress the blank prefill and just start the load at 0x8000 in this example.
Thanks for your great work on this tool!