FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Is STM32CubeMonitor a standalone application?

Go to solution
Kmax18
Senior

‎2024-01-30 07:49 AM - edited ‎2024-01-30 07:56 AM

Hello, from what I read in the ST wiki I understand that the STM32CubeMonitor (MON) is a standalone application? A P2P connection to the 'probe' (e.g. the ST-LINK/V2) is used in this configuration.
That means: it is not required that the STM32CubeIDE runs in Debug mode. Please confirm, thanks!

I also understand that the MON can be used together with the IDE, using a TCP link (not P2P).

I am asking because, although MON reports a P2P, it also logs error code 245:

[2024-01-28T17:01:46.160] [ERROR] stlinkprotocol - [stlinkprotocol.js - connectToTarget(1063:16)] - enterSWD error = 245

More in this post:

https://community.st.com/t5/stm32cubemonitor-mcus/connect-stm32cubemonitor-to-st-link-v2-enterswd-error-245/td-p/633168

Any comments? Thank you!

0 Kudos
1 ACCEPTED SOLUTION

Accepted Solutions
Go to solution
stephane.legargeant
ST Employee

‎2024-01-30 10:08 AM

Hello

STM32CubeMonitor is a stand alone application and is directly taking control of the probe. 

Please, note that in P2P mode, the ST-Link can not be shared between STM32CubeIDE, other IDE and STM32CubeMonitor.  The first tool that establish connection will block the other tools.

CubeMonitor takes control of the probe in two way :

  • during the acquisition
  • when there is no acquisition ongoing, CubeMonitor initiate a connection on a regular basis to update the connection status. 

If the IDE or programmer is using the probe (debug or flashing the target) when CubeMonitor check the connection, it will log a connection error. But it will retry later, so should not block, so you can flash with IDE and few second later perform acquisition with CubeMonitor. But you can not debug and perform the acquisition at the same time.  It may be the cause of the error you have seen.

 

If you want to use CubeIDE and CubeMonitor at the same time, you can switch to "shared" mode. (TCP)

It is a local TCP sharing between the probe, the IDE and CubeMonitor.

The page STM32CubeMonitor:How to configure shared mode - stm32mcu will help you to configure the share mode.

I hope it answers your question.  Let us know if you have additional questions. 

View solution in original post

1 REPLY 1
Go to solution
stephane.legargeant
ST Employee

‎2024-01-30 10:08 AM

Hello

STM32CubeMonitor is a stand alone application and is directly taking control of the probe. 

Please, note that in P2P mode, the ST-Link can not be shared between STM32CubeIDE, other IDE and STM32CubeMonitor.  The first tool that establish connection will block the other tools.

CubeMonitor takes control of the probe in two way :

  • during the acquisition
  • when there is no acquisition ongoing, CubeMonitor initiate a connection on a regular basis to update the connection status. 

If the IDE or programmer is using the probe (debug or flashing the target) when CubeMonitor check the connection, it will log a connection error. But it will retry later, so should not block, so you can flash with IDE and few second later perform acquisition with CubeMonitor. But you can not debug and perform the acquisition at the same time.  It may be the cause of the error you have seen.

 

If you want to use CubeIDE and CubeMonitor at the same time, you can switch to "shared" mode. (TCP)

It is a local TCP sharing between the probe, the IDE and CubeMonitor.

The page STM32CubeMonitor:How to configure shared mode - stm32mcu will help you to configure the share mode.

I hope it answers your question.  Let us know if you have additional questions. 

Top