STLINK-V3 MINIE V3J16M9 Firmware "STM32 Deubg+VCP" configuration non-functional VCP

[JohannesWilde]

For the last several days I have been trying to get the virtual COM port [VCP] of my STLINK-V3 MINIE to work together with my NUCLEO-H755ZI-Q. After realising that the VCP_RX/TX pins are not connected to the MIPI10 connector CN5 and thus soldering on my own cables and measuring the signal using an oscilloscope [confirming the signals were the expected 3.3V], I thought it should work.

However - even though the VCP was detected under Windows 11 and I double-checked the connection settings in my terminal application - I did not get any communication.

The solution seems to have been, to reprogram the V3 MINIE with the "STM32 Debug+Mass storage+VCP" firmware [Version V3J16M9]. After that it worked flawlessly [without changing anything else]. Previously the "STM32 Debug+VCP" V3J16M9 firmware version was flashed to it.

So my question is:

- Did I overlook some configuration option?

- Or is this a problem with the firmware and I should try to contact ST?

PS: The STLINK-V3 MINIE was bought quite recently - the sticker on it says "MB1762-V3MINIE-B01 K250401102".

[S C]

Hello,

You can get recent versions from STSW-LINK007 | Software - STMicroelectronics (several are available if you choose "select version")

CubeProgrammer (and other tools) deliveries are not synchronized with ST-Link firmware upgrade (they take the most recent available version when generating their release, but ST-Link firmware may evolve afterwards for boards production or bugfix purposes).

I tried the "STM32 Debug+VCP" V3J16M9 on my side and found no issue with the debug. May you please provide more details on the failure (which tool at host side, error message, LED state on the board, ...) ?

[mƎALLEm]

---

@S C wrote:

Hello,

I tried the "STM32 Debug+VCP" V3J16M9 on my side and found no issue with the debug. 

---

Ok it seems the latest version is on ST-LINK firmware upgrade tool which is for the moment the V3.J17.M10.

I tried V3.J17.M10 and didn't face any issue with that NUCLEO-H755ZI-Q board. 

@JohannesWilde I suspect you have another issue not linked to the ST link but to another issue probably linked to your power configuration that needs to be SMPS instead of LDO on that board!

[mƎALLEm]

---

@JohannesWilde wrote:

Additionally I did observe, that the on-board debugger on a NUCLEO-H755ZI-Q development board did not work when programmed with "STM32 Debug+VCP" V3J16M9.

 Can anyone else reproduce it in that way?

---

Just to be sure, what do you mean by "did not work when programmed with "STM32 Debug+VCP" V3J16M9" ? ST LINK doesn't connect anymore or you have an issue with the VCP?

From my side I have, the VCP is detected on Windows:

And I can connect to the board with STM32CubeProgrammer with the latest version of STLINK firmware: V3.J17.M10!

[JohannesWilde]

Thanks for the feedback,

it seems I have to correct my previous statement regarding the integrated debugger of the NUCLEO-H755ZI-Q development board.

1. All I was talking about was the communication [µC -> PC] via the virtual com port. Programming/debugging always worked fine.

2. After further testing with the non-mass-storage option of the V3J16M9 with the integrated debugger I did receive data:

3. Regarding the STLINK-V3 MINIE however, I will have to first connect the VCP pins in addition to the MIPI10-connector, to be able to provide further info.

Thanks for the feedback so far.

PS: @mƎALLEm regarding the power supply: My final implementation will use LDO [don't ask me why], which is why I adapted 1 of my 2 development boards to also use LDO. Programming/debugging always worked however - the only problem I had, was that the VCOM was not working.

[mƎALLEm]

---

@JohannesWilde wrote:

PS: @mƎALLEm regarding the power supply: My final implementation will use LDO [don't ask me why], which is why I adapted 1 of my 2 development boards to also use LDO. Programming/debugging always worked however - the only problem I had, was that the VCOM was not working.

---

That depends on if you will be using NUCLEO-H755ZI-Q or not. If you will use NUCLEO-H755ZI-Q, SMPS is not an option it's a must unless you modify the board's hardware to support the LDO power configuration, otherwise you will lock the MCU.

PS: if you solved your issue, please accept as solution the post that has answered your question.

[JohannesWilde]

@mƎALLEm Sorry if my formulation was not precise enough: "I adapted 1 of my 2 development boards" was supposed to mean that I added SB95, SB74, SB33, SB25 and removed SB92, SB79, SB76, R35 and added a C to VDD_LDO. This should enable me to use LDO, shouldn't it?

And as hinted to in point 3 above, I will have to modify the unchanged development board to also pass the VCP to the STLINK-V3 MINIE before I can say anything about my initial issue [non-working VCP with STLINK-V3 MINIE].

But thanks for your thoughts - they are appreciated.