PE Support

[wang-zhuo996]

As shown in the figure, when starting the PE gdb server, the extension automatically adds a service port of 50000, which causes the startup to fail.

This is the error log that I generated after I started with the following configuration.

    {
        "cwd": "${workspaceFolder}",
        "executable": "Tig200_S32K144.elf",
        "name": "Debug with PE",
        "request": "launch",
        "type": "cortex-debug",
        "device": "NXP_S32K1xx_S32K144F512M150N77P",
        "runToEntryPoint": "main",
        "showDevDebugOutput": "none",
        "servertype": "pe",
        
    },

Waiting for gdb server to start...[2025-03-26T09:19:48.729Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session connected. You can switch to "DEBUG CONSOLE" to see GDB interactions.
"C:\\PEMicro\\gdbserver\\pegdbserver_console.exe" -startserver -singlesession -device=NXP_S32K1xx_S32K144F512M150N77P -serverport=50000

P&E GDB Server for Arm(R) devices, Version 9.69.00.00
Copyright 2018, P&E Microcomputer Systems Inc, All rights reserved

Loading library C:\PEMicro\gdbserver\gdi\unit_ngs_arm_internal.dll ... Done.

Command line arguments: -startserver -singlesession -device=NXP_S32K1xx_S32K144F512M150N77P -serverport=50000 
Device selected is NXP_S32K1xx_S32K144F512M150N77P
HW Auto-Selected : Interface=USBMULTILINK Port=PE5750105   ; USB1 : Multilink Universal Rev A (PE5750105)
Connecting to target.
Unable to load libusb0.dll 
PEmicro Interface detected - Flash Version 6.15 
INFO: DAP IDCODE = 0x2BA01477 
INFO: DAP successfully powered up. DP CTRL/STAT = 0xF0000040 
Device is NXP_S32K1xx_S32K144F512M150N77P. 
Mode is In-Circuit Debug. 

(C)opyright 2012, P&E Microcomputer Systems, Inc. (www.pemicro.com)
API version is 101

TARGET XML PATH is C:\PEMicro\gdbserver\gdi\P&E\supportFiles_ARM\target_v7m_vfp.xml

PEmicro GDB Launch Failure : Could not bind socket.Another GDB Server debug session may be using the same Server Port number. To run simultaneous debug sessions, please specify a unique Server Port and GDBMI Port in the Debug Configuration for each project. If another session is not running simultaneously, make sure that the chosen port is available and that pegdbserver_console and the arm-none-eabi-gdb processes have terminated.

PE-ERROR: Unable to start server with the settings provided. Halting. 2203.
INFO: DAP IDCODE = 0x2BA01477 
Target Disconnected.
[2025-03-26T09:19:50.438Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed
GDB server session ended. This terminal will be reused, waiting for next session to start...

[wang-zhuo996]

And I checked the port usage of my computer, and found no use of port 50000 , but it still failed to launch.

[wang-zhuo996]

Is PE debugging still in its early stages?