Properly Loading PS2Link and interfacing with PS2Client #770
-
Hi All, I am trying to set up a development workflow for PS2DEV/SDK and I've run into a jam when attempting to load and debug with ps2link/ps2client. On the PS2Link GitHub page, it says the following:
The way I have been running PS2Link on my console is via uLaunchElf with a FreeMCBoot card. I open the filesystem for a folder on a flashdrive, that contains ps2link.elf alongside the listed above IRX files (all in one folder). As a side note, is this the proper way to share .IRX modules for other .ELFs I may upload onto my PS2 in the future if using custom IOP .IRX modules? Having them all in one big folder like this? When I run PS2Link it seems to work properly. It gives me a welcome message. However, interfacing PS2Link with PS2Client has proven to be rather challenging. I am seemingly able to launch a single .ELF file with ps2client with the following command: ps2client -h 192.168.0.10 execee host:TEST.ELF But that is the extent to which I can interface with PS2Link via PS2Client. I have another terminal window running with After the program instantiated with the I am not quite sure how to use these tools effectively. I am wondering if anybody else has experience and is willing to share, I am coming up pretty slim with a lot of internet searching. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
I think that's outdated information. All irx'es are built into the single .ELF file.
The proper way is undefined... it's up to the devepoler to find a solution for where to store them, or have them built-into the ELF.
Can you share an image of the welcome message?
You don't need a second terminal. After the execee command ps2client will continue to listen for debug output. |
Beta Was this translation helpful? Give feedback.
-
@rickgaiser Thanks for the detailed response.
Yeah, I've gotten the sense that there are a few ways to do the same thing. From what I can tell Is the
https://imgur.com/a/B4C3L6y
That's interesting. I've never gotten any In summary, still losing comms to |
Beta Was this translation helpful? Give feedback.
The output (from the ps2) is only displayed in 1 ps2client session. The one that you start the first. So the
ps2client listen
will show everything. Like I said, you only need 1:ps2client execee
. Then you'll see everything there. It does not hang, it's listening but nothing comes becouse the output is already intercepted by the other running session.To make ps2client quit after executing the command you can add a parameter like
-t 1
I think, it's in the help (-h
?).