VL53L4CD_GUI cannot detect X-NUCLEO-53L4A1 on NUCLEO-F401RE

[sawamura]

Hello,

I am using:

- NUCLEO-F401RE
- X-NUCLEO-53L4A1
- VL53L4CD_GUI (Rev 1.0.17549)

The VL53L4CD sensor is working correctly with the X-CUBE-TOF1 example
(53L4A1_SimpleRanging). I can read distance measurements through the
ST-Link Virtual COM Port.

However, VL53L4CD_GUI cannot detect the sensor.

When the GUI starts, it shows:

"Failed To Connect to Nucleo Board: Com Port Not Detected"

After pressing "Flash FW", it changes to:

"COM9 Connected: Sensor Not Detected.
Please ensure sensor connected then Press Black Reset Button on the Nucleo."

Additional information:

- ST-LINK is detected correctly.
- STLink Virtual COM Port (COM9) is available.
- STM32CubeProgrammer can connect successfully.
- The VL53L4CD sensor is confirmed to be working with the
  53L4A1_SimpleRanging example.
- The GUI remains in OFFLINE MODE and API Version shows TBC.

Has anyone successfully used VL53L4CD_GUI with
NUCLEO-F401RE + X-NUCLEO-53L4A1?

Is there a specific firmware required for the GUI?

Thank you.

[mfgkw]

Hi,

 

Your F401 still contains the “simple ranging” example?

 

Along with the GUI package in STSW-IMG045 there should be a bin file which has to be flashed on the F401 to communicate with the GUI on your PC.

[sawamura]

Thank you for your reply.

Did you mean STSW-IMG027?
I am using VL53L4CD GUI package STSW-IMG027.

Where is the .bin file located?

Thank you.

 

[mfgkw]

Sure, take whatever matches your board.

I do not use Windows, but I installed STSW-IMG027 in a Windows 11 VM and find the firmware here:

C:\STMicroelectronics\VL53L4CD_GUI\Resources\VL53L4CD_PSNRun_F401.bin

[sawamura]

Hi,

 

Thank you for providing the firmware file.

 

I flashed the file:

VL53L4CD_PSNRun_F401.bin

to the NUCLEO-F401RE using STM32CubeProgrammer.

Current status:

- If I simply program the .bin file, VL53L4CD_GUI cannot connect.

- I found that if I enable the option "Run after programming" in STM32CubeProgrammer during the programming process, VL53L4CD_GUI is sometimes able to connect successfully.

- When the connection succeeds, the GUI shows:

  Device Name: VL53L4CD

  API Version: api rev 0.2.2 build 3

- However, the connection is very unstable.

- Most of the time the GUI shows:

  "Failed To Connect to Nucleo Board: Com Port Not Detected"

- Occasionally the GUI works, but in most cases it does not.

Additional information:

- STMicroelectronics STLink Virtual COM Port is always visible in Windows Device Manager.

- The COM port remains available even when the GUI reports "Com Port Not Detected".

- After power cycling the board and reopening the GUI, the problem returns.

- Reprogramming the same .bin file does not always restore communication.

- I cannot identify what condition makes the GUI connect successfully.

Could you please advise:

1. Is there a required startup sequence for the GUI and NUCLEO board?

2. Should the firmware automatically start after reset and power cycle?

3. Is there any known issue with VL53L4CD_PSNRun_F401.bin on NUCLEO-F401RE?

4. How can I verify that the GUI firmware is running correctly after reset?

 

Thank you.

[mfgkw]

I can not tell anything about this, because it happens in Windows and outside my world.

But it is a different issue than your thread starter. So you should start a new question on this (after trying other USB cables and USB ports).

[sawamura]

Hi,

Thank you for your reply.

 

I understand.

 

I will create a new topic for this issue and continue the investigation there.

 

Thank you for your support.