debugging error.

Different ARM chips have different behaviour with regard to invalid memory accesses. It is the glue logic outside the processor kernel that is generating exceptions.

Are there memory at the mentioned address? Is it writeable memory? If not, you will have to figure out why your application tries to perform a write access in that memory region.

Different ARM chips have different behaviour with regard to invalid memory accesses. It is the glue logic outside the processor kernel that is generating exceptions.

Are there memory at the mentioned address? Is it writeable memory? If not, you will have to figure out why your application tries to perform a write access in that memory region.

Is it?

Isn't that message from the debugger (or the simulator)?

So it's the debugger (or the simulator) that is not correctly configured...?

See:
http://www.keil.com/forum/docs/thread10080.asp

http://www.keil.com/support/docs/814.htm

When running on the hardware, it's the memory controller glue that may (or may not) generate exceptions.

When running in a simulator, then it is obviously the Keil simulator (and the configuration to it) that decides if there will be a memory access violation or not.

The question is still if there is expected to be any writeable memory at that specific memory address.

Thanks for the reply...
I understood what you said.
How do I specify all the address ranges?
My compiler supports up to 16MB only, and my address range is up to 256MB...
Also where do i specify all these addressed. Address range and access type can be given in command line by MAP command. But entering all these ranges every time I compile is bit difficult. So how do I specify these to be fixed?

The answer to that is given in the knowledgebase article linked earlier.

These are debugger commands - they have nothing to do with compiling or the compiler!

You can put commonly-used debugger command sequences into a debugger command file - See: http://www.keil.com/support/man/docs/uv3/uv3_cm_include.htm