Adapter for MAPLE (Release)

[soniccd123]

Already tried, no effect

Again, the icon just flashes, no effect

Edit: Tried something diferent, was using a controller cable for testing, removed it and soldered smaller wires directly to Port D PCB contacts (inside the Dreamcast), seems to be recognized now, will try the other firmwares and to wire the memory correctly

Edit2: The VMU and the adapter now work, the problem seemed to be the cable length, probably was receiving some kind of interference. Thank you very much for compiling all these builds and trying to help me. I'm sorry for wasting your time, actually ashamed now that I identified the problem

[RazorX]

Already tried, no effect

Again, the icon just flashes, no effect

Edit: Tried something diferent, was using a controller cable for testing, removed it and soldered smaller wires directly to Port D PCB contacts (inside the Dreamcast), seems to be recognized now, will try the other firmwares and to wire the memory correctly

Edit2: The VMU and the adapter now work, the problem seemed to be the cable length, probably was receiving some kind of interference. Thank you very much for compiling all these builds and trying to help me. I'm sorry for wasting your time, actually ashamed now that I identified the problem

have you got it switching vmu's when you press the buttons because that isn't working for me.

Edit:
nevermind I figured it out

[soniccd123]

Again, the icon just flashes, no effect

Edit: Tried something diferent, was using a controller cable for testing, removed it and soldered smaller wires directly to Port D PCB contacts (inside the Dreamcast), seems to be recognized now, will try the other firmwares and to wire the memory correctly

Edit2: The VMU and the adapter now work, the problem seemed to be the cable length, probably was receiving some kind of interference. Thank you very much for compiling all these builds and trying to help me. I'm sorry for wasting your time, actually ashamed now that I identified the problem

have you got it switching vmu's when you press the buttons because that isn't working for me

Unfortunately no, the switching is not working, I may have a diferent circuit to sugest, but need to do some tests to confirm it works and does not interfere with whatever controller is connected to the buttons

I'm having some stability problems with my circuit, it is kind picky with touching and etc, maybe it has to do with the breadboard. The VMUs also fail frequently to read, write and format and only 8 show up correctly, even using the 25PE16. I may need to build a board to actually be able to do what I want. The VMU stability problems is also happening in the normal firmware

[s_d_a_i]

Hi @megavolt85 As I can see, you are holding the data bits for less than 250ns so the DC lost sync in the arcade firmware.

Check the image you have to keep the line stable for at least 250ns for each bit, that is half a division on the capture, please consider the falling and rising edges are different depending on the setup and the bluepill you are using and the cable capacitance, sorry I dont know if I explained correctly.

If you are using Gmanmodz maple implementation on the maple_delay function you have to increase the nop() for loop, if you're using interrupts increase the count, please

[soniccd123]

As I can see, you are holding the data bits for less than 250ns so the DC lost sync in the arcade firmware.

STM32_joy_firm.jpg

Check the image you have to keep the line stable for at least 250ns for each bit, that is half a division on the capture, please consider the falling and rising edges are different depending on the setup and the bluepill you are using and the cable capacitance, sorry I dont know if I explained correctly.

This makes sense, thanks. Unfortunately I dont have a good Osciloscope at home to check but I'll see if I can make some adjustments.

Something that I noticed testing is that, at least in Crazy Taxi, while it says that the saving has failed, It actually has saved the game correctly. Another strange ocorrence is that when using the normal firmware, formating the VMU seems to fail, while with the arcade stick one it formats correctly, but in both firmwares, just after formating, the VMU is recognized by the Dreamcast as if formating had failed and as unformated. After power cycling the Dreamcast, the VMU shows up correctly.

[s_d_a_i]

Sorry, it was addressed to Megavolt, you can do nothing about it.

[RazorX]

Again, the icon just flashes, no effect

Edit: Tried something diferent, was using a controller cable for testing, removed it and soldered smaller wires directly to Port D PCB contacts (inside the Dreamcast), seems to be recognized now, will try the other firmwares and to wire the memory correctly

Edit2: The VMU and the adapter now work, the problem seemed to be the cable length, probably was receiving some kind of interference. Thank you very much for compiling all these builds and trying to help me. I'm sorry for wasting your time, actually ashamed now that I identified the problem

have you got it switching vmu's when you press the buttons because that isn't working for me

Unfortunately no, the switching is not working, I may have a diferent circuit to sugest, but need to do some tests to confirm it works and does not interfere with whatever controller is connected to the buttons

I'm having some stability problems with my circuit, it is kind picky with touching and etc, maybe it has to do with the breadboard. The VMUs also fail frequently to read, write and format and only 8 show up correctly, even using the 25PE16. I may need to build a board to actually be able to do what I want. The VMU stability problems is also happening in the normal firmware

here is my revised schematic with working buttons:

[RazorX]

should i add any sort of cap on the 5v source to perhaps make it more stable? i have mine working now but the controller still disappears on me sometimes when i press the buttons and the board moves.

[megavolt85]

If you are using Gmanmodz maple implementation on the maple_delay function you have to increase the nop() for loop, if you're using interrupts increase the count, please

no, I have my own protocol implementation

[soniccd123]

If you are using Gmanmodz maple implementation on the maple_delay function you have to increase the nop() for loop, if you're using interrupts increase the count, please

no, I have my own protocol implementation

This seen to have stabilized more the connection, but still not perfect, still unstable using the controller cable, much better connecting the board inside the Dreamcast

Edit: I'm testing the VMU, it has a very strange behavior, looks like some instructions are missing at the end of VMU operations; After any VMU operation like saving, loading, deleting a file or formating, it fails to continue conected or glitches. I can send videos or photos of this behavior if is of help, was able to reproduce this behavior with the normal and arcade stick firmwares, and the arcade stick one actually is more stable with VMU operations. Everything is connected through a breadboard, so I don't know if this can cause such interference with SPI protocols to glitch the memory chip, I think it is more likely that it has to do with software, as also shortening the cable connecting the MAPLE bus to the STM32 has no effect on the behavior. Also, Using USB Mode seens to work perfectly without any bugs.