Creation of custom driver for an i2c device

RE: Creation of custom driver for an i2c device

helsing — Fri, 03 May 2024 12:29:20 GMT

[quote user="V.Lorz"]Could you, please, point me to documentation describing the structure which is required for the tools to recognize and link both, the application and the drivers? Is it mandatory to implement a structure like that of [ncs-example-application]?[/quote]

The top level CMakeLists.txt adds the drivers folder which loads drivers based on Kconfig options.

The drivers themselves can be in any folder as it is defined in CMakeLists.txt. The bindings, however, need to be in the folder as given in the example. Please see the documentation:

RE: Creation of custom driver for an i2c device

V.Lorz — Tue, 30 Apr 2024 19:22:17 GMT

Hi Håkon,

Thanks for noting I misspelled Monolithic and for your time and recommendations. I'll follow the course.

I've previously created a structure similar to that described at [DTS_ROOT], but neither vendor-prefixes.txt nor the driver's yaml seem to be recognized by west (currently using VS Code with nRF Connect plugins).

Could you, please, point me to documentation describing the structure which is required for the tools to recognize and link both, the application and the drivers? Is it mandatory to implement a structure like that of [ncs-example-application]?

RE: Creation of custom driver for an i2c device

helsing — Mon, 29 Apr 2024 20:42:41 GMT

Hi V.Lorz,

From https://docs.zephyrproject.org/latest/build/dts/bindings-upstream.html#rules-for-vendor-prefixes :

"For custom bindings, you can add a custom dts/bindings/vendor-prefixes.txt file to any directory in your DTS_ROOT. The devicetree tooling will respect these prefixes, and will not generate warnings or errors if you use them in your own bindings or devicetrees."

In another ticket regarding "unknown vendor prefix" a couple of links were posted:

[quote userid="106736" url="~/f/nordic-q-a/110209/node-soc-uart-40028000-fpreader-ffffffff-compatible-zeantec-jm101-has-unknown-vendor-prefix-zeantec/478712"]

We recently releaces a device driver tutorial over at https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/. Maybe that can be useful for you?

Also, we got this sample app which shows you how to make your own driver: https://github.com/nrfconnect/ncs-example-application

[/quote]

(By the way, I noticed "monolithic" is spelled without an 'h'. If you do so consistantly throughout your files, then this should be OK.)

Best regards,

Håkon