Changes

|}

|}

Used for resetting cameras/DSP. Once cameras/DSP are reset by poking this register, REG_CAMDATA and REG_CAMCNT are cleared by hw.

Used for resetting cameras/DSP. Once cameras/DSP are reset by poking this register, all three 0x0400420X camera registers return all-zero on reads. This might mean the DSP fw bin was unloaded?

=== REG_CAMCNT ===

=== REG_CAMCNT ===

For retrieving camera video data, [[NDMA]] with arm9 startup mode 11(camera) is used with this src register. The NDMA frame transfer is started when the cameras [[Interrupts|IRQ]] was thrown. Supported DSP final resolutions are 256x192 and 640x480, the corresponding frame transfer lengths are 0x18000 and 0x96000.(The 256x192 final resolution is converted by the DSP from the camera resolution)

For retrieving camera video data, [[NDMA]] with arm9 startup mode 11(camera) is used with this src register. The NDMA frame transfer is started when the cameras [[Interrupts|IRQ]] was thrown. Supported DSP final resolutions are 256x192 and 640x480, the corresponding frame transfer lengths are 0x18000 and 0x96000.(The 256x192 final resolution is converted by the DSP from the camera resolution)

The DSP fw binary still seems to be loaded after cameras were used in the exploited title, as reading this register(with cameras reinitialized prior to that) results in changing data rather than fixed data. The DSP is a proprietary CEVA DSP, since this ISA is proprietary fw binaries can't be compiled for it. Thus homebrew could potentially only use cameras when the exploited title can use cameras and cameras were used in the title prior to running hax.

The DSP is a proprietary CEVA DSP, since this ISA is proprietary fw binaries can't be compiled for it. Thus homebrew can't use cameras unless it's possible to initialize cameras without poking REG_CAMRST,(which seems to unload the proprietary DSP fw bin) which might not be possible.

== See also ==

== See also ==