Building snes9xTYL 0.4.2me from source

[azrael]

I'm new to the board so first off: Hello Guys!

I'm trying to build snes9xTYL 0.4.2me from source on MacOS X (10.4.10) with the latest PSPSDK ('psp-gcc -v' says 4.1.0). The precompiled version runs pretty fine on my 3.40-A OE PSP and I just replaced the eboot to run the one I compiled.


I had two problems I could solve:

1.) make_version_me (and I suppose make_version_user, too) was somehow wrong encoded - I had to change the line-ending from windows- to unix-style. (For those interested: CRLF -> LF) Otherwise it wouldn't run.

2.) In psp_net.cpp there was a wrong escape-sequence: '\/' should be plain '/'
(One might want to look at: wiki.services.openoffice.org/wiki/Writing_correct_Cplusplus )


And two I could not:

1.) I got several error-messages from ./psp/adhoc/stubs.s and have no idea if there are to ignore or if they cause my other problem...:

psp/adhoc/stubs.s: Assembler messages:
psp/adhoc/stubs.s:19: Warning: ignoring changed section attributes for .text.stub
psp/adhoc/stubs.s:50: Warning: ignoring changed section attributes for .text.stub
psp/adhoc/stubs.s:60: Warning: ignoring changed section attributes for .text.stub
psp/adhoc/stubs.s:88: Warning: ignoring changed section attributes for .text.stub
psp/adhoc/stubs.s:111: Warning: ignoring changed section attributes for .text.stub
psp/adhoc/stubs.s:126: Warning: ignoring changed section attributes for .text.stub
psp/adhoc/stubs.s:137: Warning: ignoring changed section attributes for .text.stub

2.) Though it compiles to an eboot and runs. It crashes after few seconds in every game. For example: I can see the "Super Mario World" title-screen and then it crashes. I get the following "bluescreen":

I regret to inform you your psp has just crashed
nuts happens... : - (
Exception Details:
Exception - Bus Error (data)
EPC - 08A08F3C
Cause - 1000001C
Status - 60008613
BadVAddr - 81810860

Which is followed by a pile of numbers I don't want to write down.



(Btw: is there a simple way to dump the BSOD into a file? - The screenshot-plugin for OE doesn't seem to work.)

Could somebody give me a hint how to solve this and get it running?
Or maybe what both the compile-errors and the Bluescreen mean - so I can try to fix it myself...?

That would be great - Thanks a lot in advance!
Azrael

[manias]

u could take a picture of the screen with a camera / webcam

[azrael]

...if that bunch of numbers helps I surely could!

See first post!

[Tinnus]

I think I remember the newest PSPSDK having problems with snes9xTYL... check the recent topics, there's one or two very like this one.

[azrael]

Well yes - I found these two before:
building snes9xTYL-0.4.2 from source
Errors Building snes9xTYL-0.4.2

But it seemed to me, that the first had problems because he uses a different SDK and the second just didn't setup the Libs correctly (At least that's how I (and you ) would read his compile-errors).

[azrael]

Hi again,
though nobody seems to be interested:
I got rid of the compiler-errors by using the latest common.s (in ./psp/adhoc) from the ps2dev-svn ...

It's a little hard to find because they renamed it to pspstub.s - it's here!

Now the eboot does compile without flaws - but it still crashes with the Bluescreen above...
So still: If anybody could give me a hand...



EDIT:
I just found a thread over at ps2dev.org about how to find the line of code that caused an exception.

According to that the error should be in tile_psp.cpp on line 516 ...
Having found that I tried to run with software-only graphics, which in deed works. I suppose that means it's a problem in the psp-accelerated graphics-mode only.

...but I got no idea what happens: I think I'll give up on it.

[twoleeland]

I have same problems compiling the SNES TYL-source.
I figured them out with long searching. (Take about 10 hours only for search)
The only problem is when i start the eboot.pbp of snes it crashes with known bluescreen.
Don't know why?
Can someone help?

[azrael]

twoleeland said:

I figured them out with long searching. (Take about 10 hours only for search)

...that's why I posted what I found out here, so nobody has to do the same searching I did. Though I couldn't get any further by now. And I think I won't try anymore.

It would have been nice if someone with more knowledge would have had a look.