Joybus Protocol: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
(the validation code in the read/write pak commands isn't a CRC) |
(Fixed controller pak example regarding MSB usage.) |
||
| Line 116: | Line 116: | ||
Similar to reading from a Pak, the write command is followed by two bytes for the address and checksum. But 32 bytes are also provided for writing to the Pak. The controller is still required to respond with a CRC byte for the received data, and it must begin responding within about 62.5 microseconds. |
Similar to reading from a Pak, the write command is followed by two bytes for the address and checksum. But 32 bytes are also provided for writing to the Pak. The controller is still required to respond with a CRC byte for the received data, and it must begin responding within about 62.5 microseconds. |
||
How the Pak interprets the address and data is up to the Pak in question. The Controller Pak |
How the Pak interprets the address and data is up to the Pak in question. The Controller Pak uses the most significant bit, in combination with the standard chip-enable, to activate/disable the pak. The Rumble Pak appears to use some kind of flip-flop/toggling logic on certain pins to control it. The Transfer Pak is a gameboy cartridge interface with bank switching. Other homebrew Paks could be utilized in many other ways too. |
||
=== 0x04 - Read EEPROM Block === |
=== 0x04 - Read EEPROM Block === |
||