help using intEEPROM bean with Full Chip Simulator on HCS12X.

[holder]

Hi Folks,

  I am using CodeWarrior v5.1 with Processor Expert. Target is MC9S12XDT512.

I am having trouble getting the intEEPROM working in the simulator. Here is what I tried to start.

1. create tutorial project (GuessTheNumber).

2. add IEE1 intEEPROM component from Processor Expert.

3. Set IEE1 "Start Address" to 13F000, "Used Size" to 400.

4. Make project.

5. Run project using FCS.

When the call to PE_low_level_init() returns I see the error :

FCS Warning (ID 9): writing to unimplemented register at pc=0xfe822d'L, Value: 0x4A, Memory Address: 0x110. EEPROM CONTROL module not implemented.

Can some kind soul tell me what I am doing wrong?

thx,

bob

[kef]

EEPROM simulation is not full implemented. You get only EEPROM registers defined in memory space, for which you get warning every time you access them.

[holder]

Are you certain about this? If I remove the EEPROM bean from the project I still get the same error message when accessing the EEPROM when running the simulator- so what is the value of adding the bean? Something is not right if I get the message with and without the bean in the FCS.

Specifically reading the file FCS_Notes_MC9S12DP512.pdf the 4Kbyte EEPROM Module is tagged with subscript 1.

1) Any memory is integral part of the core simulator

 It is NOT tagged with subscript 3 which indicates the behavior you describe.

3) Registers of this module are implemented to allow read and write access but no module specific functionality

Freescale, can you comment on the functionality of the EEPROM bean in the FCS?

thank you,

bob

[kef · Accepted solution]

Beans have nothing to do with simulator. Beans generated code should work on real hardware. And I meant previously that simulator support for EEPROM is not complete. What you have to do on real hardware to write or erase EEPROM: write to EEPROM, write command register, write status register, wait for operation complete - this all won't work properly in current simulator.

Yes, you found good point in documentation:

"Registers of this (EEPROM) module are implemented to allow read and write access but no module specific functionality"