out-of-tree driver

[Gabriele]

Hi,
This time I'm on NCS 1.3.0.
Board definition is derived from nrf5340pdk_nrf5340, with some minor variations, and it is out-of-tree. I think it is OK.
Since I moved also my DAC driver out-of-tree I'm having problems with cmake build.
This is all they provide on this topic, nothing! (docs.zephyrproject.org/.../README.html)
I'm sharing the files holding out hope that someone could kindly try it out.
Just run the build.sh script to get the work done.

Thank you

[Hakon]

Hello,

 

I'm sharing the files holding out hope that someone could kindly try it out.

 Where are you sharing the files? I can't find anything in attachments.

[Gabriele]

Sorry Hakon, here you are6102.files.zip

[Hakon]

When I run the build script it tries to build for the nrf9160_pca10090 board, which is deprecated. Shouldn't it build for the custom board you mentioned?

[Gabriele]

Dear Hakon,
it might be our NCS installations differ in some environment variable.
I guess this is beacuse I plumped for working with git submodules instead of letting west to manage multiple repositories in the standard way.
Anyway, I've solved the problem by myself.
I realized that, to get the driver compiled, cmake needed to know were to find the binding file (dts/bindings/dac/ti,dacx0501.yaml).
Placing hereunder statement in the app's CMakeList.txt proved to be the right thing.

list(APPEND DTS_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/../board-definition)

This solves the problem.
Thank you for your willing to help

[[email protected]]

Hi Gabriele，

When i think about hwo to organization my own driver for a long time ,I have notice your ticket.I look your code. FIRST OF ALL,I will thank you.

Besides, I have a question about that why there is two <dac_dacx0501.c>file.And The zephyr sample code also contain zephyr subdirectory in the out of module,But I do not know why we must to creat zephyr subdirectory when we creat the module we needed.