[DOWNLOAD] PSXSERIAL

[danhans42]

Top one would work perfectly. I used a 74HC244 as a buffer because when the playstation was powered down random garbage was sent down the serial line if siocons was still open. Its not a requirement, its just the 'HC244 is powered by the playstation, so when its powered off no communication can occur.

The newer send tool wont work with the debugger, this is part of the yaroze boot CD.

[danhans42]

I have got the source to HITSERIAL. Jihad said I could release it with his permission
I will do it soon and link it here (and send you a PM Dan). Shendo's version is a lot more simplistic though to use.

Any update on the source?

[Administrator]

I released it a few weeks ago: http://www.psxdev.net/forum/viewtopic.php?f=60&t=383

[danhans42]

Excellent. Thank you.

[Administrator]

Updated to version 1.2.

[CosmoGuy]

I tried with PL2303 instead of FTDI chip. Unfortunately i have to buy it online but my post is very slow... so i dont want to wait.

I did something like this:




I don't know what's wrong:
[youtube]http://www.youtube.com/watch?v=9cbghBIrvDo[/youtube]

Regards CosmoGuy

[Gradius]

Never rolls the wires, your making a natural resistence on them.

[Administrator]

Rx must go to Tx, and Tx must go to Rx. You have them the wrong way around.
And like Gradius said, don't coil the wires. You're creating a very crude inductor.

[Spipis]

Crazy idea:

Is there any way using the ps1 controller port instead of the Serial i/o port?
Has the same RXD-TXD-GRD pins!

[Administrator]

New bug found in V1.2 which is if any data is received, the screen will not show the text. It's no big deal, but it can be misleading. I will look into this and try to push V1.3 out.

[Greg]

I unfortunately never got SIOCONS working properly because it needs handshaking lines also (in addition to tx/rx).

However, because of LIBPS.EXE taking space in memory your EXEs cannot be larger then 500 KB,
with PSXSERIAL limit is about 1.8 MB.

You don't have to reset the console either, you can just jump back to the loader via __asm__("j 0x801EA678");
There is also benefit of using it on x64 bit Windows, now that we got a new build of send.exe

I try to get back to the serial loader via __asm__("j 0x801EA678"); but without success, maybe I miss something.

[Administrator]

I unfortunately never got SIOCONS working properly because it needs handshaking lines also (in addition to tx/rx).

However, because of LIBPS.EXE taking space in memory your EXEs cannot be larger then 500 KB,
with PSXSERIAL limit is about 1.8 MB.

You don't have to reset the console either, you can just jump back to the loader via __asm__("j 0x801EA678");
There is also benefit of using it on x64 bit Windows, now that we got a new build of send.exe

I try to get back to the serial loader via __asm__("j 0x801EA678"); but without success, maybe I miss something.

I think that address was for V1.0. That address has changed. You can figure out the address manually anyhow.
I'll work more on this today though and let you know.

[Greg]

Ok I have figure out the address.
To get back to the serial loader use __asm__("j 0x801EAAE8");
Works for PSXSERIAL V1.2.

[Administrator]

I was working on the code some more, and I believe there is a serious problem when attempting to draw the display whilst serial communication is underway. EG: If I try to use my display function during this routine,

Code: Select all

	// wait for the sync byte
	while(1)
	{
		while((*(char*)0x1F801054 & 0x2) == 0);
		if(_sio_control(0, 4, 0) == 'c')
		{
			ack=1; // add the text 'RECEIVING DATA FROM PC' and also add a polygon to the screen
			// since we are not in a while loop, the display routine wont execute repeaditly, so
			display(); // draw once to fill the first buffer
			display(); // fill the second buffer and swap to display the first buffer on screen
			break;
		}
	}

I get a crash dump screen showing the PSX registers as soon as I run PSXSERIAL.EXE on the PC side.
It's quite messed up. I have been at this for 3 hours now. My display routine is using double buffering. Single buffer code may solve the problem, though I'm not sure. I'm getting to the point where I am happy to say that maybe there is a bug in the serial library or something in the graphics library doesn't like what I'm doing.

[Administrator]

Okay. Version V1.3 has been released! The error mentioned above was happening because everything was out of sync. I fixed it by making a very crude Rx/Tx handshaking method. This is the best we can do without real RS-232 handshaking. There should be no problems now. Just let me know if you find a problem but I have tested it as much as I can. Thanks goes out to Dax for some help with the C# code on the PC side of things and also a thanks to Alessio for doing some quick tests

Oh, and some calculations for V1.3. The PS-EXE file size is 69,632 Bytes = 0x11000. PSX RAM = 0x80200000. We need to then start from the stack size, so 0x801F8000 - 0x801E7000 = 0x1EF000. PSXSERIAL Execute Address = 0x81E00000 (I could have pushed it a little higher as we can see to 0x801EF000). Anyway, we are left with 1,994,752 Bytes (1,948 KB) of free space to work with. So, we have 1,994,752 Bytes + 69,632 Bytes out of the PSX's 2,097,152 Bytes. Those equal 2,064,384 Bytes which doesn't match because we are missing the stack I believe. Please let me know if that's wrong.

[Greg]

For the return address look at: http://www.psxdev.net/forum/viewtopic.p ... 4189#p4188

PSXSERIAL v1.3 PC side is not compatible with the 1.2 PS side, a little warning will be good in the welcome screen of the ver 1.3 PC side software

[Administrator]

PSXSERIAL v1.3 PC side is not compatible with the 1.2 PS side, a little warning will be good in the welcome screen of the ver 1.3 PC side software

Added it as a note on the first topic above the download links

[Vanta]

I'm having a bit of an odd situation with my DTL-H3050 cable and PSXSERIAL, both on a windows 7 machine using a CH340 based serial to usb converter, and on a much older pc connected directly to the com1 serial port.

Basically, when I do the usual command of psxserial progname.exe com8, the cmd window states "Waiting for the PlayStation 1...", On the PS1, PSXSERIAL shows "Receiving data from PC" but both don't go any further than this.
I have tried with a few different retail PS1 consoles and an actual Yaroze system and no change.
siocons works but psxserial does not, tried under both Windows 10 and Windows XP (updated)

Any ideas?

[Administrator]

I'll check it out now since I have a DTL-H3050 myself.

*EDIT*
Confirmed. It doesn't work for me either. When I have time, I'll take a look into it.
The code is pretty old anyway (3 years now). It could use a clean up.

Okay, I've released a new Win32 EXE. Gave it a fresh new look too. The old one was a mess.
Download it from the first page in the V1.4 ZIP, or the 'Downloads' section on PSXDEV.NET will link you.
I'll have to fix that 'assembler jump routine' bug later when I start up my Windows 98 machine sometime.

[Vanta]

I'll check it out now since I have a DTL-H3050 myself.

*EDIT*
Confirmed. It doesn't work for me either. When I have time, I'll take a look into it.
The code is pretty old anyway (3 years now). It could use a clean up.

Okay, I've released a new Win32 EXE. Gave it a fresh new look too. The old one was a mess.
Download it from the first page in the V1.4 ZIP, or the 'Downloads' section on PSXDEV.NET will link you.
I'll have to fix that 'assembler jump routine' bug later when I start up my Windows 98 machine sometime.

Thanks for looking in to it!

Gave 1.2 a try, uploading Animdemo.exe (padded to the correct size), gets past the "Waiting for the PlayStation 1" issue and starts sending packets like it's supposed to, but when It gets to around 9% complete, the PS1 video feed glitches out to a black screen, Sending of packets continues to 100% with the following text:

Waiting for the PlayStation 1... Success!
Sending packet 737 of 737 (100)%
Executing the PS-EXE and Closing COM8... Success!
Exiting PSXSERIAL...

However, PlayStation output remains black.
Sorry to be a pain! and thanks again for looking into it