Skip to content

Conversation

@faxe1008
Copy link

@faxe1008 faxe1008 commented Nov 6, 2024

Adds the official ST library for the vl53l5cx tof sensor.

Will open the corresponding zephyr driver PR soonish.

Adds the official ST library for the vl53l5cx tof sensor.

Signed-off-by: Fabian Blatz <[email protected]>
@erwango
Copy link
Member

erwango commented Nov 19, 2024

Will open the corresponding zephyr driver PR soonish.

Thanks. Please ping us once it's ready for review

@erwango
Copy link
Member

erwango commented Mar 3, 2025

@faxe1008 Is this PR still in your plans ?

@faxe1008
Copy link
Author

faxe1008 commented Mar 3, 2025

Hey @erwango,

yeah so I did some work on the zephyr side for this:
faxe1008/zephyr@caf5525

But for some reason part of the initialization fails:
8fdc319#diff-909a8a275d4d87c7f05a575c52f45e54f5319a6babbf41300bcec44590ffa712R363

The plattform abstraction for the I2C seems to be working - I can read the sensor ID and the other operations prior to reading the NVM data in the init method seem to work. It's not really evident to me why this happens. Need to see if I can use a working refrence implementation and see what is happening there.
Besides that I wonder if the upload of the firmware does need to be part of init sequence, would hiding this behind a Kconfig flag be an accetable addition to cut down on flash usage?

So yeah, I'd love to continue on this one gotta find some time and a lead to fix up the init sequencing though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants