SPRUJ79 November 2024 F29H850TU
Table 5-5 lists the memory-mapped registers for the LCM_REGS registers. All register offset addresses not listed in Table 5-5 should be considered as reserved locations and the register contents should not be modified.
Offset | Acronym | Register Name | Protection |
---|---|---|---|
0h | REVISION | IP Revision tie-off value | |
8h | LCM_CONTROL | LCM Control configuration | PARITY |
20h | LCM_STATUS | LCM status register | PARITY |
28h | LCM_STATUS_CLEAR | LCM Status clear register | |
68h | PARITY_TEST | Enabling the parity test feature | |
70h | LCM_LOCK | LCM lock configuration | PARITY |
78h | LCM_COMMIT | LCM commit configuration | PARITY |
Complex bit access types are encoded to fit into small table cells. Table 5-6 shows the codes that are used for access types in this section.
Access Type | Code | Description |
---|---|---|
Read Type | ||
R | R | Read |
R-0 | R -0 | Read Returns 0s |
Write Type | ||
W | W | Write |
W1C | W 1C | Write 1 to clear |
WSonce | W Sonce | Write Set once |
Reset or Default Value | ||
-n | Value after reset or the default value | |
Register Array Variables | ||
i,j,k,l,m,n | When these variables are used in a register name, an offset, or an address, they refer to the value of a register array where the register is part of a group of repeating registers. The register groups form a hierarchical structure and the array is represented with a formula. | |
y | When this variable is used in a register name, an offset, or an address it refers to the value of a register array. |
REVISION is shown in Figure 5-3 and described in Table 5-7.
Return to the Summary Table.
IP Revision tie-off value
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
SCHEME | RESERVED | FUNC | |||||
R-1h | R-0-0h | R-0h | |||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
FUNC | |||||||
R-0h | |||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | MAJOR | ||||||
R-0h | R-0h | ||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
CUSTOM | MINOR | ||||||
R-0h | R-0h | ||||||
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-30 | SCHEME | R | 1h | This identifies the scheme revision ID register type implemented for this module Reset type: SYSRSn |
29-28 | RESERVED | R-0 | 0h | Reserved |
27-16 | FUNC | R | 0h | Functional Release Number Reflects software-compatability. If there is no software compatability, a unique func number is assigned for compatible modules, the same number is maintained. Reset type: SYSRSn |
15-11 | RESERVED | R | 0h | Reserved |
10-8 | MAJOR | R | 0h | Major Revision Number Represents major changes to the module (e.g. entirely new features are added/changed). The major revision number for this module. Reset type: SYSRSn |
7-6 | CUSTOM | R | 0h | Custom Module Number Indicates a special version of the module. May not be supported by standard software. Reset type: SYSRSn |
5-0 | MINOR | R | 0h | Minor Revision Number Represents minor changes to the module (e.g. enhancements to existing features). The minor revision number for this module. Reset type: SYSRSn |
LCM_CONTROL is shown in Figure 5-4 and described in Table 5-8.
Return to the Summary Table.
LCM Control configuration
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | CMP2_ERR_FORCE | RESERVED | CMP1_ERR_FORCE | RESERVED | STEN | ||
R-0h | R-0/W-0h | R-0h | R-0/W-0h | R-0h | R-0/W-0h | ||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R-0/W-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | CMPEN | ||||||
R-0/W-0h | R/W-0h | ||||||
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-22 | RESERVED | R | 0h | Reserved |
21 | CMP2_ERR_FORCE | R-0/W | 0h | 0: configuration is ignored 1: comparator-2 lockstep compare error is forced (i) Once the bit is configured, comprator-2 compare error output will be asserted for one cycle. This feature is used to check the error propagation path from comparator2 compare error output to the observation point defined in system control (ii) The test shall be triggered only after enabling the lockstep feature. (iii) It is not possible to execute this test with debugger connected. (iv) The test cannot be executed if there is pending functional failure or test failure (i.e. test cannot be executed when LCM_STATUS.cmp_fail = 1 or (LCM_STATUS.stpass = 0 and LCM_STATUS.stdone = 1) or (LCM_STATUS.cmp1_err_force_pass = 0 and LCM_STATUS.cmp1_err_force_done = 1) or (LCM_STATUS.cmp2_err_force_pass = 0 and LCM_STATUS.cmp2_err_force_done = 1) (v) LCM_STATUS.cmp2_err_force_done and LCM_STATUS.cmp2_err_force_pass flags need to be cleared before initiating the test a 2nd time. Reset type: SYSRSn |
20 | RESERVED | R | 0h | Reserved |
19 | CMP1_ERR_FORCE | R-0/W | 0h | 0: configuration is ignored 1: comparator-1 lockstep compare error is forced (i) Once the bit is configured, comprator-1 compare error output will be asserted for one cycle. This feature is used to check the error propagation path from comparator1 compare error output to the observation point defined in system control. (ii) The test shall be triggered only after enabling the lockstep feature. (iii) It is not possible to execute this test with debugger connected. (iv) The test cannot be executed if there is pending functional failure or test failure (i.e. test cannot be executed when LCM_STATUS.cmp_fail = 1 or (LCM_STATUS.stpass = 0 and LCM_STATUS.stdone = 1) or (LCM_STATUS.cmp1_err_force_pass = 0 and LCM_STATUS.cmp1_err_force_done = 1) or (LCM_STATUS.cmp2_err_force_pass = 0 and LCM_STATUS.cmp2_err_force_done = 1) (v) LCM_STATUS.cmp1_err_force_done and LCM_STATUS.cmp1_err_force_pass flags need to be cleared before initiating the test a 2nd time. Reset type: SYSRSn |
18-17 | RESERVED | R | 0h | Reserved |
16 | STEN | R-0/W | 0h | 0: configuration is ignored 1: self-test enabled (i) Self-test sequence will start when the bit is configured to a value of 1. The test shall be triggered only after enabling the lockstep feature. Lockstep feature shall not be disabled when the test is in progress. (ii) Once the test is initiated, both the comparators will be tested one after the other. It should be possible to execute this test with debugger connected (iii) The test can be triggered only after the previous execution of self-test is complete (i.e. ensuring by checking LCM_STATUS.stdone = 1) (iv) The test cannot be executed if there is pending functional failure or test failure (i.e. test cannot be executed when LCM_STATUS.cmp_fail = 1 or (LCM_STATUS.stpass = 0 and LCM_STATUS.stdone = 1) or (LCM_STATUS.cmp1_err_force_pass = 0 and LCM_STATUS.cmp1_err_force_done = 1) or (LCM_STATUS.cmp2_err_force_pass = 0 and LCM_STATUS.cmp2_err_force_done = 1) (v) LCM_STATUS.stdone and LCM_STATUS.stpass flags need to be cleared before initiating the test a 2nd time. (vi) Device shouldn't enter any low power modes when self-test is in progress Reset type: SYSRSn |
15-1 | RESERVED | R-0/W | 0h | Reserved |
0 | CMPEN | R/W | 0h | 0: Lockstep compare disabled 1: Lockstep compare enabled Note: (1) Mentions of 'dual module' below are only applicable to systems that support dual modules. Datasheet will explicitly state this functionality if it exists. (2) The configuration to decide whether IP is in lockstep configuration, dual module configuration or single module configuration comes from system control. (3) This bit will have impact only when the IP is configured in lockstep mode (i.e. not in single module or dual module mode) (4) Device is expected to work in either lockstep mode or dual module mode. Switching between modes is not supported except the one time switching from lockstep mode to dual-core mode. (5) User must ensure that LCM_STATUS register should not indicate a failure (i.e. cmp_fail = 1, stpass = 0, cmp1_err_force_pass = 0, cmp2_err_force_pass = 0) at the time of enabling the lockstep compare. Reset type: SYSRSn |
LCM_STATUS is shown in Figure 5-5 and described in Table 5-9.
Return to the Summary Table.
LCM status register
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | CMP2_ERR_FORCE_DONE | CMP2_ERR_FORCE_PASS | CMP1_ERR_FORCE_DONE | CMP1_ERR_FORCE_PASS | STACTIVE | STDONE | STPASS |
R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h | R-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | DBGCON | ||||||
R-0h | R-0h | ||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | CMP_FAIL | LSEN | |||||
R-0h | R-0h | R-1h | |||||
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-23 | RESERVED | R | 0h | Reserved |
22 | CMP2_ERR_FORCE_DONE | R | 0h | 0: 'comparator2 compare error forcing test' in progress or not completed 1: 'comparator2 compare error forcing test' complete Note: If the bit is set, it need to be cleared before invoking the test 2nd time. Reset type: PORESETn |
21 | CMP2_ERR_FORCE_PASS | R | 0h | 0: 'comparator2 compare error forcing test' fail 1: 'comparator2 compare error forcing test' pass (comparator2 compare error output getting asserted during test is deemed as pass) Invoking this test will trigger an NMI on a test pass. Note: If the bit is set, it need to be cleared before invoking the test 2nd time. Reset type: PORESETn |
20 | CMP1_ERR_FORCE_DONE | R | 0h | 0: 'comparator1 compare error forcing test' in progress or not completed 1: 'comparator1 compare error forcing test' complete Note: If the bit is set, it need to be cleared before invoking the test 2nd time. Reset type: PORESETn |
19 | CMP1_ERR_FORCE_PASS | R | 0h | 0: 'comparator1 compare error forcing test' fail 1: 'comparator1 compare error forcing test' pass (comparator1 compare error output getting asserted during test is deemed as pass) Invoking this test will trigger an NMI on a test pass. Note: If the bit is set, it need to be cleared before invoking the test 2nd time. Reset type: PORESETn |
18 | STACTIVE | R | 0h | 0: Self-test is not active 1: Self-test is active (in progress) The bit will be set in the next cycle of LCM_CONTROL.sten = 1 configuration and reset along with LCM_STATUS.stdone becoming '1'. Reset type: PORESETn |
17 | STDONE | R | 0h | 0: self-test in progress or not completed 1: self-test complete The bit will be zero by default and will become one once the self-test is completed. The test is deemed complete when the test sequence is complete or the test exits due to a failure. Note: If the bit is set, it need to be cleared before invoking the test 2nd time. Reset type: PORESETn |
16 | STPASS | R | 0h | 0: self-test fail 1: self-test pass The bit will be zero by default and will become one once the self-test is complete and status is pass Note: If the bit is set, it need to be cleared before invoking the self-test 2nd time. Reset type: PORESETn |
15-9 | RESERVED | R | 0h | Reserved |
8 | DBGCON | R | 0h | 0: debugger is not connected 1: debugger is connected Note: The status is latched when debugger is connected. This can be cleared only by XRSn (a) When debugger is connected, lockstep comparison of the CPU is disabled. (b) Self-test can still be performed with debugger connected. (c) Error forcing mode cannot be checked with debugger connected Reset type: XRSn |
7-2 | RESERVED | R | 0h | Reserved |
1 | CMP_FAIL | R | 0h | 0: Lockstep compare pass 1: Lockstep compare failed Note: (i) When the peripheral is configured to be in lockstep mode, the bit indicates whether lockstep comparison has failed. (i) Once the comparison is failed, Lockstep_compare_fail_status gets latched. It can be cleared only by a PORESETn or by writing to the status clear configuration. (iii) The bit will not get set during self-test mode or error forcing mode (iv) Self-test and compare error forcing check cannot be initiated when the cmp_fail flag value is 1'b1 Reset type: PORESETn |
0 | LSEN | R | 1h | 1: Peripheral is in lockstep configuration 0: peripheral is not in lockstep configuration. This configuration comes from system control. Note: lockstep_status is independent of the debugger connection. In order to check whether lockstep compare is disabled due to debugger connection, check LCM_STATUS.dbgcon Reset type: PORESETn |
LCM_STATUS_CLEAR is shown in Figure 5-6 and described in Table 5-10.
Return to the Summary Table.
LCM Status clear register
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | |||||||
R-0h | |||||||
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | CMP2_ERR_FORCE_DONE | CMP2_ERR_FORCE_PASS | CMP1_ERR_FORCE_DONE | CMP1_ERR_FORCE_PASS | RESERVED | STDONE | STPASS |
R-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0/W1C-0h | R-0h | R-0/W1C-0h | R-0/W1C-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | |||||||
R-0h | |||||||
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | CMP_FAIL | RESERVED | |||||
R-0h | R-0/W1C-0h | R-0h | |||||
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-23 | RESERVED | R | 0h | Reserved |
22 | CMP2_ERR_FORCE_DONE | R-0/W1C | 0h | 0: No impact 1: LCM_STATUS.cmp2_err_force_done is reset to zero (If hardware is trying to set the flag and software is trying to clear the same flag in the same cycle, software clear is given higher priority) Reset type: PORESETn |
21 | CMP2_ERR_FORCE_PASS | R-0/W1C | 0h | 0: No impact 1: LCM_STATUS.cmp2_err_force_pass is reset to zero (If hardware is trying to set the flag and software is trying to clear the same flag in the same cycle, software clear is given higher priority) Reset type: PORESETn |
20 | CMP1_ERR_FORCE_DONE | R-0/W1C | 0h | 0: No impact 1: LCM_STATUS.cmp1_err_force_done is reset to zero (If hardware is trying to set the flag and software is trying to clear the same flag in the same cycle, software clear is given higher priority) Reset type: PORESETn |
19 | CMP1_ERR_FORCE_PASS | R-0/W1C | 0h | 0: No impact 1: LCM_STATUS.cmp1_err_force_pass is reset to zero (If hardware is trying to set the flag and software is trying to clear the same flag in the same cycle, software clear is given higher priority) Reset type: PORESETn |
18 | RESERVED | R | 0h | Reset type: N/A |
17 | STDONE | R-0/W1C | 0h | 0: No impact 1: LCM_STATUS.stdone is reset to zero (If hardware is trying to set the flag and software is trying to clear the same flag in the same cycle, software clear is given higher priority) Reset type: PORESETn |
16 | STPASS | R-0/W1C | 0h | 0: No impact 1: LCM_STATUS.stfail is reset to zero (If hardware is trying to set the flag and software is trying to clear the same flag in the same cycle, software clear is given higher priority) Reset type: PORESETn |
15-2 | RESERVED | R | 0h | Reserved |
1 | CMP_FAIL | R-0/W1C | 0h | 0: No impact 1: LCM_STATUS.cmp_fail is reset to zero (If hardware is trying to set the flag and software is trying to clear the same flag in the same cycle, software clear is given higher priority) Reset type: PORESETn |
0 | RESERVED | R | 0h | Reserved |
PARITY_TEST is shown in Figure 5-7 and described in Table 5-11.
Return to the Summary Table.
Enabling the parity test feature
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | |||||||||||||||
R-0h | |||||||||||||||
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | TESTEN | ||||||||||||||
R-0h | R/W-0h | ||||||||||||||
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31-16 | RESERVED | R | 0h | Reserved |
15-4 | RESERVED | R | 0h | Reserved |
3-0 | TESTEN | R/W | 0h | 1010: Parity test feature is enabled All other values: Parity test feature is disabled Note: (1) When the parity test feature is enabled, acutal registers are not accessible in the memory map. Instead, the parity values (final XOR output indicating the parity error) are accessible. Parity is computed for every byte and the correponding parity error value is available at the bit-0 of every byte. Value of '1' written to the parity bit after enabling the parity test feature can be used to inject the error by inverting the stored parity value. (2) It is recommended to leave the field as 0101 or 0000 after completing the parity test. Reset type: SYSRSn |
LCM_LOCK is shown in Figure 5-8 and described in Table 5-12.
Return to the Summary Table.
LCM lock configuration
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | PARITY_TEST | RESERVED | RESERVED |
R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R/W-0h | R-0-0h | R-0-0h |
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED |
R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | LCM_STATUS_CLEAR | RESERVED | RESERVED |
R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R/W-0h | R-0-0h | R-0-0h |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | LCM_CONTROL | RESERVED | RESERVED |
R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R/W-0h | R-0-0h | R-0-0h |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | RESERVED | R-0 | 0h | Reserved |
30 | RESERVED | R-0 | 0h | Reserved |
29 | RESERVED | R-0 | 0h | Reserved |
28 | RESERVED | R-0 | 0h | Reserved |
27 | RESERVED | R-0 | 0h | Reserved |
26 | PARITY_TEST | R/W | 0h | 0: Register configuration is not locked. 1: Register configuration is locked. Reset type: SYSRSn |
25 | RESERVED | R-0 | 0h | Reserved |
24 | RESERVED | R-0 | 0h | Reserved |
23 | RESERVED | R-0 | 0h | Reserved |
22 | RESERVED | R-0 | 0h | Reserved |
21 | RESERVED | R-0 | 0h | Reserved |
20 | RESERVED | R-0 | 0h | Reserved |
19 | RESERVED | R-0 | 0h | Reserved |
18 | RESERVED | R-0 | 0h | Reserved |
17 | RESERVED | R-0 | 0h | Reserved |
16 | RESERVED | R-0 | 0h | Reserved |
15 | RESERVED | R-0 | 0h | Reserved |
14 | RESERVED | R-0 | 0h | Reserved |
13 | RESERVED | R-0 | 0h | Reserved |
12 | RESERVED | R-0 | 0h | Reserved |
11 | RESERVED | R-0 | 0h | Reserved |
10 | LCM_STATUS_CLEAR | R/W | 0h | 0: Register configuration is not locked. 1: Register configuration is locked. Reset type: SYSRSn |
9 | RESERVED | R-0 | 0h | Reserved |
8 | RESERVED | R-0 | 0h | Reserved |
7 | RESERVED | R-0 | 0h | Reserved |
6 | RESERVED | R-0 | 0h | Reserved |
5 | RESERVED | R-0 | 0h | Reserved |
4 | RESERVED | R-0 | 0h | Reserved |
3 | RESERVED | R-0 | 0h | Reserved |
2 | LCM_CONTROL | R/W | 0h | 0: Register configuration is not locked. 1: Register configuration is locked. Reset type: SYSRSn |
1 | RESERVED | R-0 | 0h | Reserved |
0 | RESERVED | R-0 | 0h | Reserved |
LCM_COMMIT is shown in Figure 5-9 and described in Table 5-13.
Return to the Summary Table.
LCM commit configuration
31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 |
RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | PARITY_TEST | RESERVED | RESERVED |
R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R/WSonce-0h | R-0-0h | R-0-0h |
23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | RESERVED |
R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h |
15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | LCM_STATUS_CLEAR | RESERVED | RESERVED |
R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R/WSonce-0h | R-0-0h | R-0-0h |
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
RESERVED | RESERVED | RESERVED | RESERVED | RESERVED | LCM_CONTROL | RESERVED | RESERVED |
R-0-0h | R-0-0h | R-0-0h | R-0-0h | R-0-0h | R/WSonce-0h | R-0-0h | R-0-0h |
Bit | Field | Type | Reset | Description |
---|---|---|---|---|
31 | RESERVED | R-0 | 0h | Reserved |
30 | RESERVED | R-0 | 0h | Reserved |
29 | RESERVED | R-0 | 0h | Reserved |
28 | RESERVED | R-0 | 0h | Reserved |
27 | RESERVED | R-0 | 0h | Reserved |
26 | PARITY_TEST | R/WSonce | 0h | 0: Register lock configuration is not committed. 1: Register lock configuration is committed. Once configuration is committed, only reset can change the configuration. Reset type: SYSRSn |
25 | RESERVED | R-0 | 0h | Reserved |
24 | RESERVED | R-0 | 0h | Reserved |
23 | RESERVED | R-0 | 0h | Reserved |
22 | RESERVED | R-0 | 0h | Reserved |
21 | RESERVED | R-0 | 0h | Reserved |
20 | RESERVED | R-0 | 0h | Reserved |
19 | RESERVED | R-0 | 0h | Reserved |
18 | RESERVED | R-0 | 0h | Reserved |
17 | RESERVED | R-0 | 0h | Reserved |
16 | RESERVED | R-0 | 0h | Reserved |
15 | RESERVED | R-0 | 0h | Reserved |
14 | RESERVED | R-0 | 0h | Reserved |
13 | RESERVED | R-0 | 0h | Reserved |
12 | RESERVED | R-0 | 0h | Reserved |
11 | RESERVED | R-0 | 0h | Reserved |
10 | LCM_STATUS_CLEAR | R/WSonce | 0h | 0: Register lock configuration is not committed. 1: Register lock configuration is committed. Once configuration is committed, only reset can change the configuration. Reset type: SYSRSn |
9 | RESERVED | R-0 | 0h | Reserved |
8 | RESERVED | R-0 | 0h | Reserved |
7 | RESERVED | R-0 | 0h | Reserved |
6 | RESERVED | R-0 | 0h | Reserved |
5 | RESERVED | R-0 | 0h | Reserved |
4 | RESERVED | R-0 | 0h | Reserved |
3 | RESERVED | R-0 | 0h | Reserved |
2 | LCM_CONTROL | R/WSonce | 0h | 0: Register lock configuration is not committed. 1: Register lock configuration is committed. Once configuration is committed, only reset can change the configuration. Reset type: SYSRSn |
1 | RESERVED | R-0 | 0h | Reserved |
0 | RESERVED | R-0 | 0h | Reserved |