VL53L5CX GUI shows no list of VL53L5CX.

[WOh.1]

I purchased P-NUCLEO-53L5A1 including X-NUCLEO-53L5A1 and NUCLEO-F401RE.

And I assembled them and connect to PC, and then I installed its driver and reboot windows 10.

When connecting, the explorer open the mass storage drive (D: (F401RE)).

However, VL53L5CX GUI shows no list of VL53L5CX using X-NUCLEO-53L5A1 as the below

Even after pressing the refresh button several times, the result was the same.

 I changed the driver's port number from COM15 to COM2.

It's because COM1, COM3~COM15 were already used.

After this, the result was the same.

When I use X-NUCLEO-53L0A1 instead of X-NUCLEO-53L5A1, VL53L0X_GUI works well.

Even after changing NUCLEO-F401RE with X-NUCLEO-53L0A1's instead of X-NUCLEO-53L5A1's, VL53L5A1_GUI shows no list.

Even after updating ST-Link, VL53L5A1_GUI shows no list.

Even after copying 53L5A1_MultiSensorRanging.bin to D:, VL53L5A1_GUI shows no list.

Why does this happen? Is X-NUCLEO-53L5A1 broken?

Thanks in advance.

[Julien NGUYEN]

Hi

With the VL53L0X GUI, the GUI detects and flashes the FW into the Nucleo while with the VL53L5CX GUI you need to flash the FW by clicking on the "Flash FW" button in the "About" tab ?

Thanks,

Julien

[WOh.1]

Hi,

Thanks for prompt response, however I got a result as the below.

 

However, by using another NUCLEO-F401RE, "Flash FW" was OK.

Yes, you were right. After flashing and clicking on "Refresh List", COM port was shown.

And then "Connect" was OK and "Mini Depth-Map" tab works well.

The difference between the new NUCLEO-F401RE and the old one was that CN11 and CN12 were open, however this is not a problem.

After opening CN11 and CN12 for the new one, "Flash FW" was not working.

But, there is a workaround for this as the below GUI user manual.

4.3 Flash FW button failed (workaround)

1. Check the device is present in Device Manager

2. Copy the .bin file from C:\ProgramFiles\STMicroelectronics\VL53L5CX_Gui\Resources to the

drive with theNucleo device (e.g. NODE_F401RE(drive letter:)) by drag and drop

3. Close the application

4. Unplug / reinsert the device

5. Restart the application

Finally, the new one works well.

And I also found another difference between the old one and the new one.

It was their drive name. The old one is "NODE_F401RE (D:)" and the new one is "NOD_F401RE (D:)"

After changine the drive name to "NODE_F401RE", "flash FW" worked well.

Unfortunately, after flashing, the drive name was restored to its original name.

Best Regards,

Woojin

[KReic.1]

WOW! I had a very frustrating evening until I saw your post!! THANK YOU VERY MUCH!!! Putting the .bin file onto the device made it so I could connect, and then changing the name to add the "E" to make it "NODE_F401RE" allowed me to flash the FW. ST, can you permanently fix these things?!