• Steam recently changed the default privacy settings for all users. This may impact tracking. Ensure your profile has the correct settings by following the guide on our forums.

PSP Programming: Setting up the environment

probably go and get yourself a coffee, a bagle or two, or some doughnuts, and play with your favourite console, because it WILL take a while..
 
Sorry for asking again, but where can I get a toolchain for PSP Version 1.00 or PSP Version 1.50?
 
its already for 1.50. Why would you want that anyway? and it takes VERY long to run. Aske roe-ur-boat. We started it up at the same time and it took a couple hours maybe more, even on a freakin supercomputer it would take at least an hour and a half.

The scripts you have to run before it are equally long, so i suggest that you do that, then leave the toolchain script running overnight.


Question, is anybody else having any problems with the mpfr script? Everytime i try to run it, at the end it keeps failing and never actually installs.
 
angelsniper45 said:
its already for 1.50. Why would you want that anyway?
Click to expand...

Making kernel mode PRXs is alot easier on Version 1.50, so that is why I need to develop something for Version 1.50.
 
roe-ur-boat said:
Kernel PRXs can be run in the latest firmwares.
Click to expand...

Well, I'm thinking of working on a kernel PRX (or just an ELF) that launches from ELF Menu or NandTool, so I do need to develop for Version 1.50.

Besides, don't user PRXs and kernel PRXs have to be in seperate PRXs in the 2.00+ Versions? (unlike Version 1.50 PRXs that can have kernel access in one PRX.)
 
no, thats past 3.0 if im correct.

nvm i got the mpfr installed
 
I've got one question.
How come in OFW, when something is created for, say firmware 3.40, it can be run on any OFW update after that.

However, in CFW we constantly have to update the homebrews. (whenever theres a new firmware) Why is that?
 
angelsniper45 said:
no, thats past 3.0 if im correct.

nvm i got the mpfr installed
Click to expand...

Well Version 2.60 and Version 2.71 already had seperate user and kernel PRXs, so I'm guessing s0nY did that in Version 2.00

mortalinstincts said:
I've got one question.
How come in OFW, when something is created for, say firmware 3.40, it can be run on any OFW update after that.

However, in CFW we constantly have to update the homebrews. (whenever theres a new firmware) Why is that?
Click to expand...

Well, I don't know for sure, but I know that's a question that can be easily answered at lan.st.
 
mortalinstincts said:
I've got one question.
How come in OFW, when something is created for, say firmware 3.40, it can be run on any OFW update after that.

However, in CFW we constantly have to update the homebrews. (whenever theres a new firmware) Why is that?
Click to expand...
Not all homebrew have to be updated every time a new firmware comes out, it depends on what functions it uses. There were issues in 3.71(perhaps 3.60 too?) with the lack of a nid resolver but that was all sorted out in the firmwares following it.
 
roe-ur-boat said:
There were issues in 3.71(perhaps 3.60 too?) with the lack of a nid resolver but that was all sorted out in the firmwares following it.
Click to expand...

It was 3.71 that had the major problems. Also, 3.60 kernel was basically like the 3.52 kernel, except it uses PSP Slim hardware modules; so it didn't give developers that much of a problem when they homebrewed for it.
 
Because of the kernel change, official firmwares automatically check for the encryption signature. Whereas since CFWs dont have that check, that means we have to go through our code and rewrite that part.
 
angelsniper45 said:
Because of the kernel change, official firmwares automatically check for the encryption signature. Whereas since CFWs dont have that check, that means we have to go through our code and rewrite that part.
Click to expand...

I know the signature part. I was asking why it wasnt compatible with the new firmware.

and i just didnt post something like this on www.lan.st (which i am already a member of) because i thought it was a too noobish question to ask to all the great developers who hang around over there... :wink: Not like we have any less great developers who hang around over here...

but i was just more comfortable asking the question here... :blushing:
 
Its because they update the signature to, im sure they update all of that stuff secretly without the general public knowing.

what is the differnece between the two differnet text types? Is it just so windows users can use DOS on it?>

Edit: Sorry for double post, didnt realize i was the last one who posted :rolleyes:
 
mortalinstincts said:
I know the signature part. I was asking why it wasnt compatible with the new firmware.

and i just didnt post something like this on www.lan.st (which i am already a member of) because i thought it was a too noobish question to ask to all the great developers who hang around over there... :wink: Not like we have any less great developers who hang around over here...

but i was just more comfortable asking the question here... :blushing:
Click to expand...

yh thats why i never signed up, i ask all my development q's here and get no answer lol, i never signed up cause i say the ultimate hall of shame :blushing:
 
roe-ur-boat said:
When it's finished you are ready to start compiling code for the PSP. Documentation of the functions in the PSP SDK is available HERE. I will explain in the next tutorial how to create and compile a basic program.

If anyone has any questions or suggestions just post below. Also, if anyone wants screenshots included, just say the word. The only reason I didn't include them now is because of my dial-up.
Click to expand...

the link for the documentation of the functions in the PSP SDK is broken..and pls can u update this thread with the tutorial on how to compile a basic program?? pls..
 
You must log in or register to reply here.
Back
Top