Posts by vpeter

daniel, remote should been fixed in v8.0.1. It is working for me and others.

Kodi repository problem: maybe related to this?

Quote from AndrewZ

How can I check the revision? Can I see it on a running system or I need to catch it during the boot?
I have problems with pairing my BT keyboard, last time it was working on some OpenELEC version

Probably you need to open the device and see chips

But if you see this Loaded imx6q-cubox-i-som-v15.dtb from u-boot then you have revision 1.5. And it is very newer (only few months). But seems there are some bugs in u-boot identifying correct one. Can you type u-boot commands I posted above?

Quote from dv505

Here's the list of test cases on a Cubox-i4 Pro rev 1.2:

Can you stop u-boot and type this commands (one line at a time) in it's prompt and post the result? Seems strange that your box needs som-v15 dtb.

gpio input 105
gpio input 68
gpio input 40
gpio input 160
gpio input 164

This is what I got

CuBox-i U-Boot > gpio input 105
gpio: pin 105 (gpio 105) value is 0
CuBox-i U-Boot > gpio input 68
gpio: pin 68 (gpio 68) value is 1
CuBox-i U-Boot > gpio input 40
gpio: pin 40 (gpio 40) value is 1
CuBox-i U-Boot > gpio input 160
gpio: pin 160 (gpio 160) value is 0
CuBox-i U-Boot > gpio input 164
gpio: pin 164 (gpio 164) value is 0

Maybe nvme support is missing here?

Yes, only 1.2 works. And for 1.5 I'm working on it atm

Only images with kernel 3.14 has full support for som v1.5. Other kernels should work but without wifi and bt (which are not supported there).

Update: This I can fix. In next release. If anyone would like to try 4.4 or 4.8 kernel on som v1.5 let me know.

Quote from DarkAllMan

I will get back to you on this... however, my time is a little limited this week.

No problem. When you can (and want).

Sorry but if this doesn't work I'm out of ideas. I have only one touchscreen and didn't have such problems.

You can stop kodi and use evtest on ts_uinput_touch device to see what data you get. This is what kodi sees it.

systemctl stop kodi
evtest

Check if mysqld is running

systemctl status mysqld
ps -ef | grep mysqld

Can you log in with phpMyAdmin and user root and password 123?

You can also try removing whole userdata folder (you will lose everything you set up - copy first if you have something important for this addon)

systemctl stop lamp
systemctl stop mysqld
systemctl stop httpd
rm -fr /storage/.kodi/userdata/addon_data/service.web.lamp
reboot

Perfect!

Not sure if you can do what you want. But I was reading this - control USB power per-port.

Can you post whole lsusb?

Try this.

I newer wrote pointercal manually. Setting TSLIB_RES_X/Y should help even if kodi doesn't show correct resolution.

One other option is to calibrate in console with command

ts_calibrate.sh

It closes kodi and shows calibration screen from tslib library.

DarkAllMan, can you try this image? Console is already set to see more output.

LibreELEC-imx6.arm-8.0.1-sr-3.14-cubox-i-som-v15.img.gz

Update: I got confirmation that this image boots on cubox-i with som v1.5.

dv505, as I can see from next post from DarkAllMan file imx6q-cubox-i-som-v15.dtb is correctly loaded. But not sure what is wrong after that.
DarkAllMan: did you enabled serial console in uEnv.txt file? It should look as

# make boot more quiet
#console_arg=quiet morequiet
# or having quiet and serial console
#console_arg=console=ttymxc0,115200 quiet morequiet
# show messages in serial console
console_arg=console=ttymxc0,115200 no_console_suspend=1

Then you should see some boot messages from kernel.

Anyway, in mine image with 3.14 kernel there is little newer u-boot used. I will investigate this but I don't have any device with SOM v1.5 (only CuBox i4Pro).

pssturges, thanks for reporting back.

Yes, seems I was testing only with kernel 4.4 which works. But not with 3.14.

Anyway, download LibreELEC-imx6.arm-8.0.1-sr-3.14.img.gz (27-Mar-2017 15:19 142322090 bytes) file again and update with it. After that IR should work.

I think this could help.