We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
My project have a large xdata area divided into several segments: VBI data, USER data, OSD char data, OSD display data ... Since some variables were defined as absolute with _at_ directive for all the segments listed above, just to speed up my job, I am having problems to list into the MAP file the real size of my "USER data". I've already used the "XDATA" directive and all absolute varialbes that are out of the "USER data" boundaries were count together. Does startup.a51 file have any point to change regarding the size? As I see, it only initializes the memory. Some hints: xdata range: 0xc000 - 0xffff VBI range : 0xc000 - 0xc357 USER range: 0xc357 - 0xc857 (*) ... (*) This is the only segment I would like to list into my MAP file Does anybody have a solution? Thanks and regards
Why do the listed contents of your MAP file bother you so much? You may be abusing the tools already (_at_ and the XDATA macro, in particular). Maybe you should start from scratch and tell us what it actually is you're trying to achieve, and why you chose the approaches you're using now.