CrasyCat,
Thanks for the reply!
Yeah, I think that is exactly the problem I'm having. I tried a variety of things in the code, this was one of them:
#pragma define_section _datastr ".datastr" far_absolute RW
__declspec(_datastr) int x12;
__declspec(_datastr) int y12;
We are using Processor Expert, which generates an LCF file. What I think I want is a .datastr section from 0x20000000-0x200000FF then .data from 0x20000100- 0x2000FFFF. I tried using the CPU Bean build options to create a 4th memory area called datastr, but when I looked at the map file, I don't think this did what I want (i.e. the section didn't have a .datastr name like .data does.)
If Processor Expert won't do what I want, I don't have a problem with disabling the LCF generation and manually editing the LCF file....
Could you tell me what I would need to do?
Do I need to make a "section" inside the data "memory area" or do I need to define a whole new section? If I could locate a section inside data at a specific address (the same way something like .bss and .romp appear in the map) that might be all I need to do (?) (I'm not sure of the terminology as to what's a segment, section, memory area, etc... haven't found doc on this yet)
Thanks!
Ross