Hi. Thanks for advice. I ended up downloading mame32 and launching from laptop connected to the tankstick. It is working! The only issue is there is echo from the commentators. From what I understand I need a more powerful (3.5 ghz or more computer).
Thanks for the interessting link.
Yesterday I tried the original RPI power supply, but same as before. After about 30-60 mins everything starts to flicker. I don't get any errors and if I reboot the system everything works fine for the next 30-60 mins.
@kiesowingme4 not sure about ethernet, i'm guessing if it connects and it has an ip address I don't see any reason why you can't connect to it in the same way. I just find it easier over wifi (I have the rpi 3, but you can connect with a dongle). I have my collection of roms stored on my onedrive and I sometimes use my phone to do the transferring of roms through es file explorer.
@kdragon_2 RetroPie is just Raspbian Linux underneath, so as long as your setup works with Raspbian and the OS detects your setup as a controller, RetroPie should recognise it and use it. As for the how to communicate with it, that's up to you - Linux/RetroPie already includes a few drivers that interpret GPIO inputs as a controller - look in the Docs.
I was interested on Milhouse build because it's best way to play 10-bit x265 videos on raspberry pi 3.
I installed it on a new sd card but they don't smooth enough, so i think I'll give up on trying playing 10-bit x265 videos
The screen I used is a 128*128 screen so yours may be different. There is also the guide in my signature for ili9341 screens, you will see the similarities between the instructions, and get some idea of the wiring
well I had my head wrapped around several problems with Reicast and controllers for the past few days. I had configured the controllers many, many times with joyconfig, editing emu.cfg, controller files for DC, etc, and I finally found the source of my problems.
The so called 'automatic configuration' is broken. No matter what you put into the config files, it gets overwritten when you run Reicast. The script tries to identify the devices configured in the OS and assign them automatically. In my case, always assigning them wrong, so anything seemed to work (keyboard or gamepad).
The only thing that worked was to comment out the line in the script (.sh) where it gets the result of the "automatic" detection and put it into the command line for Reicast call. I dont have my PI here to see exactly the script name and exact line, will try to update this post later with more details. But you get my point.
Just commenting this single line and voila, my pad started to work and I was able to get past the date/time screen, and play a game.