Posts by vpeter

Quote from thefoofighter

Do you know of anyone else with a cubox-i4pro 2gb that got kernel 4.4 working?

It works for most users including me. Others has black screen (which is the main problem).

thefoofighter, I don't know which image exactly did you use but official images are using Linux kernel 4.4. But I also provide with 3.14 which works better for some users.

Quote from kosha

Looks like it's working ok with imx6-solidrun-kernel-3.14.
On the other hand CEC isn't working good with this kernel.

I think it depends on a TV in use. For most users it is working fine.

Seems kodi krypton has issues with some video files which worked in jarvis. Nothing much can be done.

Quote from WhyTea

here it is.

Thanks. I can reproduce the issue but don't know how to solve it (seems kodi issue and not only libreelec is affected).

WhyTea, upload a sample somewhere.

AndrewZ, let me check BT with a speaker I requested back from a friend. BT keyboard I don't have.

Index of /

In Windows I think 7-zip can open .img.gz file and show the files.

Quote from tunf

Just to inform, updated to 8.0.1, no cec connection, ...

I blame your TV.

In ssh console try to stop kodi and then check what cec-client do:

systemctl stop kodi
cec-client

imx6q-cubox-i.dtb: means old revision of cubox-i. BT should work fine with it. What exactly is the problem?

You could also use kodi's build-in touchscreen calibration functionality if you had so much problems with mine addon. And yes, now that there is available I don't build it anymore.

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).