forums.ps2dev.org

[Ghoti]

Hi folks,

I have created some code and some games for the 1.5 firmwares, that code just works fine onwards to the OE versions (tested up to 3.02 OE)
however code that works fine does not work correctly anymore on m33, since I do not want to upgrade to that firmware I am stuck with this problem. Can anybody tell me what function calls and the sort have changed/added/deleted etc.? or is there something else going on?

one thing was that a lot did not work with setting the processor to 333 but when i set it to 222 it worked a lot better but not perfect. Are there more of these kinds of things? I have searched the forum but could not find anything, if i missed something please do let me know.

greets ghoti
_________________
My PSP games:

Boxy II: http://www.ghoti.nl/boxyii.php
Elementals: http://www.ghoti.nl/Elementals.php

[PiCkDaT]

I dont know if this has anything to do with it.. but the newer firmwares (or just the new slim psp idk) only support 2.00+ apps. I dont know if that means you have to code it different though. I think possibly you just change the fw version in the makefile? I'm no expert so dont totally depend on my word lol. I honestly dont know the difference in coding for other versions of firmwares I just do 1.50 :\
_________________
Enlighten me, Reveal my fate -- Follow - Breaking Benjamin

[Istari]

I think that it also needs to be built as a prx before being put in the eboot.pbp

[Ghoti]

So it should be made a fw 2.0 app and it need to be build as a prx?
are there other differences ?
_________________
My PSP games:

Boxy II: http://www.ghoti.nl/boxyii.php
Elementals: http://www.ghoti.nl/Elementals.php

[PiCkDaT]

probably not... except newer firmwares probably means better functions? :) lol
_________________
Enlighten me, Reveal my fate -- Follow - Breaking Benjamin

[CpuWhiz]

Someone should sticky a article like this as a lot of people ask about this. Comments or suggestions would be welcome. If you want to provide links related to this to add in a links selection, that would be nice.

Porting a 1.50 firmware homebrew to 3.xx firmware

3.xx firmwares require your homebrew be in prx format. To get your homebrew in this format, you need to follow a few basic steps:

1. Modify your Makefile - You need to add the following to your Makefile to compile a prx (before the include $(PSPSDK)/lib/build.mak line):

[Ghoti]

Hi

that tutorial is really nice !! Can I use this information on my site? (to help others)
So basicly what you say is you can only run this in higher firmwares, so for game releases there should be a 1.50 release and a 3.x release right?
_________________
My PSP games:

Boxy II: http://www.ghoti.nl/boxyii.php
Elementals: http://www.ghoti.nl/Elementals.php

[CpuWhiz]

[J.F.]

[CpuWhiz]

Sorry, minor mistake there. Thanks for the info and corrections J.F.

Edit: Do you mean PSP_HEAP_SIZE_MAX() from this revision?

[J.F.]

[CpuWhiz]

I had to recompile my toolchain to test that out. PSP_HEAP_SIZE_MAX() works good and I have added it to my guide (and my app). Thanks J.F.

As for the suggestion on VERS and REVS - I already knew I could do that, but thanks anyway.

[PiCkDaT]

I dont think I have a clue since I have only been coding for a couple of days now.. but why can't you run in kernel mode 3.xx? I've got 3.03-C(maybe this is why?) and it works fine.. BUT here is what probably makes it work

[J.F.]

Only 1.50 has a kernel mode exploit for running apps in kernel mode. Nothing else does, so everything else must be a user mode app. If you wish to use something from kernel level, you have to put it in an external library as demonstrated SEVERAL times in the last week in threads here.

[PiCkDaT]

Is it possible to find another kernel mode exploit or is it doomed? jw
_________________
Enlighten me, Reveal my fate -- Follow - Breaking Benjamin

[jimparis]

It's not a question of exploits... we're already able to patch out any checks, otherwise you wouldn't be able to run code at all. Sony has restructured things a bit and it's just not easy (or correct) to run apps directly in kernel mode anymore.

[J.F.]

It think it's better not to run in kernel mode in any case. Sony can't really change user mode without breaking most the games, so sticking to user mode is better for compatibility. If you need something from kernel mode, use the external prx. Then when Sony changes kernel mode (like with 3.71), you just have to change the prx, not the entire program.

[ppyyf]

[J.F.]

[Be3f]

If hb is compiled for the high fw, eg:

[Be3f]

[adrahil]

Yeah.

The only REAL requirements are:
- EBOOT.PBP has to be in usermode (can be also an elf... but recommended t oadd BUILD_PRX=1 to makefile, along the EXTRA_TARGETS=EBOOT.PBP, and don't forget to expand stack)
- Don't call kernel stuff in usermode apps (and vice versa)

But apart that, you can make PRXs from kernel or usermode, as you wish :) Just don't forget to load them to the correct memory partition.

[Be3f]

Thanks! And 20480 Kb is the absolutely maximum for psp-fat, right?
_________________
00000110 00000110 00000110

[Hellcat]

I sucessfully used PSP_HEAP_SIZE_KB(21000) even on a Fat.... but that's pretty close to the limit, tried a bit more, and got errors then....

AFAIK this also applies to the Slim, since the additional memory is an additional mem partition and does not simple expand the "normal" memory we are used to use....

[adrahil]

There is a possibility to get more mem on the slim thanks to M33 firmwares :) But to maintain compatibility with Fat, it's better to keep to the limit.

[baffo]

I've read and I'm currently reading as much as I can find on prx related threads, and try to make things work on my sdk/psp with poor results, mainly because I've got these main big question without any clue, some points I found lead me to confusion:

1) I have to extract any kernel command in a separate c file, a completely dissociated c source with its own makefile (that build_prx=1 thing), that let me have a .prx file. Then I need another "main" c source that have to import those previous kernel calls. I'm trying this way but all I get is a psp crash.

2) when I add the build prx =1 in makefile I get both the pbp and the prx, working together and ready to be placed under game folder (afaik is impossible, with one source only)

3) both main makefile and prx's must have build_prx=1, or only the prx makefile

4) I'm a jerk and one can play directly the prx without an eboot (O__O sounds stupid, but I found a thread here telling to play a prx)

5) no prx needed, if I switch to user mode and add in my main.c makefile build_prx=1 I get my eboot.pbp ready to go (and the exports? doesn't make sense 4 me, again I found a thread here with an example made this way)

6) I'm very very jerk because prx has not to stay in the eboot folder but in SEPLUGINS (or wherever else) and be enabled from recovery menu (I tried but always get crashes)

7) someone wrote "you can try playing the .elf" is it possible???? anyway I don't want an "elf" executable...

I tend to believe I have to code my pretty main.c with its own makefile, including the needed prx-file include
after compile I expect to obtain just the runnable eboot. (without prx=1 in makefile, I want a pbp here?)
Then I have to begin a brand new C project, provide the needed kernel calls, add the prx=1 thing in makefile and expect
to obtain my module.prx, and some exports file.
Done this, I copy the pbp and the prx in a nice game/371 folder and play the eboot (sometimes I get also a further
"corrupted data" icon, don't know if it's normal). Looks pretty easy, but after gameboot my psp crashes. :P

[sakya]

Hi! :)

You can put all your kernel command in a single prx
You have to compile the prx and the app separately.
Both prx and app needs BUILD_PRX = 1

Here there's a little sample:
http://www.sakya.it/downloads/testPer371.rar

To compile it:

[adrahil]

[Be3f]

Also, to build a 3.XX EBOOT, you need to edit pspdev/psp/sdk/lib/build.mak - delete strip_ here:

[J.F.]