vl53l1x driver issue with nrf5340 and ncs 2.9.0

[finkbr]

Hi,

I have an application build using ncs 2.9.0 and a custom board using the nrf5340.

The issue is that I am migrating to 2.9.0 from 2.3.0  In 2.3.0 there was no included driver for vl53l1x and we included the driver in our build.  we used

CONFIG_VL53L1X=y and included the directories in the CMakeLists file.  it all worked perfectly.  Now migration to 2.9.0 happens and we now get duplicate definitions because that driver is now included in the zephyr directories.  

So im left with a few options, which i know how to do. 

1) Keep the config and somehow make sure the build system doesnt use the zephyr version of the driver

2) create a new CONFIG_VL53L1X_PRIV config option to include our own slightly modified version of the driver (i dont know how to do this, im still learning about how hardware definitions work)

3) use the new driver which im willing to do but have a few questions because its not building properly

For option 3 (Preferred) The problem i have is that i cant seem to find the include file #include <zephyr/drivers/sensor/...> doesn't find the driver directory  I found it under sensor/st/vl53l1x but that doesn't seem to work. the intellisense doesn't find it and it throws a build error that it cant find the include file. (

#include <zephyr/drivers/sensor/st/vl53l1x/vl53l1x.h>)

I'm not sure what I'm missing here. i would have thought including the header would be simple enough but its not finding it.

Thanks for the help

Brian

[runsiv]

Hi Brian

I think 2 is the best option here. It should be enough to just rename the Kconfig reference  in your driver. 
Unfortunately our driver course is not yet updated for NCS 2.9. But I think you still can use it as a guidance for Kconfig part https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-7-device-driver-model/topic/exercise-1-13/ 

Regards

Runar

[finkbr]

The answer above will work but im still having a problem where it tried to compile the zephyr version of the driver.  I cant seen to figure out how its getting included.  i changed the name of all the CONFIG_VL53L1X that I can find to CONFIG_VL53L1X_PRIV.  Searching my entire build source I cant find anything that would make it include the zephyr version.  Any hints?

[runsiv]

Could you upload your driver here so I can take a look? we can set the case to private if you don't want the driver public

Regards

Runar

[finkbr]

My driver is the same with only very minor tweaks (added a different init)  and driver structure, i dont know why.  Any ideas how the included driver is still being compiled?  if you make this private I can upload anything you want.

[finkbr]

I have been playing with this for hours.  basically i just want to use the vl53l1x driver included with zephyr.  i need to include the header in the file that needs the api.  i cant seem to do that.  is there some sort of work around where i can get this working?  i should be able to include <zephyr/drivers/sensor/vl53l1x.h) or something like that but its not there.  really need this to work so any help is greatly appreciated.

FYI: I tried to create a custom menu config but apparently was missing some include files from the actual driver so it didn't work correctly and since i didn't originally write the code for this I'm hesitant to copy all of the driver files from zephyr into my local vl53l1x directory since its not maintainable. the best bet after looking at the files and diffing them is to use the zephyr driver and get that working.