Is it possible to debug PS1 code with an XPlorerFX ?

General information to do with the PlayStation 1 Hardware. Including modchips, pinouts, rare or obscure development equipment, etc.
Post Reply
User avatar
New Nova
Active PSXDEV User
Active PSXDEV User
Posts: 61
Joined: Oct 27, 2018
I am a: Collector, developper, artist
Motto: RTFM
PlayStation Model: DTL-H2000
Location: France
Contact:

Is it possible to debug PS1 code with an XPlorerFX ?

Post by New Nova » March 22nd, 2023, 12:30 am

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 !
Development PC : Compaq PC, Intel Pentium III 600MHz, 256MB RAM, NVIDIA GeForce4 MX 440 (AGP)
Development Unit : DTL-H2000 board + DTL-H2010 CD-ROM drive
Retail Unit : SCPH-1002 + XplorerFX + caetla + modchip + activity LED mod

User avatar
Shadow
Verified
Admin / PSXDEV
Admin / PSXDEV
Posts: 2670
Joined: Dec 31, 2012
PlayStation Model: H2000/5502
Discord: Shadow^PSXDEV

Post by Shadow » March 22nd, 2023, 1:31 am

To debug, use NO$PSX with the Psy-Q symbols. However, for basic debugging just adding printf() will suffice.
Development Console: SCPH-5502 with 8MB RAM, MM3 Modchip, PAL 60 Colour Modification (for NTSC), PSIO Switch Board, DB-9 breakout headers for both RGB and Serial output and an Xplorer with CAETLA 0.34.

PlayStation Development PC: Windows 98 SE, Pentium 3 at 400MHz, 128MB SDRAM, DTL-H2000, DTL-H2010, DTL-H201A, DTL-S2020 (with 4GB SCSI-2 HDD), 21" Sony G420, CD-R burner, 3.25" and 5.25" Floppy Diskette Drives, ZIP 100 Diskette Drive and an IBM Model M keyboard.

User avatar
New Nova
Active PSXDEV User
Active PSXDEV User
Posts: 61
Joined: Oct 27, 2018
I am a: Collector, developper, artist
Motto: RTFM
PlayStation Model: DTL-H2000
Location: France
Contact:

Post by New Nova » 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.
Development PC : Compaq PC, Intel Pentium III 600MHz, 256MB RAM, NVIDIA GeForce4 MX 440 (AGP)
Development Unit : DTL-H2000 board + DTL-H2010 CD-ROM drive
Retail Unit : SCPH-1002 + XplorerFX + caetla + modchip + activity LED mod

User avatar
TriMesh
Verified
PSX Aptitude
PSX Aptitude
Posts: 225
Joined: Dec 20, 2013
PlayStation Model: DTL-H1202
Location: Hong Kong

Post by TriMesh » May 24th, 2023, 3:35 pm

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.

Post Reply

Who is online

Users browsing this forum: No registered users and 6 guests