psxsdk Caetla/Catflap issue

All other SDK help, questions and information
Post Reply
danhans42
BANNED
BANNED
Posts: 329
Joined: Nov 28, 2012

psxsdk Caetla/Catflap issue

Post by danhans42 » August 20th, 2017, 12:25 am

Hi All,

Does anyone use psxsdk with catflap/caetla?

Every EXE I send to my PSX that is built using psxsdk comes up with the following error

Image

Obviously some of the psxsdk examples have data files on the CD, so I didnt bother trying those. I read the notes in the readme and made sure I had a CD in the drive, still no bacon.

Image


Any ideas?
You do not have the required permissions to view the files attached to this post.

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

Post by Shadow » August 20th, 2017, 3:20 am

Looks like the stack was setup correctly, and it then tried to load something into V1 but after execution of a particular function it's done something wrong. No idea why the PC register is 0xFFFFFFFF. That's odd. It looks like something wasn't loaded correctly into an address it was expecting to pull data from.
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
nocash
Verified
PSX Aficionado
PSX Aficionado
Posts: 541
Joined: Nov 12, 2012
Contact:

Post by nocash » August 27th, 2017, 7:36 am

What's that RA=80020070h from? Is that something in your uploaded EXE code (or is it an address from the caetla rom)? If it's from the EXE, disassemble the code at 80020070h and up, and the function being called at 8002006xh, either there it must have crashed. Or if it's from the ROM, try to disassemble the same code in there (eg. if loading the ROM works well enough in no$psx to copy code to 800200xxh).

Or, make sure that the EXE file size is a multiple of 800h. And compare the 800h-byte EXE header entries with other non-psxsdk EXE files (especially the entrypoint, stack pointer values, zerofill area, and the ASCII ID).

Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests