Recent content by miyasan

  1. M

    Communication port information

    I got ss-fdd. it is very expensive... I monitored SPI between Saturn and FDD. I wrote a little about it. <<command: change partition>> (1) send command token(4byte + CRC4byte) {0x80, 0x11, (uint16)partition number, CRC} (2) get ACK(4byte + CRC 4byte) {0x20, 0x00, 0x00 0x00, CRC...}...
  2. M

    Communication port information

    sorry, I missed one information. BUP_Init this function check presence of SPI device. if SPI device is presence get 3 information( unit ID, number of partition, bytes/block#2) if number of partition is larger than 15, Saturn recognize the device is wrong , and ignored it. thanks.
  3. M

    Communication port information

    used SS FDD becomes investment item, too expensive. I can't buy.... By the way, I got more information about partition change cmd in Backup library. there is low-level function in Backup lib. uint32 low-level_func(uint32 *retBuf, uint16 partition_num){ uint8 spiBuf[28]; } (1) send command...
  4. M

    Communication port information

    I use harf-cutted Link-cable. this cable connected master SPI signals(3 wire) and slave SPI signals(3wire), but disconnect VCC. I think FDD-like device need VCC to recognize SATURN's power condition. and to avoid SPI noise. maybe, I saw connector like Link-cable in the electronics parts...
  5. M

    Communication port information

    Hi. I got your document at 6 month ago. It is very interesting. (1) I try to make Sega Saturn FDD compatible device, based your document. when starting, Application check if Saturn connect with FDD by partition change command. My device get "80 11 00 00 00 00 74 3b" from saturn, but put...
Back
Top