Debugging out-of-tree device driver in NRF Connect

RE: Debugging out-of-tree device driver in NRF Connect

aonsquared — Mon, 31 Oct 2022 19:44:20 GMT

Hi Simon,

We've gotten it to work following your suggestions, however a new issue has popped up when we try to migrate the working application from NRF Connect SDK 2.0.2 to 2.1.0 or 2.1.1.

We've opened it in a separate ticket here: devzone.nordicsemi.com/.../dts-error-when-migrating-from-ncs-2-0-2-to-ncs-2-1-0-or-2-1-1

RE: Debugging out-of-tree device driver in NRF Connect

Simon — Wed, 26 Oct 2022 11:38:50 GMT

Try adding the sensor driver in a similar manner as explained here: RE: MCUBoot: adding custom serial flash driver as secondary partition

In the reply linked to above, the out-of-tree driver was meant to be used by MCUboot, so the reply will apply to you if you just swap out MCUboot with your application (lvgl_test).

Let me know if you have any issues with following the instructions in the link

Explanation:

The way the driver is added in the out_of_tree_driver example will only make it possible to access it directly.

However, in your case you're not accessing the functions in lpsddf.c directly, but instead you're accessing them through the API zephyr/drivers/sensor.h

For example, if you run sensor_sample_fetch(), it will trigger the function lps22df_channel_get().

In order for Zephyr to see the out of tree lps22df.c and map it to the sensor.h API, you have to use the approach I linked to at the top.

Best regards,

Simon

RE: Debugging out-of-tree device driver in NRF Connect

aonsquared — Tue, 25 Oct 2022 22:29:00 GMT

Zip file attached.

Are we missing a configuration option to enable debug and logging on the driver rather than the application?

devzone.nordicsemi.com/.../lvgl_5F00_test.zip

RE: Debugging out-of-tree device driver in NRF Connect

Simon — Tue, 25 Oct 2022 22:22:58 GMT

Could you upload your complete sample in zipped format, including the out-of-tree driver, so I can test it on my end and investigate this.

Best regards,

Simon