We are using Colibri iMX6 DualLite 512MB V1.1A in Colibri Evaluation Board V3.2B with Custom Linux Image developed using OE/YOCTO from Linux Image V2.8.
We need to interface some sensors with SPI communication. For that I referred this link. It says,
By default our BSP uses the MCP2515 SPI CAN controller as available on our Colibri Evaluation board V3.x. In order to use spidev instead one needs to disable (e.g. status = “disabled”) the mcp2515 device tree node and enable (e.g. status = “okay”) the spidev one and re-generate and deploy the device tree to the target.
Is Device Tree configuration is the only way to enable SPI module? Isn’t there any single SPI module which are available by default so that we can directly use?
For doing device tree customization, I referred this link. Since we are using a Custom made OS using YOCTO/OE, should we need to do any changes in this method.
And in the Guest webinar:Demystifying Device Tree for NXP® i.MX Processors, they use tftp boot, to upload the newly generated .dtb file. I haven’t used tftp boot yet. Is there any alternative for that?
Thank you for your time.