Although the features of the ERAD module are
typically used by the debugger, user applications can also take advantage of the
capabilities to monitor buses and generate interrupts and events. There are three
possible ownership scenarios:
- The user elects to give
ownership of the ERAD module to the application software or the
debugger.
- Both the application code and
the debugger share use of the ERAD module. Only the current owner of the
module (application code or debugger) is allowed to use the module at a
given time. When ownership is shared between application and debugger, the
user application has the responsibility of resolving any ownership
conflicts.
- There is no ERAD owner. In
this mode, both application code and debugger can access the module at any
given time. The software, both on the application side and the debugger
side, to resolve any potential conflicts is critical. An example scenario in
this mode can be for the debugger to use some of the EBC and SEC units,
while the application software uses the remaining units.
The ERAD module initializes the internal states
and all registers to the initial/reset states under the following conditions:
- At power-on-reset (POR)
- With DCON and SYSRSN
- Debug logic disconnected when the debugger owns the module
- Functional reset when application owns the module