VL53L5CX offline

[JVane.1]

I purchased X-NUCLEO-53L5A1 and NUCLEO-F401RE board. I assembled them and followed the Quick start guide X-NUCLEO-53L5A1 manual. I can't connect the device in the VL53L5CX.

 I update firmware and ST-Link before. I connected to the ST COM port via terminal. Report you can find in the attachment.

Why does this happen?

Thank you in advance.

Jan

[John E KVAM]

When it failed did you close the app, disconnect the USB, wait a couple of seconds, re-plug the USB and try again?

You cannot have your Putty conneced when trying to run the demo. I'm assuming you only connected the Putty once you had a failure. (I'm always forgetting to close my putty window when I want to connect the demo.)

You did notice that the user manual is the 4th button down. You clicked on it and went through it.

There is a debug dump button at the bottom. I've not had great luck with it, but knowing what is in the file is sometimes useful.

From the front screen I can see that the software found the serial port, and the disk drive. So your cable is fine.

But fairly often these days, IT departments are disabling the ability to talk to thumb drives. (To avoid viruses.) Could you again click on Flash FW and make sure the LED is flashing.

• john

[JVane.1]

Hello John,

thank you for response.

Q: When it failed did you close the app, disconnect the USB, wait a couple of seconds, re-plug the USB and try again?

• Yes, I tried it.

Q: You cannot have your Putty conneced when trying to run the demo. I'm assuming you only connected the Putty once you had a failure. (I'm always forgetting to close my putty window when I want to connect the demo.)

• Of course, I run Putty without demo application. Putty display text after pushing black button reset.

Q:You did notice that the user manual is the 4th button down. You clicked on it and went through it.

There is a debug dump button at the bottom. I've not had great luck with it, but knowing what is in the file is sometimes useful.

• You could find debug log below:

20.01.23_08:07:378: Command:   set comms media=UART

20.01.23_08:07:379: Response:   000CRES=00000000END

20.01.23_08:07:379: Extra Data:   

20.01.23_08:07:379: Command:   get info=hw

20.01.23_08:07:380: Response:   0020RES=FFFFFF0F:Sensor boot failed!END

20.01.23_08:07:380: Extra Data:   Sensor boot failed!

20.01.23_08:07:399: Command:   set comms media=UART

20.01.23_08:07:400: Response:   000CRES=00000000END

20.01.23_08:07:400: Extra Data:   

20.01.23_08:07:400: Command:   set power=on

20.01.23_08:07:404: Response:   0018RES=FFFFFF0F:Init FailedEND

20.01.23_08:07:404: Extra Data:   Init Failed

20.01.23_08:07:517: Command:   set comms media=UART

20.01.23_08:07:518: Response:   000CRES=00000000END

20.01.23_08:07:518: Extra Data:   

20.01.23_08:07:519: Command:   get info=hw

20.01.23_08:07:519: Response:   0020RES=FFFFFF0F:Sensor boot failed!END

20.01.23_08:07:519: Extra Data:   Sensor boot failed!

20.01.23_08:07:520: Command:   set comms media=UART

20.01.23_08:07:520: Response:   000CRES=00000000END

20.01.23_08:07:520: Extra Data:   

20.01.23_08:07:521: Command:   get info=hw

20.01.23_08:07:522: Response:   0020RES=FFFFFF0F:Sensor boot failed!END

20.01.23_08:07:522: Extra Data:   Sensor boot failed!

Q:But fairly often these days, IT departments are disabling the ability to talk to thumb drives. (To avoid viruses.) Could you again click on Flash FW and make sure the LED is flashing.

• LED LD1 flashing during Flash FW.

Jan

[John E KVAM]

ideas -

Try a different PC if you can. I had one guy who had the only PC in his office that for some reason just did not work. I would be interesting if there was another in existance.

Update your STLINK software:

STSW-LINK007ACTIVEDevelopment ToolsSoftware Development ToolsST-LINK, ST-LINK/V2, ST-LINK/V2-1, STLINK-V3 boards firmware upgrade

It might be an older version cannot handle the high baudrates we use.

-john

[JVane.1 · Accepted solution]

I found that it is possible to connect the sensor by following this procedure:

• run GUI
• activate Connect button
• Push black reset button on nucleo board several times.

Thank you for support.

Jan

[Kbitsnbyte]

Hello John- I am experiencing (unresolved) issues that are pretty much identical to this thread. I have attempted all of the suggested remedies- including using a different laptop, which produced the same result. It does not seem as if this thread was ever resolved from a technical perspective. Would you have any further thoughts or suggestions? Thanks much!

20/07/23_14:52:294: Command: set comms media=UART
20/07/23_14:52:295: Response: 000CRES=00000000END
20/07/23_14:52:295: Extra Data:

20/07/23_14:52:295: Command: get info=hw
20/07/23_14:52:296: Response: 0020RES=FFFFFF0F:Sensor boot failed!END
20/07/23_14:52:296: Extra Data: Sensor boot failed!

20/07/23_14:52:297: Command: set comms media=UART
20/07/23_14:52:297: Response: 000CRES=00000000END
20/07/23_14:52:297: Extra Data:

20/07/23_14:52:298: Command: get info=hw
20/07/23_14:52:299: Response: 0020RES=FFFFFF0F:Sensor boot failed!END
20/07/23_14:52:299: Extra Data: Sensor boot failed!

20/07/23_14:52:323: Command: set comms media=UART
20/07/23_14:52:323: Response: 000CRES=00000000END
20/07/23_14:52:323: Extra Data:

20/07/23_14:52:324: Command: set power=on
20/07/23_14:52:328: Response: 0018RES=FFFFFF0F:Init FailedEND
20/07/23_14:52:328: Extra Data: Init Failed

[NKhan.7]

Same error as above. I've also tried all these steps to no avail. Both LD1 and LD2 are GREEN now. LD1 was flashing green and red during the Firmware Flash stage. LD3 is red.

In Device Manager I do see the "ST-Link Debug" and "STLink Virtual Com port (COM7)" listed.

I've tried resetting the board both via disconnecting and reconnecting USB and also via the black RESET switch but that doesn't help.

Please help...

Below are the two dump files that I generated:

//VL53L5CXDebugDump_xxxx.ini dump log
[Application Info]
App Rev=2.2.0.27498
Driver Rev=TBC
FW Ver=TBC
Device FW Version=TBC
Board Info=TBC
Product=TBC

//Commands dump log
27/09/23_13:41:119: Command: set comms media=UART
27/09/23_13:41:120: Response: 000CRES=00000000END
27/09/23_13:41:120: Extra Data:

27/09/23_13:41:121: Command: get info=hw
27/09/23_13:41:121: Response: 0020RES=FFFFFF0F:Sensor boot failed!END
27/09/23_13:41:121: Extra Data: Sensor boot failed!

27/09/23_13:41:250: Command: set comms media=UART
27/09/23_13:41:250: Response: 0018RES=FFFFFF0F:Init failedEND
27/09/23_13:41:250: Extra Data: Init failed

27/09/23_13:41:251: Command: get info=hw
27/09/23_13:41:252: Response: 000CRES=00000000END
27/09/23_13:41:252: Extra Data:

27/09/23_13:41:252: Command: set comms media=UART
27/09/23_13:41:253: Response: 000CRES=00000000END
27/09/23_13:41:253: Extra Data: