Troubleshooting

This article describes some common issues and gives possible causes and remedies.

1. STM32CubeMonitor cannot connect to the board

Possible cause:

  • The firmware running on the target is forcing a Low power mode. Communication with ST-LINK is disabled when the board is in Low power mode.
  • The target is secured or debug-disabled. STM32CubeMonitor is not able to connect in this case.

2. STM32CubeMonitor cannot connect to the board in TCP mode

Possible cause and remedy:

  • The STLLinkServer driver is not present. Install STLink server.
  • Another application is connected without Shared mode on the ST-LINK. Set the other applications to share the ST-Link .