What's mean that CMD440-COR182-TAD23-NAL29

There are two possibilities:

1) enabling the MMU changes the virtual/physical address the core is running at

2) enabling the MMU changes the permissions at the virtual address the core is running at

the second is most likely but be aware of the first.

if your MMU setup marks the range where you're trying to step as read-only you can't set a breakpoint there anymore, which is how pre-v8 cores handle stepping.

try before you start stepping:

memory 0xXXXXXX +0xYYY ro,nobp,hbp 

Where the two numbers are the start and length of the read-only range. Generally it is advised that stepping into MMU enable isn't really possible (because the debugger is executing instructions via the core in the core's context and it changes).

You could set a breakpoint (hardware based if it's read only memory) past the MMU enable and run through it, though.

Matt

There are two possibilities:

1) enabling the MMU changes the virtual/physical address the core is running at

2) enabling the MMU changes the permissions at the virtual address the core is running at

the second is most likely but be aware of the first.

if your MMU setup marks the range where you're trying to step as read-only you can't set a breakpoint there anymore, which is how pre-v8 cores handle stepping.

try before you start stepping:

memory 0xXXXXXX +0xYYY ro,nobp,hbp 

Where the two numbers are the start and length of the read-only range. Generally it is advised that stepping into MMU enable isn't really possible (because the debugger is executing instructions via the core in the core's context and it changes).

You could set a breakpoint (hardware based if it's read only memory) past the MMU enable and run through it, though.

Matt

Hi Matt,

Thank your suggestion. The issue was fixed.