CW4.6 Can't debug paged EEPROM

[sebasira]

I'm facing this problem.. Using CW4.6 with HCS12XA256...

When debugging, I can't see paged EEPROM on memory component. It shows as "--". Non-paged one, shows fine... Could anyone tell me what's going on?

I create a new empty project and same thing happened.

I'll attach an image of the problem

Thanks in advance!

[sebasira]

I download the CW5.0 just to test it... and with it I can correctly debug... What could be happening with CW4.6? I'll continue working with v4.6 because of code limitations on v5.0 

[CrasyCat]

Hello

    I assume you are attempting to debug in simulator. Am I right?

    I also assume you have nothing downloaded inside of the paged EEPROM, Am I right?

   If this is the case you need to tell the debugger which are the valid memory areas for that chip.

   This can be adjusted as follows:

        - In the debugger select HCS12X FCS > Configure.

        - In the Memory Configuration dialog  either change to auto on write access or change to user defined.

        - If you selected user defined, add memory blocks corresponding to the HCS12XA256 MCU

        - Once you have finished, click on Save and save the file as default.mem in your project directory.

          This way the memory configuration file will be loaded automatically each time you start a debug session for the

          project.

CrasyCat

[sebasira]

Hello!

No, I'm not debugging in simulator...

And I can't find those options you suggest. I can't find "HCS12X FCS" on Debugger's Menu.. Here's a screenshot of my menu

I found the "debugging memory map" under MultilinkCyclonPro menu entry.

Maybe I've got to change something there... I also post a picture of that. I don't understand much, but it says that banked eeprom goes from "10800" to "FF0BFF". Is that correct? In prm file it goes from FC0800->FC0BFF, FD0800->FD0BFF and FE0800->FE0BFF. 

Thanks for helping!

[CrasyCat · Accepted solution]

Hello

OK if you are debugging on real hardware you need to adjust the Debugging Memory Map.

The dialog is described in {Install}\Help\PDF\Debugger_HC12.pdf, chapter 18 Debugging memory Map.

Alternatively as you said this was working fine on V5.1, you can check how the memory map is defined for the MCU on this version and duplicate the config on V4.x.

CrasyCat