[petrockblog]

This is fixed now – if you update the script, then update the gngeopi emulator it should sort it.

as this code is now part of retropie, please open new tickets for any issues.

thanks.

[petrockblog]

what version of retropie ? When did you last update ?

Are you running vice with dispmanx enabled or disabled ? (check setup menu / Configure emulators to use dispmanx SDL)

the configuration should be set up by default, so it should already have some default configuration lines in it. Then when you first save the config from vice, it will add the rest of the config.

[petrockblog]

running it with or without dispmanx sdl enabled ? also make sure you have an updated runcommand (sudo ./retropie_packages.sh runcommand install) as there was a bug with it that was a fixed a couple of days ago in regards to setting of sdl env variables.

[petrockblog]

Ok, SNESDev is also running. This might be a cause for the problems. You can disable SNESDev with the RetroPie-Setup Script or directly from within the downloaded SNESDev-Rpi repository that you can get from https://github.com/petrockblog/SNESDev-RPi. Within the SNESDev-Rpi folder you can call sudo make uninstallservice to uninstall the SNESDev service.

[petrockblog]

you need to upgrade runcommand also – and all the other megadrive emulators. probably easiest to do a full install.

There wasn’t really a way of adding the new functionality but keeping the “individual install” option working.

[petrockblog]

which configs have you changed ?

[petrockblog]

[quote=91932]
So the GPIO expanders are reconized correctly?
[/quote]
Yes, the GPIO expanders are recognized correctly. Maybe there are other services running that make use of the I2C interface. What does service --status-all show after a boot?

Also, how many controllers are registered? You can see this with the commands ls /dev/input/.

ControlBlockService, the driver for ControlBlock, polls the GPIO expanders and maps the inputs to two virtual gamepads. This is done independently of the fact that controllers are connected or not to the CB.

[petrockblog]

not without installing a desktop first – desktop stuff have been removed from the image – unless you installed it on top of raspbian (or you have since installed a desktop environment).

you can use “cp” to copy the file to ~/RetroPie/roms or something and then copy it off via the network share.

[petrockblog]

shipping with a custom kernel will be a pain. I do not want the extra work of that personally. We need to get the fix upstream – it needs to be submitted to the kernel bugtracker (https://bugzilla.kernel.org/), and then we have a real chance of getting it backported early to the pi kernel).

Please can you suggest this to the author.

here’s a reference to the view of pi kernel maintainers:

https://github.com/raspberrypi/linux/pull/828#issuecomment-74272707

[petrockblog]

the complete file would be best – please use a 3rd party site like pastebin and share the link. thanks.

[petrockblog]

please post your retroarch.cfg somewhere for me to check. Make sure the xarcade service is disabled from the retropie setup menu too.

[petrockblog]

Did you try my other suggestion ?

[petrockblog]

you are not running the latest uae4all. No idea what image you are running, but it is older than the 2.6 I mentioned.

Without knowing how old your image is, you might do better to start with a retropie 2.6 image, or alternatively backup your configs, update retropie-setuph and do a full binary install.

[petrockblog]

we are working on it :)

[petrockblog]

you tried the option from the retropie menu as I suggested ? xarcade2jstick – The link was just for some information – try the option xarcade2jstick from the menu.

The controller is not seen as a joystick to the system. It acts like a keyboard. if the above doesn’t work you can manually configure the keys in /opt/retropie/configs/all/retroarch.cfg

[petrockblog]

could you stick to replying on a single thread please – to avoid confusing things.

First of all I assume you are running retropie 2.6 image. You should at least start with that.

some points:

You can’t launch games directly from emulationstation. It doesn’t support that. You launch the emulator and go from there. Don’t edit the emulationstation config. Don’t add any additional script.

kickstarts go to the ~/RetroPie/BIOS folder (called kick13.rom kick20.rom etc). The emulator ships with a working AROS kickstart replacement though.

to run it directly from console (if you really want to), and without using runcommand, you will need to switch the SDL driver to use dispmanx

SDL1_VIDEODRIVER=”dispmanx” ./uae4all

[petrockblog]

you just did ? :)

[petrockblog]

You would need to enable SNESDev, e.g. from within the RetroPie-Setup menu. You could have look at the sources of SNESDev to get the correct pin out: https://github.com/petrockblog/SNESDev-RPi/blob/master/src/SNESDev.c#L177.

[petrockblog]

Sorry, I did not think about this before. You need to disable the controlblockservice before this test. You can simply do this with these commands run from within the ControlBlockService folder:
sudo make uninstallservice
Does the output of sudo i2cdetect -y 1 look different then? If the GPIO expanders are recognized correctly, we will see a line
20: 20 -- -- -- -- -- -- 27

[petrockblog]

Thanks for asking! The new boards are in customs right now, I expect to get them in the next days.

[petrockblog]

the xarcade stick shows up as a keyboard doesn’t it ?

Did you read https://www.petrockblock.com/2014/06/01/xarcade2jstick/ ?

retropie has this as an option in the setup menu.

[petrockblog]

with the latest retropie this is no longer used – it boots directly into a gui.

[petrockblog]

Ok. a next step could be to check if we can manually communicate with the GPIO expander components (The two black block in the middle of the ControlBlock).

They are using a communication interface that is called I2C. What is the output of the commands

sudo i2cdetect -y 0
sudo i2cdetect -y 1

?

These commands look for any attached I2C device.

[petrockblog]

Check https://www.petrockblock.com/forums/topic/amstrad-cpc-load-games/#post-91673

Also – they are not roms ;-) (pedantic mode)

[petrockblog]

I think it’s related to just the commands to load – you need to make sure you are telling it to load from a disk.

This may help

http://www.cpctech.org.uk/docs/loadsoft.html

I have loaded data from a disk fine with it. also tapes.

[petrockblog]

http://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md

[petrockblog]

Can you post some pictures of your setup here? This usually helps quite a lot to better analyst the problem.

[petrockblog]

did you try increasing the amount of ram allocated to the gpu (by editing /boot/config.txt ?)

[petrockblog]

you can re-install the theme by running

sudo ./retropie_packages.sh esthemesimple

[petrockblog]

Ah, got your point. If you take the MAME keyboard setting for the ControlBoard, the CB will be mounted as keyboard and will not take up js0 and js1:

Gamepadtype set to arcade or snes map to game pads and take up js0/1. Gamepadtype set to MAME maps to a keyboard and does not take up js0/1.

[petrockblog]

Since we do not have an official logo yet, I would say that a generic theme would be better.

[petrockblog]

There was a little bug introduced earlier today and then fixed, so it might work if you do a fresh install again. If it still fails, please copy the install log off from ~/RetroPie-Setup/logs/ and upload it to pastebin.com or similar. thanks.

[petrockblog]

clean install on rasbian or via the last image ?

[petrockblog]

Just to let you all know that all the code is in the main retropie branch now. So if anyone does a binary install after updating the script they will get this functionality.

[petrockblog]

Yes, choose is great! If you feel that you have something ready to share, I can make sure to include it as a module in the RetroPie-Setup Script (https://github.com/retropie/RetroPie-Setup) and, thus, in the RetroPie image :-)

[Author]

Posts