Reset Manager HWIP Technical Specification
Overview
This document describes the functionality of the reset controller and its interaction with the rest of the OpenTitan system.
Features
- Stretch incoming POR.
- Cascaded system resets.
- Peripheral system reset requests.
- RISC-V non-debug-module reset support.
- Limited and selective software controlled module reset.
- Always-on reset information register.
- Always-on alert crash dump register.
- Always-on cpu crash dump register.
- Reset consistency checks.
Theory of Operation
The OpenTitan reset topology and reset controller block diagram are shown in the diagram below. The reset controller is closely related to the power controller, please refer to that spec for details on how reset controller inputs are controlled.
Reset Topology
The topology can be summarized as follows:
- There are two reset domains
- Test Domain - Driven by
TRSTn
- Core Domain - Driven by internal POR circuitry.
- Test Domain - Driven by
- Test domain is comprised of the following components
- SOC TAP and related DFT circuits
- RISC-V TAP (part of the
rv_dm
module)
The test domain does not have sub reset trees.
TRSTn
is used directly by all components in the domain.
The Core domain consists of all remaining logic and contains 4 sub reset trees, see table below.
Reset Tree | Description |
rst_por_n
|
POR reset tree.
|
rst_lc_n
|
Life Cycle reset tree.
|
rst_sys_n
|
System reset tree.
|
rst_{module}_n
|
Module specific reset.
|
The reset trees are cascaded upon one another in this order:
rst_por_n
-> rst_lc_n
-> rst_sys_n
-> rst_module_n
This means when a particular reset asserts, all downstream resets also assert.
The primary difference between rst_lc_n
and rst_sys_n
is that the former controls the reset state of all non-volatile and life cycle related logic in the system, while the latter can be used to issue system resets for debug.
This separation is required because the non-volatile controllers (otp_ctrl
/ lc_ctrl
) are used to qualify DFT and debug functions of the design.
If these modules are reset along with the rest of the system, the TAP and related debug functions would also be reset.
By keeping these reset trees separate, we allow the state of the test domain functions to persist while functionally resetting the rest of the core domain.
Additionally, modules such as alert handler and aon timer (which contains the watchdog function) are also kept on the rst_lc_n
tree.
This ensures that an erroneously requested system reset through rst_sys_n
cannot silence the alert mechanism or prevent the system from triggering a watchdog mechanism.
The reset topology also contains additional properties:
- Selective processor HART resets, such as
hartreset
indmcontrol
, are not implemented, as it causes a security policy inconsistency with the remaining system.- Specifically, these selective resets can cause the cascaded property shown above to not be obeyed.
- Modules do not implement local resets that wipe configuration registers, especially if there are configuration locks.
- Modules are allowed to implement local soft resets that clear datapaths; but these are examined on a case by case basis for possible security side channels.
- In a production system, the Test Reset Input (
TRSTn
) should be explicitly asserted through system integration.- In a production system,
TRSTn
only needs to be released for RMA transitions and nothing else. .
- In a production system,
Reset Manager
The reset manager handles the reset of the core domain, and also holds relevant reset information in CSR registers, such as:
- RESET_INFO indicates why the system was reset.
-
ALERT_INFO contains the recorded alert status prior to system reset.
- This is useful in case the reset was triggered by an alert escalation.
-
CPU_INFO contains recorded CPU state prior to system reset.
- This is useful in case the reset was triggered by a watchdog where the host hung on a particular bus transaction.
Additionally, the reset manager, along with the power manager, accepts requests from the system and asserts resets for the appropriate clock trees. These requests primarily come from the following sources:
- Peripherals capable of reset requests: such as sysrst_ctrl and always on timers .
- Debug modules such as
rv_dm
. - Power manager request for low power entry and exit.
- Direct software request for reset.
Shadow Resets
OpenTitan supports the shadow configuration registers. These are registers stored in two constantly checking copies to ensure the values are not maliciously or accidentally disturbed. For these components, the reset manager outputs a shadow reset dedicated to resetting only the shadow storage. This reset separation ensures that a targetted attack on the reset line cannot easily defeat shadow registers.
Reset Consistency Checks
The reset manager implements reset consistency checks to ensure that triggered resets are supposed to happen and not due to some fault in the system. Every leaf reset in the system has an associated consistency checker.
The consistency check ensures that when a leaf reset asserts, either its parent reset must have asserted, or the software request, if available, has asserted. While this sounds simple in principle, the check itself crosses up to 3 clock domains and must be carefully managed.
First, the parent and leaf resets are used to asynchronously assert a flag indication. This flag indication is then synchronized into the reset manager’s local clock domain.
The reset manager then checks as follows:
-
If a leaf reset has asserted, check to see either its parent or software request (synchronous to the local domain) has asserted.
-
If the condition is not true, it is possible the parent reset indication is still being synchronized, thus we wait for the parent indication.
-
It is also possible the parent indication was seen first, but the leaf condition was not, in this case, we wait for the leaf indication.
-
A timeout period corresponding to the maximum synchronization delay is used to cover both waits.
- If the appropriate pairing is not seen in the given amount of time, signal an error, as the leaf reset asserted without cause.
-
If all reset conditions are satisfied, wait for the reset release to gracefully complete the cycle.
Hardware Interfaces
Referring to the Comportable guideline for peripheral device functionality, the module RSTMGR
has the following hardware interfaces defined.
Primary Clock: clk_i
Other Clocks: clk_aon_i
, clk_io_div4_i
, clk_main_i
, clk_io_i
, clk_io_div2_i
, clk_usb_i
Bus Device Interfaces (TL-UL): tl
Bus Host Interfaces (TL-UL): none
Peripheral Pins for Chip IO: none
Interrupts: none
Security Alerts:
Alert Name | Description |
---|---|
fatal_fault | This fatal alert is triggered when a fatal structural fault is detected. Structural faults include errors such as sparse fsm errors and tlul integrity errors. |
fatal_cnsty_fault | This fatal alert is triggered when a reset consistency fault is detected. It is separated from the category above for clearer error collection and debug. |
Security Countermeasures:
Countermeasure ID | Description |
---|---|
RSTMGR.BUS.INTEGRITY | End-to-end bus integrity scheme. |
RSTMGR.SCAN.INTERSIG.MUBI | scan control signals are multibit |
RSTMGR.LEAF.RST.BKGN_CHK | Background consistency checks for each leaf reset. |
RSTMGR.LEAF.RST.SHADOW | Leaf resets to blocks containing shadow registers are shadowed |
RSTMGR.LEAF.FSM.SPARSE | Sparsely encoded fsm for each leaf rst check. The Hamming delta is only 3 as there are a significant number of leaf resets |
RSTMGR.SW_RST.CONFIG.REGWEN | Software reset controls are protected by regwen |
RSTMGR.DUMP_CTRL.CONFIG.REGWEN | Crash dump controls are protected by regwen |
Signals
Signal | Direction | Description |
---|---|---|
ast_i.aon_pok |
input |
Input from ast . This signal is the root reset of the design and is used to generate rst_por_n . |
cpu_i.rst_cpu_n |
input |
CPU reset indication. This informs the reset manager that the processor has reset. |
cpu_i.ndmreset_req |
input |
Non-debug-module reset request from rv_dm . |
cpu_dump_i |
input |
CPU crash dump state from rv_core_ibex . |
pwr_i.rst_lc_req |
input |
Power manager request to assert the rst_lc_n tree. |
pwr_i.rst_sys_req |
input |
Power manager request to assert the rst_sys_n tree. |
pwr_i.reset_cause |
input |
Power manager indication for why it requested reset, the cause can be low power entry or peripheral issued request. |
pwr_i.rstreqs |
input |
Peripheral reset requests. |
pwr_o.rst_lc_src_n |
output |
Current state of rst_lc_n tree. |
pwr_o.rst_sys_src_n |
output |
Current state of rst_sys_n tree. |
resets_ast_o |
output |
Resets used by ast . |
resets_o |
output |
Resets used by the rest of the core domain. |
Design Details
The reset manager generates the resets required by the system by synchronizing reset tree components to appropriate output clocks.
As a result, a particular reset tree (for example rst_lc_n
) may have multiple outputs depending on the clock domains of its consumers.
Each reset tree is discussed in detail below.
POR Reset Tree
The POR reset tree, rst_por_n
, is the root reset of the entire device.
If this reset ever asserts, everything in the design is reset.
The ast
input aon_pok
is used as the root reset indication.
It is filtered and stretched to cover any slow voltage ramp scenarios.
The stretch parameters are design time configurations.
- The filter acts as a synchronizer and is by default 3 stages.
- The count by default is 32.
- The counter increments only when all stages of the filter are 1.
- If any stage at any point becomes ‘0’, the reset counter returns to 0 and downstream logic is driven to reset again.
- Both functions are expected to operate on slow, always available KHz clocks.
Life Cycle Reset Tree
Life cycle reset, rst_lc_n
asserts under the following conditions:
- Whenever
rst_por_n
asserts. - Whenever a peripheral reset request (always on timer watchdog, rbox reset request, alert handler escalation) is received.
The rst_lc_n
tree contains both always-on and non-always-on versions.
How many non-always-on versions is dependent on how many power domains are supported by the system.
System Reset Tree
System reset, rst_sys_n
asserts under the following conditions:
- Whenever
rst_lc_n
asserts. - Whenever
ndmreset_req
asserts.
The rst_sys_n
tree contains both always-on and non-always-on versions.
How many non-always-on versions is dependent on how many power domains are supported by the system.
Output Leaf Resets
The reset trees discussed above are not directly output to the system for consumption. Instead, the output leaf resets are synchronized versions of the various root resets. How many leaf resets there are and to which clock is decided by the system and templated through the reset manager module.
Assuming a leaf output has N power domains and M clock domains, it potentially means one reset tree may output NxM outputs to satisfy all the reset scenario combinations.
Power Domains and Reset Trees
It is alluded above that reset trees may contain both always-on and non-always-on versions. This distinction is required to support power manager’s various low power states. When a power domain goes offline, all of its components must reset, regardless of the reset tree to which it belongs.
For example, assume a system with two power domains - Domain A
is always-on, and Domain B
is non-always-on.
When Domain B
is powered off, all of Domain B
’s resets, from rst_lc_n
, rst_sys_n
to rst_module_n
are asserted.
However, the corresponding resets for Domain A
are left untouched because it has not been powered off.
Software Controlled Resets
Certain leaf resets can be directly controlled by software.
Due to security considerations, most leaf resets cannot be controlled, only a few blocks are given exceptions.
The only blocks currently allowed to software reset are usbdev
and spidev
. Future potential candidates are i2cdev
, i2chost
and spihost
.
The criteria for selecting which block is software reset controllable is meant to be overly restrictive. Unless there is a clear need, the default option is to not provide reset control.
In general, the following rules apply:
- If a module has configuration register lockdown, it cannot be software resettable.
- If a module operates on secret data (keys), it cannot be software resettable.
- Or a software reset should render the secret data unusable until some initialization routine is run to reduce the Hamming leakage of secret data.
- If a module can alter the software’s perception of time or general control flow (timer or interrupt aggregator), it cannot be software resettable.
- If a module contains sensor functions for security, it cannot be software resettable.
- If a module controls life cycle or related function, it cannot be software resettable.
Reset Information
The reset information register is a reflection of the reset state from the perspective of the system. In OpenTitan, since there is only 1 host, it is thus from the perspective of the processor. This also suggests that if the design had multiple processors, there would need to be multiple such registers.
If a reset does not cause the processor to reset, there is no reason for the reset information to change (this is also why there is a strong security link between the reset of the processor and the rest of the system). The following are the currently defined reset reasons and their meaning:
Reset Cause | Description |
---|---|
POR |
Cold boot, the system was reset through POR circuitry. |
LOW_POWER_EXIT |
Warm boot, the system was reset through low power exit. |
NDM RESET |
Warm boot, the system was reset through rv_dm non-debug-module request. |
SW_REQ |
Warm boot, the system was reset through RESET_REQ. |
HW_REQ |
Warm boot, the system was reset through peripheral requests. There may be multiple such requests. |
The reset info register is write 1 clear. It is software responsibility to clear old reset reasons; the reset manager simply records based on the rules below.
Excluding power on reset, which is always recorded when the device POR circuitry is triggered, the other resets are recorded when authorized by the reset manager. Reset manager authorization is based on reset categories as indicated by the power manager. The power manager has three reset categories that are mutually exclusive:
- No reset has been triggered by pwrmgr.
- Low power entry reset has been triggered by pwrmgr.
- Software or peripheral reset request has been triggered by pwrmgr.
The reset categories are sent to the reset manager so that it can decide which reason to record when the processor reset is observed. Non-debug-module resets are allowed only when no resets have been triggered by pwrmgr.
Since a reset could be motivated by multiple reasons (a security escalation during low power transition for example), the reset information registers constantly record all reset causes in which it is allowed.
The only case where this is not done is POR
, where active recording is silenced until the first processor reset release.
Even though four reset causes are labeled as warm boot, their effects on the system are not identical.
- When the reset cause is
LOW_POWER_EXIT
, it means only the non-always-on domains have been reset.- Always-on domains retain their pre-low power values.
- When the reset cause is
NDM_RESET
, it means only therst_sys_n
tree has asserted for all power domains. - When the reset cause is
HW_REQ
orSW_REQ
, it means everything other than power / clock / reset managers have reset.
This behavioral difference may be important to software, as it implies the configuration of the system may need to be different.
Crash Dump Information
The reset manager manages crash dump information for software debugging across unexpected resets and watchdogs. When enabled, the latest alert information and latest cpu information are captured in always-on registers.
When the software resumes after the reset, it is then able to examine the last cpu state or the last set of alert information to understand why the system has reset.
The enable for such debug capture can be locked such that it never captures.
Alert Information
The alert information register contains the value of the alert crash dump prior to a triggered reset. Since this information differs in length between system implementation, the alert information register only displays 32-bits at a time. The ALERT_INFO_ATTR register indicates how many 32-bit data segments must be read.
To enable alert crash dump capture, set ALERT_INFO_CTRL.EN to 1. Once the system has reset, check ALERT_INFO_ATTR.CNT_AVAIL for how many reads need to be done. Set ALERT_INFO_CTRL.INDEX to the desired segment, and then read the output from ALERT_INFO.
CPU Information
The cpu information register contains the value of the cpu state prior to a triggered reset. Since this information differs in length between system implementation, the information register only displays 32-bits at a time.
For more details on the cpu dump details, please see crash dump.
The CPU_INFO_ATTR register indicates how many 32-bit data segments must be read. Software then simply needs to write in CPU_INFO_CTRL.INDEX which segment it wishes and then read out the CPU_INFO register.
Programmers Guide
Register Table
RSTMGR.ALERT_TEST @ 0x0
Alert Test Register Reset default = 0x0, mask 0x3
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | wo | 0x0 | fatal_fault | Write 1 to trigger one alert event of this kind. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1 | wo | 0x0 | fatal_cnsty_fault | Write 1 to trigger one alert event of this kind. |
RSTMGR.RESET_REQ @ 0x4
Software requested system reset. Reset default = 0x9, mask 0xf
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3:0 | rw | 0x9 | VAL | When set to kMultiBitBool4True, a reset to power manager is requested. Upon completion of reset, this bit is automatically cleared by hardware. |
RSTMGR.RESET_INFO @ 0x8
Device reset reason. Reset default = 0x1, mask 0xff
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw1c | 0x1 | POR | Indicates when a device has reset due to power up. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1 | rw1c | 0x0 | LOW_POWER_EXIT | Indicates when a device has reset due low power exit. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2 | rw1c | 0x0 | NDM_RESET | Indicates when a device has reset due to non-debug-module request. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3 | rw1c | 0x0 | SW_RESET | Indicates when a device has reset due to | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7:4 | rw1c | 0x0 | HW_REQ | Indicates when a device has reset due to a peripheral request. This can be an alert escalation, watchdog or anything else. |
RSTMGR.ALERT_REGWEN @ 0xc
Alert write enable Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN | When 1, |
RSTMGR.ALERT_INFO_CTRL @ 0x10
Alert info dump controls. Reset default = 0x0, mask 0xf1
Register enable = ALERT_REGWEN
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x0 | EN | Enable alert dump to capture new information. This field is automatically set to 0 upon system reset (even if rstmgr is not reset). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3:1 | Reserved | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7:4 | rw | 0x0 | INDEX | Controls which 32-bit value to read. |
RSTMGR.ALERT_INFO_ATTR @ 0x14
Alert info dump attributes. Reset default = 0x0, mask 0xf
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3:0 | ro | 0x0 | CNT_AVAIL | The number of 32-bit values contained in the alert info dump. |
RSTMGR.ALERT_INFO @ 0x18
Alert dump information prior to last reset.
Which value read is controlled by the Reset default = 0x0, mask 0xffffffff
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
31:0 | ro | 0x0 | VALUE | The current 32-bit value of crash dump. |
RSTMGR.CPU_REGWEN @ 0x1c
Cpu write enable Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN | When 1, |
RSTMGR.CPU_INFO_CTRL @ 0x20
Cpu info dump controls. Reset default = 0x0, mask 0xf1
Register enable = CPU_REGWEN
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x0 | EN | Enable cpu dump to capture new information. This field is automatically set to 0 upon system reset (even if rstmgr is not reset). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3:1 | Reserved | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
7:4 | rw | 0x0 | INDEX | Controls which 32-bit value to read. |
RSTMGR.CPU_INFO_ATTR @ 0x24
Cpu info dump attributes. Reset default = 0x0, mask 0xf
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3:0 | ro | 0x0 | CNT_AVAIL | The number of 32-bit values contained in the cpu info dump. |
RSTMGR.CPU_INFO @ 0x28
Cpu dump information prior to last reset.
Which value read is controlled by the Reset default = 0x0, mask 0xffffffff
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
31:0 | ro | 0x0 | VALUE | The current 32-bit value of crash dump. |
RSTMGR.SW_RST_REGWEN_0 @ 0x2c
Register write enable for software controllable resets. When a particular bit value is 0, the corresponding value in !!SW_RST_CTRL_N can no longer be changed. When a particular bit value is 1, the corresponding value in !!SW_RST_CTRL_N can be changed. Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN_0 | Register write enable for software controllable resets |
RSTMGR.SW_RST_REGWEN_1 @ 0x30
Register write enable for software controllable resets. When a particular bit value is 0, the corresponding value in !!SW_RST_CTRL_N can no longer be changed. When a particular bit value is 1, the corresponding value in !!SW_RST_CTRL_N can be changed. Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN_1 | For RSTMGR_SW_RST1 |
RSTMGR.SW_RST_REGWEN_2 @ 0x34
Register write enable for software controllable resets. When a particular bit value is 0, the corresponding value in !!SW_RST_CTRL_N can no longer be changed. When a particular bit value is 1, the corresponding value in !!SW_RST_CTRL_N can be changed. Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN_2 | For RSTMGR_SW_RST2 |
RSTMGR.SW_RST_REGWEN_3 @ 0x38
Register write enable for software controllable resets. When a particular bit value is 0, the corresponding value in !!SW_RST_CTRL_N can no longer be changed. When a particular bit value is 1, the corresponding value in !!SW_RST_CTRL_N can be changed. Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN_3 | For RSTMGR_SW_RST3 |
RSTMGR.SW_RST_REGWEN_4 @ 0x3c
Register write enable for software controllable resets. When a particular bit value is 0, the corresponding value in !!SW_RST_CTRL_N can no longer be changed. When a particular bit value is 1, the corresponding value in !!SW_RST_CTRL_N can be changed. Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN_4 | For RSTMGR_SW_RST4 |
RSTMGR.SW_RST_REGWEN_5 @ 0x40
Register write enable for software controllable resets. When a particular bit value is 0, the corresponding value in !!SW_RST_CTRL_N can no longer be changed. When a particular bit value is 1, the corresponding value in !!SW_RST_CTRL_N can be changed. Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN_5 | For RSTMGR_SW_RST5 |
RSTMGR.SW_RST_REGWEN_6 @ 0x44
Register write enable for software controllable resets. When a particular bit value is 0, the corresponding value in !!SW_RST_CTRL_N can no longer be changed. When a particular bit value is 1, the corresponding value in !!SW_RST_CTRL_N can be changed. Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN_6 | For RSTMGR_SW_RST6 |
RSTMGR.SW_RST_REGWEN_7 @ 0x48
Register write enable for software controllable resets. When a particular bit value is 0, the corresponding value in !!SW_RST_CTRL_N can no longer be changed. When a particular bit value is 1, the corresponding value in !!SW_RST_CTRL_N can be changed. Reset default = 0x1, mask 0x1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw0c | 0x1 | EN_7 | For RSTMGR_SW_RST7 |
RSTMGR.SW_RST_CTRL_N_0 @ 0x4c
Software controllable resets. When a particular bit value is 0, the corresponding module is held in reset. When a particular bit value is 1, the corresponding module is not held in reset. Reset default = 0x1, mask 0x1
Register enable = SW_RST_REGWEN_0
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x1 | VAL_0 | Software reset value |
RSTMGR.SW_RST_CTRL_N_1 @ 0x50
Software controllable resets. When a particular bit value is 0, the corresponding module is held in reset. When a particular bit value is 1, the corresponding module is not held in reset. Reset default = 0x1, mask 0x1
Register enable = SW_RST_REGWEN_1
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x1 | VAL_1 | For RSTMGR_SW_RST1 |
RSTMGR.SW_RST_CTRL_N_2 @ 0x54
Software controllable resets. When a particular bit value is 0, the corresponding module is held in reset. When a particular bit value is 1, the corresponding module is not held in reset. Reset default = 0x1, mask 0x1
Register enable = SW_RST_REGWEN_2
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x1 | VAL_2 | For RSTMGR_SW_RST2 |
RSTMGR.SW_RST_CTRL_N_3 @ 0x58
Software controllable resets. When a particular bit value is 0, the corresponding module is held in reset. When a particular bit value is 1, the corresponding module is not held in reset. Reset default = 0x1, mask 0x1
Register enable = SW_RST_REGWEN_3
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x1 | VAL_3 | For RSTMGR_SW_RST3 |
RSTMGR.SW_RST_CTRL_N_4 @ 0x5c
Software controllable resets. When a particular bit value is 0, the corresponding module is held in reset. When a particular bit value is 1, the corresponding module is not held in reset. Reset default = 0x1, mask 0x1
Register enable = SW_RST_REGWEN_4
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x1 | VAL_4 | For RSTMGR_SW_RST4 |
RSTMGR.SW_RST_CTRL_N_5 @ 0x60
Software controllable resets. When a particular bit value is 0, the corresponding module is held in reset. When a particular bit value is 1, the corresponding module is not held in reset. Reset default = 0x1, mask 0x1
Register enable = SW_RST_REGWEN_5
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x1 | VAL_5 | For RSTMGR_SW_RST5 |
RSTMGR.SW_RST_CTRL_N_6 @ 0x64
Software controllable resets. When a particular bit value is 0, the corresponding module is held in reset. When a particular bit value is 1, the corresponding module is not held in reset. Reset default = 0x1, mask 0x1
Register enable = SW_RST_REGWEN_6
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x1 | VAL_6 | For RSTMGR_SW_RST6 |
RSTMGR.SW_RST_CTRL_N_7 @ 0x68
Software controllable resets. When a particular bit value is 0, the corresponding module is held in reset. When a particular bit value is 1, the corresponding module is not held in reset. Reset default = 0x1, mask 0x1
Register enable = SW_RST_REGWEN_7
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw | 0x1 | VAL_7 | For RSTMGR_SW_RST7 |
RSTMGR.ERR_CODE @ 0x6c
A bit vector of all the errors that have occurred in reset manager Reset default = 0x0, mask 0x3
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Bits | Type | Reset | Name | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
0 | rw1c | 0x0 | REG_INTG_ERR | The register file has experienced an integrity error. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1 | rw1c | 0x0 | RESET_CONSISTENCY_ERR | A inconsistent parent / child reset was observed. |