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. ERAD’s
features such as the EBC, SEC, ANDOR, and PCTRACE have a dedicated ownership scheme
and register set for every instance. There are three possible ownership
scenarios:
- The user elects to completely
hand over the ownership of the ERAD features to the application software or
the debugger.
- Only the current owner of the
module (application code or debugger) is allowed to use the module at a
given time. Either the debugger or application own a particular EBC/SEC
block to ensure no conflicts arising.
- There is no ERAD features. In
this mode, both application code and debugger can access the module at any
given time. It is critical for the software, both on the application side
and the debugger side, to resolve any potential conflicts. 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