Cubox-i4 Pro

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.

It appears there is some bug in the device detection of (at least) the Cubox-i4 Pro. When starting 8.0.1 (with 4.4 and sr-3.14) I get the same error message as DarkAllMan in thread-5449-post-41463.html#pid41463
U-Boot detects the device as a CuBox-i MicroSOM and tries to load that device tree. However, the file imx6q-cubox-i-som-v15.dtb does not exist. Simply renaming imx6q-cubox-i-som-v15.dtb to imx6q-cubox-i.dtb solves the issue.

Serial Output of: LibreELEC-imx6.arm-8.0.1-sr-3.14.img.gz 27-Mar-2017 15:19
It never boots.... keeps black....

U-Boot SPL 2013.10-rc4 (Mar 27 2017 - 09:37:58)
Boot Device: SD1




U-Boot 2013.10-rc4 (Mar 27 2017 - 09:37:58)


CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: MX6-CuBox-i
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment


In:    serial
Out:   serial
Err:   serial
Net:   FEC [PRIME]
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found
Hit any key to stop autoboot:  0
## Executing script at 17f00000
Wrong image format for "source" command
mmc0 is current device
** Unable to read file /boot.scr **
531 bytes read in 10 ms (51.8 KiB/s)
Importing environment from mmc0 ...
6562784 bytes read in 341 ms (18.4 MiB/s)
Booting from mmc ...
35464 bytes read in 23 ms (1.5 MiB/s)
Loaded imx6q-cubox-i-som-v15.dtb
Booting /KERNEL
Kernel image @ 0x10800000 [ 0x000000 - 0x6423e0 ]
## Flattened Device Tree blob at 18000000
   Booting using the fdt blob at 0x18000000
   Using Device Tree in place at 18000000, end 1800ba87


Starting kernel ...

Quote from vpeter

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.

Perfect. My remote is now working. Everything else seems to be working well as far as i can tell so far.

Thanks!

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.

Quote from vpeter

DarkAllMan: did you enabled serial console in uEnv.txt file? It should look as......

Yes.....

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.

Quote from vpeter

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.

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

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

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

• LibreELEC-imx6.arm-8.0.1 —> Not working, unless renaming imx6q-cubox-i.dtb to imx6q-cubox-i-som-v15.dtb

• LibreELEC-imx6.arm-8.0.1-sr-3.14 —> Working

• LibreELEC-imx6.arm-8.0.1-sr-3.14-cubox-i-som-v15 —> Working

• LibreELEC-imx6.arm-8.0.1-xbian-4.8 —> Not working, unless renaming imx6q-cubox-i.dtb to imx6q-cubox-i-som-v15.dtb

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 vpeter

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.

That's strange, because I am now running 8.0.1 (official; 4.4.19 kernel), and BT and wifi are working without a problem. But maybe that's because I have a rev1.2, not a 1.5.

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

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

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

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?

hi vpeter, tried the 3.14 version, but i had the old problem as i described here
thread-4813.html.
no problem with 4.8.
(cubox-pro).

is the main kodi repository down? i get always the "cant connect to repository..."

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

Kodi repository problem: maybe related to this?