When I see in STM32CubeMX the X-CUBE-TOF1 package if I try to load it. He answers me this package is already there. , I don’t see it appearing under Middleware as in the user manual , UM2978

[Sara BEN HADJ YAHYA]

Hello @yves2brest​ ,

Thanks for your feedback,

I am not sure I understood correctly your request, could you please share a detailed scenario, or a capture describing your issue?

Thanks,

Sara.

[yves2brest]

Hello Sara, Excuse me, for not having answered you immediately, but to your message I understood that it was necessary to use CubeMX in Stm32CubeIde18 instead of CubeMX alone. Then the program did not work because there was a missing Callback function. in the main.c on the interrupt caused by the VL53L1 sensor on the X-NUCLEO-53L1A1 expansion board. I introduced this piece of code into the code generated by Stm32CubeIde18 but does not work. I think I have to ask another question and a TOF specialist will answer. in app_tof.c. I want introduce : RANGING_SENSOR_ROIConfig_t roiConfig; roiConfig.TopLeftX=12; roiConfig.TopLeftY=12; roiConfig.BotRightX=4; roiConfig.BotRightY=4; status = VL53L1A2_RANGING_SENSOR_ConfigROI(VL53L1A2_DEV_CENTER,&roiConfig ); tempstatus=status; if (status != BSP_ERROR_NONE) { printf("VL53L1A2_RANGING_SENSOR_Start failed ROI\n"); printf("status =%E\n, status"); while(1); Could you send me the name of a TOF specialist? Best regards Yves Mevel <> Garanti sans virus. www.avg.com <> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

[CLUGA.1]

Hello @yves2brest,

I read you didn't find the interrupt callback, it is coded within the file app_tof_pin_conf.c but I understood you found a way to fix it by yourself.

Regarding the ROI the definition of the region of interest is a bit tricky.

To match your needs you should set 

 roiConfig.TopLeftX=4;

 roiConfig.TopLeftY=12;

 roiConfig.BotRightX=12;

 roiConfig.BotRightY=4;

Best Regards,

Christophe Lugand