Printable View
I think you're right, where you could probably re-assign the flash so that the PSP thinks it's the memory stick. Or maybe pack the EBOOT into an ISO structure, and mount the ISO. I haven't used Project4 yet, but doesn't it run ISOs?Zitat:
Zitat von Auraomega
Or maybe the restriction for sceKernelLoadExec is in a 3.xx PRX, and you can maybe load the 1.5 PRX and use that function instead.
I'm not really an expert in the way the PSP handles files and executables, so I can't offer that much help.
Well I just tried the re-assigning idea, and I got an error with that, so thats yet another idea gone. Project4 can run the I word yep, I will definatly try that as I hadn't thought of that previously, only question is, how do I actually do so? I'll also have a dabble in a little while at trying to load 1.50 stuff instead of 3.XX, if that works its a start, but it still won't be very Slim friendly (still, a start is a start and it may set me on the right path).Zitat:
Zitat von Judas
Thanks again.
-Aura
http://forums.qj.net/f-psp-homebrew-...mat-46926.htmlZitat:
Zitat von Auraomega
That's how to convert a PSP to an ISO. The ISO will be at least double the size using that method. Unless you have Project4 set to run either BOOT.BIN or EBOOT.BIN. Because if it always runs the same one, you don't need the other.
Well I just tested the ISO idea, and again, nothing, I get error 0x8001087, the ISO works fine though because I launched it from the memory stick without issue. Next on the list, 1.50 loading :p
-Aura
EDIT: 1.50 doesn't work either, returns 0x80020149.
Sorry to interrupt Auraomega. :o
I just have quick question as far as a fake security.
I know that there are different snippets of code for if you want to check what firmware is running, or what motherboard is being used.
I tried googling, but to no avail. Would it be possible to create something like what Sony has, where it says, "Firmware X.YZ in use, Firmware X.YZ required."
That way, I could set up my application to only be started if the user is running M33 3.90 or something like that.
Yep, if you make something to sniff out the arguments passed to vshmain.prx you should be able to find out where this information is kept, then its a simple case of restarting the vsh with those arguments.
The specific function you'll need is sceKernelExitVSHVSH(struc t SceKernelLoadExecVSHParam *param);
Find info for it in psploadexec_kernel.h
-Aura
EDIT: That method is if you want the 100% offical look, if not, you could easily find the version of the firmware with either flash0:/vsh/resource/version.txt or by checking it using a certain function (can't remember which), and just displaying the error in the app itself, this of course looks less professional but is significantly easier.
This is kinda ticking me off..
I can't get my C++ image viewer working (I made this using the tutorial at pspprogramming.com)
The error:
The main.cpp file:Code:psp-g++ -I. -I/usr/local/pspdev/psp/sdk/include -O2 -G0 -Wall -I. -I/usr/local/p
spdev/psp/sdk/include -O2 -G0 -Wall -fno-exceptions -fno-rtti -D_PSP_FW_VERSION=
150 -c -o main.o main.cpp
psp-gcc -I. -I/usr/local/pspdev/psp/sdk/include -O2 -G0 -Wall -D_PSP_FW_VERSION=
150 -L. -L/usr/local/pspdev/psp/sdk/lib main.o graphics.o framebuffer.o -lpsp
gu -lpng -lz -lm -lpspdebug -lpspdisplay -lpspge -lpspctrl -lpspsdk -lc -lpspnet
-lpspnet_inet -lpspnet_apctl -lpspnet_resolver -lpsputility -lpspuser -lpspkern
el -o hello.elf
/usr/local/pspdev/lib/gcc/psp/4.1.0/../../../../psp/bin/ld:graphics.o: file form
at not recognized; treating as linker script
/usr/local/pspdev/lib/gcc/psp/4.1.0/../../../../psp/bin/ld:graphics.o:1: parse e
rror
collect2: ld returned 1 exit status
make: *** [hello.elf] Error 1
The Makefile:Code://First app
#include <pspdisplay.h>
#include <pspctrl.h>
#include <pspkernel.h>
#include <pspdebug.h>
#include <pspgu.h>
#include <png.h>
#include <stdio.h>
#include "graphics.h"
PSP_MODULE_INFO("Image Displayer", 0, 1, 1); //This names the eboot in the XMB
#define printf pspDebugScreenPrintf //Defines that huge printf function to just 'printf'
#define MAX(X, Y) ((X) > (Y) ? (X) : (Y))
/* Exit callback */
int exit_callback(int arg1, int arg2, void *common) {
sceKernelExitGame();
return 0;
}
/* Callback thread */
int CallbackThread(SceSize args, void *argp) {
int cbid;
cbid = sceKernelCreateCallback("Exit Callback", exit_callback, NULL);
sceKernelRegisterExitCallback(cbid);
sceKernelSleepThreadCB();
return 0;
}
/* Sets up the callback thread and returns its thread id */
int SetupCallbacks(void) {
int thid = 0;
thid = sceKernelCreateThread("update_thread", CallbackThread, 0x11, 0xFA0, 0, 0);
if(thid >= 0) {
sceKernelStartThread(thid, 0, 0);
}
return thid;
}
int main(){
char buffer[200];
Image* ourImage; //Sets up an image class
pspDebugScreenInit();
SetupCallbacks();
initGraphics();
sprintf(buffer, "ourImage.png");
ourImage = loadImage(buffer);
if (!ourImage) {
//Image load failed
printf("Image load failed!\n");
} else {
int x = 0;
int y = 0;
sceDisplayWaitVblankStart(); //Allows home button to work
while (x < 480){
while(y < 272){
blitAlphaImageToScreen(0, 0, 32, 32, ourImage, x, y); //Prints the image to the screen at X, Y
y += 32;
}
x+= 32;
y = 0;
}
flipScreen();
}
sceKernelSleepThread();
return 0;
}
All help greatly appreciated.Code:TARGET = hello
OBJS = main.o graphics.o framebuffer.o
CFLAGS = -O2 -G0 -Wall
CXXFLAGS = $(CFLAGS) -fno-exceptions -fno-rtti
ASFLAGS = $(CFLAGS)
LIBDIR =
LIBS = -lpspgu -lpng -lz -lm
LDFLAGS =
EXTRA_TARGETS = EBOOT.PBP
PSP_EBOOT_TITLE = Image Example
PSPSDK=$(shell psp-config --pspsdk-path)
include $(PSPSDK)/lib/build.mak
Zitat:
Zitat von Auraomega
Thanks Aura, I will try first with the official way. The function that you mentioned is
If I were to change that to:
Would that work for checking for M33? Or should I be more specific?
You need to compile differently for C++, your makefile should have an extra bit at the bottom:
-AuraCode:./main.o: ./main.cpp
$(CXX) $(CXXFLAGS) -c ./main.cpp -o ./main.o
Aura - No you don't.
Simply add -lstdc++ to the libs line at the very end and your golden.
Try using this makefile:
Code:TARGET = hello
OBJS = main.o graphics.o framebuffer.o
CFLAGS = -O2 -G0 -Wall
CXXFLAGS = $(CFLAGS) -fno-exceptions -fno-rtti
ASFLAGS = $(CFLAGS)
LIBDIR =
LIBS = -lpspgu -lpng -lz -lm -lstdc++
LDFLAGS =
EXTRA_TARGETS = EBOOT.PBP
PSP_EBOOT_TITLE = Image Example
PSPSDK=$(shell psp-config --pspsdk-path)
include $(PSPSDK)/lib/build.mak
Still gives me the same error.. :/
Well that way does work, I got it direct from NeHe's tutorials on GU, but yeah, your way does seem easier.
@spike021:
Nope, you need to do something along the lines of:
Or something to that extent.Code:struct SceKernelLoadExecVSHParam param;
memset(¶m, 0, sizeof(param));
param.size = sizeof(param);
param.unk5 = 0x10000;
param.vshmain_args = [insert args here];
param.vshmain_args_size = sizeof([args buffer]);
sceKernelExitVSHVSH(¶m);
-Aura
Zitat:
Zitat von Auraomega
Hmmm, thanks Aura, I'll give it a try later and see if I can work it, otherwise, I'll just use the in-game method.
Nevermind I got it working now, thanks for the help guys. :D
For some odd reason the graphics.o file had to be deleted.
Seeing as you can't test it yourself, nor get the arguments yourself just yet, I'd probably go with the in game method for now, and use the "offical" method at a later date when your PSP is more homebrewable, I'd find the arguments for you myself but I'm on 3.52, and I know the arguments changed at 3.71 so its not much help.Zitat:
Zitat von spike021
Oh, and incase there was any confusion about getting the arguments, write an app and store it in flash0:/vsh/module/vshmain.prx, int main(SceSize args, void* argp) and simply write a file with the arguments in it to have a look at with a hex editor or something. You may need a few dumps to help find what varies and what doesn't. Oh, and don't forget to load the vshmain_real.prx file under vsh mode, normal module loading won't work.
-Aura
Alright Aura, that will probably help a bit also. I actually do have someone that has been testing the homebrew files and such, but it should be fine. Thanks for the really quick replies too :tup:Zitat:
Zitat von Auraomega
Aura, maybe you could load the EBOOT from the RAM. Load the EBOOT into the RAM, then instead of passing the path to the EBOOT for argp, pass the pointer to the memory address of it.
How is there any way to use the 'bigger than' and 'smaller than' operators in a switch statement?
For example:
Code:int main()
{
int x;
int y;
x = 50;
y = 100;
switch(y-x)
{
case (>10):
//Code
break;
case (<10):
//Code
break;
}
return(0);
}
Nope.
That failed too, as it doesn't load from a file it has no current working directory.Zitat:
Zitat von Judas
Back to the drawing board :p
-Aura
Code:static tablespec const yowzitch_table = { 23, 2, 2, -1, yowzitch_items };
tablespec const *yowzitch = &yowzitch_table;
/* Version and license information.
*/
static char *vourzhon_items[] = {
"1+\267", "1-Tile World: version " VERSION,
"1+", "1-Copyright \251 2001-2006 by Brian Raiter",
"1+", "1-compiled " COMPILE_TIME,
"1+\267", "1!This program is free software; you can redistribute it and/or"
" modify it under the terms of the GNU General Public License as"
" published by the Free Software Foundation; either version 2 of"
" the License, or (at your option) any later version.",
"1+\267", "1!This program is distributed in the hope that it will be"
" useful, but WITHOUT ANY WARRANTY; without even the implied"
" warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR"
" PURPOSE. See the GNU General Public License for more details.",
"1+\267", "1!Bug reports are appreciated, and can be sent to"
" [email protected]"
};
Please someone tell me where its missing :(Code:help.c:54: error: expected '}' before 'COMPILE_TIME'
Shouldn't it be:
I'm probably wrong... but meh.Code:"1+", "1-compiled , COMPILE_TIME"
I doubt it, there is no problem with VERSION.
Oh, well then VERSION would be:
But yeah, I'm wrong :(Code:"1+\267", "1-Tile World: version , VERSION"
COMPILE_TIME is not being #defined.
you're right, the header wasn't included with the source. It's anybody's guess how i'm going to find it. But thanks Archaemic.
hey i found a piece of code on the internet, and i think it will help download a string from the internet. i dont think the person posted the whole code though.
if you no what this does, or how to use it, im having trouble compiling because of stupid errors.Code:def download("www.google.com/logo.gif")
{
def file = new FileOutputStream(address.tokenize("/")[-1])
def out = new BufferedOutputStream(file)
out << new URL(address).openStream()
out.close()
}
thanks
That isn't C++. I think it is Python or Ruby.
o alright, thanks
No way that's Python...but it's definitely not C++. It looks vaguely like Java, but it's not.
It's in a language called 'Groovy', an agile dynamic language for the Java Platform.
I just want to get something cleared up for myself. I understand that the PSP can run Lua, but apparently with this thread it can run C++ as well. I was just wondering if it is limited C++ (like ajax and the PSP browser) or can I code the full deal?
You have the full use of C++ language on the PSP.Zitat:
Zitat von NameTaken33
Not strictly a PSP related programming question, but I respect you guys so I'd prefer asking here.
I'm planning on learning graphics on a PC tomorrow, but I'm not sure what to use - OpenGL or DirectX?
2nd question, which compiler/IDE would be best to use for whichever API.
3rd question, which is the best site to learn from?
I did try the NeHe stuff today, but I'm missing gLaux and I couldn't find it in the quick search I had, I'm just wondering if anyone knows of a compiler that comes with this?
Hope you guys don't mind these questions.
-Aura
1.) I'd choose OpenGL, but me being an Apple guy my opinion may be biased ;). OpenGL is cross-platform though :)
2.) Depends. Visual Studio is a pretty "out-of-the-box" package. I've never used it for anything more than command-line apps though. Code::blocks is very nice also, and I know Yaustar is always recommending it.
3.) Nehe, http://videotutorialsrock.com/, and the free edition of "The Red Book", if you're learning OpenGL. No idea if you plan to use DirectX.
Code::Blocks! A new version of it was released recently:
http://www.codeblocks.org/
-= Double Post =-
What about the standard libraries? I know iostream wouldn't work, but what about <string> or <cmath> or <cstdlib> or <vector> etc.Zitat:
Zitat von yaustar
It's all there. I'm pretty sure iostream does work, but it doesn't actually print text to the screen. It prints it to textfile created for console output.
OpenGL, definitely. It's not bound to Windows.
And yeah, Code::Blocks.
How do I convert decimal to float?
I got float to decimal though.
What? floats hold decimal values. Do you mean double to float?Zitat:
Zitat von Anti-QuickJay