nrfConnect Zephyr freestanding application with custom driver vs west workspace

Hello,

I successfully went through the tutorials in 

https://github.com/nrfconnect/ncs-example-application/tree/main and created a "west workspace" as per the instructions in README.md From there I was able to make the sample driver work and use west to build and flash with my custom overlay file, and even get it to work within VSCode.
west build -b nrf52dk_nrf52832 app -- -DDTC_OVERLAY_FILE=$(PWD)/boards/nrf52dk_nrf52832.overlay
My question is, how do I do the same with a standalone app (https://nrfconnect.github.io/vscode-nrf-connect/guides/applications.html) using VSCode + nRF SDK in a VSCode workspace?
My app/main.c wants to talk to a custom driver/sensor which in the west workspace is located in ../drivers/sensor/mysensor.c  etc with bindings one directory below and other such things.
 
In West workspace the app is at the same level as drivers, dts, CMakeLists, etc.
However if you simply load up in a VSCode workspace the app folder, you won't be able to access the custom drivers one directory down in ../drivers, ../dts, ../boards.
How do you structure an nRFConnect VSCode managed app so that it does the same thing?  Is there even a value in doing this or are you better off making a west workspace to perform app development with custom drivers?
Best,
Josh
Parents Reply Children
No Data
Related