
540
Evaluating and Programming the 29K RISC Family
tive to produce a configuration for most 29K platforms. In a rare case it may be neces-
sary to modify the source code.
For example, if a 29K system had some
special
FIFO hardware which had to be
accessed is a restricted way, the
peek
and
poke
functions would need modification to
deal with the necessary protocol.
void
cfg_peek
(to, from,count,space,size)
from
address
identifies a DebugCore data region which is to receive the data. The
count
parameter
refers to the number of objects of size
size
(measured in characters). The
space
pa-
rameter identifies the address space for the source data at address
from
; this parame-
ter is mostly iused by 3–bus procesors.
void
cfg_poke
(to, from,count,space,size)
All writes to off–chip resources are performed by this function. The data is sup-
plied from a DebugCore data region pointed to by the
from
parameter.
void
cfg_core_enter
()
This function is called when the DebugCore gains control for any reason (other
than the call to
dbg_control()
). It is called after the DebugCore has saved context and
requested a HALT message be sent to MonTIP. It is called before the DebugCore
starts processing any received message from MonTIP.
It enables the environment in which the DebugCore runs to be modified. For ex-
ample,
cfg_core_enter()
normally turns interrupts on. If it is desired that interrupts
should remain off during DebugCore operation, then the TD and DI bits should be set
in this function.
int
dbg_errno
This 32–bit memory location is used by the configuration module to indicate an
error with a requested
peek
or
poke
operation.