@nounours You'll be looking for continuity from the traces on the cart pcb. You'll also have to desolder chips or remove them from the circuit by scratching out the traces or they'll interfere. You need a clear trace or the USB stick will be hard to read.

Look at the pic of my cart. Traces go from the front of the cart to the back and to the front again. Try and find the 4 shortest traces for less interference. Thats what the multimeter will do to make your life easier. If it beeps from one end to the other then it should work.

There are solder points very near to the cart pins too. You can use those but you must use the same pins for all the carts, of course. Depending on the cart, those might be the best to use. Here is an example. 4 short traces. Then the traces are scratched out from the back out so they're cut off from the rest of the circuit for less interefence.

0_1500651011975_20160708_233847.jpg

Thank you for your reply...it helps a lot! I was thinking about manually naming the folders as well. I guess I can check and see the information that you request. Your post has been more helpful than most I have found in other forums so I appreciate it. Please excuse my "noobness" but how would I find the information that you request? Thanks...

yeah im looking forward to the n64 classic, cos that will mean new official n64 controllers, i may actually buy 2 cos those things will be worth their weight in gold mint condition in like 5-10yrs.

@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.

Mounting manually to:
"sudo mount /dev/sda1 /media/usb" (instead of usb0)
and restarting emulationstation doesn't trigger USB ROM Service as well.

Also checked other pen drive. Same issue. Checked same raspberry pi with other OS on other card (OSMC). No issue. It's strictly Retropie OS issue!

@BuZz ... Can't believe I hadn't thought of that before. SHAME on me :-(

Thanks so much for your patience, this obviously did the trick. What I did is put that command in /opt/retropie/configs/all/autostart.sh, before emulationstation is called (otherwise the games didn't show up in ES because the USB wasn't yet properly mounted). It's still unclear to me why games can be accessed via symlink in ES, but the parser cannot access them. Oh well, the workaround works, and I hope future Googlers will find it easily. Phew!

@brettsalyer it looks like you have everything running!?! Do you mind sharing with us if you found the issue? Or did just reinstalling the roms to the USB card fix the problem? Thanks

@MRZ999 yes this is how retropie still works. Unless your using a older version from around 1 year and half ago. There was a change to how retro arch saw controllers by the order they were plugged In, but was reversed shortly after.

@epd For the most part, yes. You need to add your ROMs, and set up your controllers, but other than that, should be good to go!

@DarkWolf mhhh i have not test the ps4 controller yet. With my Arcadestick and retropie i think it is approximately every 10th step. With recalbox i got the trouble more often. (that is the reason i give retropie a try again)

@ortsac thanks for your answer. I understand and will try to find a way positioning the cable differently, or just live with it :)

Regards.

gotche. sorry about that

Well after some trouble shooting the silly chinease guy who made the hub had swapped the data lines over, so the colours were not inline with the standard.

all working hunky dorey now.

@BuZz I already have my two systems set up and working after the manual copying. I'm actually out of extra Pis and USB drives at the moment. If it's broken it's not bad enough that I wasn't able to fix it so it didn't really bother me.

@WallaceTech
I think you have to find out what the UUID's are for both of your flash drives and put that information in your /etc/fstab
https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/#configure-fstab-to-automatically-mount-usb-drive

The UUID is kinda like a "finger print" or "serial number" that is unique to every drive so you won't find a duplicate. This being said, you should be able to reboot and it will remember which is which and if, by change, you take the USB drives out and don't put them back in the exact same slots as before, it will still remember who is who.

AlexMurphy is right, check out that link. It very well could be (as the link states) that your power supply isn't providing enough current. Also, if you are running a pi 3, if my memory serves me, wifi is built in. You not giving us any base information to work with makes things difficult to help.

Also, if a better power supply doesn't work, I'm guessing that it's a hardware issue, not software, in which case, this is probably the wrong place to ask.

Just gonna jump in with me too. Rebooting using ssh is no big deal but it's a minor annoyance.

@herb_fargus said in Mistake in the Retropie documentation:

I don't know how I feel about having wiki links, just the other day some stupid person spammed up one page we had to revert

Good point. Let's stick with it as it is. Thanks for your hardwork.