For awhile I have been trying to make a GAMEBOY and Raspberry Pi Mod.
My last post showing some real progress and installation of the software.
Today I will write a better guide for myself and others so they can learn from my mistakes.
If you follow this guide for setting up your SD cart this progress will take about 1,5 h to complete.
(guide is below show and tell 🙂 )
Warning: I still have to remove a error that i getting but i din’t find a solution for this atm: ”At random times i get: alsa lib pcm.c 7843: (snd_pcm_recover) underrun occurred” not when playing a game only if i am in the front end and during boot….
Lets start with show and tell:
Hardware used:
Gameboy case, wires, tact switches, empty PCB, power bar, cheap speakers and a Dremel
Below are some pictures of my GAMEBOY Pi that is mostly finished.
Things todo build in the speaker and power bar remove some plastic form d-pad because its fits to well…
But thinking of making a custom cartridge to slide in to the slot of the Gameboy.
(not my Picture just for show my version will have a power-bar also. How? wait and see )
Pictures:
How it looks now:
Build in Wifi and dongle for keyboard for now, in the future I gone extend one port to the side.
Ethernet is still available but don’t use a High-end cables, my own made utp cable works perfect 🙂
The mod of the case….
conversion:
I started this project awhile back so if you want to do this. Do little things, one thing at the time.
Don’t start doing lots of things at once because in the end you will need to change or rework it again…
(Tip from Ben Heck and now from me 😀 )
The Arivale of the FFC extender and extra Cable
After i got the ffc-cable to extend my PiTFT 2.8 inch from ada fruit.
Here are some progress pictures:
You need controls.
I have rebuild the pcb for the controls because this way its much stronger then before. And the board looks more like the original Gameboy PCB haha.
Also i made some video’s that show the different stages of the build :
RetroPi and PiTFT from Ada fruit test!
(I have 4 Pi’s: two models B and one Model 2B+
RetroPi and PiTFT and DIY Joystick test!
Testing the tact switches…
RetroPi and PiTFT and DIY Joystick test 2!
More testing of the tact switches… 😀 Mario is fun hahaha.
For those how notice i have some strange glitching in my screen in the video’s above.
This is because at that time my raspberry pi setup was not perfect. Not that its now LOL.
But the screen glitching is gone…
GAMEBOY PI Semi complete Test!
This is my last video i made for now showing it closed (taped down) and using the original GAMEBOY buttons on my custom pcb using those 8 tact switches.
If I have time i will make a new video showing it closed with screws and without glitches in the screen.
Boot in Raspberry pi, let it boot in to startx and then quit it to command line
And launch Raspi-config: (sudo raspi-config)
Always start by expanding filesystem ( most builds do this but i recommend it anyway)
The choose 3 boot options and select console autologin.
Last things: 1 Overscan disable, 4 SSH Enable, 5 Device tree Enable, 6 SPI 7 I2C and 8 Serial disable, 9 Audio force 3.5mm headphone jack.
Side note for those how need Tochscreen: I disable 6, 7 and 8 to get more Gpio pins working
but this will disable touchscreen control. But this is not needed for this project anyway. And also you can make another SD card that can use the Touchscreen interface but you will lose the Gpio pins that use SPI, I2C and Serial.
And check if everything is still working if you want to add your own controls continue below
Adding Controls:
cd /~/ git clone https://github.com/adafruit/Adafruit-Retrogame cd Adafruit-Retrogame
nano retrogame.c
Edit the file retrogame.c, looking for the table called ioStandard and the input.h table. Each line in brackets represents one pin on the GPIO header and a corresponding key code.
The full list of available keycodes can be found in /usr/include/linux/input.h
You’ll need to be careful in your GPIO pin selection…some are used by the PiTFT display, others have certain reserved functions. Any green GPIO pin is free to use…yellow pins may be okay with additional setup. If you’ve configured a tactile button on the PiTFT for shutdown, that pin is unavailable for game controls.
One wire from each button connects to a GPIO pin, while the other wire connects to an available ground pin (GND). The 2.8″ PiTFT boards have an extra header breakout for the first 26 pins…for the remaining pins, you’ll need to get clever with female jumper wires on the exposed part of the Raspberry Pi GPIO header.
That is why i disable I2C and Serial so i can use gpio 2, 3, 14 and 15. Made a mistake and was easier to use gpio 14 and 15 instead. otherwise i would only disable I2C…
After editing, compile and install the code with:
make retrogame sudo mv retrogame /usr/local/bin
Test fist before making something boot that is not working.
sudo /usr/local/bin/retrogame &
It works!
sudo nano /etc/rc.local
Reboot and you should now have “virtual” keys associated with GPIO buttons.
Or make it more fancy:
HOW TO HIDE BOOT TEXT:
sudo nano /boot/cmdline.txt
Add splach screen
Adding a splash screen can be done from in retropie so this is optional. but this way you know what is changed in retropie to show the splashscreen at start up, same method.
Custom Splash Screen for Raspberry Pi
This is a quick and dirty solution for an unanimated custom splash screen during boot.
First of all, you need to install fbi:
apt-get install fbi
Copy your custom splash image to /etc/ and name it “splash.png”
example code:
sudo mv splash.png /etc/init.d/
Next, create an init.d script called “asplashscreen” in “/etc/init.d/”.
sudo nano /etc/init.d/asplashscreen
I chose “asplashscreen” with an “a” at the beginning to be sure it starts first.
#! /bin/sh ### BEGIN INIT INFO # Provides: asplashscreen # Required-Start: # Required-Stop: # Should-Start: # Default-Start: S # Default-Stop: # Short-Description: Show custom splashscreen # Description: Show custom splashscreen ### END INIT INFO do_start () {
/usr/bin/fbi -T 1 -noverbose -a /home/pi/RetroPie/splashscreens/splash.png exit 0 }
If everything is correct you still boot in console but now is everything setup to start retropie
Start by typing:
emulationstation
After the startup you need to setup you fresh made controls by pressing one of the keys and then follow the onscreen text. Skipping by holding down one button.
After that your done and can start adding roms, you have 2 options for this by usb or by samba.
So you probably need to set that up 2 lucky for us you can do this from in emulationstation
choose retropie setup from the menu.
The let it boot directly in to emulationstation. Next Samba: Oleee
and if you did’t follow my splashscreen install you can choose it here:
For now i leave this project to rest, i am glad whit the progress that i made.
also after 6 months I can close the case 😀 hooray!!!
Recap of what to do:
-Fix asla error….
-Build power cartridge for power.
-Build in speaker
-Extend usb to connector port and replace it by usb.
Back in the hay days of the ps3RealPsDevContacted me to test his new ps3 tool.
Its a all in one tool for ps3 in a nice GUI.
He contacted me because i have been checking different build versions of eboot.bin files.
Results of scetool:
I shared a lot of info on forums like psx-scene.com ps3hax.com and i got his attention.
On twitter he asked me to beta test the final version of his tool.
I never beta tested a program my self and found it a great honor to do.
Over twitter i told him my results and he updated the bugs afterwards.
This was a great experions and found it very cool.
Below is the release info on psx-scene.com where you can download the tool your self.
He has also stated he plans on releasing the source code to his project at a later time, so others may continue the work he started. He has told me the reason he wishes to stop work on this project, is so that he can move on to develop other projects. Below you will find all 12 releases, all of which were released here at PSX-Scene first. Thanks PsDev!
It has been fun making this program, it has gone threw 12 awesome updates. I’m sad to stop working on it, but I’m happy to see what you guys can continue to make it into. I will release the source code, but not today, not in this thread. lets leave that for another time and focus on this release. This is also the most stable version, all features have been tested not only by me but other people too, (Dcnigma, Industerialcode) and all features work properly.
CHANGES:
scetool v0.28 added
New keys added to keyset
New script for EBOOT resigning
New file system layout
Removed do it button
Now everytime you select a option from one of the drop down menu it does that option right away
Removed SELF tool
Cleaner
Every option has its individual message box completion of operation
There is a new way that the file system works. There is a individual folder for all the tools (PUP Tools, scetool, Core_os Tool ect) And when you want to use the tool just place the file in the correct folder and use the GUI. This system is cleaner and allows me to not use as much code.
there is a script in the scetool folder called fix. This script is what can be edited to your standards for the EBOOT resigning. I did this so if you want to sign for 3.41 ect or change compression or anything just edit the script and run the GUI no need for new update, much more efficient
@echo off
FOR /F "tokens=1,2 delims= " %%A IN ('scetool.exe -i EBOOT.BIN') DO (
if [%%A]==[ContentID] set CID=%%B
)
scetool.exe --decrypt EBOOT.BIN EBOOT.ELF
rename EBOOT.BIN ORIGINAL_EBOOT.BIN > NUL
pause
scetool.exe --sce-type=SELF --compress-data=FALSE --skip-sections=TRUE --key-revision=0A --self-auth-id=1010000001000003 --self-add-shdrs=TRUE --self-vendor-id=01000002 --self-type=NPDRM --self-fw-version=0003005500000000 --np-license-type=FREE --np-content-id=%CID% --np-app-type=EXEC --np-real-fname=EBOOT.BIN --encrypt EBOOT.ELF EBOOT.BIN
pause
del /Q EBOOT.ELF > NUL
scetool -i EBOOT.BIN
pause
There is no more “Do It” button, since I change the way the files are modified I thought I will just make every option a button it self, si when you click the option you like from the drop down menu it will do the operation
Note* After click may take a sec for the operation to start be patient.
My version is almost a one 2 one copy of Peter his program the only different aspect is: custom screen options.
My dad complains that after he upgrade his video card he could get Peter’s version working correct.
So i looked at the application and told my dad that i could code that in one day and make it better.
I took this challenge because i written some code for custom screen options before.
My version got all basic functions that peter’s version got i left out the RGB options because otherwise i couldn’t make the dead line of one day 😀
If you select view set location Testbeeld you get another window and you can drag it to the desired screen/location…
after hitting the Set button the location is fixed.
If you hit the fullscreen button it will load the Test card/screen on that location.
I solder the Velleman K8019 kit together and made my own software:
And now let the creative thought flow!
Make a more complex program ^_^
This is a screen of the official Velleman program:
Its used to program the RFID reader you can change the door open system and add or remove cards from the system.
If you write your own program you can gather the data from the serial port and make your own database and give it functions.
For now I don´t have the need for the door unlock feature but its handy for future project.
Example : Turn on pc by presenting rfid card