Make bootload on WIO-5 mini (STM32WLE5JC) [SOLVED]

Use the 20-pin Header of the ST-LINK/V2

Get some dupont wires of your own

You want the SWDIO, SWCLK and GROUND at a minimum, on the official ST-LINK/V2 you need to power the buffers, so VCC also. You could also connect NRST

Pin 1 VCC

Pin 7 SWDIO

Pin 9 SWCLK

Pin 15 NRST

Pin 20 GROUND

I attached wires as you mentioned.

I pressed on Rest button on the WIO-5 Mini. Having this button pressed, I clicked on Connect button (having ST-LINK selected from the list).

Nothing changed. I ST-LNIK didn't recognize WIO-5. What am I missing?

@Community member​ 

So I will show you a little bit closer.

First view of ST-LINK connections

As you can see:

1. red -VCC
2. blue - SWDIO
3. yellow -SWCLK
4. white -NRST
5. gray - GND.

Next view of connections to WIO-5 Mini board:

1. red - 3.3V
2. blue - DIO
3. yellow - CLK
4. white - RST
5. grey - GND.

Having these connections, I press the Reset button on the WIO-5 mini board and hold it. Next, I click on the button Connect on the STM32 Cube Programmer window. It still doesn't recognize my WIO-5 Mini board.

Maybe these pieces of information will be helpful. WIO-5 mini is a brand new one. It was never programmed using STM-LINK or any other bootloader tool.

I expected it to be elementary, as for programming with Arduino IDE. But still have strange problems with the WIO-5 MIni board and ST-LINK.

PS. I can send AT commands to this board using Termite, in my case. It responds properly. So it works and is alive.

Maybe it will be helpful. I read the documentation of STM-LINK and found that I can check if my installation is proper. I run such a command:

STM32_Programmer_CLI -l usb

I got an unexpected result:

But I see ST-LINK in the device manager

I see it under the option Universal Serial Bus Devices and DM says that it works properly.

I checked Windows Update and USB 3.0 drivers. They are up to date.

What is wrong?

Something is wrong. ST-LINK doesn't see the WIO-5 mini-board.

I link the WIO-5 board to the STM32 by wires as is in the above pictures. I don't see any mistakes in the connections.

I applied a note from Drew from this thread How to fix STM32 Stuck with error ST-LINK error (DEV_TARGET_NOT_HALTED) - Electrical Engineering Stack Exchange and I got an answer:

And it is exactly my STM chip discovered.

But I still have this:

After several tries (button Boot pressed or PB13 connected to GND, VSS, or VCC) my WIO-5 mini doesn't respond on AT commands. So I guess that it isn't already in AT mode but still isn't in DFU mode.

It's the final cut and the end of the story (but I have to change Read Protection Level to AA - no protection):

My WIO-5 board is ready for programming now (I hope :) )

PS. It's the worst thing we - all developers - do during the overall software build process, from the backlog to the move of product to the market: DOCUMENTATION! Poorly written, unclear, and outdated.