This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

how to find what to work on when 256 bytes get full

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

Parents
  • 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).

Reply
  • 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).

Children