AnsweredAssumed Answered

Codewarrior, PRM File, PPAGE and ROM

Question asked by Adam Oldham on Jul 6, 2006
Latest reply on Jul 7, 2006 by Daniel Lundin
I am using an mc9s12gc32 chip with Codewarrior 5.5. My project is set up with the small model.

One problem, by default it looks like when the code/project is up and running with the P&E Micro debugger that I am running without paged ROM as I show valid ROM at 0x4000 to 0x7fff and 0xC000 to 0xFFEF. According to the Freescale documentation, 0x4000 to 0x7fff should be free while 0x8000 should be used for the ROM pages (and C000 is fixed).

Am I wrong here?!? Or is it right that 0x4000 and 0xC000 are the start of the ROM areas (instead of 0x8000 and 0xC000).

================================================================
Next problem, the PRM file looks like this immediately after a new project is created:
SEGMENTS /* Here all RAM/ROM areas of the device are listed. Used in PLACEMENT below. */
RAM = READ_WRITE 0x0400 TO 0x0FFF;

/* unbanked FLASH ROM */
ROM_C000 = READ_ONLY 0xC000 TO 0xFEFF;

/* banked FLASH ROM */
PAGE_3D = READ_ONLY 0x3D8000 TO 0x3DBFFF;
/* PAGE_3F = READ_ONLY 0x3F8000 TO 0x3FBFFF; not used: equivalent to ROM_C000 */
END

With a fresh project, I can click make and load into the debugger and I get this error:
Error while writing to 3d8000 to 3d8200. Information: No memory available at this address.

Why is it that a fresh project made for this specific CPU can't access ROM area to erase that it thinks should be there?!?

================================================================

if page 3F will show as ficed in 0xc000, then how do I get page 3e moved so it shows up in 0x8000 instead of 0x4000?

Outcomes