[petrockblog]

samples are not supported – I have submitted a pull request upstream to enable samples (by putting them in a samples folder in the same dir as the rom)

[petrockblog]

https://github.com/RetroPie/RetroPie-Setup/wiki/runcommand

[petrockblog]

I have uploaded a video that shows the setup and configuration of the ControlBlock together with SNES controllers:

You can find it here.

When you watch that video, do you see a difference to your setup or configuration?

[petrockblog]

I know that we have been in contact via email, I am just posting this here so that others might get help of it as well.
The ControlBlock driver has been updated a few days ago. This update fixes some reported issues with the SNES configuration of the ControlBlock. You can also find an updated step-by-step guide for the installation at https://www.petrockblock.com/2014/12/29/controlblock-power-switch-and-io-for-the-raspberry-pi/#Command-Line_Installation.

[petrockblog]

Maybe you can post an image of your hardware setup? That might give me a chance to make an educated guess for the reasons of this behavior …

[petrockblog]

[quote=116759]
I also plan to connect it to my pi with jumper wire instead of mounting it directly. I read in the documentation that there is a slight voltage drop with in the power circuitry, so you need a good power supply. I was planning to use a 5V 6A power supply like this:
http://www.jameco.com/webapp/wcs/stores/servlet/Product_10001_10001_323425_-1

Will using the ControlBlock to power the pi affect my ability to overclock? Will it affect my ability to power controllers/mouse/keyboard/thumb drive/wifi from the USB?
[/quote]

The MOSFET that the ControlBlock uses is the IRLML6402 (http://www.irf.com/product-info/datasheets/data/irlml6402.pdf). It is rated for a maximum of 3.7 A.
The ControlBlock works with the various overclocking configurations that can be selected from within the rasps-config tool.
If your other USB devices work well is hard to say for me since that depends on their power consumption behavior.

Hope that helps?

[petrockblog]

I have added information about the used pins of the ControlBlock. You can find it at https://www.petrockblock.com/2014/12/29/controlblock-power-switch-and-io-for-the-raspberry-pi/#Hardware_Interfaces.

Does this answer your question?

[petrockblog]

Even though we had contact via email, I just add the following information so that others also get these information:

I updated the description of the command-line installation procedure in the ControlBlock article. You can find it at: https://www.petrockblock.com/2014/12/29/controlblock-power-switch-and-io-for-the-raspberry-pi/#Command-Line_Installation

[petrockblog]

Hi everyone, you can find the step-by-step guide that Michael mentions above at https://www.petrockblock.com/2014/12/29/controlblock-power-switch-and-io-for-the-raspberry-pi/#Command-Line_Installation. I have added it recently.

I will publish a video series that shows the hardware setup, installation, and configuration with RetroPie this afternoon. Hopefully, that gives you some hints to solve your issues!

[petrockblog]

There are some config issues with mame/advmame as they look for roms in the other location – this was overlooked when arcade was added. Need to think of a solution for those.

[petrockblog]

glslp (the glsl are included by them afaik)

[petrockblog]

ignore what I said regarding being overwritten – if you make a new script as above that is fine – I had thought you were overwriting the main doom launch script which would get changed back. You can choose either way.

[petrockblog]

I wouldn’t change it like that as it will get overwritten.

Instead edit

/opt/retropie/configs/doom/emulators.cfg and add a new line for example lr-prboom-doom2=”blah” with the launch config, you can switch between doom2 / doom from the runcommand script then.

[petrockblog]

you can’t cycle through them currently unless you copy a selection of shaders from the subfolders in /opt/retropie/emulators/retroarch/shader to /opt/retropie/emulators/retroarch/shader or change the shader location and put a selection of shaders in there.

See the retroarch ticket.

I may add some workaround for this by symlinking a small selection of shaders to cycle through, but for now you have to use the config editor, manuall config, or copy the selection yourself.

[petrockblog]

I just tested it and it works here – if you enabled a shader for a specific system config – post the config please (via pastebin.com or similar) (eg configs/nes/retroarch.cfg)

[petrockblog]

have you tried shader configuration from the “config editor” ? (Edit retropie/retroarch configurations on the retropie section of ES)

[petrockblog]

https://github.com/libretro/RetroArch/issues/2688

[petrockblog]

you could try another SD card. Have you had this RPI working previously with this card ?

[petrockblog]

the power supply. how are you powering the raspberry pi – what does the power supply say “5v 1a” or “5v 2a” etc. try booting with no usb devices connected.

[petrockblog]

it gives the commands to refresh – so you can just type what it suggests (sudo systemctl daemon-reload). Wifi configuration is easier by using the retropie-setup wifi config script.

[petrockblog]

Please provide details of PSU – have you tried another PSU ? Have you tried disconnecting devices?

[petrockblog]

please post the output of ~/.emulationstation/es_log.txt after you have a whitescreen

please post the contents of /boot/config.txt

can use pastebin.com for the logs.

[petrockblog]

Thanks! It’s always nice to hear when things go well and people are enjoying the software :)

[petrockblog]

it is saving the gameslists – you need to wait. (you must have a lot of roms)

I may introduce a hard shutdown as it did before – but meta data could be lost then.

shaders do work – but must be configured from the configuration editor. (hotkeys wont work due to a changed file structure)

[petrockblog]

have you overclocked ?

do you have a sufficient power supply?

I would try reimaging – but instability may be due to issues like this.

[petrockblog]

Worked fine with my ps3 controller last time I tested, but will try again.

[petrockblog]

Update to RetroPie 3.5 – make sure you have a “retropie” folder on the drive

[petrockblog]

you plug them in via usb, unplug them, and they pair. then they should pair automatically on future boots.

[petrockblog]

not using the omx plugin now.

the SDL audio driver has volume control though – you could try it

configs/n64/mupen64plus.cfg

change AudioPlugin to mupen64plus-audio-sdl.so

[petrockblog]

rename them to .dat

[petrockblog]

What PSU do you have on your RPI ?

Have you tried using the stick in keyboard mode without xarcade2jstick ?

eg

https://github.com/scottnath/retropie-with-dual-x-arcades

you can use the default layout though and adjust the retroarch.cfg accordingly for player2/player2

[petrockblog]

https://github.com/RetroPie/RetroPie-Setup/wiki/Runcommand

[petrockblog]

On phone so can’t link you but answer is in the wiki. Check FAQ

[petrockblog]

https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=110233

(First hit on google searching for: enable root raspbian jessie)

[petrockblog]

you can adjust the frameskip for a smoother mouse. I think by default it has a frameskip of 3 or so.

[Author]

Posts