cancel
Showing results for 
Search instead for 
Did you mean: 

Simple Ranging Error

Buntice
Associate II

Hi I'm new to the STM32 series, I have a NUCLEO-F401RE and the X-NUCLEO-53L8A1. I am trying to edit the code from the X-CUBE-TOF1 SW package but run into the error below when compiling. Any ideas on how to resolve this issue?

 

Log output file: C:\Users\username\AppData\Local\Temp\STM32CubeProgrammer_a19188.log

ST-LINK error (DEV_USB_COMM_ERR)

Encountered Error when opening C:\ST\STM32CubeIDE_1.14.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.1.100.202311100844\tools\bin\STM32_Programmer_CLI.exe

Error in STM32CubeProgrammer

Shutting down...

Exit.

1 ACCEPTED SOLUTION

Accepted Solutions
Buntice
Associate II

Update: It was the cable that I was using to connect to my laptop that was the problem. A new one resolved the issue :grinning_face_with_sweat:

View solution in original post

3 REPLIES 3
SofLit
ST Employee

Hello and welcome to the community.

When compiling? or when launching a debug session?

Could you please provide more details of the steps you followed and the tools you used for each step?

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.
Buntice
Associate II

Thanks for the quick reply.

It's when launching the debug session in the following file (as pictured) after downloading and unzipping it from the link (X-CUBE-TOF1)Screenshot 2024-05-09 163113.png

I was following the steps from the quick start guide (attached) and was able to get the sensor working following flashing the drive with the binary file. However I want to add to the simple ranging project and hence was trying to open and run the project above. I was following UM3108 section 4.1.2.1 (also attached) but the file above already had all of the settings set as required for the 53L8A1 and hence I skipped steps 7 to 21 (as they were already set in this project file) but was then unsuccessful in being able to use it when it comes to step 23 (launching the debugger).

Please let me know if you require any more information :)

Buntice
Associate II

Update: It was the cable that I was using to connect to my laptop that was the problem. A new one resolved the issue :grinning_face_with_sweat: