cancel
Showing results for 
Search instead for 
Did you mean: 

ST-Link V2 to target SWD connection fails with STM32CUBEIDE but works with Stm32CubeProgrammer

BMorg.1
Associate

I wondering about this in STM32CUBEIDE: Reading 0x20 bytes of memory from addr 0xe00fffd0

MCU: STM32F103RBT6

STM32CUBEIDE log tail (for full log see attachment)

[4.313] handlePacket(): Reading 0x20 bytes of memory from addr 0xe00fffd0

[4.313] write(): <572> Tx: $0000000000000000000000000000000010000000040000000a00000000000000#36

[4.360] read(): <572> Rx: $vKill;a410#33

[4.360] handlePacket(): Hidden/Unsupported v-command 'vKill', see RSP for details

[4.360] write(): <572> Tx: $#00

[4.360] read(): <572> Rx: $k#6b

Stm32CubeProgrammer log:

17:38:27 : ST-LINK SN : 53FF6B065177485738500887

17:38:27 : ST-LINK FW : V2J37S7

17:38:27 : Board      : --

17:38:27 : Voltage    : 1.90V

17:38:27 : SWD freq   : 4000 KHz

17:38:27 : Connect mode: Under Reset

17:38:27 : Reset mode : Hardware reset

17:38:27 : Device ID  : 0x410

17:38:27 : Revision ID : Rev X

17:38:29 : UPLOADING OPTION BYTES DATA ...

17:38:29 :  Bank         : 0x00

17:38:29 :  Address      : 0x4002201c

17:38:29 :  Size         : 8 Bytes

17:38:29 :  Bank         : 0x01

17:38:29 :  Address      : 0x1ffff800

17:38:29 :  Size         : 16 Bytes

17:38:29 : UPLOADING ...

17:38:29 :  Size         : 1024 Bytes

17:38:29 :  Address      : 0x8000000

17:38:29 : Read progress:

17:38:29 : Data read successfully

17:38:29 : Time elapsed during the read operation is: 00:00:00.006

0 REPLIES 0