Using PEEDI
different profiles for the same FLASH, for example with different program method
type or different image file specified. This way you can easy switch to the desired
profile using the
flash set
command
COREn_ENDIAN
Synopsis:
COREn_ENDIAN = LITTLE|BIG
Description:
Define core endianness
COREn_BREAKMODE
Synopsis:
COREn_BREAKMODE = SOFT|HARD
COREn_BREAKMODE = HARD, start_addr, end_addr
Description:
Default breakpoint mode. Use to force the usage of hardware break points, when
debugging in FLASH, or when working with GDB v5.3, where the hbreak command
does not work. If ’start_addr’ and ’end_addr’ are given, then the hardware breakpoints
are used for this address range.
Note
:
The ARM EmbeddedICE logic has hardware resources for two break conditions, never
mind break or watch points. The use of software breakpoints allows unlimited number
of them, but this still requires the hardware resource of one break/watch point.
Software breakpoints are possible only if the code is executed from RAM since the
desired instruction to be hit is exchanged with special pattern. In brief, you can use up
to two watchpoints or hardware breakpoints; or one watchpoint or hardware
breakpoint, and unlimited number of software breakpoints. This means that you may
use only one watch point and still debug normally in RAM. But if your code is in
ROM/FLASH you must use hardware breakpoints, so if you have set one break or
watch point you can still do ’single step’, ’step in’ and ’step out’, but if you have set two
watch or break points, only ’continue’ is possible after the target breaks, since the
debugger needs a temporary break point to achieve the ’step’ functionality.
PEEDI User’s Manual
33