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 can make neither head nor tail of the M51 file in this respect."

    I'm afraid that's what has the information you require, so you're gonna have to bite the bullet... :-(

    I did write something in Excel once to make some sort of sense (to me) of the data organisation from the M51 file.
    Dunno if it might be of any use to you? (or even if it still works...)

Reply
  • "I can make neither head nor tail of the M51 file in this respect."

    I'm afraid that's what has the information you require, so you're gonna have to bite the bullet... :-(

    I did write something in Excel once to make some sort of sense (to me) of the data organisation from the M51 file.
    Dunno if it might be of any use to you? (or even if it still works...)

Children