I think LibreELEC uses a different kernel (compared to Raspbian), which makes UART trouble. UART0 (ttyAMA0) with the LibreELEC kernel is now used by Bluetooth, as you already found out.
There is "full UART" and "mini UART". You want to use "full UART". This should switch Bluetooth to "mini UART":
dtoverlay=pi3-miniuart-btYou could do I2C over serial port, if RX/TX is not available. To do so, the I2C option at config.txt should be on.
Maybe your DAC shield already uses RX/TX, and does not allow pass-throug at those pins. Try it without the DAC shield.
Did you have enabled i2c at the config.txt?
dtparam=i2c1=onIt's a good one. Ca. 40 MB/s is the maximum reading speed inside of a RPi3, so the card is fast enough. Error correction is usually done by the file system, and maybe reduce the storage capacity over the years. Some cards have an additional internal error correction system.
Extreme heat is the enemy of any card. With a good cooling strategy you can increase the card's lifetime. Kingston has some military grade cards, made for extreme temperature.
Another hint: I have been added this lines before the "try" statement in the off-button.py:
led_gpio_number = 13
GPIO.setup(led_gpio_number, GPIO.OUT)
GPIO.output(led_gpio_number, True)This will turn my status LED on when LibreELEC starts. The status LED will turn off automatically at shutdown, because the shutdown will set all GPIO levels back to default state.
You can use the same code, too: If you connect GPIO 13 (and maybe it's opposite ground pin) with your circuit, it will have the same effect like connecting and listening to an USB port (whether it has the default 5V or not).
The only difference is that you have to handle 3.3V of the GPIO instead of the 5V of USB.
The shutdown command will not turn off 5V completely - it goes to standby. In standby it will listen to GPIO, and can be switched on with a GPIO button.
I have been installed a power on/off button at my RPi3B+, which works perfectly with LibreELEC. Read this thread for instructions. If I understand you right, your timer will do a complete 5V power off after the shutdown.
PS: With the off-button.py script (see linked thread) you can trigger a GPIO signal right before shutdown. If you listen to that GPIO "off" signal with your timer, it should work.
However, although I can set the resolution to 576 or 1080 lines, set the Vertical sync to 50Hz but I cannot set the Horizontal Sync frequency from 31KHz to 15.6KHz in the LibreElec menu. There is no option. How can I find out if my card supports this option and how can I set it?
Yes, there is no option for horizontal frequencies.
You will find this XML tag in your guisettings.xml:
<setting id="videoscreen.whitelist">It contains all possible resolutions / vertical frequencies for the output device.
If whitelist changes from time to time with the same output device, it indicates a connection problem.
Did you try it? Not sure about your Foxconn NT3700 but modern videocards can output audio over DVI as long as you use DVI to HDMI cable.
I agree. DVI audio is not part of the official DVI standard, but supported by some video cards.
My logs:
The I2S line looks good.
This lines of your log are a potential problem:
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] main.c: Running in system mode, but --disallow-module-loading not set.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] main.c: Home directory of user 'root' is not '/var/run/pulse', ignoring.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] caps.c: Normally all extra capabilities would be dropped now, but that's impossible because PulseAudio was built without capabilities support.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] main.c: OK, so you are running PA in system mode. Please make sure that you actually do want to do that.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] main.c: Please read http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/WhatIsWrongWithSystemWide/ for an explanation why system mode is usually a bad idea.
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/run/pulse/.config/pulse/cookie': No such file or directory
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/run/pulse/.config/pulse/cookie': No such file or directory
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] authkey.c: Failed to open cookie file '/var/run/pulse/.pulse-cookie': No such file or directory
Jun 22 13:11:51 KODI-Nappali pulseaudio[265]: W: [pulseaudio] authkey.c: Failed to load authentication key '/var/run/pulse/.pulse-cookie': No such file or directoryI don't have those pulseaudio warnings in my kodi.log, but I don't have a Hifiberry shield.
Maybe user HiassofT can have a look at his log to verify whether the warnings are critical or not.
I think that's bad HDMI programming inside Kodi. The wake-up call to the AVR should get some kind of a feedback. I'm not into HDMI code, so I'm not sure whether it's doable.
You mean, I should try out something like this?
No, I mean an adapter, which has one HDMI input, and two HDMI outputs. But your adapter could be right, if you don't have a receiver with HDMI.
That Hifiberry shield is special RPi hardware. That's why I expect a driver problem. So, giving a kernel log may help to see, whether the driver has been loaded.
It uses the I2S sound port that connects directly to the CPU without the need for an additional USB conversion.
The I2S is the the keyword to search for in the kodi log. That means, there is no special Hifiberry driver.
Can you check your config.txt please? Those lines should be in it:
dtoverlay=hifiberry-digi
dtdebug=1I don't know, if the Hifiberry driver is broken or not. Maybe using an HDMI splitter instead of Hifiberry could be a solution (if you can connect it with your Samsung receiver).
Deactivating the CEC add-on is maybe worth a try.
One way of manually expanding the current system partition is to use a tool called Gparted. You can create a Linux bootable USB stick and adjust your disk partitions with it.
I agree. If you can boot from an external device, Gparted is the right way to expand the partition.
Can you boot from an external device?
Or does the LibreELEC installer start, but shows an error when trying to install?
If the installer starts, what's the error message?
Thanks for the tip! Im looking through the options and don't see this function. I even put the skin back to stock to just in case there was a hidden menu I wasnt seeing. Is this an advanced feature?
Some PC's have two menus: One for general settings, and one for boot order. For my notebook, I have to hold F12 right after power-on. Your manual may give an advice, how to access the menu for boot order. It could be a different key for your HTPC.
Both times it wrote to the USB disk, and when i boot up the HTPC it just loads as normal, no clean install.
1. Stay calm.
2. Check the boot options of your HTPC. Maybe the boot order has to be changed. It should search for a bootable USB device at first place.
It seems much more sensitive than the Wi-Fi built in RPi3B+ as it finds many more local Wi-Fi routers. However when it switches to 5GHz the signal strength drops dramatically and the connection drops out after a few minutes. Although its better than the 5GHZ Wi-Fi in the RPi3 the 5GHZ signal strength in that particular location is just too low so will find another solution to get more speed at that location.
Interesting. So, receiving signals works fine, but sending signals fails. Because sending signals needs more wattage, it might be a PSU issue.
Copy and paste to Pastebin. Then post the generated link.
