Libraries for interfacing a controller already exist (supporting GH guitars too ) so I'm not interested in that. Speed can't be pushed further I'm afraid as you get transfer errors (not for the RS232 but the card itself).Ĭontroller has 9 pins but one is not connected to anything. One 3rd party card died on me but I don't know if that's connected as I had many 3rd party cards fail even with normal usage.ġst party card on the other hand seems to be very durable and it's working fine after PS1, PS2, LPT readers, DexDrive and now Arduino usage.īut I can use resistors which should lower the voltage to required levels for logic I'm using Arduino Nano v3.0 (looking similar to Teensy board). Line to 5 V and that gave me good results. Notice that I wrote getting harder to get (over the years), not hard to get (currently).Īlso, that's a stock and who knows how many they got :Īt first I connected Memory Cards to the 3.3 V Arduino provides but I was getting read errors so I switched 3.6 If it wasn't for the "oooh, I've always wanted a DexDrive" I've would have never get one. I got mine from the same place, but i paid for shipping more then the actual device itself (20 $). I know that ATM, you're using 38k baud, but will you be considering raising the transfer speed? Last question, the interface could also be extended as a pad interface, DirectPadPro-ish you just don't quit do you? Sorry for all this OT pad discussion, just trying to understand Sony's tricks ) llers.html, is using Pins 1 and 9 for multi pad support. Is pin 4 on the pad also on the MC port? Considering that the MC port has 8 pins and the pad has 9 pins, will be researching more.ĮDIT- just realised that pin 4 of the pad is the GND: WTF is NTPad doing? Yet another site. Though, the design at uses pin 4 on the pad ports, as a pad select (but no MC ports used there). But in hindsight this would diff cause a problem, both pads responding. I had thought that the state of the ATT line signaled the choice between the MC or the pad, I.E. His notes explored the issues with third party cards, but briefly described the hardware similarities to SPI.
I had read Charles MacDonald's page on the PSX Memory cards.
Sony has obviously extended the SPI protocol, THX for clarifying. When the line is low both devices are active. Shendo ATT (SS) for Memory Card and Controller are shared. The only difference that determines which peripheral will answer is the initial command (0x01 - Controller, 0x81 - Memory Card).
#FFX PS2 GAME SAVES DEVICE MEMORY CARD CONVERTER SOFTWARE#
Software side will be provided by standalone application and MemcardRex v1.8 ATT (SS) for Memory Card and Controller are shared. So after pulling an all-nighter (couldn't sleep when there is work to be done ) I implemented a DexDrive-likeĬommand driven "firmware" which gave me speed up to par with DexDrive.Īfter I completely finish it I will post schematic and a GPLed source so people can burn it to their Arduinos. So I scrapped that approach and started looking for alternatives.Ītmel AVR chips (microcontroller on Arduino) have native SPI interface which is pretty flexible andĬan be configured to give the required 250 kHz clock. To read whole 128 kB of data one would have to wait for 10 minutes. In the PSX library I linked, the SPI communication is done using software (via digitalWrite() and DigitalRead())įor bit pushing which is ok for controllers but way too slow for Memory Cards as clock needs to be 250 kHz. Oh man, I hit a major roadblock yesterday.