PSX RS-232 Serial I/O for SIOCONS / HIT-SERIAL

[Shadow]

No. It failed to work with SIOCONS and HITMENS EXE loader. It did nothing.
I'm looking into it again to see what the problem with the schematic was...

[Shadow]

Here is a little update.
The board has been wired to TX/RX and GND on the PC serial (DB-9) connector, but refuses to work.
The only thing I can get it to do is output when I remove power (either the 5V or GND) once the Yaroze boot disc has loaded. I am running the cracked version of the Yaroze boot disc.
I am feeding it 5V from a 7805 VREG from a 9V battery. The voltage levels are a constant and a stable 5V.
Any help is appreciated.

When power is removed once the boot disc has loaded:

Code: Select all

Connected CIP ver2.0xÛ[[7Û
                         onàÿàÿ

When CTS+RTS are bridged together on the PC serial side and power is removed once the disc has loaded:

Code: Select all

Connected CIP ver2.0
Communication baud rate 9600 bps
OK
  àààààààààààààààààààààààààààààààààààààààààààÃ>

Schematic:

[Shadow]

All working now! (sort of)
I can use '>>play' to play CD-DA off of some games that have it and run '>>cb' to show the coloured bars, etc...

PC RTS and CTS are wired together.
PC DTR and DSR are wired to 5V, and the GND from the 7805 was removed. If I add the ground from the power supply, everything stops working which is very weird.

The new problem now is that it wont load any EXE's.
I receive a sync error.
I have tried PS-EXE's and Yaroze AUTO files.
It sounds to me like a handshaking problem... Any suggestions?

Code: Select all

BINARY DATA TRANSFER - BWR
ADRS = 800DEA9C
SIZE = 000338FF BYTES
INTO BURST TRANSFER SUM:00 0/ 338FF BYTES
SYNC ERROR (FFFFFFFF)
ABORT.

[rsoft]

Hmm... The sync error does point to a handshake problem.
"PC RTS and CTS are wired together." - Is that supposed to mean that PC RTS is connected to PSX CTS and vice versa?
If so, then that should be correct.
I've had similar problems trying to use siocons (the unix clone) with a Pentium 4 era PC... Never really resolved that issue. It even existed when using a USB RS232 converter.
Hope you get it running!

[Shadow]

No. The PC RTS and CTS are connected together (shorted). The RX and TX are crossed (EG: RX becomes TX). The DTR and DSR are wired to 5V. If I wire the RTS and CTS respectively, I get in SIOCONS "Yaroze DTL not ready".

I have no idea what the hell is going on.

[Shadow]

This project has been scratched... I will be re-designing a new PCB using an FTDI and USB

[rsoft]

Well, once again: RTS and CTS shouldn't be looped back. They need to be connected to the PSX for the handshake to work.
On a different note: You're most likely not going to get the full transfer speed powering the MAX232 from +3.3V as required by the PSX and its in- and outputs. For that reason I'm using a MAX3232/3222 for my build. It's the 3.3V variant of the MAX232.

[Shadow]

FTDI and USB > PSXSERIAL: http://www.psxdev.net/forum/viewtopic.php?f=62&t=425

[gwald]

All working now! (sort of)
I can use '>>play' to play CD-DA off of some games that have it and run '>>cb' to show the coloured bars, etc...

PC RTS and CTS are wired together.
PC DTR and DSR are wired to 5V, and the GND from the 7805 was removed. If I add the ground from the power supply, everything stops working which is very weird.

The new problem now is that it wont load any EXE's.
I receive a sync error.
I have tried PS-EXE's and Yaroze AUTO files.
It sounds to me like a handshaking problem... Any suggestions?

Code: Select all

BINARY DATA TRANSFER - BWR
ADRS = 800DEA9C
SIZE = 000338FF BYTES
INTO BURST TRANSFER SUM:00 0/ 338FF BYTES
SYNC ERROR (FFFFFFFF)
ABORT.

I know this is old, and your not making these anymore, just wanted to say that I'm having the same issue with my NY on linux (mint 17.1)
It works 100% correct in windows so i'm thinking your problem could be a com port Hardware or software setup issue.

[brill]

Hello!
My MasterCard cable)
Work. But so slow. Any idea?

2 x ST232BN
1 x 74HC00
10 x 1mF 50v

[danhans42]

siocons is slow unfortunately, even at 115k.

[brill]

seems problem in dos (may be some extra settings)
because CodeWarrior Debugger load much-much-much faster same file (7-10 sec).