4
SK/ZK Series User's Manual
Page 33
dialog box, choose
“MCU Configuration”
from the
“inDART-HCS12”
menu. The
MCU Configuration
dialog box will appear. Press the
“Communication Settings”
button.
4.4.8 Hardware Breakpoints and Software Breakpoints
A “hardware” breakpoint is set by taking advantage of the microcontroller’s
integrated debug peripheral. A hardware breakpoint doesn’t waste system
resources, you can set/remove them at any time (even during program
execution), but the number of available hardware breakpoints is limited.
A “software” breakpoint, on the other hand, does not take advantage of the
microcontroller’s integrated debug peripheral.
To set a software breakpoint, there are two possibilities: you can set a
software breakpoint in RAM or in FLASH. In both cases, an unlimited
number of software breakpoints can be set.
To set a software breakpoint in a RAM location, just insert a breakpoint to
that location: CodeWarrior will automatically replace the opcode present at
that location with the
“BGND”
Assembly instruction.
To set a software breakpoint in a FLASH location, you have to insert the
“BGND”
Assembly instruction into your application’s source code, recompile
the code and restart a debug session. The program execution will stop as
soon as the
“BGND”
instruction is fetched.
4.4.9 Advanced Debugging Features
The microcontroller’s built-in DBG12 module allows you to set “complex”
hardware breakpoints and to take advantage of a trace buffer.
While in debug, under the
“inDART-HCS12”
menu you will find the
“Trigger
Module Settings…”
command, that opens a dedicated dialog box which
allows you to handle all of the parameters of the microcontroller’s debug
peripheral.
