Hello, I was looking into the firmware flashing options too for my Controlblock. Have anyone tried to flash with Arduino Uno as ISP or with the Arduino Nano Every?
As I have both it would be the fastest but I would love some help to do it right...

Thanks

Hello, we recently identified a bug in the ControlBlock driver. I am very sorry for that!
Your observations see to match the symptoms caused by that. We released an update yesterday and that should also fix your problems.

Thanks for getting back to me, and thanks for making fantastic little bits of hardware, I hope it works out with the 3A+

I ordered the B model in the end, I figured that I might regret not having those extra USB ports down the line, and the larger footprint means I'll be forced into making a tidier build :)

Hi, did you get my email reply?

@loonyboi Thanks! I wasn't sure if you meant to mirror the controls by ES' UI or at file system level by copying their config files. So if I understand you correctly, setting them up identically in ES does suffice.

@m2306 I also need a few weeks to finish my stuff and get back to the Topic. I will keep you up to date as well!

Sorry for the delay on my side.

I like our solutions!

Also, a tool like jslisten also came into my mind for your second question.

Finally - very glad to hear that!

Doh, OK, re-running the script after rebooting fixed it. I must not have rebooted since updating the kernel version. Now I can run jstest /dev/input/js0and see the buttons work as well as shutdown view soft power switch and see LED indicate status.

I'm not sure if this post will be useful to others, but one never knows. In any case, the process of writing it out probably helped me figure out what went wrong.

Also, the config file is located in the folder supplementary within the driver folder ControlBlockService2.

I would be more likely to learn direct gpio wiring than buy another piece of hardware if I really wanted to get my pitendo running recalbox. I was only a little curious about recalbox. Overall I have become dissatisfied with emulation on the pi in general guess my expectations were set incorrectly. Oh well it was a fun project and I learned a lot. Eh at this point I just might pony up the dough for an Analogue Super NT and be done with it. /end rant Anyway might as well lock/delete the thread not much for anyone else to learn or discuss here and my question was answered several posts ago.

but including retro pie I think you might just make with exactly 16 GB

Hi @shukuyen ,

Sorry, I didn't make a tutorial but it was all pretty straightforward in the end.
I gutted an old Nes and dumped everything in :)

Parts used:

Rpi3 + microsd Raphnet dual nes to usb Petrockblock's controlblock and nylon posts Wiring

The hardware part was the easiest part tbh.
If you get it all wiredup i can make an image of my sd. That way you shouldnt have to configure anything :)

Thanks @petrockblog!
I just tried it out using some stipped wire.
Connecting Plyr 1 GND or Plyr 2 GND with Player 1 B for a short moment will indeed "reset" out of the current running game!

Thanks for that elaborate answer. I need to step through this now.

@attorneyinsc To what is rhe ControlBlock wired to? "arcade", "mame", "snes", etc? What controller do you use? Post your controlblockservice.cfg file.

Maybe it is also an issue with the power supply: If you are using additional USB devices your power supply or micro USB cable might be components to exchange. We had this often with other installations in the past.

@petrockblog said in Ok, got my ControlBlock.....some questions?:

Would this be the correct procedure to get the PI & ControlBlock setup?

Flash RetroPie to Micro SD Card. Boot up RetroPie & update via retropie-setup.sh (in RetroPie menu). Reboot Pi. Run ControlBlock Quick Installation Script. Shutdown Pi and disconnect power. Connect ControlBlock to GPIO Pins on Pi. Connect Micro USB to ControlBlock and Power on.

If you are using a power switch make sure to connect it to the ControlBlock.

If you are not using a power switch make sure to connect it to the Raspberry Pi. Otherwise you cannot switch on the Raspberry.

In any case you can attach the ControlBlock to the RPi before installing the ControlBlock driver.

Ok, that makes sense now.

If I've got a controlblock, and no power switch, I should disable power switch functionality and power via the pi.

If I do have a power switch, I should connect it and power via the controlblock.

@petrockblog Thanks for the confirmation.

By the way, I received the ControBlock that you gifted me with. I truly appreciate the gesture. Thank you so much!!! I will definitely put it to good use.

I never got any response from @petrockblog on this....so I'm asking again, are there diagrams that we can look at? Also, how about a Parts List? Some of us are having deficient power when the ControlBlock is used. I know that a transistor (Q1) switch supplies power to the PI using the GPIO pins. The question is, what is the max current that Q1 supplies the RPi with? Is it 2.5A or much less? Is this a constant current or fluctuating current? Without a diagram and parts list we are constantly guessing where our issues come from.