Changes

4 bytes removed ,  10:52, 12 October 2018
no edit summary
Line 495: Line 495:  
|-
 
|-
 
| 0x30
 
| 0x30
- 0x37
+
- 0x36
 
| ds
 
| ds
 
| rw
 
| rw
Line 506: Line 506:  
   byte 5: months
 
   byte 5: months
 
   byte 6: years
 
   byte 6: years
  byte 7: leap year counter / "watch error correction" register (unused)
+
|-
 +
| 0x37
 +
| s
 +
| rw
 +
| RTC time byte 7: leap year counter / "watch error correction" register (unused in code)
 
|-
 
|-
 
| 0x38
 
| 0x38
Line 651: Line 655:  
|-
 
|-
 
| 0x60
 
| 0x60
| ds(1)
+
| ds
| ro
+
| rw
first byte is wo
   
| Looping queue register
 
| Looping queue register
 
Writing to first byte resets the queue position to the nth element
 
Writing to first byte resets the queue position to the nth element
Line 662: Line 665:  
| rw
 
| rw
 
| Writing to this register pushes values on top of register 0x60's stack. Reading from this register doesn't advance the stack.
 
| Writing to this register pushes values on top of register 0x60's stack. Reading from this register doesn't advance the stack.
The first byte is used to store flags for managing FIRM/NS state - bit0 = "WirelessDisabled", bit1 = "SoftwareClosed", bit2 = "PowerOffInitiated", bit4 = "LegacyJumpProhibited". This register survives power-off, but does not seem to be saved to non-volatile storage (does not survive battery pulls). This register doesn't seem to actually control MCU behaviour by itself, it just seems to be used for storing arbitrary data.
+
The first byte is used to store flags for managing FIRM/NS state - bit0 = "WirelessDisabled", bit1 = "SoftwareClosed", bit2 = "PowerOffInitiated", bit4 = "LegacyJumpProhibited". This register survives a power-off, but it resides in RAM, so its contents get lost on battery pulls. This register doesn't seem to actually control MCU behaviour by itself, it just seems to be used for storing arbitrary data.
 
|-
 
|-
 
| 0x62 - 0x7E
 
| 0x62 - 0x7E
Trusted
225

edits