CW 6.3 MCF51JM128 Debugging Memory Map "overlapping memory"

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

CW 6.3 MCF51JM128 Debugging Memory Map "overlapping memory"

672 Views
Wanderer
Contributor II

Anyone understand the error message below?

 

MCF51JM128 Debugging Memory Map


-A memory range from 0x3fe to 0x40f is of "internal" type for display purpose.


-A memory range from 0xc00000 to 0xc0000f is of "internal" type for display purpose.


-A memory range from 0xffff8000 to 0xfffffffc is of "internal" type for display purpose.  WARNING: This module is overlapping with module having Comment:"Memory Mapped Reg. Block 4".


-A memory range from 0xffff98a1 to 0xffff98b2 is of "internal" type for display purpose. WARNING: This module is overlapping with module having Comment:"Memory Mapped Reg. Block 3".


-A memory range from 0x0 to 0x1ffff is of "physical" type,therefore accessed directly in device physical memory (0x0-0xffff).


-A memory range from 0x800000 to 0x803fff is of "physical" type,therefore accessed directly in device physical memory (0x0-0xffff).

 

Thanks, gj

Labels (1)
0 Kudos
Reply
3 Replies

405 Views
CrasyCat
Specialist III

Hello

 

To me it is obvious that

   memory range from 0xffff8000 to 0xfffffffc overlaps with memory range from 0xffff98a1 to 0xffff98b2 .

 

What exactly have you trouble to understand here?

 

CrasyCat

0 Kudos
Reply

405 Views
Wanderer
Contributor II

CrasyCat,

 

Why is CW creating overlapping memory banks?  I would expect the compile to fail if it's overwriting memory.

 

Where do I start looking to fix it?

 

Thanks, gj

0 Kudos
Reply

405 Views
CrasyCat
Specialist III

Hello

 

Sorry, I do not have the hardware available to try this out. So I cannot help further.

I would recommend you to submit a service request for that.

Click here to submit a service request.

CrasyCat

0 Kudos
Reply