We work with a Demo Image and added our own layers.
In the layer “meta-cobra-apalis-imx6” there is the recipe “linux-toradex” where we have the file “imx6q-apalis-cobra.dts”.
Appended you find from bitbake the “console-latest.log”.
Then we can install with “Toradex Easy Installer”.
When booting the installed image we see that the DeviceTree could not be correct loaded. The whole booting output is attached.
I noticed a conflict in assigning the pins to the corresponding functions.
[ 5.829428] imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_NANDF_D4 already requested by 20e0000.iomuxc; cannot claim for spi0.0
[ 5.840838] imx6q-pinctrl 20e0000.iomuxc: pin-195 (spi0.0) status -22
[ 5.847385] imx6q-pinctrl 20e0000.iomuxc: could not request pin 195 (MX6Q_PAD_NANDF_D4) from group gpio2io04grp on device 20e0000.iomuxc
[ 5.859811] mcp251x spi0.0: Error applying setting, reverse things back
[ 5.866597] mcp251x: probe of spi0.0 failed with error -22
Are you planning to use the SPI interface in your application? If not, then you might consider disabling the Interface to prevent the conflict.
Yes that is true with this conflict, but that is not really the problem. It is as above mentioned the “/pwmleds/pwm1: arguments longer than property”.
Is it possible, that the used linux-kernel is not compatible with this configuration in the DeviceTree?