From f594c99bbe3b37ec62ff49c864b7133a28d62e59 Mon Sep 17 00:00:00 2001 From: Reto Schneider Date: Wed, 20 Mar 2024 23:53:19 +0100 Subject: [PATCH] svd: Remove trailing whitespace Removing trailing whitespaces makes linters such as checkpatch.pl happy. This is relevant when copying those files in a repository with such linters in place. Signed-off-by: Reto Schneider --- mdk/nrf51.svd | 206 +++++++++++++++--------------- mdk/nrf52833.svd | 4 +- mdk/nrf52840.svd | 4 +- mdk/nrf5340_application.svd | 4 +- mdk/nrf54h20_application.svd | 108 ++++++++-------- mdk/nrf54h20_enga_application.svd | 108 ++++++++-------- mdk/nrf54h20_enga_flpr.svd | 86 ++++++------- mdk/nrf54h20_enga_ppr.svd | 86 ++++++------- mdk/nrf54h20_enga_radiocore.svd | 108 ++++++++-------- mdk/nrf54h20_flpr.svd | 86 ++++++------- mdk/nrf54h20_ppr.svd | 86 ++++++------- mdk/nrf54h20_radiocore.svd | 108 ++++++++-------- mdk/nrf54l15_application.svd | 52 ++++---- mdk/nrf54l15_enga_application.svd | 52 ++++---- mdk/nrf54l15_enga_flpr.svd | 12 +- mdk/nrf54l15_flpr.svd | 12 +- 16 files changed, 561 insertions(+), 561 deletions(-) diff --git a/mdk/nrf51.svd b/mdk/nrf51.svd index 7d5cb6d47..76ce10a20 100644 --- a/mdk/nrf51.svd +++ b/mdk/nrf51.svd @@ -301,7 +301,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + RAMSTATUS Ram status register. @@ -378,7 +378,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + SYSTEMOFF System off register. @@ -399,7 +399,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POFCON Power failure configuration. @@ -566,7 +566,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + RAMONB Ram on/off. @@ -643,7 +643,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + DCDCEN DCDC converter enable configuration register. @@ -709,7 +709,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -1047,7 +1047,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + HFCLKSTAT High frequency clock status. @@ -1116,7 +1116,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + LFCLKSTAT Low frequency clock status. @@ -1195,7 +1195,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + LFCLKSRC Clock source for the LFCLK clock. @@ -1225,7 +1225,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + CTIV Calibration timer interval. @@ -1237,8 +1237,8 @@ POSSIBILITY OF SUCH DAMAGE.\n 0 6 - - + + XTALFREQ Crystal frequency. @@ -1263,7 +1263,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -1654,7 +1654,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Length of RAM region 0. 0x52C - + PROTENSET0 Erase and write protection bit enable set register. @@ -2494,7 +2494,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + PROTENSET1 Erase and write protection bit enable set register. @@ -3334,7 +3334,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + DISABLEINDEBUG Disable erase and write protection mechanism in debug mode. @@ -3360,7 +3360,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + PROTBLOCKSIZE Erase and write protection block size. @@ -3380,7 +3380,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -4158,7 +4158,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + RXMATCH Received address. @@ -4172,7 +4172,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + RXCRC Received CRC. @@ -4206,7 +4206,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Packet pointer. Decision point: START task. 0x504 - + FREQUENCY Frequency. @@ -4821,7 +4821,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + BCC Bit counter compare. @@ -5032,7 +5032,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + OVERRIDE0 Trim value override register 0. @@ -5110,7 +5110,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -5222,7 +5222,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Receiver timeout. 0x144 - + SHORTS Shortcuts for UART. @@ -5266,7 +5266,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + INTENSET Interrupt enable set register. @@ -5705,7 +5705,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + ENABLE Enable UART and acquire IOs. @@ -5754,7 +5754,7 @@ POSSIBILITY OF SUCH DAMAGE.\n 0x514 0xFFFFFFFF - + RXD RXD register. On read action the buffer pointer is displaced. Once read the character is consumed. If read when no character available, the UART will stop working. @@ -5782,7 +5782,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + BAUDRATE UART Baudrate. @@ -5928,7 +5928,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -5953,7 +5953,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -6231,7 +6231,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -6256,7 +6256,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -6907,7 +6907,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -6932,7 +6932,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -6960,7 +6960,7 @@ POSSIBILITY OF SUCH DAMAGE.\n 4 - + SPIS1 522 @@ -7251,7 +7251,7 @@ POSSIBILITY OF SUCH DAMAGE.\n STATUS Status from last transaction. 0x440 - + OVERREAD TX buffer overread detected, and prevented. @@ -7306,7 +7306,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + ENABLE Enable SPIS. @@ -7356,7 +7356,7 @@ POSSIBILITY OF SUCH DAMAGE.\n 0x514 0xFFFFFFFF - + RXDPTR RX data pointer. @@ -7387,7 +7387,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + TXDPTR TX data pointer. @@ -7418,7 +7418,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + CONFIG Configuration register. @@ -7477,7 +7477,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + DEF Default character. @@ -7502,7 +7502,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -7527,7 +7527,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -7929,7 +7929,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -8292,7 +8292,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -8838,7 +8838,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Capture/compare registers. 0x540 - + POWER Peripheral power control. @@ -8863,7 +8863,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -9732,7 +9732,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + PRESCALER 12-bit prescaler for COUNTER frequency (32768/(PRESCALER+1)). Must be written when RTC is STOPed. @@ -9760,7 +9760,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -9785,7 +9785,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -9903,7 +9903,7 @@ POSSIBILITY OF SUCH DAMAGE.\n read-only int32_t - + POWER Peripheral power control. @@ -10102,7 +10102,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -10127,7 +10127,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -10300,7 +10300,7 @@ POSSIBILITY OF SUCH DAMAGE.\n ECB block encrypt memory pointer. 0x504 - + POWER Peripheral power control. @@ -10325,7 +10325,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -10564,7 +10564,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + ENABLE Enable AAR. @@ -10589,7 +10589,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + NIRK Number of Identity root Keys in the IRK data structure. @@ -10603,7 +10603,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + IRKPTR Pointer to the IRK data structure. @@ -10619,7 +10619,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Pointer to a scratch data area used for temporary storage during resolution. A minimum of 3 bytes must be reserved. 0x514 - + POWER Peripheral power control. @@ -10644,7 +10644,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -10977,7 +10977,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + CNFPTR Pointer to a data structure holding AES key and NONCE vector. @@ -10998,7 +10998,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Pointer to a scratch data area used for temporary storage during resolution. A minimum of 43 bytes must be reserved. 0x514 - + POWER Peripheral power control. @@ -11023,7 +11023,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -11153,7 +11153,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + REQSTATUS Request status. @@ -11494,7 +11494,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + 8 0x04 @@ -11517,7 +11517,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -11931,7 +11931,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + SAMPLE Motion sample value. @@ -11946,7 +11946,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + REPORTPER Number of samples to generate an EVENT_REPORTRDY. @@ -12009,7 +12009,7 @@ POSSIBILITY OF SUCH DAMAGE.\n read-only int32_t - + ACCREAD Snapshot of ACC register. Value generated by the TASKS_READCLEACC task. @@ -12061,7 +12061,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + LEDPRE Time LED is switched ON before the sample. @@ -12089,7 +12089,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + ACCDBLREAD Snapshot of ACCDBL register. Value generated by the TASKS_READCLEACC task. @@ -12103,7 +12103,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -12534,7 +12534,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + ENABLE Enable the LPCOMP. @@ -12559,7 +12559,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + PSEL Input pin select. @@ -12613,7 +12613,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + REFSEL Reference select. @@ -12668,7 +12668,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + EXTREFSEL External reference select. @@ -12690,10 +12690,10 @@ POSSIBILITY OF SUCH DAMAGE.\n 1 - + - + ANADETECT Analog detect configuration. @@ -12723,7 +12723,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + POWER Peripheral power control. @@ -12748,10 +12748,10 @@ POSSIBILITY OF SUCH DAMAGE.\n - + - + SWI 522 @@ -12885,7 +12885,7 @@ POSSIBILITY OF SUCH DAMAGE.\n 0x508 ERASEPAGE - + ERASEALL Register for erasing all non-volatile user memory. @@ -12916,7 +12916,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Register for erasing a protected non-volatile memory page. 0x510 - + ERASEUICR Register for start erasing User Information Congfiguration Registers. @@ -12943,7 +12943,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + PPI 522 @@ -12979,7 +12979,7 @@ POSSIBILITY OF SUCH DAMAGE.\n write-only - + CHEN Channel enable. @@ -13460,7 +13460,7 @@ POSSIBILITY OF SUCH DAMAGE.\n 1 - + @@ -15437,7 +15437,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + @@ -15468,7 +15468,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Code memory size in pages. 0x014 - + CLENR0 Length of code region 0 in bytes. @@ -15517,7 +15517,7 @@ POSSIBILITY OF SUCH DAMAGE.\n 0x038 SIZERAMBLOCKS - + CONFIGID Configuration identifier. @@ -15543,7 +15543,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Device identifier. 0x060 - + 4 0x04 @@ -15551,7 +15551,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Encryption root. 0x080 - + 4 0x04 @@ -15559,7 +15559,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Identity root. 0x090 - + DEVICEADDRTYPE Device address type. @@ -15584,7 +15584,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + 2 0x04 @@ -15592,7 +15592,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Device address. 0x0A4 - + OVERRIDEEN Radio calibration override enable. @@ -15634,7 +15634,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + 5 0x04 @@ -15649,7 +15649,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Override values for the OVERRIDEn registers in RADIO for BLE_1Mbit mode. 0x0EC - + @@ -15675,7 +15675,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Length of code region 0. 0x000 - + RBPCONF Readback protection configuration. @@ -15717,7 +15717,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + XTALFREQ Reset value for CLOCK XTALFREQ register. @@ -15742,7 +15742,7 @@ POSSIBILITY OF SUCH DAMAGE.\n - + FWID Firmware ID. @@ -15756,13 +15756,13 @@ POSSIBILITY OF SUCH DAMAGE.\n - + BOOTLOADERADDR Bootloader start address. 0x014 - + 15 0x04 @@ -15785,7 +15785,7 @@ POSSIBILITY OF SUCH DAMAGE.\n Reserved for customer. 0x080 - + diff --git a/mdk/nrf52833.svd b/mdk/nrf52833.svd index c874b7bac..af2a051f8 100644 --- a/mdk/nrf52833.svd +++ b/mdk/nrf52833.svd @@ -26172,8 +26172,8 @@ POSSIBILITY OF SUCH DAMAGE.\n SLEEPSTATE - Reflects the sleep state during automatic collision resolution. Set to IDLE - by a GOIDLE task. Set to SLEEP_A when a valid SLEEP_REQ frame is received or by a + Reflects the sleep state during automatic collision resolution. Set to IDLE + by a GOIDLE task. Set to SLEEP_A when a valid SLEEP_REQ frame is received or by a GOSLEEP task. 0 0 diff --git a/mdk/nrf52840.svd b/mdk/nrf52840.svd index 85ce629a3..d4f6c6717 100644 --- a/mdk/nrf52840.svd +++ b/mdk/nrf52840.svd @@ -25649,8 +25649,8 @@ POSSIBILITY OF SUCH DAMAGE.\n SLEEPSTATE - Reflects the sleep state during automatic collision resolution. Set to IDLE - by a GOIDLE task. Set to SLEEP_A when a valid SLEEP_REQ frame is received or by a + Reflects the sleep state during automatic collision resolution. Set to IDLE + by a GOIDLE task. Set to SLEEP_A when a valid SLEEP_REQ frame is received or by a GOSLEEP task. 0 0 diff --git a/mdk/nrf5340_application.svd b/mdk/nrf5340_application.svd index 618cc42cd..037734711 100644 --- a/mdk/nrf5340_application.svd +++ b/mdk/nrf5340_application.svd @@ -43328,8 +43328,8 @@ POSSIBILITY OF SUCH DAMAGE. SLEEPSTATE - Reflects the sleep state during automatic collision resolution. Set to IDLE - by a GOIDLE task. Set to SLEEP_A when a valid SLEEP_REQ frame is received or by a + Reflects the sleep state during automatic collision resolution. Set to IDLE + by a GOIDLE task. Set to SLEEP_A when a valid SLEEP_REQ frame is received or by a GOSLEEP task. 0 0 diff --git a/mdk/nrf54h20_application.svd b/mdk/nrf54h20_application.svd index 8ea1b7296..71592d09c 100644 --- a/mdk/nrf54h20_application.svd +++ b/mdk/nrf54h20_application.svd @@ -55234,8 +55234,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -55287,10 +55287,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -58141,7 +58141,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -58206,8 +58206,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -58236,7 +58236,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -58355,8 +58355,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -58498,10 +58498,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -58656,7 +58656,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -60757,7 +60757,7 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -60786,7 +60786,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -60905,8 +60905,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -61048,10 +61048,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -61512,9 +61512,9 @@ POSSIBILITY OF SUCH DAMAGE. HT - Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. - When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. - The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. + Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. + When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. + The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. The maximum value that can be entered is 0b1110 and this equates to 15 transactions. 0b1111 is reserved. 8 11 @@ -62041,7 +62041,7 @@ A write outputs the value to atbytesm. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -62070,7 +62070,7 @@ A write outputs the value to atbytesm. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -62189,8 +62189,8 @@ A write outputs the value to atbytesm. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -62332,10 +62332,10 @@ A write outputs the value to atbytesm. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -63356,7 +63356,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_0 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[0] controls the selection of address range comparator pair 0. 0 0 @@ -63375,7 +63375,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_1 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[1] controls the selection of address range comparator pair 1. 1 1 @@ -63394,7 +63394,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_2 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[2] controls the selection of address range comparator pair 2. 2 2 @@ -63413,7 +63413,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_3 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[3] controls the selection of address range comparator pair 3. 3 3 @@ -63432,7 +63432,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_4 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[4] controls the selection of address range comparator pair 4. 4 4 @@ -63451,7 +63451,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_5 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[5] controls the selection of address range comparator pair 5. 5 5 @@ -63470,7 +63470,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_6 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[6] controls the selection of address range comparator pair 6. 6 6 @@ -63489,7 +63489,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_7 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[7] controls the selection of address range comparator pair 7. 7 7 @@ -73779,7 +73779,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. LOCKVTORAIRCRS - Locks both the Vector table Offset Register (VTOR) and + Locks both the Vector table Offset Register (VTOR) and Application Interrupt and Reset Control Register (AIRCR) for secure mode. 0 0 @@ -81866,7 +81866,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN.0x4 0x4 EVENTS_READY[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -81876,7 +81876,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. EVENTS_READY - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -132500,7 +132500,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN.0x8 0x4 EVENTS_READY[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -132510,7 +132510,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. EVENTS_READY - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -138881,8 +138881,8 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -138894,19 +138894,19 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54h20_enga_application.svd b/mdk/nrf54h20_enga_application.svd index 35991b643..fda802419 100644 --- a/mdk/nrf54h20_enga_application.svd +++ b/mdk/nrf54h20_enga_application.svd @@ -53604,8 +53604,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -53657,10 +53657,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -56511,7 +56511,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -56576,8 +56576,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -56606,7 +56606,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -56725,8 +56725,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -56868,10 +56868,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -57026,7 +57026,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -59127,7 +59127,7 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -59156,7 +59156,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -59275,8 +59275,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -59418,10 +59418,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -59882,9 +59882,9 @@ POSSIBILITY OF SUCH DAMAGE. HT - Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. - When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. - The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. + Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. + When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. + The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. The maximum value that can be entered is 0b1110 and this equates to 15 transactions. 0b1111 is reserved. 8 11 @@ -60411,7 +60411,7 @@ A write outputs the value to atbytesm. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -60440,7 +60440,7 @@ A write outputs the value to atbytesm. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -60559,8 +60559,8 @@ A write outputs the value to atbytesm. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -60702,10 +60702,10 @@ A write outputs the value to atbytesm. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -61726,7 +61726,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_0 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[0] controls the selection of address range comparator pair 0. 0 0 @@ -61745,7 +61745,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_1 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[1] controls the selection of address range comparator pair 1. 1 1 @@ -61764,7 +61764,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_2 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[2] controls the selection of address range comparator pair 2. 2 2 @@ -61783,7 +61783,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_3 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[3] controls the selection of address range comparator pair 3. 3 3 @@ -61802,7 +61802,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_4 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[4] controls the selection of address range comparator pair 4. 4 4 @@ -61821,7 +61821,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_5 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[5] controls the selection of address range comparator pair 5. 5 5 @@ -61840,7 +61840,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_6 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[6] controls the selection of address range comparator pair 6. 6 6 @@ -61859,7 +61859,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_7 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[7] controls the selection of address range comparator pair 7. 7 7 @@ -65589,7 +65589,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. LOCKVTORAIRCRS - Locks both the Vector table Offset Register (VTOR) and + Locks both the Vector table Offset Register (VTOR) and Application Interrupt and Reset Control Register (AIRCR) for secure mode. 0 0 @@ -78386,7 +78386,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN.0x4 0x4 EVENTS_ACKED[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -78396,7 +78396,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. EVENTS_ACKED - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -102944,7 +102944,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN.0x8 0x4 EVENTS_ACKED[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -102954,7 +102954,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. EVENTS_ACKED - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -109325,8 +109325,8 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -109338,19 +109338,19 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54h20_enga_flpr.svd b/mdk/nrf54h20_enga_flpr.svd index dc0413f4c..542ac989d 100644 --- a/mdk/nrf54h20_enga_flpr.svd +++ b/mdk/nrf54h20_enga_flpr.svd @@ -40263,8 +40263,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -40316,10 +40316,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -43170,7 +43170,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -43235,8 +43235,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -43265,7 +43265,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -43384,8 +43384,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -43527,10 +43527,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -43685,7 +43685,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -45786,7 +45786,7 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -45815,7 +45815,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -45934,8 +45934,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -46077,10 +46077,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -46541,9 +46541,9 @@ POSSIBILITY OF SUCH DAMAGE. HT - Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. - When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. - The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. + Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. + When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. + The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. The maximum value that can be entered is 0b1110 and this equates to 15 transactions. 0b1111 is reserved. 8 11 @@ -47070,7 +47070,7 @@ A write outputs the value to atbytesm. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -47099,7 +47099,7 @@ A write outputs the value to atbytesm. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -47218,8 +47218,8 @@ A write outputs the value to atbytesm. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -47361,10 +47361,10 @@ A write outputs the value to atbytesm. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -58991,7 +58991,7 @@ A write outputs the value to atbytesm. 0x8 0x4 EVENTS_ACKED[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -59001,7 +59001,7 @@ A write outputs the value to atbytesm. EVENTS_ACKED - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -65372,8 +65372,8 @@ A write outputs the value to atbytesm. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -65385,19 +65385,19 @@ A write outputs the value to atbytesm. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54h20_enga_ppr.svd b/mdk/nrf54h20_enga_ppr.svd index 7edeabc89..05828c62e 100644 --- a/mdk/nrf54h20_enga_ppr.svd +++ b/mdk/nrf54h20_enga_ppr.svd @@ -40263,8 +40263,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -40316,10 +40316,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -43170,7 +43170,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -43235,8 +43235,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -43265,7 +43265,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -43384,8 +43384,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -43527,10 +43527,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -43685,7 +43685,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -45786,7 +45786,7 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -45815,7 +45815,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -45934,8 +45934,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -46077,10 +46077,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -46541,9 +46541,9 @@ POSSIBILITY OF SUCH DAMAGE. HT - Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. - When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. - The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. + Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. + When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. + The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. The maximum value that can be entered is 0b1110 and this equates to 15 transactions. 0b1111 is reserved. 8 11 @@ -47070,7 +47070,7 @@ A write outputs the value to atbytesm. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -47099,7 +47099,7 @@ A write outputs the value to atbytesm. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -47218,8 +47218,8 @@ A write outputs the value to atbytesm. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -47361,10 +47361,10 @@ A write outputs the value to atbytesm. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -58863,7 +58863,7 @@ A write outputs the value to atbytesm. 0x8 0x4 EVENTS_ACKED[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -58873,7 +58873,7 @@ A write outputs the value to atbytesm. EVENTS_ACKED - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -65244,8 +65244,8 @@ A write outputs the value to atbytesm. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -65257,19 +65257,19 @@ A write outputs the value to atbytesm. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54h20_enga_radiocore.svd b/mdk/nrf54h20_enga_radiocore.svd index f62f2f907..c0e469a64 100644 --- a/mdk/nrf54h20_enga_radiocore.svd +++ b/mdk/nrf54h20_enga_radiocore.svd @@ -52634,8 +52634,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -52687,10 +52687,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -55541,7 +55541,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -55606,8 +55606,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -55636,7 +55636,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -55755,8 +55755,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -55898,10 +55898,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -56056,7 +56056,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -58157,7 +58157,7 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -58186,7 +58186,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -58305,8 +58305,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -58448,10 +58448,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -58912,9 +58912,9 @@ POSSIBILITY OF SUCH DAMAGE. HT - Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. - When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. - The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. + Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. + When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. + The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. The maximum value that can be entered is 0b1110 and this equates to 15 transactions. 0b1111 is reserved. 8 11 @@ -59441,7 +59441,7 @@ A write outputs the value to atbytesm. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -59470,7 +59470,7 @@ A write outputs the value to atbytesm. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -59589,8 +59589,8 @@ A write outputs the value to atbytesm. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -59732,10 +59732,10 @@ A write outputs the value to atbytesm. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -60756,7 +60756,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_0 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[0] controls the selection of address range comparator pair 0. 0 0 @@ -60775,7 +60775,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_1 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[1] controls the selection of address range comparator pair 1. 1 1 @@ -60794,7 +60794,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_2 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[2] controls the selection of address range comparator pair 2. 2 2 @@ -60813,7 +60813,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_3 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[3] controls the selection of address range comparator pair 3. 3 3 @@ -60832,7 +60832,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_4 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[4] controls the selection of address range comparator pair 4. 4 4 @@ -60851,7 +60851,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_5 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[5] controls the selection of address range comparator pair 5. 5 5 @@ -60870,7 +60870,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_6 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[6] controls the selection of address range comparator pair 6. 6 6 @@ -60889,7 +60889,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_7 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[7] controls the selection of address range comparator pair 7. 7 7 @@ -64619,7 +64619,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. LOCKVTORAIRCRS - Locks both the Vector table Offset Register (VTOR) and + Locks both the Vector table Offset Register (VTOR) and Application Interrupt and Reset Control Register (AIRCR) for secure mode. 0 0 @@ -97441,8 +97441,8 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -97454,19 +97454,19 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 @@ -98413,7 +98413,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN.0x8 0x4 EVENTS_ACKED[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -98423,7 +98423,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. EVENTS_ACKED - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -124571,7 +124571,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN.0x8 0x4 EVENTS_ACKED[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -124581,7 +124581,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. EVENTS_ACKED - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 diff --git a/mdk/nrf54h20_flpr.svd b/mdk/nrf54h20_flpr.svd index ef57e2efb..9e35029d1 100644 --- a/mdk/nrf54h20_flpr.svd +++ b/mdk/nrf54h20_flpr.svd @@ -40240,8 +40240,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -40293,10 +40293,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -43146,7 +43146,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -43211,8 +43211,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -43241,7 +43241,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -43360,8 +43360,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -43503,10 +43503,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -43661,7 +43661,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -45762,7 +45762,7 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -45791,7 +45791,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -45910,8 +45910,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -46053,10 +46053,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -46517,9 +46517,9 @@ POSSIBILITY OF SUCH DAMAGE. HT - Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. - When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. - The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. + Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. + When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. + The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. The maximum value that can be entered is 0b1110 and this equates to 15 transactions. 0b1111 is reserved. 8 11 @@ -47046,7 +47046,7 @@ A write outputs the value to atbytesm. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -47075,7 +47075,7 @@ A write outputs the value to atbytesm. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -47194,8 +47194,8 @@ A write outputs the value to atbytesm. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -47337,10 +47337,10 @@ A write outputs the value to atbytesm. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -84703,7 +84703,7 @@ A write outputs the value to atbytesm. 0x8 0x4 EVENTS_READY[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -84713,7 +84713,7 @@ A write outputs the value to atbytesm. EVENTS_READY - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -91061,8 +91061,8 @@ A write outputs the value to atbytesm. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -91074,19 +91074,19 @@ A write outputs the value to atbytesm. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54h20_ppr.svd b/mdk/nrf54h20_ppr.svd index 7383062f2..a25ebccb0 100644 --- a/mdk/nrf54h20_ppr.svd +++ b/mdk/nrf54h20_ppr.svd @@ -40240,8 +40240,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -40293,10 +40293,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -43146,7 +43146,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -43211,8 +43211,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -43241,7 +43241,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -43360,8 +43360,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -43503,10 +43503,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -43661,7 +43661,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -45762,7 +45762,7 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -45791,7 +45791,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -45910,8 +45910,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -46053,10 +46053,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -46517,9 +46517,9 @@ POSSIBILITY OF SUCH DAMAGE. HT - Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. - When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. - The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. + Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. + When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. + The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. The maximum value that can be entered is 0b1110 and this equates to 15 transactions. 0b1111 is reserved. 8 11 @@ -47046,7 +47046,7 @@ A write outputs the value to atbytesm. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -47075,7 +47075,7 @@ A write outputs the value to atbytesm. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -47194,8 +47194,8 @@ A write outputs the value to atbytesm. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -47337,10 +47337,10 @@ A write outputs the value to atbytesm. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -84639,7 +84639,7 @@ A write outputs the value to atbytesm. 0x8 0x4 EVENTS_READY[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -84649,7 +84649,7 @@ A write outputs the value to atbytesm. EVENTS_READY - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -90997,8 +90997,8 @@ A write outputs the value to atbytesm. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -91010,19 +91010,19 @@ A write outputs the value to atbytesm. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54h20_radiocore.svd b/mdk/nrf54h20_radiocore.svd index eb11eea6e..7f69cc5ce 100644 --- a/mdk/nrf54h20_radiocore.svd +++ b/mdk/nrf54h20_radiocore.svd @@ -53792,8 +53792,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -53845,10 +53845,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -56699,7 +56699,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -56764,8 +56764,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -56794,7 +56794,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -56913,8 +56913,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -57056,10 +57056,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -57214,7 +57214,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -59315,7 +59315,7 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -59344,7 +59344,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -59463,8 +59463,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -59606,10 +59606,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -60070,9 +60070,9 @@ POSSIBILITY OF SUCH DAMAGE. HT - Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. - When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. - The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. + Hold Time. The formatting scheme can become inefficient when fast switching occurs, and you can use this setting to minimize switching. + When a source has nothing to transmit, then another source is selected irrespective of the minimum number of transactions. + The ATB funnel holds for the minimum hold time and one additional transaction. The actual hold time is the register value plus 1. The maximum value that can be entered is 0b1110 and this equates to 15 transactions. 0b1111 is reserved. 8 11 @@ -60599,7 +60599,7 @@ A write outputs the value to atbytesm. ITCTRL - The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, + The ITCTRL register enables the component to switch from a functional mode, which is the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for the purposes of integration testing and topology detection. 0xF00 read-write @@ -60628,7 +60628,7 @@ A write outputs the value to atbytesm. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -60747,8 +60747,8 @@ A write outputs the value to atbytesm. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -60890,10 +60890,10 @@ A write outputs the value to atbytesm. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -61914,7 +61914,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_0 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[0] controls the selection of address range comparator pair 0. 0 0 @@ -61933,7 +61933,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_1 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[1] controls the selection of address range comparator pair 1. 1 1 @@ -61952,7 +61952,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_2 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[2] controls the selection of address range comparator pair 2. 2 2 @@ -61971,7 +61971,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_3 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[3] controls the selection of address range comparator pair 3. 3 3 @@ -61990,7 +61990,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_4 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[4] controls the selection of address range comparator pair 4. 4 4 @@ -62009,7 +62009,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_5 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[5] controls the selection of address range comparator pair 5. 5 5 @@ -62028,7 +62028,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_6 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[6] controls the selection of address range comparator pair 6. 6 6 @@ -62047,7 +62047,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_7 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[7] controls the selection of address range comparator pair 7. 7 7 @@ -72337,7 +72337,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. LOCKVTORAIRCRS - Locks both the Vector table Offset Register (VTOR) and + Locks both the Vector table Offset Register (VTOR) and Application Interrupt and Reset Control Register (AIRCR) for secure mode. 0 0 @@ -107271,8 +107271,8 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -107284,19 +107284,19 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 @@ -110151,7 +110151,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN.0x8 0x4 EVENTS_READY[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -110161,7 +110161,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. EVENTS_READY - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 @@ -162385,7 +162385,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN.0x8 0x4 EVENTS_READY[%s] - Description collection: Event received when hardware handshake of SEND task for IPCT + Description collection: Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0x140 @@ -162395,7 +162395,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. EVENTS_READY - Event received when hardware handshake of SEND task for IPCT + Event received when hardware handshake of SEND task for IPCT source channel n is complete and a new signal can be triggered on that channel. 0 diff --git a/mdk/nrf54l15_application.svd b/mdk/nrf54l15_application.svd index 853c0354e..a46ea7da2 100644 --- a/mdk/nrf54l15_application.svd +++ b/mdk/nrf54l15_application.svd @@ -2962,7 +2962,7 @@ POSSIBILITY OF SUCH DAMAGE. OPSIZE - Operand size (number of bytes): + Operand size (number of bytes): This register is used when the memory is accessed via AHB Master 0 12 @@ -6057,7 +6057,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -6122,8 +6122,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -6152,7 +6152,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -6271,8 +6271,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -6414,10 +6414,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -6572,7 +6572,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -7503,7 +7503,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_0 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[0] controls the selection of address range comparator pair 0. 0 0 @@ -7522,7 +7522,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_1 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[1] controls the selection of address range comparator pair 1. 1 1 @@ -7541,7 +7541,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_2 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[2] controls the selection of address range comparator pair 2. 2 2 @@ -7560,7 +7560,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_3 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[3] controls the selection of address range comparator pair 3. 3 3 @@ -7579,7 +7579,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_4 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[4] controls the selection of address range comparator pair 4. 4 4 @@ -7598,7 +7598,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_5 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[5] controls the selection of address range comparator pair 5. 5 5 @@ -7617,7 +7617,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_6 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[6] controls the selection of address range comparator pair 6. 6 6 @@ -7636,7 +7636,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_7 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[7] controls the selection of address range comparator pair 7. 7 7 @@ -11821,7 +11821,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. LOCKVTORAIRCRS - Locks both the Vector table Offset Register (VTOR) and + Locks both the Vector table Offset Register (VTOR) and Application Interrupt and Reset Control Register (AIRCR) for secure mode. 0 0 @@ -33085,8 +33085,8 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -33098,19 +33098,19 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54l15_enga_application.svd b/mdk/nrf54l15_enga_application.svd index 9d22aaaa7..46e4c5ef2 100644 --- a/mdk/nrf54l15_enga_application.svd +++ b/mdk/nrf54l15_enga_application.svd @@ -2856,7 +2856,7 @@ POSSIBILITY OF SUCH DAMAGE. OPSIZE - Operand size (number of bytes): + Operand size (number of bytes): This register is used when the memory is accessed via AHB Master 0 12 @@ -5951,7 +5951,7 @@ POSSIBILITY OF SUCH DAMAGE. ITATBCTR0 - The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. + The ITATBCTR0 register captures the values of the atvalids, afreadys, and atbytess inputs to the TPIU. To ensure the integration registers work correctly in a system, the value of atbytess is only valid when atvalids, bit[0], is HIGH. 0xEF8 read-write @@ -6016,8 +6016,8 @@ POSSIBILITY OF SUCH DAMAGE. ITCTRL - Used to enable topology detection. - This register enables the component to switch from a functional mode, the default behavior, + Used to enable topology detection. + This register enables the component to switch from a functional mode, the default behavior, to integration mode where the inputs and outputs of the component can be directly controlled for integration testing and topology solving. 0xF00 read-write @@ -6046,7 +6046,7 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMSET - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. The claim tags have no effect on the operation of the component. The CLAIMSET register sets bits in the claim tag, and determines the number of claim bits implemented. 0xFA0 read-write @@ -6165,8 +6165,8 @@ POSSIBILITY OF SUCH DAMAGE. CLAIMCLR - Software can use the claim tag to coordinate application and debugger access to trace unit functionality. - The claim tags have no effect on the operation of the component. + Software can use the claim tag to coordinate application and debugger access to trace unit functionality. + The claim tags have no effect on the operation of the component. The CLAIMCLR register sets the bits in the claim tag to 0 and determines the current value of the claim tag. 0xFA4 read-write @@ -6308,10 +6308,10 @@ POSSIBILITY OF SUCH DAMAGE. LSR - This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. - Accesses to the extended stimulus port registers are not affected by the lock mechanism. - This register must always be present although there might not be any lock access control mechanism. - The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. + This indicates the status of the lock control mechanism. This lock prevents accidental writes by code under debug. + Accesses to the extended stimulus port registers are not affected by the lock mechanism. + This register must always be present although there might not be any lock access control mechanism. + The lock mechanism, where present and locked, must block write accesses to any control register, except the Lock Access Register. For most components this covers all registers except for the Lock Access Register. 0xFB4 read-write @@ -6466,7 +6466,7 @@ POSSIBILITY OF SUCH DAMAGE. MUXNUM - Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. + Indicates the hidden level of input multiplexing. When non-zero, this value indicates the type of multiplexing on the input to the ATB. Currently only 0x00 is supported, that is, no multiplexing is present. This value helps detect the ATB structure. 0 4 @@ -7397,7 +7397,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_0 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[0] controls the selection of address range comparator pair 0. 0 0 @@ -7416,7 +7416,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_1 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[1] controls the selection of address range comparator pair 1. 1 1 @@ -7435,7 +7435,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_2 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[2] controls the selection of address range comparator pair 2. 2 2 @@ -7454,7 +7454,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_3 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[3] controls the selection of address range comparator pair 3. 3 3 @@ -7473,7 +7473,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_4 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[4] controls the selection of address range comparator pair 4. 4 4 @@ -7492,7 +7492,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_5 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[5] controls the selection of address range comparator pair 5. 5 5 @@ -7511,7 +7511,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_6 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[6] controls the selection of address range comparator pair 6. 6 6 @@ -7530,7 +7530,7 @@ generate before a trace synchronization request occurs. The number of bytes is a RANGE_7 - Address range field. Selects which address range comparator pairs are in use with branch broadcasting. + Address range field. Selects which address range comparator pairs are in use with branch broadcasting. Each field represents an address range comparator pair, so field[7] controls the selection of address range comparator pair 7. 7 7 @@ -11715,7 +11715,7 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. LOCKVTORAIRCRS - Locks both the Vector table Offset Register (VTOR) and + Locks both the Vector table Offset Register (VTOR) and Application Interrupt and Reset Control Register (AIRCR) for secure mode. 0 0 @@ -32952,8 +32952,8 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -32965,19 +32965,19 @@ unexpectedly or might not fire. Reads of the TRCRSCTLRn might return UNKNOWN. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54l15_enga_flpr.svd b/mdk/nrf54l15_enga_flpr.svd index 46ea0fa35..6ea3fa0e8 100644 --- a/mdk/nrf54l15_enga_flpr.svd +++ b/mdk/nrf54l15_enga_flpr.svd @@ -2616,7 +2616,7 @@ POSSIBILITY OF SUCH DAMAGE. OPSIZE - Operand size (number of bytes): + Operand size (number of bytes): This register is used when the memory is accessed via AHB Master 0 12 @@ -24158,8 +24158,8 @@ POSSIBILITY OF SUCH DAMAGE. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -24171,19 +24171,19 @@ POSSIBILITY OF SUCH DAMAGE. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5 diff --git a/mdk/nrf54l15_flpr.svd b/mdk/nrf54l15_flpr.svd index b7894893a..fa475d3cc 100644 --- a/mdk/nrf54l15_flpr.svd +++ b/mdk/nrf54l15_flpr.svd @@ -2722,7 +2722,7 @@ POSSIBILITY OF SUCH DAMAGE. OPSIZE - Operand size (number of bytes): + Operand size (number of bytes): This register is used when the memory is accessed via AHB Master 0 12 @@ -24291,8 +24291,8 @@ POSSIBILITY OF SUCH DAMAGE. Busy - An abstract command was executing while command, - abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read + An abstract command was executing while command, + abstractcs, or abstractauto was written, or when one of the data or progbuf registers was read or written. This status is only written if cmderr contains 0 0x1 @@ -24304,19 +24304,19 @@ POSSIBILITY OF SUCH DAMAGE. Exception - An exception occurred while executing the + An exception occurred while executing the command (e.g. while executing theProgram Buffer). 0x3 HaltResume - The abstract command couldn't execute + The abstract command couldn't execute because the hart wasn't in the required state (running/halted). or unavailable. 0x4 Bus - The abstract command failed due to abus + The abstract command failed due to abus error (e.g. alignment, access size, or timeout). 0x5