Regarding spi and i2c device detection on colibri-imx6 custom carrier board

[Devireddy]

I have spi and i2c devices connected ,i configured for spi in imx6qdl-colibri.dtsi as below
&ecspi3 {
cs-gpios = <&gpio4 24 GPIO_ACTIVE_LOW>;
pinctrl-names = “default”;
pinctrl-0 = <&pinctrl_ecspi3>;
status = “disabled”;
};
pinctrl_ecspi3: ecspi3grp {
fsl,pins = <
/* SPI CS */
MX6QDL_PAD_DISP0_DAT3__ECSPI3_SS0 0x000b1
MX6QDL_PAD_DISP0_DAT4__ECSPI3_SS1 0x000b1
MX6QDL_PAD_DISP0_DAT2__ECSPI3_MISO 0x100b1
MX6QDL_PAD_DISP0_DAT1__ECSPI3_MOSI 0x100b1
MX6QDL_PAD_DISP0_DAT0__ECSPI3_SCLK 0x100b1
>;
};
and in another file imx6dl-colibri-harmony.dts as below
&ecspi3 {
status = “okay”;

fsl,spi-num-chipselects = <4>;
//pinctrl-names = "default";
spidev1: spidev@2 {
	compatible = "spidev";
	reg = <2>;
	spi-max-frequency = <23000000>;
	status = "okay";
};

after these modifications also i am unable find spi devices
when i enter the command
$ ls /dev/spi*
output:no such file/directory exist

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello,

It looks like you’re having trouble detecting SPI devices on your Colibri iMX6 custom carrier board. Let’s go through some steps to help resolve this issue:

1. Device Tree Configuration: You’ve made changes to the device tree files, which is a good start. Ensure that the ecspi3 node is correctly set to “okay” and that the spidev node is properly configured. Double-check that the pin configurations match your hardware setup.

2. Check for Conflicts: If your board setup includes an MCP2515 SPI CAN controller, it might be enabled by default, which can interfere with SPI device detection. Make sure to disable the MCP2515 node in the device tree by setting its status to “disabled”.

3. Verify Device Nodes: After booting, check the /dev directory for spidev nodes. If they are missing, it suggests the SPI interface isn’t initialized correctly.

4. Examine Boot Logs: Use the dmesg command to review the boot logs for any errors related to SPI initialization. Look for messages that might indicate issues with your device tree configuration or driver loading.

5. TorizonCore Overlays: If you’re using TorizonCore, ensure the correct device tree overlay is applied. You may need to adjust the overlays.txt file in the /boot directory to include the appropriate SPI overlay.

By following these steps, you should be able to identify and resolve the issue with SPI device detection. If the problem persists, carefully review your device tree modifications for any potential conflicts.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Using a 2nd I2C bus on iMX6 with Iris carrier

Our system uses an iMX6 Solo on an Iris carrier board, and we have been using the existing I2C bus off of Iris connector X16 (pins 5 & 6) successfully. Circumstances require the use of a 2nd I2C bus, which is available on connector X16 (pins 8 & 11) with some re-configuration. The problem is that I cannot get this to work and I’m at my wits end. We are experimenting with the GPIO tool, and it seems pretty clear what I should do, however I must be missing something fundamental. The GPIO tool sh…

Add an SPI device to colibri imx6

We have 2 SPI slave devices connected to the same colibri standard SPI bus with different chip_selects on our custom carrier board. We are able to communicate with the 1st SPI device using the default SPI driver from the kernel. But what do we do to make the driver work for 2nd one? By reading posts on the forum, my understanding is to add the 2nd device to board device tree file (imx6dl_colibri_eval_v3.dts). So the SPI session of the file looks like this: /* Colibri SPI */ &ecspi4 { status…

imx6ULL custom device tree.

[Devireddy]

I tried all the above mentioned things ,still the issue is there

[sahil.tx]

Hi @Devireddy ,
Is the issue only observed on custom carrier board or any other Toradex carrier board.