If you need extra / new RAM variables for your code. Try using ALDL mode 2 or 3 to read the memory space where the internal RAM is located. Do this a few times to see which locations are not changing. These are PROBABLY available. Good for quick and dirty tests of code without wanting to really figure out which locations are avail. by reading the entire code.

Cheers,
J

 

You can do this with my program, just specify the memory location range and it should dump fine to file as though it was a BIN. Then do a comparison after the fact.

 

I would really be careful about that. I would also recommend doing a "search" on the specific address that you think maybe free within the hack to ensure it is not referenced (and even that is no guarantee as sometimes the byte is accessed by "Indexing").

It may be the "byte" that hasn't changed may only be referenced in specific situations which you didn't encounter during "your test". I still feel the safest thing to do is to go through the hack and document all "low order memory".

From my review of the SD 7730, there are VERY FEW bytes free. The method you are mentioning is what I plan to do to CONFIRM they are free.