3dbrew - User contributions [en]

GPIO Registers

2019-09-29T15:23:08Z

Gericom: /* RTC_CNT (0x10147100) */

= Registers =

== GPIO ==

{| class="wikitable" border="1"
! Name
! Address
! Width
! GPIO [[GPIO_Services|bitmasks]] associated with this register
|-
| GPIO_DATA0
| 0x10147000
| 2
| 0x1, 0x2, 0x4
|-
| GPIO_DATA1
| [[#0x10147010|0x10147010]]
| 4
| 0x8, 0x10
|-
| GPIO_DATA2
| 0x10147014
| 2
| 0x20
|-
| GPIO_DATA3
| 0x10147020
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| GPIO_DATA3_INTERRUPT_CLEAR
| 0x10147022
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ??
| 0x10147024
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ?
| [[#0x10147026|0x10147026]]
| 2
| ?
|-
| GPIO_DATA4
| 0x10147028
| 2
| 0x40000
|}

== Legacy RTC ==
{| class="wikitable" border="1"
! Name
! Address
! Width
! Description
|-
| [[#RTC_CNT_(0x10147100)|RTC_CNT]]
| 0x10147100
| 2
| Control register
|-
| RTC_REG_STAT1
| 0x10147110
| 1
| Rtc status register 1 (command 0). Bitswapped
|-
| RTC_REG_STAT2
| 0x10147111
| 1
| Rtc status register 2 (command 1). Bitswapped
|-
| RTC_REG_CLKADJ
| 0x10147112
| 1
| Rtc clock adjustment register (command 6). Bitswapped
|-
| RTC_REG_FREE
| 0x10147113
| 1
| The free general purpose rtc register (command 7). Bitswapped
|-
| RTC_REG_TIME1
| 0x10147120
| 4
| Byte-wise bit-swapped (bit7 is bit0, etc.) BCD RTC (byte0 = seconds, byte1 = minutes, byte2 = hours, byte3 = day of week)
|-
| RTC_REG_TIME2
| 0x10147124
| 4 (3?)
| Day, month and year all byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM1
| 0x10147130
| 4 (3?)
| Rtc alarm time register 1 (command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM2
| 0x10147134
| 4 (3?)
| Rtc alarm time register 2 (command 5). Byte-wise bit-swapped
|-
| RTC_REG_COUNT
| 0x10147140
| 4 (3?)
| Rtc dsi counter register (ex command 0). Byte-wise bit-swapped
|-
| RTC_REG_FOUT1
| 0x10147150
| 1
| Rtc dsi fout register 1 (ex command 1). Bitswapped
|-
| RTC_REG_FOUT2
| 0x10147151
| 1
| Rtc dsi fout register 2 (ex command 2). Bitswapped
|-
| RTC_REG_ALRMDAT1
| 0x10147160
| 4 (3?)
| Rtc dsi alarm date register 1 (ex command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMDAT2
| 0x10147164
| 4 (3?)
| Rtc dsi alarm date register 2 (ex command 5). Byte-wise bit-swapped
|-
|}

= Descriptions =

== 0x10147010 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 24
| Enable/disable? GPIO interrupt 0x64 (bitmask 0x8)
|-
| 25
| Enable/disable? GPIO interrupt 0x66 (bitmask 0x10)
|}

== 0x10147026 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-8
| ?
|-
| 9
| Enable/disable interrupt 0x71.
|-
| 10-15
| ?
|}

== GPIO_DATA ==

=== GPIO_DATA0 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-2
| Used for GPIO [[GPIO_Services|bitmask]] 0x7.
|-
| 1
| DS EXTKEYIN Pen down (0 = touching, 1 = not touching)
|-
| 3
| Unused by GPIO-sysmodule and TwlBg.
|-
| 4
| Only used by [[Bootloader|Boot11]].
|-
| 5-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA1 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-1
| Used for GPIO [[GPIO_Services|bitmask]] 0x18.
|-
| 2-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA2 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x20.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA3 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-11
| Used for GPIO [[GPIO_Services|bitmask]] 0x3FFC0.
|-
| 12-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA4 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x40000.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

== Legacy RTC ==
=== RTC_CNT (0x10147100) ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Latch STAT1
|-
| 1
| Latch STAT2
|-
| 2
| Latch CLKADJ
|-
| 3
| Latch FREE
|-
| 4
| Latch TIME
|-
| 5
| Latch ALRMTIM1
|-
| 6
| Latch ALRMTIM2
|-
| 7
| Latch COUNT
|-
| 8
| Latch FOUT1
|-
| 9
| Latch FOUT2
|-
| 10
| Latch ALRMDAT1
|-
| 11
| Latch ALRMDAT2
|-
| 12
| ARM7 Busy? This may be chipselect
|-
| 13
| ARM7 write command received? (writing 1 clears it seems)
|-
| 14
| ARM7 read command recieved? (writing 1 clears it seems)
|-
| 15
| DS SIO SI pin (rtc irq pin)
|}

= Default values =

After bootrom initialization, these are the values of the registers:

{| class="wikitable" border="1"
! Address
! Value
|-
| 0x10147000
| 0x0003
|-
| 0x10147010
| 0x00000002
|-
| 0x10147014
| 0x0000
|-
| 0x10147020
| 0x00000DFB
|-
| 0x10147024
| 0x00000000
|-
| 0x10147028
| 0x0000
|}

GPIO Registers

2019-09-29T15:19:06Z

Gericom: Oops

= Registers =

== GPIO ==

{| class="wikitable" border="1"
! Name
! Address
! Width
! GPIO [[GPIO_Services|bitmasks]] associated with this register
|-
| GPIO_DATA0
| 0x10147000
| 2
| 0x1, 0x2, 0x4
|-
| GPIO_DATA1
| [[#0x10147010|0x10147010]]
| 4
| 0x8, 0x10
|-
| GPIO_DATA2
| 0x10147014
| 2
| 0x20
|-
| GPIO_DATA3
| 0x10147020
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| GPIO_DATA3_INTERRUPT_CLEAR
| 0x10147022
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ??
| 0x10147024
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ?
| [[#0x10147026|0x10147026]]
| 2
| ?
|-
| GPIO_DATA4
| 0x10147028
| 2
| 0x40000
|}

== Legacy RTC ==
{| class="wikitable" border="1"
! Name
! Address
! Width
! Description
|-
| [[#RTC_CNT_(0x10147100)|RTC_CNT]]
| 0x10147100
| 2
| Control register
|-
| RTC_REG_STAT1
| 0x10147110
| 1
| Rtc status register 1 (command 0). Bitswapped
|-
| RTC_REG_STAT2
| 0x10147111
| 1
| Rtc status register 2 (command 1). Bitswapped
|-
| RTC_REG_CLKADJ
| 0x10147112
| 1
| Rtc clock adjustment register (command 6). Bitswapped
|-
| RTC_REG_FREE
| 0x10147113
| 1
| The free general purpose rtc register (command 7). Bitswapped
|-
| RTC_REG_TIME1
| 0x10147120
| 4
| Byte-wise bit-swapped (bit7 is bit0, etc.) BCD RTC (byte0 = seconds, byte1 = minutes, byte2 = hours, byte3 = day of week)
|-
| RTC_REG_TIME2
| 0x10147124
| 4 (3?)
| Day, month and year all byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM1
| 0x10147130
| 4 (3?)
| Rtc alarm time register 1 (command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM2
| 0x10147134
| 4 (3?)
| Rtc alarm time register 2 (command 5). Byte-wise bit-swapped
|-
| RTC_REG_COUNT
| 0x10147140
| 4 (3?)
| Rtc dsi counter register (ex command 0). Byte-wise bit-swapped
|-
| RTC_REG_FOUT1
| 0x10147150
| 1
| Rtc dsi fout register 1 (ex command 1). Bitswapped
|-
| RTC_REG_FOUT2
| 0x10147151
| 1
| Rtc dsi fout register 2 (ex command 2). Bitswapped
|-
| RTC_REG_ALRMDAT1
| 0x10147160
| 4 (3?)
| Rtc dsi alarm date register 1 (ex command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMDAT2
| 0x10147164
| 4 (3?)
| Rtc dsi alarm date register 2 (ex command 5). Byte-wise bit-swapped
|-
|}

= Descriptions =

== 0x10147010 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 24
| Enable/disable? GPIO interrupt 0x64 (bitmask 0x8)
|-
| 25
| Enable/disable? GPIO interrupt 0x66 (bitmask 0x10)
|}

== 0x10147026 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-8
| ?
|-
| 9
| Enable/disable interrupt 0x71.
|-
| 10-15
| ?
|}

== GPIO_DATA ==

=== GPIO_DATA0 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-2
| Used for GPIO [[GPIO_Services|bitmask]] 0x7.
|-
| 1
| DS EXTKEYIN Pen down (0 = touching, 1 = not touching)
|-
| 3
| Unused by GPIO-sysmodule and TwlBg.
|-
| 4
| Only used by [[Bootloader|Boot11]].
|-
| 5-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA1 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-1
| Used for GPIO [[GPIO_Services|bitmask]] 0x18.
|-
| 2-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA2 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x20.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA3 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-11
| Used for GPIO [[GPIO_Services|bitmask]] 0x3FFC0.
|-
| 12-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA4 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x40000.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

== Legacy RTC ==
=== RTC_CNT (0x10147100) ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Latch STAT1
|-
| 1
| Latch STAT2
|-
| 2
| Latch CLKADJ
|-
| 3
| Latch FREE
|-
| 4
| Latch TIME
|-
| 5
| Latch ALRMTIM1
|-
| 6
| Latch ALRMTIM2
|-
| 7
| Latch COUNT
|-
| 8
| Latch FOUT1
|-
| 9
| Latch FOUT2
|-
| 10
| Latch ALRMDAT1
|-
| 11
| Latch ALRMDAT2
|-
| 12
| ARM7 Busy? This may be chipselect
|-
| 13
| ARM7 read command received? (writing 1 clears it seems)
|-
| 14
| ARM7 write command recieved? (writing 1 clears it seems)
|-
| 15
| DS SIO SI pin (rtc irq pin)
|}

= Default values =

After bootrom initialization, these are the values of the registers:

{| class="wikitable" border="1"
! Address
! Value
|-
| 0x10147000
| 0x0003
|-
| 0x10147010
| 0x00000002
|-
| 0x10147014
| 0x0000
|-
| 0x10147020
| 0x00000DFB
|-
| 0x10147024
| 0x00000000
|-
| 0x10147028
| 0x0000
|}

GPIO Registers

2019-09-29T15:18:30Z

Gericom: Updated RTC_CNT information

= Registers =

== GPIO ==

{| class="wikitable" border="1"
! Name
! Address
! Width
! GPIO [[GPIO_Services|bitmasks]] associated with this register
|-
| GPIO_DATA0
| 0x10147000
| 2
| 0x1, 0x2, 0x4
|-
| GPIO_DATA1
| [[#0x10147010|0x10147010]]
| 4
| 0x8, 0x10
|-
| GPIO_DATA2
| 0x10147014
| 2
| 0x20
|-
| GPIO_DATA3
| 0x10147020
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| GPIO_DATA3_INTERRUPT_CLEAR
| 0x10147022
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ??
| 0x10147024
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ?
| [[#0x10147026|0x10147026]]
| 2
| ?
|-
| GPIO_DATA4
| 0x10147028
| 2
| 0x40000
|}

== Legacy RTC ==
{| class="wikitable" border="1"
! Name
! Address
! Width
! Description
|-
| [[#RTC_CNT|RTC_CNT]]
| 0x10147100
| 2
| Control register
|-
| RTC_REG_STAT1
| 0x10147110
| 1
| Rtc status register 1 (command 0). Bitswapped
|-
| RTC_REG_STAT2
| 0x10147111
| 1
| Rtc status register 2 (command 1). Bitswapped
|-
| RTC_REG_CLKADJ
| 0x10147112
| 1
| Rtc clock adjustment register (command 6). Bitswapped
|-
| RTC_REG_FREE
| 0x10147113
| 1
| The free general purpose rtc register (command 7). Bitswapped
|-
| RTC_REG_TIME1
| 0x10147120
| 4
| Byte-wise bit-swapped (bit7 is bit0, etc.) BCD RTC (byte0 = seconds, byte1 = minutes, byte2 = hours, byte3 = day of week)
|-
| RTC_REG_TIME2
| 0x10147124
| 4 (3?)
| Day, month and year all byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM1
| 0x10147130
| 4 (3?)
| Rtc alarm time register 1 (command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM2
| 0x10147134
| 4 (3?)
| Rtc alarm time register 2 (command 5). Byte-wise bit-swapped
|-
| RTC_REG_COUNT
| 0x10147140
| 4 (3?)
| Rtc dsi counter register (ex command 0). Byte-wise bit-swapped
|-
| RTC_REG_FOUT1
| 0x10147150
| 1
| Rtc dsi fout register 1 (ex command 1). Bitswapped
|-
| RTC_REG_FOUT2
| 0x10147151
| 1
| Rtc dsi fout register 2 (ex command 2). Bitswapped
|-
| RTC_REG_ALRMDAT1
| 0x10147160
| 4 (3?)
| Rtc dsi alarm date register 1 (ex command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMDAT2
| 0x10147164
| 4 (3?)
| Rtc dsi alarm date register 2 (ex command 5). Byte-wise bit-swapped
|-
|}

= Descriptions =

== 0x10147010 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 24
| Enable/disable? GPIO interrupt 0x64 (bitmask 0x8)
|-
| 25
| Enable/disable? GPIO interrupt 0x66 (bitmask 0x10)
|}

== 0x10147026 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-8
| ?
|-
| 9
| Enable/disable interrupt 0x71.
|-
| 10-15
| ?
|}

== GPIO_DATA ==

=== GPIO_DATA0 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-2
| Used for GPIO [[GPIO_Services|bitmask]] 0x7.
|-
| 1
| DS EXTKEYIN Pen down (0 = touching, 1 = not touching)
|-
| 3
| Unused by GPIO-sysmodule and TwlBg.
|-
| 4
| Only used by [[Bootloader|Boot11]].
|-
| 5-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA1 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-1
| Used for GPIO [[GPIO_Services|bitmask]] 0x18.
|-
| 2-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA2 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x20.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA3 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-11
| Used for GPIO [[GPIO_Services|bitmask]] 0x3FFC0.
|-
| 12-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA4 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x40000.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

== Legacy RTC ==
=== RTC_CNT (0x10147100) ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Latch STAT1
|-
| 1
| Latch STAT2
|-
| 2
| Latch CLKADJ
|-
| 3
| Latch FREE
|-
| 4
| Latch TIME
|-
| 5
| Latch ALRMTIM1
|-
| 6
| Latch ALRMTIM2
|-
| 7
| Latch COUNT
|-
| 8
| Latch FOUT1
|-
| 9
| Latch FOUT2
|-
| 10
| Latch ALRMDAT1
|-
| 11
| Latch ALRMDAT2
|-
| 12
| ARM7 Busy? This may be chipselect
|-
| 13
| ARM7 read command received? (writing 1 clears it seems)
|-
| 14
| ARM7 write command recieved? (writing 1 clears it seems)
|-
| 15
| DS SIO SI pin (rtc irq pin)
|}

= Default values =

After bootrom initialization, these are the values of the registers:

{| class="wikitable" border="1"
! Address
! Value
|-
| 0x10147000
| 0x0003
|-
| 0x10147010
| 0x00000002
|-
| 0x10147014
| 0x0000
|-
| 0x10147020
| 0x00000DFB
|-
| 0x10147024
| 0x00000000
|-
| 0x10147028
| 0x0000
|}

GPIO Registers

2019-09-21T11:25:59Z

Gericom: /* Legacy RTC */

= Registers =

== GPIO ==

{| class="wikitable" border="1"
! Name
! Address
! Width
! GPIO [[GPIO_Services|bitmasks]] associated with this register
|-
| GPIO_DATA0
| 0x10147000
| 2
| 0x1, 0x2, 0x4
|-
| GPIO_DATA1
| [[#0x10147010|0x10147010]]
| 4
| 0x8, 0x10
|-
| GPIO_DATA2
| 0x10147014
| 2
| 0x20
|-
| GPIO_DATA3
| 0x10147020
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| GPIO_DATA3_INTERRUPT_CLEAR
| 0x10147022
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ??
| 0x10147024
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ?
| [[#0x10147026|0x10147026]]
| 2
| ?
|-
| GPIO_DATA4
| 0x10147028
| 2
| 0x40000
|}

== Legacy RTC ==
{| class="wikitable" border="1"
! Name
! Address
! Width
! Description
|-
| RTC_CNT
| 0x10147100
| 2
| 0x8000 = enabled?, 0x4000 = latch, other bits are to-be-latched bits in order of the regs below, starting from bit 0. TIME1 and TIME2 are one bit (0x10) together
|-
| RTC_REG_STAT1
| 0x10147110
| 1
| Rtc status register 1 (command 0). Bitswapped
|-
| RTC_REG_STAT2
| 0x10147111
| 1
| Rtc status register 2 (command 1). Bitswapped
|-
| RTC_REG_CLKADJ
| 0x10147112
| 1
| Rtc clock adjustment register (command 6). Bitswapped
|-
| RTC_REG_FREE
| 0x10147113
| 1
| The free general purpose rtc register (command 7). Bitswapped
|-
| RTC_REG_TIME1
| 0x10147120
| 4
| Byte-wise bit-swapped (bit7 is bit0, etc.) BCD RTC (byte0 = seconds, byte1 = minutes, byte2 = hours, byte3 = day of week)
|-
| RTC_REG_TIME2
| 0x10147124
| 4 (3?)
| Day, month and year all byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM1
| 0x10147130
| 4 (3?)
| Rtc alarm time register 1 (command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM2
| 0x10147134
| 4 (3?)
| Rtc alarm time register 2 (command 5). Byte-wise bit-swapped
|-
| RTC_REG_COUNT
| 0x10147140
| 4 (3?)
| Rtc dsi counter register (ex command 0). Byte-wise bit-swapped
|-
| RTC_REG_FOUT1
| 0x10147150
| 1
| Rtc dsi fout register 1 (ex command 1). Bitswapped
|-
| RTC_REG_FOUT2
| 0x10147151
| 1
| Rtc dsi fout register 2 (ex command 2). Bitswapped
|-
| RTC_REG_ALRMDAT1
| 0x10147160
| 4 (3?)
| Rtc dsi alarm date register 1 (ex command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMDAT2
| 0x10147164
| 4 (3?)
| Rtc dsi alarm date register 2 (ex command 5). Byte-wise bit-swapped
|-
|}

= Descriptions =

== 0x10147010 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 24
| Enable/disable? GPIO interrupt 0x64 (bitmask 0x8)
|-
| 25
| Enable/disable? GPIO interrupt 0x66 (bitmask 0x10)
|}

== 0x10147026 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-8
| ?
|-
| 9
| Enable/disable interrupt 0x71.
|-
| 10-15
| ?
|}

== GPIO_DATA ==

=== GPIO_DATA0 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-2
| Used for GPIO [[GPIO_Services|bitmask]] 0x7.
|-
| 1
| DS EXTKEYIN Pen down (0 = touching, 1 = not touching)
|-
| 3
| Unused by GPIO-sysmodule and TwlBg.
|-
| 4
| Only used by [[Bootloader|Boot11]].
|-
| 5-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA1 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-1
| Used for GPIO [[GPIO_Services|bitmask]] 0x18.
|-
| 2-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA2 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x20.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA3 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-11
| Used for GPIO [[GPIO_Services|bitmask]] 0x3FFC0.
|-
| 12-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA4 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x40000.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

= Default values =

After bootrom initialization, these are the values of the registers:

{| class="wikitable" border="1"
! Address
! Value
|-
| 0x10147000
| 0x0003
|-
| 0x10147010
| 0x00000002
|-
| 0x10147014
| 0x0000
|-
| 0x10147020
| 0x00000DFB
|-
| 0x10147024
| 0x00000000
|-
| 0x10147028
| 0x0000
|}

GPIO Registers

2019-09-21T11:02:06Z

Gericom: /* Legacy RTC */

= Registers =

== GPIO ==

{| class="wikitable" border="1"
! Name
! Address
! Width
! GPIO [[GPIO_Services|bitmasks]] associated with this register
|-
| GPIO_DATA0
| 0x10147000
| 2
| 0x1, 0x2, 0x4
|-
| GPIO_DATA1
| [[#0x10147010|0x10147010]]
| 4
| 0x8, 0x10
|-
| GPIO_DATA2
| 0x10147014
| 2
| 0x20
|-
| GPIO_DATA3
| 0x10147020
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| GPIO_DATA3_INTERRUPT_CLEAR
| 0x10147022
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ??
| 0x10147024
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ?
| [[#0x10147026|0x10147026]]
| 2
| ?
|-
| GPIO_DATA4
| 0x10147028
| 2
| 0x40000
|}

== Legacy RTC ==
{| class="wikitable" border="1"
! Name
! Address
! Width
! Description
|-
| RTC_CNT
| 0x10147100
| 2
| 0x8000 = enabled?, 0x4000 = latch, other bits are to-be-latched bits in order of the regs below, starting from bit 0. TIME1 and TIME2 are one bit (0x10) together
|-
| RTC_REG_STAT1
| 0x10147110
| 1
| Rtc status register 1 (command 0). Bitswapped
|-
| RTC_REG_STAT2
| 0x10147111
| 1
| Rtc status register 2 (command 1). Bitswapped
|-
| RTC_REG_CLKADJ
| 0x10147112
| 1
| Rtc clock adjustment register (command 6). Bitswapped
|-
| RTC_REG_FREE
| 0x10147113
| 1
| The free general purpose rtc register (command 7). Bitswapped
|-
| RTC_REG_TIME1
| 0x10147120
| 4
| Byte-wise bit-swapped (bit7 is bit0, etc.) BCD RTC (byte0 = seconds, byte1 = minutes, byte2 = hours, byte3 = day of week)
|-
| RTC_REG_TIME2
| 0x10147124
| 4 (3?)
| Day, month and year all byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM1
| 0x10147130
| 4 (3?)
| Rtc alarm time register 1 (command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMTIM2
| 0x10147134
| 4 (3?)
| Rtc alarm time register 2 (command 5). Byte-wise bit-swapped
|-
| RTC_REG_COUNT
| 0x10147140
| 4 (3?)
| Rtc dsi counter register (ex command 0). Byte-wise bit-swapped
|-
| RTC_REG_FOUT1
| 0x10147150
| 1
| Rtc dsi fout register 1 (ex command 1). Bitswapped
|-
| RTC_REG_FOUT2
| 0x10147151
| 1
| Rtc dsi fout register 2 (ex command 2). Bitswapped
|-
| RTC_REG_ALRMDAT2
| 0x10147160
| 4 (3?)
| Rtc dsi alarm date register 1 (ex command 4). Byte-wise bit-swapped
|-
| RTC_REG_ALRMDAT2
| 0x10147164
| 4 (3?)
| Rtc dsi alarm date register 2 (ex command 5). Byte-wise bit-swapped
|-
|}

= Descriptions =

== 0x10147010 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 24
| Enable/disable? GPIO interrupt 0x64 (bitmask 0x8)
|-
| 25
| Enable/disable? GPIO interrupt 0x66 (bitmask 0x10)
|}

== 0x10147026 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-8
| ?
|-
| 9
| Enable/disable interrupt 0x71.
|-
| 10-15
| ?
|}

== GPIO_DATA ==

=== GPIO_DATA0 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-2
| Used for GPIO [[GPIO_Services|bitmask]] 0x7.
|-
| 1
| DS EXTKEYIN Pen down (0 = touching, 1 = not touching)
|-
| 3
| Unused by GPIO-sysmodule and TwlBg.
|-
| 4
| Only used by [[Bootloader|Boot11]].
|-
| 5-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA1 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-1
| Used for GPIO [[GPIO_Services|bitmask]] 0x18.
|-
| 2-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA2 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x20.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA3 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-11
| Used for GPIO [[GPIO_Services|bitmask]] 0x3FFC0.
|-
| 12-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA4 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x40000.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

= Default values =

After bootrom initialization, these are the values of the registers:

{| class="wikitable" border="1"
! Address
! Value
|-
| 0x10147000
| 0x0003
|-
| 0x10147010
| 0x00000002
|-
| 0x10147014
| 0x0000
|-
| 0x10147020
| 0x00000DFB
|-
| 0x10147024
| 0x00000000
|-
| 0x10147028
| 0x0000
|}

GPIO Registers

2019-09-21T10:19:46Z

Gericom: /* Legacy RTC */

= Registers =

== GPIO ==

{| class="wikitable" border="1"
! Name
! Address
! Width
! GPIO [[GPIO_Services|bitmasks]] associated with this register
|-
| GPIO_DATA0
| 0x10147000
| 2
| 0x1, 0x2, 0x4
|-
| GPIO_DATA1
| [[#0x10147010|0x10147010]]
| 4
| 0x8, 0x10
|-
| GPIO_DATA2
| 0x10147014
| 2
| 0x20
|-
| GPIO_DATA3
| 0x10147020
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| GPIO_DATA3_INTERRUPT_CLEAR
| 0x10147022
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ??
| 0x10147024
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ?
| [[#0x10147026|0x10147026]]
| 2
| ?
|-
| GPIO_DATA4
| 0x10147028
| 2
| 0x40000
|}

== Legacy RTC ==
{| class="wikitable" border="1"
! Name
! Address
! Width
! Description
|-
| RTC_CNT (?)
| 0x10147100
| 2
| ???
|-
| RTC_REG_STAT1
| 0x10147110
| 1
| Rtc status register 1 (command 0). Bitswapped
|-
| RTC_REG_STAT2
| 0x10147111
| 1
| Rtc status register 2 (command 1). Bitswapped
|-
| RTC_REG_CLKADJ
| 0x10147112
| 1
| Rtc clock adjustment register (command 6). Bitswapped
|-
| RTC_REG_FREE
| 0x10147113
| 1
| The free general purpose rtc register (command 7). Bitswapped
|-
| RTC_RAW
| 0x10147120
| 4
| Byte-wise bit-swapped (bit7 is bit0, etc.) BCD RTC (byte0 = seconds, byte1 = minutes, byte2 = hours, byte3 = day(?))
|-
| RTC_?
| 0x10147124
| 4
| RTC offset?
|-
| RTC_?
| 0x10147130
| 4
| ???
|-
| RTC_?
| 0x10147134
| 4
| ???
|-
| RTC_?
| 0x10147140
| 4
| Some sort of byte-wise bit-swapped seconds counter
|-
| RTC_REG_FOUT1
| 0x10147150
| 1
| Rtc dsi fout register 1 (ex command 1). Bitswapped
|-
| RTC_REG_FOUT2
| 0x10147151
| 1
| Rtc dsi fout register 2 (ex command 2). Bitswapped
|-
| RTC_?
| 0x10147160
| 4
| ???
|-
| RTC_?
| 0x10147164
| 4
| ???
|-
|}

= Descriptions =

== 0x10147010 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 24
| Enable/disable? GPIO interrupt 0x64 (bitmask 0x8)
|-
| 25
| Enable/disable? GPIO interrupt 0x66 (bitmask 0x10)
|}

== 0x10147026 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-8
| ?
|-
| 9
| Enable/disable interrupt 0x71.
|-
| 10-15
| ?
|}

== GPIO_DATA ==

=== GPIO_DATA0 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-2
| Used for GPIO [[GPIO_Services|bitmask]] 0x7.
|-
| 1
| DS EXTKEYIN Pen down (0 = touching, 1 = not touching)
|-
| 3
| Unused by GPIO-sysmodule and TwlBg.
|-
| 4
| Only used by [[Bootloader|Boot11]].
|-
| 5-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA1 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-1
| Used for GPIO [[GPIO_Services|bitmask]] 0x18.
|-
| 2-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA2 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x20.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA3 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-11
| Used for GPIO [[GPIO_Services|bitmask]] 0x3FFC0.
|-
| 12-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA4 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x40000.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

= Default values =

After bootrom initialization, these are the values of the registers:

{| class="wikitable" border="1"
! Address
! Value
|-
| 0x10147000
| 0x0003
|-
| 0x10147010
| 0x00000002
|-
| 0x10147014
| 0x0000
|-
| 0x10147020
| 0x00000DFB
|-
| 0x10147024
| 0x00000000
|-
| 0x10147028
| 0x0000
|}

GPIO Registers

2019-09-21T09:08:00Z

Gericom: /* Legacy RTC */

= Registers =

== GPIO ==

{| class="wikitable" border="1"
! Name
! Address
! Width
! GPIO [[GPIO_Services|bitmasks]] associated with this register
|-
| GPIO_DATA0
| 0x10147000
| 2
| 0x1, 0x2, 0x4
|-
| GPIO_DATA1
| [[#0x10147010|0x10147010]]
| 4
| 0x8, 0x10
|-
| GPIO_DATA2
| 0x10147014
| 2
| 0x20
|-
| GPIO_DATA3
| 0x10147020
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| GPIO_DATA3_INTERRUPT_CLEAR
| 0x10147022
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ??
| 0x10147024
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ?
| [[#0x10147026|0x10147026]]
| 2
| ?
|-
| GPIO_DATA4
| 0x10147028
| 2
| 0x40000
|}

== Legacy RTC ==
{| class="wikitable" border="1"
! Name
! Address
! Width
! Description
|-
| RTC_CNT (?)
| 0x10147100
| 2
| ???
|-
| RTC_REG_STAT1
| 0x10147110
| 1
| Rtc status register 1 (command 0). Bitswapped
|-
| RTC_REG_STAT2
| 0x10147111
| 1
| Rtc status register 2 (command 1). Bitswapped
|-
| RTC_REG_CLKADJ
| 0x10147112
| 1
| Rtc clock adjustment register (command 6). Bitswapped
|-
| RTC_REG_FREE
| 0x10147113
| 1
| The free general purpose rtc register (command 7). Bitswapped
|-
| RTC_RAW
| 0x10147120
| 4
| Byte-wise bit-swapped (bit7 is bit0, etc.) BCD RTC (byte0 = seconds, byte1 = minutes, byte2 = hours, byte3 = day(?))
|-
| RTC_?
| 0x10147124
| 4
| RTC offset?
|-
| RTC_?
| 0x10147130
| 4
| ???
|-
| RTC_?
| 0x10147134
| 4
| ???
|-
| RTC_?
| 0x10147140
| 4
| Some sort of byte-wise bit-swapped seconds counter
|-
| RTC_?
| 0x10147150
| 1
| ???
|-
| RTC_?
| 0x10147151
| 1
| ???
|-
| RTC_?
| 0x10147160
| 4
| ???
|-
| RTC_?
| 0x10147164
| 4
| ???
|-
|}

= Descriptions =

== 0x10147010 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 24
| Enable/disable? GPIO interrupt 0x64 (bitmask 0x8)
|-
| 25
| Enable/disable? GPIO interrupt 0x66 (bitmask 0x10)
|}

== 0x10147026 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-8
| ?
|-
| 9
| Enable/disable interrupt 0x71.
|-
| 10-15
| ?
|}

== GPIO_DATA ==

=== GPIO_DATA0 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-2
| Used for GPIO [[GPIO_Services|bitmask]] 0x7.
|-
| 1
| DS EXTKEYIN Pen down (0 = touching, 1 = not touching)
|-
| 3
| Unused by GPIO-sysmodule and TwlBg.
|-
| 4
| Only used by [[Bootloader|Boot11]].
|-
| 5-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA1 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-1
| Used for GPIO [[GPIO_Services|bitmask]] 0x18.
|-
| 2-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA2 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x20.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA3 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-11
| Used for GPIO [[GPIO_Services|bitmask]] 0x3FFC0.
|-
| 12-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA4 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x40000.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

= Default values =

After bootrom initialization, these are the values of the registers:

{| class="wikitable" border="1"
! Address
! Value
|-
| 0x10147000
| 0x0003
|-
| 0x10147010
| 0x00000002
|-
| 0x10147014
| 0x0000
|-
| 0x10147020
| 0x00000DFB
|-
| 0x10147024
| 0x00000000
|-
| 0x10147028
| 0x0000
|}

GPIO Registers

2019-09-21T08:56:49Z

Gericom: Updated some rtc regs

= Registers =

== GPIO ==

{| class="wikitable" border="1"
! Name
! Address
! Width
! GPIO [[GPIO_Services|bitmasks]] associated with this register
|-
| GPIO_DATA0
| 0x10147000
| 2
| 0x1, 0x2, 0x4
|-
| GPIO_DATA1
| [[#0x10147010|0x10147010]]
| 4
| 0x8, 0x10
|-
| GPIO_DATA2
| 0x10147014
| 2
| 0x20
|-
| GPIO_DATA3
| 0x10147020
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| GPIO_DATA3_INTERRUPT_CLEAR
| 0x10147022
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ??
| 0x10147024
| 2
| 0x40, 0x80, 0x100, 0x200, 0x400, 0x800, 0x1000, 0x2000, 0x4000, 0x8000, 0x10000, 0x20000
|-
| ?
| [[#0x10147026|0x10147026]]
| 2
| ?
|-
| GPIO_DATA4
| 0x10147028
| 2
| 0x40000
|}

== Legacy RTC ==
{| class="wikitable" border="1"
! Name
! Address
! Width
! Description
|-
| RTC_CNT (?)
| 0x10147100
| 2
| ???
|-
| RTC_REG_STAT1
| 0x10147110
| 1
| Rtc status register 1 (command 0). Bitswapped
|-
| RTC_REG_STAT2
| 0x10147111
| 1
| Rtc status register 2 (command 1). Bitswapped
|-
| RTC_REG_FREE
| 0x10147113
| 1
| The free general purpose rtc register (command 7). Bitswapped
|-
| RTC_RAW
| 0x10147120
| 4
| Byte-wise bit-swapped (bit7 is bit0, etc.) BCD RTC (byte0 = seconds, byte1 = minutes, byte2 = hours, byte3 = day(?))
|-
| RTC_?
| 0x10147124
| 4
| RTC offset?
|-
| RTC_?
| 0x10147130
| 4
| ???
|-
| RTC_?
| 0x10147134
| 4
| ???
|-
| RTC_?
| 0x10147140
| 4
| Some sort of byte-wise bit-swapped seconds counter
|-
| RTC_?
| 0x10147150
| 1
| ???
|-
| RTC_?
| 0x10147151
| 1
| ???
|-
| RTC_?
| 0x10147160
| 4
| ???
|-
| RTC_?
| 0x10147164
| 4
| ???
|-
|}

= Descriptions =

== 0x10147010 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 24
| Enable/disable? GPIO interrupt 0x64 (bitmask 0x8)
|-
| 25
| Enable/disable? GPIO interrupt 0x66 (bitmask 0x10)
|}

== 0x10147026 ==

{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-8
| ?
|-
| 9
| Enable/disable interrupt 0x71.
|-
| 10-15
| ?
|}

== GPIO_DATA ==

=== GPIO_DATA0 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-2
| Used for GPIO [[GPIO_Services|bitmask]] 0x7.
|-
| 1
| DS EXTKEYIN Pen down (0 = touching, 1 = not touching)
|-
| 3
| Unused by GPIO-sysmodule and TwlBg.
|-
| 4
| Only used by [[Bootloader|Boot11]].
|-
| 5-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA1 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-1
| Used for GPIO [[GPIO_Services|bitmask]] 0x18.
|-
| 2-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA2 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x20.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA3 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0-11
| Used for GPIO [[GPIO_Services|bitmask]] 0x3FFC0.
|-
| 12-31
| Unused by GPIO-sysmodule and TwlBg.
|}

=== GPIO_DATA4 ===
{| class="wikitable" border="1"
! Bit
! Description
|-
| 0
| Used for GPIO [[GPIO_Services|bitmask]] 0x40000.
|-
| 1-15
| Unused by GPIO-sysmodule and TwlBg.
|}

= Default values =

After bootrom initialization, these are the values of the registers:

{| class="wikitable" border="1"
! Address
! Value
|-
| 0x10147000
| 0x0003
|-
| 0x10147010
| 0x00000002
|-
| 0x10147014
| 0x0000
|-
| 0x10147020
| 0x00000DFB
|-
| 0x10147024
| 0x00000000
|-
| 0x10147028
| 0x0000
|}

CGFX

2014-09-09T08:30:03Z

Gericom: /* DATA */

CGFX is a container format used to store graphics resources. It can contain 3D models, textures and animation data.

== CGFX ==

CGFX header :
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "CGFX"
|-
| 0x4
| 0x2
| Byte order mark: FFFE (little endian) or FEFF (big endian)
|-
| 0x6
| 0x4
| CGFX header size
|-
| 0xA
| 0x2
| ?
|-
| 0xC
| 0x4
| File size (bytes)
|-
| 0x10
| 0x4
| Number of entries
|}

A typical CGFX file contains two main entries, beginning directly after the CGFX header: DATA and IMAG.

== DATA ==

DATA contains a list of DICT references.

DATA header (for N = 0..15) :
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "DATA"
|-
| 0x4
| 0x4
| DATA Size (in bytes)
|-
| 0x8 +(N*8)
| 0x4
| Number of entries in DICT N
|-
| 0xC +(N*8)
| 0x4
| Offset (self-relative) to DICT N
|}

The DATA header contains the entry counts and offsets for each DICT entry. The number of entries can vary (probably based on the version?), but are always in the following order. Any unused entries are zeroed.

Typical entries:
{| class="wikitable"
|-
! N
! Type
|-
| 0
| Models
|-
| 1
| Textures
|-
| 2
| LUTS (Material/Color/Shader look-up tables?)
|-
| 3
| Unknown
|-
| 4
| Unknown
|-
| 5
| Cameras
|-
| 6
| Lights
|-
| 7
| Fog
|-
| 8
| Environments
|-
| 9
| Skeleton animations
|-
| 10
| Texture animations
|-
| 11
| Unknown animations
|-
| 12
| Unknown
|-
| 13
| Unknown
|-
| 14
| Unknown
|-
| 15
| Unknown
|}

== DICT ==

DICTs are generic structures used to store values (and associate them to a key ?). A DICT header is 0x1C bytes long.

DICT header :
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "DICT"
|-
| 0x4
| 0x4
| DICT size (in bytes)
|-
| 0x8
| 0x4
| Number of entries
|-
| 0xC
| 0x10
| ?
|}

DICT entry:
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| ?
|-
| 0x4
| 0x2
| ?
|-
| 0x6
| 0x2
| ?
|-
| 0x8
| 0x4
| Offset (self-relative) to symbol
|-
| 0xC
| 0x4
| Value (often offsets)
|}

== CMDL ==

CMDL is used to describe a 3D model.

CMDL Header :
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Flags (bit 7: hasSkeletonSobj)
|-
| 0x4
| 0x4
| Magic "CMDL"
|-
| 0x8
| 0x4
| ?
|-
| 0xC
| 0x4
| Offset (self-relative) to model name
|-
| 0x10
| 0x18
| ?
|-
| 0x28
| 0x4
| Number of entries in Animation Types DICT
|-
| 0x2C
| 0x4
| Offset (self-relative) to Animation Types DICT
|-
| 0x30
| 0xC
| Global scale vector (3 floats : x, y, z)
|-
| 0x3C
| 0x18
| ?
|-
| 0x54
| 0x30
| Matrix 1
|-
| 0x84
| 0x30
| Matrix 2
|-
| 0xB4
| 0x4
| Number of Vertex Info SOBJ entries
|-
| 0xB8
| 0x4
| Offset (self-relative) to Vertex Info SOBJ list
|-
| 0xBC
| 0x4
| Number of MTOB DICT entries
|-
| 0xC0
| 0x4
| Offset (self-relative) to MTOB DICT
|-
| 0xC4
| 0x4
| Number of Vertex Info SOBJ entries
|-
| 0xC8
| 0x4
| Offset (self-relative) to Vertex Info SOBJ list
|-
| 0xCC
| 0x4
| Number of Unknown DICT entries
|-
| 0xD0
| 0x4
| Offset (self-relative) to Unknown DICT
|-
| 0xD4
| 0xC
| ?
|-
| 0xE0
| 0x4
| Skeleton Info SOBJ offset (self-relative) [only present if flag bit 7 is set]
|-
| 0xB8+[0xB8]
| 0x4*N
| Vertex Info SOBJ self-relative offset list
|}

A CMDL section refers to outside data; it can not be considered separately from the rest of the CGFX file.
The second DICT in the CMDL section contains offsets to MTOB objects.

== SOBJ ==

SOBJ structures can be used to describe 3D objects that are part of the model. If such is the case then they will follow this structure :

{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x3
| Flags ?
|-
| 0x3
| 0x1
| SOBJ type ? (0x10 = model, 0x02 = skeleton)
|-
| 0x4
| 0x4
| Magic "SOBJ"
|-
| 0x44
| 0x4
| Y = Offset (self-relative) to bone correspondance array
|-
| 0x48
| 0x4
| X = Offset (relative to SOBJ magic) to SOBJ data structure (wrong ?)
|-
| 0x44+Y+0x00
| 0x4
| N = Number of bone IDs in bone correspondance array
|-
| 0x44+Y+0x14
| 0x4*N
| Bone correspondance array
|-
| X+0x18
| 0x1
| Face data format (?) : 0x1 = u8, 0x3 = u16
|-
| X+0x20
| 0x4
| Face data section size (in bytes)
|-
| X+0x24
| 0x4
| Face data section offset (self-relative)
|-
| X+0x58
| 0x4
| Vertex data section size (in bytes)
|-
| X+0x5C
| 0x4
| Vertex data section offset (self-relative)
|-
| X+0x68
| 0x1
| Vertex data format size (in bytes)
|}

{| class="wikitable"
|-
! Vertex format size
! Description
|-
| 0x14
| X (float), Y (float), Z (float), U (float), V (float)
|-
| 0x18
| X (float), Y (float), Z (float), Unk (u32?), U (float), V (float)
|-
| 0x20
| X (float), Y (float), Z (float), NX (float), NY (float), NZ (float), U (float), V (float)
|-
| 0x28v1
| X (float), Y (float), Z (float), NX (float), NY (float), NZ (float), U (float), V (float), (local) Bone IDs (4*u8), Bone weights (4*u8)
|-
| 0x28v2
| X (float), Y (float), Z (float), NX (float), NY (float), NZ (float), U (float), V (float), Unk1 (u32), (local) Bone IDs (2*u8), Bone weights (2*u8)
|}

Vertex format 0x28 (and possibly others) supports multiple bone assignment. In this case, the sum of all bone weights is 0x64.

== TXOB ==

TXOBs are contained within MTOBs. They can describe textures; if such is the case, then their structure is as follows :

{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Flags
|-
| 0x4
| 0x4
| Magic "TXOB"
|-
| 0xC
| 0x4
| Offset (self-relative) to symbol
|-
| 0x18
| 0x4
| Texture height
|-
| 0x1C
| 0x4
| Texture width
|-
| 0x28
| 0x4
| Mipmap levels
|-
| 0x34
| 0x4
| Texture format ID (see table below)
|-
| 0x3C
| 0x4
| Texture height (?)
|-
| 0x40
| 0x4
| Texture width (?)
|-
| 0x44
| 0x4
| Texture data size
|-
| 0x48
| 0x4
| Texture data offset (self-relative)
|}

{| class="wikitable"
|-
! Texture format ID
! Description
|-
|0x0
|RGBA8
|-
|0x1
|RGB8
|-
|0x2
|RGBA5551
|-
|0x3
|RGB565
|-
|0x4
|RGBA4
|-
|0x5
|LA8
|-
|0x6
|HILO8
|-
|0x7
|L8
|-
|0x8
|A8
|-
|0x9
|LA4
|-
|0xA
|L4
|-
|0xB
|A4 ?
|-
|0xC
|ETC1 (see notes below)
|-
|0xD
|ETC1A4 ?
|}

Every texture format has its texture data divided into 8x8 tiles. See [[SMDH#Icon_graphics|SMDH]] for more information.
ETC1 is a compressed texture format which compresses blocks of 4x4 pixels into u64s. These u64 are traditionally stored in big endian; however, nintendo's implementation stores them in little endian. ETC1 textures are stored in 8x8 tiles; decompressed 4x4 therefore have to be organized accordingly. See [https://gist.github.com/smealum/8897237] for implementation example.

== LUTS ==

Appears to contain color lookup tables possibly for use with shaders.

LUTS Header:
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "LUTS"
|-
| 0x4
| 0x2
| Seems to adhere to powers of 2 (width/height/flags?)
|-
| 0x6
| 0x2
| Seems to adhere to powers of 2 (width/height/flags?)
|-
| 0x8
| 0x4
| ?
|-
| 0xC
| 0x8
| all zeroes ?
|-
| 0x14
| 0x4
| ?
|-
| 0x18
| 0x4
| Offset to DICT (self-relative) ?
|}
All observed instances have an otherwise unreferenced DICT section immediately afterward (the last LUTS value being a 0x4, which may describe the relative position of that DICT), which appears to describe material specularity.

== Skeleton data ==

Skeleton data is stored in an array. Each entry is 0xE0 bytes in length and organized this way :

{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Offset (self relative) to name symbol
|-
| 0x8
| 0x4
| Joint ID
|-
| 0xC
| 0x4
| Parent joint ID
|-
| 0x10
| 0x4
| Signed offset (self-relative) to parent joint
|-
| 0x2C
| 0xC
| Angle vector (floats, x, y, z)
|-
| 0x38
| 0xC
| Position vector (floats, x, y, z)
|-
| 0x44
| 0x30
| Transformation matrix (4x3)
|-
| 0x70
| 0x30
| Identity matrix ? (4x3)
|}

Each entry stores the joint transformation data twice; once as angle/position vectors and once as a transformation matrix. Each entry also stores a second matrix which appears to always be identity. (?)

== CANM ==

CANMs are used to store skeletal animation data.

== Links ==
* Another CGFX Format Description: [http://florian.nouwt.com/wiki/index.php/CGFX_(File_Format) http://florian.nouwt.com/wiki/index.php/CGFX_(File_Format)]

CGFX

2014-09-05T18:13:51Z

Gericom:

CGFX is a container format used to store graphics resources. It can contain 3D models, textures and animation data.

== CGFX ==

CGFX header :
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "CGFX"
|-
| 0x4
| 0xC
| ?
|-
| 0x10
| 0x4
| Number of entries
|}

A typical CGFX file contains two main entries, beginning directly after the CGFX header: DATA and IMAG.

== DATA ==

DATA contains a list of DICT references.

DATA header (for N = 0..15) :
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "DATA"
|-
| 0x4
| 0x4
| DATA Size (in bytes)
|-
| 0x8 +(N*8)
| 0x4
| Number of entries in DICT N
|-
| 0xC +(N*8)
| 0x4
| Offset (self-relative) to DICT N
|}

The DATA header contains the entry counts and offsets for each DICT entry, and holds sixteen such references. Unused references are zero-padded.

== DICT ==

DICTs are generic structures used to store values (and associate them to a key ?). A DICT header is 0x1C bytes long.

DICT header :
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "DICT"
|-
| 0x4
| 0x4
| DICT size (in bytes)
|-
| 0x8
| 0x4
| Number of entries
|-
| 0xC
| 0x10
| ?
|}

DICT entry:
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| ?
|-
| 0x4
| 0x2
| ?
|-
| 0x6
| 0x2
| ?
|-
| 0x8
| 0x4
| Offset (self-relative) to symbol
|-
| 0xC
| 0x4
| Value (often offsets)
|}

== CMDL ==

CMDL is used to describe a 3D model.

CMDL Header :
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "CMDL"
|-
| 0x8
| 0x4
| CMDL section size (in bytes)
|-
| 0x24
| 0x4
| Number of entries in first DICT ?
|-
| 0x28
| 0x4
| Offset (self-relative) to first DICT
|-
| 0x2C
| 0xC
| Global scale vector (3 floats : x, y, z)
|-
| 0xB0
| 0x4
| N/2, where N is the number of entries in SOBJ list
|-
| 0xB4
| 0x4
| Offset (self-relative) to SOBJ list
|-
| 0xBC
| 0x4
| Offset (self-relative) to MTOB DICT
|-
| 0xB4+[0xB4]
| 0x4*N*2
| SOBJ list; each word is an offset (self-relative) to an SOBJ structure
|}

A CMDL section refers to outside data; it can not be considered separately from the rest of the CGFX file.
The second DICT in the CMDL section contains offsets to MTOB objects.

== SOBJ ==

SOBJ structures can be used to describe 3D objects that are part of the model. If such is the case then they will follow this structure :

{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x3
| Flags ?
|-
| 0x3
| 0x1
| SOBJ type ? (0x10 = model, 0x02 = skeleton)
|-
| 0x4
| 0x4
| Magic "SOBJ"
|-
| 0x44
| 0x4
| Y = Offset (self-relative) to bone correspondance array
|-
| 0x48
| 0x4
| X = Offset (relative to SOBJ magic) to SOBJ data structure (wrong ?)
|-
| 0x44+Y+0x00
| 0x4
| N = Number of bone IDs in bone correspondance array
|-
| 0x44+Y+0x14
| 0x4*N
| Bone correspondance array
|-
| X+0x18
| 0x1
| Face data format (?) : 0x1 = u8, 0x3 = u16
|-
| X+0x20
| 0x4
| Face data section size (in bytes)
|-
| X+0x24
| 0x4
| Face data section offset (self-relative)
|-
| X+0x58
| 0x4
| Vertex data section size (in bytes)
|-
| X+0x5C
| 0x4
| Vertex data section offset (self-relative)
|-
| X+0x68
| 0x1
| Vertex data format size (in bytes)
|}

{| class="wikitable"
|-
! Vertex format size
! Description
|-
| 0x14
| X (float), Y (float), Z (float), U (float), V (float)
|-
| 0x18
| X (float), Y (float), Z (float), Unk (u32?), U (float), V (float)
|-
| 0x20
| X (float), Y (float), Z (float), NX (float), NY (float), NZ (float), U (float), V (float)
|-
| 0x28v1
| X (float), Y (float), Z (float), NX (float), NY (float), NZ (float), U (float), V (float), (local) Bone IDs (4*u8), Bone weights (4*u8)
|-
| 0x28v2
| X (float), Y (float), Z (float), NX (float), NY (float), NZ (float), U (float), V (float), Unk1 (u32), (local) Bone IDs (2*u8), Bone weights (2*u8)
|}

Vertex format 0x28 (and possibly others) supports multiple bone assignment. In this case, the sum of all bone weights is 0x64.

== TXOB ==

TXOBs are contained within MTOBs. They can describe textures; if such is the case, then their structure is as follows :

{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "TXOB"
|-
| 0x14
| 0x4
| Texture height
|-
| 0x18
| 0x4
| Texture width
|-
| 0x30
| 0x1
| Texture format ID (see table below)
|-
| 0x38
| 0x4
| Texture height (?)
|-
| 0x3C
| 0x4
| Texture width (?)
|-
| 0x40
| 0x4
| Texture data size
|-
| 0x44
| 0x4
| Texture data offset (self-relative)
|}

{| class="wikitable"
|-
! Texture format ID
! Description
|-
|0x0
|RGBA8
|-
|0x1
|RGB8
|-
|0x2
|RGBA5551
|-
|0x3
|RGB565
|-
|0x4
|RGBA4
|-
|0x5
|LA8
|-
|0x6
|HILO8
|-
|0x7
|L8
|-
|0x8
|A8
|-
|0x9
|LA4
|-
|0xA
|L4
|-
|0xB
|A4 ?
|-
|0xC
|ETC1 (see notes below)
|-
|0xD
|ETC1A4 ?
|}

Every texture format has its texture data divided into 8x8 tiles. See [[SMDH#Icon_graphics|SMDH]] for more information.
ETC1 is a compressed texture format which compresses blocks of 4x4 pixels into u64s. These u64 are traditionally stored in big endian; however, nintendo's implementation stores them in little endian. ETC1 textures are stored in 8x8 tiles; decompressed 4x4 therefore have to be organized accordingly. See [https://gist.github.com/smealum/8897237] for implementation example.

== LUTS ==

Appears to contain color lookup tables possibly for use with shaders.

LUTS Header:
{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Magic "LUTS"
|-
| 0x4
| 0x2
| Seems to adhere to powers of 2 (width/height/flags?)
|-
| 0x6
| 0x2
| Seems to adhere to powers of 2 (width/height/flags?)
|-
| 0x8
| 0x4
| ?
|-
| 0xC
| 0x8
| all zeroes ?
|-
| 0x14
| 0x4
| ?
|-
| 0x18
| 0x4
| Offset to DICT (self-relative) ?
|}
All observed instances have an otherwise unreferenced DICT section immediately afterward (the last LUTS value being a 0x4, which may describe the relative position of that DICT), which appears to describe material specularity.

== Skeleton data ==

Skeleton data is stored in an array. Each entry is 0xE0 bytes in length and organized this way :

{| class="wikitable"
|-
! Offset
! Length
! Description
|-
| 0x0
| 0x4
| Offset (self relative) to name symbol
|-
| 0x8
| 0x4
| Joint ID
|-
| 0xC
| 0x4
| Parent joint ID
|-
| 0x10
| 0x4
| Signed offset (self-relative) to parent joint
|-
| 0x2C
| 0xC
| Angle vector (floats, x, y, z)
|-
| 0x38
| 0xC
| Position vector (floats, x, y, z)
|-
| 0x44
| 0x30
| Transformation matrix (4x3)
|-
| 0x70
| 0x30
| Identity matrix ? (4x3)
|}

Each entry stores the joint transformation data twice; once as angle/position vectors and once as a transformation matrix. Each entry also stores a second matrix which appears to always be identity. (?)

== CANM ==

CANMs are used to store skeletal animation data.

== Links ==
* Another CGFX Format Description: [http://florian.nouwt.com/wiki/index.php/CGFX_(File_Format) http://florian.nouwt.com/wiki/index.php/CGFX_(File_Format)]

SHBIN

2014-02-26T15:58:51Z

Gericom: /* Instructions */

[[Category:File formats]]
== Overview ==

The SHBIN (SHader BINary) file is used to contain compiled and linked shader programs. These can include vertex shaders (typically compiled from .vsh files) and geometry shaders (typically compiled from .gsh files, though .asm have been observed).
In commercial games/apps, SHBIN files can be found as standalone files with the extension .shbin, or contained within .bcsdr files. BCSDR files use CGFX as a container, but the underlying DVLB/DVLP/DVLE structure remains unchanged.

A SHBIN's structure starts with a header, then a DVLP, then DVLE(s).

== DVLB Header ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLB"
|-
| 0x4
| 0x4
| N = number of DVLEs in SHBIN
|-
| 0x8
| 0x4*N
| DVLE offset table; each offset is a u32 relative to the start of the DVLB section
|-
|}

The DVLP file comes directly after the header.

== DVLP ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLP"
|-
| 0x4
| 0x4
| ? (Maybe a version number?)
|-
| 0x8
| 0x4
| Offset (relative to DVLP start) to the compiled shader binary blob
|-
| 0xC
| 0x4
| Size of compiled shader binary blob, in words
|-
| 0x10
| 0x4
| Offset (relative to DVLP start) to shader instruction extension table
|-
| 0x14
| 0x4
| Number of shader instruction extension table entries (each entry is 8-byte long)
|-
| 0x18
| 0x4
| Offset (relative to DVLP start) to filename symbol table
|-
|}

== Instructions ==

=== Encoding ===
{| class="wikitable" border="1"
|-
!Name
!Description
!Encoding
|-
|DP3
|Dot product vec3*vec3
|0000 01DD DDDD ??AA AAAA BBBB BBXX XXXX
|-
|DP4
|Dot product vec4*vec4
|0000 10DD DDDD ??AA AAAA BBBB BBXX XXXX
|-
|MOV
|Move register
|0010 01DD DDDD ??AA AAAA 0000 00XX XXXX
|-
|?
|End 2
|1000 0100 0000 0000 0000 0000 0000 0000
|-
|?
|End 1
|1000 1000 0000 0000 0000 0000 0000 0000
|-
|CAL
|Call subroutine
|1001 00SS SSSS SSSS SSSS SSLL LLLL LLLL
|}

=== Fields ===
{| class="wikitable" border="1"
|-
!Name
!Description
|-
|D
|dest register
|-
|A
|opA register
|-
|B
|opB register
|-
|X
|extension id
|-
|S
|absolute offset for subroutine (in words)
|-
|L
|number of instructions to execute in subroutine
|}

== DVLE ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLE"
|-
| 0x6
| 0x1
| Shader type (0x0 = vertex shader, 0x1 = geometry shader; might contain other flags)
|-
| 0x8
| 0x4
| Program's main offset in binary blob (in words)
|-
| 0xC
| 0x4
| Program's endmain offset in binary blob (in words)
|-
| 0x18
| 0x4
| Offset (relative to DVLE start) to unk1 table
|-
| 0x1C
| 0x4
| Number of entries in unk1 table (each entry is 0x14-byte long)
|-
| 0x20
| 0x4
| Offset (relative to DVLE start) to label table
|-
| 0x24
| 0x4
| Number of entries in label table (each entry is 0x10-byte long)
|-
| 0x28
| 0x4
| Offset (relative to DVLE start) to unk2 table
|-
| 0x2C
| 0x4
| Number of entries in unk2 table (each entry is 0x8-byte long)
|-
| 0x30
| 0x4
| Offset (relative to DVLE start) to variable (?) table
|-
| 0x34
| 0x4
| Number of entries in variable table (each entry is 0x8-byte long)
|-
| 0x38
| 0x4
| Offset (relative to DVLE start) to symbol table
|-
| 0x3C
| 0x4
| Size of symbol table (in bytes)
|-
|}

Label table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Label ID
|-
| 0x4
| 0x4
| Offset (relative to shader program blob start) to label's location, in words
|-
| 0x8
| 0x4
| ?
|-
| 0xC
| 0x4
| Offset (relative to DVLE symbol table start) to label's symbol
|-
|}

Variable table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Offset (relative to DVLE symbol table start) to variable's symbol
|-
| 0x4
| 0x2
| Variable start register
|-
| 0x6
| 0x2
| Variable end register
|-
|}

Each DVLE is associated to an individual shader shader program contained in the binary blob. A single shader binary blob may contain multiple shader programs of the same kind.

The data contained in unk1 table is sent over to the GPU.

SHBIN

2014-02-26T15:57:11Z

Gericom: /* Encoding */

[[Category:File formats]]
== Overview ==

The SHBIN (SHader BINary) file is used to contain compiled and linked shader programs. These can include vertex shaders (typically compiled from .vsh files) and geometry shaders (typically compiled from .gsh files, though .asm have been observed).
In commercial games/apps, SHBIN files can be found as standalone files with the extension .shbin, or contained within .bcsdr files. BCSDR files use CGFX as a container, but the underlying DVLB/DVLP/DVLE structure remains unchanged.

A SHBIN's structure starts with a header, then a DVLP, then DVLE(s).

== DVLB Header ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLB"
|-
| 0x4
| 0x4
| N = number of DVLEs in SHBIN
|-
| 0x8
| 0x4*N
| DVLE offset table; each offset is a u32 relative to the start of the DVLB section
|-
|}

The DVLP file comes directly after the header.

== DVLP ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLP"
|-
| 0x4
| 0x4
| ? (Maybe a version number?)
|-
| 0x8
| 0x4
| Offset (relative to DVLP start) to the compiled shader binary blob
|-
| 0xC
| 0x4
| Size of compiled shader binary blob, in words
|-
| 0x10
| 0x4
| Offset (relative to DVLP start) to shader instruction extension table
|-
| 0x14
| 0x4
| Number of shader instruction extension table entries (each entry is 8-byte long)
|-
| 0x18
| 0x4
| Offset (relative to DVLP start) to filename symbol table
|-
|}

== Instructions ==

=== Encoding ===
{| class="wikitable" border="1"
|-
!Name
!Description
!Encoding
|-
|DP3
|Dot product vec3*vec3
|0000 01DD DDDD ??AA AAAA BBBB BBXX XXXX
|-
|DP4
|Dot product vec4*vec4
|0000 10DD DDDD ??AA AAAA BBBB BBXX XXXX
|-
|MOV
|Move register
|0010 01DD DDDD ??AA AAAA 0000 00XX XXXX
|-
|CAL
|Call subroutine
|1001 00SS SSSS SSSS SSSS SSLL LLLL LLLL
|-
|?
|End 2
|1000 0100 0000 0000 0000 0000 0000 0000
|-
|?
|End 1
|1000 1000 0000 0000 0000 0000 0000 0000
|}

=== Fields ===
{| class="wikitable" border="1"
|-
!Name
!Description
|-
|D
|dest register
|-
|A
|opA register
|-
|B
|opB register
|-
|X
|extension id
|-
|S
|absolute offset for subroutine (in words)
|-
|L
|number of instructions to execute in subroutine
|}

== DVLE ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLE"
|-
| 0x6
| 0x1
| Shader type (0x0 = vertex shader, 0x1 = geometry shader; might contain other flags)
|-
| 0x8
| 0x4
| Program's main offset in binary blob (in words)
|-
| 0xC
| 0x4
| Program's endmain offset in binary blob (in words)
|-
| 0x18
| 0x4
| Offset (relative to DVLE start) to unk1 table
|-
| 0x1C
| 0x4
| Number of entries in unk1 table (each entry is 0x14-byte long)
|-
| 0x20
| 0x4
| Offset (relative to DVLE start) to label table
|-
| 0x24
| 0x4
| Number of entries in label table (each entry is 0x10-byte long)
|-
| 0x28
| 0x4
| Offset (relative to DVLE start) to unk2 table
|-
| 0x2C
| 0x4
| Number of entries in unk2 table (each entry is 0x8-byte long)
|-
| 0x30
| 0x4
| Offset (relative to DVLE start) to variable (?) table
|-
| 0x34
| 0x4
| Number of entries in variable table (each entry is 0x8-byte long)
|-
| 0x38
| 0x4
| Offset (relative to DVLE start) to symbol table
|-
| 0x3C
| 0x4
| Size of symbol table (in bytes)
|-
|}

Label table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Label ID
|-
| 0x4
| 0x4
| Offset (relative to shader program blob start) to label's location, in words
|-
| 0x8
| 0x4
| ?
|-
| 0xC
| 0x4
| Offset (relative to DVLE symbol table start) to label's symbol
|-
|}

Variable table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Offset (relative to DVLE symbol table start) to variable's symbol
|-
| 0x4
| 0x2
| Variable start register
|-
| 0x6
| 0x2
| Variable end register
|-
|}

Each DVLE is associated to an individual shader shader program contained in the binary blob. A single shader binary blob may contain multiple shader programs of the same kind.

The data contained in unk1 table is sent over to the GPU.

SHBIN

2014-02-26T15:54:11Z

Gericom: Better use this for naming opcodes: http://www.renderguild.com/gpuguide.pdf

[[Category:File formats]]
== Overview ==

The SHBIN (SHader BINary) file is used to contain compiled and linked shader programs. These can include vertex shaders (typically compiled from .vsh files) and geometry shaders (typically compiled from .gsh files, though .asm have been observed).
In commercial games/apps, SHBIN files can be found as standalone files with the extension .shbin, or contained within .bcsdr files. BCSDR files use CGFX as a container, but the underlying DVLB/DVLP/DVLE structure remains unchanged.

A SHBIN's structure starts with a header, then a DVLP, then DVLE(s).

== DVLB Header ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLB"
|-
| 0x4
| 0x4
| N = number of DVLEs in SHBIN
|-
| 0x8
| 0x4*N
| DVLE offset table; each offset is a u32 relative to the start of the DVLB section
|-
|}

The DVLP file comes directly after the header.

== DVLP ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLP"
|-
| 0x4
| 0x4
| ? (Maybe a version number?)
|-
| 0x8
| 0x4
| Offset (relative to DVLP start) to the compiled shader binary blob
|-
| 0xC
| 0x4
| Size of compiled shader binary blob, in words
|-
| 0x10
| 0x4
| Offset (relative to DVLP start) to shader instruction extension table
|-
| 0x14
| 0x4
| Number of shader instruction extension table entries (each entry is 8-byte long)
|-
| 0x18
| 0x4
| Offset (relative to DVLP start) to filename symbol table
|-
|}

== Instructions ==

=== Encoding ===
{| class="wikitable" border="1"
|-
!Name
!Description
!Encoding
|-
|DP3
|Dot product vec3*vec3
|0000 01DD DDDD ??AA AAAA BBBB BBXX XXXX
|-
|DP4
|Dot product vec4*vec4
|0000 10DD DDDD ??AA AAAA BBBB BBXX XXXX
|-
|MOV
|Move register
|0010 01DD DDDD ??AA AAAA 0000 00XX XXXX
|-
|CAL
|Call subroutine
|1001 00SS SSSS SSSS SSSS SSLL LLLL LLLL
|}

=== Fields ===
{| class="wikitable" border="1"
|-
!Name
!Description
|-
|D
|dest register
|-
|A
|opA register
|-
|B
|opB register
|-
|X
|extension id
|-
|S
|absolute offset for subroutine (in words)
|-
|L
|number of instructions to execute in subroutine
|}

== DVLE ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLE"
|-
| 0x6
| 0x1
| Shader type (0x0 = vertex shader, 0x1 = geometry shader; might contain other flags)
|-
| 0x8
| 0x4
| Program's main offset in binary blob (in words)
|-
| 0xC
| 0x4
| Program's endmain offset in binary blob (in words)
|-
| 0x18
| 0x4
| Offset (relative to DVLE start) to unk1 table
|-
| 0x1C
| 0x4
| Number of entries in unk1 table (each entry is 0x14-byte long)
|-
| 0x20
| 0x4
| Offset (relative to DVLE start) to label table
|-
| 0x24
| 0x4
| Number of entries in label table (each entry is 0x10-byte long)
|-
| 0x28
| 0x4
| Offset (relative to DVLE start) to unk2 table
|-
| 0x2C
| 0x4
| Number of entries in unk2 table (each entry is 0x8-byte long)
|-
| 0x30
| 0x4
| Offset (relative to DVLE start) to variable (?) table
|-
| 0x34
| 0x4
| Number of entries in variable table (each entry is 0x8-byte long)
|-
| 0x38
| 0x4
| Offset (relative to DVLE start) to symbol table
|-
| 0x3C
| 0x4
| Size of symbol table (in bytes)
|-
|}

Label table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Label ID
|-
| 0x4
| 0x4
| Offset (relative to shader program blob start) to label's location, in words
|-
| 0x8
| 0x4
| ?
|-
| 0xC
| 0x4
| Offset (relative to DVLE symbol table start) to label's symbol
|-
|}

Variable table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Offset (relative to DVLE symbol table start) to variable's symbol
|-
| 0x4
| 0x2
| Variable start register
|-
| 0x6
| 0x2
| Variable end register
|-
|}

Each DVLE is associated to an individual shader shader program contained in the binary blob. A single shader binary blob may contain multiple shader programs of the same kind.

The data contained in unk1 table is sent over to the GPU.

SHBIN

2014-02-26T14:32:29Z

Gericom: /* DVLP */

[[Category:File formats]]
== Overview ==

The SHBIN (SHader BINary) file is used to contain compiled and linked shader programs. These can include vertex shaders (typically compiled from .vsh files) and geometry shaders (typically compiled from .gsh files, though .asm have been observed).
In commercial games/apps, SHBIN files can be found as standalone files with the extension .shbin, or contained within .bcsdr files. BCSDR files use CGFX as a container, but the underlying DVLB/DVLP/DVLE structure remains unchanged.

A SHBIN's structure starts with a header, then a DVLP, then DVLE(s).

== DVLB Header ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLB"
|-
| 0x4
| 0x4
| N = number of DVLEs in SHBIN
|-
| 0x8
| 0x4*N
| DVLE offset table; each offset is a u32 relative to the start of the DVLB section
|-
|}

The DVLP file comes directly after the header.

== DVLP ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLP"
|-
| 0x4
| 0x4
| ? (Maybe a version number?)
|-
| 0x8
| 0x4
| Offset (relative to DVLP start) to the compiled shader binary blob
|-
| 0xC
| 0x4
| Size of compiled shader binary blob, in words
|-
| 0x10
| 0x4
| Offset (relative to DVLP start) to shader instruction extension table
|-
| 0x14
| 0x4
| Number of shader instruction extension table entries (each entry is 8-byte long)
|-
| 0x18
| 0x4
| Offset (relative to DVLP start) to filename symbol table
|-
|}

=== Opcodes ===
{| class="wikitable" border="1"
|-
!Opcode
!Description
|-
|0x02
|DP4
|-
|0x13
|MOV
|}

== DVLE ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLE"
|-
| 0x6
| 0x1
| Shader type (0x0 = vertex shader, 0x1 = geometry shader; might contain other flags)
|-
| 0x8
| 0x4
| Program's main offset in binary blob (in words)
|-
| 0xC
| 0x4
| Program's endmain offset in binary blob (in words)
|-
| 0x18
| 0x4
| Offset (relative to DVLE start) to unk1 table
|-
| 0x1C
| 0x4
| Number of entries in unk1 table (each entry is 0x14-byte long)
|-
| 0x20
| 0x4
| Offset (relative to DVLE start) to label table
|-
| 0x24
| 0x4
| Number of entries in label table (each entry is 0x10-byte long)
|-
| 0x28
| 0x4
| Offset (relative to DVLE start) to unk2 table
|-
| 0x2C
| 0x4
| Number of entries in unk2 table (each entry is 0x8-byte long)
|-
| 0x30
| 0x4
| Offset (relative to DVLE start) to variable (?) table
|-
| 0x34
| 0x4
| Number of entries in variable table (each entry is 0x8-byte long)
|-
| 0x38
| 0x4
| Offset (relative to DVLE start) to symbol table
|-
| 0x3C
| 0x4
| Size of symbol table (in bytes)
|-
|}

Label table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Label ID
|-
| 0x4
| 0x4
| Offset (relative to shader program blob start) to label's location, in words
|-
| 0x8
| 0x4
| ?
|-
| 0xC
| 0x4
| Offset (relative to DVLE symbol table start) to label's symbol
|-
|}

Variable table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Offset (relative to DVLE symbol table start) to variable's symbol
|-
| 0x4
| 0x2
| Variable start register
|-
| 0x6
| 0x2
| Variable end register
|-
|}

Each DVLE is associated to an individual shader shader program contained in the binary blob. A single shader binary blob may contain multiple shader programs of the same kind.

The data contained in unk1 table is sent over to the GPU.

SHBIN

2014-02-25T14:25:31Z

Gericom: /* DVLP */

[[Category:File formats]]
== Overview ==

The SHBIN (SHader BINary) file is used to contain compiled and linked shader programs. These can include vertex shaders (typically compiled from .vsh files) and geometry shaders (typically compiled from .gsh files, though .asm have been observed).
In commercial games/apps, SHBIN files can be found as standalone files with the extension .shbin, or contained within .bcsdr files. BCSDR files use CGFX as a container, but the underlying DVLB/DVLP/DVLE structure remains unchanged.

A SHBIN's structure starts with a header, then a DVLP, then DVLE(s).

== DVLB Header ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLB"
|-
| 0x4
| 0x4
| N = number of DVLEs in SHBIN
|-
| 0x8
| 0x4*N
| DVLE offset table; each offset is a u32 relative to the start of the DVLB section
|-
|}

The DVLP file comes directly after the header.

== DVLP ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLP"
|-
| 0x4
| 0x4
| ? (Maybe a version number?)
|-
| 0x8
| 0x4
| Offset (relative to DVLP start) to shader program binary blob
|-
| 0xC
| 0x4
| Size of shader program binary blob, in words
|-
| 0x10
| 0x4
| Offset (relative to DVLP start) to shader instruction extension table
|-
| 0x14
| 0x4
| Number of shader instruction extension table entries (each entry is 8-byte long)
|-
| 0x18
| 0x4
| Offset (relative to DVLP start) to filename symbol table
|-
|}

== DVLE ==

{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Magic "DVLE"
|-
| 0x18
| 0x4
| Offset (relative to DVLE start) to unk1 table
|-
| 0x1C
| 0x4
| Number of entries in unk1 table (each entry is 0x14-byte long)
|-
| 0x20
| 0x4
| Offset (relative to DVLE start) to label table
|-
| 0x24
| 0x4
| Number of entries in label table (each entry is 0x10-byte long)
|-
| 0x28
| 0x4
| Offset (relative to DVLE start) to unk2 table
|-
| 0x2C
| 0x4
| Number of entries in unk2 table (each entry is 0x8-byte long)
|-
| 0x30
| 0x4
| Offset (relative to DVLE start) to variable (?) table
|-
| 0x34
| 0x4
| Number of entries in variable table (each entry is 0x8-byte long)
|-
| 0x38
| 0x4
| Offset (relative to DVLE start) to symbol table
|-
| 0x3C
| 0x4
| Size of symbol table (in bytes)
|-
|}

Label table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x1
| Label ID
|-
| 0x4
| 0x4
| Offset (relative to shader program blob start) to label's location, in words
|-
| 0x8
| 0x4
| ?
|-
| 0xC
| 0x4
| Offset (relative to DVLE symbol table start) to label's symbol
|-
|}

Variable table entry :
{| class="wikitable" border="1"
|-
! Offset
! Size
! Description
|-
| 0x0
| 0x4
| Offset (relative to DVLE symbol table start) to variable's symbol
|-
| 0x4
| 0x2
| Variable start register
|-
| 0x6
| 0x2
| Variable end register
|-
|}

Each DVLE is associated to an individual shader pipeline stage. Typically, the first DVLE is associated to the program's vertex shader and the second is associated to the program's geometry shader.

Language selection

2012-06-19T14:57:12Z

Gericom: Looks a little bit more nice.

{{Main page box|Language|Main Page/Language_selection}}
<div style="margin: -.3em -1em -1em -1em;">
{| width="30%" bgcolor="#fff" border="0" cellpadding="2px" cellspacing="2px" style="margin:auto;"
|- align="center" bgcolor="#e7eef6"
|- valign="top" style="background: #F5FAFF;"
</div>

[[File:FRFLAG.jpg|alt="French Flag"|link=Main_Page/Fr|50px]] [[File:JPFLAG.gif|50px| alt="Japan Flag"| link=メインページ]] [[File:USFLAG.gif|50px| alt="USA Flag"| link=Main_Page]] [[File:ESFLAG.jpg|alt="Spain Flag"|link=Main_Page/es|50px]] [[File:Drapeau chine.gif|alt="China Flag"|link=首页|50px]]


* [[Translation_Info]]

{{box-footer-empty}}

Games

2012-06-19T14:54:56Z

Gericom: Sortable

This page lists off many 3DS games and info about them, as well info about the product code and serial format. If the list is missing a game, and you have info about it, feel free to add it to the list.

Some of these games also have a savegame dumped, which can be downloaded under the Savegame column of the table. Info about the savegames' filesystem can be found on the [[Savegames]] page.

== Game list ==
Note the [DEMO] in the title name denotes that the game is a demo. Also, when adding games, please keep them in alphabetical order, keeping demos at the start of the list.

{| class="wikitable sortable" border="1"
|-
! width="35%" | Title
! width="12%" | [[Serials|Serial]]
! width="12% | Product Code
! width="5%" | EUR (P)
! width="5%" | USA (E)
! width="5%" | JPN (J)
! width="5%" | ROM Size
! width="5%" | FLASH Size
! width="5%" | FLASH ID
! width="5%" | FLASH Chip #
! width="6%" | Savegame
|-
| [DEMO] Mario Kart 7 (E3)
| ?
| CTR-P-AMKU
| No
| No
| No
| ?
| ?
| ?
| ?
| ?
|-
| [DEMO] Nintendogs+Cats (Kiosk)
| LNZ-CTR-ADAX
| CTR-P-ADAX
| Yes
| ?
| ?
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| [DEMO] Steel Diver
| LNZ-CTR-ASDX
| CTR-P-ASDX
| Yes
| No
| No
| ?
| ?
| ?
| ?
| ?
|-
| [DEMO] Super Mario 3D Land
| LNZ-CTR-AREX
| CTR-P-AREX
| Yes
| No
| ?
| ?
| ?
| ?
| ?
| ?
|-
| [DEMO] Super Mario 3D Land (E3)
| ?
| CTR-P-CTAP
| No
| No
| No
| ?
| ?
| ?
| ?
| ?
|-
| [DEMO] The Legend of Zelda: Ocarina of Time 3D
| LNZ-CTR-AQEX
| CTR-P-AQEX
| Yes
| Yes
| Yes
| ?
| ?
| ?
| ?
| ?
|-
| Asphalt 3D
| LNA-CTR-ASFX
| CTR-P-ASFX
| Yes
| Yes
| Yes
| ?
| 128kByte
| ?
| ?
| ?
|-
| Cubic Ninja
| LNA-CTR-AQNX
| CTR-P-AQNX
| Yes
| Yes
| Yes
| ?
| 128kByte
| ?
| ?
| ?
|-
| Dead or Alive - Dimensions
| LNA-CTR-ADDX
| CTR-P-ADDX
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Lego Star Wars III: The Clone Wars
| LNA-CTR-ALGX
| CTR-P-ALGX
| Yes
| Yes
| No
| 4GBit
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Mario Kart 7
| LNA-CTR-AMKX
| CTR-P-AMKX
| Yes
| Yes
| Yes
| 8GBit
| 512kByte
| ?
| ?
| ?
|-
| Nintendogs+Cats: French Bulldog & New Friends
| LNA-CTR-ADBX
| CTR-P-ADBX
| Yes
| Yes
| Yes
| ?
| 512kByte
| 0xC22213
| 25L4001
| ?
|-
| One Piece: Unlimited Cruise SP
| LNA-CTR-ALFX
| CTR-P-ALFX
| No
| No
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Pilotwings Resort
| LNA-CTR-AWAX
| CTR-P-AWAX
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Puzzle Bobble Universe
| LNA-CTR-ABBX
| CTR-P-ABBX
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| [[Raving Rabbids: Travel in Time 3D]]
| LNA-CTR-ARBX
| CTR-P-ARBX
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| [http://dl.dropbox.com/u/7830918/3DS%20Upload/decrypted.bin de]/[http://dl.dropbox.com/u/7830918/3DS%20Upload/encrypted.bin en]
|-
| Ridge Racer 3D
| LNA-CTR-ARRX
| CTR-P-ARRX
| Yes
| Yes
| Yes
| 8GBit
| 512kByte
| 0xC22213
| 25L4001
| ?
|-
| Samurai Warriors - Chronicles
| LNA-CTR-A66X
| CTR-P-A66X
| Yes
| Yes
| Yes
| ?
| 512kByte
| 0xC22213
| 25L4001
| ?
|-
| Splinter Cell 3D
| LNA-CTR-ASCX
| CTR-P-ASCX
| Yes
| Yes
| Yes
| 16Gbit
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Steel Diver
| LNA-CTR-ASDX
| CTR-P-ASDX
| Yes
| Yes
| Yes
| ?
| 512kByte
| 0xC22213
| 25L4001
| [http://dl.dropbox.com/u/32759832/3DS_saves/Steel_Diver/decrypted.sav de]/[http://dl.dropbox.com/u/32759832/3DS_saves/Steel_Diver/encrypted.sav en]
|-
| Super Mario 3D Land
| LNA-CTR-AREX
| CTR-P-AREX
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Super Monkey Ball 3D PAL
| LNA-CTR-ASMX
| CTR-P-ASMX
| Yes
| Yes
| Yes
| 2GBit
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| Super Street Fighter IV - 3D Edition
| LNA-CTR-ASSX
| CTR-P-ASSX
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
| [[The Legend of Zelda: Ocarina of Time 3D]]
| LNA-CTR-AQEX
| CTR-P-AQEX
| Yes
| Yes
| Yes
| ?
| 128kByte
| 0xC22211
| 25L1001
| [http://dl.dropbox.com/u/32759832/3DS_saves/Zelda_OoT/decrypted.sav de]/[http://dl.dropbox.com/u/32759832/3DS_saves/Zelda_OoT/encrypted.sav en]
|-
| The Sims 3
| LNA-CTR-AS3X
| CTR-P-AS3X
| Yes
| Yes
| Yes
| 4GBit
| 512kByte
| 0xC22213
| 25L4001
| ?
|-
| Tom Clancy's Ghost Recon: Shadow Wars
| LNA-CTR-AGRX
| CTR-P-ARGX
| Yes
| Yes
| Yes
| 2GBit
| 128kByte
| 0xC22211
| 25L1001
| ?
|-
|}

Elisherer's Savefile collection: [http://sherer.co.il/saves http://sherer.co.il/saves]

4.0.0-7

2012-05-04T10:33:31Z

Gericom:

'''Ability to add folders'''

Probably the biggest new feature, this lets you organise your Home Menu with folders. Here's how they work.
Select an unoccupied tile and select "Create Folder".
Tap "Edit Settings" if you want to name your folder, but remember: only the first letter shows up on its Home Menu icon. The full name appears on the top screen when you tap the folder.
Press your stylus onto an icon for a second and you'll 'pick it up'.
Drag it over to the folder and take your stylus off the screen to 'drop' the icon into the folder.
That's pretty much all there is to it. You can't put folders inside other folders, so don't try to nest them.

Video: http://youtube.com/Uo8cm9rpAA4

'''eShop Revamp'''

The other most noticeable improvement is to the eShop. Here's what's new:
New layout — now split into two rows, the bottom is for easy access to 3DS Download Software, 3DS Virtual Console, DSiWare and 3DS Demos, while the top row is for the usual curated list and 'themes'. The search bar is now at the top, too.
QR Code option — the 3DS has been able to scan QR codes for ever, but now the eShop gives you a bespoke option. Tap this in the Settings/Other menu, scan a QR code and it'll open the relevant page in the eShop.

'''Ability to patch games'''

This is a big one. Nintendo has added the ability for games — both retail and download — to receive updates in the form of patches or free add-on content. Here's what will be available in future.
Mario Kart 7 will get an update to address glitches. This update will be released in May, so don't go looking for it now.
Mighty Switch Force! will get five extra levels and a quick-retry button, all for free.

'''Supercards Block'''

Obviously, it blocks some supercards (like R4, M3, G6, RTS, DSTT, etc.)
For that you need the Firmware upgrade of your flashcard

Talk:BCWAV

2012-02-27T10:24:27Z

Gericom: Created page with "Are there some example files available?--~~~~"

Are there some example files available?--[[User:Gericom|Gericom]] 12:24, 27 February 2012 (CET)

Talk:3DSExplorer

2011-12-13T13:00:34Z

Gericom: /* *FS#.bin decrypt */

Now I figured that I didn't explain the target of this app... It's suppose to be an Explorer like program to see inside the different filesystems that the 3ds has. Now it's the ExeFS, RomFS and SAVE. As knownledge keep flowing i'll continue to develop the application. With the goal of making a full functional drag&drop file explorer for image files. --[[User:Elisherer|Elisherer]] 18:35, 15 September 2011 (CEST)

It fails showing the tmd file content. Have you finshed working on this feature?--[[User:Lazymarek9614|Lazymarek9614]] 15:49, 20 September 2011 (CEST)
:No, I don't have time to work on it..it's not interesting enough --[[User:Elisherer|Elisherer]] 15:36, 21 September 2011 (CEST)
::Yeah, the 3DS doesn't care when the tmd file was modified... it's not useful for hacking.--[[User:Lazymarek9614|Lazymarek9614]] 21:09, 21 September 2011 (CEST)

I downloaded the sources,but I can't find Save.cs and reference "System.Development". Matyapiro31
:You are right... I fixed it.. notice that the source is not the released version it has some experimental stuff in it... --[[User:Elisherer|Elisherer]] 10:53, 30 September 2011 (CEST)

Do you know [http://monodevelop.com/ Mono Develop]?
You can release it as multi-patform,such as Linux,Machitosh,etc.
:I did not know that until now. But I don't have time to make the transition. I'm happy with VS2008 and it's relatively easy to make changes and new features for the app. The source is open and you can make a linux port if you want. --[[User:Elisherer|Elisherer]] 18:16, 30 September 2011 (CEST)
:You need no change.mono can run c# program like Java VM. Matyapiro31
::I tried to compile it,but That was old one,and there is "System.development."
:::[http://stackoverflow.com/questions/5865060/c-on-os-x-and-linux This] says that I need to fix stuff after I convert my project. and then work with the mono app which I don't find very convinient... and about the reference I don't know what it's about..I don't know a namespace called System.Development --[[User:Elisherer|Elisherer]] 17:42, 2 October 2011 (CEST) (P.s you can sign your messages with the quick signature button or 4 tildes: '~' 4 times)

lblBrew_Click() had no exception handler,

you have to change this method in fmExplorer.cs to
private void lblBrew_Click(object sender, EventArgs e)
{
try
{
System.Diagnostics.Process.Start(lblBrew.Text);
}
catch (Exception ex)
{
MessageBox.Show("Cannot open link that was clicled.\n"+ ex.Message);
}
}

Matyapiro31

The algorithm for the Image Hash might be either MD2 or MD4. I found out by using HxD and Notepad. --[[User:Kiddyshaq34|Kiddyshaq34]]
:Ok, but of what? (i know it's suppose to be 128 bit) And why not MD-5? --[[User:Elisherer|Elisherer]] 07:10, 9 October 2011 (CEST)
::Because MD5 is longer and the Image Hash has the same number of bytes as MD2 and MD4.
:::MD2, 4 & 5 are all 128bit which is 0x10 bytes... --[[User:Elisherer|Elisherer]] 20:28, 9 October 2011 (CEST)
::::Oh, I've forgotten about MD5. You are right.

3DS include RSA Securuty 's [http://www.rsa.com/node.aspx?id=1204 BSafe]

from 3DS manual. Matyapiro31
:Thanks Matyapiro31 but I think RSA is used for encryption and *not* hashing. So the RSA might be used for ROMs and WiFi... --[[User:Elisherer|Elisherer]] 14:48, 9 October 2011 (CEST)

あほ。RSA BSafe support all security method.See [http://www.rsa.com/japan/products/bsafe/CRYPTOCJ_DS_1101-J.pdf this.]

I cannot find English version,sorry.
Matyapiro31
:I guess if you mean [http://www.rsa.com/node.aspx?id=3063 this] then the digest algorithms are the ones that we know of..we havn't tried HMAC yet or CNG but from experience we see that nintendo uses regular digest algorithms like CRC16-Modbus and SHA-256. I'll add the HMAC ones to the brute force hash tool to see if it finds something... --[[User:Elisherer|Elisherer]] 22:36, 12 October 2011 (CEST)

I've tried to decrypt 'Super Mario 3D Land' but your tool shows me an 'Corrupt Save File' error.--[[User:Lazymarek9614|Lazymarek9614]] 18:36, 18 November 2011 (CET)
:Corrupted save file might be from 2 reasons: * Size is not right (128K or 512k) * CRC on wearleveling wrong. Both problems occur from NDS adapter plus malfunctioning...try blowing on the cart and the adapter and download the savefile again... --[[User:Elisherer|Elisherer]] 20:16, 18 November 2011 (CET)
::I actually don't use the useless NDS Adapter Plus, but I used DSM and I've tried it two times (always the same data).. I hope Nintendo doesn't use a new encryption now! Shall I send you the sav file?--[[User:Lazymarek9614|Lazymarek9614]] 20:27, 18 November 2011 (CET)
:::Yes please, I could check it within the application... --[[User:Elisherer|Elisherer]] 20:35, 18 November 2011 (CET)
::::Have you found anything?--[[User:Lazymarek9614|Lazymarek9614]] 21:25, 18 November 2011 (CET)
:::::No..it's seems that the key found isn't the right key (even that it appears 4 times in the file). we need to figure out how to decrypt the save files without searching blindly for the key. --[[User:Elisherer|Elisherer]] 21:33, 18 November 2011 (CET)
:::::I got an idea. Xor the image's 0x100-0x103 with every (0x200 block)'s 0x100-0x103 to see if it produces 'DISA' ..it should work with the already known files and might be faster to find. i'll try it tomorrow.. --[[User:Elisherer|Elisherer]] 21:40, 18 November 2011 (CET)
::::::Mind linking to a SM3DL save here so I could look at it?(Btw, you're not looking for a "key", you're looking for an AES-CTR xorpad.) --[[User:Yellows8|Yellows8]] 06:03, 22 November 2011 (CET)
:::::::I'll ask for permission. In the meanwhile, can we talk about it at n-dev.net? I made a [http://n-dev.net/showthread.php?tid=4 thread] there. --[[User:Elisherer|Elisherer]] 16:26, 22 November 2011 (CET)
::::::::Yes, you can share them!--[[User:Lazymarek9614|Lazymarek9614]] 17:24, 22 November 2011 (CET)
:::::::Catch the files on my server [http://www.sherer.co.il/saves http://www.sherer.co.il/saves] (Super Mario 3D Land).--[[User:Elisherer|Elisherer]] 17:43, 22 November 2011 (CET)
::::::::I'm stumped too. Since some chunks of data appears several times in these saves, in theory the CTR should still be repeating.(CTR seems to repeat >0x200 bytes now, not sure.) Didn't really manage to decrypt much via xor. --[[User:Yellows8|Yellows8]] 22:08, 22 November 2011 (CET)
::::::::I would guess they finally fixed the bug that limited the xor stream to just 0x200 bytes repeating, and now it behaves more like the data saved to SD cards? --[[User:Neimod|Neimod]] 01:30, 25 November 2011 (CET)
::::::::But you can see that same blocks share the same xorpad in the file...the DISA header is in the file 4 times and encrypted the same all the 4 times.. so the key may not repeat but maybe every block has it's own xorpad based on its offset in the image (my speculation) --[[User:Elisherer|Elisherer]] 09:02, 25 November 2011 (CET)

== *FS#.bin decrypt ==
Maybe I found the key: I think it's the unknown value at Rom. It's 16 characters long.
When I use it, it doesn't give a error or something.
--[[User:Gericom|Gericom]] 16:06, 12 December 2011 (CET)

Talk:3DSExplorer

2011-12-12T14:06:41Z

Gericom:

Now I figured that I didn't explain the target of this app... It's suppose to be an Explorer like program to see inside the different filesystems that the 3ds has. Now it's the ExeFS, RomFS and SAVE. As knownledge keep flowing i'll continue to develop the application. With the goal of making a full functional drag&drop file explorer for image files. --[[User:Elisherer|Elisherer]] 18:35, 15 September 2011 (CEST)

It fails showing the tmd file content. Have you finshed working on this feature?--[[User:Lazymarek9614|Lazymarek9614]] 15:49, 20 September 2011 (CEST)
:No, I don't have time to work on it..it's not interesting enough --[[User:Elisherer|Elisherer]] 15:36, 21 September 2011 (CEST)
::Yeah, the 3DS doesn't care when the tmd file was modified... it's not useful for hacking.--[[User:Lazymarek9614|Lazymarek9614]] 21:09, 21 September 2011 (CEST)

I downloaded the sources,but I can't find Save.cs and reference "System.Development". Matyapiro31
:You are right... I fixed it.. notice that the source is not the released version it has some experimental stuff in it... --[[User:Elisherer|Elisherer]] 10:53, 30 September 2011 (CEST)

Do you know [http://monodevelop.com/ Mono Develop]?
You can release it as multi-patform,such as Linux,Machitosh,etc.
:I did not know that until now. But I don't have time to make the transition. I'm happy with VS2008 and it's relatively easy to make changes and new features for the app. The source is open and you can make a linux port if you want. --[[User:Elisherer|Elisherer]] 18:16, 30 September 2011 (CEST)
:You need no change.mono can run c# program like Java VM. Matyapiro31
::I tried to compile it,but That was old one,and there is "System.development."
:::[http://stackoverflow.com/questions/5865060/c-on-os-x-and-linux This] says that I need to fix stuff after I convert my project. and then work with the mono app which I don't find very convinient... and about the reference I don't know what it's about..I don't know a namespace called System.Development --[[User:Elisherer|Elisherer]] 17:42, 2 October 2011 (CEST) (P.s you can sign your messages with the quick signature button or 4 tildes: '~' 4 times)

lblBrew_Click() had no exception handler,

you have to change this method in fmExplorer.cs to
private void lblBrew_Click(object sender, EventArgs e)
{
try
{
System.Diagnostics.Process.Start(lblBrew.Text);
}
catch (Exception ex)
{
MessageBox.Show("Cannot open link that was clicled.\n"+ ex.Message);
}
}

Matyapiro31

The algorithm for the Image Hash might be either MD2 or MD4. I found out by using HxD and Notepad. --[[User:Kiddyshaq34|Kiddyshaq34]]
:Ok, but of what? (i know it's suppose to be 128 bit) And why not MD-5? --[[User:Elisherer|Elisherer]] 07:10, 9 October 2011 (CEST)
::Because MD5 is longer and the Image Hash has the same number of bytes as MD2 and MD4.
:::MD2, 4 & 5 are all 128bit which is 0x10 bytes... --[[User:Elisherer|Elisherer]] 20:28, 9 October 2011 (CEST)
::::Oh, I've forgotten about MD5. You are right.

3DS include RSA Securuty 's [http://www.rsa.com/node.aspx?id=1204 BSafe]

from 3DS manual. Matyapiro31
:Thanks Matyapiro31 but I think RSA is used for encryption and *not* hashing. So the RSA might be used for ROMs and WiFi... --[[User:Elisherer|Elisherer]] 14:48, 9 October 2011 (CEST)

あほ。RSA BSafe support all security method.See [http://www.rsa.com/japan/products/bsafe/CRYPTOCJ_DS_1101-J.pdf this.]

I cannot find English version,sorry.
Matyapiro31
:I guess if you mean [http://www.rsa.com/node.aspx?id=3063 this] then the digest algorithms are the ones that we know of..we havn't tried HMAC yet or CNG but from experience we see that nintendo uses regular digest algorithms like CRC16-Modbus and SHA-256. I'll add the HMAC ones to the brute force hash tool to see if it finds something... --[[User:Elisherer|Elisherer]] 22:36, 12 October 2011 (CEST)

I've tried to decrypt 'Super Mario 3D Land' but your tool shows me an 'Corrupt Save File' error.--[[User:Lazymarek9614|Lazymarek9614]] 18:36, 18 November 2011 (CET)
:Corrupted save file might be from 2 reasons: * Size is not right (128K or 512k) * CRC on wearleveling wrong. Both problems occur from NDS adapter plus malfunctioning...try blowing on the cart and the adapter and download the savefile again... --[[User:Elisherer|Elisherer]] 20:16, 18 November 2011 (CET)
::I actually don't use the useless NDS Adapter Plus, but I used DSM and I've tried it two times (always the same data).. I hope Nintendo doesn't use a new encryption now! Shall I send you the sav file?--[[User:Lazymarek9614|Lazymarek9614]] 20:27, 18 November 2011 (CET)
:::Yes please, I could check it within the application... --[[User:Elisherer|Elisherer]] 20:35, 18 November 2011 (CET)
::::Have you found anything?--[[User:Lazymarek9614|Lazymarek9614]] 21:25, 18 November 2011 (CET)
:::::No..it's seems that the key found isn't the right key (even that it appears 4 times in the file). we need to figure out how to decrypt the save files without searching blindly for the key. --[[User:Elisherer|Elisherer]] 21:33, 18 November 2011 (CET)
:::::I got an idea. Xor the image's 0x100-0x103 with every (0x200 block)'s 0x100-0x103 to see if it produces 'DISA' ..it should work with the already known files and might be faster to find. i'll try it tomorrow.. --[[User:Elisherer|Elisherer]] 21:40, 18 November 2011 (CET)
::::::Mind linking to a SM3DL save here so I could look at it?(Btw, you're not looking for a "key", you're looking for an AES-CTR xorpad.) --[[User:Yellows8|Yellows8]] 06:03, 22 November 2011 (CET)
:::::::I'll ask for permission. In the meanwhile, can we talk about it at n-dev.net? I made a [http://n-dev.net/showthread.php?tid=4 thread] there. --[[User:Elisherer|Elisherer]] 16:26, 22 November 2011 (CET)
::::::::Yes, you can share them!--[[User:Lazymarek9614|Lazymarek9614]] 17:24, 22 November 2011 (CET)
:::::::Catch the files on my server [http://www.sherer.co.il/saves http://www.sherer.co.il/saves] (Super Mario 3D Land).--[[User:Elisherer|Elisherer]] 17:43, 22 November 2011 (CET)
::::::::I'm stumped too. Since some chunks of data appears several times in these saves, in theory the CTR should still be repeating.(CTR seems to repeat >0x200 bytes now, not sure.) Didn't really manage to decrypt much via xor. --[[User:Yellows8|Yellows8]] 22:08, 22 November 2011 (CET)
::::::::I would guess they finally fixed the bug that limited the xor stream to just 0x200 bytes repeating, and now it behaves more like the data saved to SD cards? --[[User:Neimod|Neimod]] 01:30, 25 November 2011 (CET)
::::::::But you can see that same blocks share the same xorpad in the file...the DISA header is in the file 4 times and encrypted the same all the 4 times.. so the key may not repeat but maybe every block has it's own xorpad based on its offset in the image (my speculation) --[[User:Elisherer|Elisherer]] 09:02, 25 November 2011 (CET)

== *FS#.bin decrypt ==
Maybe I have found the key: I think it's the unknown value at Rom. It's 16 characters long.
When I use it, it doesn't give a error or something.
--[[User:Gericom|Gericom]] 16:06, 12 December 2011 (CET)