System Workbench for STM32

Hi there,

about your first question:
When using the debug symbol (the little bug), the console output gets reset and just the output of the gdb call is left
(GNU gdb (GNU Tools for ARM Embedded Processors) 7.10.1.20160616-cvs
Copyright (C) 2015 Free Software Foundation, Inc. ... ).
Due to this, I'm using the Target->Erase/Program commands to avoid this (abnormal behaviour?).

The Nucleo ST-Link Debugger is completely disconnected from the Nucleo board itself and therefore, the Nucleo board gets it's power supply externally (so, JP5 is set to E5V).
All the other jumpers on the ST-Link / Nucleo board are setted as you described.

About my circuit:
I removed the external pull-up (I'm used to this by working e.g. with the AVRs), no change.
I also just connected vSSA and VDDA to GND.
The SWD connections I already described by the JP1 (on my board) to the debugger connections, so the connections i made are like:

Nucleo ST-Link Debugger -> Custom board:
(1) VDD_TARGET -> JP1-1 (3.3V)
(2) SWCLK -> JP1-2 (SWCLK)
(3) GND -> JP1-5 (GND)
(4) SWDIO -> JP1-3 (SWDIO)
(5) NRST -> JP1-4 (NRST)
Result: Doesn't work with mentioned error message (Cannot identify target bla bla).

Nucleo ST-Link Debugger -> Nucleo board with STM32L053:
(1) VDD_TARGET -> CN7-16 (3.3V)
(2) SWCLK -> CN7-15 (SWCLK)
(3) GND -> CN7-19 (GND)
(4) SWDIO -> CN7-13 (SWDIO)
(5) NRST -> CN7-14 (NRST)
Result: Works flawless, debugging, flashing, setting and removing breakpoints et cetera.

I'm also almost certain now, that it has nothing to do in special with the Nucleo ST-Link Debugger, as I borrowed one of these little chinese ST-Link clones from a work colleague (ebay-link, it looks like this ) and the same thing happens with this one.
Following up the connections I made with this second debugger:

Clone ST-Link Debugger -> Custom board:
(1) T_JRST -> JP1-4 (NRST)
(2) 3.3V -> JP1-1 (3.3V)
(4) T_SWCLK -> JP1-2 (SWCLK)
(6) T_SWDIO -> JP1-3 (SWDIO)
(7) GND -> JP1-5 (GND)
Result: Doesn't work with mentioned error message (Cannot identify target bla bla).

Clone ST-Link Debugger -> Nucleo board with STM32L053:
(1) T_JRST -> CN7-14 (NRST)
(2) 3.3V -> CN7-16 (3.3V)
(4) T_SWCLK -> CN7-15 (SWCLK)
(6) T_SWDIO -> CN7-13 (SWDIO)
(7) GND -> CN7-19 (GND)
Result: Works flawless, debugging, flashing, setting and removing breakpoints et cetera.

The interesting thing is, all four (!!) mentioned scenarios are able to flash the Nucleo board and my custom board, as well, using the ST-Link Utility.

About this strange error message:
Is there a possibility (e.g. a kind of -verbose switch to enable or similar) to get the information, which signature was read from my custom board, to compare it with the read signature by the ST-Link Utility?

Best regards,
Markus