-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ESP32 and ESP8266: "mc read failure, check connections", printed data displays evidence of card data being read #33
Comments
Try using pull-ups. Put 1K external pull-up resistors to 3.3V on Cmd, Data, Att, Clk and Ack lines. |
Thanks for the very quick response! Tried that with both devices, unfortunately only got:
There's a decent chance it was something to do with the suboptimal setup I have at the moment rather than anything else though. Will try the Nano when it arrives next week and report back 👍 |
One thing to note since you said that you are using ports on the multitap. Are the ports still connected to the logic board? It might be interfering with the connection... |
Each port had its own board to simplify the wiring to the logic board, I removed them and either reused the wires for the logic board or soldered new ones on directly onto the memory card pins Have now gotten the Nano. I'm getting the same results from the latest master but I tried commit IDE: Arduino IDE 2.2.1
|
Ooof, my bad, I was looking into the ESP code and noticed I left some log stuff in the I most likely had some kind of wiring issue initially and broke the file. Thanks for the help and the project overall, saves me from having to buy a PS2 for some PocketStation experiments I want to do! |
@padraigfl have you successfully been able to write? Could you share the setup / schematic you're using? I'd greatly appreciate it! I have an ESP8266 I'll be using as well. |
Hi @lf94 , I didn't actually test too much wrt writing yet but I was able to move around save files on a PocketStation and have them appear in the new order so I assume it is writing correctly. I think my initial issues were due to trying to reuse the wires already attached to the memory card socket rather than anything with the project. I'll be messing about with it a fair bit more in the next few weeks, gonna stick with the ESP8266 to see if I can unearth any issues. I think there's some downsides to gutting a multitap (it feels very likely to break or let something be inserted incorrectly) so I may try and create a different adapter instead. |
Nice, that sounds like good news to me - I'll probably attempt this today or tomorrow. |
I've tried this on both an ESP32 (38 pin dev board) and ESP8266 (Wemos D1) with the same results for both. MemcardRex is picking up the board as 0.6 but is immediately stalling.
Having ran the Python script (
python3 .\memcarduino.py -p COM4 -r data.txt
) it outputs the following:The SLES-03575 game code refers to one of the games I know is on the memory card so it does seem to be reading something, changing the line
ser.write(MCR + b"\x00\x01")
appears to be iterating through the files in the memory card from the game codes.I've tried two memory cards (one official, one not) and gotten the same results on both boards.
The memory card port is one zombied together from a broken multi-tap, I've tried multiple of the ports from the multi tap
I've ordered an Arduino Nano and will try it out too when it arrives, but if there's anything else I can debug here I'd appreciate knowing it.
The text was updated successfully, but these errors were encountered: