Hi BugBlatter
I am intentionally using a linear address range in the project:
0x4000...0xffff is addressed with no paging necessary and so runs with maximum efficiency (this is achieved by leaving PPAGE at its initial value of 0x00).
The 0x3d page is then used exclusively by the file system for saving parameters, web pages and other recorded data. The file system manager switches the page in and out when it needs to save or retrieve something.
The problem I have with the CodeWarrior debugger is that it automatically erases all FLASH contents when updating code (all pages). This means that it also trashes and data in the file system (for example hardware parameters such as the local MAC address and files such as web pages) and these have to be restored after a software upgrade, making development work rather tedious.
I have another downloader which allows me to delete only the pages containing code (in my case it leaves the 0x3d page intakt). Then I can switch back over to the CodeWarrior if I need to debug anything.
The CodeWarrior 3.1 had problems with linear memory writing (downloads failed) but this has been solved in the latest V4.5 for HCS12.
There remains the minor restriction that (as far as I know) it can not be set up to not delete specific pages. This is a 'minor' CodeWarrior definciency for which there are cures in conjunction with other downloader tools.
Regards