Quote:
|
Originally Posted by Jon236
It does....another approach (which might save some memory space), is based on your thumbwheel positions, call a function which puts the dsitred command list into the structure. That way you'll just have one structure, not multiple copies.
|
You'd be better off declaring all the arrays as rom const as Alan described, because if you have a function copy the data into the struct then all that data still has to reside in Flash AND then you end up using a bunch of RAM for the RAM copy. You may as well just use it out of Flash directly. Plus you'll waste a bunch of CPU cycles doing the copying
. We're not using the script language but from what I understand the array does not get changed at run-time so it's a good candidate for making rom const. Unfortunately that doesn't help with Chris' other problem of filling up the 32K of Flash.
Something that might be worth considering is using the EEPROM to store your autonomous programs to get them out of Flash - you'll have to use the EEPROM code that someone posted on here last year though and it would generally be painful, but it would free up some space.