Retroflag Snes case

cyperghost

@hurricanefan Do you have annother Pie? It's not the layout of the GPIOs or so... So I think it's rather something with the case.

HurricaneFan

@cyperghost I have a pi 3b thats screwed into another case. I'll try to test that shortly.

Chuck_B

@jandalf81 said in Retroflag Snes case:

This way, the fan starts spinning when you set the POWER switch to ON (and doesn't stop while the Pi is powered on).

And Retropie starts only when I set the POWER SWITCH to ON. Correct?

HurricaneFan

@cyperghost So just finished testing with the same sd card and a pi 3b (not plus) and the safe shutdown and reset code works just fine. The pi 3b+ has something that doesn't like the shutdown/reset code. Super weird!!

lostless

@hurricanefan I have the retro flag case and using @cyperghost script and it’s working fine on my pi 3b+

cyperghost

@hurricanefan Please try following, the retroflag scripts enables UART for getting the power LED work
comment out or write enable_uart=0 from your ~~/boot/command.txt~~ /boot/config.txt

HurricaneFan

@cyperghost I don't have a file called command.txt in /boot

I have a file called cmdline.txt is that what you want edited?

cyperghost

@hurricanefan Sorry it's /boot/config.txt

HurricaneFan

@cyperghost changing enable_uart=1 to enable_uart=0 did the trick on my 3b+ pi. Thank you so much!

cyperghost

@hurricanefan Well committed that to my git.

retroisbest

@chuck_b said in Retroflag Snes case:

Hi guys, I hope I'm not too off-topic, but I have no idea ho ask about that.

I was wondering if the snes retroflag case switch works as a powerblock.
I mean, one of the most annoying things about the Raspberry is that everytime you plug it, it boots automatically.

With the retroglag snes case (I'm referring to the PAL version) if I plug the raspberry but the switch of the case is set to off, retropie boots anyway or it blocks the booting until I switch it on?

I have the same issue with my rpi2 and a NESPi case + as soon as I plug power into it, it turns on even if the case switch is off, if i then press it on then off it initiates the shutdown command but won't turn back on until I press the switch to on then off again.

Very odd and confusing.

Chuck_B

@retroisbest I'm not having issue cause I hadn't buy the case yet. I don't know how to help you

wurstsemmesepp

Hi,

I am encountering the same issue as @HurricaneFan with mi 3B+. I installed the safe shutdown script as described in the readme and switched to ON. As this did not work, I found this thread and tried the enable_uart=0 which did not work either. Do you guys have any more ideas?

quicksilver

@wurstsemmesepp did you try cyberghosts copy of the script found here?:

https://github.com/crcerror/retroflag-picase

wurstsemmesepp

@quicksilver yes I did, same result, does not work :(

jandalf81

@wurstsemmesepp I had the same issue, the Power switch just wouldn't work. In my case, the PCB was faulty. I contacted my vendor for a refund, so I got another case. The one I have now works without flaws. You might have the same...

cyperghost

@jandalf81 Or the Pi GPIOs itself are damaged somehow ... but the cases are mass products so it's feasible that there are some rejects.

wurstsemmesepp

Thanks for your replies. Is there an easy way to check GPIO functionality?
The safe shutdown switch seems to work however. When switching from off to on, the LED turns off when the script is not installed and turns slightly darker when the script is installed indicating that its power source changes.

cyperghost

@wurstsemmesepp Yes write a small bash script or use wiringPi and set some GPIOs to low and high. wiringPi offers a list how the state of GPIO is. For function test use a LED and connect it to GPIO and ground. It should light on or light off per current GPIO state.

Here is a small tutorial. You do't need a resistor a breadboard for this ;)

And in german
http://www.raspberrypi-tutorials.de/software/einfaches-schalten-der-gpio-ein-und-ausgaenge-am-raspberry-pi.html

and in russian
http://raspberrypi.ru/blog/328.html

wurstsemmesepp

Thanks @cyperghost I did that. The result was the following (I used a multimeter instead of an LED and had a 10 s high and afterwards low signal):

High means approx. 3.3 V
acts as intended means the voltage is at 3.3 V when it is supposed to be high and 0 when it is supposed to be low.
GPIO 14: low before running the GPIO script, acts as intended, nothing else happens.
GPIO 2: high before running the GPIO script, acts as intended, setting the signal to low reboots the PI.
GPIO 3: high before running the GPIO script, acts as intended, setting the signal to low shuts down the PI.
GPIO 4: high before running the GPIO script, acts as intended, nothing else happens.
The safe shutdown script was installed before this test.

Looks like the case-PCB is faulty, right?

edit: added additional information.