Issues compiling custom I2C driver

RE: Issues compiling custom I2C driver

napei_ — Wed, 16 Nov 2022 23:21:23 GMT

A solution that doesn't require every one of my team to custom-patch zephyr for every out-of-tree sensor would be nice if possible. Understandable if nrf SDK isn't set up for this at the moment, however could this raised internally as a feature request?

RE: Issues compiling custom I2C driver

Kenneth — Mon, 14 Nov 2022 14:48:25 GMT

Hi,

I tried this, and seems to work.

First I download https://patch-diff.githubusercontent.com/raw/zephyrproject-rtos/zephyr/pull/48389.diff and placed it in \v2.1.2\zephyr

Then I apply the commit:

Then for instance opened the lis2dh example project and added the following to the overlay file:

&i2c0 {
    mcp9600: mcp9600@67 {
        compatible = "microchip,mcp9600";
        label = "MCP9600_I2C";
        reg = <0x67>;
        status = "okay";
      };
};

And in main.c I added microchip_mcp9600 similar to st_lis2dh:

void main(void)
{
	const struct device *sensor = DEVICE_DT_GET_ANY(st_lis2dh);

	if (sensor == NULL) {
		printf("sensor No device found\n");
		//return; // commented out to ensure the core run further.
	}
	if (!device_is_ready(sensor)) {
		printf("sensorDevice %s is not ready\n", sensor->name);
		//return; // commented out to ensure the core run further.
	}

	const struct device *sensor2 = DEVICE_DT_GET_ANY(microchip_mcp9600);

	if (sensor2 == NULL) {
		printf("sensor2 No device found\n");
		return;
	}
	if (!device_is_ready(sensor2)) {
		printf("sensor2 Device %s is not ready\n", sensor2->name);
		return;
	}

Build and flash.

I don't have any sensor connected, so I get the standard reply "is not ready".

Best regards,
Kenneth

RE: Issues compiling custom I2C driver

napei_ — Sat, 12 Nov 2022 01:44:45 GMT

I'm still stuck on this, wondering if there's any internal samples that implement drivers like this?

RE: Issues compiling custom I2C driver

napei_ — Wed, 02 Nov 2022 12:20:20 GMT

I've previously looked through these. I also followed along with a nordic person's presentation on drivers in Zephyr as well (outside nrf SDK) https://www.youtube.com/watch?v=o-f2qCd2AXo

Only other thing that I can see is some Zephyr-only guides place the board definition and the driver implementations outside the app/ folder where the nrf SDK code would usually be. I'm at a loss at the moment because it should "just work".

I can't find (unless I'm just missing it) any samples in either nrf or zephyr that do per-application drivers like this.

RE: Issues compiling custom I2C driver

Kenneth — Wed, 02 Nov 2022 12:07:16 GMT

Hello,

Not entirely sure what you have forgotten here, but I suggest to take a look at these threads on some suggested links that you can look at for comparison:

https://devzone.nordicsemi.com/f/nordic-q-a/89759/making-a-device-driver-for-nrf52833-using-device-tree-for-spi-supported-device-that-is-not-available-in-zephyr-drivers-sensors

https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/peripherals/posts/writing-device-drivers-for-uart-peripherals

Kenneth