cancel
Showing results for 
Search instead for 
Did you mean: 

Can't access STM32-LPM01-XN via terminal after firmware update to v1.0.8

Abdessamad
Associate II

I’m using the X-NUCLEO-LPM01A (PowerShield) and previously had firmware version 1.0.1, where I could connect via a serial terminal over USB and interact with the board using commands.

But error occured short after, with LED 2 on the board indicating USB enumeration failure.

Updating the STM32-LPM01-XN firmware version to the latest one (1.0.8) solved that issue but now no sign of connection via a COM port terminal.

Everything works fine using via a graphical user interface using the STM32CubeMonitor-Power software tool.

But would prefer controlling via COM terminal ...

Thanks for the support

8 REPLIES 8
Andrew Neil
Super User

@Abdessamad wrote:

Everything works fine using via a graphical user interface using the STM32CubeMonitor-Power software tool.


But the GUI just connects to the board via COM port, surely?

You're not trying to use the terminal while the COM port is already in use by the GUI, are you ?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Thanks for your reply!

I can confirm the port is not in use by STM32CubeMonitor-Power when I try PuTTY.

Here are the settings I use:

Screenshot 2026-03-25 171643.png

Do you see the COM port in Device Manager ?

What, exactly, happens when you try to use PuTTY ?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.
Abdessamad
Associate II

I see the COM port in the device manager. 
however on putty i am not able to send any command (it is not responding to keyboard input), the window stays open without any activity.

previously on the 1.0.1 firmware version, i got welcome message when using putty.

Abdessamad
Associate II

IMG_1682.png

I have the same output from putty.

Show a screenshot of your PuTTY settings - are you sure it supports that baud rate?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.

Screenshot 2026-03-25 212803.png

Here are my settings.

I also tried with lower rates, but same issue.

The documentation mentions the following: "On host USB virtual COM port, configuration of baud rate may be not needed since replaced by USB maximum baudrate"

Your previous screenshot showed COM3; now you show COM9 - which is it ?

A complex system that works is invariably found to have evolved from a simple system that worked.
A complex system designed from scratch never works and cannot be patched up to make it work.