Safety-certified tools Tools for Automotive Applications C-STAT Static analysis C-RUN Runtime analysis Debugging and trace probes Build tools for Linux
Accessing registers in an unclocked or powered-down peripheral unit, in C-SPY, might give unexpected results.
Accessing registers in an unclocked or powered-down peripheral unit during debugging might cause unexpected behavior. Incorrect data can be read, writes might have unexpected results or no effect. In some cases, writes or reads might cause the CPU to reset or the debug connection might be lost.
The exact behavior in such cases depends on the device implementation.
Just displaying the peripheral memory address range in the Memory window or displaying the peripheral registers in the Registers window can be enough to cause these effects.
One way to view some registers, while avoiding accessing unclocked or powered-down peripheral registers, is to create an application-specific register group. To do that, choose View > Registers > Register User Groups Setup during a debug session. Create a User Register Group with only the registers that can be accessed without issues.
Note that you can create a combined group that contains registers from any predefined register group (for example a combination of UART and GPIO registers).
If accessing registers in an unclocked, powered-down or otherwise disabled peripheral unit leads to crashes or to a change in program behavior, you must take steps to avoid this. Consider these alternatives:
For information on C-SPY macros and Register User Groups, choose Help > C-SPY Debugging guide.
All product names are trademarks or registered trademarks of their respective owners.