ST-LINK V2 does not work

[Frozenhore]

Hi!

I would like to ask for a little help. I have a LoraWan E5 wich I want to program with ST-Link V2, but as soon as I want to connect to it in the STM32CubeProgrammer I get the errors below. I also attached the pinout that I follow. I connect SWDIO, SWCLK, 5V and GND to the LoRa e5 mini. If I ping the lora with an AT command it responses on the serial monitor so the LoRa is ok. I updated the firmware wich was successful, also tried to set to reset mode and press the RST button while connecting but none of these are work. How would I be able to connect it?

[Andrew Neil]

So adding RST would be good.

[Frozenhore]

Wired it from Pin 15, but did not help. I am also pushing rst button when clicking on connect.

[Frozenhore]

Still no solution, anyone any idea? Im googling like for days now but still cannot find a solution for it.

[Andrew Neil]

Again, Have you contacted Seeed Studio for support? It's their board...

[Techn]

Please read the wiki page carefully!!!

The AT command firmware contains a bootloader for DFU and the AT application. The "PB13/SPI_SCK/BOOT" pin is used to control Wio-E5 to stay in the bootloader or jump to the AT application. When PB13 is HIGH, the module will jump to AT application after reset, with a default baud rate of 9600. When PB13 is LOW (press the "Boot" button on Wio-E5 mini), the module will stay in the bootloader, and keep transmitting "C" character every 1S at baud rate 115200.

If you remove the built in fimware, be sure to have a backup of the firmware or download from wherever it is..

tip

• Factory AT Firmware is programmed with RDP(Read Protection) Level 1, developers need to remove RDP first with STM32Cube Programmer. Note that regression RDP to level 0 will cause a flash memory mass to erase and the Factory AT Firmware can't be restored again.
• The "PB13/SPI_SCK/BOOT" pin on the Wio-E5 module is just a normal GPIO, not the "BOOT0" pin of the MCU. This "PB13/SPI_SCK/BOOT" pin is used in the bootloader of the Factory AT firmware, to decide to jump to APP or stay in bootloader(for DFU). The real "BOOT0" pin doesn't pinout to the module, so users need to be careful when developing the low-power applications