MotionJPEG processing chip. The data is placed into KRAM, using KING's control of RAINBOW related registers
| 0x200 (word) | Horizontal scroll |
|---|---|
| 0x204 (half) | Control |
| 0x208 (half) | Unknown |
| 0x20C (half) | Unknown |
| 0x210 (half) | Unknown |
| 0x214 (half) | Unknown |
More information needed!
More information needed!
More information needed!
More information needed!
More information needed!
More information needed!
The basic format (markers + size + data) is like JPEG. Occurrence data is 0xFF 0xFF 0x00 markers for distinguishing and (again, like JPEG).
One is 1 block data corresponding to a vertical 16 dot? (What it is, the 2x2 luminance block?)
Huffman table has not been found yet. Do you use a fixed Huffman codes, it seems to be a sign of its own compression.
Be the first to appear in a block of data. Quantization table, including the actual data of the image?
FFFFh, [Block Size (2byte)], [First quantization table? (64byte?)],[Second quantization table? (64byte?)], [Real data? (Block size - 130byte)]
Quantization table is not zig-zag, but is left-left, as usual?
Emerge from the second block of data. Actual data of the image?
FFF8h, [Block Size (2byte)], [Real data? (Block size - 2byte)]
Unknown. Run length?
Unknown. Run length?
Unknown