Changes

| sd| rowo| ?2bit value, writing will mask away/"acknowledge" the event, set to 3 by mcuMainLoop on reset if reset source is Watchdog bit0: RTC clock value got reset to defaults bit1: Watchdog reset happened

| sds

| sds

| s(3)

| Danger zone - [[MCU_Services#MCU_firmware_versions|MCU unlock sequence]] is written here.

| sd

bit4: doesn't seem to do anything, but an mcu::RTC command uses thisOther bits are unused, and seem seems to do nothingsomething with the watchdogBit 4 sets a bit at a RAM address which seems to control the watcdog timer state, then this bit is immediately unmasked. This field has a bitmask of 0x0F.

| sd| ro(?)wo| ??? switches up input bits from <code>0123456--</code> to <code>12-0435-</code> then writes them to REG[0x5D] (<code>0xFFC02</code>)

| sd

bits Bits 4 and 5 have no effect on a 2DS because the backlight source is the bottom screen.The rest of the bits are masked away.

| s??| ro(?)wo| ??? Seems to be stubbed, just returns the written value from the write handler function.

| ??rw

| ssd| rorw

| dssd(0x645)| ro / rw| Empty battery pattern holder, repeats all written bytesPower LED state + some extra data

| Camera LED state, 4bits wide, 0, 3, 6-0xF = off, 1 = slowly blinking, 2 = constantly on, 4 = flash once, 5 = delay before changing to 2

| ro(wo?)| ??? The write function for this register is stubbed.

| Register-mapped MCU RESET?2 bits bit0: turns off P00 and sets it to output mode (seems to kill the entire SoC) bit1: turns on a prohibited bit in an RTC Control register and turns P12 into an output

| Unused?

| Unused???, accelometer related

| s| rw| ?|-| 0x4D| s| rw| ?|-| 0x4E

| ro(?)- | ? These registers are out of bounds (these seem to be invalid regsiters0xFFC00 and up), they don't exist, writing is no-op, reading will yield FFs.

| invalid (ro)-| These registers don't exist at all, thus writing is no-op, reading them will yield 0xFFFFs.

| invalid (ro)-| These registers don't exist at all, thus writing is no-op, reading them will yield 0xFFFFs.

NoteShared register: the letter "s" in the size field means that the given register is in a "shared register pool", meaning if you read/write with size more than 1 you can read the next `readamount-1` of shared registers. It's possible to corrupt resgister is in the shared value of a "non-shared" register by writing into a shared register with a size bigger than onepool in RAM at address <code>0xFFBA4 + registernumber</code>. Writing more than 0x100 bytes into a shared  Dynamic register will corrupt all writable : these registers, including aren't in the shared portion of pool, they just "non-sharedpretend" to be there. These registersoften don't retain their set value, change rapidly, or control various hardware.

Non-shared (dynamic) register: it's a register whose contents separate from the shared register pool. Messing with these registers will not affect the shared register pool at all.