Skip to main content
N
NEO-MEC
Visitor II
May 17, 2024
Solved

The sample code for the VL53L5A1 sensor cannot be built.

  • May 17, 2024
  • 2 replies
  • 2336 views

This is my first time posting.

Thank you for viewing.

 

・I would like to use the VL53L5A1 sensor with the STM32L0 series.

・Created according to the manufacturer's document "UM2974".

・When I created it with STM32CubeMX Ver6.11.0, the build did not pass.

The device used is "NUCLEO-L010RB".

・It says that "53l5a1_conf.h" does not exist, but is it not generated?

 

I would like to know the solution.

thank you.

 

Best answer by Zhiyuan.Han

Hi 

Our X-CUBE-TOF expert started from scratch CubeMX 6.11.0 with TOF1 v342 for 53L5A1_SimpleRanging example on NUCLEO-L010RB, All is fine it's compiling on CubeIDE...
please try attached the .ioc to see if help.

 

Br

Zhiyuan.Han

2 replies

Anne BIGOT
Anne BIGOT
Technical Moderator
May 21, 2024

Hello

Your request was raised internally. We will come back to you soon.

Best regards

 

Our community relies on fruitful exchanges and good quality content. You can thank and reward helpful and positive contributions by marking them as 'Accept as Solution'. When marking a solution, make sure it answers your original question or issue that you raised. ST Employees that act as moderators have the right to accept the solution, judging by their expertise. This helps other community members identify useful discussions and refrain from raising the same question. If you notice any false behavior or abuse of the action, do not hesitate to 'Report Inappropriate Content'
Zhiyuan.Han
Zhiyuan.HanBest answer
Technical Moderator
August 29, 2024

Hi 

Our X-CUBE-TOF expert started from scratch CubeMX 6.11.0 with TOF1 v342 for 53L5A1_SimpleRanging example on NUCLEO-L010RB, All is fine it's compiling on CubeIDE...
please try attached the .ioc to see if help.

 

Br

Zhiyuan.Han

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Terms & ConditionsAccessibility statement