Posts by dv505

Quote from vpeter

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

The output for "gpio input 160" is different: gpio: pin 160 (gpio 160) value is 1

The Cubox-i that I have is from (probably) the first batch. I pre-ordered it (September 2013), and it was delivered in January 2014.

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.

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

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.