Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

stop the leading blank fill of a Bank (with the Intel Hex output) #206

Closed
cjmonica opened this issue Jun 27, 2024 · 1 comment
Closed

stop the leading blank fill of a Bank (with the Intel Hex output) #206

cjmonica opened this issue Jun 27, 2024 · 1 comment

Comments

@cjmonica
Copy link

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.

Thanks for your great work on this tool!

@cjmonica
Copy link
Author

cjmonica commented Jul 1, 2024

Thanks Lorenzi that looks great so far! Thanks again for this awesome tool!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants