In a compiler I have used earlier it was possible to see directly which databytes were where in the chain so that I did not have to try moving a byte to xdata just to find out that that space was shared by someting else making the move worthless. Is such a table available with Keil? I can make neither head nor tail of the M51 file in this respect. Erik
You could consider using some simple filtering tools to extract, for example, the DATA area in the M51 file's SYMBOL TABLE and run that through a sort to get a quick idea of what overlays what and how bit the overlaid areas are.
gawk -f m51data.awk erik.m51 | sort > m51data.out
/SYMBOL TABLE OF MODULE:/ { do { if (substr($1, 1, 2) == "D:") print } while (getline) }
D:001FH PUBLIC AnnuncTmr D:0023H SYMBOL startClk D:0025H SYMBOL buf D:0025H SYMBOL i D:0025H SYMBOL lcdBuf D:0025H SYMBOL lcdBuf D:0025H SYMBOL p D:0025H SYMBOL pUnadj D:0025H SYMBOL p_ D:0025H SYMBOL storeCtlNdx D:0025H SYMBOL t D:0025H SYMBOL t_ D:0026H SYMBOL p D:0026H SYMBOL shiftCtr D:0027H SYMBOL bitCtr
I minor bit of editing above... s/bit/big/ s/uploade/uploaded/ Now, with that out of the way... Inspecting the sorted output, the addresses having a single data object are where the move to xdata will be the easiest. These are usually associated with data objects having static duration (i.e., globals and those defined static).
Thanks Dan, Just back at work after moving, I'll try it when my brain has come back Erik
OK, and if that simple version does not quite do the trick, we can get a little fancier to get the results you want. "If you can spec it, we can tweak it!" (TM) ;-)