Access violation at 0xFFFE2000

Hi,

I just started a project with the NXP (Sharp) LH79525 controller.
I created a new project in Keil µVision3, selected the controller, and used the pre-made startup file; LH79524.s
The LH79524 and LH79525 are all most identical, so I guess that is why it chooses this one.

I wrote a simple C program, just to try out the simulator, but here the problem begins.
When building, no warnings or errors occurs, but when running the Debug, I get the access violation in the 0xFFFE2000 register.
This is the RCPC (Reset, Clock and Power Register) register. I am not really experienced in programming systems like this, but I find it pretty impotent to have access to this register.

Any one who knows if this is a bug, or some setting that has not been set?

Regards Bjoern Soerensen

 RE: Access violation at 0xFFFE2000

what does the device's data sheet tell you? I don't know your device, the answer IS there.

 RE: Access violation at 0xFFFE2000

I do exactly what the datasheet tell me.
But it seems that the default values for the controller are not loaded right.

According to the LH79525 User manual, bit 9 in 0xFFFE2000 should be, by default be 1. This is the write protection bit for RCPC register.

 RE: Access violation at 0xFFFE2000

But it seems that the default values for the controller are not loaded right.

It's possible that there are bugs in the simulator. You can report them to Keil and wait for a fix in future releases, or you can provide a workaround using debugger initialization script.

 RE: Access violation at 0xFFFE2000

Ok, that's what I feared.
I will make a report to Keil about it.

Can you give me some more information regarding debugger initialization script? I am not familiar with this.

 RE: Access violation at 0xFFFE2000

Can you give me some more information regarding debugger initialization script? I am not familiar with this.

It's here:
http://www.keil.com/support/man/docs/uv3/uv3_db_cmd_input_file.htm

You can initialize MCU registers with proper values using debugger initialization file.

 RE: Access violation at 0xFFFE2000

Thank you very much. I will take a look at it right away.

 RE: Access violation at 0xFFFE2000

Hello Bjoern Soerensen,

Please notice that there is no simulation for this device available. See also http://www.keil.com/dd/chip/4470.htm

Best Regards,
Martin Guenther

 RE: Access violation at 0xFFFE2000

Hi,

Incredible that I have not seen this before now.
Guess this is the reason for my problems, or what?

The note says:

NOTE
Simulation for this device is provided by the default peripheral simulation driver.

Complete peripheral simulation is not available at this time