[petrockblog]

Really glad to hear!

[petrockblog]

I would be interested in that as well. However, I do not have the resources and time for that so that everyone is invited to contribute here. The script uses some RaspberryPi specific emulator ports, which would have to be modified accordingly (I guess).

[petrockblog]

The runcommand script changes the resolution down to VGA when you start a ROM and use HDMI for video output. The original resolution is restored when exiting the emulator. This increases the speed a lot. I have not tested the runcommand for every emulator, that is why the runcommand script is not used for every system.

[petrockblog]

I am currently observing the same behavior with gpSP. Maybe there have been some recent updates of the Raspbian graphics libraries!?

[petrockblog]

Did you use the source-based or binaries-based installation?

I would suggest to disconnect the USB game pad to exclude this possible source of errors.

[petrockblog]

Please give some more details that might help others to understand what exactly lead to this error (chosen emulator, ROM name, hardware setup, your interaction with the RPi, etc)

[petrockblog]

Maybe you are also facing the same issue as described at https://github.com/retropie/RetroPie-Setup/issues/175.

[petrockblog]

There is an approved list of compatible USB sound cards at http://elinux.org/RPi_VerifiedPeripherals#USB_Sound_Cards.
If you get such a card, it would be great to hear about the sound quality here :-)

[petrockblog]

A possible next step would be to SSH into the pi and disable the splash screen with the Setup Script.
You could also try to start a NES rom directly from command line. The commands that Emulation Station uses can be found in /home/pi/.emulationstation/es_systems.cfg.

[petrockblog]

Did you expand the root filesystem via sudo raspi-config? Maybe there is no space left after you have copied the ROMs.

I have tested the image with HDMI video output. You should be able to SSH into the RPi.

[petrockblog]

You need to make sure that your ROMs have the same extensions as used in /home/pi/.emulationstation/es_systems.cfg.

[petrockblog]

Just to be sure: You used the SD-card image?

Also, does everything boot and start fine, when you do not have the RetroPort USB connected to the RPi?

Maybe it works, if you use an active (i.e., a self-powered) USB hub to connect the RetroPort USB. This is just a guess, though.

[petrockblog]

I will have a look into the DGEN problem within the next days. You need to copy ROMs into the corresponding directories. Emulation Station shows only the systems for which ROM files are available.

[petrockblog]

You misspelled the target directory ;-) It is /etc/ (see also https://www.petrockblock.com/?post_type=topic&p=1314#post-1314)

[petrockblog]

Great – I will add it to the script and downloads!

[petrockblog]

how do you update?

[petrockblog]

Yes – you can use the source-based installation and just select DGEN and the PSX emulator!
I plan to update the script and downloads at the beginning of next week. Maybe something related to those emulators has changed.

[petrockblog]

I like your project!

If there is an article or blog post with details I could put a link to that on this website.

[petrockblog]

That looks great!
Do you also provide the ES theme?
I already saw the new issue at Github. My plans are to include the emulator in the RetroPie Script at the beginning of the week.

[petrockblog]

The critical parts of the source code can be found in the lines starting at https://github.com/petrockblog/SNESDev-RPi/blob/master/src/main.c#L200.

[petrockblog]

Making SNESDev more configurable is actually on my to-do list. I do not know when exactly I will find time for that though.

[petrockblog]

SNESDev and the gamecon driver must not be installed at the same time, because thez do interfere with each other when accessing the GPIO pins. I have no experience with pikeyd, but it sounds as if it also accessed the GPIO pins. This would mean that only one of these three programs must run at the same time.

For debugging, I would also suggest to disable the custom splashscreen to see the console output during boot.

[petrockblog]

For troubleshooting, you could exit Emulation Station by pressing F4 and look at the console output. Maybe that gives some other clues.

[petrockblog]

It sounds as if you have installed the ROMs with root permissions only – you need to change the owner and the group of the ROMs directory (and, to make it easy, the rest of the RetroPie directories as well) to “pi”. You can do this with the commands sudo chown -R pi /home/pi/RetroPie/ and sudo chgrp -R pi /home/pi/RetroPie/

[petrockblog]

Emulation Station must not be started from LXDE, because of the way Emulation Station uses the graphics device!
You need to exit LXDE, starting Emulation Station should work from command line then. If you enable the autostart on boot for Emulation Station, you need to disable the autostart of LXDE as well.

[petrockblog]

What was your configuration before that? Did you boot into LXDE or into the command shell?

You should still be able to use SSH to log into your RPi. Could you post the content of the file /etc/inittab here? That is where the critical changes were probably made.

[petrockblog]

The current binaries are from the beginning of May. Unfortunately, I do not follow the development of all components that can be installed with the RetroPie Script so that I cannot tell you the differences to the most recent versions.

Since it takes a very long time to do the installation with the sources, I do recommend to start with the binaries and to use the source-based installation only for selected component later on, e.g., in case of updates or troubleshooting.

[petrockblog]

A list of possible keys that RetroAch understands is given at https://www.petrockblock.com/forums/topic/xarcade-usb-keyboard/#post-1714. Hope that helps!

[petrockblog]

If you are using the composite video out, you need to disable the variable HDMI resolution from within the RetroPie Setup Script.

[petrockblog]

Are you using the gpSP emulator, which comes with the recent version of the RetroPie Setup and SD-card download?

I have “Zelda – Minish Cap” running with full speed and perfect sound.

[petrockblog]

Nice – I am glad to hear that it is working now!

Have fun!

[petrockblog]

Ok, a few more ideas:

– You need to delete the file /home/pi/.emulationstation/es_input.cfg to have Emulation Station show the input configuration screen again.

– Also, do you put the crimp connector onto the pin headers with the right orientation? GND should be on the outer two pins as shown in the diagram attached to this post.

– There is a program for explicitly testing the button located in /home/pi/RetroPie/supplementary/SNESDev/supplementary/testButton/. If this directory does not exist,you need to install SNESDev together with the BCM library via the source-based installation of the RetroPie Setup Script. If you select only SNESDev and the BCM library this will take only a few minutes.

– Orientation of the adapter itself: The pin header has to point to the inside of the RPi.

Maybe one of these points give you a hint?!

[petrockblog]

Hmm, I did not observe sound issues over HDMI at all so far. Maybe you want to try out one of the other two SNES emulators (SNES9X, PiSNES) that also come with the SD-card image or can be installed with the RetroPie Setup Script.

DGEN can be configured with the file /retropie/configs/all/dgenrc by default.

[petrockblog]

Hi,

I need your help in order to improve the articles and information that you are reading. If you have any suggestions or any open questions, I would be glad if you could point me to the specific points in the articles where you would expect certain kinds of information! I am also glad that we are talking right now.

If you have the RetroPie GPIO adapter (https://www.petrockblock.com/2012/10/21/the-retropie-gpio-adapter/), the simplest way for enabling the button would be to
– use the Sd-card image
– Enable SNESDev from within the RetroPie Setup Script
– do not enable the gamecon driver and SNESDev at the same time, because both access the GPIO pins and they do interfere with each other.

If you press the button 3 times, the press of the ESC key is simulated. If you press the button 5 times, the shutdown command is executed.

For connecting SNES controllers to the GPIO adapter, the central diagram is given at http://petrockblog.files.wordpress.com/2012/10/wpid-photo-19-10-2012-20011.jpg. If you are sure that the wiring is correct, I wouldn’t suggest to enable SNESDev with the setup script. I have also attached two images to this post that show the wiring between the crimp connector and the two SNES connectors. If you are following the described wiring between the connectors, and you are using the GPIO adapter, and you are using SNESDev and the SD-card image, then things should work!

Btw: The RetroPie Setup Script installs SNESDev in the directory /usr/local/bin. A binary and (optionally) the sources of SNESDev can also be found in /home/pi/RetroPie/supplementary/SNESDev-RPi, but these are not used when SNESDev is enabled with the RetroPie Setup Script.

I hope this helps!?

[petrockblog]

You can have a look at the sources of the RetroPie Setup Script, e.g., at https://github.com/retropie/RetroPie-Setup/blob/master/retropie_setup.sh#L801 to give you an idea about hat might be needed to install a new core.

[Author]

Posts