CodeWarrior Development ToolsのトピックRe: debug erasing EEprom

debug erasing EEprom

mlockner — Wed, 05 Nov 2014 12:26:44 GMT

When starting a new debug session (mc9s08dz128) the second 1K of the EEprom memory is getting cleared. I have the address range 0x3c00 to 0x3ff blocked from writing and this works for the first 1K of EEprom but does not stop Page 1 from being erased. Is there a way to prevent Page 1 from being erased?

Re: debug erasing EEprom

trytohelp — Fri, 07 Nov 2014 08:26:56 GMT

Hi Martin,

What is the tool version used ?

CW for MCU V6.3 (Classic) or CW for MCU v10.x (eclipse)

Have a great day,
Pascal Irrle

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: debug erasing EEprom

mlockner — Fri, 07 Nov 2014 12:16:42 GMT

I am using codewarrior 10.6

Re: debug erasing EEprom

trytohelp — Fri, 07 Nov 2014 14:07:23 GMT

Martin,

In the prm file, the EEPROM is defined by:

EEPROM

= READ_ONLY

0x3C00 TO 0x3FFF;

the EEPROM size is 0x400.

Do you mean each time you will launch the application the EEPROM is cleared ?

Do you use Processor Expert ?

What is the Page 1 ?

The PPAGE_1 is already contained in segment at 0x4000-0x7FFF.

I don't understand what is the problem.

Have a great day,
Pascal Irrle