What you need to know before you start
Making custom homebrew applications for a PSP means writing your own programs and loading them onto the console instead of using official games. This requires a PSP that has been modified to run unsigned code — a process called jailbreaking or modding — plus development tools on a computer, and basic programming knowledge.
The legal status of homebrew development itself is not illegal in most places, but jailbreaking a PSP may violate your device's terms of service. If your PSP is still under warranty, modifying it will void that warranty. You should understand this trade-off before you proceed.
This guide covers the technical steps and tools involved. It does not cover how to jailbreak a PSP — that process varies by hardware revision and is outside the scope of this article. You will need to research your specific PSP model separately.
Key Takeaways
- Homebrew development requires a jailbroken PSP, a computer with development tools installed, and knowledge of C or C++ programming.
- The most common development kit is PSPSDK, which runs on Windows, Mac, or Linux and includes a compiler, debugger, and sample code.
- Your first project should be a straightforward program like a text display or calculator to test your setup before attempting complex applications.
- You load finished programs onto the PSP by copying compiled files to a specific folder on the device's memory card via USB.
- Jailbreaking a PSP voids its warranty and may violate terms of service, so weigh the risks before modifying your device.
Setting up PSPSDK on your computer
PSPSDK is the free toolchain most homebrew developers use. It includes a C/C++ compiler, libraries for graphics and sound, and example code. read it from the official PSPSDK repository on GitHub. The installation process differs by operating system.
On Windows, read the pre-built installer or use MinGW to compile PSPSDK from source. On Mac, use Homebrew package manager to install the dependencies, then compile PSPSDK. On Linux, install build-essential and the required libraries, then compile from source. Each path takes 30 minutes to two hours depending on your internet speed and whether you have the required tools already.
After installation, test your setup by opening a terminal or command prompt and typing psp-gcc --version. If you see a version number, the compiler is working. If you see "command not found", the installation did not complete correctly — check that PSPSDK is in your system PATH.
Understanding the PSP file structure and build process
PSP programs are compiled into EBOOT.PBP files, which the jailbroken PSP can run. Each program lives in its own folder on the memory card under PSP/GAME/ or PSP/HOMEBREW/. The folder name becomes the program's identifier.
Before you compile, you need a build script — usually a Makefile — that tells the compiler how to turn your source code into an EBOOT.PBP file. PSPSDK includes templates for this. Copy the Makefile from an example project into your own project folder, then edit it to match your program's name and source files.
To build your program, open a terminal in your project folder and type make. The compiler will read your source code, check for errors, and create an EBOOT.PBP file in a subfolder. If there are syntax errors, the compiler will print them to the screen with line numbers — fix those errors and run make again.
Writing your first straightforward program
Start with a program that does one thing well: display text, draw a shape, or read button input. Do not attempt a full game or complex graphics engine on your first try. A working straightforward program teaches you how the build process works and how the PSP's hardware responds to code.
PSPSDK includes sample programs in the examples folder. Open hello_world or graphics and read the source code. These examples show you how to initialize the PSP's screen, draw pixels, and handle the controller. Copy one of these examples, rename it, and modify it slightly — change the text, change a color, add a second shape. Compile it and test it on your PSP.
Once you have a working example, you can add features one at a time. Add button input. Add sound. Add a loop that changes what appears on screen. Each small addition teaches you how a different part of the PSP works. This approach is slower than copying a full project, but you will understand what each line of code does.
Loading programs onto your PSP
Connect your jailbroken PSP to your computer via USB cable. On the PSP, go to Settings, then USB Connection, and select USB Mode. The PSP will appear as a removable drive on your computer.
Create the folder path PSP/GAME/YOURAPPNAME on the memory card if it does not exist. Copy your compiled EBOOT.PBP file into that folder. You can also add an ICON0.PNG file (144 by 80 pixels) to display a custom icon in the PSP's menu, and a PIC1.PNG file (480 by 272 pixels) for a background image.
Disconnect the USB cable. On the PSP, go to Game, then Memory Stick, and you should see your program listed. Select it and press X to run it. If it does not appear, check that the folder path is exactly correct and that EBOOT.PBP is spelled correctly.
Debugging when your program crashes or does not work
PSP programs can crash silently — the screen goes black and nothing happens. To see error messages, you need a debugger or a way to print text to the screen. The simplest approach is to add print statements to your code using the pspDebugScreenPrintf() function, which displays text directly on the PSP screen.
Add this function call at key points in your code to see whether the program reaches that point. Recompile, load the new EBOOT.PBP onto your PSP, and run it again. If you see the text, the program reached that line. If you do not see it, the crash happened before that point. Move your print statement earlier and try again.
For more advanced debugging, use a PSP emulator like PPSSPP on your computer. Run your program in the emulator first — it will show error messages in a console window instead of crashing silently. Once the program works in the emulator, test it on real hardware.
Resources and communities for ongoing learning
The PSP Homebrew Development wiki at pspsdk.org documents the libraries and functions available to you. The PSPSDK GitHub repository includes example code for graphics, sound, networking, and file input. Read the examples that match what you want to build.
Communities like the PSP subreddit and the PSP Homebrew forums have developers who answer questions about compilation errors, hardware behavior, and design decisions. Search for your error message before posting — someone has usually encountered it before.
Start with small projects and expand from there. A working calculator is more valuable than an incomplete game. A program that reads the controller and draws shapes teaches you more than copying someone else's full project without understanding it.
Frequently Asked Questions
Do I need to know how to program before I start?
Yes. Homebrew development requires at least basic C or C++ knowledge. If you have never programmed before, spend a few weeks learning the fundamentals — variables, loops, functions, and conditionals — using free online tutorials. Then return to PSP development. Trying to learn programming and PSP development at the same time will be frustrating.
Can I use an emulator instead of a real PSP?
PPSSPP is a PSP emulator that runs on Windows, Mac, and Linux. You can test your programs in the emulator before loading them onto real hardware. However, the emulator does not perfectly match real PSP behavior — some programs work in the emulator but crash on a real PSP. Always test on actual hardware before considering a program finished.
What if my program compiles but does not run on the PSP?
Check that your PSP is jailbroken correctly and can run other homebrew programs. If other programs work but yours does not, the problem is in your code. Add print statements to see where the crash happens, or test in PPSSPP to see error messages. If the program runs in the emulator but not on hardware, you may be using a function that the emulator supports but the real PSP does not.
Can I make games with graphics and sound?
Yes, but it takes more work. PSPSDK includes libraries for 2D graphics, 3D graphics, and audio. Start with 2D graphics and straightforward sound effects before attempting 3D. Many homebrew games exist — study their source code if it is publicly available to see how they handle graphics loops and input.
Where do I find the PSPSDK read?
Visit github.com/pspdev/pspsdk and follow the installation instructions for your operating system. The repository also includes documentation and example code. Do not read from random websites — use the official GitHub repository to avoid outdated or modified versions.