Hello,

The behavior of the GDBServer has been changed a bit.
The problem in the old implementation was, that GDBServer was always trying connecting directly to the target when starting up
which did not allow the user to setup some basic settings like target endianess and initial JTAG speed which are necessary to guarantee a proper target connection.
The new version of the GDBServer waits to connect to the target until GDB requests a connection to the GDBServer.

As soon as you connect to the GDBServer, it connects to the target.
Example:
(Windows + r): arm-none-eabi-gdb
(gdb) target remote localhost:2331
--> Now GDBServer connects to the target


Best regards
Alex

Hi,

There is not much to understand:
a) The GDBServer waits for an incoming connection from GDB before it tries to communicate with the target
b) The example I added in my last post was a sample call to start GDB (by typing "arm-none-eabi-gdb" in the command line under Windows) and telling it to connect to a GDBServer on port 2331 (by typing "target remote localhost:2331")
(Should look like in the attached screenshots)

Hope it helps.

Best regards
Alex

Hi,

Of course there is a GDBServer version for Windows
It was there a long time before the Linux version. But according to your screenshots you are already using the Windows version.
If you mean if there is any new version:
The latest release version for Windows & Linux can always be downloaded here: segger.com/jlink-software.html
The latest beta version for Windows & Linux can always be downloaded here: segger.com/beta-software-version.html


Best regards
Alex