This usually happens when the peripheral module is accessed before its clock has been enabled.
Many microcontrollers disable peripheral clocks by default to reduce power consumption. If TRACE32 (or the application) accesses registers of a peripheral whose clock is not running, the access may result in a bus error. In TRACE32, this is typically indicated by question marks (?) instead of a register value.
Depending on the processor architecture, such an invalid access can also have more severe consequences. The access may cause a bus stall, blocking further memory accesses and potentially leaving the processor unresponsive until a reset is performed.
Therefore, before accessing a peripheral module or its registers, make sure that:
The peripheral clock is enabled.
The peripheral module has been properly initialized.
Any required power or reset control settings for the module are configured correctly.
After the peripheral is enabled and accessible, its registers can be safely read or modified.
To prevent accidental access to peripheral registers, particularly those with severe effects on the target state, users can restrict debugger access via the command MAP.DenyAccess.
Once peripheral initialization is complete, debugger access can be restored using the command MAP.NoDenyAccess.
For detailed descriptions of the commands MAP.DenyAccess and MAP.NoDenyAccess, please refer to the General Commands Reference Guide M.
Add a comment