Kinetis MicrocontrollersのトピックRe: flex memory in debug

flex memory in debug

kristies1 — Wed, 31 Oct 2012 16:29:13 GMT

I have flex memory in K60 partitioned as eeprom, and would like the dflash to not be erased when debugging with CW10.2.

Currently every time I start a new debug session the dflash is erased, and losing all eeprom contents.

How can I keep CW from erasing the dflash?

Kristie

Re: flex memory in debug

pbanta — Wed, 31 Oct 2012 16:53:24 GMT

Hi Kristie,

I use Target Tasks to accomplish this on my K70FX project. You can create a Target Task and associate it with a debug configuration. It gives you total control over what is erased/programmed to a sector boundary. You can find info about Target Tasks here:

CodeWarrior Tool Tip #2: Programming flash memory is easy &laquo; The Embedded Beat: Freescale Blog Community

Good luck.

Paul

Re: flex memory in debug

BlackNight — Wed, 31 Oct 2012 17:13:00 GMT

Beside of using a Target Task, you can use a setting to preserve regions of your flash:

Programming part of flash | MCU on Eclipse

Hope this helps,

Erich

Re: flex memory in debug

kristies1 — Wed, 31 Oct 2012 19:07:37 GMT

Thanks for the reply. I had range error problems with the non-volatile memory preservation, but that page helped.