i got it a bit mixed up RAM_END is the last physical byte for chip
so you need to read lst file to see where allocated mem finishes.
pic18's only of course
so ...
buff max size = RAM_END...
this may be a possibility i have not got around t trying it, it may need asm support
i kind of forget the vagaries of pbp labels
asm var RAM_END is set to last byte allocated by pbp
Ram past...
Unfortunately, the Linker will reserve memory you claim at compile time. I can only suggest reserve test3 var byte[maximum expected size]. Unless you're scarce on SRAM, it shouldn't matter.
i can fix the problem by assign the max value used to buffer array , but it just a waist of buffers when they are not needed when the value should be lower than the max number , just goes against...
its an exiting program that uses named constants to set the buffer size , the same named constants are used in multi locations to set other variables and math
Allocation of memory is done at compile time - not during runtime. Hence the content of a variable can not dictate the size of an array since the content of a variable, by definition, can change...
Competitions are subject to the privacy policy and website terms and conditions of picbasic.co.uk, owned and controlled by Crownhill Associates Limited (“Crownhill”).
The following rules shall apply, together with any instructions or rules specific to any current competition. By entering any of the community run competitions, you are deemed to have accepted the following:
...
Common Development and Distribution License (CDDL) is a free software license, produced by Sun Microsystems, based on the Mozilla Public License (MPL), version 1.1.
Menu
Re: varable index buffer setup unsing a varable
i got it a bit mixed up RAM_END is the last physical byte for chip
richard - 27th November 2020, 02:38so you need to read lst file to see where allocated mem finishes.
pic18's only of course
so ...
buff max size = RAM_END...