PlayStation Development Network

Hello there, long time no see !

While researching for PS1 dev kit, I came across the PSY-Q debugger hardware that plugs into the parallel port of a debug PS1 unit.
Since for my code I use an XPlorerFX (flashed with caetla), is it possible to debug code with this ?
Like in CodeWarrior, having the ability to step the code and use breakpoints.

If yes, how so ? What are the software needed ? Do I need to reflash my XPlorer with another firmware ?
If no, is there a workaround to do remote debugging ?

Thanks in advance for any answers !

To debug, use NO$PSX with the Psy-Q symbols. However, for basic debugging just adding printf() will suffice.

No it's not what I meant.
I mean REMOTE debugging with such boards as the PSY-Q one that went into the parallel port of a blue unit : https://www.retroreversing.com/official ... ion-devkit

My question is : is there a possibility to replicate HARDWARE REMOTE debugging ? Also, if possible, using the old Metrowerks CodeWarrior for PS1 and tweaking parameters, so I can do in-code breakpoints and debugging.

New Nova wrote: ↑March 22nd, 2023, 1:38 am No it's not what I meant.
I mean REMOTE debugging with such boards as the PSY-Q one that went into the parallel port of a blue unit : https://www.retroreversing.com/official ... ion-devkit

My question is : is there a possibility to replicate HARDWARE REMOTE debugging ? Also, if possible, using the old Metrowerks CodeWarrior for PS1 and tweaking parameters, so I can do in-code breakpoints and debugging.

No. The whole story is a little messy - that blue target cart was part of the proposed Psy-Q PSX development system, but it never got a formal release because Sony licensed the Psy-Q toolchain (as "SDEV-TC") for their official development kit, and as part of the agreement Psygnosis agreed to stop selling it individually. They then retargeted their debugger to work with the official Sony DTL-H2000 development board.

There was also a Codewarrior version that worked with the DTL-H2000 - IIRC, you had to install a different driver (DECI?) and it did not play well with the TSR driver module in the official devkit. This is distinct from (but probably close to) the version of CW that targeted the Yaroze.

There was also a CW debug stub for the "Ez-O-Ray" homebrew development cart that worked with a standard retail PSX, although since it also needs the Datel "PC Comms Link" card and a PC with an ISA bus slot to plug it into, it's basically just of historical interest now.

In theory, someone could write a DECI driver that talked to the Explorer hardware and interfaced with CW, but as far as I know nobody has actually done it.