Code debugging without real hardware
Code debugging without real hardware
Hello,
I'm moving the first steps with some sample code with the Psy-Q SDK.
I've never approached console development, so I wonder if it is possible to debug one's code (e.g. printf() statements) when code is run inside an emulator. Tried epsxe and xebra but none of them prints anywhere my printf()s. Xebra has a debug window but I don't have clear how making use of it.
Alternatively, shall I use FntPrint()?
Thanks for any suggestion!
I'm moving the first steps with some sample code with the Psy-Q SDK.
I've never approached console development, so I wonder if it is possible to debug one's code (e.g. printf() statements) when code is run inside an emulator. Tried epsxe and xebra but none of them prints anywhere my printf()s. Xebra has a debug window but I don't have clear how making use of it.
Alternatively, shall I use FntPrint()?
Thanks for any suggestion!
-
Shendo Verified
- C Programming Expert
- Posts: 250
- Joined: Mar 21, 2012
- I am a: Programmer
- Motto: Never settle
- PlayStation Model: SCPH-7502
- Discord: ShendoXT
- Location: Croatia, EU
To my knowledge only no$psx directs stdout to debug window. For other emulators you will have to use FntPrint().
Dev console: SCPH-7502, FreePSXBoot, CH340 serial cable.
-
Administrator Verified
- Admin / PSXDEV
- Posts: 2691
- Joined: Dec 31, 2012
- I am a: Shadow
- PlayStation Model: H2000/5502
Virus Total reports it mainly as a trojan, but I trust no$cash and the emulator is excellent.
It is better than PSXFIN (PSx) and ePSXe, but it still doesn't beat XEBRA by Dr. Hell.
Some games work better under XEBRA than than do on NO$PSX, so NO$CASH has some tweaking to do
https://www.virustotal.com/en/file/dc73 ... 376793443/
To debug, click 'Window' -> 'Debug Messages'.
It is better than PSXFIN (PSx) and ePSXe, but it still doesn't beat XEBRA by Dr. Hell.
Some games work better under XEBRA than than do on NO$PSX, so NO$CASH has some tweaking to do

https://www.virustotal.com/en/file/dc73 ... 376793443/
To debug, click 'Window' -> 'Debug Messages'.
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.
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.
- LocoMJ
- What is PSXDEV?
- Posts: 3
- Joined: Nov 20, 2014
- I am a: programmer, electronic engineer
- Contact:
Sorry for updating this post but I'm very interested in the topic.
Yesterday I installed PSYQ and I played with some examples. But my question is, how could I debug the code? What's the minimum tools/hardware I need?
Thanks!
Yesterday I installed PSYQ and I played with some examples. But my question is, how could I debug the code? What's the minimum tools/hardware I need?
Thanks!
-
Administrator Verified
- Admin / PSXDEV
- Posts: 2691
- Joined: Dec 31, 2012
- I am a: Shadow
- PlayStation Model: H2000/5502
To actually debug properly, you need an official Sony development kit, such as the DTL-H2000, H2500 or 2700. For basic debugging, printf's under NO$PSX works, but if you want something easier, you'll need CAETLA on an Xplorer/Xploder cartridge.
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.
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.
-
Verified
- C Programming Expert
- Posts: 161
- Joined: Oct 06, 2012
- PlayStation Model: SCPH-5502
- Contact:
PCSX-R also allows console output. Just activate these two check boxes on "CPU Config" window:

Could it be possible to modify PCSX-R's source code to allow ELF files with debugging symbols so as to run it using GDB?

Could it be possible to modify PCSX-R's source code to allow ELF files with debugging symbols so as to run it using GDB?

-
Administrator Verified
- Admin / PSXDEV
- Posts: 2691
- Joined: Dec 31, 2012
- I am a: Shadow
- PlayStation Model: H2000/5502
Yes, that's very much possible but it's a bit of work to do so.
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.
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.
Excellent information here. Great post. Thanks for such a helpful share!
Who is online
Users browsing this forum: No registered users and 3 guests