You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for sharing this driver and sorry for abusing the issue system for a question .
Could you describe what one needs to do to add this driver to a custom application? What i did is the following:
copy the following directories to my workspace (the folder above my application folder): drivers, nrf_servo, include
add the boards folder to my own application folder (next to my src)
add CONFIG_NRF_SERVO=y to my proj.conf
add #include "drivers/nrf_servo.h>" to mu main.c
However, when i build my project i get:
workspace/blinky_3/prj.conf:2: warning: attempt to assign the value 'y' to the undefined symbol NRF_SERVO
I assume that the driver (added to my workspace) is not seen by cmake? However, i cannot see how that is configured from your example project. Could you elaborate how you got the custom driver to be recognized?
I should say that i am new to zephyr and nRF Connect so i might be missing something obvious.
Thanks!
The text was updated successfully, but these errors were encountered:
Thank you for sharing this driver and sorry for abusing the issue system for a question .
Could you describe what one needs to do to add this driver to a custom application? What i did is the following:
drivers
,nrf_servo
,include
boards
folder to my own application folder (next to mysrc
)CONFIG_NRF_SERVO=y
to myproj.conf
#include "drivers/nrf_servo.h>"
to mumain.c
However, when i build my project i get:
workspace/blinky_3/prj.conf:2: warning: attempt to assign the value 'y' to the undefined symbol NRF_SERVO
I assume that the driver (added to my workspace) is not seen by cmake? However, i cannot see how that is configured from your example project. Could you elaborate how you got the custom driver to be recognized?
I should say that i am new to zephyr and nRF Connect so i might be missing something obvious.
Thanks!
The text was updated successfully, but these errors were encountered: