08-09-2022, 12:12 PM
(08-09-2022, 06:26 AM)boriel Wrote: Sorry for the delay (I've been out for a while).Yep, with a bit of trial and error, but thank you.
Glad you found it!!
Cheers!
I was wondering if you could give me some tips regarding memory allocation.
I'm using some music written using beepola, which must be hardcoded because of how the software compiles (I'm still not it the level where I can disassemble and modify that code). I'm planning on saving the player and music data above 62000-63000, up to ramtop (I assume I can write up to 65535, as I think ZX Basic will locate my udg sets somewhere else - I include them with incbin and let the compiler decide their location, am I correct?)
I'm trying to figure how heap space works and where the assembly locates it. Is there a way to figure how much heap space my code will actually require? Is it allocated at the end of the code, or somewhere else? If I hardcode the music at 63000, for instance, will the heap space be reserved after that, or between the compiled code and that address?
Also, the compiler saves the code starting at 32768 unless otherwise specified. Is there a reason for that address? I assume I can start somewhere after 23755 with --org, as long as I leave some bytes for the sinclair basic loader, is this correct?