bdi
Wind
for Tornado™, BDI2000 (MPC8xx/MPC5xx)
User Manual
19
© Copyright 1997-2007 by ABATRON AG Switzerland
V 1.38
Breakpoints:
There are two breakpoint modes supported. One of them (SOFT) is implemented by replacing appli-
cation code with a TRAP instruction. The other (HARD) uses the built in breakpoint logic. If HARD is
used, only up to 4 breakpoints can be active at the same time.
The following example selects SOFT as the breakpoint mode:
BREAKMODE SOFT ;<AGENT> SOFT or HARD, HARD uses PPC hardware breakpoints
All the time the application is suspended (i.e. caused by a breakpoint) the target processor remains
freezed.
Restrictions when using Agent mode:
This mode supports only system level debugging. Only fully linked systems can be debugged. Load-
ing of modules is not supported because an agent not running within the target cannot create Vx-
Works tasks. In general only the system context is supported.
Following a list of unsupported WDB requests and WDB requests with restrictions:
bkendModeSet
Only WDB_MODE_EXTERN is accepted
bkendMemFill
Supported, but large memory blocks may cause a target agent time-out
bkendMemMove
Supported, but large memory blocks may cause a target agent time-out
bkendMemChecksum
Supported, but large memory blocks may cause a target agent time-out
bkendMemProtect
Returns OKAY but does nothing
bkendCacheTextUpdate
Returns OKAY but does nothing
bkendMemScan
Supported, but large memory blocks may cause a target agent time-out
bkendVIOWrite
not supported
bkendFuncCall
not supported
bkendDirectCall
not supported
For large VxWorks core, the target server time-out value may be increased.
Tornado II:
Hardware breakpoints are also supported with Tornado II. There are 4 instruction and 2 data hard-
ware breakpoints available. Hardware breakpoints can be set with the Tornado Shell (enter help).
The following example sets a hardware breakpoint on writing to the variable "loopCount":
bh &loopCount,3
