Check the dmesg log and see what input/USB devices are being detected by the kernel. RetroPie is simply a collection of scripts running on Raspbian, so if it works in the plain distribution, it should work here too.
Sorry for the delay, i don't have time to respond and try Amiga before :(
@HoraceAndSpider did answer your question in a very detailed manner! In short a HDF image is a WHDLoad package that has been converted into an image. Therefore no package available means no HDF (please keep me honest anyone). An awesome guy called @ransom1122 made many conversions (and many other cool stuff). At the very end there's no real advantage of using one over the other as it's ultimately the same thing. Feel free to use the setup you're most comfortable with. Just that WHDLoad packages tend to be updated quite regulary as you've mentioned earlier (check the Latest News section there).
With respect to Heimdall2 AGA package, it is working fine here. You may have issue either with the package version or with some uae parameters. FYI I'm using latest version version 1.6 (16.03.05) as of writing. An uae for that game could be found there.
I have the last version too.
And the game is a working fine on my friend PI with the Ultimate Amiga Pack from @ransom1122 . And on my PI with same settings, it don't. It's why it is very strange for me ? Same Game same UAE file same WHDload.
To debug check within your package folder. There has to be a file named whdscript_debug. You must have launched the game at least once for this file to be created. If you open it with a text editor you should see few lines telling you what went wrong during last launch.
Ok thanks i will read it.
Now it's my friend @waal that working on Amiga for me. He know better Amiga than me.
He read some where it can come because my games are on an USB drive !
And my WHDLoad too, have you make some test on USB Hard Drive too ?
Maybe it can be a good idea to copy only the WHDLoad to the SD Card ? ...
I am using the stock 5V charger that came with the Pi
Charger? or Power Supply? What is the current rating? You need 2.5A. Take a look at this. with regard to your blinking green LED as it indicates a corrupt card or an incorrectly written image. One final thing worth a try is that you edit your /boot/config.txtand add or uncomment ( remove the # before ) hdmi_force_hotplug=1. You said that the screen is connected at the GPIO but is it powered externally or by the GPIO or by the USB? - this is why your use of a correct supply is essential. If you are not using an external supply for the screen, you will need to force the hdmi to get the screen to work - I had this issue with a screen that was powered by the usb ports on the Pi.
This is cheating a little, as your ROMs should obviously align with MAME set required, but many classics don't change from set to set.
I wouldn't call it cheating at all! ;) I have 250+ games in mame4all and mame2003 folders. If I compare them as binary they are almost 100% identical directories. On top of that if you TorrentZip your sets they'll have the exact same hash and are 100% identical except for the half dozen or so not supported in mame4all.
So I edited es_settings.cfg to my liking (kiosk UI, snes-mini theme, ect...) then I used "chattr" to lock it ALL down. I can switch to full UI and do whatever I need to do, but after a restart it reverts back to kiosk.
sudo chattr +i es_settings.cfg
to unlock it:
sudo chattr -i es_settings.cfg
that did the trick. I'll leave that way until next update.
Thank you! It's almost perfect. It's good for me. But the IDs of the axes (-0, +0; -1, +1) are used from /opt/retropie/configs/all/retroarch-joypads/ . They can be different in different controllers. For example, I have 2 gamepads. And they have different IDs of the axes of the right stick. Probably, it can be with the left stick. So, it's not really a universal solution.