Posts by Da Flex

Thanks! This is classic showcase stuff, so I move the thread to that sub-forum.

Quote from Skripo

Thank you very much for your help, I will create a guide from all the help I received on this forum.

Good idea! You can upload that guide to our Wiki, or post it here, and someone else (me) can upload it.

Hedda Because you don't stop to advertise your device, I have to close this thread.

Mario77 Yes, that's right. I use a resistor with the LED, but I forgot the value. You'll find on the web, how to connect an LED to GPIO.

Mario77 No, the dtoverlay implementation only does the shutdown, no reset by long-press. I did a test to be sure.

Here is the original implementation that I used before dtoverlay. You can implement reset by long-press easily from there:

#!/usr/bin/python

# This script was authored by AndrewH7 and belongs to him.
# (www.instructables.com/member/AndrewH7)
# You have permission to modify and use this script only for your own personal usage.
# You do not have permission to redistribute this script as your own work.
# Use this script at your own risk.

import sys
sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')
import RPi.GPIO as GPIO
import os

# Replace YOUR_CHOSEN_GPIO_NUMBER_HERE with the GPIO pin number you wish to use.
# Make sure you know which rapsberry pi revision you are using first.
# The line should look something like this e.g. "gpio_number = 7".
button_gpio_number = 3
led_gpio_number = 13

# Use BCM pin numbering (i.e. the GPIO number, not pin number).
# WARNING: this will change between Pi versions.
# Check yours first and adjust accordingly.
GPIO.setmode(GPIO.BCM)

# It's very important the pin is an input to avoid short-circuits.
# The pull-up resistor means the pin is high by default.
GPIO.setup(button_gpio_number, GPIO.IN, pull_up_down = GPIO.PUD_UP)
GPIO.setup(led_gpio_number, GPIO.OUT)

# Switch LED on.
# LED will switch off automatically at shutdown by using normal GPIO state.
GPIO.output(led_gpio_number, True)

# Use falling edge detection to see if pin is pulled low to avoid repeated polling.
# Send command to system to shutdown.
try:
    GPIO.wait_for_edge(button_gpio_number, GPIO.FALLING)
    os.system("shutdown -h now")
except:
    pass

# Revert all GPIO pins to their normal states (i.e. input = safe).
GPIO.cleanup()

I agree.

Hmm, then maybe it's broken.

PS: At boot time hardware will get checked. There is a chance that Raspbian ignores a hardware defect, but LE don't. On Raspbian you should find a log, and if there is a defect, the log will name that hardware part.

Stroke_Papy Can you write some more details, please? Does LE audio work with a different firmware? I don't understand what you wrote.

The RPi firmware is written to the chip, so it stays active when you switch to another OS / microSD. config.txt / guisettings.xml are not relevant for this part.

If the firmware is the issue, you have to find a version that works with all your OS'es. Maybe switch from Retropi to Lakka, if Retropi needs incompatible firmware.

Quote from Mario77

I know it's not the point of this thread but all you can access from a windows PC is /flash directory..

Thx, this is helpful. I don't use Windows anymore, so I don't know what they support now.

If you connect the card to a PC, the "storage" folder (see instructions) will become the "STORAGE" partition.

With the infos you gave so far, I can't provide a solution. I don't know whether you copied the script folder into the storage folder, nor do I know which pins are used by your hardware. A circuit diagram and / or an example script by the manufacturer would help.

PS: If you can't access the "STORAGE" partition on PC (Windows), use the PC program PuTTY to copy from PC to RPi.

Usually people have at least analogue audio. Can you make a microSD with Raspbian and update the RPi firmware from there?

PS: Background: Maybe another RPi OS updated the firmware (you use multiple cards), and with that firmware LE can't provide audio.

Quote from Skripo

Good news, what keymap should I use?

None. All important buttons are pre-defined by CEC. If needed, you can add functions to color buttons, or change pre-defined buttons.

PS: CEC is made for your original TV remote control. Only IR codes, which are implemented by the TV, can pass-through by CEC to LE.

Skripo Yes, CEC is easy. It's activated by default on LE, and works as you said.

Quote from kolwe-x

I've already problems with this line: Copy folder "shutdown_scripts" to /storage

How can I do this?

Attach the microSD to your PC and copy that folder into the /STORAGE partition. Then do the rest of the instructions on RPi by SSH.

I don't have that case, but I think your chances are pretty good.

The volume settings are OK. Maybe you have to enable on-board audio at config.txt:

dtparam=audio=on

Don't waste your time, there is no mysterious LE switch to route your input to output. It's all about the HiFiBerry driver.

What's your HDMI setup? (which TV / monitor / AVR model, HDMI cabling RPi -> TV or RPi -> AVR -> TV)

If you can't get analogue audio, chances are your volume is set to zero (check the bottom of guisettings.xml for volume size).

UHD is higher than your TV resolution. The RPi has to down-scale UHD to 1080p, which obviously doesn't work well. Because UHD is not made for your TV, I suggest to ignore this issue.