Error in services launch sequence. PEmicro GDB Launch Failure

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Error in services launch sequence. PEmicro GDB Launch Failure

Jump to solution
12,102 Views
myna
Contributor III

Hello.

When downloading s32k118EBV sample code, the following error occurs.

Error in services launch sequence
PEmicro GDB Launch Failure : Could not bind socket. Address and port are already in use. 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.

Please check attached capture file.

How can I solve this problem???

Labels (1)
1 Solution
11,531 Views
myna
Contributor III

I did check netstat, it was already using the gdb port elsewhere.

So, I did change GDB Server port Number in Debug Configuration--> GDB Server Settings

Eventually, the problem was solved.

Thank you.

myna

View solution in original post

5 Replies
11,531 Views
myna
Contributor III

I've already checked, but there is no running  pegdbserver_console.

Is there any other solution?

0 Kudos
Reply
11,532 Views
jiri_kral
NXP Employee
NXP Employee

You can check if any other application isn't using gdb server's port. You can use windows commandline> netstat -a -b 

pastedImage_1.png

Assuming that restart of your PC machine also doesn't help, correct? 

Jiri 

0 Kudos
Reply
11,532 Views
myna
Contributor III

I did check netstat, it was already using the gdb port elsewhere.

So, I did change GDB Server port Number in Debug Configuration--> GDB Server Settings

Eventually, the problem was solved.

Thank you.

myna

7,852 Views
yangjinzhuang
Contributor IV

What GDB server port number should I set for the two cores?

0 Kudos
Reply
11,531 Views
jiri_kral
NXP Employee
NXP Employee

Hi, 

check if there is no another pegdbserver_console instance running in Windows task manager (CTRL+SHIFT+ESC). If yes - end the task. 

Jiri

0 Kudos
Reply