Posts by F1Fanb0y

Just ran rpiboot to compare..

theres some differences but looks like its not crashing out. does your CM3 definitley have flash memory, i think you can buy them without.

other than that i would try a different usb port or PC and see if the problem follows the slice or the PC.

Thanks everyone for continuing to support the Slice its very much appreciated.

HiassofT I've successfully booted an RPi2-9.2.6 image, its very much useable and I have been able to test video and audio content from both the local drive and a network source via the ethernet port.

in addition to the dt-blob.bin i also copied:-

config.txt

overlays\ws2812.dtbo

overlays\slice.dtbo

I also added the following to the config.txt

dtoverlay=slice

dtoverlay=ws2812

dtoverlay=mmc

not sure if any of this extra stuff has made any difference but its done me no harm at least.

ws2812 doesnt seem to be working anymore but that might be because i need to install the slice addons.

I have not tested:-

IR sensor working

Analogue Audio & Optical not working

Wifi Dongle working

Radio Remote Control working

Happy to help with any testing in the future, I'll probably keep the RPi2 image until the next update to see what happens!

Cheers

Edit: updates on testing

This is now resolved, thanks everyone for your help.

Despite using the stock config and reseating the CM the black screens continued.

There were actually 2 types of black screens:-

The first was caused by switching on the Slice and then powering up other devices and switching sources while the Slice was booting, this resulted in the TV displaying 'no signal'. This was resolved by creating an edid.dat file using tvservice -d.

The second is still unexplained but was resolved by doing a soft reset using the Libreelec menu. Most of my settings are now restored and the Slice is still working with no issues.

Cheers g7ruh i'll give that a go as well.

Thanks, Matthew

Thanks HiassofT I'm now using the stock config.txt, i'll give this a go for a couple of weeks and will report back.

Cheers

for a few weeks now i seem to be getting an occasional black screen after booting my Slice3. It started after 9.2.3 and still seems to be happening on 9.2.4.

ssh works just fine every single time, the kore remote just seems to just say 'connecting'. Once or twice its occured after booting, the kodi screen has frozen and the remote goes back to connecting.

wondering if anyone can see any clues in the debug log files:

http://ix.io/2u9x

http://ix.io/2u9y

Cheers

Hi HiassofT  bleep42

I tested those sample videos on 9.2.3 and the firmware patch allows the videos to play without issues.

Cheers

Would've thought the Slice's HDMI chip couldnt be upgraded so 4K would never be an option for the slice. If a CM4 did work and offered some feature updates I would still consider an upgrade.

Still use my slice several times each week, and i think its great - just wish it had a power switch. Thanks for looking after it LibreElec team!

Quote from CvH

hopefully final LE 9.2.1 images for slice are ready

Index of /test/slice/

would be nice if you could help testing

Thanks CvH

Tested some videos, game roms, music via HDMI - all looks good on the CM3.

Just confirming that running the above python script removes the green led only while it is set to low. When you set it to high again the green returns.

I can also confirm that by writing some extra logging into the ws2812 source code and building a slice image, that the device's 'ws2812_write' function is not called at any point and both of its internal buffers (rgba & pwm) do not show any green values, but only the pattern that was last sent (off or red).

So could some other process be directly accessing the PWM pin?

Thanks ghollingworth, have tried to get raspi-gpio to run but its coming back 'file not found', so maybe i'm missing some dependencies.

what I can use easily though is python, would this code effectively do the same?

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

import os
import RPi.GPIO as GPIO
import time

pin=43
GPIO.setmode(GPIO.BCM)

GPIO.setup(pin, GPIO.OUT)

GPIO.output(pin, GPIO.LOW)
print "GPIO pin ", pin, " low"
time.sleep(1)
GPIO.output(pin, GPIO.HIGH)
print "GPIO pin ", pin, " high"

Thanks g7ruh I haven't seen it myself for a couple of months, out of interest is your sound via the optical/analog or HDMI? do you use the wifi dongle or ethernet? Do you use the IR to control it with a remote? These are some of the things I've changed around recently.

That's awesome, thanks chewitt and ghollingworth!

I've written directly to /dev/ws2812 while its happening, using a python script based off the libreelec slice addon, and whether you clear them or change their colour the one (same) led will turn back to green in a gradual change of colour and brightness, all other leds stay at what state they were set to.

From my experience it can be weeks or months from seeing it and then it can happen every single day, its really unpredictable and so far I haven't worked out how to trigger it into happening.

If there's anything I can do to help, just let me know.

Thought I’d create a thread especially for the green LED bug, the more knowledge we can collect about it in one place the better the chance of a fix being created. The bug has been around since probably the beginning and occasionally people still ask about it.

What is it?

The LED strip will randomly light just one green LED, its always the same LED, the closest one to the power plug.

Once the bug appears the only way to clear it is to unplug the power, rebooting does not clear the bug. the green LED will stay until a reboot.

What we do know

Writing RGB values directly to the WS2812 device will only temporarily clear it before the green LED bleeds back in.

Playing LED patterns while the bug is present causes the whole LED strip to flicker as it plays.

The fact that you can stop Kodi with “systemctl stop kodi” and the bug still continues until power off tells me that the bug is low level? Possibly kernel level, and probably in the WS2812 device driver? Alternatively it could also be caused by the hardware?

The source code to the ws2812 driver is here slice-drivers/ws2812.c at master · LibreELEC/slice-drivers · GitHub

What next?

If you spot something about this bug that nobody else has mentioned or have spotted wrong information please leave a comment below, also if anyone has worked out how to make this bug repeatable please comment as it could go a long way in helping to work out what’s happening.

Hi chewitt,

Thanks for keeping the slice alive, its much appreciated!

Quote from chewitt

Instead we will roll it into our normal Pi images

If Slice users in the future load a regular Pi image would there likely be any loss of functionality of the Slice specific hardware? e.g. analog sound/SPDIF or LED patterns etc. Or could these be in an addon that would keep the functionality?

Cheers, Mattthew

I have one of those dual PS1 USB adapters connected to my Slice to use for some retro gaming.

I've got both controllers working the Kodi menu and both work perfectly on the snes9x2010 emulator. For some reason I just cant get the second controller to do anything on the genplus emulator.

I'm wondering if anyone can see anything in the log as to the reason why.

pastebin

Cheers.

Quote from CvH

(LE9 Beta 3) 8.95.003 builds (Kodi18 RC5.2) are ready for testing, could you pls test if it starts/works (we are sadly low at slice hw so we can't properly test it)

Index of /test/slice/

All working for the CM3 , cheers CvH

Quote from ewoks

Everything works fine just System ⇢ LibreELEC ⇢ Settings screen keep default light blue colour for selection and titles.

I know what you mean, all other screens (e.g. system) are your preferred colour...

But the Libreelec keeps its blue colour...

It's never really bothered me personally, but i guess it comes down to development priorities.

Quote from CvH

(LE9 Beta 1) 8.95.001 builds (Kodi18 RC3) are ready for testing, could you pls test if it starts/works (we are sadly low at slice hw so we can't properly test it)

Index of /test/slice/

just did some quick tests and its all looking good to me. thanks CvH!