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

    Edited once, last by DarkAllMan (March 27, 2017 at 9:01 PM).

    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

    Code
    # 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.

    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

    Edited once, last by dv505 (March 30, 2017 at 6:46 PM).

    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.

    Edited once, last by vpeter (March 30, 2017 at 7:22 PM).

    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.

    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.

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

    This is what I got

    Code
    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

    Edited once, last by vpeter (March 31, 2017 at 5:46 PM).

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

    Edited once, last by danielk (April 1, 2017 at 11:25 AM).